Author |
Message
|
saurabh25281 |
Posted: Fri Nov 14, 2014 12:17 am Post subject: MFT file transfer progress stuck at 0% from IIB FTE Output |
|
|
Centurion
Joined: 05 Nov 2006 Posts: 108 Location: Bangalore
|
Hi All,
I am new to MFT and we are trying to setup MFT for file transfer between our IIB and MFT servers.
We have 2 Queue Managers MFTQMGR & IB9QMGR on the MFT and IIB servers respectively.
The configurations are as follows
Coordination Queue Manager: IB9QMGR
Command Queue Manager: MFTQMGR
Agents have been created in the MFT Server by using fteCreateAgent command
./fteCreateAgent -agentName MFT.AGENT -agentQMgr MFTQMGR
At IIB end the agent was created as per the norm BROKER_NAME.EG_NAME i.e. IB9NODE.ISDCOM1
I am able to see the status of both the agents as active from the MFT Server, but not from the IIB server.
The issue is when I send a sample message to my flow containing the FTE o/p nodes, that point to the destination agent MFT.AGENT and a destination folder, the transfer does not take place.
However, from the MQ explorer I can see that a transfer has started, but the progress remains at 0%
Below are the details of the properties file that we have at the MFT server end.
coordination.properties
coordinationQMgr=IB9QMGR
coordinationQMgrHost=elufrmft001
coordinationQMgrChannel=SYSTEM.DEF.SVRCONN
coordinationQMgrPort=2414
command.properties
connectionQMgr=MFTQMGR
agent.properties
agentQMgr=MFTQMGR
agentDesc=
agentName=MFT.AGENT
Apart from these there are a pair of SNDR/RCVR channels between the IIB and MFT queue managers.
So wanted to know from the experts, if there are any configurations that have been left out which might help resolve the problem and start the file transfer, or investigate the cause further?
I can also see FFDC and ABEND files in the logs folder.
BR
Saurabh |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Nov 14, 2014 2:16 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
your coordination channel is a poor choice. Avoid any system objects and make sure any objects you do use have adequate permissions  _________________ MQ & Broker admin |
|
Back to top |
|
 |
saurabh25281 |
Posted: Fri Nov 14, 2014 2:50 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006 Posts: 108 Location: Bangalore
|
Point taken. I will define a different SVRCONN, but should it make any difference, since I am not getting any error message relate to permissions. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Nov 14, 2014 3:04 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
saurabh25281 wrote: |
Point taken. I will define a different SVRCONN, but should it make any difference, since I am not getting any error message relate to permissions. |
Try and see. Also if you have the choice, why use the broker's qmgr as MFT coordination qmgr?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
saurabh25281 |
Posted: Fri Nov 14, 2014 3:19 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006 Posts: 108 Location: Bangalore
|
Tried with a different SVRCONN (MFT.COORD.CHNL), but the result remains the same.
There is no particular reason for the choice of coordination QMgr. But do we have to revert the .mqsc scripts already applied to the existing coordQMgr before making the other side as coordQmgr.
Are you recommending the below configuration?
Coordination Queue Manager: MFTQMGR
Command Queue Manager: MFTQMGR
Is this a best practice to make non-broker Qmgr as coordQmgr? Just curious.
BR
Saurabh Ghosh |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Nov 14, 2014 7:22 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
The coordination queue manager runs a number of extra processes. I just thought I would want isolation from the broker's queue manager and processes.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
saurabh25281 |
Posted: Wed Nov 19, 2014 3:52 am Post subject: |
|
|
Centurion
Joined: 05 Nov 2006 Posts: 108 Location: Bangalore
|
|
Back to top |
|
 |
|