2 Process Orchestration and Monitoring

The Process Orchestration and Monitoring (POM) application is a user interface for scheduling, tracking and managing batch jobs.

Process Orchestration and Monitoring has the following tabs:

• Batch Monitoring

• System Configuration

• Batch Administration

• Scheduler Administration

• Schedule Maintenance

• AMS Utilities

Batch Monitoring

Batch Monitoring

The Batch Monitoring tab provides a runtime view of the statuses and dependencies with regard to the different batch cycles for the selected business day.

Select Batch Monitoring in the Navigation Area to open the Batch Monitoring tab.

The application will by default open for a business date where at least one schedule is active. If none found, it will open for the most recent business date where at least one schedule is active.

Figure 2-1 Batch Monitoring

Header

The header displays information about the batches displayed in the Batch Monitoring tab. You can also use the header selection to choose which schedule batches to display.

Figure 2-2 Batch Monitoring Header

1. Business Date - Displays the business date for the oldest schedules displayed in Batch Monitoring.

   Use this field to select the oldest schedule displayed in Batch Monitoring.

2. Environment Status Icon - Click this icon to display a panel at the right side of the screen showing the status of the Scheduler, Execution Engine and the environments. The user can also manage the information displayed. See Status for more information.

3. Activity Feed - Click this icon to display a panel at the right side of the screen containing activities performed by the system and by the user.

4. Environments - Displays information about each environment integrated with Process Orchestration and Monitoring.

   Select one of these panels to display information about that environment’s batch processes.

5. Monitoring Cycle - Displays the monitoring cycle of the batches displayed.

   Select a monitoring cycle to see the batches scheduled for that cycle. The following monitoring cycles are available:

   • Nightly

   • Recurring

   • Standalone

6. Upgrade Available - Use this button to navigate to the Schedule Maintenance screen for the option to upgrade the batch schedule to a new version. This button only appears when there is a new version of the schedule available and there is no upgrade in progress or in error. When an upgrade is in progress or in error, the button caption changes to View Upgrades which also navigates the user to the Schedule Maintenance screen.

7. Close Schedule - Use this button to close the schedule. This button only appears for Active schedules.

8. Restart Schedule - Use this button to restart the schedule. This button only appears for Active schedules.

9. Download Cycle Summary - Use this button to download a summary for the currently selected business day for the selected schedule. Once clicked, the Download Cycle Summary dialog provides the user options to select the cycle and format. This button only appears for Completed schedules.

10. Create Schedule - Use this button to create a new Scheduler Day. This button only appears when a schedule tile is selected for which there is no open Scheduler Day. Click this button to create a new Scheduler Day for the selected schedule for the business date following the last schedule instance.

Schedule Tiles

Each schedule tile displays information for a batch schedule that POM is responsible for running.

Select a tile to display the list of batch processes for that schedule.

Each panel displays the following information:

Figure 2-3 Schedule Tile

Note:

• A red tile with a red cloud indicates that a new schedule version upgrade has failed. Navigate to the Schedule Maintenance screen by clicking on the View Upgrades button to address the failure.

• A blue spinner in the top left of the tile (2) indicates that the schedule is in the process of being upgraded to a new version. The user can navigate to the Schedule Maintenance screen by clicking on the View Upgrades button to check the progress of the upgrade.

  When a schedule is being upgraded or when the schedule upgrade has failed, the user is prevented from most activities on the Batch Monitoring and on the Batch Administration screen.

  
  

• An amber warning circle in the top left of the tile (2) indicates that the schedule is set to run in safe mode. This means that the batch schedule will simulate a complete run but without the jobs actually executing on the application server. Aside from the amber warning circle displayed in the top left of the tile, a ‘Safe Mode is currently enabled’ message is displayed in the area right below the tile area.

  

• An amber tile indicates that there is no instance of the schedule for the selected business date.

1. Schedule name and Version - Displays the abbreviation of the application or application group and the software version.

2. Run Status - Displays the status of the batch processes.

   • Completed (green check mark icon)

   • Active (green target icon)

   • Error (red X icon)

   • No activity (amber triangle icon)

   • Suspended (pause icon)

   • Safe mode (Amber circle icon with a warning icon inside of it)

3. Schedule Upgrade - A grey cloud indicates that a newer version of the batch schedule is available.

   A red cloud indicates that schedule upgrade has failed. Navigate to the Schedule Maintenance screen to address the failure.

   A blue spinner indicates that a schedule upgrade is in progress.

4. Monitoring Cycles and Statuses - Displays the number of completed and total processes for each monitoring cycle.

5. Last Schedule Date - Indicates the last date on which the batch processes were configured.

Batch Jobs Header

The batch jobs header displays the following information:

Figure 2-4 Batch Jobs Header

Run Status Chart

The run status chart shows a chart summary of the status of the different batches (including the number of batch jobs with that status) that are included in the selected cycle for the selected schedule. The possible statuses are:

• Loaded - Jobs are in loaded state when the scheduler day is first created.

• Pending - Job is waiting to run.

• Completed - Job ran successfully on the system.

• Error - A failure occurred due to an issue in the environment or the job's application.

• Held - An administrator placed the job on hold.

• Skipped - An administrator has skipped the running of the job so the remaining jobs in the cycle can proceed.

• Running - Job is currently running on the system.

• Long Running - The job's run time has exceeded a threshold. This threshold is calculated by multiplying the job's average run time and the Long Run Average Time Multiplier defined on the schedule Settings section of the System Configuration screen.

• Disabled - Job was disabled by an administrator on the Batch Administration screen.

• System Held - Job was placed on hold by the system due to a lack of resources to run it.

• Skipped on Error - Job was preconfigured to be skipped on a failure.

• Waiting - Job is waiting for completion of pre-dependencies (Hourly Cycle, Nightly Cycle, External Dependency and Inter-Schedule Predecessor Jobs).

Completed Batch Job Statistics

For completed batch jobs, the batch job header shows the following information:

• Run Start

• Run End

• Total Duration

• Average Duration

Active Batch Job Statistics

Note:

Active Batch Job Statistics are not yet implemented. They will be implemented in a future version of POM.

For active batch jobs, the batch job header shows the following information:

• Estimated Completion Time

• Estimated Time Remaining

• Total Duration

• Average Duration

• Run Start

Batch Information

The batch information area displays the following information about the batch process results:

Execution Requests - Displays the number of completed executions and the total number of execution requests. Click to open the Execution Requests Window.

Agent Job Requests - Displays the number of completed and total number of Agent job requests. Click to open the Agent Job Requests Window for the schedule and cycle selected.

Scheduler Tasks - Displays all tasks scheduled to run during the current scheduler day. Click to open the Scheduler Tasks window.

External Dependencies - Displays the number of successful and total number of external dependencies. Click to open the Batch Cycle Details Screen.

