Messages from Adapter framework to IS disappear

[Former Member]

During processing of interfaces, it happens some times that the sending of messages from Adapter Framework to Integration Server is broken but no status message is traced. Before this break, the messages’ state is correctly visible on integration server (SXMB_MONI), after that, messages are no more contained in persistence layer of the adapter framework or of the integration server. So it’s very difficult to know which messages have been processed, and for this reason there is a great effort for application/functional team to reprocess interfaces’ file.

After the last succesfully processed message, there are a lot of log messages on application and default trace of this type:

for location com.sap.aii.adapter.file.File2XI.processFileList():

Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'd902100e953f3e15b0e04b3caf9dc415': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available.

Channel CC_File_OUT02_1058: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: Some of the IS access information is not available. SLDAcess property may be set to true, but SLD is not available. - continue processing

Delivery Exception for guid'87b54890-ae37-11da-c751-001125a5fff4' - non recoverable error, retry anyway

For location com.sap.aii.adapter.file.File2XI.addAuditLog( ... ssageKey, AuditLogStatus, String, String,Object[]):

FILE_ERR_211

This behavior is independent of interface type and happens randomly (about 2-3 times a week).

We try, without success, to implement a workaround setting SLDaccess parameter to false for AF CPA cache service and specifying the xiadapter.isconfig.<parameters> for adapter service. With this configuration File Adapter didn’t work and CPA cache didn’t contain any comunicaton channels. Maybe we have to set the correct value of parameter directoryURL (which it is?).

Thank a lot in advance

Danilo Vaccarella

[STALANKI]

Probably your XI post installation steps are not proper/or problem in authorization.

there is note for SAP XI readiness check..search in the maket place for it.

[Former Member]

Thank you for your suggestion, but nothing seems to be wrong in configuration (however I'm contuining my checks). In the meantime, are there other suggestions?

Hi

Danilo

[Former Member]

Problem was solved by applying patch 14 (SP11) of AFW Core (note 935169).

Bye

Danilo