About Scenario Manager Login Accounts

OFS AM users gain access to the Scenario Manager application through User ID and password authentication. An associated functional role corresponds to particular user tasks and authorities.

Creating Scenario Manager Login Accounts

As administrator, the user setup process requires that you complete the following tasks:

• Create a database login account and password (Refer to Create the Database Login Account for more information).
• Set up an account and functional roles in the Scenario Manager. Before performing any tasks in the Scenario Manager, you must set up a user login account that establishes access and roles in the Scenario Manager. Perform these setups by adding records to the database.
• Grant the database roles that the functional roles require. You can grant the role of data miner, or MNR to an ScenarioManager user.

Note:

Oracle suggests having only a few generic users in the database to use the Scenario Manager, as most organizations have an extremely small user population to execute these tools.

Create the Database Login Account

The system instantiates the database as a set of Oracle database tables. Therefore, each user whom the OFS AM client authorizes to use the Scenario Manager must have login access to the Oracle database. As administrator, you must setup an Oracle database login account for each user, and assign the KDD_MNR user role to this account.

Note:

OFSBDF does not support external logins (for example, OPS$accounts) in an Oracle database environment. Users must provide an explicit password when logging on.

The assumption is that the Oracle client’s system administrator has training and experience in performing such setups, and, therefore, does not require instructions here on how to perform this task. However, for information about setting up Oracle database accounts, Refer to the appropriate Oracle database documentation.

Note:

The Solaris and Oracle database login user IDs do not have to be identical. However, the Scenario Manager and Oracle database login user IDs MUST be identical.

Set Up an Account and Functional Roles

To create a Scenario Manager account and functional role, follow the steps:

1. Access the KDD_USER table. The following table defines the attributes for the KDD_USER table.

   Table 8-7 KDD_USER Table Attributes

   Column Name	Description
   USER_ID	User’s database login ID.
   USER_NM	User’s name.
   USER_ROLE_CD	User’s default database role.
   ACTV_FL	Active user indication (Y or N).
   WRKLD_CD	Not used by the Scenario Manager.

2. Enter the following information into the table using an SQL script:
   1. User database login ID in the USER_ID column. (The Scenario Manager and Oracle database login user IDs must be identical.)
   2. User name in the USER_NM column.
   3. Default user role in the USER_ROLE_CD column.
   4. To use the Scenario Manager, the user needs the MNR (data miner) database role. The MNR database role is responsible for adjusting the pattern logic of existing scenarios and employs data mining techniques to create new patterns and scenarios.
   5. Flag of Y(es) or N(o) in the ACTV_FL column to specify whether the user is active. A sample SQL insert statement is:

      INSERTINTO KDD_USER VALUES (‘KDD_MNR’, ‘KDD MINER’, ‘MNR’, ‘Y’, ‘FT’);

Grant a Database Role

To grant a database role to the Scenario Manager KDD_MNR user,follow the steps:

1. Access the KDD_USER_ROLE table. The following table defines the attributes in the KDD_USER_ROLE table.

   Table 8-8 KDD_USER_ROLE Table Attributes

   Column Name	Description
   USER_ID	User’s login ID.
   USER_ROLE_CD	User’s database role.

2. .Enter the following information into the table using an SQL script:
   • User login ID in the USER_ID column.
   • User role MNR in the USER_ROLE_CD column. A sample SQL insert statement is:

     INSERTINTO KDD_USER_ROLE values (‘KDD_MNR’, ‘MNR’);