Argument | Description |
-Dimage.name= baseImageName | Optional. Base image such as ubuntu or centos:7. Default: centos:7 |
-Dinstance.name= instance_ name | Optional. Integration Server instance to include in the image. Default: default (The instance named default.) |
-Dport.list= ports | Optional. Comma-separated list of the ports on the instance to expose in the image. Default: 5555,9999 |
-Dpackage.list= Wm packages | Optional. Comma-separated list of Wm packages on the instance to include in the image. Default: all (this includes all of the Wm packages and the Default package) |
-Dinclude.jdk={true|false} | Optional. Whether to include the Integration Server JDK (true) or JRE (false) in the image. Default: true |
-Dfile.name= Dockerfile_name | Optional. Filename for the generated Dockerfile. Default: Dockerfile_IS |
-Dtarget.configuration= configuration_name | Optional. Target configuration of Integration Server for which the Dockerfile is being created. If the Dockerfile is for an Integration Server that will be used as the local development server, specify: localdev For more information about using an Integration Server running in a Docker container as the local development server for the local service development feature in , see webMethods Service Development Help. |
Argument | Description |
-Dfile.name= Dockerfile_name | Optional. Filename of the Dockerfile to use to build the Docker image. Default: Dockerfile_IS |
-Dimage.name= Docker_ image_name | Optional. Name for the generated Docker image. Default: is:micro |
Argument | Description |
-Dinstance.name= instance_name | Optional. Integration Server instance that includes the user-defined packages. Default: default (The instance named default.) |
-Dimage.name= Docker_image_name | Optional. Name of the core Integration Server image on which this image should be built. Default: is:micro |
-Dpackage.list= packages | Optional. Comma-separated list of the custom packages to include in the image. Default: all “all” indicates that the image for packages will include all the custom packages on the Integration Server instance. The Default package and packages beginning with “Wm” will not be included in the image. Note: Make sure to include any custom packages containing services that you want to expose to consumers when Integration Server runs in a Docker container in Integration Cloud. If you do not include a package that contains an exposed service a request for the service fails with a service not found error when Integration Cloud redirects the request to the Docker container. |
-Dfile.name= Dockerfile_name | Optional. Filename for the Dockerfile that contains the custom packages. Default: Dockerfile_IS_Pkg |
Argument | Description |
-Dinstance.name= instance_ name | Optional. Integration Server instance that includes the user-defined packages. Default: default (The instance named default.) |
-Dfile.name= Dockerfile_name | Optional. Filename for the Dockerfile that contains the custom packages. Default: Dockerfile_IS_Pkg Docker build uses the file with the specified name located in the packages directory of the specified instance, specifically: Software AG_directory/ Integration Server_directory /instances/instance name/packages/ |
-Dimage.name= Docker_image_name | Optional. Name for the generated Docker image that contains the custom packages. Default: is:microPkg |