Configuring Oracle for Scheduler

There are some configuration procedures that are recommended to be performed to ensure optimal interaction between Oracle and the Scheduler adapter:

  • Configuring Oracle Parameters

  • Configuring User Access

  • Configuring Interception Criteria Access

  • Configuring Interception Parameters

  • Defining an Oracle Applications Agent List

Configuring Oracle Parameters

At the time that the Oracle Applications adapter is installed, these parameters in Oracle should be configured by the Oracle database administrator:

Parameter

Value

REL_EXT_REQ

Specifies whether external requests should be released. Valid values are Y or N.

LOG_EXT_REQ

Specifies whether to log the messages about external requests. Valid values are Y or N.

MASTER_ALLOWED

Specifies which Scheduler master can release external requests.

PURGE_FREQUENCY

Specifies how often the log data recorded about the external requests should be purged. Values are numerical expressing the number of days to keep the data.

PROFILE_ACCESS

Specifies whether the Scheduler administrator can access the Oracle Applications Profile settings to modify the interception criteria. Valid values are Y or N.

Configuring User Access

In most cases, user accounts should be locked down by the DBA to prevent users from going into their accounts to modify their access. If users have access to their account, they could enhance their security access to ensure that their concurrent requests bypass the interception criteria that was created to control the flow of concurrent requests being processed.

The Oracle DBA should configure each user’s access to their profile to prevent users from accessing the profile to make changes. On the CONC_HOLD screen of a profile, configure the profile’s security by clearing the checkmark in the Updatable option in the User Access section. The user can still access their account but they cannot modify the profile.

Configuring Interception Criteria Access

The ability to set up criteria for intercepting jobs is controlled from within Oracle. The Oracle DBA can maintain total control over job interception if needed or the DBA can give the administrator in Tidal Automation the capability to manage job interception. To grant the Tidal Automation administrator this ability to manage job interception criteria, the Oracle DBA must choose the Updatable option in the Program Access section of the CONC_HOLD screen.

If a user in Scheduler cannot modify the interception criteria, Update on the Interception tab of the Oracle connection definition is unavailable.

Configuring Interception Parameters

A parameter configuration table called SABDG_PARAMETERS manages job interception in Oracle Applications. These two parameters should be added to this table:

  • PROFILE_ACCESS – Specifies whether a user can configure the job interception queue filter criteria. The value is either Y or N.

  • MASTER_ALLOWED – Specifies which TA Master is allowed to release jobs. The value is the host machine name. The Oracle Database Administrator should use these SQL statements to populate the SABDG_PARAMETERS table:

    Insert into sabdg_parameters(PARAMETER, VAL_BOOL) values (‘PROFILE_ACCESS’,’Y’)

    Insert into sabdg_parameters(PARAMETER, VAL_STR) values (‘MASTER_ALLOWED’, ‘Host Name’)

Defining an Oracle Applications Agent List

You can assign jobs to run using OracleApps agent/adapter lists similar to the way you assign them to individual agents. With OracleApps lists, however, you have access to useful functions not available with individual connections. You can specify alternate connection(s) to run your jobs if the primary connection is unavailable or you can broadcast jobs to run on all the servers in the list at the same time.

To define an Oracle Applications Agent list:

  1. Click Definitions in the Navigation pane > Agent Lists > OracleApps to display the OracleApps Agent Lists pane.

  2. Right-click the OracleApps Agent Lists pane and click Add Agent List.

    OR

    Click Add on the Scheduler toolbar to display the Agent List Definition dialog.

  3. Enter the name of the OracleApps adapter list (up to 60 characters) in the List Name field.

  4. Click the parent list if you want to create nested lists in the Parent List field.

    If you specify a parent list, the list you are editing will be a child list of the parent and will appear below its parent in the list hierarchy.

  5. Click the type of list based on how you want your jobs to be assigned to an Oracle Applications connection in the list.

    • Ordered – In support of high-availability, Scheduler chooses the first available agent to run the job based on the order that the connections appear in the Agents Selected section. For example, if the first (primary) connection in the list is not available, Scheduler tries the second (alternative) connection in the list. You might want to use this list type for critical jobs where multiple connections are capable of processing the request.

    • Random – Chooses connections from the Agents Selected field randomly. This is a crude form of workload balancing. For more advanced load balancing, you should choose the Balanced option.

    • Rotation – Scheduler cycles through the list of connections in the Agents Selected field and launches jobs assigned to that list in rotation. When the end of the list is reached, the first connection in this list is chosen. This is a form of workload balancing where you can predict where the next job will run.

    • Broadcast – Scheduler runs the job on every connection in the Agents Selected section. For example, you can use this option to schedule a maintenance process on each machine in the list using the same job.

  6. Highlight the appropriate OracleApps agent from the Agents Available section on the List tab.

  7. Click left arrow to add the selected connection to the list by moving it from the Agents Available section to the Agents Selected section. You can also drag and drop connections from one section to another.

  8. Click OK.