8 Starting and Stopping Oracle Identity Manager

This chapter describes how to start and stop Oracle Identity Manager, and how to access the Administrative and User Console. This chapter contains the following topics:

Removing Backup xlconfig.xml Files After Starting or Restarting
Starting Oracle Identity Manager
Stopping Oracle Identity Manager
Accessing the Administrative and User Console
Using Diagnostic Dashboard to Verify Installation

Note:

You must complete all relevant postinstallation steps before starting Oracle Identity Manager. Refer to the "Postinstallation Configuration for Oracle Identity Manager and IBM WebSphere Application Server" section for more information.

8.1 Removing Backup xlconfig.xml Files After Starting or Restarting

After you start any Oracle Identity Manager component for the first time, or after you change any passwords in the xlconfig.xml file, Oracle Identity Manager encrypts and saves the passwords. Oracle Identity Manager also creates a backup copy of the xlconfig.xml file before saving changes to the file. These backup files contain old passwords in plaintext. The backup file are named xlconfig.xml.x, where x is the latest available number, for example xlconfig.xml.0, xlconfig.xml.1, and so on.

Note:

You must remove these backup files after starting any Oracle Identity Manager component for the first time, or on restarting after changing any passwords in xlconfig.xml once you have established that the new password is working properly.

8.2 Starting Oracle Identity Manager

This section describes how to start Oracle Identity Manager on Microsoft Windows, UNIX, or Linux.

To start Oracle Identity Manager:

Verify that your database is up and running.
Start Oracle Identity Manager by starting the WebSphere application server. Run one of the following scripts appropriate for your operating system to start IBM WebSphere Application Server and Oracle Identity Manager:

To start an administrative server on Microsoft Windows, run the WEBSPHERE_HOME\profiles\PROFILE_NAME\bin\startServer.bat SERVER_NAME script.

To start an administrative server on UNIX or Linux, run the WEBSPHERE_HOME/profiles/PROFILE_NAME/bin/startServer.sh SERVER_NAME script.

8.3 Stopping Oracle Identity Manager

This section describes how to stop Oracle Identity Manager gracefully on Microsoft Windows, UNIX, or Linux. To stop Oracle Identity Manager gracefully, you stop the WebSphere application server by running one of the following scripts appropriate for the operating system.

On Microsoft Windows:

WEBSPHERE_HOME\profiles\PROFILE_NAME\bin\stopServer.bat SERVER_NAME

On UNIX or Linux:

WEBSPHERE_HOME/profiles/PROFILE_NAME/bin/stopServer.sh SERVER_NAME

8.4 Accessing the Administrative and User Console

After starting the WebSphere application server and Oracle Identity Manager, you can access the Administrative and User Console by performing the following steps:

Navigate to the following URL by using a Web browser:
```
http://hostname:port/xlWebApp
```
In this URL, hostname represents the name of the computer hosting the application server and port refers to the port on which the server is listening. The default port number for WebSphere is 9080.

Note:
The application name, xlWebApp, is case-sensitive.

For example:
```
http://localhost:9080/xlWebApp
```
After the Oracle Identity Manager login page is displayed, log in with your user name and password.

8.5 Using Diagnostic Dashboard to Verify Installation

The Diagnostic Dashboard verifies each component in your postinstallation environment by testing for:

A trusted store
Single sign-on configuration
Messaging capability
A task scheduler
A Remote Manager

The Diagnostic Dashboard also checks for all supported versions of components along with their packaging.