Adding assisted life-cycle middleware servers

By configuring assisted life-cycle middleware servers, you can manage representations of externally created middleware servers that were created outside of the administrative domain.

Before you begin

See Adding middleware servers to configurations for information about installing the middleware agent on nodes and federating those nodes into the configuration.

About this task

With assisted life-cycle middleware servers, you can create a representation of the server in the administrative console. The middleware agent provides the information that WebSphere Virtual Enterprise needs to manage these servers. You can configure the following assisted life-cycle middleware server types:

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

Procedure

  1. Create a representation of the middleware server in the administrative console.
    1. Add an existing server. In the administrative 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 the middleware agent or a node agent. Create a name for the server that is unique among all servers in the cell.
    3. Specify the server template that you want to use for the middleware server.

    4. Click Finish.
    5. Click Save to save your 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 your 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, you can specify the username and password that is required to start and stop the servers in the middleware server.
  3. Start the middleware server. In the administrative console, click Servers > All servers. Select the server that you want to start and click Start. The start server operation that is defined for the server runs.
    Note: If the middleware 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

You can create a middleware server template that is based on your configured server. After you create a middleware server template, you can create additional servers using the template, which creates servers with the same settings as your 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 life-cycle middleware servers, you group together the representations that you created. These servers must have the same applications installed.

The logs and trace views in the administrative console are not supported for assisted life-cycle middleware servers. Configure the external log viewing service to view the log files for these server types in the administrative console.


The URL for this topic is: