Migrate Payments application

 

 

Considerations before migrating Payments application

• Ensure the Payments database tier has been migrated to WebSphere Commerce Payments v6 level.

• (i5/OS) Ensure the user, who will be running the Payments migration, has the SECOFR class authority.

• (Linux) You should run WCIM as the same user you use to start your WebSphere Commerce application server. You must use a non-root user, for example, wasuser to do so. To switch to the wasuser type su - wasuser.

• If you have any third-party cassette installed on your previous release, ensure that you have copied the following directory from your previous release to the corresponding directory of WebSphere Commerce v6:
  WC_installdir/payments/cassettes/third-party_cassette_name

Note : Ensure that the non-root user (such as wasuser) have the read/write authority of WAS directory before starting migration.

 

Migrate Payments application using WCIM

To migrate your Payments application using the WCIM utility, firstly refer to Deciding the migration mode of your Payments application.

After deciding your migration mode, refer to either of the following link to migrate your Payments application:

• Migrate Payments application using two machines.

• Migrate Payments application using one machine.

Notes:

• (i5/OS) The length of the Websphere Commerce or Payments instance name you enter cannot be greater than 10 characters long and cannot include the following characters: / \ " | < > ? * : &

• (Linux)(Windows)(AIX)(Solaris) The length of the Payments instance name you enter into WCIM cannot be greater than 12 characters long, and cannot include the following characters: / \ " | < > ? * : &

Related tasks

• Deciding the migration mode of your Payments application.

• Migrate Payments application using two machines.

• Migrate Payments application using one machine.