Using the TIBCO iProcess Web Services Server Plug-in in a firewall environment you may receive a WS_LOCERR if the TIBCO iProcess Engine is started before the TIBCO iProcess Web Services Jetty server.
book
Article ID: KB0091763
calendar_today
Updated On:
Products
Versions
TIBCO iProcess Web Services Server Plug-in
-
Not Applicable
-
Description
Resolution: If you have TCP port ranging enabled on your TIBCO iProcess Engine, confirm that the TCP port range you have chosen does not conflict with the ports defined for use by the TIBCO iProcess Web Services Server Plug-in or any other iProcess Plug-Ins. If the TIBCO iProcess Engine is started first, it will bind to the ports needed by other processes. The default port numbers for iProcess applications are as follows.
10000 – TIBCO iProcess Web Services Plug-in 10010 – TIBCO iProcess Web Services Plug-in 10021 – TIBCO iProcess Technology Plug-in 10025 – TIBCO iProcess SWJMX Deployment Process
Note that hese port numbers could be different in you environment if you chose different ports during installation or have modified their configuration files after installation.
Solution = = = = Reconfigure the TCP port range used by the TIBCO iProcess Engine via the swadm command. See the TIBCO iProcess Engine: Administrator’s Guide located in the Documentation Library for details.
Issue/Introduction
Using the TIBCO iProcess Web Services Server Plug-in in a firewall environment you may receive a WS_LOCERR if the TIBCO iProcess Engine is started before the TIBCO iProcess Web Services Jetty server.