Add assisted lifecycle middleware servers

By configuring assisted lifecycle middleware servers, we can manage representations of externally created middleware servers that were created outside of the administrative domain.

Read about adding middleware servers to configurations for information about installing the node agent on nodes, and federating those nodes into the configuration.

With assisted lifecycle middleware servers, we can create a representation of the server. The node agent provides the information that Intelligent Management needs to manage these servers. We can configure the following assisted lifecycle middleware server types:

  • Intelligent Management support for using the following server types is stabilized:

    • Apache Tomcat

    • BEA WebLogic

    • JBoss

    • External WebSphere application server (application servers that run outside the Intelligent Management cell)

    Avoid trouble: On the console, when you select Servers > All servers > middleware_server, and then click Stop for a middleware server that displays a status of Started, we can intermittently receive an error. The following message is an example of the error:

      Error xdblade31b04/WASMaintModeDC1_xdblade31b04 has not been started.

    The server cannot be stopped from this page when this situation occurs.

    As a work-around, complete one of the following actions to stop the started middleware server:

    • Click Servers > Server Types > type_of_middleware_server > middleware_server. Then click Stop for a middleware server that displays a status of Started.

    • Stop and then start the servers from the command line.


    After you install the node agent on WebSphere Application Server Community Edition nodes and federate the nodes, middleware discovery can automatically create representations of these servers in the console. You do not need to perform the manual steps to create the representation of the server in the console. We can continue to manage these servers in the WAS Community Edition console. Make any representative changes in the console.

    1. Create a representation of the middleware server.

      • If we use wsadmin scripting commands:

      • If we use the console.

        1. Add an existing server.

          In the console, click Servers > Add a server and select Add an existing server.

        2. Select the node on which the middleware server that you are configuring runs.

          The node must be running a node agent. Create a name for the server that is unique among all servers in the cell.

        3. Specify the server template to use for the middleware server.

        4. Click Finish.

        5. Click Save to save the changes to the master configuration.

    2. Perform additional configuration steps for the middleware server, including adjusting the values for the WebSphere variables for each server type and configuring server operations to stop and start the servers:

      The WebSphere variables define settings for the middleware server such as the installation location and vary depending on the middleware server type. By editing the server start and stop operations, we can specify the username and password required to start and stop the servers in the middleware server.

    3. Start the middleware server.

      The start server operation defined for the server runs.

      If the node agent and the server are stopped at the same time, the last known status of the server is reported. Because the last known status is reported as started, the on-demand router (ODR) tries to route to the server.

    What to do next

    We can create a middleware server template based on the configured server. After creating a middleware server template, we can create additional servers using the template, which creates servers with the same settings as the original server.

    To easily manage groups of existing servers to host an application, configure dynamic clusters. By configuring a dynamic cluster, the product can adjust the number of running servers to meet the application service policy. For assisted lifecycle middleware servers, you group together the representations created. These servers must have the same applications installed.

    The logs and trace views in the console are not supported for assisted lifecycle middleware servers. For Apache Tomcat servers, BEA WebLogic servers, JBoss servers, Liberty profile servers, and external WebSphere application servers (application servers that run outside the Intelligent Management cell), we can view logs for these middleware servers on the machines that host them. For other assisted lifecycle middleware servers, configure the external log viewing service to view the log files in the console.


    Related concepts

  • Middleware nodes and servers

    Related tasks

  • Add middleware servers to configurations
  • Configure external WebSphere application servers
  • Create dynamic clusters
  • Configure the external log viewing service
  • Configure middleware server operations
  • Configure Apache Tomcat servers
  • Configure BEA WebLogic servers
  • Configure JBoss servers

  • Configure Liberty profile servers
  • Configure assisted life-cycle WebSphere Application Server Community Edition servers
  • Create middleware server templates