Issue in calling Adapter Module

Hi experts,
We have a File -
> IDoc scenario where the file has got fixed length data. The data is in the following format:
Header xdfsdfefefeswefr
Detail dfdkfereorierwer
Detail fdfkjwoeiefiwere
Detail
Trailer erererewoirwoiwe
We do not have any identifier to identify the header, detail and trailer record.
We have gone for custom java adapter module which inserts H, D, T as the first character of each line in the file to identify the Header, Detail and Trailer nodes.
We added a entry for calling the adapter module under the module tab in file sender communciation channel. The EAR for adapter module has been deployed successfully.
But we are unable to call the adapter module at runtime.
The channle log has no indication wrt to the module being called.
We are on SAP XI 3.0 SP17
If any one has faced a similar issue. Please respond and your help would be highly appreciated.
regards,
Younus

Hi,
Check this document.Nice document on adding an adpater module at runtime.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00838345-708c-2a10-1199-9514c0b0a91c
this forum replies too..
Reg Integration Scenario
Thanks,
Vijaya.

Similar Messages

Performance issue when calling java module

Hi experts,
It takes much time to call Java module 'JBND_CRM_SVY_XSLT_TRANSFORM' from abap function module.
When I executed runtime analysis via t-cd:se30,
most of time is consumed in 'wait for RFC' .
When the java module is called, it always takes much time.
I think VMC memory management is not the cause,
because the issue also occurs at first call.
The kernel patch level is 146 of release 700.
Do you have any idea to improve performance?
Regards,
Fukuhara Yohei

Hi
try with this code
remove
READ TABLE i_events INTO wa_events WITH KEY name = 'USER_COMMAND'.
IF sy-subrc EQ 0.
wa_events-form = 'USER_COMMAND'.
MODIFY i_events FROM wa_events TRANSPORTING form WHERE name =
wa_events-name.
ENDIF.
and change alv
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = sy-repid
i_callback_user_command = 'USER_COMMAND'
it_fieldcat = i_ztal_prof1_cat[]
i_save = 'A'
TABLES
t_outtab = i_ztal_prof1.
Marco

Calling adapter module in PI7.1

Hello,
I have migrated an adpater module from XI3.0 and deployed it successfully, but I get an error ("Object not found") at runtime. I have the suspicion that the expression I use in the com channel for referencing the module is wrong.
The module shall be used in a communication channel of type file adapter.
What exactly do I have to enter on the module tab?
My EJB is called ProcessingInstructionModule, it's in a package called com.sapcons.xi.af.conversion, the provider is sap.com.
So I tried
localejbs/sap.com/com.sapcons.xi.af.conversion/ProcessingInstructionModule
com.sapcons.xi.af.conversion/ProcessingInstructionModule
and several other combinations but always got
"Object not found in lookup of com.sapcons.xi.af.conversion"
or
"exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sapcons.xi.af.conversion, the whole lookup name is localejbs/sap.com/com.sapcons.xi.af.conversion/ProcessingInstructionModule"
Any idea?
Thank in advance
Rainer

Hi,
Check for typo errors in jndi name.
Check the following links which are helpful for ur problem.
http://help.sap.com/saphelp_nwpi71/helpdata/en/e9/61e1407e858031e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nwpi71/helpdata/en/16/2da04028f40160e10000000a1550b0/frameset.htm
SDM Troubleshooting for the error:
http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm
Thanks,
Ramesh

Some issues regarding JEE adapter module development in NWDS 7.1

Hi guys,
I'm trying to develop my first AM in NWDS 7.1 and I'm facing some issues which I'd be happy if you would help me out with.
1, I'm going step by step according this document http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa&overridelayout=true but I have an information Warning "Classpath entry PI_AF_LIBS/... (all PI AF 7.1 classes) will not be exported or published. Runtime ClassNotFOundExcpetion may result". Why am I getting this if I have checked the checkboxes with these libraries in Project->Preferences->Java Build Path->Order and Export(tab)? If this checked I'd say it will be exported with the project.
2, I need to create an SDA file to deploy the module, because the server is not available directly. So first if I'm not wrong I need to have an EAR file which I can use to create the SDA. But how can I get this EAR file? This document describes only direct way of deployment.
Thanks in advance,
Olian

1. The jars need to be referenced in the project build path to enable the compilation of the code
The warning can be overlooked as the jars are present in PI.
2. The EAR Project that gets created (as per the description in the referred document) can be exported to the get the necessary
ear file.

PI 7.1 adapter module issue

I deoplyed my module and worked fine. now i changed some code by adding parameter to module
strModuleKey = moduleContext.getContextData("module.key");
I changed the related things in my communication channel(gave parameters)
Now, i get below error while executing...
java.lang.ClassCastException: class com.sap.aii.af.sdk.xi.mo.MessageContext:library:com.sap.aii.af.sdk.libcom.sap.engine.boot.loader.ResourceMultiParentClassLoader428c6e04alive incompatible with interface com.sap.engine.interfaces.messaging.api.Message:interface:com.sap.aii.af.ms.ifccom.sap.engine.boot.loader.ResourceMultiParentClassLoader2dd7e4d6alive
Followed the below url but in vain..
PI JAVA ADAPTER MODULE PROBLEM
Incompatible with interface - Exception in Adapter Module
Issue on developing Adapter Module
Also if you are using PI 7.1 refer to the blog:
/people/stefan.grube/blog/2008/12/11/adjust-your-pi-70-adapter-modules-for-pi-71-in-15-minutes
Please let me know if u have any other suggestions other than this...
Thanks
Prabhakar

Hi Venkat,
Yes, you cannot add custom modules to soap adapter.
Please refer below documentation for the same..!!
http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/8c4756224a6fb5e10000000a155369/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Regards,
Swetha.

File adapter - Archive issue with adapter module

