Originally posted by: cemeinz

Hello!

I have serious problems using the new WebSphere FTP Adapter.

Well, I followed the whole bunch of information and setting provided in the on-line library and the 1147.pdf (which deals with this adapter).

As a summary: I could not write a file to a FTP server using the new adapter.

If I switch back to the old "deprecated" one, everything works fine and the files were written onto the FTP server. If I used a third party product (for example FTP plug-in for Firefox 2) I was able to write onto the server, too.

I am using WTX 8.2.0.1 (build 16).

The log file indicates: "Target not available" with map status="error" map return="9" and adapter return "-13" for the output card.

With enabled tracing, i received the following error:
java.lang.NullPointerException at com.ibm.websphere.dtx.j2ca.MConnectionImpl.connect (Unknown Source).

Maybe some could provide a working example or a better "walkthrough" than the one delivered by IBM.

Regards!
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

I get the same problem trying to ftp to a fujitsu VME mainframe. It seems to fail when it tried to do an unsupported ftp command on the receiving server, in this case PWD. I've raised a pmr for this 41400.999.866 but haven't heard anything back yet. I think they're too busy with SP2 due at the end of the month.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Please try adding to the command line: -mcf:customParserClassName com.ibm.j2ca.ftp.util.FTPLongListEntryParser
This is an advanced option for FTP adapter used to parse "ls -l" output.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: janhess

That didn't change my result.

<2340-904>: 14.15.40.546 - 05/20/2008 JCA Tracing: ftpaddress ## PASS *****
<2340-904>: 14.15.40.609 - 05/20/2008 JCA Tracing: ftpaddress ## 230 User :username logged in
<2340-904>: 14.15.40.609 - 05/20/2008 JCA Tracing: ftpdaddress ## PWD
<2340-904>: 14.15.40.609 - 05/20/2008 JCA Tracing: fttpaddress ## 502 PWD not implemented
<2340-904>: 14.15.40.609 - 05/20/2008 javax.resource.ResourceException: An error occurred in while getting the physical connection the EIS
<2340-904>: 14.15.40.609 - 05/20/2008 java.lang.NullPointerException

at com.ibm.websphere.dtx.j2ca.MConnectionImpl.connect(Unknown Source)
<2340-904>: 14.15.40.609 - 05/20/2008 Error code: -13 , Error message: null

Message was edited by: janhess
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

A set of command options is still not working. Can you post the command line, leaving all confidential info out?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

-TV D:\wtx82\.metadata\FTPtrace.MTR -is:maxRecords 100 -is:createFileIfNotExists false -is:fileInLocalDirectory false -is:secondServerPortNumber 21 -is:splitCriteria 0 -is:localArchivingEnabledForCreate false -is:secondServerProtocol FTP -is:deleteOnRetrieve false -is:functionName Create -is:ExecuteFTPScript ftpscript.txt -is:generateUniqueFile false -wtx:ispec com.ibm.j2ca.ftp.FTPFileInteractionSpec -mcf:customParserClassName com.ibm.j2ca.ftp.util.FTPLongListEntryParser -wtx:record com.ibm.j2ca.ftp.record.FTPInputStreamRecord -mcf:userName UserName -mcf:password ******* -mcf:hostName HostMachine

I have tried this with and without -is:ExecuteFTPScript ftpscript.txt but it makes no difference.

Message was edited by: janhess
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

I have tried to send a file to a Windows server but still get an error.Using these parameters
-TV+ D:\wtx82\.metadata\FTPtrace.MTR -is:maxRecords 100 -is:createFileIfNotExists true -is:fileInLocalDirectory true -is:splitCriteria 0 -is:localArchivingEnabledForCreate false -is:deleteOnRetrieve false -is:functionName Create -is:generateUniqueFile false -wtx:ispec com.ibm.j2ca.ftp.FTPFileInteractionSpec -wtx:record null -mcf:userName username -mcf:filename test -mcf:password ****** -mcf:hostName hostname
The example map has the input file data in filename on the output card. I don't think this is correct. However, I'm not sure where to specify the data to transfer in the output card.

The error in this case is

