Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS
Adding complete life cycle middleware servers
You can 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 can perform 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)
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 aWebSphere Virtual Enterprise environment. See Creating and configuring ODRs for more information.
- PHP server: WebSphere Virtual Enterprise can create PHP servers. See Creating PHP servers and PHP dynamic clusters for more information.
- WebSphere Application Server Community Edition server: WebSphere Virtual Enterprise supplies 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 V2 and later servers. WebSphere Application Server Community Edition V1 and V2 servers can be represented in the administrative console as assisted life cycle servers. See Creating complete life cycle WebSphere Application Server Community Edition servers and dynamic clusters for more information.
- Generic server: Generic servers are managed in, but not supplied by WebSphere Application Server or WebSphere Virtual Enterprise. These servers might be a Java™ server, a C or C++ server or process, a CORBA server, or a Remote Method Invocation (RMI) server. See 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. See Creating proxy servers for more information.
- Web server: WebSphere Application Server and WebSphere Virtual Enterprise can work with a Web server to route requests for dynamic content, such as servlets, from Web applications. See Communicating with Web servers for more information.
- Application server: Application servers are supported for both WebSphere Application Server and WebSphere Virtual Enterprise. See Creating application servers for more information.
What to do next
You can cluster application servers, WebSphere Application Server Community Edition servers, and PHP servers.
Subtopics
Creating PHP servers and PHP dynamic clusters
Creating complete life cycle WebSphere Application Server Community Edition servers and dynamic clusters
Previous topic
Creating and configuring ODRsNext topic
Creating dynamic clusters
Related concepts
Middleware nodes and servers
Supported middleware server types
Related tasks