Resolving Workflow Connection Errors in Control Center

Technote (troubleshooting) Problem(Abstract) Workflow Process administrators can run into a number of problems when trying to open or validate Workflow Process through the Control Center. These are usually due to configuration problems with MAXIMO.INI or SQL.INI. This document outlines the common causes for these types of errors.

Resolving the problem MAXIMO.INI MAXIMO.INI Section [java] When not using EAR files JavaParameters=Djava.rmi.server.codebase="http://ACMEMAX01:7001/ http://ACMEMAX01/lib/jndi.jar" -Djava.security.policy=maxlib.policy -cp . Section Description The [java] section gives the parameters for Java. This section is used by Workflow Designer to locate java code. In this example Maximo context, ACMEMAX01 is the name of the Application Server and 7001 is the listen port assigned by the Maximo administrator. Note the "/" after the port number, the double space between the two http: specifications and the space between -cp and the ending period. The [java] section gives the parameters for Java. This section is used by Workflow Designer to locate java code. In this example Maximo context, ACMEMAX01 is the name of the Application Server and 7001 is the listen port assigned by the Maximo administrator. Note the "/" after maximo and the space between -cp and the ending period. The [AppServer] section indicates the location of the MXServer and jsp location. In this example Maximo context, MAXPROD is the name of

[java] When using EAR Files JavaParameters=Djava.rmi.server.codebase="http://ACMEMAX01:7001/maximo/" -Djava.security.policy=maxlib.policy -cp .

[AppServer] When not using EAR files MAXPROD=ACMEMAX01/AcmeProdServ jsphost=ACMEMAX01:7001/jsp

the database (as defined in the SQL.INI), ACMEMAX01 is the name of the Application Server, and AcmeProdServ is the name of the Maximo server instance in mxserver.properties (mxe.name). 7001 is the listen port assigned by the Maximo administrator. [AppServer] When using EAR files MAXPROD=ACMEMAX01/AcmeProdServ jsphost=ACMEMAX01:7001/maximo/jsp The [AppServer] section indicates the location of the MXServer and jsp location. In this example Maximo context, MAXPROD is the name of the database (as defined in the SQL.INI), ACMEMAX01 is the name of the Application Server, and AcmeProdServ is the name of the Maximo server instance in mxserver.properties (mxe.name). 7001 is the listen port assigned by the Maximo administrator.

Error Messages Problem: When launching WorkFlow Designer from the Control Center, user receives message Unable to load "WFDESIGN.exe." File not found.

Note: You may not have licensing for Workflow Designer. If you are licensed for Workflow Designer, please contact your Business Service Manager. Solution: Check that WFDESIGN.EXE is in your Control Center folder. If not, copy it from the Workflow Designer CD into the Control Center folder (usually C:\Program Files\Control Center.). Problem: When validating a Workflow Process, user receives message User name and site are not valid. Please try again.

Solution: Log into Control Center as a user that is a member of the site for which you are creating a Workflow Process. Important note: MAXIMO and SYSADM are not members of the default MAXIMO site. Problem: When validating a Workflow Process, user receives message Unable to load the WorkflowLoader.class. Check that WFSecurityManager.class and Workflowloader.class are in the classpath.

Solution 1: Ensure that the application server and port number piece in the [java] section of MAXIMO.INI are correct, e.g.: When not using EAR Files [java] JavaParameters=-Djava.rmi.server.codebase="http://AppServerName:PortNumber/ http://AppServerName/lib/jndi.jar " -Djava.security.policy=maxlib.policy -cp . Note the "/" after the port number, the double space between the two http: specifications and the space between -cp and the ending period. When using EAR Files [java] JavaParameters=Djava.rmi.server.codebase="http://AppServerName:PortNumber/maximo/" -Djava.security.policy=maxlib.policy -cp . Note the "/" after maximo and the space between -cp and the ending period. Solution 2: If this is already the case, then ensure that you have one copy of SQL.INI on your workstation or mapped drive to a file server and that both pieces of the remotedbname in the [odbcrtr] or [oragtwy] section in SQL.INI are correct, e.g.: Microsoft SQL Server: [odbcrtr] ... remotedbname=DatabaseName,DSN=DSNName Oracle: [oragtwy] ... remotedbname={DBAlias},@tns:{ConnectString}

Problem: When validating a Workflow Process, user receives message The system was

unable to connect to an application server on the specified host and shows a computer name:

Solution 1: Ensure that name of application server in [AppServer] section of MAXIMO.INI is correct, e.g.: [AppServer] DBName=AppServerName/MXServerName ... Solution 2: If this is already the case, then ensure that port number of the application server in [AppServer] section of MAXIMO.INI is correct, e.g.: (a) When using EAR Files [AppServer] ... jsphost=AppServerName:PortNumber/maximo/jsp (b) When not using EAR Files [AppServer] ... jsphost=AppServerName:PortNumber/jsp

Problem: When validating a Workflow Process, user receives message The system was unable to connect to an application server on the specified host, and shows an IP address:

Solution 1: Ensure that the application server is running. Solution 2: If it is running, then make sure that the database name is correct in the [AppServer] section of MAXIMO.INI, e.g.: [AppServer] DBName=AppServerName/MXServerName ...

Problem: When validating a Workflow Process, user receives message The system was unable to connect to an application server on the specified host and shows a single word:

Solution 1: Ensure that in the [AppServer] section of MAXIMO.INI, the MXServerName (defined in the corresponding {MXServerName}.properties file in the mxe.name section) is correct., e.g.: [AppServer] DBName=AppServerName/MXServerName ... Solution 2: If this is the case, but you have specified a non-zero RMI port in MXServer.properties (mxe.rmi.port, mxe.registry.port), you must specify the mxe.registry.port in the [AppServer] section as follows: [AppServer] DBName=AppServerName:RegistryPortNumber/MXServerName ... Solution 3: If you are using BEA WebLogic 7.0, make sure that the Machine is set to (none) and the Listen Address for the Maximo server is empty (see example below).

Problem: When attempting either to enable a Workflow process or connect to the Workflow Inbox, user receives error Cannot Load JVM.

Solution: Perform the following steps wherever the Control Center (e.g., C:\Program Files\Control Center executables are located. 1. Select and copy all .DLL files from the C:\Program Files\Control Center\jre\BIN folder. 2. Paste the copied files into the Control Center folder. These steps will correct the error. Problem: When attempting either to save or enable a Workflow process , user receives error User name and password are not valid. Please try again.

Solution: There are two or more Maximo installations on your Application Server whose mxe.name is not unique (usually MXServer). Change any servers that do not have unique names to unique ones, and delete, rebuild and redeploy the EAR files.

Historical Number M03741 Product Alias/Synonym MAXIMO