<3204-2524>: 10.50.11.546 - 05/21/2008 JCA Tracing: ftpaddress ## PASS *****
<3204-2524>: 10.50.11.546 - 05/21/2008 JCA Tracing: ftpaddress ## 230 User CLAS logged in.
<3204-2524>: 10.50.11.546 - 05/21/2008 JCA Tracing: ftpaddress ## PWD
<3204-2524>: 10.50.11.546 - 05/21/2008 JCA Tracing: ftpaddress ## 257 "/" is current directory.
<3204-2524>: 10.50.11.546 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: ftpaddress ## MODE S
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: ftpaddress ## 200 Mode S ok.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.562 - 05/21/2008 JCA Tracing: Added connection event listener: com.ibm.j2ca.base.internal.WBIDefaultConnectionManager@7fe87fe8
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Using the default PasswordCredential
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Getting connection to EIS
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Received connection to EIS
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.578 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.578 - 05/21/2008 Warning: transactions disabled: EIS does not support local transactions
<3204-2524>: 10.50.11.578 - 05/21/2008 Connection opened
<3204-2524>: 10.50.11.578 - 05/21/2008 Calling Begin Transaction
<3204-2524>: 10.50.11.578 - 05/21/2008 maxRecords = 100
<3204-2524>: 10.50.11.578 - 05/21/2008 createFileIfNotExists = true
<3204-2524>: 10.50.11.578 - 05/21/2008 fileInLocalDirectory = true
<3204-2524>: 10.50.11.578 - 05/21/2008 splitCriteria = 0
<3204-2524>: 10.50.11.578 - 05/21/2008 localArchivingEnabledForCreate = false
<3204-2524>: 10.50.11.578 - 05/21/2008 deleteOnRetrieve = false
<3204-2524>: 10.50.11.578 - 05/21/2008 functionName = Create
<3204-2524>: 10.50.11.593 - 05/21/2008 generateUniqueFile = false
<3204-2524>: 10.50.11.593 - 05/21/2008 JCA Tracing: after getWBIInteractionListener aspect called to obtain interactionMetrics listener
<3204-2524>: 10.50.11.593 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.11.593 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.11.593 - 05/21/2008 Error code: -1003 , Error message: null
<3204-2524>: 10.50.11.593 - 05/21/2008 java.lang.ClassNotFoundException: null

at java.lang.Class.forNameImpl(Native Method)

at java.lang.Class.forName(Class.java:127)

at com.ibm.websphere.dtx.j2ca.MAdapterImpl.createRecord(Unknown Source)

at com.ibm.websphere.dtx.j2ca.MAdapterImpl.put(Unknown Source)
<3204-2524>: 10.50.11.593 - 05/21/2008 Calling End Transaction - Rollback
<3204-2524>: 10.50.12.453 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.12.453 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.12.453 - 05/21/2008 JCA Tracing: Notifying 1 connection listener(s) that client has closed connection handle com.ibm.j2ca.ftp.FTPFileConnection@7f3a7f3a
<3204-2524>: 10.50.12.453 - 05/21/2008 JCA Tracing: Removed connection event listener: com.ibm.j2ca.base.internal.WBIDefaultConnectionManager@7fe87fe8
<3204-2524>: 10.50.12.453 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: ftpaddress ## QUIT
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: ftpaddress ## 221
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: Entering method.
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.12.468 - 05/21/2008 JCA Tracing: Exiting method.
<3204-2524>: 10.50.12.468 - 05/21/2008 Connection closed

Message was edited by: janhess
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

In this last command line "-wtx:record null", it should be "-wtx:record com.ibm.j2ca.ftp.record.FTPInputStreamRecord"
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: janhess

I tried that and got a new error. Why isn't the wizard setting these parameter values correctly or am I just misinterpreting the documentation.
<2488-1672>: 14.23.21.140 - 05/21/2008 JCA Tracing -- SEVERE: CWYFT0104E: Error: The directory path for the Create operation is invalid; it is either NULL or an empty string. Explanation=The directory path is invalid. UserAction=Ensure that the directory path is correct.
<2488-1672>: 14.23.21.140 - 05/21/2008 JCA Tracing: Inside BasePerformanceMonitor aspect Input record is com.ibm.j2ca.ftp.record.FTPInputStreamRecord@0
<2488-1672>: 14.23.21.140 - 05/21/2008 JCA Tracing: Inside BasePerformanceMonitor aspect Active Event Point is com.ibm.j2ca.extension.monitoring.CEI.impl.EventPointLoggerImpl@26562656
<2488-1672>: 14.23.21.140 - 05/21/2008 Error code: -1003 , Error message: Invalid output directory path, it is NULL or empty string. Please specify a valid value, error code:
<2488-1672>: 14.23.21.140 - 05/21/2008 com.ibm.j2ca.base.exceptions.MissingDataException: Invalid output directory path, it is NULL or empty string. Please specify a valid value, error code:

at com.ibm.j2ca.ftp.FTPFileInteraction.execute(FTPFileInteraction.java:280)

at com.ibm.websphere.dtx.j2ca.MAdapterImpl.put(Unknown Source)
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Please try adding -mcf:outputDirectory - mandatory parameter, represents directory on FTP server.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: janhess

What do I specify as the value if it's goung to the root?

I used . and that seemed to work.

However, when changing the connection details for the Fujitsu VME mainframe I I still get the original error.

<2488-2164>: 15.11.36.359 - 05/21/2008 JCA Tracing: hostname ## PWD
<2488-2164>: 15.11.36.359 - 05/21/2008 JCA Tracing: hostname ## 502 PWD not implemented
<2488-2164>: 15.11.36.359 - 05/21/2008 javax.resource.ResourceException: An error occurred in while getting the physical connection the EIS
<2488-2164>: 15.11.36.359 - 05/21/2008 java.lang.NullPointerException

at com.ibm.websphere.dtx.j2ca.MConnectionImpl.connect(Unknown Source)
<2488-2164>: 15.11.36.359 - 05/21/2008 Error code: -13 , Error message: null

Message was edited by: janhess
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: Sarath K Ambadas

