Info WebSphere Process Server - File Adapter errors

Once you deploy a mediation module containing a file adapter on a websphere process server and turn on global security, things start going bad.

This mess could manifest itself in very many ways, some of which I encountered are listed below along with their solutions



Problem 1:
Error message : SECJ5010E: Could not create default AuthenticationToken during propagation login. The following exception occurred: com.ibm.websphere.security.auth.WSLoginFailedException: Validation of LTPA token failed due to invalid keys or token type.

Fix: Upgrade WAS to at least 6.0.2.11 (WAS is currently at 6.0.2.27)
Create an entry in Admin Console->Global Security->Addition Properties->Custom properties :
com.ibm.ws.security.createTokenSubjectForAsynchLogin=true




Problem 2:
Error message: CWWBF0060E: Cannot find a specific session EJB component.Process for the process

Fix: Go to the resource view in WID, and clean the respective EJB project of the Module. Then go back to the business integration view and 'clean' the entire module.
You might have to shutdown and restart WID after this. Rebuild the project and deploy. The error will go away.




Problem 3:
Error message: com.ibm.websphere.sca.ServiceRuntimeException: caused by: java.lang.IllegalStateException: No implementation or binding handler was found to process this interaction

Fix: Uninstall the following iFix: 6.0.2.0-WS-WPS-IFJR28515.pak
Better still, upgrade to 6.0.2.4

General Warning about iFixes:
Expect every iFix emitted by IBM to break something in the existing product. You'll often hear of iFixes for iFixes and it is not funny, especially if you are in production. Your best bet is to avoid iFixes if possible.
Better still, upgrade to 6.0.2.4



Problem 4
The file adapter (inbound) doesn't work well at all on Solaris (or any unixy systems). The file adapter doesn't know when the file transfer to the inbound folder is completed and starts reading it the moment its poll interval time is up. The adapter works well on windows as windows locks the file during transfer.

Fix: There is none at this time, unless you just want to just transfer the file to another location without parsing it. (Create a 0 byte .done file for file that is placed in the inbound folder and programatically copy the original file to the destination location. The .done file will be transferred to the archive folder (if archiving is turned on))


Check out the following book that could help you work better with WPS: