Siebel Analytics Installation and Configuration Guide > Installing Siebel Analytics Software in the UNIX Environment > Installing Siebel Analytics Web Components >

Installing Siebel Analytics Web on WebSphere

To install Siebel Analytics Web on WebSphere, you perform the following process:

To confirm that the WebSphere daemon is running

  1. Log in as root.
  2. Start a telnet session to the AIX machine.
  3. Run the following command.

    ps -ef | grep WebSphere

    If WebSphere is running, you should see a list of grep results.

  4. If Siebel Analytics had been previously installed, but is not installed now, you may see an error message when starting WebSphere. If you receive an error message, do the steps listed in To modify setupCmdLine.sh file to include Siebel Analytics environment variables.

To modify setupCmdLine.sh file to include Siebel Analytics environment variables

  1. Start a telnet session to the machine on which WebSphere is installed.
  2. Navigate to $WAS_HOME/bin.

    NOTE:  $WAS is the directory where WebSphere is installed, usually
    /usr/WebSphere/AppServer.

  3. Edit the setupCmdLine.sh file to append the following command to the last line:

    . INSTALLDIR/setup/sa-webinit.sh

    For example,

    . /usr/local/SiebelAnalytics/setup/sa-webinit.sh

    NOTE:  Include the period and space at the beginning of the line.

To stop the Web server

  1. Start the WebSphere Advanced Administration Console. Do this using one of the following methods:
    • Start the Windows Administration Client.

    $WAS\bin\adminclient.bat <Server Name>

    • Run the Administration Console through X Window.

    $WAS/bin/adminclient.sh <Server Name>

  2. Remove all Siebel Analytics-related services under the Enterprise Applications directory.
    1. In the WebSphere Administrative Domain tree, expand the Enterprise Applications directory.
    2. Right-click on the Analytics Enterprise and choose Stop. Remove the service.

To restart WebSphere

  1. Return to the WebSphere Advanced Administrative Console session.
  2. Run the following commands:

    ps -ef|grep Web

    /usr/WebSphere/AppServer/bin

    ./startupServer.sh &

    ps -ef|grep Web

    The process requires approximately a minute to finish.

  3. Open up the WebSphere Advanced Administrative Console on AIX or Windows.

    If the Server started successfully, you should see the following output in the WebSphere Advanced Administrative Console Event Message pane:

    SRVE0171I: Transport http is listening on port 9080.

    NOTE:  Port 9080 is the port that the embedded HTTP Listener (Web Server) awaits requests.

  4. Point a Web browser to http://<Server Name>:<Port>/webapp/examples/.

    You should see the WebSphere Application Server Examples home page.

  5. To see the IBM WebSphere Web Container configuration, click the Show server configuration hyperlink.

To create a new application server

  1. In the WebSphere Advanced Administrative Console, expand the WebSphere Administrative Domain tree to Nodes > Application Servers.
  2. Right-click and choose New.
  3. In the Create Application Server dialog box, enter the values for the Application Server name and the Working directory. Click OK.
  4. Click OK on the confirmation dialog box.

To create a WAR file

  1. Start a telnet session to a machine that has Siebel Analytics Web installed.
  2. Navigate to the Siebel Analytics installation directory. For example:

    /usr/local/SiebelAnalytics

  3. Set the JAVA_HOME environment variable, if it is not already set.

    env | grep JAVA_HOME

    setenv JAVA_HOME /usr/java130

  4. Run the jar command to create the WAR file:

    $JAVA_HOME/bin/jar cf Analytics.war -C Web/Servlet .

    NOTE:  You must include the "." at the end of the command.

To deploy the WAR file

  1. In the WebSphere Advanced Administrative Console, go to Click the Install stand-alone module radio button.
  2. Click Browse, then click Open.
  3. In the Application name field, enter an arbitrary name (for example, Analytics).
  4. In the Context root for web module field, enter Analytics.
  5. Click Next until the Selecting Application Servers window opens.

    If the Virtual Host value is empty, select default_host.

  6. Click Select Server.

    Select the server created in To create a new application server.

    NOTE:  Do not use the default server.

  7. Click Finish.

To restart WebSphere

  1. In the WebSphere Advanced Administrative Console, navigate to WebSphere Administrative Domain > Nodes > Server Name.

    Right-click the server and choose Stop. In the confirmation dialog box, click Yes.

  2. After the WebSphere Advanced Administrative Console closes, start a telnet session to the machine on which WebSphere has been installed.
  3. Navigate to $WAS_HOME/bin.
  4. Run the following command:

    ps -ef | grep WebSphere

    Confirm that only the grep WebSphere process is running (that is, that WebSphere is stopped).

  5. Run the following command:

    nohup ./startupServer.sh &

    Wait while WebSphere starts. WebSphere is started when the time column no longer increases when running multiple iterations of ps -ef | grep WebSphere.

  6. Start the WebSphere Advanced Administrative Console.
  7. Regenerate the plug-in by right-clicking on Node Name and Regen WebSphere Plugin.
  8. Start the Application Server that you defined earlier.

To confirm Analytics Web is functioning

To check the port number being used by Siebel Analytics

  1. In the WebSphere Advanced Administrative Console, navigate to WebSphere Administrative Domain > Nodes > SiebelAnalytics Web.
  2. In the Name pane, select Installed EJB Modules.
  3. Click the Services tab and, in the Service window, choose Web Container Service. Click Edit Properties.
  4. Click the Transport tab and, in the HTTP transports window, note the port number for the host.
  5. Navigate to WebSphere Administrative Domain > Virtual Hosts. For default_host, click the General tab.

    Check that the port number appears in the Aliases list. If it does not, add it.


 Siebel Analytics Installation and Configuration Guide
 Published: 09 September 2004