Containers

Integration Cloud allows you to package existing webMethods Integration Server services as images or repositories and upload them on Integration Cloud using the Docker CLI. You can create and upload images by running the is_container scripts available with the Integration Server installation from Integration Server_directory/docker, store the images in a registry on Integration Cloud, and manage those images from the Integration Cloud user interface. Images or a repository can be versioned or labeled using tags, that is, a tag is a label applied to an image or a repository. Tags help you to distinguish various images or repositories.

Images are read-only templates from which containers are instantiated, that is, a container is a runtime instance of an image. A container also consists of an execution environment and a standard set of instructions. After uploading an image on Integration Cloud, you can create and launch services from the image/tag to the desired stage, specify the number of containers and the container port for each service, and see details of the running instances. A service can contain one or more containers and is defined as a named group of containers created out of a single image tag.

Note:

Universal Messaging (UM) can now be run as a container in Integration Cloud. For creating the UM Docker images supported by Integration Cloud, you must run the Integration Cloud UM script to modify the base image before it is uploaded into Integration Cloud.

You can access containers if you have the Settings > Access Profiles > Administrative Permissions > Container > Access permission. You can administer containers if you have the Settings > Access Profiles > Administrative Permissions > Container > Administer permission. On the Settings > Access Profile > Container tab, enter the names of the webMethods Integration Server Access Control List (ACL) groups separated by a comma, for example, Administrators, Developers, and so on. Users who are assigned to this Access Profile will also be now part of the Integration Server container user group (s) and can perform tasks allowed for those user groups. Note that Integration Cloud Administrator profiles are not automatically assigned to the Integration Server Administrators ACL group. If you do not map an Access Profile to an Integration Server group, you will not be able to invoke Integration Server services.

Note:

You must enable CSRF Guard and configure the CSRF guard settings in webMethods Integration Server Administrator before you create the Docker image and upload it to Integration Cloud. Enabling the CSRF security feature will prevent CSRF attacks. See the webMethods Integration Server Administrator’s Guide on the Software AG Documentation website at http://documentation.softwareag.com for more information.

You can use the Docker Command Line Interface (CLI) to perform the following tasks:

Log in to the system: #docker login -u <username> -p <password> https://<subdomain>.<domain.com>/, for example, docker login -u x@x.com -p test123 https://john.wmic1.com/.

Tag an image or repository: #docker tag <imagename>:<tagname> <subdoamin.wmis.com>/<subdomain>/<stage name>/<image-name>:<tag-name>, for example, #docker tag is_912:withkeystore john.wmic1.com/john/development/is_912:withkeystore2.

Push or upload an image or repository: #docker push <subdoamin.wmis.com>/<subdomain>/<stage name>/<image-name>:<tag-name>, for example, #docker push john.wmic1.com/john/development/is_912:withkeystore2.

Pull or download an image or repository: docker pull <subdoamin.wmis.com>/<subdomain>/<stage name>/<image-name>:<tag-name>, for example, #docker pull john.wmic1.com/john/development/is_912:withkeystore2.