Topic
  • 3 replies
  • Latest Post - ‏2014-06-10T06:26:34Z by mark99
Anshul_kumar
Anshul_kumar
13 Posts

Pinned topic Issue with starting Multiple assembly lines from command prompt in TDI

‏2014-06-09T08:32:25Z |

We have 8 services (All DSML adapters) and we are required to run then all together using a .sh file. We are able to run one TIMListener (Assembly line) at a time but the moment we try to run the next one it says the address already in use and throws a network bind issue. We are using this command for running one AL at a time:

nohup ./ibmdisrv -c"<path of the xml file>" -r"TIMListener" &

 

This works fine for one AL at a time but the moment we start a new listener with this we start getting address bind issue.

Any Suggestion? We have a default TDI server and all listeners are listening on separate ports. Also this works fine when we do it using the GUI, no issue at all. Not able to understand what is the issue here when we try to run it from command prompt.

Is there a way to run multiple assembly lines using one command.

  • yn2000
    yn2000
    1112 Posts

    Re: Issue with starting Multiple assembly lines from command prompt in TDI

    ‏2014-06-09T14:06:46Z  

    When you use the GUI you  are turning-on one server. If you call one ibmdisrv you are also turning on one server. If you call ibmdisrv twice, then you are turning on two servers, while each server needs its own port. Note: I am not talking about the port of the TIMListener, but the API port of the server. The setting of the API port is in the solution.properties. So, I don't know how you configure two TIMListener ALs, but please keep that principal in mind.

    Rgds. YN.

  • Anshul_kumar
    Anshul_kumar
    13 Posts

    Re: Issue with starting Multiple assembly lines from command prompt in TDI

    ‏2014-06-10T05:35:49Z  
    • yn2000
    • ‏2014-06-09T14:06:46Z

    When you use the GUI you  are turning-on one server. If you call one ibmdisrv you are also turning on one server. If you call ibmdisrv twice, then you are turning on two servers, while each server needs its own port. Note: I am not talking about the port of the TIMListener, but the API port of the server. The setting of the API port is in the solution.properties. So, I don't know how you configure two TIMListener ALs, but please keep that principal in mind.

    Rgds. YN.

    We changed the value of api.remote.on to false from true in the solutions.properties and this was resolved. We are able to start multiple AL's now simultaneously.

  • mark99
    mark99
    26 Posts

    Re: Issue with starting Multiple assembly lines from command prompt in TDI

    ‏2014-06-10T06:26:34Z  

    We changed the value of api.remote.on to false from true in the solutions.properties and this was resolved. We are able to start multiple AL's now simultaneously.

    hi 

     

    other option is to start one tdi server and use the tdisrvtl command to start the assembly lines

    tdisrvctl  -h 127.0.0.1 -p 1098 -op  start -c "id feed" -r "id feed xcess add modify"

    you can also send parameters tot your assembly line

    tdisrvctl  -h 127.0.0.1 -p 1098 -op  start -c "id feed" -r "id feed xcess add modify" -alop $initialize {dodelta:false} 

    or wait till it is finished

    tdisrvctl  -h 127.0.0.1 -p 1098 -op  start -c "id feed" -r "id feed xcess add modify" -sync -listen