Workshop Exercise 4.2 - Reviewing End-to-End Deployment
Table of Contents
- Objective
- Step 1 - Confirming the PostSync Job Run
- Step 2 - Investigating the Run Automation in Controller
- Step 3 - Investigating Virtual Machine
Objective
- Confirm the kickoff of the workflow via postSync job
- Validate that Active Directory was installed
Step 1 - Confirming the PostSync Job Run
In addition to the configure-controller job, we also added a job that happens after all resources are synced. This job will kickoff the workflow we specified in the Controller configuration configMap.
In the OpenShift web console, navigate to Workloads > Jobs, where a job named run-automation-in-controller-GENERATED-STRING will now be present:
The output from the pod should look similar to the configure-controller job:
Step 2 - Investigating the Run Automation in Controller
Back in Controller, under Views > Jobs, there should be some new jobs that have been launched, driven by the workflow launch:
Step 3 - Investigating Virtual Machine
To confirm that FT was install, visit the Console for our virtual machine named ad01 and log in using domain credentials:
You should be able to click around and see multiple applications launched. Start with the FTView Client file, picture with a trend, and push the “Start” button, or push the “Stop” botton. If the pictures are “X”d out it’s not communicating with the the Controller (Codesys Group). They may not be ready, or maybe there are other issues.
Next check out the UA Expert application, there you will be able to see how it’s communictating with the PLC.
Finally check out the Codesys IDE deployment. This is the actual program that was created to run the PLC.
Navigation