Migrating IBM Websphere Commerce Version 7 Feature Pack 8 configuration files

Migrate your IBM Websphere Commerce Version 7 configuration files by manually merging them with, or copying them to, your HCL Commerce Version 9.1 production environment.

Procedure

  1. If you customized any of the following files in IBM Websphere Commerce Version 7, merge, or copy, the customized file to your HCL Commerce Version 9.1 production environment.
    • WC_eardir/Stores/WebContent/WEB-INF/web.xml
    • WC_eardir/.settings/org.eclipse.wst.common.component/*
      Note: This path refers to the whole directory.
    • WC_eardir/META-INF/ibmconfig/cells/defaultCell/applications/defaultApp/deployments/defaultApp/resources.xml
    • WC_eardir/xml/config/BusinessAuditDataCapture.xml
    • WC_eardir/xml/config/payments/ppc/plugins/CustomizationPlugin/PluginDeployment.xml
    • WC_eardir/xml/config/payments/ppc/plugins/LOCPlugin/PluginDeployment.xml
    • WC_eardir/xml/config/payments/ppc/plugins/PaymentechPlugin/PluginDeployment.xml
    • WC_eardir/xml/config/payments/ppc/plugins/SimpleOffline/PluginDeployment.xml
    • WC_eardir/xml/config/payments/ppc/plugins/SimplePunchoutPlugin/PluginDeployment.xml
    • WC_eardir/xml/config/wc-server.xml
    • WC_eardir/xml/ldap/ldapentry.xml
    • WC_eardir/xml/member/MemberRegistrationAttributes.xml
    • WC_eardir/xml/PromotionEngineConfiguration/*PromotionEngineConfig.xml
    • WC_eardir/xml/config/businessContext.xml
  2. Copy the files under the following directories for all of your different components in your IBM Websphere Commerce Version 7 production environment, to your HCL Commerce Version 9.1 production environment.
    • WC_eardir/xml/config/com.ibm.commerce.component_name-ext/*
    Where:
    component_name-ext
    The name of the component that you customized, for example, catalog or member.
  3. Update your wc-server.xml file to contain the correct settings, paths, and host name for your HCL Commerce Version 9.1 production environment.
    Note:
    • If the wc-server.xml file contains the CrossTransactionCache tag, it is generally recommended to remove it so that the default configuration is used. If the defaults are not sufficient, the CrossTransactionCache tag can be added back within the InstanceProperties tag, specifying only the configuration settings that must be changed from the default values. For more information on the configuration settings for the CrossTransactionCache tag, including the default values, see Additional HCL Commerce data cache configuration.
    • If you have any other configuration updates in your wc-server.xml configuration file, you must merge those changes before migrating it to HCL Commerce Version 9.1 development or production environments.

      For example, to enable marketing in Management Center for HCL Commerce, see Enabling Management Center marketing features.

    Important: If you have enabled WebSphere Application Server application security enabled in your IBM Websphere Commerce Version 7 wc-server.xml configuration file, you must disable it for use with HCL Commerce Version 9.1.

    Ensure that the security element of the wc-server.xml configuration file contains the attribute enabled="false".

  4. Optional: HCL Commerce Version 9.1.8.0 or later Update your wc-server.xml configuration file to enable more aggressive file persistence values for the Assets tool in HCL Commerce Version 9.1.
    1. Locate the ScheduledContentManagedFileEARUpdateConfiguration tag.
    2. Update the values for minNumOfFileForUpdate and minSecFromLastUpload. These values dictate how often files are moved from the HCL Commerce database, where they are initially uploaded to, to the file system where they are persisted. Because the process no longer requires updating the HCL Commerce Enterprise Archive (EAR) file, they can be set to more aggressive values than appropriate in previous versions of WebSphere Commerce.
      minNumOfFileForUpdate=1
minSecFromLastUpload=300
      In this example, a single file will trigger the persistence process, or the process will repeat after a maximum of 300 seconds (or 5 minutes).

Results

Your custom configuration files are migrated from your old WebSphere Commerce installation and are ready to be used with your new HCL Commerce Version 9.1 installation.