Are you familiar with docker-compose in the Workload Automation (WA) deployment process?

It’s about time you started using it to deploy Workload Automation containers.

The 3 “S” joint venture of WA, along with Docker Compose, stand by the following slogans:

 

  • Simplicity?!?!?!? Not more than 5 steps ………….
  • Speed?!?!?!? Just enough time for a coffee break …….
  • Security?!?!?! No worries, we take care of everything ………

Let’s start the 3 “S” adventure!

 

1. If you are an IBM customer retrieve your IBM entitled key to access the IBM Entitled Registry or request a new one. To request a new one, see https://github.com/WorkloadAutomation/ibm-workload-automation-docker-compose/blob/master/README.md.

If you are an HCL customer, ask to your Sales representative for a HCL entitled key. For more information, see
https://github.com/WorkloadAutomation/hcl-workload-automation-docker-compose/blob/master/README.md.

 

2. If you are an IBM customer, log in to the IBM Entitled Registry and look for the most recent WA docker images:

docker login -u cp -p <your_IBM_entitled_key> cp.icr.io

 

You should find entries similar to the following in the IBM Entitled Registry:

cp.icr.io/cp/ibm-workload-automation-agent-dynamic:9.5.0.02.20200727

cp.icr.io/cp/ibm-workload-automation-server:9.5.0.02.20200727

cp.icr.io/cp/ibm-workload-automation-console:9.5.0.02.2020072

 

If you are an HCL customer, log in to the HCL Entitled Registry and look for the most recent WA docker images:

docker login -u <your_username> -p <your_HCL_entitled_key> hclcr.io

 

You should find entries similar to the following in the HCL Entitled Registry:

hclcr.io/wa/hcl-workload-automation-agent-dynamic:9.5.0.02.20200727

hclcr.io/wa/hcl-workload-automation-server:9.5.0.02.20200727

hclcr.io/wa/hcl-workload-automation-console:9.5.0.02.20200727

 

  1. Clone the Workload Automation public Docker Compose repository on your machine by running:

 

IBM:

git clone https://github.com/WorkloadAutomation/ibm-workload-automation-docker-compose.git

or

HCL:

git clone https://github.com/WorkloadAutomation/hcl-workload-automation-docker-compose.git

 

Otherwise, if you do not have Git installed on your machine, download the zipped file from the main page of the repository by clicking “Code” and select “Download zip file”.

 

  1. Customize the WA container installation parameters as required by modifying them in your local docker-compose.yml
  2. Accept the license in env and, additionally, for HCL customers only, set the Flexera License ID.
  3. To start the WA containers, from the directory where the docker-compose.yml file has been cloned, run the following command:

 

docker-compose up –d

 

And that’s it! Now go have a coffee while the WA containers get up and running, and by the time you’re done, they’ll be ready to use …………

 

If you’re curious, then try it out and become a 3 “S” joint venture sponsor user!

Author’s Bio

Davide Malpassini, Workload Automation Technical Lead

Davide joined HCL in September 2019 as the  Technical Lead working on the IBM Workload Automation product suite. He has 14 years of experience in software development and was tasked with the extension of the Workload Automation product from a Kubernetes native environment to the Red Hat OpenShift Container Platform, and the  REST API for the Workload Automation engine. He has a Master’s Degree in Computer Engineering. Linkedin: https://www.linkedin.com/in/davide-malpassini-71b25582/

 

 

 

Serena Girardini, UX Manager for Workload Automation

Serena is the Test and UX manager for the Workload Automation product in distributed environments. She joined IBM in 2000 as a Tivoli Workload Scheduler developer and she was involved in the product relocation from the San Jose Lab to the Rome Lab during a short-term assignment in San Jose (CA). For 14 years, Serena gained experience in Tivoli Workload Scheduler distributed product suite as a developer, customer support engineer, tester and information developer. She covered for a long time the role of L3 fix pack release Test Team Leader and, in this period, she was a facilitator during critical situations and upgrade scenarios at customer sites. In her last 4 years at IBM, she became IBM Cloud Resiliency and Chaos Engineering Test Team Leader. She joined HCL in April, 2019 as an expert Tester and she was recognized as the Test Leader for the product porting to the most important Cloud offerings in the market. She has a Bachelor’s Degree in Mathematics. Linkedin: https://www.linkedin.com/in/serenagirardini/

 

Louisa works, Information Developer, Workload Automation

Louisa is an Information Developer planning, designing, developing, and maintaining customer-facing technical documentation and multimedia assets.  Louisa completed her degree at University of Toronto, Canada, and currently lives in Rome, Italy.

Linkedin: https://www.linkedin.com/in/louisa-ientile

 

 

Pasquale Peluso, Workload Automation Software Engineer

Pasquale joined HCL in September 2019 as a member of the Verification Test team. He works as verification tester for the Workload Automation suite on distributed and cloud-native environments. He has a Master’s Degree in Automation Engineering.

Linkedin: https://it.linkedin.com/in/pasqualepeluso

 

 

Filippo Sorino, Software Developer

Filippo joined HCL in September 2019 as a Junior Software Developer working as a Tester for the IBM Workload Automation product suite.  He has a Bachelor’s Degree in Engineering.

Linkedin: https://www.linkedin.com/in/filipposorino

 

 

Federico Yusteenappar, Workload Automation Junior Software Developer

He joined HCL in September 2019 as Junior Software Developer working as a Cloud Developer for the IBM Workload Automation product suite. His main focus was the extension of the Workload Automation product from a Kubernetes native environment to the Red Hat OpenShift Container Platform. He has a Master’s Degree in Computer Engineering.

Linkedin: www.linkedin.com/in/federicoyusteenappar

 

Comment wrap
Further Reading
article-img
Automation | February 9, 2021
Automate Anything, Run Anywhere, starting from the Workload Automation Test environment!
Automate anything, Run Anywhere is our motto!What better place to start making it real than from our very own Workload Automation test environment?We have been applying it in our Test Lab for Workload Automation version 9.5 since its general availability in 2019, and to all the subsequent fix packs, including the last one, fix pack 3.
article-img
Automation | February 1, 2021
How to move your Workload Automation on-premises deployment to cloud
To improve productivity and to save IT management costs and time, our customers are starting to move to the cloud environment and are moving heavy workloads from a set of on-premises machines to a resilient cloud infrastructure. So, our principal mission is to facilitate, secure, and support moving a workload automation deployment, from an on-premises infrastructure (minimum WA 95 FP3 version required) to any cloud infrastructure where Workload Automation (WA) is already supported.Link for the video guide: https://youtu.be/7AQHgCnpqLc
article-img
Automation | January 14, 2021
Safeguarding Carryforwards during a Migration to WA 9.5
A question which everyone would have in mind while Upgrading to WA 9.5 is to manage all the Carryforwards that are present in old Production Plan on the older Version of the Master and to migrate them to the newer Master Server . This Blog aims to sort this problem once and for all to ensure seamless transition to IWS 9.5 without any hassles .As you would already know if you are reading this Blog that WA 9.5 comes with a whole set of New Features and most noticeable Change Architecturally is to move to Liberty as a Middleware in place of Websphere Application Server, JazzSM for both the Engine as well the DWC Profile.
Close