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 discusses 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 the Diagnostic Dashboard to Verify Installation

Note:

You must complete all relevant postinstallation steps described in Chapter 7, "Postinstallation Configuration for Oracle Identity Manager and BEA WebLogic Server" before starting Oracle Identity Manager.

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.

Starting Oracle Identity Manager

This section describes how to start Oracle Identity Manager on Microsoft Windows and UNIX.

To start Oracle Identity Manager:

Verify that your database is up and running.
Start Oracle Identity Manager by running one of the following scripts appropriate for your deployment. Running the Oracle Identity Manager start script also starts BEA WebLogic Server.

To start an Administrative Server on Microsoft Windows, run the OIM_HOME\xellerate\bin\xlStartServer.bat script.

To start an Administrative Server on UNIX, run the OIM_HOME/xellerate/bin/xlStartServer.sh script.

Note:

In a clustered enviroment, start the Administrative Server by running the xlStartServer.bat/xlStartServer.sh script, and then start the cluster for admin console.

Stopping Oracle Identity Manager

T his section describes how to stop Oracle Identity Manager on Microsoft Windows and UNIX. To stop an Administrative Server or Managed Server:

Log on to the WebLogic Server Administration Console by using the following URL:
```
http://hostname:port/console
```
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 BEA WebLogic Server is 7001.
Expand the Servers option in the left navigation pane.
Right-click the server that you want to stop, and select Start/Stop Server.
In the main window, select the Graceful shutdown of this server option to stop the server.

Verify that the server is stopped in the Status section at the bottom of the main window.

Note:

In a clustered installation, right-click the cluster name you want to stop and select Start/stop this Cluster, and then click Gracefully shutdown of all Managed Servers. When all the cluster members are shut down, follow steps 2 through 4 to stop the Administrative Servers.

Accessing the Administrative and User Console

After starting the BEA WebLogic 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 BEA WebLogic Server is 7001.

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

For example:
```
http://localhost:7001/xlWebApp
```

After the Oracle Identity Manager login page is displayed, log in with your user name and password.

Using the 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.