If detailed screen shots are needed. You can reach me at
oimimage@gmail.com
Since we installed OIM 11.1.1.5, we are now installing OID stack also on 11.1.1.5
Basic Install Steps
1)Run Rcu 11.1.1.5
2)Install ofm_idm_win_11.1.1.2.0_64_disk1_1of1
3)Install p12395123_111150_MSWIN-x86-64 (11.1.1.5 patch set)
4)Start WLS Admin server
5)Go to C:\Oracle\Middleware\Oracle_IDM2\bin and run config.bat and provide details as requested.
We have now configured OID OVD ODIP ODSM and OHS
::::::OID:::::::
1)Go to WLS admin console and you will see an additional managed server '
wls_ods1'
2)Set a new variable ORACLE_INSTANCE as 'C:\Oracle\Middleware\asinst_1'
(The location of writable files in your Oracle Identity Management installation.)
Now execute the below steps.
C:\Oracle\Middleware\asinst_1\bin>
opmnctl status -l
Processes in Instance: asinst_1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ohs1 | OHS | 2160 | Alive | 1222706905 | 20208 | 20:19:16 | https:9999,https:4443,http:7777
ovd1 | OVD | 3400 | Alive | 1222706897 | 164132 | 20:26:09 | https:8899,ldap:6501,ldaps:7501,http:8080
oid1 | oidldapd | 1776 | Alive | 1222706907 | 58708 | 20:26:41 | N/A
oid1 | oidldapd | 1468 | Alive | 1222706906 | 22964 | 20:26:42 | N/A
oid1 | oidmon | 3916 | Alive | 1222706894 | 30024 | 20:26:42 | LDAPS:3131,LDAP:3060
EMAGENT | EMAGENT | 3884 | Alive | 1222706898 | 13348 | 20:25:46 | N/A
Status tells us that OID, OVD,OHS are up and running.
Now execute the following
C:\Oracle\Middleware\Oracle_IDM2>
ldapbind -h localhost -p 3060 -D cn=orcladmin -w Passw0rd
bind successful
Many of the activities that you can perform at the command line can also be performed in Oracle Enterprise Manager Fusion Middleware Control or Oracle
Directory Services Manager. A few functions are only available from the command line.
Oracle Internet Directory supports the standard LDAP command-line utilities
ldapadd, ldapaddmt, ldapbind, ldapcompare, ldapdelete, ldapmoddn,
ldapmodify, ldapmodifymt, and ldapsearch.
For example:
ldapbind -D "cn=orcladmin" -q -h "myserver.example.com" -p 3060
ldapsearch -b "cn=subschemas
For further information. refer admin guide.
::::::OVD:::::::
Execute the following command to register Oracle Virtual Directory with the
WebLogic Administration Server. Registering with the WebLogic Administration
Server allows you to manage Oracle Virtual Directory using Fusion Middleware
Control.
Execute the following command to register OVD (Most probably you will get an exception as OVD might have been
registered with FMW control during configuration itself!)
C:\Oracle\Middleware\asinst_1>
opmnctl registerinstance -adminHost localhost -adminPort 7001 -adminUsername weblogic
Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:
Registering instance
Command succeeded.
Starting the Oracle Virtual Directory instance, by executing the following
command:
$ORACLE_INSTANCE/bin/
opmnctl startall
(This was already done in our case while configuration itself.as we got alive status above while verifying)
Verifying that Oracle Virtual Directory has started by executing the following
command:
$ORACLE_INSTANCE/bin/
opmnctl status -l
Now execute the following
C:\Oracle\Middleware\Oracle_IDM2>
ldapbind -p 6501
bind successful
:::Common pointers for OID and OVD and OHS::::
For OID or OVD to start serving, there is no necissity to have a weblogic.
You can just power on the system, start the database, start the opmn related service and thats it.
Please see below for further clarity.
I just started the database and the Oracle Process Manager (asinst_1) service.
Now proceed as below
C:\Oracle\Middleware\asinst_1\bin>
opmnctl status -l
Processes in Instance: asinst_1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ohs1 | OHS | 1824 | Alive | 1222707158 | 20216 | 0:10:46 | https:9999,https:4443,http:7777
ovd1 | OVD | 2040 | Alive | 1222707157 | 194720 | 0:10:46 | http:8080,ldap:6501,ldaps:7501,https:8899
oid1 | oidldapd | N/A | Down | N/A | N/A | N/A | N/A
oid1 | oidldapd | N/A | Down | N/A | N/A | N/A | N/A
oid1 | oidmon | N/A | Down | N/A | N/A | N/A | N/A
EMAGENT | EMAGENT | 1996 | Alive | 1222707155 | 11500 | 0:10:46 | N/A
C:\Oracle\Middleware\asinst_1\bin>
opmnctl startall
opmnctl startall: starting opmn and all managed processes...
Oracle Process Manager (asinst_1) service by itself starts all components.
We actually need not issue startall command here. I just showed for a demo here.
In a practical environment, make the opmn process a manual one (you can change in windows services--services.msc)
The reason being, database should be up and running for opmn service to start properly.
So if database and opmn service are both set to automatic, then problems may occur. so set database to automatic. ensure database is up and running, then start opmn. or you can set both to manual.
C:\Oracle\Middleware\asinst_1\bin>
opmnctl status -l
Processes in Instance: asinst_1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ohs1 | OHS | 1824 | Alive | 1222707158 | 20216 | 0:13:50 | https:9999,https:4443,http:7777
ovd1 | OVD | 2040 | Alive | 1222707157 | 194720 | 0:13:50 | http:8080,ldap:6501,ldaps:7501,https:8899
oid1 | oidldapd | 1308 | Alive | 1222707162 | 51196 | 0:00:14 | N/A
oid1 | oidldapd | 3184 | Alive | 1222707161 | 23020 | 0:00:15 | N/A
oid1 | oidmon | 3164 | Alive | 1222707160 | 30108 | 0:00:15 | LDAPS:3131,LDAP:3060
EMAGENT | EMAGENT | 1996 | Alive | 1222707155 | 11636 | 0:13:50 | N/A
So all the processes are alive.
Now you can use a normal LDAP browser and connect to either OID or OVD.
Connect with a ldap browser tool with 3060 non ssl port for OID -- working fine
Connect with a ldap browser tool with 6501 non ssl port for OVD -- working fine.
Connect with a ldap browser tool with 3131 ssl port for OID -- wont work-- reason below
OID SSL port 3131 is configured in SSL 'No-Authentication' mode which uses anonymous ciphers for encryption and server authentication is not performed.
LDAP browser tools do not support anonymous ciphers and hence SSL handshake would fail.
Connect with a ldap browser tool with 7501 ssl port for OVD -- working fine
for us to use Enterprise Manager and Oracle Directory Services Manager to administrate OID or OVD, only then we need to
start weblogic server.
so deploying OID and OVD in WLS is only a nice to have feature. You can as well install them without WLS.
Now start admin server for enterprise manager and wls_ods1 managed server for oracle directory services manager.
-->Starting admin server and managed server for wls_ods1
logon to EM using http://localhost:7001/em/
On the left hand side you will have Farm_[Domain name] under which you have OID, OVD, OIM and DIP listed below 'Identity and Access Management'
Similarly you have ODSM under 'Application Deployments' , OHS under 'Web Tier' and many other FMW components.
Using this EM console, we can do most of admin operations of OID and OVD.. Only to utilize this advantage we have deployed OID and OVD in WLS domain.
logon to ODSM using http://localhost:7005/odsm
This is only a web tool to browse OID and OVD using explorer. But this tool has many limitations.
(refer to admin guide of OVD and OID for these limitations)
Connect to OID with ODSM with ldap ssl port(3060) -- Working fine
Connect to OID with ODSM with ldap non ssl port(3131) -- Working fine
OVD cant be connected with ODSM with ldap ports (ssl and non ssl)
Connect to OVD with ODSM with admin ssl port(8899) -- working fine
Connect to OVD with ODSM with admin non ssl port (8080) -- wont work
In addition to above, we have DSML service for OVD.
DSML stands for Directory Service Markuo Language.
DSML v2.0 is a Web Services protocol that closely mirrors LDAP.
DSMLv2 is designed to allow arbitrary Web Services clients to access Directory Services using the client's native protocols (SOAP over HTTP).
DSMLv2 allows content stored in a Directory Service to be easily accessed by standard off-the-shelf
Web Service applications and development tools, removing the need for application developers to use and understand one of the LDAP SDK libraries.
OVD includes a html based gateway that provides DSML and XSLT rendered directory reporting.
Below are the url's supporting the same.
http://localhost:8080/ --> This is Oracle Virtual Directory browser.
if prompted for username and password, provide cn=orcladmin and its password
http://localhost:8080/Browser.htm
http://localhost:8080/secure/Admin.htm
https://localhost:8899/
if prompted for username and password, provide cn=orcladmin and its password
:::::OHS::::
Below are OHS url's
http://localhost:7777/https://localhost:4443/
Note that OHS got installed along with OID and OVD here.
Actually OID or OVD does not need a OHS.
Most probably OHS is included in OID installation pack because OIF might need that. This is just an assumption. You cannot skip this OHS installation step, but can definitely skip the configuration.
