9 Starting Oracle Identity Manager

This chapter, describes how to start the various Oracle Identity Manager components for Windows and UNIX.

Note: You must complete all relevant post-installation steps described in Chapter 8, "Post-Install Configuration for Oracle Identity Manager and WebLogic" before starting Oracle Identity Manager.

Removing Backup xlconfig.xml Files After Starting or Restarting

After starting any Oracle Identity Manager component either the first time, or after changing any passwords in xlconfig.xml, passwords are encrypted and saved. However, Oracle Identity Manager also keeps a backup copy of xlconfig.xml (named xlconfig.xml.<x>) before saving. This backup xlconfig.xml.<x> file contains the passwords in plain text.

Important: Be sure to remove these files after starting any Oracle Identity Manager component either the first time, or after restarting after changing any passwords in xlconfig.xml once you have established that the new password is working properly. The backup file is named xlconfig.xml.<x>, where x is the latest available number, for example xlconfig.xml.0, xlconfig.xml.1, and so on.

Starting Oracle Identity Manager on Windows

This section describes how to start Oracle Identity Manager on Windows. Start up consists of the following basic steps:

1. Verify that your database is up and running.

2. Start your application server.

3. Start at least one of the Oracle Identity Manager client components.

Starting the Oracle Identity Manager Server

There are two command scripts for starting your WebLogic application server:

• xlStartServer.bat for an administrative server, which resides in the <XL_HOME>\xellerate\bin directory.

• xlStartManagedServer.cmd for a managed server, which resides in the directory <WEBLOGIC_HOME>\user_projects\domains\<domain_name>\, where <domain_name> is the name of your WebLogic domain.

Starting the Administrative and User Console

Once your application server is up and running, you can start your Administrative and User Console.

To start the Administrative and User Console:

1. Launch your web browser, then point it to the following URL:

   http://<hostname>:<port>/xlWebApp

where <hostname> represents the name of the machine hosting the application server, and <port> refers to the port on which the server is listening. The default port number for WebLogic is 7001.

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

For example:

http://localhost:7001/xlWebApp

2. After the Oracle Identity Manager login screen appears, login with your user name and password.

   
   

   Note: The default administrator user name and password are xelsysadm.

   
   

Starting Oracle Identity Manager on UNIX

This section describes how to start Oracle Identity Manager on Solaris. The process consists of the following steps:

1. Verify that your database is up and running

2. Start your application server

3. Start one or more Oracle Identity Manager components

Starting the Administrative and User Console

Once your application server is up and running, you can start your Administrative and User Console.

To start the Administrative and User Console:

1. Open your web browser, and enter the following URL:

   http://<hostname>:<port>/xlWebApp

   where <hostname> is the name of the machine hosting the application server, and <port> is the port on which the server is listening. The default port for WebLogic is 7001.

   
   

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

   
   

   For example:

   http://localhost:7001/xlWebApp

2. After the Oracle Identity Manager login screen appears, login with your user name and password.

   
   

   Note: The default administrator user name and password are xelsysadm.

   
   

Using Diagnostic Dashboard to Verify Installation

The Diagnostic Dashboard verifies each component in your post-installation 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.

Note: See "Using the Diagnostic Dashboard" for information on installing and using the Diagnostic Dashboard.