IBM WebSphere Application Server classic virtual system patterns
Learn about predefined classic virtual system patterns for WebSphere Application Server.
The predefined classic virtual system patterns for WebSphere Application Server provide topologies for supporting web applications that are based on recommended best practices.
Requirements
A configured NTP server that is accessible by your virtual machines is required for your IBM WebSphere Application Server environment to function properly. When classic virtual system patterns are deployed, the NTP server is used to establish the system time for your virtual machines. Without a synchronized date and time, deployment problems can occur including issues with federation, LTPA tokens, and the addNode command. If an NTP server is not used, the system clocks for the appliance and the hypervisors must be synchronized manually. Your classic virtual system instances might have trouble starting because of mismatched time. For information on defining your NTP server in the system settings, see the related links.
Supported versions of WebSphere Application Server
- 8.5.5.24
- 9.0.5.16
- Liberty 23.0.0.8
Available patterns
- Single server classic virtual system patterns
- The following single server classic virtual system patterns come
predefined with Cloud Pak System Software for Power®:
- WebSphere single server
- Cluster classic virtual system patterns
- The following cluster classic virtual system patterns come
predefined with Cloud Pak System Software for Power:
- WebSphere cluster
- WebSphere advanced cluster
- WebSphere cluster (development)
- WebSphere advanced cluster (development)
- WebSphere cluster (large topology)
Important: Both the WebSphere advanced cluster classic virtual system pattern and the WebSphere advanced cluster (development) classic virtual system pattern are available with the WebSphere Application Server 7.0.0.17 with Intelligent Management Pack virtual image.Note: For WebSphere cluster patterns, the WebSphere administrator user ID and password is set to be the same as the non-root user (default isvirtuser), but is a separate entity. If you change the WebSphere administrator password after initial deployment, clone operations on other nodes in the cluster will not succeed. They will fail federation, because the activation script uses the WebSphere administrator password specified at initial pattern deployment.
| Feature | WebSphere advanced cluster | WebSphere advanced cluster (development) | WebSphere cluster | WebSphere cluster (development) | WebSphere cluster (large topology) | WebSphere single server | WebSphere single server with sample |
|---|---|---|---|---|---|---|---|
| IBM HTTP Server | X | X | X | X | X | ||
| Smaller number of nodes | X | X | |||||
| Stand-alone server | X | X | |||||
| IBM HTTP Server is co-located in the same virtual machine as the deployment manager. | X | X | |||||
| IBM HTTP Server is located in a separate virtual machine from the deployment manager. | X | X | X | ||||
| Larger set of nodes | X | ||||||
| ODR | X | X | |||||
| Number of virtual machines | 9 | 4 | 4 | 3 | 15 | 1 | 1 |
- WebSphere advanced cluster
- An IBM WebSphere Application Server Network Deployment topology
with IBM WebSphere Application Server Hypervisor Edition Intelligent Management Pack,
which provides features for larger scale development or production
environments. Important: This classic virtual system pattern is available with the virtual images for WebSphere Application Server Version 7.0.0.21 or Version 8.0.0.3 with Intelligent Management Pack.
- WebSphere advanced cluster (development)
- A WebSphere Application Server Network Deployment topology
with IBM WebSphere Application Server Hypervisor Edition Intelligent Management Pack features
for small scale development environments. Important: This classic virtual system pattern is available with the virtual images for WebSphere Application Server Version 7.0.0.21 or Version 8.0.0.3 with Intelligent Management Pack.
- WebSphere cluster
- A WebSphere Application Server topology for larger scale development or production environments. The IBM HTTP Server is located in a dedicated virtual machine in an unmanaged node.
- WebSphere cluster (development)
- An IBM WebSphere Application Server Hypervisor Edition topology for small scale development environments. The deployment manager and IBM HTTP Server, that is an unmanaged node, are located on the same virtual machine so that fewer virtual machines are required for a deployment.
- WebSphere cluster (large topology)
- A WebSphere Application Server topology
for large-scale environments. The topology consists of a deployment
manager, ten custom nodes with the same properties, and four IBM HTTP Servers.
Scripting programmatically splits the default core group within cells. The default core group is divided if it grows beyond recommended total Java™ processes per core group. Separate core group bridges are defined to connect the new core groups. These bridges adhere to various heap, HAM protocol, and version settings guidelines. One or more IBM HTTP servers are defined, and there is a larger set of nodes in a large topology cluster.
- WebSphere single server
- A WebSphere Application Server topology or part of a WebSphere Application Server Network Deployment topology. The single node can be used for a development environment. It can also be used as part of a multiple node production environment, in which the application configuration is manually duplicated. This classic virtual system pattern contains a WebSphere Application Server under one virtual machine.