Integrations running in IBM Integration Bus (IIB) on Cloud can now seamlessly connect to on-premises systems over a secure connection. Using the simple IIB on Cloud web UI, on-premises endpoints can be defined in the cloud to allow integrations to access them via a secure connection to an On-Premises agent.

In the first release of this connectivity function access to MQ queue managers and DB2 databases has been added. Other endpoint types will be added in the future, and please feel free to comment below on which types of endpoint access you would like to see added next.

It is now possible to take message flows that access both MQ and DB2 and deploy them to IIB on Cloud without making any modification. Integrations can be moved from on-premises IIB to IIB on cloud in a matter of minutes without complex installs or configuration being required.

For more details about IIB on Cloud see an introduction to using IBM Integration Bus on Cloud.

8 comments on"Secure connectivity to on-premises systems is now available in IIB on Cloud"

  1. Hi, is it possible to connect IIB on premise message flows to some other applications which runs on cloud?

  2. 2JBG_BRIAN_LEE June 12, 2017

    Hi there:

    Regarding the IIBoC agent configuration file.

    The following was found in the IIB v10 infocenter,
    “Because the agent is a component of IBM Integration Bus, you must download the agent configuration file to the same location as IBM Integration Bus.”

    Can some one elaborate on “same location as IBM Integration Bus”?

    Does that mean that the agentp.json must be downloaded to the directory where my local IIBSWITCH_NODE is running? In my case, C:\Program Files\IBM\IIB\\server

  3. 2JBG_BRIAN_LEE June 12, 2017

    Hi there:

    Regarding “It is now possible to take message flows that access both MQ and DB2 and deploy them to IIB on Cloud without making any modification”.

    I have setup and tested that my “Endpoint connectivity” in IIBoC is working (i.e. connecting to my queue manager running on premise).

    I then successfully deployed simple BAR (with a HTTP Node->Compute Node->MQ Output Node->HTTP Reply Node), I was able to invoke the web service and get a reply. However, no message was ever put in the MQ queue.

    I deployed the same BAR to IIBoP (i.e. local broker) and it is behaving as expected (i.e. put a message in the queue and reply to the HTTP Request).

    Any suggestion/advice is greatly appreciated.

    • CU99_john_reeve June 12, 2017

      It is strange that you are getting a reply back from the HTTP Reply node but the MQOutput node did not seem to put a message to a queue. Does the reply you get from the http request contain any error information? Also, it is possible to download the logs for the running bar file in the web ui. It would be worth checking those to see if there is an MQOutput error message along with an mq error code.
      Regards, John.

      • 2JBG_BRIAN_LEE June 12, 2017

        Hi John:

        Thanks for the quick response.

        I am getting the following error in the log.
        2017-06-12 18:13:48.153172: [Thread 343] (Msg 3/3) BIP2678E: Failed to make a server connection to queue manager ‘BROKER10’: MQCC=2; MQRC=2568.

        I am an experienced MQ and IIB developer/admin. My question then is:
        In MQOutput node, what else (i.e. aside from the MQ queue name) do I need to specify? The same flow is running on IIBoP without any problem.

      • 2JBG_BRIAN_LEE June 13, 2017

        Hi John:

        I solved the issue by following a post on:

        Turned out that I have to “set up the policy name for the MQ nodes in the Integration Toolkit, you need to use ‘/MQEndpoint/policy_name’.
        The ‘policy_name’ should match what you specify for MQ Endpoint connectivity in IIB on Cloud.”

        The message was put into the queue successfully after I set the policy name on the MQOutput node.

  4. we should be able to add FTP/SFTP endpoints to fetch the files and drop to the on-premise ftp servers.

Join The Discussion

Your email address will not be published. Required fields are marked *