Add middleware servers to configurations - Intelligent Management
Using middleware servers, we can manage all of the servers in the environment, including servers that are not created with Intelligent Management, using the product administrative domain.
If we are configuring representations in the domain of externally created middleware servers, perform the following tasks on the nodes:
- Install and configure the middleware software on the nodes.
- The node agent on each node must be at the same fix pack level as the deployment manager.
- Federate nodes to an Intelligent Management cell.
- Create and configure ODRs.
- Each of our nodes must have the same network view for each endpoint and resource that is related to WebSphere Application Server. All host entries or host alias entries related to WAS within a hosts file must be included in the hosts file on each of the other nodes in the configuration, including any hosts file on nodes that run the node agent. For example, if we define a product-related host alias called xdagentA in the hosts file for the nodeA node, then the hosts file on each middleware node must contain an entry for the xdagentA host alias.
Middleware servers encompass all servers in the middleware tier that provide the infrastructure for applications or their data. The steps vary depending on if we are configuring complete lifecycle management middleware servers or assisted lifecycle management middleware servers.
Deprecated feature: Assisted and Complete Lifecycle servers have been deprecated in WAS v9.0. Migrate WebSphere Liberty servers to a Liberty Collective configuration. There is no recommended migration action for other server types.depfeat
Tasks
- Complete lifecycle servers include any servers that the environment can instantiate, or create. These server types include WAS types such as application servers, generic servers, Web servers, and proxy servers. The product adds complete lifecycle management for PHP servers and WAS Community Edition servers. See adding complete lifecycle middleware servers.
- With assisted lifecycle servers, we use templates to create representations of servers. However, these servers still exist within the administrative domain of their respective middleware platform. These servers can be controlled operationally. Server health and performance are monitored. We can configure the administrative console to display log files and configuration files for these servers. See adding assisted lifecycle middleware servers.
What to do next
To easily manage groups of servers to host an application, configure dynamic clusters. We can create clusters of either type of server. However, dynamic application placement is supported only on complete lifecycle servers. When we create a dynamic cluster of assisted lifecycle middleware servers, the same version of middleware software and the same applications must be installed on the servers. If the servers in a dynamic cluster have varying sets of applications installed, routing through the on-demand router might result in failed requests.
The logs and trace views in the administrative console that we access by clicking Troubleshooting > Logs and trace are not supported for externally created middleware servers and PHP servers. We can use the external log viewing service to view the log files for these server types in the administrative console. To configure the external log viewing service, navigate to the configuration panel for the server and click External log service.
Subtopics
- Intelligent Management: middleware server creation administrative tasks
- Intelligent Management: middleware application administrative tasks
- Intelligent Management: node agent custom properties
- Add complete life-cycle middleware servers (deprecated)
- Add assisted lifecycle middleware servers (deprecated)
- Manage middleware servers
Related: