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

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 ...
140 comments
Read more

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201...
3 comments
Read more

Message Broker (WMB) installation and setup on Linux

Message Broker (WMB) installation and setup on Linux Installing the Binaries As a first step download the trail version of the message broker binaries from IBM site and install them. this part is very simple and process is depends on your operating system. Like for windows, you have .exe file and Linux has rpm and unix you get pkg or other. After installation Set up a broker database [Windows] __ 1. Create the broker database, BRKDB. Open a WebSphere Message Broker Command Console: mqsicreatedb BRKDB This command also establishes the required ODBC connection. _ 2. Verify your user account for the broker database. [Linux] If you are creating Oracle databases for 32-bit brokers on Linux® and UNIX® systems, run the mqsi_setupdatabase command before you create a database. mqsi_setupdatabase– Database–Database_Home_Directory Eg:mqsi_setupdatabase oracle /oracle/product/9i/Db_1 Add $ORACLE_HOME/lib to the end of the MQSI_LIBPATH library search path environment variabl...
Post a Comment
Read more