Troubleshoot: The adapter for WebSphere InterChange Server

The following lists potential problems you may encounter while configuring the adapter, and actions to resolve these problems.

Problem:

You have the InterChange Server (ICS) and repository on one machine, and the WebSphere Commerce Server on another machine. What configuration information is needed for the Visigenic ORB agent to work across subnets? The symptom is the following dialog box that pops up when attempting to connect, indicating that the WebSphere Commerce Server is not running even though you can independently verify that it is.

"Can't locate the InterChange Server. The server is probably not running."

Solution 1:

1. Create a user-level environment variable, named VBROKER_ADM which points at the adm directory in your Visibroker installation (that is, d:\inprise\vbroker\adm).
2. In the adm directory, create a text file named agentaddr which contains the IP addresses or host names of the client machine which connect to the adapter.
3. Restart the osagent process, making sure that VBROKER_ADM is in the environment of the user or shell that starts this process. You should now be able to connect your WebSphere Commerce Server to the adapter. Note that each osagent must have its own agentaddr text file that contains the remote IP of the WebSphere Commerce Server.

Note: There is no extension on agentaddr, and the only osagent that should be running is on the ICS side.

Solution 2:

Others have had better success with an alternative environment variable, OSAGENT_ADDR_FILE, which should specify the path to and filename of the agentaddr file. Because the ORB needs a few minutes of discovery time, attempt reconnecting over a ten minute window before giving up on any particular method.

Problem:

The WebSphere Commerce Server is unable to connect to more than one InterChange Server. The OSAGENT_ADDR environment variable was set on the WebSphere Commerce Server machine but can only connect to the InterChange Server running on the machine specified. You are running two InterChange Servers on two different subnets, and a WebSphere Commerce Server on a third machine. An osagent is running on each InterChange Server machine and each machine has the VBROKER_ADM environment variable configured properly to point to the directory containing the agentaddr file which contains the IP address of each InterChange Server/osagent machines.

Solution:

Create a localaddr text file in the directory specified in the VBROKER_ADM environment variable of each osagent machine, and specify the IP address or the DNS alias of the other osagent machine.

Problem:

You are trying to connect an NT machine's WebSphere Commerce Server to an InterChange Server(ICS) running
on Solaris.

Solution:

Make sure that the agentaddr file for both the WebSphere Commerce Server and ICS locations have not only the IP address of the machine being connected to, but the machines own IP address as well. Therefore, the agentaddr file on the NT machine must have both its own IP address and the IP address of the Solaris machine.

Note: For other problems not addressed in this file, contact your IBM support representative. The WebSphere Interchange Server adapter is not supported on iSeries, Linux, IBM eServer zSeries, or S390 Linux.

(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.