Whn you look at the trace,
<2488-2164>: 15.11.36.359 - 05/21/2008 JCA Tracing: hostname ## PWD
<2488-2164>: 15.11.36.359 - 05/21/2008 JCA Tracing: hostname ## 502 PWD not implemented

it says pwd command is not supported. Looks like the FTP service you are connecting to doesnt support pwd command.

The FTP server should support some of the basic RFC 959 commands which are used by the FTP adapter.

USER
PASS
LIST
PWD
DELE
RETR
RNFR
RNTO
STOR
PASV
PORT
NLST

etc

Thanks
Sarath Ambadas
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

I know it doesn't support PWD and some others but the old ftp adapter coped with this. The websphere ftp adapter doesn't and needs to.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: cemeinz

Hello!

It is me again, the author of this thread.

I have made some further steps, but no I have the next error. Attached is my complete trace file.

It indicates, that a file "null" should be transfered. Clearly, what this means, but I am not sure how to specify this parameter right. I have a simple input file and the whole file should be transfered onto the ftp.

Interesting could be the line containing this information: "JCA Tracing -- SEVERE: CWYFT0121E"

Thanks in advance.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

Yes I got a similar error - see earlier post.
I eventually got it to work to a windows server using these parameters

-TV+ D:\wtx82\.metadata\FTPtrace.MTR -is:maxRecords 100 -is:createFileIfNotExists true -is:fileInLocalDirectory true -is:splitCriteria 0 -is:localArchivingEnabledForCreate false -is:deleteOnRetrieve false -is:functionName Create -is:generateUniqueFile false -wtx:ispec com.ibm.j2ca.ftp.FTPFileInteractionSpec -wtx:record com.ibm.j2ca.ftp.record.FTPInputStreamRecord -mcf:outputDirectory directory name -mcf:userName username -mcf:filename filename -mcf:password PASSWORD -mcf:hostName hostname

If you want to send it to the root directory use .
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: cemeinz

Hello!

Thanks for this quick reply.

Well, i double-checked your settings with mine, enabled some variable from false to true, but I am still not able to write a file onto our FTP server.

Here is the concrete part of the trace file:

16.42.29.286 - 05/23/2008 JCA Tracing: Entering method.
16.42.29.301 - 05/23/2008 JCA Tracing -- SEVERE: CWYFT0121E: Die Datei null ist entweder ungültig oder nicht im angegebenen Verzeichnis /support/ für die Outbound-Operation CREATE vorhanden. Explanation=Beim Überprüfen, ob die Datei vorhanden ist, ist ein Fehler aufgetreten. UserAction=Stellen Sie sicher, dass die Datei in dem angegebenen Verzeichnis vorhanden ist, und wiederholen Sie die Aktion.
16.42.29.301 - 05/23/2008 Error code: -1003 , Error message: Invalid output file name, its NULL or empty string, error code:
16.42.29.301 - 05/23/2008 com.ibm.j2ca.base.exceptions.MissingDataException: Invalid output file name, its NULL or empty string, error code:
at com.ibm.j2ca.ftp.FTPFileInteraction.validateFileName(FTPFileInteraction.java:1374)

It is in german, because the system is in german.

The information is still: File null not valid or not in the path /support/ for this outbound operation CREATE available. The system tells me to check, that the file is not there.

So, which file is mentioned here? My input file? This is available in Input Card 1. My output file? I added your command parameter "-mcf:filename FILENAME" (FILENAME=File name from input card 1).

What did I do wrong?

Thanks in advance!
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

Are you sure your file name is in the correct format for the receiving machine and that you are actually getting a file name from the input card.
The error is Invalid output file name, its NULL or empty string.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: cemeinz

Hello!

I enabled a new output card with mapping rule "GETFILENAME()" and this rule returns the right file name (the one I specified).

About the correct format: well, i simply choosed "out.txt" and this should work on a Debian FTP Server.

About the output file name: I used the command line parameter for this and put out.txt as the file name.

The payload itself is put into the XSD/global/FTPFile/sequence/Content/sequence/AsBinary XML field with mapping rule =InputFile or =Package(InputFile).

Thanks in advance.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Did you try "-is:filename FILENAME" instead of "-mcf:filename FILENAME"?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: cemeinz

Hello!

Finally, I did it. And it worked.

It worked once before your posting, then I delete the parameter for file name, because I want to name it dynamically using the appropiate XSD field.

This did not work either.

After swichting back to the static way, I used "mcf" instead of "is". Turning back to "is" makes the mapping runs successfully.

At this point, I wish to thank everybody who was involved in this issue.

Next topic should be "how to use the xsd fields" right.

Any suggestions? Is this buggy or works this well? Static parameters are not the way, we / I build maps .

Thanks guys / girls.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

The only way for WS FTP adapter to get execution parameters is using command line.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: cemeinz

Hello!

This circumstances let the following two question arise:
1) How to put a file and its unique file name via WebSphere FTP Adapter onto a dynamically established FTP connection?
2) Could I throw the FTP.xsd as type tree away and could I use any type tree ? I can use command line options for every type tree, it has not been this specific "FTP WebSphere" type tree.

Kind regards.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange