Deployments
The Deployments functions support the capabilities required to deploy packages or schedules, view the deployment definitions, and perform a rollback of a deployment.
Deploy
The deploy function is used to deploy a package or a registered schedule definition within the OpCon Deploy system to a registered OpCon system. During the deploy process, the package version or schedule version is selected from the repository, the target OpCon system is selected, optionally, transformation rules can be selected from the repository, an optional description can be inserted, and the definition is then deployed to the target OpCon system.
Deployment supports backward compatibility between OpCon systems 19.0 and 18.3.x. During the deployment process a check is made to determine if the OpCon versions match. If they do not match, a check is made to see if OpCon 19.0 features are present in the definition. If this is the case, the deployment is stopped with an error message indicating the incompatibility.
It is possible to perform the deployment immediately or perform a scheduled deployment at a future date and time.
As part of the Deploy process, it is also possible to perform a Deployment Simulation by selecting Simulation instead of Deploy once the selection process is complete. If the Simulation process completes without any errors, then it is possible to continue with the deployment of the package or schedule.
The Deploy process is divided into two distinct phases with the first phase being the selection phase and the second phase being the deployment phase. The deployment phase consists of the deployment check and the deployment phase.
OpCon Deploy requires that each OpCon Deploy system participating in the OpCon Deploy environment requires a license. To enforce this, a check is made to determine if the requested system has a valid OpCon Deploy license. If the system does not have a valid license, the following message will be displayed:
Deploy Selection Phase
To start the Deploy process, select the deployments Deploy function. The Select a Deployment type dialog will appear so that the deployment type can be selected (Schedule or Package).
The deployment process begins with the selection of the type of deployment. Following that, various dialogs will be presented leading the user through the process.
Schedule Deployment
To deploy a schedule, select the Schedule icon. The Select a Schedule to deploy dialog appears and you will need to select the schedule definition.
The Select a Schedule to deploy dialog presents a screen and a Select capability that allows you to enter a text string to retrieve specific schedule records or use the displayed default value of asterix (*) to retrieve all schedule records. Once the text string has been entered select the Refresh button and the schedule information will be displayed. Subsequent requests will be added to the existing list. It must be noted that wild cards are not supported, instead the text entered in the Name field is checked against the schedule name in the schedule record (i.e. test will return all schedule records that contain the character sequence in the name).
A list of schedule names appears in the upper portion of the dialog. When a schedule is selected, a list of versions available for the schedule appears in the lower table.
Once a schedule has been selected, select the Next button.
Once a schedule has been included in a package, it can no longer be deployed as a separate entity. If a user with administration privileges is logged in, a list of all schedules will be displayed, as there may be exceptional circumstances when a schedule of a package needs to be updated.
Once the schedule has been selected, the next task is to select the target OpCon system to which the schedule will be deployed. It should be noted that the user role of the user will define what OpCon systems are present in the drop-down list. For example, if the user role is Production, then only Production OpCon systems will appear in the list.
Once a target OpCon system has been selected, the user has four options (Next, Simulate, Batch Deploy, or Deploy) to continue the process.
Deployment Server Selection Dialog Options
| Option | Description |
|---|---|
| Next | Select Next if there is a requirement to add transformation rules to the Deployment process |
| Simulate | Select Simulate to perform a deployment simulation, where a check is made to determine if the schedule will deploy without any problems |
| Batch Deploy | Select Batch Deploy to deploy the schedule to the target OpCon system at a future date and time |
| Deploy | Select Deploy to deploy the schedule to the target OpCon system immediately (This is the default option) |
When Next is selected, it will be possible to add transformation rules to the deployment process. It should be noted that it is possible to add a set of transformation rules to a server that will be used for every deployment to that server.
The Select transformation rules dialog presents a screen and a Select capability that allows you to enter a text string to retrieve specific transformation rule records or use the displayed default value of asterix (*) to retrieve all transformation rule records. Once the text string has been entered select the Refresh button and the transformation rule information will be displayed. Subsequent requests will be added to the existing list. It must be noted that wild cards are not supported, instead the text entered in the Name field is checked against the transformation rule name in the transformation rule record (i.e. test will return all transformation rule records that contain the character sequence in the name).
A selection of transformation rules and versions appear in the upper table of the screen. To add a transformation rule, select the rule in the upper table and then select the include arrow. To remove a transformation rule, select the rule in the lower table and the select the remove arrow.
It is then possible to continue by selecting the Next, Simulate, Batch Deploy, or Deploy option.
Deploy Transformation Rule Selection Dialog Options
| Option | Description |
|---|---|
| Next | Select Next and the deployment summary screen will be displayed |
| Simulate | Select Simulate to perform a deployment simulation, where a check is made to determine if the schedule will deploy without any problems - The additional transformation rules will be included in this Simulate check |
| Batch Deploy | Select Batch Deploy to deploy the schedule to the target OpCon system at a future date and time |
| Deploy | Select Deploy to deploy the schedule to the target OpCon system immediately (This is the default option) |
When Next is selected, the Summary dialog appears presenting the sections the user made. It is possible to add a description that will be included in the deployment record, to set the schedule auto build options, to indicate if any existing schedules in the daily must be rebuilt, and if OpCon SAP R3 jobs are encountered, to create the SAP server job definitions. If the checkbox is not selected, then the OpCon SAP R3 jobs will be linked with the existing SAP server job definitions.
When setting the auto build options, first select the Auto Build checkbox and then set the values for Days In Advance and Days. When selecting the Auto Build checkbox, the values are initially set to 1. When not selected, the Auto Build and Auto Delete settings return to the values currently defined on the schedule imported into OpCon Deploy.
To remove the AutoBuild options, select the AutoBuild Checkbox and set the days in advance for and days to 0. To remove the AutoDelete option, select the AutoDelete Checkbox and set the days ago to 0.
If the requirement is to rebuild the existing schedules in the daily after the schedule definition has been deployed, select the Rebuild Schedules in Daily checkbox. When this is selected, all schedules present in the daily from the current date will be rebuilt. During the rebuild process, a check is made to see if the schedules are in an On-Hold condition. If the schedule is in an On-Hold condition the schedule is rebuilt in that condition. A check is also made to see if the schedule in the daily has any schedule instance properties and if schedule instance properties are present, these values are used during the rebuild process instead of the values from the master.
It is then possible to continue by selecting the Back, Simulate, Batch Deploy, or Deploy option.
Deployment Summary Dialog Options
| Option | Description |
|---|---|
| Back | Select Back and go to previous dialogs to alter selections |
| Simulate | Select Simulate to perform a deployment simulation, where a check is made to determine if the schedule will deploy without any problems - The additional transformation rules will be included in this Simulate check |
| Batch Deploy | Select Batch Deploy to deploy the schedule to the target OpCon system at a future date and time |
| Deploy | Select Deploy to deploy the schedule to the target OpCon system immediately (This is the default option) |
Machine Feature Check
If OpCon Deploy is selected, the schedule is then deployed to the target OpCon system. At this point, a check is performed to verify features contained in the deployment match features on a requested machine. If a deployment contains a feature that a requested feature does not have, the deployment will be stopped and Impex will return the following error message:
If there are multiple features missing in a machine, each one will now be displayed.
Since a Batch User ID is required for all jobs, File Watcher v1 is not allowed in OpCon Deploy.
Job Output Parsing v1 and v2 are now treated differently. Job Output Parsing v2 will require v1 to also be present on the machine.
Machine feature checks are also performed during Deployment Simulations. For more information on machine features, refer to Simulate Deployment.
Simulate Deployment
When Simulate is selected, the following checks are completed for production systems:
- A check is made to see if the existing schedule definition on the target system matches the definition that was saved during the previous deployment process. This is done to see if local changes have been made to the definition since the previous deployment.
- A check is done to see if all sub schedules referenced from the new definition are available on the target OpCon system.
- A check is done to see if all machines defined in the new schedule definition are available on the target OpCon system.
- A check is done to see if all machine groups defined in the new schedule definition are available on the target OpCon system.
- A check is done to see if all batch users defined in the new definition are available on the target OpCon system.
- A check is done to see if all external dependencies defined in the new definition are available on the target OpCon system.
- For Windows jobs, machine features are checked for embedded scripts, file arrival, job output parsing, environmental variables, run in command shell and encrypted token support.
- For UNIX jobs, machine features are checked for embedded scripts, file arrival, job output parsing, environmental variables and encrypted token support.
- For IBM i jobs, machine features are checked for file arrival.
The Sample Simulation Report shows a sample of a Simulate report that contains multiple warnings. When warnings are found during a Simulate process, it will not be possible to deploy the Schedule. If no warnings are encountered, a Deploy option will appear next to the Copy To Clipboard option, which can then be used to complete the Deployment process.
Encrypted Tokens
When a schedule containing Windows, UNIX or IBM i jobs with encrypted tokens is selected for deployment, all machines to which these jobs will be deployed are checked to ensure encrypted tokens are supported by the agent. This check is performed when running a simulation of a schedule deployment and the results are included in the Simulation Report when completed (For more information on the list of items checked during simulation, please refer to the Simulate Deployment section).
To verify encrypted token support, perform the process for simulating a deployment. As noted in the Simulate Deployment section, there are multiple checks performed in this process. The simulation verifies that the feature "encryptedTokens.v1" is supported by the agents.
If encrypted tokens are not supported, an error message will be displayed in the report once the simulation has completed.
The encrypted token support check is only performed during a simulation and is not performed for deployments.
For deployments to a primary machine with alternate machines or a Machine Group, each machine must support encrypted tokens to successfully complete the deployment. Machine selection for the job is set in the Job Details:
When Batch Deploy is selected, the Batch Deployment dialog will appear. The user should then select a date using the date selector, select a time from the Time drop-down list, enter their OpCon Deploy Password, and select OK to submit the request. The Time drop-down list consists of hourly values from 00:00 to 24:00. The reason that selection from the list must be made is that the time is appended to value DEP-FRQ- to create the required frequency name when performing the job add function.
Once OK has been selected, a confirmation message will be displayed requesting the user to confirm that the deployment must take place.
When Deploy is selected, a confirmation message will be displayed requesting the user to confirm that deployment must take place.
When OK is selected, the deployment check phase commences. During this phase, a check is made to see if a previous deployment of the schedule definition exists on the target OpCon system by retrieving the schedule.
If a previous deployment is found on the target OpCon system, an action is performed depending on the server type.
If the server type is a production server, a check is performed matching the retrieved schedule definition with the value saved in the previous deployment record to determine if there have been any changes made to the schedule definition since the previous schedule deployment. If a mismatch is encountered, a message will be displayed informing the user that the deployed schedule definition does not match the previous schedule definition.
The user has the option to see the differences by selecting the See Differences button, to abort the deployment by selecting the No button, or continue with the deployment of the new version by selecting the Yes button. It should be noted that any changes will not be lost, as the retrieved schedule definition is stored in the deployment record and can be referenced.
To determine the differences, a JSON compare is performed on the extracted information and the information in the deployment record defined in the deployment information. The path value indicates where the difference is so /scheduleList/0/jobList/0 indicates the first job in the first scheduleList of the JSON definition.
If the server type is a non-production server, a check is performed to see if the schedule definition exists on the target OpCon system. If the schedule definition exists on the system, a message will be displayed informing the user that the schedule definition already exists providing information on when it was deployed and who deployed it. The user has the option to abort the deployment so that it can be determined if the deployment should go ahead or continue with the deployment of the new version. It should be noted that any changes will not be lost as the retrieved schedule definition is stored in the deployment record and can be referenced.
During the deployment of a schedule definition to a target OpCon system, deployment information is added to the start of the Schedule documentation field. This contains information about the deployment and should not be changed. During the Deploy Check phase, this information is extracted from the retrieved schedule definition and used to obtain the deployment record from the repository associated with that deployment. If the deployment information is not found, the following error message will be displayed:
The user has the option to abort the deployment and check why this information is missing or continue with the deployment.
If deployment completes successfully, the following message will be displayed:
If the deployment errors, a message will be displayed informing the user why the deployment errored.
Package Deployment
To deploy a package, select the Package icon. The Select a Package to deploy dialog appears and you will need to select the package definition.
The Select a Package to deploy dialog presents a screen and a Select capability that allows you to enter a text string to retrieve specific package records or use the displayed default value of asterix (*) to retrieve all package records. Once the text string has been entered select the Refresh button and the package information will be displayed. Subsequent requests will be added to the existing list. It must be noted that wild cards are not supported, instead the text entered in the Name field is checked against the package name in the package record (i.e. test will return all package records that contain the character sequence in the name).
A list of package names appears in the upper portion of the dialog. When a package is selected, a list of versions available for the package appears in the lower table.
Once a package has been selected, select the Next button.
Once the package has been selected, the next task is to select the target OpCon system to which the package will be deployed. It should be noted that the user role of the user will define what OpCon systems are present in the drop-down list. For example, if the user role is Production, then only Production OpCon systems will appear in the list.
Once a target OpCon system has been selected, the user has four options (Next, Simulate, Batch Deploy, or Deploy) to continue the process.
Deployment Server Selection Dialog Options
| Option | Description |
|---|---|
| Next | Select Next if there is a requirement to add transformation rules to the deployment process |
| Simulate | Select Simulate to perform a deployment simulation, where a check is made to determine if the package will deploy without any problems |
| Batch Deploy | Select Batch Deploy to deploy the package to the target OpCon system at a future date and time |
| Deploy | Select Deploy to deploy the package to the target OpCon system immediately (This is the default option) |
If the selected server allows transformation rules, click Next to select these rules in the dialog screen and apply them to the deployment. If the server does not allow transformation rules, the transformation rules selection dialog screen will be hidden and the user should select Deploy to begin the deployment process.
Clicking Next when there are no transformation rules selected for the deployment will display the information message "No transformation rules will be applied during this deployment" in the Build options and Summary dialog.
If transformation rules are selected, the result of the deployment depends on the value of the global property setting: "FAIL_IF_TRANSFORMATION_RULES_PRESENT_AND_TRANSFORMATION_DISABLED".
If False – The deployment will succeed but no transformation rules will be applied. A warning message is displayed on the summary screen: "Transformation rules are not allowed for the selected server. No transformation rules will be applied to this deployment."
If True – Sending a deployment to this server is not possible. The transformation rules table will appear but the Deploy and Batch Deploy buttons will be disabled since an attempted deployment would fail. An error message will also be displayed: "Transformation rules are not allowed for the selected server. This deployment will fail."
During deployment, once a server that allows transformation rules has been selected, transformation rules can be selected in the Transformation Rules Selection Dialog (seen below). The Build options and Summary screen includes the list of transformation rules that will be applied during the deployment. It should be noted that it is possible to add a set of transformation rules to a server that will be used for deployment to that server.
As noted in the Transformation Rules topic, the rules are listed in the order of what is applied before initiating deployment. This means the transformation rules will be applied as follows:
- Server Transformation Rules
- Package Transformation Rules
- Deployment Specific Transformation Rules
Overlapping Transformation Rules
The order in which transformation rules are applied is important in the event that one rules overlaps another. Following the order in which transformation rules are applied, if a rule is set for a job at the server level, that rule overrides a transformation rule applying to the job at a lower level. For example:
- Server Transformation Rule – Replace machine'Test1' with machine 'Test2'
- Package Transformation Rule – Replace machine 'Test1' with machine 'Test3'
The rule at the server level to replace machine Test1 with machine Test2 is accepted and applied to the job, and the rule at the package level to replace Test1 with Test3 will be ignored. But, a transformation rule applied at a lower level may overlap a rule that transformed the job at a higher level. Using the above example, adding a Deployment Transformation Rule:
- Deployment Transformation Rule – Replace machine 'Test2' with machine 'Production'
Now, all jobs which were pointing to machine Test1 or machine Test2 are mapped to Production. The Development Transformation Rule has overlapped the other transformation rules.
Transformation rules may be selected from the window in the Build Options and Summary screen. Clicking on a transformation rule from the list opens another window — View Transformation Rules. The fields in this table are not editable:
