Payments pre-migration considerations

Before migrating Payments, ensure that you have addressed the following considerations:

• All prerequisite software has been migrated or updated.

• You can access the previous version of the Payments and WebSphere Commerce databases.

  (i5/OS) If the WebSphere Commerce, V5.5, 5.6, or 5.6.1 database library is on a remote machine from where WebSphere Commerce, v6 is installed, add a relational database directory entry for the remote system on the system where WebSphere Commerce, v6 is installed. Use the WRKRDBDIRE command to work with relational database directory entries.

• (i5/OS) The following step is only necessary if you have customized or updated your Payments application server settings since you first created it. Create the following file:

  /tmp/new.xml
  
  

  and include the following information in this file:

  <?xml version="1.0"?>
  <!DOCTYPE websphere-sa-config SYSTEM "$XMLConfigDTDLocation$$dsep$xmlconfig.dtd" >
  <websphere-sa-config>
  
  <node name="NodeName" action="locate">
  
  <application-server name="Payments_application_servername" action="export">
  
  </application-server>
  
  </node>
  </websphere-sa-config>
  
  

  where Payments_application_servername is the name of your Payments application server.

• If your previous version of Payments uses the default port numbers 80 and 443, the WCIM utility used to migrate Payments will change the port numbers to the default WebSphere Commerce Payments, v6 ports, 5432 and 5433. If your previous Payments does not use the default ports 80 and 443, WCIM does not change the port numbers to the WebSphere Commerce Payments, v6 default ports. (Note : if you use ports 5432 or 5433 for other applications you will experience port conflicts when you start WebSphere Commerce Payments, v6.)

Related tasks

• Migrate Payments application

• Migrate Payments database