![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
Adding assisted lifecycle middleware servers (deprecated)
By configuring assisted lifecycle middleware servers, you can manage representations of externally created middleware servers that were created outside of the administrative domain.
Before you begin

Read about adding middleware servers to configurations for information about installing the node agent on nodes, and federating those nodes into the configuration.
About this task
- Apache Tomcat
- JBoss Application Server
- Custom HTTP servers
- BEA WebLogic Server
- WebSphere Application Server Community Edition
- Apache HTTP Server
- External WebSphere application server (application servers that run outside the Intelligent Management cell)
- Liberty profile server
- Apache Tomcat
- BEA WebLogic
- JBoss
- External WebSphere application server (application servers that run outside the Intelligent Management cell)

Error xdblade31b04/WASMaintModeDC1_xdblade31b04 has not been started.
The
server cannot be stopped from this page when this situation occurs. - Click Stop for a middleware server that displays a status of Started. . Then click
- 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 administrative console. 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 the WebSphere Application Server Community Edition console. Make any representative changes in the administrative console.
Procedure
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 lifecycle 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 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), you 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 administrative console.