Installing the Web Interface › Deploy the Web Interface (Oracle Iplanet Web Server)

Deploy the Web Interface (Oracle Iplanet Web Server)

On Windows, UNIX and Linux, you can deploy the Web Interface under Oracle Iplanet Web Server; perform the following procedure from Step 2.

On Solaris, if you are not able to start Oracle Iplanet Server after deploying Web Interface with supported version of Oracle Iplanet Web Server following Step2, then perform Step1 and try to access Web Interface.

Follow these steps:

1. Update the Java Home by completing the following steps:
   1. Start the Administration Server.
   2. While running Oracle Iplanet Web Server, run the script set_start (this script was created during the Web Interface installation) from a console.
   3. Run the following command from same console.

      Replace Oracle Iplanet Web Server Installation Home with the installation home directory (for example, /bsohome/harweb/oracleiplanetwebserver) for Oracle iplanet web server.

      Replace configuration node directory with the configuration node directory name.

      webservd -d Oracle Iplanet Web Server Installation Home/configuration node directory/config -r /b
      

      For example:

      webservd -d /bsohome/harweb/Oracle Iplanet/https-bso-sd-sun/config -r /b
      

      Note: To stop the server instance, use the script (stopserv) provided by Oracle iplanet web server.

   4. Log in to the Admin console of Oracle iplanet web server.
   5. Select the specific configuration under Configuration Tasks.
   6. Click Edit Configuration.
   7. Select Java.
   8. In the Java Home path field, enter the full path to the JDK 1.6.x installation on the application server computer.
   9. Click Save and then deploy the pending changes.
2. Deploy the Web Interface by completing the following steps using the Admin Console of Oracle Iplanet Web Server:
   1. Start the Administration Server.
   2. Log in to the Admin console of Oracle Iplanet Web Server.
   3. Select the specific Virtual Server under Virtual Server Tasks.
   4. Click Add Web Application.
   5. Select the Specify a package file or a directory path that must be accessible from the server option.
   6. In the WAR file path field, enter the complete path name of the WAR file on the application server computer.
   7. For the Application URL, enter /webapp-name

      Note: webapp-name is the name of your Web Interface application instance.

   8. For Target Directory, select Default if you want to install under default path; otherwise, provide the specific path.
   9. Click OK to deploy.
   10. To apply the pending changes, click Deployment Pending.
   11. Click Deploy.
   12. Wait for it to finish.

       Important! You can enter non-English characters (such as Japanese or accented characters) when you specify the name of the context root (WAR file name). Note, however, that .WAR file names with non-English characters may lead to problems due to system limitations in some servlet containers. If your .WAR filename contains non-English characters, Tomcat and other application servers may not be able to generate a context with a matching name. Therefore, you should use only single-byte, English characters when you name the .WAR file you are creating, especially for Tomcat.

   13. (For Oracle Iplanet Server on Linux operating systems only) Copy the following libraries from $CA_SCM_HOME/lib to HARWEB_INSTALLATION_HOME/WEB-INF/lib:

       libhcomm.so
       libhutils.so
       libharagent.so
       libsignfile.so
       libhauth.so
       libhauthserver.so
       

   14. Restart the Oracle Iplanet Web Server.
   15. Point a browser to http://host-name[:port]/webapp-name/

       Note: host-name is the name of your application server host computer, :port is an optional port number, and webapp-name is the name of your Web Interface application instance.

   16. When the initial CA Harvest SCM page appears, verify that you can log in to the Web Interface.