Inter-Schedule Dependencies - Displays the number of successful and total number of inter-schedule dependencies. Click to open the Batch Cycle Details Screen.

Callbacks - Displays the number of successful and total number of callbacks. Click to open the Batch Cycle Details Screen.

Schedule Links - Displays the number of successful and total number of schedule links. Click to open the Batch Cycle Details Screen.

Execution Requests Window

The Execution Requests window displays information about execution requests for a batch.

Click Done or the close window icon to close the window.

Figure 2-5 Execution Requests Window

Execution Requests

This section displays the following information about each execution request in the batch process:

• Execution ID

• Status

• Cycle

• Flow

• Scheduler Day

• Total Jobs

• Completed

• Pending

• Skipped

• Failed

• System Held

• Submitted

See Table Menu Options in the Common User Interface Controls for information about the options available for this section.

Execution Details

This section displays the following information about each job run by the execution request:

• Job Run ID

• Status

• Job Name

• Process Name

• Job Execution ID

• Last Update

• First Job

• Error Info

See Table Menu Options in the Common User Interface Controls for information about the options available in this section.

Agent Job Requests Window

The Agent Job Requests window displays information about batch requests submitted to the POM Agent. The agent is the component of POM usually deployed on the application server where the batch jobs actually execute.

Click Done or the close window icon () to close the window.

Figure 2-6 Agent Job Requests Window

Agent Job Requests

This section displays the following information about each Agent job request in the batch process:

• Status - Possible values are Complete, Running, Error, Canceled and Loaded

• Request ID - Agent request ID

• Type - Possible values are EXEC (shell script based job) or RI/RASE/RPAS/BDI which are all values for service based jobs

• Job - job name

• Process - Process name

• Payload - Service payload in case the type corresponds to a service based job

• Info - Error Information in case the request is in Error status

• Agent Id - The identifier of the Agent which Initiates the job execution request

• Application Name

• Create Date

• Start Time

• End Time

• Last Update Time

• Execution Request Id

• Job Run Id

• Submitted

See Table Menu Options in the Common User Interface Controls for information about the options available in this section.

Scheduler Tasks

The Scheduler Tasks window displays information about tasks that are scheduled to run during the current scheduler day. See the Scheduler Administration section of this chapter.

When the new scheduler day is created every day (at the end of the Nightly batch run), it creates the scheduler tasks according to the way they are set up in the Scheduler Administration screen.

Figure 2-7 Nightly Scheduler Task Window

Figure 2-8 Recurring Scheduler Tasks Window

Click Done or the close window icon () to close the window.

The Scheduler Tasks window for the Nightly and Recurring cycles display the same task attributes listed below. The difference is that there is only one Nightly task for a scheduler day whereas there could be multiple Recurring flows running throughout the day.

Nightly/Recurring Scheduler Tasks

This section displays the following information about each Nightly/Recurring Scheduler task:

• Task ID

• Enabled - Switch to enable or disable the execution of the task

• Status - Possible values are: Enabled, Disabled, Completed, Skipped On Delay, Scheduled, Error, or Cancelled

• Flow Name - Nightly or recurring flow name

• Schedule Date

• Schedule Time

• Time Zone

Note:

When the New Scheduler Day is created, if the start time for a certain task has elapsed, the task will be scheduled for the next day. The Next Schedule Run column will show the next time the task will execute.

See Table Menu Options in Common User Interface Controls for information about the options available for this section.

Task Executions

Task Executions

This section displays the following information about each task executions:

• Status - Possible values are: Completed, Error

• Start Time

• Info - If the Status is Error, this field changes to a link which, when clicked, will open a dialog showing error details.

See Table Menu Options in Common User Interface Controls for information about the options available in this section.

The user can edit the Nightly or Recurring tasks to change the time they run for the day. Permanent changes need to be entered in the Scheduler Administration screen.

Note:

If the user makes a change to the time, he or she needs to click the Run action to schedule the task.

Also, for the task to be editable, it must be in a state other than Scheduled. If it is in a Scheduled state, the user can click the stop action, which puts the task in a Cancelled state and it is therefore editable.

It is alternatively possible for the user to circumvent the steps mentioned above and click on Run Now if they intend to schedule the task for immediate execution.

Figure 2-9 Standalone Scheduler Tasks Window

Click Done or the close window icon () to close the window.

Standalone Scheduler Tasks

This section displays the following information about each Standalone Scheduler task:

Task ID

Enabled - Switch to enable or disable the execution of the task.

Status - Possible values are: Enabled, Disabled, Completed, Skipped On Delay, Scheduled, Error, Cancelled.

Process Name

Frequency - Daily or Every x minutes.

Limit Occurrences -If this field has a value, the process will run every x minutes for y occurrences.

Prevent Start During Nightly - Indicates that the process should not start running when Nightly is in progress. If the process starts running before Nightly start, it will continue running even if the run extends into the Nightly run.

Schedule Date

Schedule Time

Next Scheduled Run - Displays the date and time the next run will occur.

Time Zone

See Table Menu Options in Common User Interface Controls for information about the options available in this section.

The user can edit a Standalone task to change any of the fields in the window below. Edits are effective just for the day's run. Permanent changes must be entered in the Scheduler Administration screen.

Note:

If the time is left blank for a standalone task, it will execute immediately upon clicking Ok.

When the New Scheduler Day is created, if the start time for a certain task has elapsed, the task will be scheduled for the next day. The Next Schedule Run column will show the next time the task will execute.

Task Executions

This section displays the following information about each task execution:

• Execution ID

• Status - Possible values are: Completed, Error

• Start Time

• Info - If the Status is Error, this field changes to a link which, when clicked, will open a dialog showing the error details.

See Table Menu Options in Common User Interface Controls for information about the options available in this section.

Batch Cycle Details Screen

The Batch Cycle Details screen displays the following sections:

Header

The header displays the following information about the batch cycle:

• Run Status Chart

Completed Batch Job Statistics

Completed Batch Job Statistics

For completed batch jobs, the batch job header shows the following information:

• Run Start

• Run End

• Total Duration

• Average Duration

Active Batch Job Statistics

For active batch jobs, the batch job header shows the following information:

Note:

Active Batch Job Statistics are not yet implemented. They will be implemented in a future version of POM.

• Estimated Completion Time

• Estimated Time Remaining

• Total Duration

• Average Duration

• Run Start

External Dependencies

The External Dependencies section lists all the external batch job dependencies for the entire current Schedule. These dependencies are only shown if the system level external dependencies indicator is turned on. An external dependency is usually a dependency on a customer's internal process. This dependency is released once the customer calls an endpoint into POM for a specific POM job.

The following information is displayed for each external dependency:

• Status

• Source Job - Click to open the job in the Batch Job Details screen. The source job is a job in the current schedule which is dependent on the external (target) job.

• Target Job - The job that, when complete, will release the dependency which the source job is waiting on.

• A Disable/Enable button to disable or enable the dependency.

