3 Installing and Configuring WebSphere for Oracle Identity Manager

This chapter explains how to set up WebSphere before and after installing Oracle Identity Manager.

This chapter discusses the following topics:

• Overview of WebSphere Installation and Configuration

• Installing the WebSphere Application Server

• Installing the WebSphere Application Client

• Enabling SOAP Communication with WebSphere

• Obtaining the Bootstrap Port

• Upgrading the WebSphere Server and Client

• Setting Environment Variables

• Setting the Memory Size

• Obtaining the WebSphere Cell and Node Name

• Preparing to Install Oracle Identity Manager as a Non-Root User on UNIX or Linux

• Starting WebSphere Before Installing Oracle Identity Manager

Note:

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

Overview of WebSphere Installation and Configuration

The following are high-level pre- and post-installation tasks. You must perform all of these tasks.

Task overview: WebSphere installation and configuration:

1. Install the WebSphere Application Server.

   See "Installing the WebSphere Application Server" on page 3-2 for more information.

2. Install WebSphere Application Client.

   See "Installing the WebSphere Application Client" on page 3-2 for more information.

3. Enable SOAP Communication to WebSphere.

   See "Enabling SOAP Communication with WebSphere" on page 3-3 for more information.

4. Upgrade WebSphere server and client software.

   See "Upgrading the WebSphere Server and Client" on page 3-4 for more information.

5. Prepare the environment.

   See "Setting Environment Variables" on page 3-4 for more information.

6. Increase the memory setting for the Java Virtual Machine.

   See "Setting the Memory Size" on page 3-5 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 3-5 for more information.

8. Install Oracle Identity Manager.

   See "Starting WebSphere Before Installing Oracle Identity Manager" on page 3-6 for more information.

Installing the WebSphere Application Server

Install WebSphere using the full (default) installation option.If you select instead a custom installation of WebSphere, pay attention to the following:

• Make sure that the path you specify for the application server location ends with AppServer. For example on Windows, a valid path might be the following:

  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

• By default, the WebSphere installation uses the application server named server1.

  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, set up message queues, and perform other operations.

To enable SOAP communication with WebSphere:

1. Open the following file in a text editor:

   <WEBSPHERE_HOME>\properties\soap.client.props

   Edit the property lines as follows:

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

   Note:

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

2. Save and close the file.

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 must also 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 view the bootstrap port number on a non-clustered (singleton) installation:

1. Log in to the WebSphere administrative console.

2. Select Servers, then select Application Servers, then select <SERVER_NAME>, then select End Points, and then select Bootstrap Address.

   The bootstrap port is displayed.

To view the bootstrap port number on a clustered installation:

1. Log in to the WebSphere administrative console.

2. Select Servers, then select Application Servers, then select <Model_Node_Server_Name>, then select End Points, and 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

   3. from 5.1.1.5 to 5.1.1.12

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

   3. from 5.1.1.5 to 5.1.1.12

Setting Environment Variables

Setting environment variables involves the following:

• Ensure that the JAVA_HOME system variable is set to the appropriate JDK. On Microsoft Windows, Solaris, and Linux, set JAVA_HOME to Sun JDK. On AIX, set JAVA_HOME to the IBM JDK (bundled with IBM WebSphere).

  See Also:

  Oracle Identity Manager Release Notes for Release 9.0.3.1 for information about certified JDK versions

• Remove the ANT_HOME system variable if it is defined.

• For Microsoft Windows, Solaris, and Linux, ensure that the Sun JDK is being used when a Java command is run. To do this, include the /java/jre/bin/ directory of the Sun JDK installation in the PATH ahead of all other path entries. For example:

  Microsoft Windows

  set PATH=<SUN_JDK_HOME>\jre\bin;%PATH%
  
  

  Solaris or Linux

  export PATH=<SUN_JDK_HOME>/jre/bin:$PATH
  
  

• For AIX, ensure that the IBM JDK (bundled with IBM WebSphere) is being used when a Java command is run. To do this, include the /java/jre/bin/ directory of IBM JDK installation in the PATH ahead of all other path entries. For example:

  export PATH=<IBM_JDK_HOME>/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.

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, then 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 procedure 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.

To obtain the cell and node name:

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

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

2. Click Servers on the left section.

3. Click Application Servers under Servers.

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

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.

Preparing to Install Oracle Identity Manager as a Non-Root User on UNIX or Linux

Installing Oracle Identity Manager as a non-root user on a WebSphere application server running on UNIX or Linux requires certain permissions. Before attempting to install Oracle Identity Manager as a non-root user on a WebSphere application server running on UNIX or Linux, verify the operating system user account installing Oracle Identity Manager has write and execute permissions on the directories where WebSphere will be installed, including <WEBSPHERE_HOME> and <NDM_HOME>.

Starting WebSphere Before Installing Oracle Identity Manager

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 <WEBSPHERE_HOME>\bin\startServer.bat script. For example, run:

<WEBSPHERE_HOME>\bin\startServer.bat <server name>

To start WebSphere on UNIX or Linux, use the <WEBSPHERE_HOME>/bin/startServer.sh script. For example, run:

<WEBSPHERE_HOME>/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 or Linux" for more information.