Software AG Products 10.11 | Running Business Processes and Composite Applications | webMethods Integration Server Administrator’s Guide | Using Integration Server with Docker | Excluding Web Services Support from a Docker Image for Microservices Runtime
 
Excluding Web Services Support from a Docker Image for Microservices Runtime
The is_container script provides you the option to exclude web services functionality from the Docker image created for a Microservices Runtime. Excluding the web services reduces the size of the Docker image significantly. However, other Microservices Runtime features that rely on web services functionality cannot be used and will not run, specifically:
*Any built-in service that relies upon web services functionality cannot execute. Attempts to run any of the following services result in a ServiceException:
*pub.soap* services.
*pub.utils.ws.setCompatibilityModeFalse.
*pub.client:soapClient.
*pub.client:soapHTTP.
*pub.client:soapRPC.
*pub.trigger:createJMSTrigger, when jmsTriggerType=SOAPJMS.
*SOAP-JMS triggers cannot be created on the Microservices Runtime running in a Docker container. Furthermore, an existing standard JMS trigger already exists cannot be changed to a SOAP-JMS.
*A request to access a WSDL URL or to invoke a web service returns a HTTP status code 404 with the following message: WebServices Support (WebServices) is not available in the installed product.
*Server configuration parameters related to web services functionally have no effect.
*Web services configuration such as web service end point aliases and policies are ignored.
*If a custom package containing web service descriptors is loaded by the Microservices Runtime running in a Docker container, Microservices Runtime partially loads the packages. Assets in the package that rely on web services functionality will not be loaded and cannot be used. Attempts to execute the operations or services in the web service descriptor result in the following message in the server.log: The Web service descriptor webServiceDescriptorName cannot be loaded. WebServices Support (WebServices) is not available in the installed product.
*If a system package that contains web service descriptors or other assets that rely on web services functionality is loaded by o the Microservices Runtime running in Docker container, Microservices Runtime loads the entire package. Attempts to run the operations or services in the web service descriptor result in the following message in the server.log: The Web service descriptor webServiceDescriptorName cannot be loaded. WebServices Support (WebServices) is not available in the installed product.