Inter-Schedule Dependencies

The Inter-Schedule Dependencies section lists all the inter-schedule batch job dependencies for the entire current Schedule. These dependencies are only show if the system level inter-schedule dependencies indicator is turned on. An inter-schedule dependency links the current schedule and a target schedule where a job in the target schedule is dependent on the completion of a job in the current schedule.

The following information is displayed for each inter-schedule dependency:

• Status

• Source Job - Click to open the job in the Batch Job Details screen.

• Target Job - Click to open the job in the Batch Job Details screen. Target job is dependent on the source job.

• Target Process - Process containing the target job.

• Target Schedule - Schedule containing the target process/job.

• A Disable/Enable button to disable or enable the dependency.

Schedule Links

A Schedule Link links the current schedule and a target schedule where the current schedule does not start until the completion of a job in the target schedule.

The following information is displayed for each schedule link:

• Status

• Source Job - Click to open the job in the Batch Job Details screen. The job in the current schedule which starts the current batch when the Target Job completes.

• Target Job - Click to open the job in the Batch Job Details screen. The job in the Target Schedule which when completes fulfills the dependency for the Source Job in the current schedule.

• Target Process - The process which the Target job belongs to. - The schedule whose job is a dependency for the job in the current schedule.

• Info - Shows information regarding error if failed or skipped.

• Target Schedule

• If it was not successful, a Retry button to retry the schedule link.

Callbacks

The Callbacks section lists all the external status update request and response callbacks based on the External Status Update mode set in the External System Configuration screen.

The following information is displayed for each callback:

• Status

• Job - Click to open the job in the Batch Job Details screen.

• Process - Process containing the job.

• Date of callback

• A Payload link to display the Payload Window for the callback.

• An Info link to display the Info Window describing the callback response.

• If the callback was not successful, a Retry button to retry the callback.

Batch Jobs

The Batch Jobs section lists all the batch jobs for the selected schedule and the selected cycle. The table displays the following information:

• Status

  • Loaded - Jobs are in loaded state when the scheduler day is first created.

  • Pending - Job is waiting to run.

  • Completed - Job ran successfully on the system.

  • Error - A failure occurred due to an issue in the environment or the job's application.

  • Held - An administrator placed the job on hold.

  • Skipped - An administrator has skipped the running of the job so the remaining jobs in the cycle can proceed.

  • Running - Job is currently running on the system.

  • Long Running - The job's run time has exceeded a threshold. This threshold is calculated by multiplying the job's average run time and the Long Run Average Time Multiplier defined on the schedule Settings section of the System Configuration screen.

  • Disabled - Job was disabled by an administrator on the Batch Administration screen.

  • System Held - Job was placed on hold by the system due to a lack of resources to run it.

  • Skipped on Error - Job was preconfigured to be skipped on a failure.

  • Waiting - Job is waiting for completion of pre-dependencies (Hourly Cycle, Nightly Cycle, External Dependency and Inter-Schedule Predecessor Jobs).

• Job - Click to open the job in the Batch Job Details screen.

• Application

• Last Update

• Parameter

• Job Type - Depending on the value, determines if a job is service based or shell script based.

• Process Name

• Process Status

• Log - When the job is in error, this field will display a down-arrow icon which when clicked will display the content of the log.

• Job Description

• Start Time

• End Time

• Duration

• Average Run Time

• Average Historical Run Time

• Number of Runs

• Error Source

• Waiting

• Waiting Reasons

Action Menu and Icons

See Action Menu and Icons for common actions that can be performed through the Action menu and the icons. You can also perform the following actions:

Table 2-1 Batch Jobs - Actions Menu/Icons and Description

Actions Menu/Icons	Description
Hold	Use the Actions > Hold or the Hold button to put the process on hold.
Skip	Use the Actions > Skip or the Skip button to skip the process.
Run	Use the Actions > Run or the Run button to run the process immediately.
Rerun	Use the Actions > Rerun or the Rerun button to run the job again.
Kill	Use the Action>kill or the Kill button to stop the execution of the job. The job needs to be running for this action to be enabled. When the Kill command is enacted on the screen one of two confirmation messages opens depending on whether a cleanup script is associated with the job being killed. If a cleanup script is associated with the job, the confirmation message presented is “a cleanup will be performed after this job is terminated. It is advisable to wait a few minutes after termination before proceeding with the remaining batch schedule” This is because it may take a minute or so for the cleanup to complete. If a cleanup script is not associated with the job, the user is cautioned to make sure he or she is sure about proceeding without a cleanup script. That maybe be acceptable, as not all jobs require cleanup when terminated. The confirmation message in this case is “there is no post termination cleanup script associated with this job. the job will be terminated but not post cleanup will be performed. This may or may not be ok for this job. Check with Oracle Support if this is a concern.
Edit Parameters	Use the Actions > Edit Parameters or the Edit Parameters button to edit the parameters for the job. The new parameters are only effective for the current day's batch run.

View Menu

See View Menu for information about the options in the View menu.

Status Details for Job

Certain status values on the Batch Jobs section such as 'Error' or 'Long Running' act as a link. When clicked a popup is displayed containing more details about why the job is in the given status and helpful suggestions for resolving the issue. An example is shown below for a job in error.

Footer

The screen can be set to auto refresh periodically by selecting the pre-defined interval from the Auto Refresh list. By default, this value is set to None on page load.

Use the Refresh button to refresh the screen immediately.

Use the Recover button to automatically attempt fixing system failures and resume the schedule. This is useful if there is a system or communications failure that interrupts the execution of a schedule.

Last refreshed shows the time and date of the last refresh of the interface.

Batch Job Details

The Batch Job Details screen provides detailed information about a batch job.

Depending upon the status of the job, one or more of the following buttons will be available at the top of the screen:

• Hold

• Run - This is available only for Standalone jobs.

• Release

• Release Skip

• Rerun

• Skip

Figure 2-10 Batch Job Details

Figure 2-11 Batch Job Details with Status Information

Execution Requests

If the job was executed, this section displays the following information about the job execution:

• Status

• Execution ID

• Request Time

• Error Info - This will only show in case of an error status.

Executions

If the job was executed, this section displays the following information about the job execution:

• Status

• ID

• Job Run ID

• Start Time

• End Time

• Log - Provides a link to download the execution log.

Pre Dependencies

This section displays the following information about job pre-dependencies:

• Status

• Job - Click to open the job in the Batch Job Details screen.

• Process

• A Disable/Enable button is available for jobs that have not yet completed.

Post Dependencies

This section displays the following information about job post-dependencies:

• Status

• Job - Click to open the job in the Batch Job Details screen.

• Process

• A Disable/Enable button is available for jobs that have not yet completed.

External Dependencies

An external dependency is usually a dependency on a customer's internal process. This dependency is released once the customer calls an endpoint into POM for a specific POM job. This section displays the following information about job external dependencies:

