Module processor deployment.

Hi All,
I hav written a custom module processor.i even hav a helper class which is called in the module processor.I developed it thru NWDS.But when i try to deploy the ear file that is generated out of the jar file of the module,it is giving a warning that the libraries hav a hard reference on the server.
the application-j2ee-engine.xml looks like the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="library">com.sap.aii.af.lib</reference-target>
</reference>
<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="service">com.sap.aii.adapter.xi.svc</reference-target>
</reference>
<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="service">com.sap.aii.af.svc</reference-target>
</reference>
<reference
reference-type="hard">
<reference-target
provider-name="sap.com"
target-type="service">com.sap.aii.af.cpa.svc</reference-target>
</reference>
<fail-over-enable
mode="disable"/>
</application-j2ee-engine>
Can anyone help me out in deploying the module processor.
Thnx in Advance
Anil.

Hi Anil,
Its great that your problem is solved but what was the problem. Was it related to changing of related to changing of references.
If you are in a position please do post the problem and how you solved it.
Regards
Sidharth

Similar Messages

Class Cast Exception In Module Processor

Hi,
I'm trying implement "Step by step guide to develop a
module for reading file name in a
sender file adapter" by Krishnakumar Ramammoorthy. When I deploy the EAR in my server I'm getting following exception:
#1.5#0003BA92DD90003B0000240000001D190003FCBEF3B117E6#1122321992587#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0##nd2xidb.svc.doi.test_XD2_3621750#Guest#46b9f3b0fd4611d9af850003ba92dd90#output##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Channel CC_File_S_ABCMCodes: Sending file failed with java.lang.ClassCastException - continue processing#
I'm running it on XI 3.0 SP 11.
I'm trying to send a file and planning to modify the content in the module processor.
Please let me know if anyone has a clue ?
to get above mentioned document please search for "ramammoorthy", it's the first document.
https://www.sdn.sap.com/sdn/search.sdn?contenttype=url&query=ramammoorthy&selected=0&content=/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fSDN!2fiViews!2fWCM!2fcom.sap.sdn..wcm.search.search_adv%3Fprttheme%3DCSIN%26QueryString=ramammoorthy%26SearchPluginName=sdn_all%26SelectedCustomProps=resourcetype(value=s*)
thanks
Sibo

Hi All,
The problam was in ejb-jar.xml. You should use the interfaces provided by module framework as home and remote interface.
I made following changes in ejb-jar.xml and it worked..
<session>
 <ejb-name>GetFileNameBean</ejb-name>
 <!local-home>gov.doi.fbms.moduleprocessor.GetFileNameLocalHome</local-home>
 <local-home>com.sap.aii.af.mp.module.ModuleLocalHome</local-home>
 <!local>gov.doi.fbms.moduleprocessor.GetFileNameLocal</local>
 <local>com.sap.aii.af.mp.module.ModuleLocal</local>
 <ejb-class>gov.doi.fbms.moduleprocessor.GetFileNameBean</ejb-class>
 <session-type>Stateless</session-type>
 <transaction-type>Container</transaction-type>
 </session>
Please refer to document http://help.sap.com/saphelp_nw04/helpdata/en/32/43d84072378031e10000000a1550b0/content.htm
Thanks a lot for your help..
Sibo

Module processor usage in File ADapter

Hi all,
I have a scenario Idoc->Xi->File to be in Xi 3.0.
There is already an XI 2.0 system up and running wherin they have used dispatcher classes for the File Adapter Configuration.They have used the Transform Class "com.sap.aii.messaging.adapter.XSLTConversion" and have added the particular XSLT mapping Program in "namespace1.XSLTService.XSLTConversion.XSLTFileName=
convert.xsl".
When I want to configure these in XI 3.0 as a Receiver File Adapter, documentation says that we need to specify these in Module Processor as a sevice. For this the precursor is that we need to deploy the Java Classes in SDM.
But my question is whether we have to include the XSLT coding too in the Archive and Deply it in the SDM? Is it not that its required only for the Java Classes to be Deployed using SDM or else the XSLT Codings too in a JAR File?

Hi Stefan,
Thanks a lot for your reply.
I already tried this way by storing the file in the File system of the server.
But for example,the XSLT file is this path of the Server,
F:\usr\sap\D49\SYS\global\tech_adapter\xslt\DR11_adapter_exit.xsl
Then, what exactly should be the path specification in the XSLT Sevice filename....Now its exactly as I have mentioned above and the file is stored physically over there....
The error log was like this,
2005-02-16 11:54:37 Success output 1108572877484 The message was successfully received by the messaging system. Profile: XI URL: http://cmis147:50000/MessagingSystem/receive/AFW/XI
2005-02-16 11:54:37 Success output 1108572877484 Using connection AFW. Trying to put the message into the receive queue.
2005-02-16 11:54:37 Success SAPEngine_Application_Thread[impl:3]_0 1108572877500 The message was successfully retrieved from the receive queue.
2005-02-16 11:54:39 Success SAPEngine_Application_Thread[impl:3]_0 1108572879093 The message status set to DLNG.
2005-02-16 11:54:39 Success SAPEngine_Application_Thread[impl:3]_0 1108572879109 Delivering to channel: FILE_DR11_Outbound
2005-02-16 11:54:39 Error SAPEngine_Application_Thread[impl:3]_0 1108572879125 Exception caught by adapter framework: failed to configure the transformation object
2005-02-16 11:54:39 Error SAPEngine_Application_Thread[impl:3]_0 1108572879125 Delivery of the message to the application using connection AFW failed, due to: failed to configure the transformation object.
2005-02-16 11:54:39 Success SAPEngine_Application_Thread[impl:3]_0 1108572879125 The asynchronous message was successfully scheduled to be delivered at Wed Feb 16 11:59:39 EST 2005.
2005-02-16 11:54:39 Success SAPEngine_Application_Thread[impl:3]_0 1108572879140 The message status set to WAIT.
But when I see the monitoring for the AdapterFramework it says its ok.
So I thought the path is probably invalid.
Your opinions please...
Thanks in Advance,
Romit.

J2EE adapter module not getting invoked by module processor

Hi All,
i have deployed my .ear file in SDM Repository successfully.
but my J2EE adapter module is not getting invoked by module processor......this i can say because i have written code to audit log my message in the java class...but when i gave input an empty file, the audit log of that file in Message Audit Log showed only 3 Steps of file converted to XML format, no data found so not generating message, deletion of my empty file.
Can anybody suggest how to enable my J2EE adapter module as i have created this module so that if i give empty file, then in the adapter i am creating a dummy XML for my message.
Thanks and Regards,
Rajeev Gupta

Hi Stefan,
1. JNDI name in visual admin is CustomerMeter
2. the files in .ear file are:
libraries,
ejb project file,
META-INF folder
in ejb project file the following files are there:
ejb-j2ee-engine.xml
ejb-jar.xml
CustomerMeter.class
Please tell what to do now.
Hi Amol,
in audit log only 3 messages are coming: File converted to XML format, no data in document so not sending message, deleting of empty file.
i have given audit log statements in java class but my audit-log statements are not coming in the audit log
this means my adapter module is not getting invoked.
Please tell what to do to correct this error.
Thanks and Regards,
Rajeev Gupta

[ModuleAdapter]Exception : Failed to call the module processor

Hello,
We deployed our Module Adapter on PI server and tried to execute it but we're having an exception :
Exception caught during processing mail message[3]: com.sap.aii.af.lib.mp.processor.ModuleProcessorException: Error during processing local bean: localejbs/fr.xx.xx.xx.ModueAdapterBean
Mail : failed to call the module processor: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: object not found in lookup of fr.xx.xx.xx.ModuleAdapterBean
We're working on SAP PI 7.11
Do you have any idea of what could possibly cause this?
Thanks in advance for your help.
Imane.

Thanks for responding Spantaleoni,
In my application.xml, here is what I have :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
 "http://java.sun.com/dtd/application_1_3.dtd">
<application>
 <display-name>ModuleAdapterEAR</display-name>
 <description>EAR for Mail conversion </description>
 <module>
 <ejb>ModuleAdapterEJB.jar</ejb>
 </module>
</application>
And my application-j2ee-engine.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="service">engine.security.facade</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">engine.j2ee14.facade</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.aii.af.lib.facade</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="service">com.sap.aii.af.svc.facade</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="interface">com.sap.aii.af.ifc.facade</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.base.technology.facade</reference-target>
 </reference>
 <provider-name>sap.com</provider-name>
 <fail-over-enable
 mode="disable"/>
</application-j2ee-engine>
My ejb-j2ee-engine.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-j2ee-engine SYSTEM "ejb-j2ee-engine.dtd">
<ejb-j2ee-engine>
 <enterprise-beans>
 <enterprise-bean>
 <ejb-name>ModuleAdapterBean</ejb-name>
 <jndi-name>ModuleAdapter</jndi-name>
 <session-props/>
 </enterprise-bean>
 </enterprise-beans>
</ejb-j2ee-engine>
Edited by: ImaneA on Aug 2, 2011 3:36 PM

Module Processor not getting executed

Hi All,
I hav created a module processor in the same way as it is mentioned in the pdf
https://websmp201.sap-ag.de/nw-howtoguides
-> exchange infrastructure -> how to Create Modules for the J2EE Adapter Engine.
But to my surprise, it is not working.I hav even enclosed the code that is displayed in the work bench showing whether the Module Processor is called or not.But while executing, nothing is displayed.Please help me out in this regard.
Thnx in Advance
Anil.

Hi Anil,
Just check the following ,
1.The JNDI name that you have given.
2.The order in which u have written the modules...that matters a lot.
3. The server in which you have deployed the bean
Regards
Divya

Doubts on Module Processor

Hello All,
What are Module Processors in XI? Where do we use them? Can anybody please send me some docu about this concept?
//Priya//

Hi Priya,
These are the basic steps involved in writing a module:
1. Make sure you have the following jar files with you.
aii_af_cci.jar
aii_af_mp.jar
aii_af_ms_api.jar
aii_af_ms_spi.jar
aii_af_trace.jar
aii_af_svc.jar
aii_af_cpa.jar
2. Open NetWeaver Developer Studio. Create a new EJB Module
New>J2EE>EJB Module.
Specify a meaningful name for the module and click Finish.
3. Right click on the folder ejbModule and create new package.
Enter a meaningful name for package and click Finish.
4. Right click on the Project, select New-->Folder. Enter lib as the folder name.
Copy all the jar files specified above from your local system and paste them into newly create lib folder.Right click on the project. Select Properties-->Java build path. Go to Libraries tab and add the jar files from lib folder to the classpath.
5. Switch to J2EE Perspective-->J2EE Explorer tab.
Right click on the newly created package and select New-->EJB.
6. Specify a meaningful name for the EJB. Select Bean Type as Stateless Session Bean.
Make sure to uncheck the checkbox Generate default interfaces.
Click on Next.
7. On the next screen change the values of following attributes as specified below.
Remote Interface: com.sap.aii.af.mp.module.ModuleRemote
Home Interface: com.sap.aii.af.mp.module.ModuleHome
Local Interface: com.sap.aii.af.mp.module.ModuleLocal
LocalHome Interface: com.sap.aii.af.mp.module.ModuleLocalHome
Click on Finish.
8. After clicking on Finish, a Creation error will be reported. Ignore this error as the file would still be created as specified.
Open the newly created file in Java Editor and add Module to the implements list of the bean class. Press Ctrl + Shift + O to remove import errors if any.
You will see a new error as
Class must implement the inherited abstract method Module.process(ModuleContext, ModuleData).
Right click in the java editor and select Source-->Override / Implement methods. Select process method from Module interface and click Ok.
You should have an error free build of the project after this.
process is the only method where we need to write the business logic.
With this you are ready to right the situation specific business logic in the process method.
9. Once you create a deployable archive i.e. .ear for this using NDS, you can deploy this archive using NDS or using SDM.
Also go through these links:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
and also there is a how to guide on Service Market Place which delas with creating modules for your Adapter. Think it might be helpful to you and answer your query,
https://websmp202.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
Just open the link below, and select the topic How to create adapter modules for j2ee engine
The how to guide is available at the SAP marketplace.
https://service.sap.com/~sapdownload/011000358700003237612005E/HowToCreateAdapterModules.pdf
and also go through <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-code-samples/how%20to%20develop%20a%20module%20for%20reading%20file%20name%20in%20a%20sender%20file%20adapter%20xi%203.0.pdf">Step by Step guide to develop a module for reading a file name in sender file adapter</a>
I hope all this information provided will help you create your module successfully.
Regards,
Abhy

