Sometimes you have to chuckle at the titles of PMRs. I came across this one today:

“Information not included in the user guide for IBM WebSphere Adapter for FTP V6.0.2”

Where they admit they forgot very minor details like the fact you have to create all the directories manually or the ftp location where inbound events will actually get picked up from.

More interesting, it looks like you can expect an outage once every four years:

The default parser provided by Commons Net API v1.4.1 fails to handle files with Feb 29 as the creation date.

and of course, you know when WebSphere Integration Developer tells you that it aborted something? Oh, you should just ignore that:

4. When using the enterprise service discovery wizard, the following informational message is displayed in the log: ‘Aborting DataBinding Generation type specified is not a DataBinding Generator: com.ibm.j2ca.ftp.FTPFileDataBinding’.
You can ignore this message and continue working.

If it’s an ignorable warning, why is it generated in the first place?

Related Posts

• Asynchronous SCA One-Way Operations And How To Recover
• Exploring The Contents of a WID Module Project
• WebSphere 6.1 and Jakarta Commons Logging (JCL) using Log4J in an EJB
• Venting some WebSphere Integration Developer Steam
• WebSphere Default Messaging (SIBus) and WebService Error Handling

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.