4 Installing and Configuring WebSphere for Oracle Identity Manager

This chapter explains how to set up WebSphere before and after installing Oracle Identity Manager. You must perform the following pre- and post-installation tasks:

Note: Refer to "Deploying in a Clustered WebSphere Configuration" if you are using WebSphere in an application server cluster.

1. Install the WebSphere Application Server—see "Installing the WebSphere Application Server" on page 4-1 for more information.

2. Install WebSphere Application Client—see "Installing the WebSphere Application Client" on page 4-2 for more information.

3. Enable SOAP Communication to WebSphere—see "Enabling SOAP Communication with WebSphere" on page 4-2 for more information.

4. Upgrade WebSphere server and client software—see "Upgrading the WebSphere Server and Client" on page 4-3 for more information.

5. Prepare the environment—see "Setting Environment Variables" on page 4-3 for more information.

6. Increase the memory setting for the Java Virtual Machine—see "Setting the Memory Size" on page 4-3 for more information.

7. Obtain the cell and node name of the WebSphere instance where you plan to install Oracle Identity Manager—see "Obtaining the WebSphere Cell and Node Name" on page 4-4 for more information.

8. Install Oracle Identity Manager—see "Installing Oracle Identity Manager with WebSphere" on page 4-4 for more information.

Installing the WebSphere Application Server

Install the 5.1.1.5 version of WebSphere using the full (default) installation option.If you select instead a custom installation of WebSphere, heed the following points:

• Make sure that the path you specify for the application server location ends with AppServer (For example on Windows, a valid path might be: C:\IBM\WebSphere\AppServer).

• Make sure that the following WebSphere components are installed during the WebSphere installation:

  • Admin scripting

  • Ant utilities

  • Assembly and deployment tools

  • Embedded Messaging Server and client

• The default WebSphere installation uses the application server name server1. However, you can use any server name for your Oracle Identity Manager installation. See "Configuring WebSphere on a Nondefault Server" for detailed information on configuring WebSphere to use a nondefault server name.

Installing the WebSphere Application Client

The WebSphere Application Client is required to run the Oracle Identity Manager Design Console. Install the WebSphere Application Client 5.1 with the typical (default) installation. Consult your WebSphere documentation for detailed installation procedures.

Enabling SOAP Communication with WebSphere

The Oracle Identity Manager installer communicates with WebSphere as a SOAP client (using JACL commands to create data sources, setup message queues, and perform other operations).

1. To enable SOAP, edit the following properties in the file soap.client.props, which resides in the directory <WEBSPHERE_HOME>\AppServer\properties\. The lines you edit should look like this:

   com.ibm.SOAP.securityEnabled=true
   com.ibm.SOAP.loginUserid=xelsysadm
   com.ibm.SOAP.loginPassword=xelsysadm
   
   

2. Save and close the file.

   
   

   Note: If you used a user ID or password other than xelsysadm for WebSphere, enter those here.

   
   

Obtaining the Bootstrap Port

During WebSphere Application Client installation, you are prompted for the WebSphere Server hostname and port. The port is the WebSphere bootstrap port. You also must provide this port number during Design Console installation. Obtain the bootstrap port number using the WebSphere administrative console.

Note: The WebSphere application server must be running to obtain the bootstrap port number.

To get the bootstrap port number on a non-clustered (singleton) installation:

1. Log in to the WebSphere administrative console.

2. Select System Administration, select <Server1 Name>, select End Points, then select Bootstrap Address. The bootstrap port is displayed.

To get the bootstrap port number on a clustered installation:

1. Log in to the WebSphere administrative console.

2. Select System Administration, select Deployment Manager, select End Points, then select Bootstrap Address. The bootstrap port is displayed.

Note: If you are using a clustered WebSphere environment, manually edit the Oracle Identity Manager Design Console configuration file and provide a list of all the bootstrap ports in the cluster. See "Installing Oracle Identity Manager Cluster using a Shared Directory" for more information.

Upgrading the WebSphere Server and Client

Both the WebSphere server and the client must be updated with the latest fix packs from IBM. Perform these upgrades in the following order:

1. Upgrade your WebSphere server as follows:

   1. from 5.1 to 5.1.1

   2. from 5.1.1 to 5.1.1.5

2. Upgrade your WebSphere client as follows:

   1. from 5.1 to 5.1.1

   2. from 5.1.1 to 5.1.1.5

Setting Environment Variables

Setting environment variables involves:

• Be sure the JAVA_HOME system variable is set to the appropriate JDK.

• Remove the ANT_HOME system variable if that variable is defined.

• Ensure that the IBM JVM bundled with WebSphere server is being used when a Java command is executed. To do this, include the WebSphere server directory java/jre/bin in the PATH ahead of all other path entries, for example:

  set PATH=<WEBSPHERE_HOME>\java\jre\bin;%PATH%
  
  

Setting the Memory Size

Use the following steps to set the memory size. The WebSphere application server must be running to set the memory size.

1. Connect to the WebSphere administrative console using the following URL: http://<WebSphere Host>:<WebSphere Admin Port>/admin

2. Select Servers>Application Servers.

3. Select the server name.

4. On the Configuration tab, scroll to the Additional Properties section.

5. Select Process Definition.

6. On the Configuration tab, scroll to the Additional Properties section.

7. Click Java Virtual Machine.

8. In the General Properties list, change the value for Maximum Heap Size to 1024 MB.

9. Select OK.

10. Select Save to commit the setting.

Obtaining the WebSphere Cell and Node Name

After installing and initially configuring WebSphere, use the following steps to obtain the cell and node name of the WebSphere instance where you plan to install Oracle Identity Manager. The Oracle Identity Manager installer will prompt you for this information during installation:

1. Connect to the WebSphere administrative console using the following URL:

   http://<WebSphere Host>:<WebSphere Admin Port>/admin
   
   

2. Click Servers on the left pane.

3. Click Application Servers under Servers.

4. Click the server instance (server1, default) on the right pane.

5. Click the Runtime tab.

6. Note the values for Cell Name and Node Name.

   
   

   Note: If the value of State is not Started, then restart the server instance.

   
   

Installing Oracle Identity Manager with WebSphere

The Oracle Identity Manager installer needs to communicate with your WebSphere server during installation, therefore you must verify that the application server is running before you start installation.To start WebSphere on Windows, use the Windows Start Menu, or the startServer.bat script located in the <WEBSPHERE_HOME>\AppServer\bin\ directory. For example, run:<WEBSPHERE_HOME>\AppServer\bin\startServer.bat <server name>To start WebSphere on UNIX, use the startServer.sh script located in the <WEBSPHERE_HOME>/AppServer/bin/ directory. For example, run:<WEBSPHERE_HOME>/AppServer/bin/startServer.sh <server name>To install Oracle Identity Manager, follow the installation instructions in the chapter specific to your operating system. See "Installing Oracle Identity Manager Server on Windows" or "Installing Oracle Identity Manager Server on UNIX" for more information.