Cisco Cisco Workload Automation 6.3 User Guide

Page of 40
12
Configuring the Oracle Database Adapter
Defining Oracle Database Adapter Users
b.
Verify that the master is displayed in the 
Service
 list and click on the 
Stop
 button to stop the master.
UNIX:
Enter 
tesm stop
2.
Create the license file:
For a Permanent license, rename your Permanent license file to master.lic.
For a Demo license, create a file called demo.lic, then type the demo code into the demo.lic file.
3.
Place the file in the 
C:\Program Files\TIDAL\Scheduler\Master\config
 directory.
4.
Restart the master:
Windows:
Click 
Start
 in the Service Control Manager. 
UNIX:
Enter 
tesm start
The master will read and apply the license when it starts.
5.
To validate that the license was applied, select 
Registered License
 from 
Activities
 main menu. 
Defining Oracle Database Adapter Users
There are two types of users associated with the Oracle DB Adapter, Runtime Users and Schedulers. You maintain 
definitions for both types of users from the Users pane.
Runtime Users
Runtime users in the context of Oracle DB jobs represent those users and passwords required for Oracle DB 
Authentication. If the Oracle DB server requires authentication based on user and password credentials, these users 
need to be defined as runtime users.
Schedulers
Schedulers are those users who will define and/or manage Oracle DB jobs. There are three aspects of a user profile 
that grant and/or limit access to scheduling jobs that affect Oracle DB:
Security policy—Grants or denies add, edit, delete and view capabilities for Oracle DB jobs.
Authorized runtime user list—Grants or denies access to specific Oracle DB authentication accounts for use with 
Oracle DB jobs.
Authorized agent list—Grants or denies access to specific Oracle DB Adapter connections for use when defining 
Oracle DB jobs.
Defining and securing Oracle Database users with CWA is covered in these sections: