What should the owner for a sql job type be set to? And how is the password handled?
Article ID: 18712
Updated On:
Products
Issue/Introduction
Description:
What should the owner for a sql job type be set to within Workload Automation AE 11.3.x? And how is the password handled?
Solution:
Here is an example
C:\Program Files (x86)\CA\Workload Automation AE>autorep -d -J markdb Job Name Last Start Last End ST Run/Ntry Pri/Xit ________________________________________________________________ ____________________ ____________________ __ ________ _______ markdb 04/10/2014 16:30:49 04/10/2014 16:30:49 SU 71/1 0 Status/[Event] Time Ntry ES ProcessTime Machine -------------- --------------------- -- -- --------------------- ---------------------------------------- STARTING 04/10/2014 16:30:49 1 PD 04/10/2014 16:30:49 host1 RUNNING 04/10/2014 16:30:49 1 PD 04/10/2014 16:30:50 host1 SUCCESS 04/10/2014 16:30:49 1 PD 04/10/2014 16:30:50 host1 C:\Program Files (x86)\CA\Workload Automation AE>autorep -q -J markdb /* ----------------- markdb ----------------- */ insert_job: markdb job_type: SQL machine: localhost owner: [email protected] permission: date_conditions: 0 alarm_if_fail: 1 sql_command: "select sysdate from dual" C:\Program Files (x86)\CA\Workload Automation AE>autosys_secure CA WAAE Security Utility Please select from the following options: [1] Activate CA EEM instance security. [2] Manage EDIT/EXEC superusers. [3] Change database password. [4] Change remote authentication method. [5] Manage [email protected] or [email protected] users. [6] Get encrypted password. [0] Exit CA WAAE Security Utility. > 5 Manage [email protected] or [email protected] users Please select from the following options: [1] Create [email protected] or [email protected] password. [2] Change [email protected] or [email protected] password. [3] Delete [email protected] or [email protected] password. [4] Show all [email protected] or [email protected] users. [9] Exit from "Manage [email protected] or [email protected] users" menu. [0] Exit CA WAAE Security Utility. > 4 CAUAJM_I_60140 Listing all [email protected] or [email protected] users: [email protected] ================= excerpt from agentparm.txt file ======================== communication.alias_1=WA_AGENT_DB db.connectionPool.maxSize=5 db.default.password=824CC7B267621C57 db.default.url=jdbc:oracle:thin:@host1:1521:ora11 db.default.user=scott2 db.out.format.paramSeparator=| db.out.format.valueSeparator== db.persistance.connectionKeySeparator=# db.trig.namePrefix=CYB_ db.trig.pollingInterval.ms=10000 db.trig.processMissingTriggers=false db.trig.propfile=dbtrigOracle jdbc.drivers=oracle.jdbc.driver.OracleDriver:sun.jdbc.odbc.JdbcOdbcDriver plugins.start_internal_7=database ==================
Summary
In the above example notice that the agentparm.txt file contains some default values.
The user scott2 along with its encrypted password and a connect string (db.default.url).
If the job definition does not set owner and connect_string then those values in agentparm.txt will be used.
In the job definition markdb we are overriding the user/password and in the job def.
We are using [email protected]
The value ora123 is not a real hostname or valid Oracle SID or dbname.
The database name is ora11, as seen in the db.default.
The string after the @ in the owner field can be an arbitrary value.
This allows for the situation where if one has the same dbname on 2 different hosts and the same user in each database but they have different passwords one can simply set the owner field so that it is unique for each dbname/host.
Example:
owner: [email protected]
owner: [email protected]
Enter each in autosys_secure in that same manner.
username of scott
domain/host of OrclOnHost1
password ...whatever
And
username of scott
domain/host of OrclOnHost2
password ...whatever2
Environment
Component:
Feedback
