A failed connection between System Manager and InterChange Server Express
is unlikely after you have validated your installed system as described in the
Quick Start Guide. However, if at a later time System
Manager is unable to connect to InterChange Server Express, make sure the
following requirements are still being met in your current installation:
- InterChange Server Express must be running in order for System Manager to
connect to it. Examine the logging output for InterChange Server
Express to ensure that it has a logging statement which reads
"<server name>" is ready", where <server
name> is the name of your InterChange Server Express instance.
- The IBM Java Object Request Broker (ORB) must be running for clients such
as the tools to communicate with it.
- When register, you must specify the name of InterChange Server Express
exactly as it exists. If you use the wrong case or leave out a single
character when trying to register a server instance, then System Manager will
be unable to connect. You can be sure of the exact name of the server
with the following techniques:
- Examine the name exactly as it appears in whatever interface is used to
start the server. On Windows, the server name is commonly supplied as
the variable SERVERNAME with the default value
WebSphereICS in the start_server.bat batch file. If
your InterChange Server Express is on OS/400, you can use the administrative
Console supplied for use with OS/400 to examine the server name. Note
that on OS/400, all names for instances of InterChange Server Express are in
uppercase, and you must match the casing when you register an instance of
InterChange Server Express with System Manager.
- Examine the name as it is displayed in the InterChange Server Express
logging output. The log entry "<server name>"
is ready" indicates that the server has started and by what name it can be
identified.
- You must specify the correct user name, which by default is
admin.
- You must specify the correct password. The default password is
null, but it can be changed, as described earlier in this
guide. If you cannot connect when specifying the password
null, make sure that no who works with the server instance has
changed the password.
If you have cached the user name and password, the password value sometimes
gets corrupted. It will still appear as four asterisks, so you will not
intuitively think that its value has changed. Delete the cached value
in the Password field and type the password again.