Module processor exit bean

Hi all,
I am trying to do the following scenario.
Generate PDF file out of file adapter using the following URL :
/people/sap.user72/blog/2005/07/27/xi-generate-pdf-file-out-of-file-adapter
I downloaded the jar files according to weblog.
I have one doubt. I am not able to deply or placing the module processor exit bean.I am not able to find the way to call the bean.
Caould anybody please guide me to solve the probelm.
Thanks & Regards,
Gopi.

Hi Gopi,
You need to deploy the Module processor bean on your XI server.
The Module would be called from the module tab in your receiver file adapter.
Open the receiver communication channel and go to the module tab.There in the first table control(Processing sequence) prior to the standard sapCallAdapter place your module.
Put it as :
Module Name
localejbs/sap.com/<your earfilename>/<your EJB name>
or
localejbs/<JNDI name(if defined)>
Type :
Local enterprise bean
Key
0
Regards,
Sulakshana

Module Processor not working

Hi All,
I am working with on creating a module processor for the sender adapter. The code is simple and I am pretty sure it works. Its barely outputs the Module Processor object thats created within the java code.
I am having problem getting the module to work.
I have a module 'CallSapAdapter' (not localejbs/CallSapAdapter) predefined in my sender adapter. I have create my Java class CreateData in a package called Sample. I then created a EAR & deployed it using SDM. Then on, I then added this module ('CreateData') in the modules tab above the 'CallSapAdapter'. Chose the type as 'Local Enterprise Bean'.
I am unable to get the file deleted (In the adapter I have configured the processing mode as delete). Even I cant see the communication channel log for the specific adapter as I see the following error message
Application error occurred during request processing.
Error [javax.servlet.ServletException: null], with root cause [java.lang.reflect.InvocationTargetException: null].
Kindly let me know where am I going wrong. Is it in specifying the module name as 'CreateData'??
Regards
Keerti

Did you set the references to libraries and services in the application-j2ee-engine.xml correctly?
Compare it:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.aii.af.lib</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="service">com.sap.aii.adapter.xi.svc</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="service">com.sap.aii.af.svc</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="service">com.sap.aii.af.cpa.svc</reference-target>
 </reference>
 <fail-over-enable
 mode="disable"/>
</application-j2ee-engine>
> Also, does removing the libraries from the EAR have
> implications other than the size of the EAR?
Yes

Error targeting server for the EJB module while deploying the sample banking application

I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

The deployment process invokes javac internally to compile some generated classes.
Do you have javac installed and in the path?
Seth
Scott Springer wrote:
I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Problem in Module processor

Hi All,
can any body help me on this
how much time will take the module processor to execute the message.
If 4/5 messages are entering into MP at the same time what will happened
I am getting the error in this stage when iam using receiver FILE Adapter
getting the error log " Message is entering into the Module Processor"
then in the next log i will be getting the following error differently
Attempt to process file failed with
com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution:
com.sap.aii.adapter.file.varsubst.VariableDataSourceException: Caught SAXException while parsing XML payload:Fatal Error:com.sap.engine.lib.xml.parser.parserException: XMLparser: No data allowed here(:main:,row:,col:75)"
com.sap.engine.lib.xml.parser.parserException:XMLParser:N o data allowed here:(hex) 76,65,72 (:main:,row:1,col:9)
for the same message when the sys tried to resend
parserException:start-tag 'EIT' is different from the end-tag'E1EDP03(:main:,row:1,col:16)
but there is no problem with payload also
Regards
Sankar

Hi All,
1.I am not using custom Module, it is IDOC to File Scenarion.
2.No Content Conversion.
3.There is no problem with Mapping.
Maximum Messages are successfull, some messages are failed in the Module due to this error.
Every message (main:, row:1:,col:1923) this will be changing and some times </ expected, Document is not well-formed, No data allowed here "
"If i rescend the message 1 by 1 message is processing successfully, but if select more than 1 message only one message getting processed".
Around 4 interfaces with this type of error, but all having same problem some messages are failed with this kind of error.
If more messages are attempting to process at the same time in the module processor is there any loading problem that causes this error?.
Thanks & Regards
Sankar

Usage of Module processor in SOAP Receiver Adapter