Hi All,
I have 2 issues here. We are currently using PI 7.11 EHp1 SP02.
1. Arhival with "add time stamp" wont work. It just gives us an error message saying simpledate format exception.
I have gone through the OSS note 1265534 and thought this will resolve the issue. But our BASIS team believes this note is only applicable for PI 7.1 SP01. Can you one using PI 7.11 SP02 comment on this?
Note: Archive option with out add time stamp works fine.
2. When I use adapter module in my sender file configuration, the archive option itself does not work. Read the official SAP help which says "To archive source files where a permanent error occurred during processing, set the indicator.
A permanent error occurs either during the conversion of the file content, or in a module in the module processor."
So the question here is, how do we make the error permanent? The only way to throw error from adapter module is using the ModuleException. It has 4 different constructors. I have used both
ModuleException me = new ModuleException ("My error Msg"); and
Module Exception me1 = new ModuleException ("Error String", new Throwable("My error Msg");
In both the cases, the archival wont happen.
Any ideas welcome.
Thanks
Jai

Hi,
I am using NFS protocol here not FTP. Sorry I dint mention that earlier.
Thanks
Jai
Edited by: Jaishankar on Apr 1, 2010 9:55 AM
Edited by: Jaishankar on Apr 6, 2010 11:10 AM

Issue in Adapter Module

Hi Experts,
I have written an Adapter module to set the target file name (because it could not be done with usual DynamicConfig in mapping because of multimapping). I am facing a peculiar issue with it. For ex: I have 3 msgs. First msg started executing the module to set the target fillename and about to end the module execution. Meanwhile second msg enters the module execution and changes the file name. This is resulting in first msg to post a file with name set by second msg. I have put "Maintain order at runtime" in interface determination of ID to fix the issue. But this isssue is still persisting. Please let me know, how can a msg acquire a lock on the module and untill it finishes it execution, no other msg should start the module execution.
Thanks,
Rakesh

Hi Michal,
I have written below code to name the \target file in module code. I have also set "Adapter specific msg attributes" in receiver file adapter and referred file name from dynamic config:
public ModuleData process(ModuleContext inputModuleContext, ModuleData inputModuleData)
     throws ModuleException {
               Object obj = null;
               Message msg = null;
               AuditAccess audit = null;
               MessageKey keyOut = null;
               obj = inputModuleData.getPrincipalData();
               msg = (Message) obj;
               keyOut = new MessageKey(msg.getMessageId(),msg.getMessageDirection());
               try
                    audit = PublicAPIAccessFactory.getPublicAPIAccess().getAuditAccess();
                    audit.addAuditLogEntry(keyOut, AuditLogStatus.SUCCESS, "Module Started Execution..");
                    MessagePropertyKey mpk = new MessagePropertyKey("FileName","http://sap.com/xi/XI/System/File");
                    InputStream is = msg.getDocument().getInputStream();
                    DocumentBuilderFactory docBuilderFact = DocumentBuilderFactory.newInstance();
                    DocumentBuilder docBuilder      = docBuilderFact.newDocumentBuilder();
                    Document doc = docBuilder.parse(is);
                    Node nl = (Node) doc.getDocumentElement();
                    Node n = nl.getFirstChild();
                    Attr a = (Attr) n.getAttributes().item(0);
                    String Num = a.getValue();
                    audit.addAuditLogEntry(keyOut, AuditLogStatus.SUCCESS, "Number is "+Num);
                    Attr a1,a2;
                    if (n.getNodeName().equalsIgnoreCase("Create"))
                         a1 = (Attr) n.getAttributes().item(1);
                         String sd = a1.getValue();
                         audit.addAuditLogEntry(keyOut, AuditLogStatus.SUCCESS, "Start Date is "+sd);
                         String fileName = sd + "-" + Num + ".xml";
                         msg.setMessageProperty(mpk,fileName);
                    else(n.getNodeName().equalsIgnoreCase("Update"))
                         a2 = (Attr) n.getAttributes().item(2);
                         String sd = a2.getValue();
                         audit.addAuditLogEntry(keyOut, AuditLogStatus.SUCCESS, "Start Date is "+sd);
                         String fileName = sd + "-" + Num + ".xml" ;
                         msg.setMessageProperty(mpk,fileName);
               catch(Exception e)
                    audit.addAuditLogEntry(keyOut, AuditLogStatus.ERROR, "Execption Occured.." + e);
               return inputModuleData;
When 3 msgs get created for Create interface, File name set by first msg is being changed by second and file for first msg is posted with name set by second (because second msg has changed the target file in module code by that time )

Digital Signature validation issue in Adapter Module

Hi guys,
we have developed an adapter module for digital signature validation, unfortunately, it simetimes work, sometimes doesnt. Strange is, that the same adapter module works for one customer, while for another one doesn't.
We have sent through some "invalid" messages, which should have been valid at the client, where the module works and theu were flagged as valid. It seems the problem is caused by "special" spanish characters, because validation works for the messages where are only standard chars.
Any idea, what to check? Java version, system encoding?
Any help appreciated,
Olian

Hi,
Not really sure about what causes such issues, but if your module coding uses String and byte[] manipulation, are you using explicite encoding when declaring such types ? I remember facing strange issues with XML field values, and "forcing" encoding to "UTF-8" when appropriate, it solved all my errors (string typed object, when converted internally by the JVM, were not always represented by the same bytes object)
Hope this helps
Chris

AS2 adapter-- Module tab configuration to call seeburger std mappings..!

Hi Experts,
Seeburger has been installed and i want to use AS2 adapter to make use the seeburger standard mappings.
When i opened the module tab, its been found that for
Sender AS2 adapter:
Module Name                                     Module Key
localejbs/Seeburger/solution/as2             solutionid
localejbs/CallSapAdapter                         exit
Module configuration
_Modulekey      ParameterName               ParameterValue_
Solutionid           Mappingname               SEE_ORDERS_UN_...
can i use the above steps??
Is solutionid is enough to call the seeburger mapping?
or
do i need to use the Bic module to call the seeburger std mapping like below?
Module Name                                    Module Key
localjbs/CallBicXIRaBean                         bic
Module configuration
Modulekey     ParameterName               Parameter Value
Bic               Mappingname              SEE_ORDERS_UN_...
Kindly let me know.
Regards
Krupa.

HI,
For module configuration for As2 refer the below help.
Sender configuration:
AS2 identifier is the party identified which will be provided by the WAN network provider.
Under the party identifiere tab
Agency will be seeburger
Scheme=AS2ID
Name = WAN network no of the partner who is sending the file
Few changes in the module parameter tab.
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
Module configuration:
bic= destSourceMsg = MainDocument
bic= destTargetMsg = MainDocument
bic= mappingName= See_E2X_EDIFACT_ORDERS_UN_D93A
Receiver AS2 adapter configuration:
When the adapter is used in a receiver channel, it obtains a message from the Integration Engine and sends it to a business partner. In this case, the following steps are required:
1. Define the channel as a Receiver channel on the Parameters tab
2. The last step ensures the module sequence is complete:
Make sure the module ModuleProcessorExitBean does exist in the module sequence:
Module Name=localejbs/ModuleProcessorExitBean
Type=L
Module Key=Exit
with the following module parameter:
Module Key=Exit
Parameter Name=JNDIName
Parameter Value=deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
Refer the below thread which has the same discussion.
Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
Thanks and Regrds,
Chirag

Best approach for RFC call from Adapter module

What is the best approach for making a RFC call from a reciever file adapter module?
1. JCo
2. Is it possible to make use of MappingLookupAPI classes to achieve this or those run in the mapping runtime environment only?
3. Any other way?
Has anybody ever tried this? Any pointers????
Regards,
Amol

Hi ,
The JCo lookup is internally the same as the Jco call. the only difference being you are not hardcoding the system related data in the code. So its easier to maintain during transportation.
Also the JCO lookup code is more readable.
Regards
Vijaya

Receiver File Adapter Module processor issue

Hello all,
I have deployed (using SDM) a specific module for one of my file communication channel.
In MDT, I have the following error :
Exceptions survenues pour Adapter Framework : Object not found in lookup of Module0001
La diffusion du message vers l'application via File_http://sap.com/xi/XI/System a échoué en raison de : com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of Module0001.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of Module0001.
Where can be the source of this problem ?
Thanks a lot

Jean
Also check if the "JNDI" name that you have specified in the Receiver Adapter module
excluding localejbs matches the deployed name in the "J2ee Aministartor Deploy service.
for example if you have
localejbs/sap.com/BeanName
you should have
the service deployed under
/sap.com/BeanName
regards
krishna

Issue with overwriting msg using adapter module when WSS enabled in SOAP CC

Hi guys,
I have a SOAP->RFC scenario where on the sender side I'm using an adapter module. This adapter module should modify the message content based on some conditions. This works fine unless the WSS is enabled in the sender SOAP CC. When enabled, the message doesn't get modified. If disabled, it works fine. Do you have any explanation for this? Is there any workaround for this?
Thanks, Olian

Hi Olian,
For 2004s (PI71) too sender adapter doesn't support modules (in normal SOAP mode and not in AXIS)
http://help.sap.com/saphelp_nwpi71/helpdata/EN/a4/f13341771b4c0de10000000a1550b0/frameset.htm
>>if I use the module w/o WSS enabled on the CC,
Can you tell me how you did this??
Regards
Suraj

PI 7.1 Adapter Module Development - Identify SOAP Fault Message

Hi Experts,
here's a PI 7.1 Adapter Module Development issue I hope you can help me to resolve. It's about identifying SOAP fault messages.

Scenario at a glance:
Adapter Modules placed in the modules chain at request and response time in a synchronous Scenario:
- Request: SOAP Axis to RFC 
- Response and Fault Response: RFC to SOAP Axis

The issue is how to identify SOAP fault message in SOAP Axis Adapter Module in the response message:
The client gets SOAP fault messages like the follwong one:
 <SOAP:Body>
 <SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <ns1:exception xmlns:ns1="http://typen.geschaeftsstelle.pab.barmer.de">
 <ns1:errortext>bla bla bla ...</ns1:errortext>
 </ns1:exception>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>


But when trying to access the tags faultcode and/or faultstring in the adapter module via xPath expressions I do not get them. Obviously the SOAP Fault tags are built AFTER the adapter module has been passed. So my question is:
How can I clearly/uniquely detect a SOAP fault response message (and distinguish it from a "normal" response message) in my SOAP Axis Adapter Module?

I tried it the following way:


// Check Message Payload for SOAP Fault Message via xPath expressions
...
// SOAP Fault Code
zv_xPression = zc_constXPattern.replaceFirst("&", "faultcode");
zv_soapFaultCode = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// SOAP Fault String
zv_xPression = zc_constXPattern.replaceFirst("&", "faultstring");
zv_soapFaultString = XPathAPI.eval(zv_doc, (String) zv_xPression).toString();
// check for SOAP Fault Message
if (zv_soapFaultCode.equals("") && zv_soapFaultString.equals("")) {
 // Create Audit Log entry - NOT a SOAP Fault Message
 zv_msgText = zc_constModuleName + " 0190: xPath - OK! This message is NOT a SOAP Fault Message";
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.SUCCESS, zv_msgText);
 zv_faultCheck = false;
}
else {
 ...
 // Create Audit Log entry - SOAP Fault Message
 zv_msgText = zc_constModuleName 
 + " 0200: xPath - this message is a SOAP Fault Message. " 
 + " - Faultcode is: " + zv_soapFaultCode 
 + " - Faultstring is: " + zv_soapFaultString; 
 zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
 ...
}
...

But zv_soapFaultCode and zv_soapFaultString are always empty (with other payload tags this coding works fine).

Any ideas? 
Thanx very much in advance!
Regards,
Volker

Hi Alex!
Like already mentioned I solved my problem by identifying the SOAP exception with the messageClass attribute of the PI message header. Acess code:
try {
String zv_msgClass = zv_piMsg.getMessageClass().toString();
} catch (Exception e) {
zv_msgText = zc_constModuleName
+ " E0110: Message processing terminated."
+ " Reason: Error while getting MessageClass "
+ zv_dataSource
+ e;
// create trace and audit log entry (severity ERROR) for exception
zv_location.errorT(ZV_SIGNATURE, zv_msgText);
zv_audit.addAuditLogEntry(zv_msgKey, AuditLogStatus.ERROR, zv_msgText);
ModuleException me = new ModuleException(e);
zv_location.throwing(ZV_SIGNATURE, me);
e.printStackTrace();
throw me;
} // end of try-catch-block
But I do not think this will solve your problem. I am almost sure, that something in your Axis configuration is wrong/missing. If a handler cannot be instatiated then it really may be missing. Have a look at defaultTrace.trc. Maybe you will find more suitable information about the root cause of your problem. Also have a look at NWA under software components and/or application modules if you can find/see your modules.
But there is a general issue when trying to catch PI fault messages. If e.g. the requestor tries to login with wrong userid/pasword, then you will have no chance to catch this kind of error - at least as far as I know. Because in this very early stage of PI message processing no module is called.
One last question: Did you develop your own Adapter or just an adapter module? In the first case: Is your adapter started and healthy? Have a look at RWB -> communication channel monitoring.
Regards,
Volker

Standard Adapter Module "Message Transform Bean" in Seeburger AS2 Adapter

Hi,
    I am calling standard adapter module "Message Transform Bean" in seeburger AS2 Sender adapter where I am getting the following error :
ClassNotFoundException:com.sap.aii.messaging.adapter.Conversion . Can anybody help me on this. Appreciate for your respoinse.
Thank you,
Mallikarjuna Rao M

Hi,
Thank you for your replies I manage to get NWA dump for this issue.. Here is the log
Could not call backend system: Error in ???-module:Transform: failed to set up the transformer for channel 6857fd15f84d3e23a7b0f51ca1851b20; modkey TXT2XML; caused by java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
[LOC: com.seeburger.as2.impl.SHCInitiatorProcessor.initiateToBackend] Caused by: Error in ???-module:Transform: failed to set up the transformer for channel 6857fd15f84d3e23a7b0f51ca1851b20; modkey TXT2XML; caused by java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
at com.seeburger.xi.api.module.impl.nw71.SeeModuleProcessorLocal71.process(SeeModuleProcessorLocal71.java:55)
at com.seeburger.xi.connector.fw.InitiationThread.run(InitiationThread.java:101)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:259)
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:228)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:353)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.sap.aii.af.modules.trans.MessageTransformBean.loadClass(MessageTransformBean.java:121)
at com.sap.aii.af.modules.trans.MessageTransformBean.setup(MessageTransformBean.java:178)
at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:346)
at sun.reflect.GeneratedMethodAccessor484_10002.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy2674_10002.process(Unknown Source)
at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:249)
at sun.reflect.GeneratedMethodAccessor311_10002.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy102_10002.process(Unknown Source)
at com.seeburger.xi.api.module.impl.nw71.SeeModuleProcessorLocal71.process(SeeModuleProcessorLocal71.java:43)
Waiting for your valuable inputs on this.
Thank you,
Mallikarjuna Rao M

Encoding Issues in AS2 Adapter

Hi,
I have a scenario : AS2 (Sender) - IDOC (Receiver).
Third party is sending the EDI message which we successfully receive at XI and send an IDOC to R/3 system. Now the issue is :
EDI message has some Cyrillic characters (ISO-8859-5 encoded) in one field of the EDI message. But when we receive the message in XI the cyrillic characters get converted in some junk data and is send as such to the R/3 system. XI is not able to read the data in correct encoding. I have tried using "xmlAnonymizerBean" in the Module tab of the adapter, using it just before the Call Adapter but this did not solve the purpose.
Any idea how can we read the data in correct encoding in XI.
Also I asked them to send the data in UTF-8 encoding. They changes the encoding from there end and sent the data in UTF-8 encoding, but in this case the message did not get processed in Seeburger also. (did not reach XI).
Any help on this?
Vikas

Hi,
Are you using BIC mapping designer to convert EDI to XML and Vice versa?
In that case, you can refer this discussion:
Re: Seeburger BIC Mapping Designer: Special Character (German Umlaut) Problem
Regards,
Ravi Kanth Talagana

Issue in calling Adapter Module

Similar Messages

Maybe you are looking for