Batch Client Started Without Wrapper Using Script batch_nowrapper(.cmd) - returns FMS-Interface: Connection Failed (Errorcode: -305) - When Performing File checkin or File checkout (Doc ID 1933674.1)

Last updated on JULY 11, 2016

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.3.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
--------------------------
On Agile e6.1.3.0 GA and HF0005

When attempting to execute a file checkin or file checkout with the batch client started without the wrapper
receiving error
... Scenario: Message received: I:Server Message: FMS-Interface: Connection failed (Errorcode: -305) ...


STEPS:
---------------------
1.) In PLM prepare a document to have a file assigned
2.) Create a LogiView Procedure to checkout the file to the client - e.g. "SCE/CliChkOutBatch"
3.) Prepare Batch client to execute a simple scenario calling the LGV to checkout the file to the client
Therefore modify files:
- %ep_root%\examples\LGVCall.groovy (configure LGV "SCE/CliChkOutBatch")
- %ep_root%\examples\LGVCall.properties
- %ep_root%\cmd\batchclient_nowrapper.cmd (needs JAVA_HOME setting)

4.) Run the batch client started with script "batchclient_nowrapper.cmd"
e.g.
batchclient_nowrapper.cmd -i %ep_root%\examples\LGVCall.groovy -p %ep_root%\examples\LGVCall.properties -T %ep_root%\axalant\ini\testclient.properties
5.) Receive error
Server Message: FMS-Interface: Connection failed (Errorcode: -305)


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms