WebSphere Commerce EnterpriseNew feature for Feature Pack 8Linux

Deploying the virtual system pattern

Provide details about the virtual system pattern in IBM PureApplication Software, IBM PureApplication System, or IBM PureApplication Service. Then, deploy the IBM WebSphere Commerce Pattern V2.1.0.1 for Red Hat Enterprise Linux for x86.

About this task

The virtual system pattern consists of two separate patterns: DB2 HADR pattern for commerce and commerce application pattern. The DB2 HADR pattern must be deployed first. Note the host names, DB2 instance ports, user IDs, passwords, and all other parameters because they are needed to deploy the commerce application pattern.

If you choose to deploy the virtual application pattern instead of the virtual system pattern, the DB2 HADR and commerce application patterns are deployed together by the virtual application pattern. The dependencies are resolved automatically. The virtual application pattern provides a simple way to deploy DB2 HADR server and commerce application together. You must use the virtualized environment to run DB2.

The virtual system pattern provides the flexibility to create a DB2 HADR server with a pattern or manually, such as in a native environment.
Note: Manually creating a DB2 HADR server increases complexity. Ensure that you consider the complexities when you maintain your server.


  1. In the IBM PureApplication System user interface, click Patterns > Virtual System Patterns. The Virtual System Patterns pane displays a list of existing virtual system patterns.
  2. Select DB2 HADR pattern for commerce, and then commerce application pattern. The patterns must be deployed in this order. Note the information that is generated when the DB2 pattern is deployed, such as, host names, ports, user IDs, and passwords. The generated information is needed to deploy the commerce application pattern.
    Note: The Commerce virtual system pattern is referencing the WebSphere Application Server Hypervisor Edition with larger disks. The pattern import process might point to a different WebSphere Application Server Hypervisor Edition with smaller disks. Ensure that the correct image is used. Otherwise, the deployment might fail.

    If you choose to deploy commerce application as a virtual application pattern, ensure that the correct image is used in the virtual system pattern editor.

  3. Click the Deploy icon on the toolbar.
  4. Provide the following information.
    Virtual System Name
    Enter the name of the virtual system instance in which to deploy this virtual system pattern.
    Choose Environment
    Use the defaults that are provided, or select the environment profile, cloud group, IP group, or priority if choices exist.
    Schedule deployment
    By default this parameter is set to Start now. Change this setting if you want to wait to initiate deployment.
    Component attributes
    Review and, if necessary, change previously set values such as user IDs and passwords, or download URLs. To change these parameters, click the link to each of the virtual parts. As an example, click the Standalone server link.
    Avoid troubleAvoid trouble: If you plan to add capacity to your clusters by adding more nodes later, you must not change your file server. Write down the downloadUserID, downloadUserPassword, and db2InstallerUrl values that you use for future reference. Every time you deploy an instance, the deployment uses the same values for these three parameters. If the values for these parameters change, you have no way of providing the new information to the deployed instance. This is especially important if you are required to change your passwords at regular intervals. If you are required to change the downloadUserPassword value after you deploy, you must change it back to its original value if you later decide to add more nodes.
  5. Click Quick Deploy to start deployment.


Your virtual system is deployed with the following status message, Virtual system is ready.

You now have a production WebSphere Commerce environment with Feature Pack 8, and Fix Pack 9 enabled.