16.13 Verifying the OIM Installation

Before you can verify the Oracle Identity Manager (OIM) installation, ensure that the following servers are up and running:

  • Administration Server for the domain in which the Oracle Identity Manager application is deployed

  • Managed Server hosting Oracle Identity Manager

  • Managed Server hosting the Oracle SOA 11g suite

You can verify your Oracle Identity Manager installation by:

  • Checking the Oracle Identity Manager Server URL, such as http://<Hostname>:<Port>/oim/faces/faces/pages/Admin.jspx.

  • Checking the Identity Management shell, such as http://<Hostname>:<Port>/admin/faces/pages/Admin.jspx. This shell is used for Users and Role Management tasks.

  • Checking the Oracle Identity Manager Self Service URL, such as http://<Hostname>/<Port>/oim.

  • Verifying the configuration between Oracle Identity Manager and Oracle SOA (BPEL Process Manager) as follows:

    1. Log in to the Oracle Identity Manager Administration Console, with xelsysadm:


    2. Create a Request, such as modifying a user profile.

    3. Log in to the SOA Infrastructure to verify whether the composite applications are displayed.


    4. Log in to the BPEL Worklist application, with xelsysadm:


    5. In the list of tasks, verify whether the request has come for approval.

    6. Click on the task, and click Approve in the Actions tab.

    7. Click on the refresh icon. The request comes back. Approve it again.

    8. Go to http://<host>:<oim_port>/oim/faces/pages/Admin.jspx and verify whether the request is completed.

    9. Go to http://<host>:<oim_port>/admin/faces/pages/Admin.jspx and verify whether the user profile is modified.

  • Logging in to the Design Console, xelsysadm, and the appropriate password. A successful login indicates that the installation was successful.

  • Starting the Remote Manager service by running remotemanager.sh or remotemanager.bat, as appropriate. (remotemanager.sh on UNIX or remotemanager.bat on Windows resides in your Oracle Home directory under a folder named remote_manager.