You are invited to attend a webcast on the topic of WebSphere Partner Gateway 6.2.0 - Configuring to use the SFTP Protocol.
On 23 April 2009 at 11:00 AM EDT, a WebSphere Support Technical Exchange presentation on WebSphere Partner Gateway 6.2.0 - Configuring to use the SFTP Protocol will be delivered by Max Terpolilli, a subject matter expert. An open question and answer session will follow the presentation.
This presentation focuses on the implementation of the SFTP protocol, configuration of the SFTP Receivers and Destinations, creation and installation of key pairs, and setup of an end-to-end scenario for test transmissions. Screen shots of successful and unsuccessful transactions are also included.
Level of Difficulty: Intermediate
Plan to join the meeting 10 minutes early. Presentations typically last for 30-45 minutes followed by a question and answer session. For more information and details on how to participate in this and other free WebSphere Support Technical Exchanges click here.
Date: April 23, 2009
Time: 11:00 AM EDT
For dial-in numbers and web conferencing information, please visit:
We look forward to seeing you on the webcast.
This topic has been locked.
5 replies Latest Post - 2011-01-02T03:35:06Z by sfishman
Pinned topic WPG 6.2.0 - Configuring to use the SFTP Protocol Webcast on April 23, 2009
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-01-02T03:35:06Z at 2011-01-02T03:35:06Z by sfishman
Re: WPG 6.2.0 - Configuring to use the SFTP Protocol Webcast on April 23, 20092009-04-17T15:40:59Z in response to josephlamSFTP is a problem area in WPG. We are currently facing some issues while trying to implement it in our integration framework.
Are there any Fix available for the issues with SFTP ?
Two issues which we are facing right now is :
1. SFTP Destination : WPG is not preserving the original filename when writing files to SFTP Destination, instead WPG is renaming the files using the WPG's internal Message ID.The Message ID is always 47 characters. (Eg : 1238756734008001A64A80A2B815184C14DB58D4DAF9269.vcm).
2. SFTP Receiver : No PreProcess Handlers are associated with the Receiver. Generic Document Flow handler is needed to set the Sender and Receiver for the messages. Without this handler, WPG is not able to identify the Sender and Receiver for Binary files received over SFTP Transport.
Re: WPG 6.2.0 - Configuring to use the SFTP Protocol Webcast on April 23, 20092009-04-20T18:51:08Z in response to SystemAdmin1. WPG is not preserving the original filename when writing files to SFTP Destination
There is an APAR, JR32312, that supposedly fixes this problem. The fix will ship 4/20/09 barring any problems that arise during testing.
sfishman 0600021T4U4 PostsACCEPTED ANSWER
Re: WPG 6.2.0 - Configuring to use the SFTP Protocol Webcast on April 23, 20092010-12-28T05:53:56Z in response to SystemAdminHow does one get SFTP receiver to function like FTP receiver with respect to None;Binary;Binary? Can you outline the solution? Apparently, can't use a filename of <TargetPartner>.<filename> as with ftp, and also can't use a convention of <doc_root>/<sourcePartner>/Binary/Production either. This seems like a common situation and I am searching for how to do it. Note below from Sovic references Generic Document Flow Handler. Can you elaborate? Is that a user exit that will just simply read some kind of filename convention that we make up such as <sourcepartner>.<targetpartner>.filename?
Re: WPG 6.2.0 - Configuring to use the SFTP Protocol Webcast on April 23, 20092010-12-29T20:01:02Z in response to sfishmanYou can have a dedicated SFTPReceiver for a given partner pair. Hardcode the senderid, receiverid, package, protocol and document type in the GeneridDocumentHandler available in the preprocessor handler option of the SFTP Receiver.
Let me know if this satisfies your requirement.
sfishman 0600021T4U4 PostsACCEPTED ANSWER
Re: WPG 6.2.0 - Configuring to use the SFTP Protocol Webcast on April 23, 20092011-01-02T03:35:06Z in response to SystemAdminThank you. Looking for something better because that will mean a receiver will only handle one partner to partner situation. I would rather have receiver as platform to platform instead but partner independent.
FTP receiver works this way, with one receiver listening to as many directories as you like, each directory associated with a diff partner source but by file name, can be sent to any target partner.
I was wondering of FTP/S will do the same, or is this particular behavior in FTP receiver limited to only FTP (non-encrypted).