Extending the Domain with Oracle Identity Manager 14-7
The cluster_soa has the managed servers WLS_SOA1 and WLS_SOA2 as members.
Click Next.
13.
On the Configure Machines screen, create a machine for each host in the topology.
a. Click the tab UNIX if your hosts use Linux or a UNIX-based operating system.
Otherwise, click Machines. b.
Name : Name of the host. Best practice is to use the DNS name.
c. Node Manager Listen Address
: DNS name of the machine.
d. Node Manager Port
: Port for Node Manager Provide the information shown in the following table.
Leave the default values for all other fields.
Delete the default local machine entry under the Machines tab. Click Next.
14.
On the Assign Servers to Machines screen, indicate which managed servers to run on each of the machines you created.
Click a machine in the right pane. Click the managed servers you want to run on that machine in the left pane.
Click the arrow to assign the managed servers to the machines. Repeat until all managed servers are assigned to machines.
For example:
■
OIMHOST1 : WLS_OIM1 and WLS_SOA1
■
OIMHOST2 : WLS_OIM2 and WLS_SOA2
Click Next to continue. 15.
On the Configure JMS File Stores screen, update the directory locations for the JMS file stores. Provide the information shown in the following table.
Note: Do not make any changes to clusters that already have entries
defined.
Name Node Manager Listen
Address
Node Manager Listen Port
OIMHOST1 OIMHOST1
5556 OIMHOST2
OIMHOST2 5556
Name Directory
UMSJMSFileStore_ auto_1
u01apporacleadminIDMDomainsoa_ clusterjmsUMSJMSFileStore_auto_1
UMSJMSFileStore_ auto_2
u01apporacleadminIDMDomainsoa_ clusterjmsUMSJMSFileStore_auto_2
14-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management
Click Next.
16. On the Configuration Summary screen, click Extend to extend the domain.
17. On the Installation Complete screen, click Done.
18.
Restart WebLogic Administration Server, as described in Section 20.1, Starting
and Stopping Oracle Identity Management Components.
14.4 Configuring Oracle Identity Manager on IDMHOST1
You must configure the Oracle Identity Manager server instances before you can start the Oracle Identity Manager and SOA Managed Servers. The Oracle Identity
Management Configuration Wizard loads the Oracle Identity Manager metadata into the database and configures the instance.
Before proceeding, ensure that the following are true:
■
The Administration Server is up and running.
BPMJMSServer_auto_1 u01apporacleadminIDMDomainsoa_
clusterjmsBPMJMSServer_auto_1
BPMJMSServer_auto_2 u01apporacleadminIDMDomainsoa_
clusterjmsBPMJMSServer_auto_2
SOAJMSFileStore_ auto_1
u01apporacleadminIDMDomainsoa_ clusterjmsSOAJMSFileStore_auto_1
SOAJMSFileStore_ auto_2
u01apporacleadminIDMDomainsoa_ clusterjmsSOAJMSFileStore_auto_2
OIMJMSFileStore_ auto_1
u01apporacleadminIDMDomainoim_ clusterjmsOIMJMSFileStore_auto_1
OIMJMSFileStore_ auto_2
u01apporacleadminIDMDomainoim_ clusterjmsOIMJMSFileStore_auto_2
Notes:
■
Use u01apporacleadminIDMDomainsoa_ clusterjms as the directory location for the
UMSJMSFileStore_auto_1, UMSJMSFileStore_auto_2, BPMJMSServer_auto_1, BPMJMSServer_auto_2,
SOAJMSFileStore_auto_1, and SOAJMSFileStore_auto_2 JMS file stores
■
Use u01apporacleadminIDMDomainoim_ clusterjms as the directory location for the
OIMJMSFileStore_auto_1 and OIMJMSFileStore_auto_2 JMS file stores
■
The locations u01apporacleadminIDMDomainsoa_ clusterjms and
u01apporacleadminIDMDomainoim_clusterjms are on shared storage and must be accessible from OIMHOST1 and
OIMHOST2
Name Directory
Extending the Domain with Oracle Identity Manager 14-9
■
The environment variables DOMAIN_HOME and WL_HOME are not set in the current shell.
The Oracle Identity Management Configuration Wizard is located under the Identity Management Oracle home. Type:
IAM_ORACLE_HOME binconfig.sh
Proceed as follows:
1. On the Welcome screen, click Next
2. On the Components to Configure screen, Select OIM Server.
Click Next. 3.
On the Database screen, provide the following values:
■
Connect String: The connect string for the Oracle Identity Manager database:
oimdb1-vip.mycompany.com:1521:oimedg1oimdb2-vip.mycompany .com:1521:oimedg2oimedg.mycompany.com
If you are using Oracle Database 11.2, replace the vip address and port with the 11.2 SCAN address and port.
■
OIM Schema User Name : edg_oim
■
OIM Schema password : password
■
MDS Schema User Name : edg_mds
■
MDS Schema Password : password
Select Next. 4.
On the WebLogic Administration Server screen, provide the following details for the WebLogic Administration Server:
■
URL : The URL to connect to the WebLogic Administration Server. For
example: t3:OIMHOST1.mycompany.com:14000
■
UserName : weblogic
■
Password : Password for the weblogic user
Click Next. 5.
On the OIM Server screen, provide the following values:
■
OIM Administrator Password : Password for the Oracle Identity Manager
Administrator. This is the password for the xelsysadm user. The password must contain an uppercase letter and a number. Best practice is to use the
same password that you assigned to the user xelsysadm in Section 10.4.4,
Creating Users and Groups for Oracle Identity Manager.
■
Confirm Password : Confirm the password·
■
OIM HTTP URL : Proxy URL for the Oracle Identity Manager Server. This is
the URL for the Hardware load balancer that is front ending the OHS servers for Oracle Identity Manager. For example:
http:oiminternal.mycompany.com:80.
■
Key Store Password : Key store password. The password must have an
uppercase letter and a number.
Click Next. 6.
On the BI Publisher screen, provide the following values:
14-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management
■
Configure BI Publisher : Select if you want to Configure Oracle Identity
Manager with Oracle BI Publisher. This is Optional and depends on your requirements.
■
BI Publisher URL : The URL of BI Publisher, if you selected it.
■
Enable LDAP Sync : Selected.
Click Next. 7.
On the LDAP Server Screen, the information you enter is dependent on your implementation. Provide the following details:
■
Directory Server Type :
– OID, if your Identity Store is in OID.
– OVD if you access your Identity Store through OVD.
■
Directory Server ID : A name for your Oracle Internet Directory server. For
example: IdStore. This is only required if the directory type is OID.
■
Server URL : The LDAP server URL. For example:
ldap:idstore.mycompany.com:389
■
Server User : The user name for connecting to the LDAP Server. For example:
cn=oimLDAP,cn=systemids,dc=mycompany,dc=com
■
Server Password : The password for connecting to the LDAP Server.
■
Server Search DN : The Search DN, if you are accessing your IDStore using
Oracle Virtual Directory Server. For example: dc=mycompany,dc=com.
Click Next. 8.
On the LDAP Server Continued screen, provide the following LDAP server details:
■
LDAP Role Container : The DN for the Role Container. This is the container
where the Oracle Identity Manager roles are stored. For example: cn=Groups,dc=mycompany,dc=com ·
■
LDAP User Container : The DN for the User Container. This is the container
where the Oracle Identity Manager users are stored. For example: cn=Users,dc=mycompany,dc=com·
■
User Reservation Container : The DN for the User Reservation Container. For
example: cn=Reserve,dc=mycompany,dc=com.
Click Next. 9.
On the Configuration Summary screen, verify the summary information.
Click Configure to configure the Oracle Identity Manager instance 10.
On the Configuration Progress screen, once the configuration completes successfully, click Next.
11.
On the Configuration Complete screen, view the details of the Oracle Identity Manager Instance configured.
Notes: BI Publisher is not a part of the IDMDomain. The steps to
configure the BI Publisher are not covered in this Enterprise Deployment Guide.
Extending the Domain with Oracle Identity Manager 14-11
Click Finish to exit the Configuration Assistant. 12.
Restart WebLogic Administration Server, as described in Section 20.1, Starting
and Stopping Oracle Identity Management Components.
14.5 Propagating the Oracle Identity Manager and SOA Managed Servers to OIMHOST1 and OIMHOST2
