WebSphere Commerce V5.4 Handbook: Architecture and Integration Guide

520 WebSphere Commerce V5.4 Handbook, Architecture and Integration Guide

Also ensure that the firewall between the Web server and Commerce Application

Server node (FW2) allows traffic at the port being used by the HTTP transport for

the application (9080 in the example above).

13.15 Verify the store and runtime

Now that the WebSphere Commerce runtime environment is configured and a

store is published, you need to verify that all the components are functioning

correctly.

13.15.1 Verify the tools

To verify the WebSphere Commerce administration tools are working properly,

do the following:

1. Ensure the following applications are started:

– IBM HTTP Server

– IBM WebSphere Application Server Administrative Server

– IBM DB2 Server

2. Ensure that the following application servers are started from the WebSphere

Application Server Administrative Console:

– WebSphere Commerce Server - <instance name>

Note: The plug-in configuration file contains information about the entire

WebSphere Administrative Domain. However, the Web server will not be

configured to serve applications other than WebSphere Commerce.

The host names for all WebSphere nodes listed in plugin-cfg.xml must be

known to the Web server machine; otherwise the HTTP Server will fail to start.

The /usr/HTTPServer/logs/error_log will contain messages similar to the

following:

[error] ws_transport: transportSetServerAddress: unable to resolve

hostname[error] ws_server: serverAddTransport: Failed to initialize server

address

Either delete all elements from the plugin-cfg.xml that relate to other nodes, or

alter the Transport tags to use a non-existent IP address (such as 0.0.0.0) so

that the Web server will not try to resolve the host name. For example:

<Transport Hostname="0.0.0.0" Port="9085" Protocol="http"/>

These manual editing steps will be required each time the plug-in

configuration file is regenerated.

Chapter 13. AIX three-tier runtime with DB2 and IBM HTTP Server 521

– WebSphere Payment Manager

3. Ensure the IBMPayServer is started.

4. Start the Store Services from the Start menu.

5. Start the Administration Console from the Start menu.

6. Start the WebSphere Commerce Accelerator from the Start menu.

13.15.2 Verify the store

To verify the WebSphere Commerce store is working properly, do the following:

1. Precompile the store JSPs.

In order to view the store pages correctly without waiting for the WebSphere

Application Server to compile each page after it is requested, we first need to

compile all the sample store JSPs. In our example, we have already

precompiled the JSPs.

2. Enter the store home page URL. If you do not recall the URL, it can be

accessed from the Publish Summary of Store Services. The store home page

URL will look something like the following:

http://<hostname>/webapp/wcs/stores/servlet/<store>/index.jsp

For example - tooltech:

http://m23vnx88.itso.ral.ibm.com/webapp/wcs/stores/servlet/tooltech/index.j

sp

3. Register a user.

4. Browse the store catalog.

5. Select an item to purchase.

6. Complete an order by selecting a valid payment type.

7. Enter 16 zeroes (0s) as your credit card number so that you would be able to

test it.

13.15.3 Verify Payment Manager

Once you get the order confirmation within the store, do the following to verify the

integration of WebSphere Commerce and WebSphere Payment Manager:

1. If you use a different IP address for the port 8000 server, update the host

aliases for the VH_instance_tools virtual host accordingly, in the WebSphere

Administrative Console.

522 WebSphere Commerce V5.4 Handbook, Architecture and Integration Guide

2. Because the WebSphere Commerce Tools require Internet Explorer 5.5, you

will need a Windows machine that can access the port 8000 Web server in

the DMZ.

3. You may need to create a route on the Payment Manager node to the

Network Dispatcher.

# route add 10.100.0.0 mask 255.255.255.0 9.24.105.51

4. Use the secure interface on the firewall (FW2) as the gateway.

5. Disable the proxy (SOCKS) server for the Microsoft Internet Explorer.

6. Ensure that the remote Payment Manager has been started. See 19.3.4,

“Start WebSphere Payment Manager” on page 724 for detailed instructions.

7. Log in to the WebSphere Payment Manager Console:

https://<paymentmanager_host>/webapp/PaymentManager

The default password is wcsadmin, which must be changed at initial logon.

8. Check the

Order check box and click Approve Selected. You should see the

order that was just placed.

9. You should see a message indicating that the order was approved and that

there are no more pending orders to approve.

Congratulations, the three-tier AIX runtime environment implementation is now

complete.