Migrate >


Take the first steps after WebSphere Commerce migration

After you have migrated the database and application tiers, migrate applicable WebSphere Commerce features, functions and customizations you have performed.


Procedure

  1. After migration, the WebSphere Commerce Accelerator, Administration Console, and Organization Administration Console tools are version 7 default tools. Manually merge any customizations you may have made to the WebSphere Commerce Accelerator, Administration Console, or Organization Administration Console tools in previous releases into the version 7 environment.

  2. After migration, your Stores project web.xml file is a default WebSphere Commerce version 7 file. Manually merge any customizations you may have made to this file in previous releases into the version 7 file.

  3. DOM integration functions were introduced in WebSphere Commerce v6 Feature Pack 5. These functions were merged into WebSphere Commerce v7. The original classes for DOM integration have been deprecated. When you migrate from WebSphere Commerce Version 6 Feature Pack 5 (DOM enabled) to WebSphere Commerce v7, you can replace the deprecated classes.

    1. Query the CMDREG table.

      select * from CMDREG;

    2. Check the CLASSNAME column in the query result, if any deprecated classes occur, replace them.

      update CMDREG set CLASSNAME='replacement class' where CLASSNAME='deprecated class';

      Deprecated classes Replacement classes
      com.ibm.commerce.inventory.commands.DOMDoInventoryActionCmdImpl com.ibm.commerce.inventory.commands.DoInventoryActionCmdImpl
      com.ibm.commerce.order.commands.DOMCheckInStorePickupCmdImpl com.ibm.commerce.order.commands.CheckInStorePickupCmdImpl
      com.ibm.commerce.order.commands.DOMOrderStatusCmdImpl com.ibm.commerce.messaging.commands.OrderStatusCmdImpl
      com.ibm.commerce.order.commands.DOMOrderStatusNotifySendCmdImpl com.ibm.commerce.messaging.commands.OrderStatusNotifySendCmdImpl
      com.ibm.commerce.order.commands.DOMValidatePaymentMethodCmdImpl com.ibm.commerce.order.commands.ValidatePaymentMethodCmdImpl
      com.ibm.commerce.order.facade.server.commands.DOMComposeInventoryRequirementCmdImpl com.ibm.commerce.order.facade.server.commands.ComposeInventoryRequirementCmdImpl
      com.ibm.commerce.order.facade.server.commands.DOMComposeOrderDetailsCmdImpl com.ibm.commerce.order.facade.server.commands.ComposeOrderDetailsCmdImpl
      com.ibm.commerce.order.facade.server.commands.DOMComposeUsableShippingInformationCmdImpl com.ibm.commerce.order.facade.server.commands.ComposeUsableShippingInformationCmdImpl
      com.ibm.commerce.orderitems.commands.DOMOrderItemAddCmdImpl com.ibm.commerce.orderitems.commands.OrderItemAddCmdImpl
      com.ibm.commerce.orderitems.commands.DOMOrderItemBaseCmdImpl com.ibm.commerce.orderitems.commands.OrderItemBaseCmdImpl
      com.ibm.commerce.orderitems.commands.DOMOrderItemUpdateCmdImpl com.ibm.commerce.orderitems.commands.OrderItemUpdateCmdImpl

    3. Check the struts configuration files, if com.ibm.commerce.order.facade.client.DOMOrderFacadeClient is in use, replace it with com.ibm.commerce.order.facade.client.OrderFacadeClient.

    4. Restart WebSphere Commerce Server.


See also

  1. Deploy the migrated custom code
  2. Host name change for e-mail template
  3. Reuse custom staging triggers
  4. Migrate from Member Manager to Virtual Member Manager
  5. Configure WAS for use with WebSphere MQ
  6. Version 5.6.1 Configuring the SSL Accelerator option after migration
  7. Verify encryption settings


+

Search Tips   |   Advanced Search