Server bundle overview

A server bundle isolates the workload processes so that they can be independently managed.

A pod can be composed of one or more server bundles. The server bundles in a pod share the same database, network interface, storage volume, and resources, such as CPU and memory.

You can specify the following server bundle parameters to configure the deployment:

Name

The user-defined name for the server bundle. You can also specify whether the server bundle is the default server bundle. For both values, ensure that all is specified.

Pod count

The number of pods to deploy for the server bundle. Ensure that 1 is specified.

Type

The type of the server bundle. Ensure that all is selected.

Additional server properties

As an option, you can add the following properties:

Route subdomain

If you specify a subdomain, it is added as a prefix to the main domain when the route is created for the server bundle.

Additional server configurations

To configure the WebSphere® Application Server Liberty application server, you can provide custom parameters, as shown in the following example:

  server-custom.xml: |-
    <!-- Enable features -->
    <featureManager>
        <feature>jsp-2.3</feature>
    </featureManager>

    <!-- To access this server from a remote client add a host attribute to the following element, e.g. host="*" -->
    <httpEndpoint id="defaultHttpEndpoint"
                  httpPort="9080"
                  httpsPort="9443" />
    <!-- Automatically expand WAR files and EAR files -->
    <applicationManager autoExpand="true"/> 

Bundle-level properties

To add Maximo® Health system properties to specific server bundles, you can specify property names and values when you deploy the application.