Oracle® Role Manager Integration Guide Release 10g (10.1.4) Part Number E12030-05 |
|
|
View PDF |
This chapter contains procedures for configuring the JBoss application servers for Oracle Identity Manager (Identity Manager) and Oracle Role Manager (Role Manager) in preparation for deployment of the Oracle Role Manager Integration Library (Integration Library).
This chapter includes the following sections:
The Role Manager Integration Library is intended to be deployed on the application server on which Identity Manager is deployed. The procedures in this chapter assume the following:
You have the access to the files installed in ORMINT_HOME.
You have the appropriate permission to add and modify files in the application server where Identity Manager is deployed.
You have the appropriate permission to stop and start the application server where Identity Manager is deployed.
To configure the Role Manager server:
On the Role Manager application server host, copy the following file into the deploy directory of the application server for Role Manager (for example, C:\jboss-4.2.3\server\default\deploy):
ORMINT_HOME/samples/jboss/ormoim-service.xml
Edit the settings in the ormoim-service.xml file for your environment.
This file contains sample configuration for the JMS queues required to support the Integration Library.
The settings in this file may have to be modified to reflect your deployment environment, including the JNDI location of Identity Manager, for example, to change the message bean properties java.naming.provider.url attribute.
For example, if the Identity Manager application server is run on a host named Server_OIM, and the jnp bind address is 1099 as specified in the jboss-service.xml file where it is deployed, then the values for java.naming.provider.url should be:
jnp://Server_OIM:1099/queue
To configure the Identity Manager server:
On the Identity Manager application server host, copy the following files into the deploy
directory of the application server for Identity Manager (for example, C:\jboss4.2.3\server\default\deploy):
ORMINT_HOME/samples/jboss/oimorm-service.xml ORMINT_HOME/lib/server_api_14.jar
Edit the settings in the oimorm-service.xml file for your environment.
This file contains sample configuration for the JMS queues required to support the Integration Library.
The settings in this file may have to be modified to reflect your deployment environment, including the JNDI location of Role Manager, for example, to change the message bean properties java.naming.provider.url attribute.
For example, if the Role Manager application server is run on a host named Server_ORM, and the jnp bind address is 1099 as specified in the jboss-service.xml file where it is deployed, then the values for java.naming.provider.url should be:
jnp://Server_ORM:1099/queue jnp://Server_ORM:1099/ejb/orm
Copy the following two files into JBOSS_HOME/server/default/lib:
ORMINT_HOME/lib/orm_encryption.jar ORMINT_HOME/oimlib/OIM-IntegrationTransport.jar
Before you can start using the Role Manager Integration library, the Identity Manager startup command must include the path to the Integration Library software. Making this change before the Integration Library software is deployed does not affect the operation of Identity Manager until it is restarted.
To modify how Identity Manager is invoked for the Integration Library:
Open the following file for editing:
For UNIX-based systems:
$ $OIM_HOME/xellerate/bin/xlStartServer.sh
For Windows systems:
OIM_HOME\xellerate\bin\xlStartServer.bat
Add the following argument to the Identity Manager startup command:
-DORMINT_ROOT_DIR=ORMINT_HOME
where ORMINT_HOME is the full path to the home directory of the Role Manager Integration Library.
For example, on Windows, it might be similar to:
C:\jboss4.2.3\bin\run.bat -DXL.HomeDir=C:\OIM\xellerate -Djava.awt.headless=true -DORMINT_ROOT_DIR=C:\ORMINT_HOME
Save and close the start script.
For these changes to go into effect, restart the Identity Manager server.