App Connect

 View Only

  • 1.  Running Standalone Integration server as a Linux service or as a task/background task

    Posted 20 days ago

    Hi All,

    ACE Version 12.0.11.0 and Redhat Linux.

    I have a standalone Integration Server created and I can start if fine on Linux.

    I want to run the this standalone IS as a service or as a task.

    as it is now , when I start it with IntegrationServer command, it does not run as a task under Linux.

    How would I do this?

    Emile



    ------------------------------
    Emile Kearns
    ------------------------------


  • 2.  RE: Running Standalone Integration server as a Linux service or as a task/background task

    IBM TechXchange Speaker
    Posted 20 days ago

    Hi Emile, 

    Standalone integration servers are intended to be run in containers where their lifespan matches that of the container they are running in ... which would typically occur in a system such as Kubernetes / OpenShift where an operator is then available to manage the containers. If this is not the case, and you are intending to just run the product outside of containers in a standard on-metal install, then you should utilise an integration node owned server (it is the purpose of the node process to "look after" the integration servers from the admin and health standpoint).

    Cheers,

    Ben



    ------------------------------
    Ben Thompson
    IBM UK
    ------------------------------

    Original Message


  • 3.  RE: Running Standalone Integration server as a Linux service or as a task/background task

    Posted 19 days ago

    Thanks Ben, much appreciated.

    Just a side question, if we use the OS function, like in Linux, running it with & to indicate it is to run as a back ground task, would that suffice?



    ------------------------------
    Emile Kearns
    ------------------------------

    Original Message


  • 4.  RE: Running Standalone Integration server as a Linux service or as a task/background task

    Posted 17 days ago

    Your user id that is starting the Integration Node needs to execute mqsiprofile in the /opt/IBM/ace-{version}/server/bin/mqsiprofile.

    Usually best to have a service id created you can sudo to then you can modify its .bash_profile to execute the mqsiprofile and setup the ODBCINI and ODBCINST environment variables if your using native ODBC database access to your databasses.

    When you issue the mqsistart INODE-Name

    it will run in background automatically. 

    You use mqsistop to stop it.  See mqsi commands for more info.



    ------------------------------
    Robert Rehms
    ------------------------------

    Original Message


  • 5.  RE: Running Standalone Integration server as a Linux service or as a task/background task

    Posted 11 days ago

    We run multiple Independent Integration Server successfully like this on a Linux box:

    $ cat /etc/systemd/system/ace\@.service
    [Unit]
    Description=IBM App Connect Enterprise - Independent Integration Server %I
    Wants=network.target
    After=network.target
     
    [Service]
    EnvironmentFile=/var/ace/%I/environment.txt
    WorkingDirectory=/var/ace/%I/
    Type=simple
    ExecStart=/bin/bash -c '\
      source /opt/IBM/mqsi/${ACE_VERSION}/server/bin/mqsiprofile && \
      exec IntegrationServer --name %I --work-dir /var/ace/%I'
    KillSignal=SIGINT
    # ACE exits with return code 0 when Default Remote Queue Manager can not be
    # reached. This is why we have to set 'always'.
    Restart=always
    RestartSec=5s
    User=ace
    Group=mqbrkrs
     
    [Install]
    WantedBy=multi-user.target



    ------------------------------
    Daniel Steinmann
    ------------------------------

    Original Message


  • 6.  RE: Running Standalone Integration server as a Linux service or as a task/background task

    Posted 10 days ago

    Thanks, we will try this. In the meantime, we created an INode



    ------------------------------
    Emile Kearns
    ------------------------------

    Original Message