Archive Error Files

[former_member185881]

Hi All

The scenario is like this --

I have created a module in which i am checking for duplicate file. If its not duplicate it is successfully getting processed. now if its found duplicate then i am throwing an exception in module.

In communication channel i have checked mark "Archive Error File" and given the archive directory.

Now when i am checking communication channel under Runtime Workbench --

i can see this Error --

Error : Attempt to process file failed with null.

is this error means my adapter is failed?????

and if my adapter is failed then it should Archive it, but its not Archiving to the specified directory.

Please need a solution for this

REgards

Dheeraj Kumar

[prateek]

The problem here is tha the Archive option only works when you have Permanent error thrown from the Module. In your case, the error is not Permanent and hence archiving won't work. For creating such exception, you need to implement ModuleException constructor in your custom module. The format is

ModuleException(String message, Throwable cause){}

Regards,

Prateek

[former_member185881]

Hi Prateek

-

---

The problem here is tha the Archive option only works when you have Permanent error thrown from the Module. In your case, the error is not Permanent and hence archiving won't work. For creating such exception, you need to implement ModuleException constructor in your custom module. The format is

ModuleException(String message, Throwable cause){} -

---

One of my friend told me i should include some parameters under module tab of my communication channel

"AF_Modules/MessageTransformBean" under Processing sequence

"Transform.permanentErrors = true" under module configuration

he told this is a standard module provided by SAP.

Now i believe according to your answer I have to include ModuleException(String message, Throwable cause){} in my module code am i right na. I need to implement this because i am using module. and above standard module we will use if we are not using our own module.

If some where i am wrong correct me.

Regards

Dheeraj kumar

[former_member185881]

Hi All

I have developed a module for checking duplicate files.

If duplicate file is found i am throwing an exception from my module. And doing archiving of these files because these files i want to shift to another directory of FTP server as these files will not be picked by XI.

• In my Sender Communication Channel i have given these settings

--> I have checked mark "Archive Faulty Source files"

path i have specified like this --> /my_folder/duplicate_Folder/

Under module Tab - processing Sequence i have given :

Module Name ...................................................... Module Key

AF_Modules/MessageTransformBean ...................... 2

localejbs/TestEJBBean(my module) ......................... 1

CallSapAdapter .......................................................... 0

Under Module Configuration -

Module Key ........... Parameter Name ..................................... Parameter value

2 ........................ Transform.PermanentErrors .......................... true

When i am putting my xml file into ftp, the file is moving to specified folder.

In communication Channel Monitoring i am getting these things:

- Success Send binary file "WPUUMS_20091106_20100000000000004382_1_010.xml" from FTP server "10.10.100.205:\XIDEV_STORES\sapinbound", size 1206 bytes with QoS EO

Success Transform: using Transform.Class: $identity

Success Transform: transforming the payload ...

Success Transform: successfully transformed

Success CustomModule :: process method started and file name Duplicate

Error Attempt to process file failed with null

-

---

I am not getting any solution what to do. Please need solution.

REgards

Dheeraj Kumar

Edited by: Dheeraj Kumar on Dec 11, 2009 1:10 PM

[prateek]

MessageTransformBean won't help because it can raise Permanent error only when processing fails in MessageTransformBean itself. In your case as per your module configuration, it will pass the MessageTransformBean successfully and raise the same error as earlier.

You need to implement the constructor I mentioned earlier and exception should to be caught into it.

Regards,

Prateek

[former_member185881]

This message was moderated.

[former_member185881]

Hi All

Please need a help how to make constructor????????

REgards

Dheeraj kumar

[former_member203627]

Hi Dheeraj,

Did you get any solution for this, even i am having the same problem. Need to know the solution...Please help ! ! !

[Former Member]

We are facing a similar issue.

I have an ItemField adapter module develop to parse some EDI files.

I have rasied a permannet error in order to check the Archvie faulty message feature,

But the Adapter failed to archive the files.

Infact it is currently blocking other files from bening processd.

I have added the Transform.PermanentErrors=true the File adapter as part of the development

but this did'nt do the trick.

I have to say I am really dissapointed.

We are lookign for a workaround In-house.

OSS response was :

Dear Nimrod,

I would like to apologize for long waiting period.

During that time SAP support and CA development along with product

management department has reviewed the issue.

This issue is related to integration between Conversion Agent and SAP.

Unfortunately we found that the feature was not implimented.

This requirement was brought up by you only in the past 5 years.

At this stage we can not say if and when we will accommodate this

request.

Please let us know if you need more information regarding the issue.

Kind Regards,

XXXX

[former_member185881]

Hi Ria sen

Sorry for late reply

Did you get the solution or still strugling?

Regards

Dheeraj Kumar

Edited by: Dheeraj Kumar on Jan 15, 2010 9:49 AM

[former_member185881]

Hi Nimrod

I too raised the same OSS request to SAP but i didnt got any good response, afterwards we changed our requirement and achieved the thing with other way round.

Well I would like to know what you are trying to do, whats your requirement?

Regards

Dheeraj Kumar

[Former Member]

Hi Nirmod,

We have the exact same issue and raised a OSS note (I read SAP's resposnse to you before creating the OSS message)

Find below response from SAP for our message.

Faulty Source Files will be archived only when

a component called CMTransformBean with in ConversionAgent throws

retrycontrolexception or a messaging exception on error.

But this is not the case now. ConversionAgent just throws

CM module exception. So with the present implementation this feature

will not work. This cannot be changed with any setting in

Conversion Agent. This requires a code/implemetation change since it is

adding a new functionality. According to our product management

implemeting this feature will tentatively happen in Q3 of 2010.

I guess we should be happy, at last they have decided to implement the feature.

Regards

Jai

P.S: I am still trying to figure out how to archive when an error happens in a custom adapter module.