WebSphere Application Server Hypervisor Edition Version 8.5.5.1 new features

Content

Before you begin, you must be familiar with the Liberty collective administrative domain. For more information, see Introducing the Liberty collective: A cloud-enabled application server management foundation.

The Liberty controller part implements the Collective controller portion of the Liberty collective. The Liberty host part implements the Collective host and Collective member portions of the Liberty collective.

To build a Liberty pattern, complete the following steps:

Import WebSphere Application Server Hypervisor Edition.

1. Download WebSphere Application Server Hypervisor Edition Version 8.5.5.1 from IBM Passport Advantage.
2. Import Hypervisor Edition into the IBM Workload Deployer Catalog or Pure Application Systems Workload Console Catalog and accept the License agreement.

1. Create a new pattern.
2. Edit the pattern.
3. In the Pattern editor, select the Liberty Controller part and drag it to the Pattern canvas.
4. Select the Liberty Host part and drag it to the Pattern canvas.
5. Edit the Liberty Controller part properties. The IBM Workload Deployer or PureApplication Systems information center has details on all of the common part properties that are found in the WebSphere Application Server Hypervisor Edition parts. The following list is an explanation of specific Liberty controller part properties.
1. Liberty Controller keystore password: The password that is used for inbound HTTPS keystore, inbound HTTPS truststore, server identity keystore, collective trust keystore and the collective root signers keystore.
2. Liberty profile server name: The name of the Liberty profile server that acts as the collective controller server.
3. WebSphere administrative user name/password: The Liberty controller server runs under this userid. Administrative access for the collective controller is defined by this userid and password in the server.xml quickStartSecurity section of the server definition.
6. Edit the Liberty Host part properties.
1. You can select one or more Liberty hosts as part of the pattern. By default, one Liberty host is part of the pattern. If you want more than one Liberty host, increase the number.
2. The IBM Workload Deployer or PureApplication Systems information center has details on all of the common part properties that are found in the WebSphere Application Server Hypervisor Edition parts.
3. WebSphere administrative user name/password property: All Liberty collective members that are pushed out to the host are started and run under this user name.
7. Click done editing.

Deploy a Liberty Collective Pattern.

When you select the pattern you created and click Deploy, the pattern topology deploys. The Liberty Controller part deploys first, then a Liberty collective server is created and started to accept Liberty Host registrations. The Liberty host parts deploy when the Liberty controller starts. The Liberty host parts are registered to the collective controller.

The following changes are made to WebSphere Application Server or Liberty installations during deployment:
• Creates /opt/IBM/WebSphere/Liberty/etc/server.env file with the following two entries:

JAVA_HOME=/opt/IBM/WebSphere/AppServer/java/jre
WLP_USER_DIR=/opt/IBM/WebSphere/Profiles/Liberty

• Updates are made to the WebSphere Application Server JRE java.security file so that Liberty SSL works properly.

In the following files:
/opt/IBM/WebSphere/AppServer/java/jre/lib/security/java.security
/opt/IBM/WebSphere/AppServer/java_1.7_64/jre/lib/security/java.security
The following lines are commented out:
ssl.SocketFactory.provider=com.ibm.websphere.ssl.protocol.SSLSocketFactory
ssl.ServerSocketFactory.provider=com.ibm.websphere.ssl.protocol.SSLServerSocketFactory

• The Liberty Controller server starts when the virtual machine that hosts the controller restarts.


Restrictions.

1. When the Liberty collective pattern deploys, additional Liberty Hosts can be added or removed from the Virtual System instance. On the removal path, the virtual machine that is hosting the Liberty Host is deleted; but remains registered with the Liberty controller.
2. Within the pattern editor, there is no relationship arrow between the Liberty Controller and Liberty Host parts.