Skip Headers
Oracle® Role Manager Administrator's Guide
Release 10g (

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

Go to previous page
Go to next page
View PDF

1 Introduction

This chapter introduces the Oracle Role Manager administration tools.

It contains the following topics:

1.1 Overview of Oracle Role Manager Administration

Oracle Role Manager administration tools can be divided into the following categories:

Each of these areas of administration can be performed on the command line; data load can also be initiated remotely using the Oracle Role Manager administrative console.

1.1.1 Configuration and Data Model Deployment

Oracle Role Manager configuration is stored in the database and must be deployed (copying the configuration into the database) before any data is loaded into the system. When installing Oracle Role Manager with the Install Software and Configure option, this deployment is done automatically. When installing Oracle Role Manager with the Install Software Only option, this must be performed manually.

Many administrators will select the Install Software Only option so that there is the opportunity to change the default configuration or customize the data model to prepare for loading data into an extended model. Refer to Chapter 2 for more information.

1.1.2 Data Load

The loading of data into Oracle Role Manager can be initiated directly from the command line using the load.bat or scripts and from the Oracle Role Manager administrative console.

The command-line scripts, provided for convenience, can be used for regularly scheduled, automated data loads. When using the administrative console, the Oracle Role Manager server must be deployed to the application server and running before the load process can be initiated. Refer to Chapter 3 for more information.

1.1.3 System Identity Management

System Identities are system users that can be used for access to the Oracle Role Manager system. System Identities normally represent external systems; one example could be a user-provisioning system that accesses Oracle Role Manager as a part of role resolution workflows or access provisioning processes; another example could be for simple data synchronization. Refer to Chapter 4 for more information.

1.2 Displaying the Administrative Console

The URL for the Oracle Role Manager administrative console, including the port number, is determined by the configuration of the application server on which the Oracle Manager server is deployed.

The URL typically includes the name of the application server host computer and the port number assigned during application server configuration.

For example, in WebSphere:


By default, there is only one user of the Oracle Role Manager administrative console, the Oracle Role Manager System Administrator account. The user name and password for this System Identity is set during initial deployment.