Installing WebSphere Application Server advanced options and sample patterns

Answer

About the advanced options

When you edit the WebSphere Application Server topology of a virtual system pattern, you can configure advanced functionality for the virtual system pattern by using the advanced options.

The available options depend on the topology of the virtual system pattern that you are editing. For virtual system patterns that contain only a stand-alone server part, you can enable session persistence and global security. For virtual system patterns that contain a deployment manager and a custom node, you can enable clusters, session persistence, and global security.

The following image shows the options for cluster virtual system patterns:

defaultdata_softlayer.zip

• The PureApplication Service command-line tooling is used to install the advanced options and create the sample patterns. For more information about setting up the command-line interface, see the IBM PureApplication System documentation in IBM Knowledge Center.
• If the wget command is present, the script attempts to download the command-line tooling from the PureApplication Service.
• To create the WebSphere Application Server sample patterns, WebSphere Application Server Hypervisor Edition must be imported into the virtual image catalog, and the license must be accepted.
• To install the advanced options and create sample patterns, you must have administrative authority to create patterns and scripts.
• Running within a cgywin shell is not supported.

1. Create a work directory. This example uses a directory called /tmp/WHVscripts.
2. Extract defaultdata_softlayer.zip to the /tmp/WHVscripts directory.
3. Change to the /tmp/WHVscripts directory.
4. To make the defaultdata.sh script executable, run the following command: chmod 775 defaultdata.sh
5. Run the defaultdata.sh script from the /tmp/WHVscripts directory using the following syntax:

./defaultdata.sh PureApp_systemName  PureApp_UI_userid  PureApp_UI_password 2>&1 > defaultdata.log

1. Create a work directory to contain the command-line tooling and the code in the defaultdata_softlayer.zip file. This example uses a directory called /tmp/WHVscripts.
2. Download the command-line tooling from one of the following locations and save the files to the /tmp/WHVscripts directory:
• Download the tooling directly from https://PureApp_systemName/downloads/cli, where PureApp_systemName is the fully qualified domain name of your PureApplication Service.
• From the Welcome tab in IBM PureApplication System, click Download tooling.
3. Extract the tooling to the /tmp/WHVscripts directory.
4. Extract defaultdata_softlayer.zip to the /tmp/WHVscripts directory.
5. To make the defaultdata.sh script executable, run the following command: chmod 775 defaultdata.sh
6. Run the defaultdata.sh script from the /tmp/WHVscripts directory using the following syntax:

./defaultdata.sh PureApp_systemName  PureApp_UI_userid  PureApp_UI_password 2>&1 > defaultdata.log

• WebSphere cluster

An IBM 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, which is an unmanaged node, are located on the same virtual machine, reducing the number of virtual machines that are deployed.
• 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.
• WebSphere advanced cluster

An IBM WebSphere Application Server Network Deployment topology with IBM WebSphere Application Server Hypervisor Edition Intelligent Management Pack features for larger-scale development or production environments.
• 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 virtual system pattern contains a WebSphere Application Server under one virtual machine.

• Message: No WebSphere OVA images were found in the appliance catalog.

The installation script requires that a supported version of WebSphere Application Server Hypervisor Edition is installed and the license accepted. If WebSphere Application Server Hypervisor Edition is not installed, install the product from the Open Virtualization Archive (OVA) file, accept the license agreement, and run the script again.

• Message: The advanced options already exist.

The install script detected that some patterns or options are already installed. You can safely ignore this error.

• Message: A Timeout Communication with the appliance occurred.

Verify that the appliance IP address is correct and can be reached from the VM instance. The VM instance firewall might also be preventing network access to the appliance.


• There is an error when importing the configuration scripts.

Verify that the script files were exported to the directory from which you are running the installation script.