Migrate > Take the first steps after WebSphere Commerce migration > Migrating from a previous payment implementation > Migrating WebSphere Commerce Payments Multipayment Framework to v7 (compatibility mode)

Post Payments application and database tier migrating steps

In this step you define the host name and port number of the Payment server, you also specify whether to use SSL.

After you have completed Payments instance and database tier migration complete the following steps:

Procedure

1. After payments migration has completed successfully, sign out of the session. Sign on with the QSECOFR user profile and delete the temporary user profile, that was created for the Payments database tier migration, and change the owner for the objects to QPYMSVR:

   DLTUSRPRF USRPRF(paytemp) OWNOBJOPT(*CHGOWN QPYMSVR) PGPOPT(*NOCHG)
   

2. Open Configuration Manager
   

3. Verify or change WCSRealm properties:

   1. Expand WebSphere Commerce > node_name > Payments > Instance List > payments_instance > Instance Properties > WCSRealm.

   2. If required, change the WebSphere Commerce Web server host name and Web server port number.

   3. If you have changes the values, click Apply. When the action is complete, the following message is displayed:

      The WCSRealm was successfully created. 
      

4. Check the host name. If the final host name is not the host name of migrated payments instance, update it using Configuration Manager according to the following instructions:

   1. Expand hostname > Commerce > Instance List > commerce_instance > Instance Properties > Payments.

   2. Alter the Web server Hostname to reflect the final hostname for the migrated Payments instance.

   3. Click Apply to apply the final payment Web server host name to the Commerce instance. After clicking Apply, you are prompted to exit the Configuration Manager.

5. Exit from Configuration Manager.

6. Ensure the section in the WebSphere Commerce instance.xml and wc-server.xml files that refer to this Payments server has been updated to the final host name and port. The following example shows what the file would contain if you choose to enable SSL:

   <PaymentManager
           ... 
           Hostname="myhost.mydomain.com"
           WebServerPort="5433"
           ... />
   

7. Change the host name for the Payments instance. Before starting the migrated Payments instance for production in most migration scenarios, you might want to change the host name for the migrated Payment instance to a final one.

   1. Open the following file:

      • WC70_userdir/instances/migrated_payments_instance/xml/migrated_payments_instance.xml

      • WC70_installdir/instances/migrated_payments_instance/xml/migrated_payments_instance.xml

      • WC70_installdir\instances\migrated_payments_instance\xml\migrated_payments_instance.xml

   2. In this file, locate the HostName attribute of the PMWebServer element. For example:

      PMWebServer 
      ... 
      HostName="myhost.mydomain.com"
      ... /> 
      

      Change the host name to the final host name.

   3. Open Configuration Manager.
      

   4. Under WebSphere Commerce expand host_name > Payments > Instance List > payments_instance > Instance Properties > Web server.

   5. Regardless if any changes were made to this panel or not, click Apply to apply the final host name to the Web server. This action may take several minutes to complete. Once completed, a new migrated_payments_instance.xml file is created. This apply action also ensures that the host name of the migrated Payments instance will be correct in the SitePaymentsPayment Settings page in the Administration Console.

8. Check the Payments server custom properties.

   1. Open the file PaymentsInstance.properties under WC70_installdir/payments/instances/migrated_payments_instance and verify or change the wpm.DBjdbcURL and DBjdbcURL to use the final host name.

   2. Check the Payments instance custom properties in WebSphere Application Server by the following steps:

      • Log on to the WebSphere Application Server Administration Console of profile named migrated_payments_instance. The profile is created during the Payments application migration and named with the migrated Payments instance name.

      • Go to Servers > Application Servers > server1 > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties

9. Start the Payments instance using either of these methods:

   • Start and stop WebSphere Commerce Payments from Configuration Manager.

   • Start and stop WebSphere Commerce from a command line.

Previous topic:

Migrate the Payments application

+

Search Tips   |   Advanced Search