An eai_bw.eag plug-in error is displayed when attempting to open and EAI BusinessWorks step
Article ID: KB0080906
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Workspace (Windows) | All supported versions |
Description
When opening an EAI_BW step in the iProcess Modeler the error "The iProcess plug-in interface function <EAIGWD_EditStep> in plug-in <eai_bw.eag> returned and unexpected value" is displayed.
The error indicates that the iProcess BusinessWorks Client plug-in was unable to connect to the server plug-in in the iProcess Engine.
As part of the iProcess BusinessWorks Server Plug-in, one of the background processes starts a JMX Server. The client plug-in connects to the JMX Server.
The causes can be:
1. Configuration of the client plug-in.
2. Configuration of the server plug-in.
3. Routing between the client and server machine on the network.
4. The server running the iProcess engine has multiple network interface cards configured.
The error indicates that the iProcess BusinessWorks Client plug-in was unable to connect to the server plug-in in the iProcess Engine.
As part of the iProcess BusinessWorks Server Plug-in, one of the background processes starts a JMX Server. The client plug-in connects to the JMX Server.
The causes can be:
1. Configuration of the client plug-in.
2. Configuration of the server plug-in.
3. Routing between the client and server machine on the network.
4. The server running the iProcess engine has multiple network interface cards configured.
Issue/Introduction
An eai_bw.eag plug-in error is displayed when attempting to open and EAI BusinessWorks step
Environment
All supported operating systems
Resolution
The JMX Server port is configured on the iProcess Engine (iPE) in the $SWDIR/etc/jmxconfig.properties file.
The JMX Server uses the port specified in the file, and second port (port +1) for the RMI Connector.
Both must be free for the JMX Server to function.
On the client side, the JMX Server to connect to is configured in the CLIENT_HOME/jmsdb.properties file.
Check the hostname is correct and the port matches the port specified in the server configuration file.
If the above is configured correctly provide TIBCO Support with the following:
1. The iProcess engine configuration files:
SWDIR/swdefs
SWDIR/etc/staffpms
SWDIR/etc/swjmx.properties
SWDIR/eaiframework/frameworkconfig.xml
SWDIR/eaijava/jmxconfig.properties
SWDIR/eaijava/eaijavaplugin.properties
SWDIR/eaijava/jmx/config.xml
SWDIR/jmsadmin/jmsdb.properties
2. The iProcess client configuration file,
CLIENTDIR/jmsdb.properties
3. Output from the following commands on the iProcess Engine server:
set (if the the iPE server is Windows for the user that starts the iPE)
env (if the the iPE server is Unix for the user that starts the iPE)
swadm show_all_attributes
swadm show_processes
swsvrmgr status –v
sweaireg list
ipconfig /all
4. The iProcess logs files from the $SWDIR/logs directory.
5. Confirm if:
a. There is more than one iProcess engine running on the machine?
b. Is the iProcess client and server being run on the same machine?
The JMX Server uses the port specified in the file, and second port (port +1) for the RMI Connector.
Both must be free for the JMX Server to function.
On the client side, the JMX Server to connect to is configured in the CLIENT_HOME/jmsdb.properties file.
Check the hostname is correct and the port matches the port specified in the server configuration file.
If the above is configured correctly provide TIBCO Support with the following:
1. The iProcess engine configuration files:
SWDIR/swdefs
SWDIR/etc/staffpms
SWDIR/etc/swjmx.properties
SWDIR/eaiframework/frameworkconfig.xml
SWDIR/eaijava/jmxconfig.properties
SWDIR/eaijava/eaijavaplugin.properties
SWDIR/eaijava/jmx/config.xml
SWDIR/jmsadmin/jmsdb.properties
2. The iProcess client configuration file,
CLIENTDIR/jmsdb.properties
3. Output from the following commands on the iProcess Engine server:
set (if the the iPE server is Windows for the user that starts the iPE)
env (if the the iPE server is Unix for the user that starts the iPE)
swadm show_all_attributes
swadm show_processes
swsvrmgr status –v
sweaireg list
ipconfig /all
4. The iProcess logs files from the $SWDIR/logs directory.
5. Confirm if:
a. There is more than one iProcess engine running on the machine?
b. Is the iProcess client and server being run on the same machine?
Feedback
Yes
No
Powered by
