Troubleshoot: Payments

 

Problem

After Payments migration to WebSphere Commerce, v6 Payments, you receive port conflicts when you start Payments.

 

Solution:

Modify the Web server ports through the WebSphere Commerce Configuration Manager to avoid any port conflicts. There are two ports: the SSL port (port 433 by default for previous Payments, 5433 by default for WebSphere Commerce, v6 Payments) and the non-SSL port (port 80 by default for previous Payments, port 5432 by default for WebSphere Commerce, v6 Payments). If the port numbers used by the premigrated instance (SSL or non-SSL) are the non-default ports they are carried forward to the new instance. If the port numbers used by the premigrated instance (SSL or non-SSL) are the default ports, they are changed to the WebSphere Commerce, v6 Payments default ports in the migrated Payments instance.

Make sure that both of the port numbers that are assigned to the Web server for the Payments instance are not in use by other jobs. If so, change the port number for the migrated instance in order to avoid the port conflict.

All Payments Web server ports should be changed through Configuration Manager when possible. This ensures that all properties and files are updated with the same information. To change WebSphere Commerce Payments ports...

  1. Start Configuration Manager for WebSphere Commerce, v6.

  2. Under WebSphere Commerce, expand hostname > Payments > Instance List > payments_instance > Instance Properties.

    1. Click WCSRealm.

    2. By default, the box "Use Non-SSL WC Client" will be cleared. Depending on your previous Payments setup, you might want to select this box which will change the port from 443 to 80. If this is done, click Apply.
      When the changes have been made, you will see a message "The WCSRealm was successfully created."

    3. Click OK

  3. Under Instance Properties, click on WebServer.

  4. The Server Port will be set to 5432 and depending on your previous WebSphere Commerce, V5.5 configuration, the Use SSL box can be checked and a value of 5433 will be shown in the SSL Port box. These port numbers do not need to be changed but if a change is made ensure that Apply is clicked to save your changes.

  5. The message "Event: Configuring Payments instance" is logged when the changes have been completed.

  6. The corresponding Server Port or SSL Port will need to be changed on the WebSphere Commerce side as follows:

    1. Make a backup of the following file:

      WC60_userdir/instances/migrated_WC_instance/xml/ migrated _WC_instance.xml

      (Linux) WC60_installdir/instances/migrated_WC_instance/xml/ migrated _WC_instance.xml Windows

      (Windows) WC60_installdir\instances\migrated_WC_instance\xml\ migrated _WC_instance.xml

    2. Open the following file and search for WebServerPort :

      WC60_userdir/instances/migrated_WC_instance/xml/ migrated _WC_instance.xml

      (Linux)

      WC60_installdir/instances/migrated_WC_instance/xml/ migrated _WC_instance.xml

      (Windows)

      WC60_installdir\instances\migrated_WC_instance\xml\ migrated _WC_instance.xml

    3. Change this port to the Server Port value or to the SSL Port value (if Use SSL is checked)

    4. Save your changes.

    5. When any port is changed, the Web Server plug-in should be updated. Complete the following steps:

      1. Open the WAS Administration Console and sign on.

      2. Expand Environment and click Update Web Server Plugin.

      3. Click OK. The message "The web server plugin configuration was updated successfully" should be posted.

Related concepts