Introduction

The Deployment History is available from the Deployment sub-view of the JS7 - History view. The view displays objects that have been deployed to connected Controllers.

Deployment History View

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

Explanation:

• The view supports filters for frequently used date ranges. For longer periods the Advanced Filter is offered.
• The deployment status per object is displayed 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:

Explanation:

• Deployment of job scheduling objects is performed from JOC Cockpit to Controllers and Agents.
• Deployment operations are performed in an asynchronous manor.
  • This results in the fact that some time after a user deployed an object an asynchronous event arrives to confirm if a deployment was successful or not.
  • For example, if a Controller or Agent is not available then this does not prevent deployment of objects. Instead the deployment operation is 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 use of JS7 - Resource Locks that have not previously been deployed.
• Consider that in case of failed deployment any objects included with the deployment operation are denied by the Controller. This means deployment is a transactional operation that is either performed completely or is rolled back.

Advanced Filter

The Advanced Filter offers to search for deployments in past periods.