Install > Installing WebSphere Commerce feature packs > Enable features


Enable the Management Center

The Management Center is enabled by default in WebSphere Commerce version 7. You can disable the Management Center for a specific instance, but once disabled, it cannot be enabled again for that instance. To re-enable the Management Center after it has been disabled, create a new instance.

Once you install a WebSphere Commerce Feature Pack, follow the steps on this page to enable the Management Center feature for the Feature Pack you installed. The Management Center feature delivered in a Feature Pack can be successfully re-enabled if you disabled it.


Before you begin

To use the Management Center to manage the catalogs, promotions, and marketing, first enable the feature. Before you enable the Management Center, complete the following prerequisites:

  1. Review the minimum Hardware prerequisites for installing WebSphere Commerce.

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

  3. AIXLinuxWindowsSolaris Verify the 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. WebSphere Commerce Developer Verify the test server is stopped and that Rational Application Developer is not running.

  5. Backup the database:

    • DB2 Backup overview

    • Oracle See the database vendor's user manual for information about backup and restore procedures.

    • Apache Derby See the database vendor's user manual for information about backup and restore procedures.

    The database updates included in this feature cannot be undone. To undo a database update after enabling the Management Center feature, restore the database backup.


Procedure

  1. Complete one of the following tasks:

    • AIXLinuxSolaris Log on as a WebSphere Commerce non-root user.

    • Windows Log on with a user ID that is a member of the Windows Administration group.

  2. Navigate to the following directory:

  3. Run the enablement script:

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

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

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

    • The -DdbaPassword=<password> is only required for the content versioning feature.

    • 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_INSTALL/instances/instance/logs/enablemanagement-center_timestamp.log file.

    For enablement details refer to log file:

    • WC_INSTALL/instances/instance/logs/enablemanagement-center_timestamp.log

    WebSphere Commerce Developer 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:

    The following warning messages in the feature pack enablement log can be safely ignored: 

    • +++ Warning +++: Tue Mar 10 15:45:50 EDT 2009    
java.lang.NoClassDefFoundError: 
com.ibm.commerce.catalog.facade.CatalogFacade
     at java.lang.ClassLoader.defineClassImpl(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:258)


    • Attribute value cannot be migrated ${parent.width} in file D:\IBM\WCDE_P~1\components\management-center\backup\LOBToolsCustom\WebContent\WEB-INF\src\lzx\commerce\shell\ApplicationMenuItems.lzx
Attribute value cannot be migrated ${this.getPromptText(this.parent.parent.promptText)} in file D:\IBM\WCDE_P~1\components\management-center\backup\LOBToolsCustom\WebContent\WEB-INF\src\lzx\commerce\promotion\restricted\objectDefinitions\BasicCodePatternBuilder.lzx
Attribute value cannot be migrated ${parent.assetGroup.visible} in file D:\IBM\WCDE_P~1\components\management-center\backup\LOBToolsCustom\WebContent\WEB-INF\src\lzx\commerce\marketing\propertiesViews\WebActivityBuilder.lzx

  4. WebSphere Commerce Developer Republish the application:

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

    2. Start the WebSphere Commerce Test Server. Some errors are displayed in the console, these errors can be safely ignored.

    3. In the Servers view, right-click the test server then click Publish.

    4. Wait for the application to finish publishing and to restart. Ensure that no errors are displayed.

    5. If you customized a previous version of Management Center, see Migrate Management Center to migrate those customization to the latest version Management Center.

  5. Optional: If you have a remote Web server, propagate the plugin-cfg.xml file to the remote machine.

    Option Description
    IBM HTTP Server Web server The plugin-cfg.xml is propagated automatically through the WAS Administrative Console.

    The IBM HTTP Server must be running for auto-propagation to function properly. If you have created a userid and password to access the 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.

    All other Web servers Propagate the plug-in configuration file by manually copying the plugin-cfg.xml file from...

    WC_PROFILE/config/cells/cell_name/nodes/node_name/servers/web_server_name

    ... on the WebSphere Commerce machine, to the Remote Configuration Directory that was specified during the instance creation process.

  6. AIXLinuxSolarisWindows If you are running WebSphere Commerce in a clustered environment or if the server is configured with LDAP server, restart the WebSphere Commerce Server.

  7. 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.

  8. If you are using a staging server, ensure that the enablement script ran successfully on both the staging server and the production server before running the stagingcopy utility.

    DB2 If you encounter problems with staging copy, complete the following steps:

    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.


Results

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

Next topic: Disable components in the WebSphere Commerce Accelerator


Related concepts

IBM Management Center for WebSphere Commerce


+

Search Tips   |   Advanced Search