Adding complete life-cycle middleware servers

You 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.

About this task

By configuring complete life-cycle servers, the environment performs the following tasks on your 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, WebSphere® Application Server Community Edition servers, and application servers)

Avoid trouble: On the administrative console, when you select Servers > All servers > middleware_server, and then click Stop for a middleware server that displays a status of Started, you 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.

Procedure

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 aIntelligent Management environment. Read about creating and configuring ODRs for more information.
PHP server: Use Intelligent Management to create PHP servers. Read about creating PHP servers and PHP dynamic clusters for more details.
WebSphere Application Server Community Edition server: Intelligent Management offers assisted and complete life-cycle management for WebSphere Application Server Community Edition servers. Complete life-cycle management is supported for WebSphere Application Server Community Edition Version 2 and later servers. WebSphere Application Server Community Edition Version 1 and Version 2 servers can be represented in the administrative console as assisted life-cycle servers. Read about creating life-cycle servers and dynamic clusters for more information.
Generic server: Generic servers are managed in, but not supplied byWebSphere Application Server. 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 about creating generic servers for more information.
Proxy server: Proxy servers, like the ODR, route requests to application server nodes. However, the ODR is the required proxy for dynamic operations. For more information read about creating proxy servers.
Web server: Intelligent Management works with a web server to route requests for dynamic content, such as servlets, from web applications. Read about communicating with web servers for more information.
Application server: Application servers are supported for both WebSphere Application Server and Intelligent Management. By creating dynamic clusters of application servers, you enable application server virtualization. Read about creating application servers for more information.

What to do next

You can create dynamic clusters of application servers, WebSphere Application Server Community Edition servers, and PHP servers.