Add complete life-cycle middleware servers (deprecated)
We can configure complete life-cycle middleware servers so that the dynamic operations environment can govern all aspects of server operations, create and remove server instances, and deploy applications to the servers.
Deprecated feature: Assisted and Complete Lifecycle servers have been deprecated in WebSphere Application Server v9.0. Migrate WebSphere Liberty servers to a Liberty Collective configuration. There is no recommended migration action for other server types.depfeat
By configuring complete life-cycle servers, the environment performs the following tasks on the middleware servers:
- Create and remove server instances based on the needs of the dynamic operations environment
- Govern all aspects of server configuration
- Provide operational control over the server
- Deploy applications to the server
- Visualize and monitor server health and performance
- Use expression-based dynamic clustering (for PHP servers, WAS Community Edition servers, and application servers)
On the administrative console, when we select...
-
Servers > All servers > middleware_server > Stop
...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:
- Servers > Server Types > type_of_middleware_server > middleware_server > Stop
- Stop and then start the servers from the command line.
Tasks
Follow the steps to create your complete life-cycle middleware server. The steps vary depending on the server type:
| On demand router (ODR) | The on demand router is a specialized proxy server that can route work to application server nodes. The ODR is required for a Intelligent Management environment. |
| PHP server | Use Intelligent Management to create PHP servers. |
| WAS Community Edition server | Intelligent Management offers assisted and complete life-cycle management for WAS Community Edition servers. Complete life-cycle management is supported for WAS Community Edition v2 and later servers. WAS Community Edition Version 1 and v2 servers can be represented in the administrative console as assisted life-cycle servers. |
| Generic server | Generic servers are managed in, but not supplied byWAS. These servers might be a Java server, a C or C++ server or process, a CORBA server, or a Remote Method Invocation (RMI) server. Read |
| WebSphere Proxy server | Proxy servers, like the ODR, route requests to application server nodes. However, the ODR is the required proxy for dynamic operations. |
| Web server | Intelligent Management works with a web server to route requests for dynamic content, such as servlets, from web applications. |
| Application server | Application servers are supported for both WAS and Intelligent Management. By creating dynamic clusters of application servers, we enable application server virtualization. |
What to do next
We can create dynamic clusters of application servers, WAS Community Edition servers, and PHP servers.
Subtopics
- Create PHP servers and PHP dynamic clusters
- Intelligent Management: PHP server administrative tasks
- Create complete life-cycle WAS Community Edition servers and dynamic clusters (deprecated)
Related: