5 Loading Data

This chapter provides the information about the following sections:

Loading Standard and Sample Data
Manual Data Model Deployment

5.1 Loading Standard and Sample Data

To upload the standard data and the sample data into the Role Manager, perform the following procedure.

To load standard and sample data:

If the application server on with Role Manager is deployed is not already running, start it.
In a Web browser, go to the Role Manager Administrative Console. For example, by default:

JBoss: http://<host>:8080/ormconsole

WebSphere: http://<host>:9080/ormconsole

WebLogic: http://<host>:7001/ormconsole
Type user name and password of the Role Manager Administrator previously defined in "Installing Role Manager", and then click Log In.
Click Upload.
Click Browse.
Navigate to select the standard_roles.dar file found in <ORM_install>/samples/sample_data.
Click Load.
Click refresh until you see that all processes are finalized.
Optionally, to upload sample organizations and people, repeat these steps for the sample_data.dar file found in the same location.

Loading the sample data can take several minutes. While data is being loaded, you can click refresh to monitor progress.

Once the data load processes display as being finalized, you can go back to the Role Manager Web application and check the sample data.

5.2 Manual Data Model Deployment

If you change the standard configuration or standard data model, you need to run a command to deploy your customizations to the database.

This procedure assumes you have already completed the following steps:

A database instance has been created for Role Manager with the appropriate tablespaces. (Refer to "Database Setup".)
The Role Manager database owner and application user schemas have been created and contain no data. (Refer to "Creating the Role Manager Users".)
The database is accessible and the service on which Role Manager is installed is started.

To deploy model and configuration customizations:

If you have any custom configuration or data model customizations, create an archive file containing your customizations and append the file name with .car. For more information about custom configuration, refer to the "Oracle Role Manager Administrator's Guide" and for more information about data model customization, refer to Oracle Role Manager Developer's Guide.
In <ORM_install>/config, create a file named db.properties that contains the following two lines:
```
db.driverClass=oracle.jdbc.driver.OracleDriver
db.connection_string=jdbc:oracle:thin:@$HOST$:$PORT$:$SERVICE_NAME$
```
where $HOST$ is the database host name, $PORT$ is the database listener port, and $SERVICE_NAME$ is the database instance on which the Role Manager users were created.
In a command window, navigate to <ORM_install>/bin.
Run the following command to deploy the configuration and data model and create the Role Manager Administrator:
```
deploy "<collection_of_cars>" <orm-owner> <ormapp-user> <admin-user>
```
where:

<collection_of_cars> contains the relative paths and file names of all CAR files to deploy. This collection must be within quotes. This collection must be within quotes with delimiters appropriate to the platform (semicolon (;) for Windows, otherwise colon (:). If you are not deploying any customized CAR files, the default collection must include standard.car and configurations.car.

The first deployment must include the configuration.car* file. If you require the standard data model, for example, if you want to use the out-of-the-box web UI and/or the sample data, you must also include the standard.car file.

Note:
The default configuration.car file gives all privileges from the standard data model to the system administrator system role. If you want to start with a more hardened security policy, you must use the configuration_hardened.car file. You can use the hardened configuration and then decide to give privileges set in the default configuration.car file to the system administrator system role. To do so, you can either use the web UI or load the privilege mappings using the admin_systemrole_privilege_mapping.dar file.

<orm-owner> is the username of the Role Manager database owner user created in "Creating the Role Manager Users"

<ormapp-user> is the username of the Role Manager application user created in "Creating the Role Manager Users"

<admin-user> is the username for the Role Manager Administrator to create.
At the prompt, type the password of the Role Manager database owner.
At the prompt, type the password of the Role Manager application user.
At the prompt, type the password for the new Role Manager Administrator account.

Note:

After deploying the data model and configuration, you must load the sample and the standard data. Refer to "Loading Standard and Sample Data" for instructions.