| Oracle® Identity Manager Installation and Configuration Guide for BEA WebLogic Server Release 9.1.0 Part Number E10370-03 |
|
|
View PDF |
| Oracle® Identity Manager Installation and Configuration Guide for BEA WebLogic Server Release 9.1.0 Part Number E10370-03 |
|
|
View PDF |
This chapter explains how to deploy Oracle Identity Manager in a clustered BEA WebLogic Server environment.
This chapter discusses the following topics:
Installing and Configuring a Database for Oracle Identity Manager
Setting Up a BEA WebLogic Server Oracle Identity Manager Cluster
A clustered installation requires multiple host computers. The instructions in this chapter involve a deployment of 3+n computers. Your configuration can vary.
Table 9-1 describes the entities needed for a cluster, the computers that the entities run on, and the software required for the entities. Host computers and entities are labeled.
Table 9-1 WebLogic-Based Oracle Identity Manager Cluster Host Computers
| Host Computers | Entities | Software | Description |
|---|---|---|---|
|
ADMIN_SERVER_HOST |
Administrative Server |
BEA WebLogic Server |
The Administrative Server is the BEA WebLogic Server instance that configures and manages the BEA WebLogic Server instances in its domain. |
|
XLMANAGED_SERVER_HOST_n |
xlManagedServer_n node manager |
BEA WebLogic Server Oracle Identity Manager |
Managed servers are BEA WebLogic Server instances that are the cluster members. Members are controlled by the Administrative Server. Each application server in the cluster runs Oracle Identity Manager. The Managed Servers run on one or more host computers. Replace n with the node number, such as xlManagedServer_1. You can have more than one application server for each host computer. |
|
Not applicable |
xlCluster |
This is the name of the BEA WebLogic Server cluster for Oracle Identity Manager. |
|
|
IIS_HOST |
IIS server |
IIS BEA WebLogic Server IIS plug-in |
The IIS Web server acts as the front end to the BEA WebLogic Server cluster and handles load balancing. |
Caution:
Deploying an application in a clustered installation is a complex procedure. This document assumes that you have expertise in installing and running applications on a BEA WebLogic Server cluster. These instructions only provide details specific to Oracle Identity Manager. They are not complete instructions for setting up a BEA WebLogic Server cluster. For more information about clustering, refer to BEA WebLogic Server documentation.Refer to Chapter 4, "Installing and Configuring a Database for Oracle Identity Manager" for information.
The basic procedure for deploying Oracle Identity Manager in a BEA WebLogic Server cluster is to install and configure an Administrative Server and a single Managed Server, and then clone the Managed Server for the other cluster members.
Note:
This chapter assumes that you are running a dedicated Administrative Server host on which Oracle Identity Manager is not running.To set up a BEA WebLogic Server Oracle Identity Manager cluster:
Install BEA WebLogic Server on ADMIN_SERVER_HOST.
Install BEA WebLogic Server on all managed hosts (XLMANAGED_SERVER_HOST_1...n).
Configure the XLMANAGED_SERVER_HOST_1 to listen to the Administrative Server.
Refer to the "Configuring a Node Manager for a Managed Server" section for more information.
Create a BEA WebLogic Server configuration.
Refer to the"Creating a BEA WebLogic Server Configuration" section for more information.
Configure the Remote Start options for xlManagedServer_1 and start the cluster.
Refer to the "Configuring Remote Start Options" section for more information.
Install Oracle Identity Manager on the ADMIN_SERVER_HOST.
Refer to the "Installing Oracle Identity Manager" section for more information.
Configure BEA WebLogic Server.
Refer to the "Configuring BEA WebLogic Server After Installing Oracle Identity Manager" section for more information.
Add new servers to your cluster.
Refer to the "Adding New Servers to the BEA WebLogic Server Cluster" section for more information.
(Optional) Configure the IIS Proxy Plug-ins.
Refer to the "Configuring the Microsoft IIS Proxy Plug-in" section for more information.
(Optional) Configure database-based HTTP session failover.
Refer to the "Configuring Database-Based HTTP Session Failover" section for more information.
Install BEA WebLogic Server on the Administrative Server and XLMANAGED_SERVER_HOST_1 and any other XLMANAGED_SERVER_HOST_n computers. Configure the Node Manager on all MANAGED_SERVER_HOST computers so that they can be controlled by the Administrative Server. Refer to the "Configuring a Node Manager for a Managed Server" section for more information about configuring the Node Manager.
To control your Managed Servers remotely from the Administrative Server, you must set up and configure Node Manager on each of the remote systems hosting Managed Servers by following the instructions on the BEA e-docs page:
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html
On each remote computer, on which BEA WebLogic Server is installed and Managed Servers are configured, edit the nodemanager.hosts file and specify the IP address/DNS Name (set ReverseDnsEnabled=true in the nodemanager.properties file to use DNS name) of the Administrative Server host.
Note:
After installing BEA WebLogic Server, you must start (or restart) the Node Manager to generate the initial
nodemanager.hosts file.The default location of the nodemanager.hosts and nodemanager.properties files is:
For Microsoft Windows:
BEA_HOME\weblogic81\common\nodemanager
For UNIX:
BEA_HOME/weblogic81/common/nodemanager
Before installing Oracle Identity Manager, you must prepare your Administrative Server host (ADMIN_SERVER_HOST). Use the WebLogic Configuration Wizard to create a configuration. The configuration includes a domain for Oracle Identity Manager, a cluster, and settings for the Managed Server (xlManagedServer_1) and its host computer (XLMANAGED_SERVER_HOST_1).
To create a BEA WebLogic Server Oracle Identity Manager cluster configuration, install BEA WebLogic Server on ADMIN_SERVER_HOST and create (or edit) a BEA WebLogic Server configuration by using the WebLogic Configuration Wizard.
The following steps are an overview of the process for creating a BEA WebLogic Server cluster configuration for installing Oracle Identity Manager:
Create or use an existing domain to host the Oracle Identity Manager application.
Add a Managed Server entry (xlManagedServer_1).
Create a cluster (xlCluster).
Add xlManagedServer_1 to the cluster.
Add a host entry for your Managed Server (XLMANAGED_SERVER_HOST_1).
Assign xlManagedServer_1 to XLMANAGED_SERVER_HOST_1.
Create the BEA WebLogic Server administrator account.
Create the Internal user and the User group.
Add the Internal user to the User group.
Set start up mode and choose the SDK.
Save your configuration.
To create a BEA WebLogic Server cluster configuration for installing Oracle Identity Manager:
Start the WebLogic Configuration Wizard:
Microsoft Windows:
Click Start, select Programs, BEA WebLogic Platform, and then select Configuration Wizard.
UNIX:
Run the BEA_HOME/weblogic81/common/bin/config.sh script.
In the Create or Extend a Configuration page, create a new configuration:
Select Create a new WebLogic configuration.
Click Next.
In the Select a Configuration Template page, select the basic template:
Select the Basic WebLogic Server Domain template.
Click Next.
In the Choose Express or Custom Configuration page, select a custom configuration:
Click the Custom option to create a custom configuration.
Click Next.
In the Configure the Administration Server page, enter the Administrative Server information:
Enter a name for the Administrative server (such as AdminServer).
Accept the defaults settings for the other fields.
Click Next.
In the Managed Servers, Clusters, and Machine Options page, set up your cluster:
Select Yes to create the cluster.
Click Next.
In the Configure Managed Servers page, configure your Managed Server:
Click Add to create a Managed Server entry.
Select the IP address from the Listen Address list.
Enter the listening port, for example, 7051.
Accept the default values for all other fields.
Click Next.
Click Next on the Choose SIP Server Type page without selecting any option.
Click Next again on the Configure SIP Data-Tier Managed Server Partition page.
In the Configure Cluster page, configure your cluster:
Click Add to create a cluster entry.
Specify a name for the cluster (such as xlCluster).
Provide a unique multicast address and port number.
At this time, the Cluster Address is not required.
Click Next.
In the Assign Servers to Cluster page, assign the Managed Server to your cluster:
Highlight the Managed Server name from the Server section.
Use the right arrow to assign it to the cluster.
Click Next.
In the Configure Machines page, configure your Managed Server host computer:
For a Windows host:
Click the Machine tab.
Click Add.
Enter the name of the Managed Server host, such as XLMANAGED_SERVER_HOST_1.
Enter the Node Manager listen address.
Accept the default value of 5555 for the listening port.
Click Next.
For a UNIX host:
Click the UNIX or Linux Machine tab.
The Configure Machines page UNIX or Linux machine tab is displayed.
Click Add.
Enter the name of the Managed Server host, such as XLMANAGED_SERVER_HOST_1.
Select the option for GID binding, if you want to enable GID binding.
Enter the GID to bind as.
Select the option for UID binding, if you want to enable UID binding.
Enter the UID to bind as.
Enter the host address.
Enter the listen port.
Click Next.
In the Assign Servers to Machines page, assign the Managed Server to the Managed Server host computer:
Select the Managed Server.
Select the host computer.
Click the right-arrow button to assign the server to the host computer.
Click Next.
In the Database (JDBC) Options page, the JDBC component is defined by the Oracle Identity Manager Installer. Do not define your JDBC component:
Click No.
Click Next.
In the Messaging (JMS) Options page, the JMS component is defined by the Oracle Identity Manager Installer. Do not define your JMS component:
Click No.
Click Next.
In the Configure Administrative Username and Password page, enter your administrator information:
The default user name is weblogic. Use this name, or enter another name.
Enter a password and confirm it.
Enter a description for the user. (Optional)
Select Yes to create an additional user and group that are required by Oracle Identity Manager so that the Internal user can be created for Oracle Identity Manager.
Click Next.
In the Configure Users and Groups page, configure the user and group information:
Click Add to create a new user.
Enter Internal for the user name.
Note:
The Internal user name is case-sensitive.Enter a password and confirm it.
Enter a description for this user.
Click the Group tab.
The Configure Users and Groups page displays the Group list. Enter the group information:
Click Add to create a user group.
Enter User for the group name.
Note:
The User group name is case-sensitive.Enter a description for the group.
Click Next.
In the Assign Users Groups page, assign the Internal user to the User group:
Select the User group from the Group list on the right side of the page.
Select Internal user in the User list.
Click Next.
In the Assign Groups to Groups page, it is not necessary to assign groups to other groups. To continue, click Next.
In the Assign Users and Groups to Global Roles page, it is not necessary to assign users or groups a global role. To continue, click Next.
If you are running the wizard on a Windows computer, then the Configure Windows Options page is displayed. Otherwise, The Configure Server Start Mode and Java SDK page is displayed. In this case, skip this step and continue with Step 21.
Configure the Microsoft Windows Options.
You can choose to create a start menu shortcut for the Administrative Server, and to run the Administrative Server as a Windows service.
Click the Yes or No options to indicate your preferences.
Click Next.
Note:
If you add a shortcut to the Start menu, then the Build Start Menu Entries page is displayed. Select or decline the options, and then click Next.In the Configure Server Start Mode and Java SDK page, select the server start mode and the Java SDK.
Select the desired mode for BEA WebLogic Server.
Select the Sun SDK or JRockit SDK.
Click Next.
In the Create WebLogic Configuration page, select the configuration directory:
Enter the name of the domain in the Configuration Name field.
If required, change the configuration location.
Review other configuration details. If desired, go back to make any changes.
Click Create.
In the Creating Configuration page, complete your configuration and start the Administrative Server.
On Microsoft Windows, select Start Admin Server and then click Done.
The wizard exits and the server starts and prompts you for the BEA WebLogic Server user name and password. Enter weblogic for the user name and weblogic for the password if you accepted the default values for user name and password when you created the WebLogic domain. If you created a unique user name and password when you created the WebLogic domain, enter those values.
On UNIX, enter the following commands:
cd BEA_HOME/user_projects/domains/domain_name sh startWebLogic.sh
The Administrative Server starts.
To allow the Managed Servers to be controlled remotely by the administration console, set the server classpath and the memory parameters. Use the WebLogic Server Administration Console to configure the server.When you clone the Managed Server (to add members to your cluster), these settings are copied to the clone. If you install BEA WebLogic Server in another directory on the new host computer, you must manually edit the remote start settings for the new Managed Server.To configure the server remote start options:
Open the WebLogic Server Administration Console by navigating to the following URL:
http://localhost:7001/console
Click the server name, for example xlManagedServer_1, under domain name/Servers.
Click the Remote Start tab, and then:
In the Java Home field, enter the path of the Sun SDK or JRockit SDK directory, for example, C:\bea\jdk142_15.
Set the BEA Home field. For example, if BEA WebLogic Server is installed on the C drive, you set the BEA Home field to C:\bea\.
Increase the memory by appending the following to the Arguments field:
For Sun SDK:
-Xms1280m -Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m
For JRockit SDK:
-Xms1280m -Xmx1280m -XnoOpt
For deployment on Microsoft Windows, locate the Class Path field and add the path to weblogic.jar. If you are using SQL Server as the database, then you must also add the mssqlserver.jar, msbase.jar, and msutil.jar Microsoft JDBC files to the Class Path field. For example:
Note:
Microsoft SQL Server is not supported in Oracle Identity Manager release 9.1.0. See ÒCertified ComponentsÓ in Oracle Identity Manager Release Notes for information about certified components.BEA_HOME\weblogic81\server\lib\weblogic.jar;C:\sqljars\msbase.jar;C:\sqljars\msutil.jar;C:\sqljars\mssqlserver.jar;
Note:
Ensure that you perform this step on all Managed Servers.Click Apply to save the setting on the Remote Start tab.
Ensure that the Node Manager is running on the remote host, for example XLMANAGED_SERVER_HOST_1. If the Node Manager is not running, start it by running the BEA_HOME\weblogic81\server\bin\startNodeManager script.
Start the server from the administration console by performing the following steps:
Click <domain>, select Clusters, select xlCluster, then select <xlManagedServer_n> in the navigation bar on the left side of the page.
Select the Control tab in the main pane.
To start the server, click Start this server.
Note:
If you have a problem starting the server because of Host Name validation, then go to server for both Admin and Managed servers, select Key Stores & SSL under the Configuration tab, change Hostname Verification to None under the Advanced Options, and restart the server.The server starts, and its state changes from UNKNOWN to RUNNING.
Install Oracle Identity Manager on ADMIN_SERVER_HOST. See either Chapter 5, "Installing Oracle Identity Manager on Microsoft Windows" or Chapter 6, "Installing Oracle Identity Manager on UNIX" for more information.
After you have installed Oracle Identity Manager, you must further configure BEA WebLogic Server. Some of the configuration is cluster-specific, and some is the same as you would do for any Oracle Identity Manager system.To perform postinstallation configuration of BEA WebLogic Server:
Stop the Managed Server and Administrative Server. For detailed information about this procedure, refer to Chapter 8, "Starting and Stopping Oracle Identity Manager".
Restart the Administrative Server by using the xlStartServer.bat script for Windows, or the xlStartServer.sh script for UNIX. Refer to Chapter 8, "Starting and Stopping Oracle Identity Manager" for more information about starting the Administrative Server.
Complete the tasks described in "Required Postinstallation Tasks".
Copy the Oracle Identity Manager directory from ADMIN_SERVER_HOST to XLMANAGED_SERVER_HOST_1 by maintaining the identical directory hierarchy structure.
Note:
If the XLMANAGED_SERVER_HOST_1 is located on the same computer as ADMIN_SERVER_HOST, then you do not need to copy the Oracle Identity Manager directory.Each server in the cluster must know the location of the others. Refer to the "Specifying Cluster Members" section for more information.
If XLMANAGED_SERVER_HOST_1 is a different computer than ADMIN_SERVER_HOST, then copy the following Oracle Identity Manager files to the BEA WebLogic Server installation directory on the XLMANAGED_SERVER_HOST_1:
Copy OIM_HOME\ext\nexaweb-common.jar to the BEA_HOME\weblogic81\server\lib\ directory.
Copy OIM_HOME\xellerate\lib\wlXLSecurityProviders.jar to the BEA_HOME\weblogic81\server\lib\mbeantypes\ directory.
Start the cluster.
After you have set up your cluster, you can add more servers by cloning the first Managed Server (xlManagedServer1).
Note:
If you install BEA WebLogic Server in a different location on a new Managed Server host, then additional configuration is necessary.To add a server to your cluster:
Install BEA WebLogic Server on XLMANAGED_SERVER_HOST_n.
Refer to the "Installing BEA WebLogic Server" section for more information.
Note:
To control the server remotely, you must edit the nodemanager.hosts file.Configure the Node Manager for xlManagedServer_n.
Refer to the "Configuring a Node Manager for a Managed Server" section and the "Creating a BEA WebLogic Server Configuration"section for more information.
Set up Oracle Identity Manager on XLMANAGED_SERVER_HOST_n.
Refer to the "Installing Oracle Identity Manager on New Hosts" section for more information.
Configure the XLMANAGED_SERVER_HOST_n computer.
Refer to the "Configuring New Host Computers" section for more information.
Add the new host computer to the list of cluster members.
Refer to the "Specifying Cluster Members" section for more information.
Configure new JMS servers corresponding to the new cluster member Managed Servers.
Refer to the "Creating JMS Entries for New Cluster Members" section for more information.
To install Oracle Identity Manager on a new host in the BEA WebLogic Server cluster:
Ensure that the name and path of the JAVA_HOME directory used by Oracle Identity Manager is the same across all the nodes of the cluster.
Copy the OIM_HOME directory, in which Oracle Identity Manager is installed in the cluster, to the new host, by maintaining the identical directory hierarchy structure.
Copy the wlXLSecurityProviders.jar file from OIM_HOME\xellerate\lib directory into the BEA_HOME\weblogic81\server\lib\mbeantypes\ directory.
Copy the OIM_HOME\xellerate\ext\nexaweb-common.jar file to the BEA_HOME\weblogic81\server\lib\ directory.
To configure a new host to the BEA WebLogic Server cluster, you must create an entry for the host, clone the server, then set up a JMS server.To add a new host to the BEA WebLogic Server cluster:
Open the WebLogic Server Administration Console by navigating to the following URL:
http://localhost:7001/console
Click <domain_name>.
Click Machines on the directory tree in the left pane.
Click Configure a new Machine.
Enter a name for this computer, for example, XLMANAGED_SERVER_HOST_2.
Click Create.
Click the Node Manager tab.
Enter the listen address (IP address) for this computer.
Accept the default for the listen port.
Ensure that Debug Enabled is selected.
Click Apply.
Right-click the existing manager server name, for example, xlManagedServer_1, and select Clone <server_name> from the shortcut menu.
Enter a name for the new server, for example, xlManagedServer_2.
Select the host computer from the Machine menu, for example, XLMANAGED_SERVER_HOST_2.
Ensure that the cluster, for example, xlCluster, is selected in the Cluster menu.
Enter the listen address in the Listen Address field.
Enter the listen port in the Listen Port field.
Scroll down and click Clone.
If BEA WebLogic Server is installed in a different directory than xlManagedServer_1, then change the remote start configuration to include the directory location.
Navigate to the host computer and start the node manager.
To create JMS entries for new cluster members:
On the Administration Server host, run the setup_wl_server script to configure a new JMS server corresponding to the new Managed Server, and configure the distributed queue.
To run the setup_wl_server script:
Navigate to the OIM_HOME/xellerate/setup directory.
Run setup_wl_server.cmd for Microsoft Windows and setup_wl_server.sh for UNIX by appending the following parameters:
BEA_HOME ADMIN_SERVER_HOST ADMIN_SERVER_HOST_port WEBLOGIC_admin_login WEBLOGIC_admin_password XLMANAGED_SERVER_n
Run the following scripts depending on the operating system of the computer hosting Oracle Identity Manager.
Microsoft Windows:
setup_wl_server.cmd c:\bea\weblogic81 t3://192.168.50.172 8001 wladmin wladmin XLMANAGED_SERVER_2
UNIX:
./setup_wl_server.sh /opt/bea/weblogic81 t3://192.168.50.172 8001 wladmin wladmin XLMANAGED_SERVER_2
Configure the settings for the newly added JMS server. Refer to the "WebLogic JMS Server Configuration Changes" section for detailed information about this procedure.
Stop all Managed Servers gracefully by using the Admin Console and then gracefully stop the Administrative Server.
Start the Administrative Server by running the OIM_HOME\xellerate\bin\xlStartServer script.
To specify the location of all the cluster members, perform the following steps:
Edit the OIM_HOME\xellerate\config\xlconfig.xml file on each node in the cluster. Modify the Discovery section to specify the cluster members. You can accomplish this one of the following two ways:
Specify the cluster address that resolves to multiple computers instead of specifying individual members. This enables you to update the DNS server when adding new members rather than editing the xlconfig.xml file for each Oracle Identity Manager component.
If you follow this method, then the port number must be the same on all of the computers.
In the xlconfig.xml file on each server in the cluster, specify all the URLs (including port) for all servers in the cluster.
If you use this approach, then the xlconfig.xml file must be updated each time a server is added to the cluster. You must do this for every Oracle Identity Manager component (server or Design Console) in the cluster.
In the Discovery section of the xlconfig.xml file, add the list of all servers to each of the four occurrences of the <java.naming.provider.url> property, for example:
Note:
JBoss Application Server clustered environments are not supported in Oracle Identity Manager release 9.1.0. See ÒCertified ComponentsÓ in Oracle Identity Manager Release Notes for information about certified components.<Discovery><CoreServer><java.naming.provider.url>t3://192.168.50.28:7051,192.168.50.184:7051</java.naming.provider.url><java.naming.factory.initial>weblogic.jndi.WLInitialContextFactory</java.naming.factory.initial></CoreServer><BackOffice><java.naming.provider.url>t3://192.168.50.28:7051,192.168.50.184:7051</java.naming.provider.url><java.naming.factory.initial>weblogic.jndi.WLInitialContextFactory</java.naming.factory.initial></BackOffice><Scheduler><java.naming.provider.url>t3://192.168.50.28:7051,192.168.50.184:7051</java.naming.provider.url><java.naming.factory.initial>weblogic.jndi.WLInitialContextFactory</java.naming.factory.initial></Scheduler><!-- For JBoss use ConnectionFactory (non-clustered and HAILXAConnectionFactory (Clustered) --><JMSServer><connectionFactory>xlConnectionFactory</connectionFactory><java.naming.provider.url>t3://192.168.50.28:7051,192.168.50.184:7051</java.naming.provider.url><java.naming.factory.initial>weblogic.jndi.WLInitialContextFactory</java.naming.factory.initial></JMSServer></Discovery>
Start all cluster members by using the Admin Console.
To configure the Microsoft IIS proxy plug-in:
To enable the Web clients to fail over, place the load balancer before the BEA WebLogic Server cluster, and configure it for session affinity. Alternatively, you can configure a BEA WebLogic Server proxy plug-in into the application server.
To configure the IIS proxy plug-in, use the iisproxy.dll and iisforward.dll extension and filters.
Follow the BEA WebLogic Server documentation to perform this activity:
Use the documentation at the following URL:
http://e-docs.bea.com/wls/docs81/plugins/isapi.html#113486
You will be using Request Forwarding based on a context name xlWebApp and Nexaweb, while deploying the whole application.
The following is a sample iisproxy.ini file.
WlForwardPath=/xlWebApp*,/NexaWeb* Debug=ON WebLogicCluster=192.168.50.28:7051,192.168.50.184:7051
Oracle Identity Manager on BEA WebLogic Server cluster is by default configured to provide memory-to-memory session replication and failover. However, it is possible to use database-based replication.To enable database-based replication:
Edit the profile weblogic.profile in OIM_HOME/Profiles on the application server host, and change the replication mechanism from InMemory to Database.
To patch the application, run the patch_weblogic script found in the OIM_HOME\xellerate\setup directory.
Note:
The database tables required for holding the sessions must be created manually. Refer to BEA documentation for information about creating these tables.It is possible to use other types of failover mechanisms in BEA WebLogic Server. To use them, change the deployment descriptor (weblogic.xml) in the OIM_HOME/DDTemplates/xlWebApp directory, then insert the proper settings for the Web application descriptor. After the change, run the patch_weblogic script to fix the existing application.
Note:
If the deployment descriptor is changed (for example, during an upgrade), then you must perform the same changes again on the deployment descriptor.