Enabling the Management Center

To use the Management Center to manage your catalogs, promotions, and marketing, first enable the feature.

Before you beginBefore you enable the Management Center, complete the following prerequisites:

  1. Install the Management Center feature that corresponds to the WebSphere Commerce feature pack that you are using:

    • Feature Pack 3

    • Feature Pack 3.0.1

    • Feature Pack 4

      Enabling the Feature Pack 4 Management Center feature, on a machine that has Feature Pack 3.0.1 Management Center feature enabled, creates a backup of the existing LOBTools WAR file. The LOBTools WAR file included with Feature Pack 4 replaces your existing WAR file. Refer to Overview: Migrating Management Center

  2. Ensure that your system meets all of the prerequisites for the feature pack.

  3. Ensure that your administrative server is started. For example:

    • If WebSphere Commerce is managed by WAS Deployment Manager (dmgr), start the deployment manager and all node agents. Optionally, your cluster can also be started.

    • If WebSphere Commerce is not managed by WAS Deployment Manager (dmgr), start the WAS server1.

  4. Ensure that the test server is stopped and that Rational Application Developer is not running.

About this taskTo enable the Management Center:

  1. Ensure that you are logged on as a WebSphere Commerce non-root user.

  2. Navigate to the following directory:

  3. To enable the feature...

    1. Run the enablement script:

      • config_ant.bat -buildfile WC_installdir/components/common/xml/enableFeature.xml -DinstanceName=instance -DfeatureName=management-center -DdbUserPassword=db_password [-DdbaPassword=dba_password]

      • ./config_ant.sh -buildfile WC_installdir/components/common/xml/enableFeature.xml -DinstanceName=instance -DfeatureName=management-center -DdbUserPassword=db_password [-DdbaPassword=dba_password]

      • enableFeature.bat -DfeatureName=management-center [-DdbaPassword=dba_password]

      The dba_password is required only if you are enabling the feature on an Authoring server.

    2. The following messages are shown:
      You must read and accept the End User License Agreement to continue.
      

      • Press Enter key to display the agreement.

        On some systems, you might be required to hit the Enter key several times before the license agreement is displayed.

      Review the License Agreement. If you accept the conditions, enter y for the message: Do you accept? (y,n)

    If the script runs successfully in the runtime environment, you see a BUILD SUCCESSFUL message in the command window where you ran the script and a BUILD SUCCESSFUL message in the WC_installdir/instances/instance/logs/enablemanagement-center_timestamp.log file. For enablement details refer to log file:

    If the script runs successfully in the development toolkit, you see an enableFeature.bat completed message in the command window where you ran the script. For enablement details refer to log file:

  4. Republish the application:

    1. Open WebSphere Commerce Developer and switch to the Project Explorer view.

    2. Start the WebSphere Commerce Test Server.

    3. Right-click the test server in the Servers view and select Publish.

    4. Wait for the application to finish publishing and to restart.

  5. Optional: If you have a remote Web server, propagate your plugin-cfg.xml to your remote machine. Do one of the following:

    • If you are using an IBM HTTP Server Web server, the plugin-cfg.xml is propagated automatically through the WAS Administrative Console. To set up the automatic propagation of your plugin-cfg.xml file, see Selecting a Web server topology diagram and roadmap topic in the WAS Information Center.

      The IBM HTTP Server must be running for auto-propagation to function properly. If you have created a userid and password to access your IBM HTTP Server, update the web server definition in the WAS Administrative Console with this information. If you do not update the Web server definition, auto-propagation will fail.

    • For all other Web servers, propagate the plug-in configuration file by manually copying the plugin-cfg.xml file from WC_profiledir/config/cells/cell/nodes/node/servers/web_servername directory on your WebSphere Commerce machine, to the Remote Configuration Directory that was specified during the instance creation process.

  6. If you are running WebSphere Commerce in a clustered environment, restart your WebSphere Commerce Server.

  7. If the server is configured with LDAP server, restart your WebSphere Commerce Server.

  8. Verify that the enablement script ran successfully by accessing this URL: https://host_name:8000/lobtools If you have enabled the Management Center successfully, you will see the Management Center logon screen.

  9. If you are using a staging server run the stagingcopy utility.

    If you encounter problems with staging copy...

    1. Change STMTHEAP to the maximum value. For example:

      db2 update database configuration for db_schema using stmtheap 240000

    2. Change APPLHEAPZ to 3000. For example:

      db2 update database configuration for db_schema using applheapsz 3000

    3. Disconnect all users from DB2.

    4. Stop and restart DB2.

    5. Run the stagingcopy utility.

ResultsOnce enabled, you can begin using the Management Center to manage business operations for your store.

The Management Center supports single language stores for the consumer direct and B2B direct store models. If you select to work with a multilingual store, a message displays to indicate that the store is not supported and that you should select an appropriate store. For information on how to make a multilingual store compatible with the Management Center, see Change language support.

The Management Center supports multilingual stores for the consumer direct, advanced B2B direct, extended sites, demand chain, and supply chain store models.