...

• For information about deployment steps consider refer to JS7 - Deployment of Scheduling Objects.
• For underlying security requirements see JS7 - Secure Deployment .of Scheduling Objects.

Deployment History View

The view displays shows deployments, i.e. the point in time when one or more objects have been deployed to one or more Controllers.

...

• The view supports filters for frequently used date ranges. For longer periods the Advanced Filter is offeredprovided.
• The deployment status per object is displayed for individual objects is shown as either being deployed or not deployed.

Users can combine the status filter buttons such as Not Deployed with a date range button to identify failed deployments:

...

• Deployment of job scheduling objects is performed from JOC Cockpit to Controllers and Agents.
• Deployment operations are performed in an asynchronous manormanner.
  • This results in from the fact that some time after a user has deployed an object an asynchronous event arrives will arrive to confirm if a the deployment was successful or not.
  • For example, if a Controller or Agent is not available then this does will not prevent deployment of objects. Instead the deployment operation is will be queued and will be performed as soon as the components are available.
• Failed deployments can occur if dependent objects have not been deployed, for example if JS7 - Workflows makes make use of JS7 - Resource Locks that have not previously been deployed.
• Consider Note that in case the event of a failed deployment any , all objects included with the deployment operation are will be denied by the Controller. This indicates that is because deployment is a transactional operation that is either performed completely or is rolled back.

Advanced Filter

The Advanced Filter offers to search allows searching for deployments in past periodsthe past as shown in the following screenshot: