This project demonstrates how to build docker images using Command Central Docker Builder.
Command Central Docker Builder is an tool provided by Software AG on Docker Store. It leverages Command Central templates to run provisioning operations during Docker image build, driven from a standard Dockerfile.
Login to Docker Store with your Docker ID, open https://store.docker.com/images/softwareag-commandcentral and accept license agreement to get access to Command Central images.
Login to Docker with your Docker ID from your console and verify you can download the images:
docker login
docker pull store/softwareag/commandcentral:10.1.0.1-serverModify init.yaml to configure product and fix repositories, poiting to Master 10.1 repostories on Empower using your Empower credentials or point to your local 10.1 mirrors
product:
products:
location: http://sdc.softwareag.com/dataservewebM101/repository/
username: [email protected]
password: yourpass
fix:
fixes:
location: http://sdc.softwareag.com/updates/prodRepo
username: [email protected]
password: yourpassAdd your 10.1 webMethods Microservices Container license file to the current folder as licenseKey.xml file.
To build images using Command Central composite template run
docker-compose buildSee template.yaml for basic webMethods Microservices Container (MSC) runtime instance definition.
There are 3 flavors of images:
- Simple - easy way to build images
- Unmanaged - customized image without SPM management agent
- Managed - customized image with SPM management agent
Check image sizes:
docker imagesStart Command Central container first
docker-compose run --rm initStart all 3 types of containers we just built:
docker-compose up -dWait up to 2 minutes and access them as:
- Simple - http://0.0.0.0:5551/
- Unmanaged - http://0.0.0.0:5552/
- Managed - http://0.0.0.0:5553/
Login as Administrator/manage
There is no size optimization for this image but it is the easiest to build. Suitable for ad-hoc testing.
Simple image comes with SPM and thus can be managed in Command Central.
Unmanaged image does not include management agent (SPM) and thus cannot be managed by Command Central, but can be managed by an orchestration tool of your choice.
Managed image includes Command Central agent (SPM) and thus:
- You can monitor, administer and even configure it in Command Central
- And still manage by an orchestration tool of your choice
Open Command Central to see simple and managed containers in the maganed landscape.
You can run tests against them using Command Central API:
docker-compose run --rm testTail the logs if you need to
docker-compose logs -fdocker-compose downCommand Central Docker Builder 10.1 has the following requirements for the template.yaml:
- The template alias MUST be container, e.g.
alias: container - The template MUST use repositories named products and fixes to match those defined in
init.yamlfile - There MUST be no required parameters in the template. All parameters MUST have default values
- The template MUST provision the layer(s) to the
localnode alias
See the difference between adopted template.yaml and original template.yaml for MSC basic template.
The above limitations are planned to be removed in the upcoming Command Central Builder release to allow seamless use of the same templates for VMs and containers
Your Docker build runs on Windows and fails, ensure that git client uses UNIX crlf instead of Windows. Change git configuration and re-clone the repository
git config --global core.autocrlf falseContact us at TECHcommunity if you have any questions.
DISCLAIMER These tools are provided as-is and without warranty or support. They do not constitute part of the Software AG product suite. Users are free to use, fork and modify them, subject to the license agreement. While Software AG welcomes contributions, we cannot guarantee to include every contribution in the master project.