Troubleshooting designer tools

This section describes problems you may encounter when launching any of the designer tools. These include: Business Object Designer, Map Designer, Process Designer, and Relationship Designer. The following problems are addressed:

Designer tool fails to launch and gives a JVM.dll error

Problem

Designer tool fails with the following error message: failed to locate JVM.dll.

Solution

The designer tool cannot find the jvm.dll file or it is loading an incorrect version of it. One or both of the following solutions should fix the problem:

  • Depending on the location of your jvm.dll file, make sure you have the correct path listed in your Path System variables. The jvm.dll file is typically located in one of the following directories:
    • ProductDir\bin
    • ProductDir\jre\bin
    • ProductDir\jre\bin\classic
  • If the above solution does not fix the problem, perform a search on your system for the jvm.dll file, and delete all but the one located in ProductDir\jre\bin\classic.

Designer tool cannot connect to System Manager

Problem

System Manager opens, but designer tools cannot connect to it.

Solution

This typically happens because System Manager cannot bind to a local port (default = 13000). The following list explains three possible reasons why this may happen along with solutions for each explanation.

  • There is already another instance of System Manager running. In this case, be sure you are running only one instance of System Manager.
  • Another application is using the same port. In this case, you can configure System Manager to use a port other than the default port, which is 13000. To do this, provide the following argument in startcsm.bat:
    -vmargs -Dcom.ibm.btools.internal.comm.port=new_port_number
    
  • A firewall running on your machine is preventing network connections. In this case, one of the following solutions should allow System Manager to co-exist with your firewall:
    • Change the firewall setting to allow connections to port 13000.
    • Configure System Manager to use a port other than the default port of 13000. Instructions are described in the second bullet-point above.

If the above solutions do not solve the problem, you can try the following debugging argument in the startcsm.bat file to see if the console output provides any further insight into the problem:

.... -consoleLog -vmargs -Dcom.ibm.btools.internal.comm.debug=true ...

Note:
If you do not see a separate console window, change the following in startcsm.bat:
-vm %CROSSWORLDS%/jre/bin/javaw.exe
to
-vm %CROSSWORLDS%/jre/bin/java.exe

Designer tool cannot be launched from System Manager

Problem

System Manager opens, but designer tools cannot be launched from it.

Solution

One of the following solutions should fix this problem:

  • Make sure your CROSSWORLDS system variable is pointing to the correct directory. This variable should be set in the CWSharedEnv.bat file, which resides in the bin subdirectory of the product directory.
  • Make sure that the Path System variable includes a path to the jvm.dll file.
    Example: ProductDir\jre\bin\classic
  • Make sure the startcsm.bat file contains the correct value for the CWTools.home variable.
    Example: ProductDir\bin
  • Make sure the information contained in the cwtools.cfg file is correct. This file is located at ProductDir\bin.

Copyright IBM Corp. 1997, 2004