The SystemOut.log file is not available in the WebSphere Commerce development environment. The contents of the Console view contain the messages that are discussed here.
To ensure that WebSphere Commerce Payments is started:
- Open the following log file in a text editor:
WAS_installdir/logs/server_name/SystemOut.log
WAS_userdir/logs/server_name/SystemOut.log
where server_name is the name of the WebSphere Commerce Payments application server. WebSphere Commerce Payments application servers always have a name of instance_name_Commerce_Payments_Server, where instance_name is the name of the WebSphere Commerce Payments instance.
For example, if you have a WebSphere Commerce Payments instance called wpm, the server_name would be wpm__Commerce_Payments_Server.
- Ensure that the following text appears near the end of the log file:
CEPFW0702: IBM WebSphere Commerce Payments has started successfully. . WSVR0221I: Application started: instance_name_Commerce_Payments_App . . . WSVR0001I: Server instance_name_Commerce_Payments_Server open for e-business
where instance_name is the name of the WebSphere Commerce Payments instance.In the Console view, instance_name_Commerce_Payments_App is replaced with server1.
Note: Some text that appears in the log file has been omitted to indicate the relevant clearly.
If WebSphere Commerce Payments fails to start, you will see messages similar to the following near the end of the log file:
WSVR0101W: An error occurred starting, instance_name_Commerce_Payments_App WSVR0217I: Stopping application: instance_name_Commerce_Payments_App . . WSVR0220I: Application stopped: instance_name_Commerce_Payments_App . . WSVR0003E: Server instance_name_Commerce_Payments_Server failed to start.
where instance_name is the name of the WebSphere Commerce Payments instance.
In the Console view, instance_name_Commerce_Payments_Server is replaced with server1.
Note: Some text that appears in the log file has been omitted to indicate the relevant messages clearly.