Skip Headers
Oracle® Identity Manager Installation and Configuration Guide for Oracle Application Server
Release 9.1.0

Part Number E10368-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

8 Starting and Stopping Oracle Identity Manager

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

Important:

You must complete all post-installation steps in Chapter 7, "Postinstallation Configuration for Oracle Identity Manager and Oracle Application 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, UNIX. To start Oracle Identity Manager, start Oracle Application Server. Use the following steps to start the Oracle Application Server and Oracle Identity Manager:

  1. Verify that your database is up and running

  2. Start Oracle Application Server as follows:

    Microsoft Windows

    From the Start menu, select Oracle - Oracle Application Server Instance Name, Oracle Process Manager, and then click Start Oracle Process Manager.

    UNIX

    1. Go to the ORACLE_HOME/opmn/bin directory.

    2. Run the following command:

      ./opmnctl startall
      

Stopping Oracle Identity Manager

To stop Oracle Identity Manager gracefully, stop the Oracle Application Server by performing the following steps:

Microsoft Windows

From the Start menu, select Oracle - Oracle Application Server Instance Name, then select Oracle Process Manager, then select Stop Oracle Process Manager.

UNIX or Linux

  1. Go to the ORACLE_HOME/opmn/bin/ directory.

  2. Run the following command:

    ./opmnctl stopall
    

Accessing the Administrative and User Console

After starting Oracle Application Server and Oracle Identity Manager, you can access the Administrative and User Console. Perform the following steps to access the Administrative and User Console:

  1. Add the fully-qualified domain name of the host with your Oracle Application Server instance to your system's hosts file. This fully-qualified domain name can be found from URL that appears after you log into Enterprise Manager for Oracle Application Server.

  2. Browse 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 Oracle Application Server is 7777. To determine the port that Oracle Application Server is listening on, open ORACLE_HOME/install/readme.txt on UNIX or Linux, and ORACLE_HOME\install\readme.txt on Microsoft Windows.

    Note:

    The application name, xlWebApp, is case-sensitive.

    For example:

    http://localhost:7777/xlWebApp
    
  3. 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:

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

Note:

See "Using the Diagnostic Dashboard" for more information.