• Status

• Job - Click to open the job in the Batch Job Details screen. The job that, when complete, will release the dependency which the currently displayed job is waiting on.

• A Disable/Enable button is available for jobs that have not yet completed.

Inter-Schedule Dependencies

An inter-schedule dependency links the current schedule and a target schedule where a job in the target schedule is dependent on the completion of the currently displayed job in the current schedule. This section displays the following information about job inter-schedule dependencies:

• Status

• Job - Click to open the job in the Batch Job Details screen. Job which is dependent on the source job.

• Process - Process containing the job.

• Schedule - Schedule containing the process/job.

• A Disable/Enable button is available for jobs that have not yet completed.

Schedule Links

This section displays the following information about schedule links for a job:

• Status

• Job - Click to open the job in the Batch Job Details screen. The job in the Target Schedule that., when completed, will fulfill the dependency for the currently displayed schedule.

• Process - The process the job belongs to.

• Schedule - The schedule whose job is a dependency for the job in the current schedule.

• Info - Shows information regarding error if failed or skipped.

• A Disable/Enable button is available for jobs that have not yet completed.

• A Retry button is available for schedule links with a Skipped or Failed status.

Callbacks

This section displays the external status update request and response callbacks based on the External Status Update mode set in the External System Configuration screen. This section displays the following information about job callbacks:

• Status

• Job - Click to open the job in the Batch Job Details screen.

• Process

• A Payload link to display the Payload Window for the callback.

• An Info link to display the Info Window describing the callback response.

• A Retry button is available for callbacks with a Skipped or Failed status.

Payload Window

The callback payload window shows the field name and value for each field in the payload.

Select Done to close the window.

Figure 2-12 Callback Payload Window

Info Window

The callback info window shows information about a request and response.

Select Done to close the window.

Figure 2-13 Callback Info Window

Status

Status

The Status sidebar displays information about the Scheduler, Execution Engine, and the environments that Process Orchestration and Monitoring communicates with to execute batches.

Figure 2-14 Status Sidebar

Scheduler

Displays the status of the Scheduler, and an Admin link to enable or disable the scheduler for a particular batch schedule in the Scheduler Administration window.

Execution Engine

Displays the status of the execution engine, and a Config show configuration of the execution engine in Execution Engine Configuration.

Environment Statuses

Displays the following for each environment:

Figure 2-15 Environment Status

1. Status - Icon indicating the current status of the integration with the environment. This will be either success or error .

2. Environment - Abbreviation of the environment name.

3. Health Check - Opens the Health Check for the environment.

4. Link - An icon which indicates if Inter-Schedule Dependencies are enabled or disabled.

5. Active/Inactive Switch - Turning the switch deactivates the job agent for the environment.

Download Cycle Summary

Use the Download Cycle Summary window to download information about a completed batch cycle:

1. Click Download Cycle Summary in the Batch Jobs Header.

   The Batch Cycle Summary window opens.

   Figure 2-16 Download Cycle Summary Window

   

2. Use the Cycle menu to select the cycle for which to download the summary.

3. Select the Type of data to download: CSV (comma-separated values) or JSON.

4. Click Download to download the summary file, or click Cancel to close the window without downloading.

Scheduler Administration Window

The Scheduler Administration window allows you to enable or disable batch schedules.

When the Scheduler is disabled for a particular schedule, tasks will still be scheduled and will still trigger at the specified time but will immediately move to the Canceled state.

Select the Done button to close the window.

Figure 2-17 Scheduler Administration Window

Execution Engine Configuration

The Execution Engine Configuration window displays configuration of communication between the user interface and the execution engine.

Select the Done button to close the window.

This window displays the following configurations:

Figure 2-18 Execution Engine Configuration Window

• Executor Service Polling Interval - Determines the number of seconds between each polling interval for the batch execution process on Process Orchestration and Monitoring.

• Monitoring Service Polling Interval - Determines the number of seconds between each polling interval for the monitoring process on Process Orchestration and Monitoring.

• Thread Pool Size - Maximum number of concurrent threads permitted for use by the Execution Engine.

Health Check

The Health Check window displays the status of the processes communicating with the environment.

Figure 2-19 Health Check Window

This window displays the following for each communication process:

• Severity - The severity of any errors in communication:

  • SUCCESS - The process communicates successfully.

  • ERROR - The process is not communicating with the environment.

• Source - The name of the process and the response received by the process.

Activity Feed

The Batch Monitoring screen includes an Activity Feed icon at the top right corner.

When the icon is clicked, the Activity Feed panel opens on the right side of the screen. The panel displays up to seven days’ worth of activities performed both by the system and by users through the user interface.

Click the close window icon () to close the window.

Figure 2-20 Activity Feed

System Configuration

The System Configuration screen allows an administrator to modify parameters and connection properties for the environments integrated with Process Orchestration and Monitoring. It also allows an administrator to maintain POM application level configurations.

Select System Configuration in the Navigation Area to open the System Configuration screen and select the Schedules tab. This tab displays the schedule level configurations for each schedule setup for this environment.

Figure 2-21 System Configuration

Configure New Schedule

When POM is first installed for a specific customer, it does not include any application batch schedules out of the box such as Merchandising, Retail Intelligence, and so on. An Oracle administrator or a system integrator needs to first configure those schedules before they can be loaded (from a batch schedule spreadsheet). Configuring a new schedule entails setting up schedule properties such as the schedule name and description, customer environment information for callbacks. It also entails setting up the location of different components and services with which different POM components need to interact to function properly.

Configuring a new schedule is typically done upon provisioning the environment by Oracle operations. If for any reason the configuration has not yet been done by Oracle, an administrator can alternatively accomplish that through the UI.

To configure a new schedule, click the Configure New Schedule button at the top right of the Schedules tab of the System Configuration screen. The Configure New Schedule window is displayed.

Figure 2-22 Configure New Schedule

The following new schedule information can be set on this window:

• Schedule Configuration - This is for identifying and describing the schedule. Attributes for this section are:

  • Schedule Name - A short identifier of the new schedule. This usually matches the main application name such as Merchandising, RI, and so on.

  • Description - A short description of the schedule.

• External System Configuration - This identifies an external system, typically a customer's environment. This is needed for optionally notifying the customer's system of a job failure or success. This feature is also referred to as Callback. Attributes for this section are:

  • URL

  • Username

  • Password

• Platform Services - Internal Oracle services for retrieving information stored there by other applications or systems. Attribute for this section is:

  • URL

• Job Agent - The Job Agent is a component of POM responsible for submitting the request to execute a batch job. This is usually deployed in the same location as the application where the jobs actually run. If the schedule being configured contains multiple applications, it is optional to add an agent for each application. This isn't a common practice however as an agent can handle running multiple applications. Attribute for this section is:

  • URL

