Integrate Sterling B2B Integrator/File Gateway with WebSphere MQ FTE

"Integrate Sterling B2B Integrator/File Gateway with WebSphere MQ FTE" table of contents

  1. Integrate Sterling B2B Integrator/File Gateway with WebSphere MQ FTE
  2. Configure WebSphere MQ FTE
  3. Configure Sterling B2B Integrator
  4. Configure Sterling File Gateway
  5. Test the solution & Summary

IBM has several Integration Solutions and several File Transfer Solutions. Often aimed at different use-case scenarios. Sterling B2B Integrator and Sterling File Gateway is often seen as B2B Gateway solutions to integrate external partners to your self. IBM WebSphere MQ File Transfer Edition (MQ FTE) is maybe more seen as an internal File Transfer Solution. Technically there is no such limit to where it could be used, but all the solutions has its pros and cons.

In this Post I will integrate Sterling B2B Integrator/Sterling File Gateway with IBM WebSphere MQ FTE. So the scenario here is typically for those having both Sterling B2B Integrator/Sterling File Gateway and WebSphere MQ FTE. Probably not the most common Use Case, but I did show this as a Proof of Technology Use Case to a customer asking for just this type of connection.

The Blog Post is quite long, so I have divided it into several parts. One for the Configuration of WebSphere MQ FTE, one for the Configuration in Sterling B2B Integrator, one for the Configuration of Sterling File Gateway and lastly one for Summary and Test of the solution.

Prerequisites

In this example I have used one of my Sterling B2B Integrator Nodes installed in a previous post. And the File Gateway installed on top of that B2B Integrator Node. I also have a Windows Server 2012 R2 running where I have WebSphere MQ 8.0 installed. So this is the servers involved and used in this example.

"Integrate Sterling B2B Integrator/File Gateway with WebSphere MQ FTE" table of contents

  1. Integrate Sterling B2B Integrator/File Gateway with WebSphere MQ FTE
  2. Configure WebSphere MQ FTE
  3. Configure Sterling B2B Integrator
  4. Configure Sterling File Gateway
  5. Test the solution & Summary

4 comments on “Integrate Sterling B2B Integrator/File Gateway with WebSphere MQ FTEAdd yours →

  1. Hello,

    First of all thank you for this guide.
    I am trying to follow it, however the adapter fails to start and I get this in the error log file of the queue manager:

    AMQ9777: Channel was blocked

    EXPLANATION:
    The inbound channel ‘SYSTEM.DEF.SVRCONN’ was blocked from address
    ‘192.168.88.84’ because the active values of the channel matched a record
    configured with USERSRC(NOACCESS). The active values of the channel were
    ‘CLNTUSER(sterling)’.
    ACTION:
    Contact the systems administrator, who should examine the channel
    authentication records to ensure that the correct settings have been
    configured. The ALTER QMGR CHLAUTH switch is used to control whether channel
    authentication records are used. The command DISPLAY CHLAUTH can be used to
    query the channel authentication records.

    The user sterling is the one who runs the integrator and he is also added on the MQ machine and the mqm, FTAGENTS and FTUSERS groups.

    Any ideas on what I might be doing wrong? Thanks in advance.

    1. Hi,

      It is a long time since I did this, and I have just replaced my laptop, and have not yet moved my MQ server to my new Mac, so I am not able to go back and check this. But it has to do with the default authentication in MQ, and that is a field of expertise by itself. I remember that I pretty much disabled all security in my MQ to get rid of the hassle since it is an internal test solution anyway and the fact that MQ is not my field of expertise. I think you could try to run MQSC command ALTER QMGR CHLAUTH(DISABLED) to disable all security. This is of course only if this is a test solution where security isn’t a concern. If not, talk to someone who knows MQ and the security settings in MQ to give the Sterling User the correct access rights.

      1. Thank you for the reply.

        Just for the record, I was able to make it work by:
        – creating a new server-connection channel
        – creating a channel authentication record for the sterling user in that channel
        – using that channel when configuring the adapter in sterling
        – running the addSpoke script again and setting the agentIPAddress to the sterling ip address
        – authorizing the user sterling to put/get/inquire messages in the reply queue

        I’m sure there is a better way to do it, but this worked for me.
        Anyway, again thank you for this great guide.

Leave a Reply to Erlend Cancel reply

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

%d bloggers like this: