Verifying the remote Configuration Manager client level

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

You need to install the Configuration Manager client only if you want to use the Configuration Manager GUI and you want to run the client on a separate machine. Usually, users run the client on WebSphere Commerce server machine, since that is where Configuration Manager is installed. If you choose to use a different host, then you need to verify the remote client level after you complete the steps in Installing the Configuration Manager client.

For IBM i OS operating systemIf you want to use the Configuration Manager GUI, you must complete the following procedure after you For IBM i OS operating systemInstall the Configuration Manager client. If you want to create the instance silently instead of using the Configuration Manager GUI, you do not need to complete the following procedure.

Procedure

  1. On the Configuration Manager server node (WebSphere Commerce 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>8.0.0.0</version>
    3. Check the value in the <build-info> tag.
      For example, <build-info date="11/30/15" 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:
      • LinuxAIXWindowsWC_installdir/properties/version/COMMERCE.product
      • For IBM i OS operating systemWC_rmtMgt_installdir/properties/version/COMMERCE.product.

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

    2. Check the value in the <version> tags.
      For example, <version>8.0.0.0</version>
    3. Check the value in the <build-info> tag.
      For example, <build-info date="11/30/15" 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.