Hi,
I have scenario where I am calling an external Web Service via XI. Unfortunately I need Java Mapping to generate the complete SOAP Message (there are some special header elements required by the Web Service) and flag 'no soap' in the SOAP Receiver Adapter. This works fine, but I have additional Web Service Calls that have the same Header logic and I don't want to use Java Mapping all the time.
I was wondering if it is possible to use graphical User Mapping for the Business Data that goes to the SAOP Body as a payload and use Java code to generate the SOAP Message (actually the SOAP Wrapper and the Header).
Can I do this in XI using the Module processor in the SOAP Receiver adapter or do I have to use two mappigs, one based on the Graphical mapping and another using Java Mapping? Is it feasible at all in XI?
Thanks in advance.

Hi,
You can use Module Processor.
But,
1. If it is a synch call, in when the message is going from the SOAP adapter to the Webservice, you will need to manually Add the SOAP header as you want . ( you will need to create the entire SOAP mesage as the output of the Module ).
2. When the response comes back, the same module will need to remove the SOAP header etc and pass a valid , XML message to the Graphical mapping.
If you have a requirement that some fields of the SOAP header will be needed to be accesed in the Response mapping, then you would need to either add this field to some field in the response payload.
Better option would be to use, Either a Java or a XSL mapping that does all the required stuff for you.
Regards
Bhavesh

Exception in Module Processor

Hi All,
I want to know wot happens when an exception occurs in a module processor?i hav a requirement in which i hav to pass adapter module a message when nothing goes wrong in a custom module processor.If an exception is raised in the module processor,does it prevents from passing the message to the adapter module?Please provide me some info regarding this.
Thnx in Adv
Anil.

Hi Anil,
we don't have such an requirement like you. But we have
also developed some module exit. And when the module exit
raise an exception the message does not go through. We
could see the message hanging with an exception in the
runtime workbench.
An it is also not possible to restart the message again
because the exception is raised again. So if we have an
exception the error will persist and we was not able to
restart the message again. This message was lost!
But in your case you maybe don't want that the message get
lost. In this case you can not use exception to modell you
requirement i think. But i don't have another solution for
you at the moment.
Thanks,
Ly-Na Phu

Module processor enhancement with file content conversion

Hi All,
I have a bean (module processor) that converts the a PDF doc to text. I need to use the same bean with file content conversion. Module processor processing sequence is as follows:
1) My Bean: localejbs/myBean
2) Default: localejbs/CallSapAdapter (Bean for file content conversion).
When I tried the same (myBean + File adapter with file content conversion) , it was not working as expected. But the same bean works fine with normal file adapter (myBean + File adapter without file content conversion).
Couldn't figure out the reason. Please help.
Regards,
Ajay.

As the content conversion of the file adapter is done before calling the customer module, it is not possible to use both.
As workaround you can do the file content conversion with help of the MessageTransformBean. In the module chain you put the MessageTransformBean after your module.
Note that the configuration of the MessageTransformBean has to be done like the J2SE sender file adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/frameset.htm
You find an example here:
https://websmp206.sap-ag.de/~sapdownload/011000358700001186732005E/HowToConveModuleJMS.pdf
Regards
Stefan

Zip Payload using PayloadZipBean Module Processor

Hi,
I'm using AF_Modules/PayloadZipBean in module processor of Receiver SOAP adapter to compress/zip the message payload. I've used the following module key parameters :
Parameter Name      Parameter Value
zip.Mode                  zipAll
zip.filenameKey        contentType
In the adapter engine monitoring from RWB I can see the following warning message :
Warning Zip: message is empty or has no payload
But I can see the msg payload from the RWB message monitor as expected.
Can anyone please throw any light on this issue?
Thanks in advance,
Dipankar

Hi Stefan,
Can you please explain what you meant by transfer-encoding gzip?
Actually the requirement is to receive xml message in compressed zipped format along with digital signature. As I understand using the ModuleProcessor which you mentioned in your blog I can send zipped message (using File Adapter I've actually achieved the result as mentioned in your blog. So thanks a lot for that!). But in file adapter I can't use digital signature. So how to satisfy both the requirements using a single adapter (and maybe using some module processors over it)?
Thanks for your help!
Dipankar

Module processor deployment.

Similar Messages

Maybe you are looking for