The following content is displayed on the same screen for your experiment so that you can make any necessary reference in experiment. Start your experiment now!

1. Step one(Duration: 2 mins)
   

   The z/OS Cloud Broker solution provides independent access and deployment capabilities to z/OS resources and services. Application developers can bind z/OS resources and cloud applications together through the Cloud Platform, thereby directly connecting z/OS The integration of resources and Cloud Native applications integrates z-assets into the cloud-native development strategy.
   The laboratory platform is based on Openshift 3.11, and zCEE instances, host applications and openshift front-end applications are automatically deployed through z/OS Cloud Broker. The following is the basic flow chart of this experiment

   

2. Step two(Duration: 3 mins)
   

   1. Use the admin user to log in to the openshift control platform, please confirm that the current project is zoscb, if it is another project, please use the command to switch to zoscb project
   Excuting an order:
   1) oc login -u admin -p admin
   2) oc project zoscb

   

   2. IBM z/OS Cloud Broker acts as a bridge between openshift and host resources, running on the openshift platform architecture in the form of pods. By linking with the zosmf cloud provisioning component, based on the deployed host CICS, DB2 and other subsystem template files, the ability to automatically deploy host resources and services from the cloud platform is realized.

   

   The customized zCEE template file on the host contains various parameters of the zCEE startup address space. for reference:

   

    

3. Step three:在openshift平台执行ansible脚本，部署主机zCEE 应用instance(Duration: 4 mins)
   

   1. Enter your user's script save directory cd /zoscb-lab/test001
   (Note: In order to ensure the experimental environment, the current user cannot cd into other test user directories, and please do not use vi and other commands to modify the yaml file)
   You can first use the cat command to view the details of the deployment script:
   Execute the command: cat test001-provision.yaml

   

   2.The provision script first creates a host zCEE instance through the subscript zosconn-instance1.yaml, and you can use the cat command to view the script details in the current user directory.
   Execute the command: cat /zoscb-lab/test001/zosconn-instance1.yaml

   

   The instance deployment subscript specifies the definition of clusterServiceClass and clusterServicePlan corresponding to zos Cloud Broker.
   3. Establish a servicebinding based on the zCEE instance created in the previous step, and view the servicebinding creation script through the cat command
   Execute the command: cat /zoscb-lab/test001/zosconn-instance1-binding.yaml

   

   4. After checking and confirming the above steps, execute the following ansible script commands in the terminal to create serviceinstance and servicebinding. This step takes 2-3 minutes to execute. Please wait for the script execution to complete, and do not cancel during execution.
   Execution command: ansible-playbook /zoscb-lab/test001/test001-provision.yaml

   

4. Step Four：执行脚本，部署openshift平台应用(Duration: 5 mins)
   

   1. Execute the cat operation to view the content of the openshift platform node.js application deployment script. The node.js application will read the HOSTNAME and PORT from the zCEE instance deployed in the previous step to call the host service Regions.
   Excuting an order:cat /zoscb-lab/test001/node-web-app-test001.yaml

   

   2. Execute the application deployment script, deploy the node.js application on openshifit, and create the corresponding service and pod.
   Excuting an order:oc apply -f node-web-app-test001.yaml

   

   3. Use the oc command to view the deployed service in the previous step and get the front-end node.js application port number
   Excuting an order:oc get service node-app-svc1

   

5. Step Five：通过UI查看应用部署结果(Duration: 5 mins)
   

   Open the Firefox browser and enter http://master.example.com:[nodeJs port number obtained in the previous step].
   That is, you can view the host Region services exposed by the newly deployed zCEE instance on the host side. The specific CICS region displays the country information (China).
   For example: http://master.example.com:32049

   

6. Step 6: Resource recovery(Duration: 6 mins)
   

   1. Run the script to clear the openshift platform node.js application deployed by the user test001 through the script, including the running service and pod. This script takes 1-2 minutes to execute, please do not cancel it halfway.
   Run command:ansible-playbook delete-node-app-test001.yaml

   

   (Note: The red message in the running of the ansible script is because the pod has been deleted and cannot be found and can be ignored)
    

   2. Run the script to deprovision the host zCEE instance and binding deployed by this user test001. This step takes 2-3 minutes, please do not cancel it halfway.
   Run command:ansible-playbook test001-deprovision.yaml

   

   (Note: The red message in the running of the ansible script here is a small bug in openshift, which can be ignored and does not affect the subsequent deprovsion process)
   
   So far, we have realized that based on the openshift platform, through the IBM cloud broker as a bridge, the host zCEE instance is automatically deployed to expose the host CICS service. Through this experiment, we can intuitively experience that through the IBM z/OS Cloud Broker, the services and resources of z/OS can be easily integrated into cloud platforms such as openshift to realize the deployment of host services and resources in a hybrid multi-cloud environment.

Start Your Experiment