Configuring WebSphere eXtreme Scale for the Liberty profile on z/OS operating systems

After you install Liberty for z/OS operating systems, you can configure the Liberty server to run your WebSphere® eXtreme Scale applications.

Before you begin

Install the Liberty profile on your z/OS® operating system. To complete the installation for WebSphere eXtreme Scale, see the information about the Liberty and the UNIX Shell.

About this task

Complete the steps in this task after you have successfully create the Liberty server.xml file. When you successfully create the server.xml file with the server create server1 command, output similar to the following example is displayed:
Server server1 created.

Procedure

  1. Open the server.xml file in the wlp_install/usr/servers/server1/ directory.
    When you run the command server create server1, the server.xml file is created and contains the following configuration:
    <server description="new server">
    <!-- Enable features -->
    <featureManager>
    <feature>jsp-2.2</feature>
    </featureManager>
    
    <httpEndpoint id="defaultHttpEndpoint"
    host="localhost"
    httpPort="9080"
    httpsPort="9443" />
    </server>
  2. Enter the following command to start the Liberty server:
    server start server1
    When the server starts successfully, the output that is similar to the following example is displayed:
    Server server1 started with process ID 67371533.
    You have created and started your first Liberty server instance. By default, that server listens on localhost:9080. The server uses user identity.
  3. Enable the eXtreme Scale server feature in the Liberty.
    Modify the server.xml file to configure a catalog server with default settings. Use the following attributes in the server.xml file, which tells eXtreme Scale to create a catalog and container server:
        <!-- Enable features -->
        <featureManager>
            <feature>eXtremeScale.server-1.1</feature>
        </featureManager>
    
        <xsServer isCatalog="true" />
    
        <logging traceSpecification="*=info" maxFileSize="200" maxFiles="10" />
    
    </server>
    Note: A container server is started automatically when an objectgrid.xml file and a deployment.xml file are located in the grids folder.

    For more information about other supported features, see Data caching and the Liberty profile.

    The Liberty dynamically detects and applies the changes that you made to the server.xml file. Monitoring for changes and dynamic updates are advantages of running eXtreme Scale applications in the Liberty.
  4. Verify that the server started.
    Browse the wlp_install/usr/servers/server1/logs/messages.log ASCII file, which contains the following message, if the server started successfully:
    The server server1 has been launched.
    :
    TCP .. is now listening for requests on host localhost (IPv4: 127.0.0.1) port 9080.
    Monitoring dropins for applications.
    Feature update completed in n.nnn seconds.
    The server server1 is ready to run a smarter planet.
    Starting server configuration update.
    The server configuration was successfully updated in n.nn seconds.
    TCP .. stopped listening for requests on host localhost (IPv4: 127.0.0.1) port 9080.
    TCP .. started and is now listening for requests on host * (IPv4) port 9080.

What to do next

To begin running eXtreme Scale in the Liberty, you must start container and catalog servers for the data grid. For more information, see Starting and stopping secure servers in the Liberty profile.