Integrate Sterling B2B Integrator/File Gateway with WebSphere MQ FTE (page 4)

Configure Sterling File Gateway

The last step is to create what is needed in Sterling File Gateway. That is in practice the Producer, Consumer, Routing Channel Template and the Routing Channel.

In this example there will be used a standard Producer that uploads a file through
myFileGateway, a Consumer that is a Agent on WebSphere MQ FTE, and a simple Pass-Through Routing Channel Template, to together create a Routing Channel.

There will also be a Community that the Producer and Consumer is
belonging to.

Create a Community

A Community is not necessary, but doesn’t hurt. The only important thing is that WebSphere MQ FTE is activated as a protocol in the community that is used.

Go to Participants -> Communities to create a new community.

SFG_Community_001

Give the Community a suiting name.

SFG_Community_002

Members of the Community can both initiate and Listen for connections, and the WebSphere MQ FTE Protocol is activated.
SFG_Community_003

Create Partners

A Producer and Consumer need to be created to test the communication.

Create Producer

The Producer is in this case a standard Producer that uploads files through myFileGateway.

Go to Participants -> Partners and select Create.

Select the Community created above.

SFG_Producer_001

Give the producer a name, and other mandatory data.

SFG_Producer_002

Add Username and Password for the user.

SFG_Producer_003

Set the Partner to be a Producer of Data.

SFG_Producer_004

Summary of the Producer Partner.

SFG_Producer_005

Create Consumer

The Consumer will be an Agent on WebSphere MQ FTE. In this case the Agent will be AGENT1 created earlier.

Go to Participants -> Partners and select Create. Use the WMQFTE Community.

SFG_Consumer_001

Add information for the User Account.

SFG_Consumer_002

Set the Partner Role to be Consumer of Data, and that the Partner will listen.

SFG_Consumer_003

Select Listen for WebSphere MQ FTE Connections.

SFG_Consumer_004

Add the necessary information to connect to MQ FTE. Select the Agent Adapter created earlier, and the Agent and Queue Manager as well as the Reply Queue created earlier. The Destination Directory is a folder I have created on my NFS Share for the SB2BI/SFG Cluster.

SFG_Consumer_005

The summary of the Consumer Partner.

SFG_Consumer_006

Create a Routing Channel Template

For this example, I create a simple Routing Channel Template that only does a Pass Through. So it receives a file with any file name, and passes it through without any more logic.

ES_Demo_Passthrough

Create a Routing Channel

I then use the Routing Channel Template, the Producer and the Consumer to create a Routing Channel.

ES_Demo_Passthrough_Channel

I am then ready to test the solution.

"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

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

%d bloggers like this: