| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| CDInput Node with remote C:D Server |
« View previous topic :: View next topic » |
| Author |
Message
|
| fvclaus |
 Posted: Tue Feb 25, 2014 8:10 am Post subject: CDInput Node with remote C:D Server |
 |
|
Newbie
Joined: 25 Feb 2014
Posts: 5
|
I am new to Connect:Direct and have a question regarding the CDInput node:
Is it necessary to have direct access to the C:D files either via a network share or by running on the same machine with file access permissions?
In my scenario, I need to fetch files from a remote C:D server where I do not have any other form of access. My first intuition, with exactly zero knowledge of C:D, was that the CDInput can just fetch the files via the network from the C:D server. After reading the Getting Started, User and Adminstration guide of C:D, I believe that either my Broker needs to run on the same server as the C:D server (connecting to localhost) or share the files via a network share. There is also a section in the WMB Help Center that says:
| Quote: |
| If the directory is remote, the directory must be mounted to the WebSphere Message Broker machine. If the mounted file system has a different path on the WebSphere Message Broker machine, the brokerPathToInputDir must be set to the correct value. |
I have also read everything else in the Help Center about C:D, but I am still not certain enough to open up a ticket to the create a network share as this will effect dozens of other interfaces which must be migrated to WMB.
Thanks in advance for the clarification |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Feb 25, 2014 10:08 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The point of having Connect:Direct is to facilitate the movement of files from one server to another. Hence you'd use the CDInput node to conenct to the C agent running locally on your server (which would be configured to use local disc & access rules) and that agent would communicate with it's counterpart on the remote machine to move the file.
If you want to just use mounted shared disk, use the FileInput node
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Tue Feb 25, 2014 2:22 pm Post subject: Re: CDInput Node with remote C:D Server |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| fvclaus wrote: |
I am new to Connect:Direct and have a question regarding the CDInput node:
Is it necessary to have direct access to the C files either via a network share or by running on the same machine with file access permissions? |
Simple answer is yes. You need to run the broker on the same machine as CD or you need some sort of shared storage.
Alternatively,as Vitor says, you could just use the file input node.
I guess there are some pros and cons for each. E.g.
1) File input node polls whereas the CD Input node does not so there will be some delay in picking up the files using the file node. The polling interval is configurable so the smaller the value the less delay. The CD node picks the files up pretty much as soon as they arrive.
2) File nodes have been around a long time so maybe are a bit more robust.
3) File nodes can pick up incomplete files so you might need an additional 'move' step in the process. Not sure if the CD nodes can pick up incomplete files but the CD file transfer gives you the ability to add the move step to the transfer process.
4) CD node can only pick up files transferred by CD whereas the file node will pick up any file matching the file pattern and directory specified in the node.
Anyone like to add to / contradict this list?
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 25, 2014 4:43 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| This is the only time I've ever considered smiling in the context of working with C |
|
| Back to top |
|
|
| fvclaus |
| Posted: Thu Feb 27, 2014 7:56 am Post subject: Re: CDInput Node with remote C:D Server |
|
|
Newbie
Joined: 25 Feb 2014
Posts: 5
|
Thank you all for your quick replies. We are going to use a network share now.
| fatherjack wrote: |
| 1) File input node polls whereas the CD Input node does not so there will be some delay in picking up the files using the file node. The polling interval is configurable so the smaller the value the less delay. The CD node picks the files up pretty much as soon as they arrive. |
The documentation states that the polling interval is fixed at one second:
| Quote: |
| The input node does not poll for transfers, but is triggered instead when they arrive. However, the Connect:Direct server manager does need to poll for events to notify the CDInput node about a transfer. The Connect:Direct server manager has a polling interval of one second. |
You could also set the polling interval of the FileInput node to 1 sec. Assuming that the 4 sec difference from the 5 sec default value are important.
| fatherjack wrote: |
3) File nodes can pick up incomplete files so you might need an additional 'move' step in the process. Not sure if the CD nodes can pick up incomplete files but the CD file transfer gives you the ability to add the move step to the transfer process. |
This sounds like a problem. Does C:D not have a staging directory where incoming files are stored and, when complete, moved to the target directory?
I still don't understand the advantage of using a CDInput node versus a FileInput node. FileInput nodes are more flexible and easier to configure. If file access is always needed, isn't it possible to always replace a CDInput node with a FileInput node? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Feb 27, 2014 8:19 am Post subject: Re: CDInput Node with remote C:D Server |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fvclaus wrote: |
| fatherjack wrote: |
3) File nodes can pick up incomplete files so you might need an additional 'move' step in the process. Not sure if the CD nodes can pick up incomplete files but the CD file transfer gives you the ability to add the move step to the transfer process. |
This sounds like a problem. Does C not have a staging directory where incoming files are stored and, when complete, moved to the target directory? |
Yes, that's exactly what my worthy associate is saying. A FileInput node can pick up an incomplete file, a CD node will not.
| fvclaus wrote: |
| I still don't understand the advantage of using a CDInput node versus a FileInput node. FileInput nodes are more flexible and easier to configure. If file access is always needed, isn't it possible to always replace a CDInput node with a FileInput node? |
Aside from the advantage above, the CD node interfaces directly with the CD agent software running on the server. So you have access to all of the facilties of CD. The FileInput node just polls a directory.
And yes, you can always replace a CDInput node with a FileInput node. But if you're using CD to perform the file transfer (as you must be or you wouldn't be considering which node to use), what advantage would this give you?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
