IBM Business Process Manager: Connecting to Process Center from Process Designer
MattLuczkowiak 120000P9G8 Comments (6) Visits (14021)
When using IBM Business Process Manager, some of the core functionality for authoring process applications is done through the Process Designer and to use this tool, after downloading and installing the Process Designer, we need to be able to connect to the Process Center itself.
In some cases, it has been seen that even though a user is able to use a browser to log in to the Process Center, when starting up Process Designer and using the same credentials, the Process Designer is unable to connect to Process Center.
Generally, the connection information to make this happen is stored in a file called eclipse.ini, located in the Process Designer install directory. Specifically, there is an option in that file called:
and it needs to be set to the address of your Process Center, like so:
This is the first place to check to ensure this location is correct. If it is, and the Process Designer will still not connect, it could be because of how the Process Center was installed and configured. If the Process Center was configured using only the short hostname and not a fully qualified hostname, this can cause issues. The reason is that even though the initial connection is made, subsequent exchanges fail since Process Center sends back just its short hostname and the Process Designer machine may not know what that means.
If Process Center is configured using just the short name of
instead of a fully qualified name of
The machine where Process Designer is installed cannot resolve mySampleServer and cannot connect. The quickest fix to this is to add an entry to your host's file on the machine where Process Designer is installed mapping mySampleServer to the fully qualified name (or directly to the IP).
To see if this could be the issue, you can check the directory where Process Designer is for a .txt file with a name like:
If any of these files' contents has an error like:
then you may be experiencing this issue.
There is a technote from IBM WebSphere Application Server which details a similar issue, though the files and symptoms may be slightly different, the solution of editing the host's file is the same: