Skip to main content

Creating a IBM WebSphere MQ File Transfer Edition (FTE) bridge agent to a mainframe - Middleware News

This article shows you how to create an IBM® WebSphere® MQ FTE bridge agent, a special FTE agent that can be used to communicate with a mainframe, and explains the special parameters used by the bridge agent.

Prerequisites

  • Basic knowledge of WebSphere MQ FTE
  • WebSphere MQ FTE V7.0.4.1 or later installed on each end. (Bridge agent functionality is not available in earlier versions of WebSphere MQ FTE).

Step 1. Creating the bridge agent

The command to create a bridge agent is fairly standard, but adds certain parameters that are not commonly used on distributed systems. Pay particular attention to the parameters shown in bold:
fteCreateBridgeAgent -agentName  
    -agentQMgr 
    -agentQMgrHost 
    -agentQMgrPort 
    -agentQMgrChannel 
    -bt 
    -bh 
    -bm 
    -bsl 
    -bfe 
    -btz

Example

This command creates a bridge agent on agthost.ibm.com to talk to mainframe.ibm.com:
fteCreateBridgeAgent -agentName FTPAGENT -agentQMgr AGTFTE -agentQMgrHost agthost.ibm.com
-agentQMgrPort 1426 -agentQMgrChannel SYSTEM.DEF.SVRCONN -bt FTP -bh mainframe.ibm.com 
-bm UNIX -bsl en_US -bfe IBM1047 -btz US\Eastern
The bfe parameter is what you will need to confirm with the mainframe team. This example transfers to z/OS using a format of IBM1047. Here is the definition that you get for bfe when using -h on fteCreateBridgeAgent:
Required.  
Defines the file-encoding format of the file stored on the protocol file server.  For example: UTF-8.
You can get all of the possible values by typing fteCreateBridgeAgent -hcs.

Step 2. Import MQSC file

The next step, as for any agent you create, is to import the definitions in the mqsc file after the create bridge command is successful. Using the example above:
runmqsc AGTFTE < FTPAGENT_create.mqsc

Step 3. Edit the ProtocolBridgeCredentials.xml file

Edit the resultant ProtocolBridgeCredentials.xml file. Open the file in your editor and find the following string:
user name
userid that will run the createtransfer command
serverUserId
logon id for the mainframe
serverPassword
password for this userid

Step 4. Start the bridge agent

You can now start the bridge agent in the same way as on distributed FTE servers. Using the example above:
fteStartAgent FTPAGENT

Step 5. Test a file transfer

Test the bridge agent by transferring a text file. The source agent in this example is AGTAGENT (which has already been created). The target is the bridge agent you just created: FTPAGENT. A most important parameter is dce.
fteCreateTransfer -sa AGTAGENT -da FTPAGENT -t text -dce ibm1047 -df
You will need to confirm the parameter ibm1047 with the z/OS team, and then verify that the source file was transferred to the mainframe.
Labels:

Comments

Post a Comment

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Post a Comment
Read more

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...
143 comments
Read more

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...
Post a Comment
Read more