• Schedule Variables - These variables hold System (POM) level configurations such as IDCS or OCI IAM URL, or Job level configurations such as batch directory, DB_ALIAS, and so on. The job level configurations can also be defined on the batch schedule spreadsheet. Attributes for this section are:

  • Type - Job or System

  • Variable Name

  • Value

• Services - This section allows for entry of services POM integrates with. These include the BDI Process Services, IDCS or OCI IAM, and all services corresponding to the different applications with service-type batch jobs. Attributes for this section are:

  • Type - This is a drop down for all the possible service types; for example, the RI Web Services URL which POM would use to invoke RI service-based batch jobs.

  • Application - Application Name to which this service corresponds such as RI.

  • URL

• Job Type - This is an optional section for setting up one or more custom job types other than the standard, pre-defined job types provided by the retail applications, such as EXEC, RI, RASE, BDI, and RPAS. The user then associates a custom job type with the base URL for endpoints at the destination system. These are endpoints for starting a job, restarting a job, killing a job, checking status of a job, fetching the log for a job, and validating the URL. By setting up a custom job type, the user must then create a custom schedule spreadsheet containing jobs with that job type. When this batch schedule runs, POM executes that job using the corresponding, defined Start endpoint. If the user misses the opportunity to configure the job type at this point, they do have the opportunity to add that using the Job Type Configuration screen (see Edit Job Type for more information). Attributes for this section are:

  • Name – A short, alphanumeric identifier of the job type. This typically reflects the system or application where associated jobs are to be executed (for example, RDS).

  • URL – Base URL for endpoints at the destination system where batch is to be invoked (for example, https://server/services/batch).

  • OAuth Scope – Authentication scope for accessing the batch endpoints at the above URL.

Schedule Settings and Connections Configuration

Select the Schedules tab on the System Configuration screen to configure the settings and connections for an environment.

The following information is shown for each environment:

• Schedule name abbreviation.

• Schedule version number.

• Business Date - Date for which the specific schedule's batches will run next.

• The system options are a set of key-value pair of attributes and values specific to the given schedule such as location of directories or throttle enabling setting. System options can also be used to define shell script warning or error exit codes. If any such codes are specified, they will cause a shell script based job to fail or complete with warning.

  Examples of system options:

  Last Schedule Update - Last date on which the schedule was updated.

• System Options link

  Each Schedule is associated with a number of system options specific to its environment and settings. Those can be edited by clicking the System Options link located next to the Business Date.

  Figure 2-23 Edit System Options

  

  The system options are a set of key-value pair of attributes and values specific to the given schedule such as location of directories or throttle enabling setting. System options can also be used to define shell script warning or error exit codes. If any such codes are specified, they will cause a shell script based job to fail or complete with warning.

  Examples of system options:

  Key	Value
  enableThrottling	FALSE
  WarningCode110	Some input files were not processed
  ErrorCode40	Input file corruption detected

  The user can edit the values, add or remove options.

• Settings - See Edit Settings for details.

  

  • Data Retention Days

  • Long Run Average Time Multiplier

  • External Dependencies

  • InterSchedule Dependencies

• Throttling - See Edit Throttling for details.

  

  • Job Agent Throttle Limit

• Environment - See Edit Environment for details.

  

  • Job Agent name (for example, RPASCE). This also acts as a link which, when clicked, opens the Job Agent Configuration Window.

  • Job Agent version

• External Configuration - See Edit External Configuration for details.

  

  • External URL

  • External Status Update Mode

  • Credentials

• Job Type - See Edit Job Type for details.

  

  • Job Type - For example, RDS.

Edit Settings

To edit the settings for an environment, click the edit icon in the Settings section to open the Settings window.

Figure 2-24 Edit Settings Window

The following settings are available in this window:

• Data Retention Days - Number of days for which data is to be retained

• Long Run Average Time Multiplier - Used to calculate when a job is considered long running.

  A job is long running when its current run time is longer than this number times than the average run time of that job. For example, if a job's average run time is 3 minutes, and the Long Run Average Time Multiplier is 3, then the job is considered long running if it has been running for at least 9 minutes. A notification is sent when a job is deemed long running.

• Default Average Time Multiplier - This multiplier is used in lieu of the Long Run Average Time Multiplier when the latter has no value.

• Business Date - The earliest business date for which to run batch schedules. See Business Date Explained for an explanation of how POM uses this setting.

• Background Jobs - Enable or disable background jobs.

• External Dependencies - A switch for enabling or disabling external dependencies.

• InterSchedule Dependencies - A switch for enabling or disabling InterSchedule dependencies.

• Repave Strategy - This strategy together with the next field's value is used to determine if a job should be allowed to run on a particular server node. When a node is scheduled to be repaved (updated with the latest software patch), no batch job should be running on it when the repave starts. To prevent such a situation, a best guess is needed as to when a node should stop accepting jobs to be run. There are two strategy for determining when that time is:

  • Fixed: Uses the next field's value (Window Duration - in seconds) to determine the time at which the node will start rejecting requests for running jobs. For example, if this value is 3600 seconds, the node will stop accepting requests one hour before the repave starts.

  • Variable: Multiplies the next field's value (multiplier) with the job's average run time to determine if the node likely has enough time to run the job to completion. For example, if the multiplier is three and the job about to be submitted for running on this node has an average run time of five minutes and the repave is due to start at a time longer than the 15 minutes (the product of the two numbers), the job will be allowed to run. Otherwise it won't be.

• Window Duration / Multiplier - This field is dynamically altered depending on the previous field's value and is used in conjunction with the previous field. See the previous field's explanation for details.

Select OK to save the changes, or select Cancel to exit the window without saving changes.

Business Date Explained

When the business date is initially set, it's supposed to be set as the First Run Business Date. It's meant for the POM application to compare to the Current Business Date (shown below the Business Date on the screen). If the (First Run) Business Date is earlier than the Current Business Date, POM will run the next batch schedule for the day after the Current Business Date. If the (First Run) Business Date is later than the Current Business Date, POM will run the next batch schedule for that date rather than the day after the Current Business Date.

Note:

The Current Business Date advances automatically every time batch completes for the day

The reason the (First Run) Business Date is updatable on this screen, is to give the ability to start the next schedule run at that date, skipping some run days. Here are a couple example scenarios:

Scenario 1: Common Scenario

System Configuration screen's Business Date: 11/28/2019

System Configuration screen's Current Business Date: 08/12/2019

The next batch schedule run will be for business date 08/13/2019.

When that batch run starts, the Current Business Date advances to 08/13/2019 and the screen is updated accordingly.

Scenario 2: Skip a Few Days

System Configuration screen's Business Date: 11/28/2019

System Configuration screen's Current Business Date: 08/12/2019

User changes the Business Date on the System Configuration screen to 08/18/2019

The next schedule run will be for business date 08/18/2019.

When that batch run starts, the Current Business Date moves to 08/18/2019 (since the (First Run) Business Date is greater than Current Business Date) and the screen will be updated accordingly. The (First Run) Business date will remain at 08/18/2019 until changed by an administrator on this screen.

Edit Throttling

The throttling settings can be changed by selecting the edit icon in the Throttling section to open the Throttling window.

Figure 2-25 Edit Throttling Window

This window allows for update of the throttling value for each application hosted on this Job Agent.

Select OK to save the changes, or select Cancel to exit the window without saving changes.

Edit Environment

The environment settings can be changed by selecting the edit icon in the Environment section to open the Environment window.

Note:

One schedule can be supported by one or multiple Job Agents. Usually, the mapping is one Job Agent to an application.

Also, the Job Agent is a component of POM responsible for submitting the request to execute a batch job.

Figure 2-26 Edit Environment Window

At the top of the Environment window, the user can set the Platform Services URL.

The window then provides two tabs: the Job Agents tab and the Services tab.

On the Job Agents tab, the user can add or change the following Agent related information:

• Application - application name

• Name - Agent's name

• Job Agent Version - Release version of the Agent

• Job Agent URL

On the Service tab, the user can add or change services related information. These are services that POM integrates with, such as BDI Process Services, IDCS or OCI IAM, and all services corresponding to the different applications with service-type batch jobs.

Select OK to save the changes, or select Cancel to exit the window without saving changes.

Job Agent Configuration Window

The Job Agent Configuration window displays configuration information about the selected Agent.

An Agent is the component usually deployed alongside the application for which the batch runs. It receives requests from the POM application, usually deployed on a common server. These requests direct the agent to invoke the actual job execution on the target application.

Select the Done button to close the window.

Figure 2-27 Job Agent Configuration Window

This window displays information about the Agent's Configuration Settings, Throttle Groups and Job Types.

It also displays a Configuration URLs section which lists service URLs that POM needs to operate. These include service URLs for calling endpoints to execute batch in the case where the jobs are service-based (versus shell-script-based) and are of pre-defined job types such as RI, RASE and RPAS.

The Throttle Groups section displays throttle limits (the maximum number of job that can execute concurrently). These are defined either on the batch schedule spreadsheet or on the Throttling section of this System Configuration screen.

The Job Types Configuration section displays all custom job types defined either on the batch schedule spreadsheet or on the Job Type section of this System Configuration screen.

This window also features a Sync With POM button (formerly called Publish). When clicked, it will synchronize the information on this screen from POM to the Job Agent. These changes are also synchronized automatically to the Job Agent upon the daily creation of a new scheduler day.

Edit External Configuration

The external configuration settings can be changed by selecting the edit icon in the External Configuration section to open the External Configuration window.

Figure 2-28 Edit External Configuration Window

The following settings are available in this window:

• External Status URL - Customer system's URL that is called when POM is to notify the customer's system. Note that this calling feature is also referred to as Callback.

• External Status Update Mode - Job status for which POM is to call the customer's URL. This menu has the following options:

  • ALL - POM will make a call for each job's execution regardless of success or failure.

  • FAILED - POM will make a call only for failed jobs.

  • NONE - POM will never make a call.

• Update Credentials - When clicked, User Name and Password fields are shown. Setting these values will update the credentials POM uses to call the customer's URL.

Select OK to save the changes, or select Cancel to exit the window without saving changes.

Edit Job Type

The job type configuration can be changed by selecting the edit icon in the Job Type section to open the Job Type Configuration window .

Figure 2-29 Job Type Configuration Window

This window displays a table of configured job types. Each row contains the following fields:

 Job Type - A short, alphanumeric identifier of the job type. This typically reflects the system or application where associated jobs are to be executed (for example, RDS).

 URL - Base URL for endpoints at the destination system where batch is to be Invoked (for example, https://server/services/batch).

 Job Start - Endpoint for invoking the execution of a job.

 Job Restart - Endpoint for restarting the execution of a job after failure.

 Job Status - Endpoint for POM to fetch the status of a started job.

 Job Kill - Endpoint for terminating the execution of a running job.

 Job Logs - Endpoint for fetching the log(s) for a job.

 Validation - Endpoint for validating that the endpoints are reachable.

 Scope - Authentication scope for accessing the above endpoints.

The user can edit or delete an existing row, or create a new job type.

Select OK to save the changes, or select Cancel to exit the window without saving changes.

See the POM Implementation Guide for additional details on setting up custom schedules with custom job types.

System Settings

Select the System tab in the System Configuration screen to view the system configuration for Process Orchestration and Monitoring.

Figure 2-30 System Information Screen

Edit System Settings

Select the edit icon (not shown) located at the rightmost of the System Information window to enable the editing of information on this window.

Figure 2-31 Edit System Settings Window

The following settings are available in this window:

• Environment Name - This is the physical environments name such as '<customer name> stage 1'.

• Customer Name

• Process Services URL - This URL is set at install time and cannot be changed on this window. It shows the value of POM's services URL.

• Platform Services URL - This URL is set at install time and cannot be changed on this window. It shows the value of the Platform Services URL.

• Deployed on CFS - A flag indicating whether this environment is on the Oracle's CFS platform.

Select OK to save the changes, or select Cancel to exit the window without saving changes.

Global Edit

Select the Global Edit button to open the Global Edit screen. This screen sets configurations for all the schedules. Refer to the sections above for explanation of the different configurations.

Figure 2-32 Global Edit Screen

Use the Apply check boxes to activate the fields for the settings to be applied to all schedules. The following settings can be applied to all schedules:

• Data Retention Days

• Long Run Average Time Multiplier

• Business Date

• Background Jobs

• External Dependencies

• InterSchedule Dependencies

• External URL

• External Status Update Mode

• Repave Strategy

• Credentials:

  • Username

  • Password

Batch Administration

The batch administration screen provides the ability to maintain information specific to the batch schedule.

Select Batch Administration in the Navigation Area to open the Batch Administration tab.

Figure 2-33 Batch Administration

Batch Administration Header

The Batch Administration header includes the following options:

1. Batch Tiles - There is a batch tile for each software environment Process Orchestration and Management connects to. Select a tile to show the batch processes for that environment. See Batch Tiles for more information about these tiles.

2. Cycle Tabs - Displays the cycles for which batch information is to be maintained.

   Select a cycle tab to see the batch details for that cycle. The following cycles are available:

   • Nightly

   • Recurring

   • Standalone

3. Export Config - Use this button to export configurations for the selected schedule and cycle. These configurations include Scheduler tasks, throttle limit values, data retention values, notifications settings and (most importantly) which jobs are enabled or disabled.

   When clicked, the user is presented with a dialog for selecting the type of file to export (JSON or Excel)

   

   Depending on the user's browser setting, the file is either saved in the default local file system directory or a file save/open dialog is presented first.

   

   If the export is done for the purpose of applying the same configurations on another environment (Lift & Shift), the user is recommended to export to a JSON file. This file is then used in the Import Config function (explained below) to import the configurations into another environment.

   The user has the option to manipulate the exported file before importing back into the same environment or a different one. In that case an export to an Excel file is more suitable for ease of manipulation. Caution needs to be taken when manipulating the content of the exported file, especially for maintaining proper data format.

   Refer to the “Export/Import Schedule Configuration” chapter of the Process Orchestration and Monitoring Implementation Guide for details on applying changes to the exported spreadsheet before importing it back in.

4. Import Config - Use this button to import new batch configurations for the selected schedule and cycle. When clicked, the user is presented with a dialog to select the desired type of import.

   

   The user can select to import Scheduler tasks configuration and/or Jobs configuration and/or Notifications configuration. The jobs configuration includes such settings as throttle values, data retention values, enabled/disabled setting and Job Start/Completion notifications. The Scheduler tasks are those directives for the POM Scheduler to run the different batch cycles at specified times. The Notifications configuration includes e-mail addresses and retention periods associated with the different notification types.

   Once the import type is selected and the Import Config button is clicked, the user is presented with a file selector dialog (not shown). User can then choose to import a JSON or an Excel file.

5. When a schedule is being upgraded using the Schedule Maintenance screen or when the schedule upgrade has failed, the user is prevented from most activities on the Batch Monitoring and on the Batch Administration screen.

   
   

Batch Tiles

Each tile displays the following information:

Figure 2-34 Batch Tile

1. Schedule Name and Version - Displays the abbreviation of the application or application group and the software version.

2. Cycles and Statuses - Displays the number of batch processes for each cycle.

Batch List

The information in the batch list depends upon the cycle chosen:

• Nightly

• Recurring

• Standalone

Actions Menu and Icons

Actions Menu and Icons

See Action Menu and Icons for common actions that can be performed through the Action menu and the icons. You can also perform the following actions:

Table 2-2 Batch Jobs - Actions Menu/Icons and Description

Actions Menu/Icons	Description
Edit and Edit icon	Select an item in the table, then select Actions > Edit or the edit icon to edit the item.
Enable All	Use the Actions > Enable All or the Enable All button to put the process on hold.
Disable All	Use the Actions > Disable All or the Disable All button to skip the process.

View Menu

See View Menu for information about the options in the View menu.

Nightly

The nightly cycle displays the following information for each batch:

Figure 2-35 Nightly Batch List

• Enabled

• Job - Click the Job to open the batch in the Batch Job Details screen.

• Process Name

• Application - A schedule may be made up of multiple applications. There needs to be at least one application.

• Module - An application may be made up of multiple modules. Modules within an application are optional.

• Parameters - A job may be run with a list of input parameters. This column always shows the original list of parameters.

• Active Parameter - This column shows the customized list of parameters.

• Job Type - A Job Type is an attribute of a Job in POM and signifies the kind of Job that is run. POM has the following pre-built Job types:

  • EXEC - For all shell-script based jobs

  • RI - DIS-based jobs for the RI schedule

  • RASE - DIS-based jobs for the RSP schedule

  • BDI - BDI Jobs

  • RPAS - RPAS-Web Service jobs for the RPAS schedule

• Kill Cleanup Script - Name of a script that will be executed after the kill is performed. This is an optional field as not all jobs require cleanup after termination.

• External Status Update - Job status for which POM is to call a customer's URL. The URL is defined in the External Configuration section of the System Configuration screen. This column has the following possible values:

  • ALL - POM will make a call for this job's execution regardless of success or failure.

  • FAILED - POM will make a call only for if this job fails.

  • NONE - POM will not make a call.

• Notification At

  • Start of Job – Send notification of type JobStarted when the selected job starts.

  • Completion of Job - Send notification of type JobCompleted when the selected job completes successfully. Note that there is a separate notification of type Error that is sent when a job fails.

• Skip On Error - Skip this job if it fails.

• Threshold Run Time (Seconds) - Amount of time greater than which the job is deemed long running.

• Notes

• Job Name

• Job Wrapper Name

• Days of the Week - Days of the week for which the job is to be run.

Recurring

The Recurring cycle includes an Hourly Cycle menu. Select an hour in this menu to choose the hour of the day during which the displayed jobs will run.

The recurring cycle includes the following information for each batch:

Figure 2-36 Recurring Batch List

• Flows - Select a flow in the Flows list to view all jobs for that flow. The following information is shown for each flow:

  • Flow Name

  • Enabled or Disabled

• Jobs - The Jobs list shows the following information for each job. Refer to the Nightly cycle above for an explanation of each field:

  • Enabled

  • Job - Click the Job to open the batch in the Batch Job Details screen.

  • Process Name

  • Application

  • Module

  • Parameters

  • Active Parameter

  • Job Type - Job Type of 'EXEC' Indicates that the job executable is shell script based. All other job types, such as 'BDI', 'RI', and so on, indicate that the job is service-based. Service-based job types require different configurations than shell-script based.

  • Kill Cleanup Script - Name of a script that will be executed after the kill is performed. This is an optional field as not all jobs require cleanup after termination.

  • External Status Update

  • Skip On Error

  • Threshold Run Time (Seconds)

  • Notes

  • Job Name

  • Job Wrapper Name

  • Days of the Week

Standalone

The standalone monitoring cycle includes the following information for each batch. Refer to the Nightly cycle above for an explanation of each field:

Figure 2-37 Standalone Batch List

• Enabled

• Job - Click the Job to open the batch in the Batch Job Details screen.

• Process Name

• Application

• Module

• Parameters

• Active Parameter

• Job Type - Job Type of 'EXEC' Indicates that the job executable is shell script based. All other job types, such as 'BDI', 'RI', and so on, indicate that the job is service-based. Service-based job types require different configurations than shell-script based.

• Kill Cleanup Script - Name of a script that will be executed after the kill is performed. This is an optional field as not all jobs require cleanup after termination.

• External Status Update

• Skip On Error

• Threshold Run Time (Seconds)

• Notes

• Job Name

• Job Wrapper Name

• Days of the Week

Batch Job Details

The Batch Job Details screen allows maintenance of various types of dependencies associated with a batch job.

Figure 2-38 Batch Job Details

Pre Dependencies

This section displays the following information about a job's pre-dependencies:

• Enabled - Switch to enable or disable the pre-dependency.

• Job

• Process

Post Dependencies

This section displays the following information about a job's post-dependencies:

• Enabled - Switch to enable or disable the post-dependency.

• Job

• Process

External Dependencies

This section allows for the maintenance of the following information about a job's external dependencies. An external dependency is normally a process internal to a customer's system.

• Enabled - Switch to enable or disable the external dependency.

• Job

• A Remove button is available to delete the external dependency.

Inter-Schedule Dependencies

This section allows for the maintenance of the following information about a job's inter-schedule dependencies. An inter-schedule dependency is a dependency for the current job on a job belonging to another batch schedule. The job for which this Jobs Detail screen is shown will wait for the job entered here.

• Enabled - Switch to enable or disable the inter-schedule dependency.

• Job - Name of job belonging to the other schedule.

• Process - Name of process containing Job.

• Schedule - Name of other schedule containing the dependency.

• A Remove button is available to delete the inter-schedule dependency.

Schedule Links

This section allows for the maintenance of the following information about schedule links for a job. Schedule links are a way to link schedules together where the completion of the job in the current schedule causes the start of execution of the dependent schedule.

• Enabled - Switch to enable or disable the schedule link.

• Job - Name of job belonging to the dependent schedule.

• Process - Name of process containing Job.

• Schedule - Name of the dependent schedule.

• A Remove button is available to delete the schedule link.

Scheduler Administration

The Scheduler Administration screen displays information about the different cycles' Scheduler tasks and allows for their administration.

When an application's batch schedule is first created within POM, Scheduler tasks are created for each of the different cycles as follows:

• One task for Nightly

• One task for each of the recurring flows

• One task for each of the standalone processes

The tasks are all originally created in a disabled state.

An administrator would then access the Scheduler Administration screen to configure all available tasks according to the specific customer's needs.

Nightly Scheduler Task Administration

On the Scheduler Administration screen, the user selects a schedule tile at the top of the screen and the Nightly tab right below the tile. The Nightly cycle's Scheduler task is shown in the tasks table below.

Note:

There is only one Nightly Scheduler task, as there is only one Nightly batch run.

Figure 2-39 Nightly Scheduler Task Administration

The user can either edit the schedule time in-line or select the row, click the edit icon then edit the schedule run time in the Edit Task Nightly popup.

Recurring Scheduler Tasks Administration

On the Scheduler Administration screen, the user selects a schedule tile at the top of the screen then the Recurring tab right below the tile then the hourly flow from the drop down to the right of the Recurring tab. The Recurring flow's Scheduler tasks are shown in the tasks table.

Figure 2-40 Recurring Scheduler Tasks Administration

The user can either edit the schedule time for each task in-line or select a task, click on the edit icon then edit the schedule run time in the Edit Task popup.

Standalone Scheduler Tasks Administration

In the Scheduler Administration screen, the user selects a schedule tile at the top of the screen and the Standalone tab right below the tile. The Standalone cycle's Scheduler tasks are shown in the tasks table.

Figure 2-41 Standalone Scheduler Tasks Administration

The user can either edit the schedule time for each task in-line, or select a task then click the edit icon to change any of the fields shown in the Edit popup below.

The user can also create and delete Standalone tasks.

Note:

The user has the option to enter a blank time as long as a frequency in minutes is entered. This will cause the first occurrence to execute immediately.

Note:

The Prevent start during nightly switch prevents the task from running while the Nightly batch is running. However, it won’t stop a run that is in progress when the Nightly process starts.

Schedule Maintenance

The Schedule Maintenance screen displays information about the batch schedule upgrade results. You can upgrade a batch schedule to a new version through this screen.

Figure 2-42 Schedule Maintenance Tab

1. Batch Tiles - There is a batch tile for each schedule available in Process Orchestration and Management. Select a tile to show the history of the selected schedule's upgrades or available upgrades.

2. Import Latest Schedule - Use this button to upgrade the selected schedule from a spreadsheet. When clicked, a file selector dialog is displayed (not shown).

   The import file is a spreadsheet.

3. Update History Status List - Displays information about each past or available upgrade of the batch schedule. This menu displays the following information for each batch upgrade:

   • Upgrade Status

   • Version

   • Date Upgraded

   • Description

4. Upgrade - Use this button to upgrade the schedule. This button only appears for schedules for which an upgrade available.

5. Retry - Use this button to retry a failed update. This button only appears for schedules that have not completed successfully. The retry will resume the upgrade from the failed step.

6. Cancel - Use this button to cancel the upgrade for an ongoing upgrade as long as it's in stage 4 or less, or to cancel an upgrade in an error state.

   When an ongoing upgrade is canceled, it is marked as Error. The user can then either click the Cancel button again to remove the attempted upgrade so it can be started over, or click the Retry button to resume the upgrade from the failed step.

7. Download files menu - Use this menu to download schedule files. See Download Files for more information.

   

Download Files

Click on the ellipses then select from the download files menu to download files for an upgrade version. This menu has the following options:

• Download Previous Configuration

• Download POM Seed File

Download Previous Configuration

Use the Download Previous Configuration option to download a file containing the specific schedule version configurations. This file is in JSON format.

Download POM Seed File

Use the Download POM Seed File to download an SQL file with POM seed data for the specific schedule version.

Footer

The screen can be set to auto refresh periodically by selecting the pre-defined interval from the Auto Refresh list. By default, this value is set to 30 minutes on page load which means the Auto Refresh is turned off.

Use the Refresh button to refresh the screen immediately.

Last refreshed shows the time and date of the last refresh of the interface.

AMS Utilities

The AMS Utilities are functions performed only by the Oracle administrators.

Select AMS Utilities from the Tasks menu to display the submenu.

The AMS Utilities submenu contains the following tasks:

• Manual Job Run

• Override Job Status

• Override Execution Request Status

Manual Job Run

An Oracle administrator uses the Manual Job Run utility to run a job for a particular schedule from either the Nightly or Hourly cycle. Once the selections are made, the user clicks on Run to submit the job for execution. The user then uses the Batch Monitoring screen to monitor the execution of the job.

Note:

A job that is manually run on this UI is run standalone without regard to dependencies.

Figure 2-43 Manual Job Run

Override Job Status

The next AMS Utility is Override Job Status.

Occasionally, a job in POM gets stuck with a status where manual intervention is needed. This is to reset the status and get the job running for instance. This screen is used for this purpose.

Figure 2-44 Override Job Status

Select the schedule and the cycle to display all jobs for those selections in the Jobs table.

In the table, select the row for the job you intend to override the status for and click the Change Status button or select Change Status from the table's Actions menu. The Change Status popup is displayed.

You are required to enter a comment justifying overriding the job's current status.

Notice the warning message. An administrator needs to understand the impact of overriding the current status as it may lead to data corruption if an unintended action takes place.

Override Execution Request Status

The next AMS Utility is Override Execution Request Status.

Occasionally, a job in the POM's Execution Engine gets stuck with a status where manual intervention is needed. This is to reset the status and get the job running for instance. This screen is used for this purpose.

Figure 2-45 Override Job Execution Status

Select the schedule and the cycle to display all jobs for those selections in the Jobs table.

Select the row in the Details table for which you intend to override the status and click the Change Status button or select Change Status from the table's Actions menu. The Change Status popup is displayed.

You are required to enter a comment justifying overriding the job's current status.

Notice the warning message. An administrator needs to understand the impact of overriding the current status as it may lead to data corruption if an unintended action takes place.