For IBM i OS operating systemSolarisLinuxAIXWindows

For IBM i OS operating systemWindowsAIXLinuxSolaris Verifying the remote Configuration Manager client level

The Configuration Manager client and the Configuration Manager must be at the same level. If you have applied any WebSphere Commerce fix packs on the WebSphere Commerce node, you must apply the same or corresponding Windows fix pack level to the Configuration Manager client node.

SolarisLinuxAIXWindowsThe steps in this topic are necessary only if you want to use the Configuration Manager GUI, and you also want to run the client on a separate machine. Usually, users will run the client on WebSphere Commerce server machine, since that is where it is installed. If you choose to use a different host then you need to verify the remote client level after you perform the steps to the following topic:
For IBM i OS operating systemIf you want to use the Configuration Manager GUI, you must perform the steps in this topic after you perform the steps in the following topic: If you want to create the instance silently instead of using the Configuration Manager GUI, you do not need to perform these tasks.

Procedure

  1. On the Configuration Manager server node (WebSphere Commerce or WebSphere Commerce Payments node):
    1. Open the following file in a text editor: WC_installdir/properties/version/COMMERCE.product
    2. Check the value in the <version> tags. For example,
      <version>7.0.0.0</version>
    3. Check the value in the <build-info> tag. For example,
      <build-info date="01/01/09" level="xxxxx"/>
    4. Check the value in the <id> tag. For example,
      <id>wc.server.pro</id>
  2. On the Configuration Manager client node:
    1. Open the following file in a text editor: SolarisLinuxAIXWindowsWC_installdir/properties/version/COMMERCE.productFor IBM i OS operating systemWC_rmtMgt_installdir/properties/version/COMMERCE.product.

      For IBM i OS operating systemWhere WC_rmtMgt_installdir is the install directory of the WebSphere Commerce Remote Management Utilities.

    2. Check the value in the <version> tags. For example, <version>7.0.0.0</version>
    3. Check the value in the <build-info> tag. For example, <build-info date="01/01/09" level="xxxxxxx"/>
    4. Check the value in the <id> tag. For example, <id>wc.server.pro</id>
  3. If the values for both tags on both nodes match, the Configuration Manager client and server are at the same level.