Troubleshoot: Test order with a payments error
If you are unable to complete a test order due to a WebSphere Commerce Payments error:
- Ensure that WebSphere Commerce Payments has been started.
After WebSphere Commerce Payments is started, ensure that you can log onto the WebSphere Commerce Payments graphical user interface directly:
- Access the Payments user interface from a browser by typing the URL:
http://host_name:port/webapp/PaymentManager
Where:
- host_name
- The fully qualified host name of the machine running the Web Server for WebSphere Commerce Payments. The host name may be a virtual host name on the Web server.
- port
- The port number WebSphere Commerce Payments is running on as shown in the Configuration Manager WebServer information for your Payments instance.
- Type your Payments user ID.
- Type your Payments password.
- Click Logon.
If you receive an indication of an error occurring while accessing the user registry, there may be a communication problem between WebSphere Commerce Payments and WebSphere Commerce. Should this occur, stop and restart the WebSphere Commerce Payments instance. Verify that WebSphere Commerce is started and able to take requests. For example, try a test logon to the WebSphere Commerce Accelerator. If the problem persists, enable the tracing of WebSphere Commerce Payments. (The trace specification string to use is com.ibm.websphere.commerce.payments.*=all=enabled.) Check the resulting trace.log file for information that may be useful to troubleshoot a configuration error.
- Ensure that the store has been configured to use WebSphere Commerce Payments. At publish time:
- Open the Publish Details page for your store.
- Check for the presence or absence of warnings that begin with the string WebSphere Commerce Payments was not configured for the store.
- Ensure that a payment business policy is defined for the payment method the store will use.
Related tasks
Related reference