I've configured an AL as seen on TDI_AMC_Guide, so i can access it with AMC. when running the AL with "ibmdisrv.bat -c al.xml -d" - the AL runs fine, and listens on port 1099, and i can access it as i should with AMC.
When I make this AL run as a windows service (using ibmdiservice), the AL runs fine, but doesn't listen on port 1099, and of course i can't access it from AMC.
I've tried several ibmdiservice.props cmdoptions - but no luck.
Any ideas?
PS - it works fine on TDI 6.0's service on a different box.
The RMI interface of the Server API uses port 1099 (by default) to handle commands from clients (AMC, tdisrvctl, ...). The Server will execute AssemblyLines even if the Server API fails to start. Are there any error messages in ibmdi.log which indicate that the Server API has not started ?
Do you have a message like this in your ibmdi.log : "CTGDKD023I Remote API Engine successfully initialized. SSL and Client Authentication are enabled." ? Check if the API is enabled in the solution.properties file in the folder specified by "ibmdiroot" in your ibmdiservice.props file. Also check the etc/global.properties file in that folder. If the API is enabled (api.on=true & api.remote.on=true), then you should contact the L2 support guys.
|
