SAP PI 7.1 custom adapter deployment error
Hi Experts,
I have developed one custom SFTP adapter and i am trying to deploy it in PI server via JSPM.
But in JSPM i am getting some error messages. what may be the cause of this error.
ERROR log:
sample_ra.sda<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.7.1006]/>
<!NAME[D:\usr\sap\P71\DVEBMGS88\j2ee\JSPM\log\log_2011_06_15_11_00_05\deploy_2011-06-15_11-55-05.log]/>
<!PATTERN[deploy_2011-06-15_11-55-05.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%25d[%6s]:%m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 15, 2011 11:55:05 AM [Info ]:DC API is trying to connect to 'p71:58804'
Jun 15, 2011 11:55:06 AM [Info ]:DC API has Connected to 'p71:58804'
Jun 15, 2011 11:55:06 AM [Path ]:+++++ Starting V A L I D A T E action +++++[ deployerId=10 ]. timerId=51
Jun 15, 2011 11:55:06 AM [Path ]:Selected archives for validation. [ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
Jun 15, 2011 11:55:06 AM [Debug ]:Got full sdu path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Jun 15, 2011 11:55:06 AM [Path ]:component version handling rule is UpdateAllVersions.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:deployment workflow strategy is normal deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Error strategies[ deployerId=10 ]:
Jun 15, 2011 11:55:06 AM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2011 11:55:06 AM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorSkipDepending'
Jun 15, 2011 11:55:06 AM [Debug ]:deployer initialized successfully:[id:#52, elapsed: 125 ms.].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Debug ]:Total time:[#52: 0.125 sec].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Info ]:Start validating.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Validating completed. Preparing the validation result.
Jun 15, 2011 11:55:06 AM [Path ]:
Sorted Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Admitted'
Deployment Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Admitted'
Jun 15, 2011 11:55:06 AM [Info ]:+++ Validation finished with status 'Success' +++[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:+++++ End V A L I D A T E action +++++[ deployerId=10 ]. Total time:[#51: 0.25 sec]
Jun 15, 2011 11:55:06 AM [Path ]:+++++ Starting D E P L O Y action +++++ [ deployerId=10 ] [ timerId=53]
Jun 15, 2011 11:55:06 AM [Path ]:Selected archives for deployment. [ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
Jun 15, 2011 11:55:06 AM [Debug ]:Got full sdu path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Jun 15, 2011 11:55:06 AM [Path ]:component version handling rule is UpdateAllVersions.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:deployment workflow strategy is normal deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:life cycle deploy strategy is disable LCM deploy strategy.[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Error strategies[ deployerId=10 ]:
Jun 15, 2011 11:55:06 AM [Path ]:error action 'DeploymentAction' is 'OnErrorStop'
Jun 15, 2011 11:55:06 AM [Path ]:error action 'PrerequisitesCheckAction' is 'OnErrorStop'
Jun 15, 2011 11:55:06 AM [Debug ]:deployer initialized successfully:[id:#55, elapsed: 125 ms.].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Debug ]:Total time:[#55: 0.125 sec].[ deployerId=10 ]
Jun 15, 2011 11:55:06 AM [Path ]:Starting deployment.[ deployerId=10 ]
Jun 15, 2011 11:55:07 AM [Debug ]:deployment triggered : DeployItem[file=
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
,deployItemStatus=Admitted
,versionStatus=NEW
,description=
sdu=name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', softwareType ''J2EE', sub type '''
clusterDescriptor=null
Jun 15, 2011 11:55:09 AM [Debug ]:deployment performed : DeployItem[file=
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda
,deployItemStatus=Aborted
,versionStatus=NEW
,description=
1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.pi.adapter.sftp/SFTPAdapter_raEAR application.
ERRORS:
Connector Schema Validator: Versions of standard and additional xmls do not match., file: SFTP_Adapter_ra.rar#META-INF/connector-j2ee-engine.xml, column 0, line 0, severity: error
Hint: 1) Given application file is not valid one.
sdu=name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', softwareType ''J2EE', sub type '''
clusterDescriptor=null
Jun 15, 2011 11:55:17 AM [Error ]:Deployment Exception during deployment phase 'DeploymentException',cause=An error occurred while deploying the deployment item 'sap.pi.adapter.sftp_SFTPAdapter_raEAR'.; nested exception is:
com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of sap.pi.adapter.sftp_SFTPAdapter_raEAR. Cannot deploy it.
Jun 15, 2011 11:55:17 AM [Error ]:Deployment Items status: '
Sorted Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Aborted'
Description:'1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.pi.adapter.sftp/SFTPAdapter_raEAR application.
ERRORS:
Connector Schema Validator: Versions of standard and additional xmls do not match., file: SFTP_Adapter_ra.rar#META-INF/connector-j2ee-engine.xml, column 0, line 0, severity: error
Hint: 1) Given application file is not valid one.'.
Deployment Items -
1. Client path '
p71\sapmnt\trans\EPS\in\SFTPAdapter_raEAR_SDA.sda'
Sdu info :name 'SFTPAdapter_raEAR', vendor 'sap.pi.adapter.sftp', location 'SFTP_Adapter', version '1.1', software type ('J2EE', sub type ''), dependencies :[none]
Deploy status is 'Aborted'
Time statistics( ms ):
1.validate : -1
1.1.deployment : 2156
1.1.1.Notify:Event triggered : 16
1.1.2.Disable LCM deployment : 2140
1.1.2.1.Perform delivery : 2140
1.1.2.1.1.Application Deployer : 2140
Description:'1. [ERROR CODE DPL.DS.5402] JLinEE reported following erros for sap.pi.adapter.sftp/SFTPAdapter_raEAR application.
ERRORS:
Connector Schema Validator: Versions of standard and additional xmls do not match., file: SFTP_Adapter_ra.rar#META-INF/connector-j2ee-engine.xml, column 0, line 0, severity: error
Hint: 1) Given application file is not valid one.'.
Jun 15, 2011 11:55:17 AM [Path ]:+++++ End D E P L O Y action +++++[ deployerId=10 ]. Total time:[#53: 10.779 sec]
Hi Debashish,
I have a similar requirement to develop a Custom module for SFTP adapter for SAP PI 7.1 version..
Can you please advise how you build the adapter and please share the document if you have any...
thanks
Similar Messages
-
Seeburger EDI Adapter Deployment Error: Cannot register EarLoader
Hello,
we currently have updated our SAP Netweaver Development Environment 2004s to SP20. This installation runs on IBM iSeries.
We also have to deploy a Seeburger EDI Adapter (Version 1.8) but we faced following error in the deployment:
---snipped
PM Error: Aborted: development component
'SeeFunctionsEar'/'seeburger.com'/'SEEBURGER
AG'/'20090701183537.1.8.1'/'1', grouped by software component
'SeeXIExtendedTools'/'seeburger.com'/'LOCAL'/'20090701183537.1.8.1''/'1':
Caught exception during application deployment from SAP J2EE Engine's
deploy service:
java.rmi.RemoteException: Cannot register EarLoader for application
seeburger.com/SeeFunctionsEar..
Reason: null; nested exception is:
java.lang.NullPointerException
(message ID:
com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
---snipped
We've deployed not only with the JSPM but also with developer Studio. (The SDM-Tool has a big problem after upgrating to SP20 - SAP knows the error and with the next SP this will be fixed. So this tool cannot be used!)
First of all, I think it is very useful for us to know what is the EarLoader but unfortunately we can't find any information on the sap help, documentation or here in the SDN. Neither on the Web .....
Could someone explain the issue to me, please?
Thanks in advance.
Christian SperlichHi,
1)Can you check your class path, whether it is configured correctly
2)Check whether you have included the latest class file while importing
3)Check whether you have activated the objects after you have made changes are imported
Regards
Agasthuri Doss -
Resource Adapter Deployment Error (Resolved)
This Problem Has Been Resolved.
I'm trying to develop an application using Inbound resource adapters on Weblogic 9.2.1 .
I have the resource adapter and the MDB packaged separately. The MDB appears to deploy successfully, but the resource adapter does not.
I get the following exception
javax.naming.NamingException [Root exception is java.rmi.RemoteException: javax.naming.InitialContext; nested exception is:
java.io.NotSerializableException: javax.naming.InitialContext]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:97)
at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:421)
at weblogic.jndi.internal.WLEventContextImpl.bind(WLEventContextImpl.java:297)
at weblogic.jndi.internal.WLContextImpl.bind(WLContextImpl.java:389)
at weblogic.connector.deploy.JNDIHandler.bindRA(JNDIHandler.java:575)
at weblogic.connector.common.RAInstanceManager.putRAintoJNDITree(RAInstanceManager.java:1361)
at weblogic.connector.common.RAInstanceManager.activate(RAInstanceManager.java:432)
A similar issues was referenced in this message :
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4330872
It appears that the exception means the InitialContext is not serializable.
This is my start(BootstrapContext) method in my resource adapter. If I DO NOT call new InitialContext(), or setMDBOnMessageMethod(), the exception does not occur.
public void start(BootstrapContext ctx)
this.ctx = ctx;
System.out.println("entering AddScanResourceAdapterImpl start");
logger.info("entering AddScanResourceAdapterImpl start");
try
this.JNDIContext = new InitialContext(); // This causes the exception.
this.wm = this.ctx.getWorkManager(); // Calling this does not cause and exception.
setMDBOnMessageMethod(); // This also appears to cause the same exception.
catch (Exception e)
System.out.println("AddScanRA start : Exception thrown: " + e);
// TODO: Log problem.
logger.info("exiting AddScanResourceAdapterImpl start");
private void setMDBOnMessageMethod()
try
Class socketListenerClass = com.fedex.ground.tms.mtms.server.addscan.connector.ra.AddScanSocketHandler.class;
Class[] paramTypes = { java.net.Socket.class };
this.onMessageMethod = socketListenerClass.getMethod("onMessage", paramTypes);
catch (NoSuchMethodException ex)
ex.printStackTrace();
Thanks for your any help,
John
Edited by johnbrod20 at 04/17/2007 6:48 AMHi John,
One of my customer is facing the same error .
Can you please share the resolution of this problem -
Unable to deploy custom adapter module in PI 7.31
Hi pros,
I created a custom adapter module to split some complex input files to multiple messages. We use a SAP PO 7.31 java-only installation. I followed this document to create my adapter module:
How to Create Modules for the JEE Adapter Engine
I know it is for PI 7.1 but a colleague of mine said that he was able to create a running adapter module for PI 7.3 following the guide. I created the following projects:
EAR project references the EJB project:
Project facet of the EJBproject:
ejb-jar.xml config:
application-j2ee-engine.xml (in EAR project):
When I try to deploy my module, I get the following error:
Java version:
NWDS version:
Any hint is appreciated! What can be wrong? What can I check again?
THANKS!
Message was edited by: Stefan MünchowI am not sure if the version is the problem. We have PI 7.31, support package 14, patch level 0 and NWDS 7.31 support package 12, patch level 4. The version of NWDS is lower than the version of the PI. According to Note 1599298 the error occurs when the NWDS is higher than the one of PI. Besides, we are able to deploy BPMN processes with the same NWDS to the same server.
This is the exact exception trace shown in NWDS:
com.sap.ide.eclipse.sdm.deploy.DeploymentException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:110)
------------- Nested exception -------------------
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:80)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [sap.com_SplitArticleFileModule_EAR] failed
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/DP2/J64/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/213/SplitArticleFileModule_EAR.ear] failed
at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
... 11 more
Caused by: com.sap.engine.services.deploy.container.rtgen.GenerationException: Open failed for '/usr/sap/DP2/J64/j2ee/cluster/server0/temp/deploy/SplitArticleFileModule_EAR.ear1422275742985/com.sap.aii.utilxi.server.jar' with fd 218 returning message 'couldn't find 'END' tag' and errno 0 after trying cache.
at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.createSingleModule(WebServicesGenerator.java:100)
at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.generate(WebServicesGenerator.java:54)
at com.sap.engine.services.deploy.container.rtgen.AnnotationsSupportingGenerator.generate(AnnotationsSupportingGenerator.java:27)
at com.sap.engine.services.deploy.ear.jar.moduledetect.GeneratorWrapper.generate(GeneratorWrapper.java:43)
at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generate(ModuleGeneratorTool.java:110)
at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generateOverExistingModules(ModuleGeneratorTool.java:97)
at com.sap.engine.services.deploy.ear.jar.ModuleGeneratorTool.generateModules(ModuleGeneratorTool.java:80)
at com.sap.engine.services.deploy.ear.jar.EARReader.read(EARReader.java:240)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.prepareNewDeploymentInfo(DeployUtilTransaction.java:217)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:199)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
... 12 more
Caused by: java.util.zip.ZipException: Open failed for '/usr/sap/DP2/J64/j2ee/cluster/server0/temp/deploy/SplitArticleFileModule_EAR.ear1422275742985/com.sap.aii.utilxi.server.jar' with fd 218 returning message 'couldn't find 'END' tag' and errno 0 after trying cache.
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:154)
at java.util.jar.JarFile.<init>(JarFile.java:141)
at java.util.jar.JarFile.<init>(JarFile.java:105)
at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesSupportHandlerImpl.generateWebSupport(WebServicesSupportHandlerImpl.java:79)
at com.sap.engine.services.webservices.server.deploy.preprocess.WebServicesGenerator.createSingleModule(WebServicesGenerator.java:69)
... 26 more
Maybe the used jar files could be the problem? -
Custom adapter module deployment in PI 7.1
We upgrade XI 3.0 to PI 7.1. However, I dont see SDM directory anymore which is what I had used to deploy my custom adapter module.
Is there a different way to deploy custom adapter module in 7.1? Is SDM discontinued?
When I try to deploy the ear file from NWDS directly I get deployment exception error
"Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !".
I have given the message server host and port correctly in preferences.
I am using NWDS 7 and JAVA SDK 1.4.2.15.
Is there a new procedure to deploy custom adapters in PI 7.1?
Regards
Haseebhi,
check this document:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00838345-708c-2a10-1199-9514c0b0a91c
regards. -
SAP PI crashes because of Custom Adapter module
Hi,
We are facing a strange problem. We have deployed a custom adapter module developed in java which accesses a Hardware Security Module(HSM) and uses the keys in HSM to digitally sign our data. Now, when I use particular methods in this code and deploy it on PI server, the server crashes while testing this out. As soon as I run the channel having this adapter module, PI server becomes unavailable. It restarts on its own after a few minutes.
One of the reasons I identified to be causing this issue is the signing mechanism used in code. When I used a mechanism that was not supported or not correct, it crashed the server. If i corrected it, it worked fine. I found no other thing in my code causing this behaviour apart from this mechanism. But I am still not able to understand how a single method in a code can cause the whole server to crash. Has anybody here faced such a problem? Any pointers would be appreciated.
We are using SAP PI 7.31 java only installation.
Thanks,
Ravi DesaiHi Ravi
1. To check if it is a memory issue. Once you start the channel, check the memory usage in nwa. Check if the memory is increasing once the channel is started.
2. Add debug statements to print logs in default traces at as many places as possible. Since your code is not reaching the Catch block, using the debug statement you can reach the line in the code which is causing this issue.
Regards
Osman Jabri -
Hi ALL,
i have developed one custom adapter and its was working fine now we have change some code according to new requirement. now the thnig is this adapter is capable for sending the data once but when its again going to send data its giving me error:
Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.ClassCastException: com.sap.aii.af.ra.ms.transport.TransportHeaders.
Transmitting the message using connection http://XXXXX:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.ClassCastException: com.sap.aii.af.ra.ms.transport.TransportHeaders.
Can anybody give me any clue why its happenng...
Thanks & Regards
Kunaal
Edited by: KUNAAL MASIH on Feb 2, 2009 11:39 AMHi,
i am just guessing.........i think you have developed a custom adpater module for a adapter which you are using in a synchronous scenario..........so i think what has happened is that for your first req msg's response when came to your custom adpater module is erroring due to some reason..........so just check whether you are doing some processing for the synch response in your custom adapter module.
Regards,
Rajeev Gupta -
Hi Experts,
We developed a custom adapter for PI 7.1.
Now we need to deploy it in a PI system that cannot be connected to a NW Developer Studio. Is there another way to do this deploy?
In PI 7.0 we use to deploy through the Visual Administrator. Since VA is not available in PI 7.1, which tool should we use?You first create the EAR file as per document below (which also has many other information about custom module creation)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa?quicklink=index&overridelayout=true
Then convert it to SDA as per following link
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20a221c6-3943-2e10-5198-dada408de5ac?quicklink=index&overridelayout=true
And finally you can deploy using JSPM. Since 7.1 versions don't have SDM, you need to convert the EAR files into SDA in order to be able to deploy it. -
Using OIM 11gR2 Deployment Manager to create a custom adapter
I have been trying to create a custom adapter by importing an xml file using the OIM 11gR2 Deployment Manager, but so far it only results in this stack trace:
+<Error> <XELLERATE.WEBAPP> <BEA-000000> <Class/Method: LoadDeploymentUtility/importSelected encounter some problems: Import failed for entity : 'adpADTESTADAPTER' which is of type : 'EventHandler', with the following error message :Unable to save dataobject for EVT+
com.thortech.xl.ddm.exception.DDMException: Import failed for entity : 'adpADTESTADAPTER' which is of type : 'EventHandler', with the following error message :Unable to save dataobject for EVT
+ at com.thortech.xl.ddm.engine.SchemaInstanceFacade.performImport(SchemaInstanceFacade.java:460)+
+ at com.thortech.xl.ejb.beansimpl.tcImportOperationsBean.performImport(tcImportOperationsBean.java:1143)+
+ at Thor.API.Operations.tcImportOperationsIntfEJB.performImportx(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.oracle.pitchfork.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:34)+
+ at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)+
+ at com.oracle.pitchfork.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:42)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)+
+ at $Proxy342.performImportx(Unknown Source)+
+ at Thor.API.Operations.tcImportOperationsIntf_uawk3z_tcImportOperationsIntfRemoteImpl.__WL_invoke(Unknown Source)+
+ at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)+
+ at Thor.API.Operations.tcImportOperationsIntf_uawk3z_tcImportOperationsIntfRemoteImpl.performImportx(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)+
+ at $Proxy360.performImportx(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)+
+ at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)+
+ at $Proxy361.performImportx(Unknown Source)+
+ at Thor.API.Operations.tcImportOperationsIntfDelegate.performImport(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)+
+ at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)+
+ at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)+
+ at oracle.iam.platform.utils.DMSMethodInterceptor.invoke(DMSMethodInterceptor.java:25)+
+ at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)+
+ at $Proxy362.performImport(Unknown Source)+
+ at com.thortech.xl.webclient.actions.LoadDeploymentUtilityAction.importSelected(LoadDeploymentUtilityAction.java:3516)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:269)+
+ at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(tcLookupDispatchAction.java:133)+
+ at com.thortech.xl.webclient.actions.tcActionBase.execute(tcActionBase.java:894)+
+ at com.thortech.xl.webclient.actions.tcAction.execute(tcAction.java:213)+
+ at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)+
+ at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)+
+ at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)+
+ at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)+
+ at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:305)+
+ at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)+
+ at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)+
+ at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)+
+ at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
+ at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)+
+ at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)+
+ at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)+
+ at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)+
+ at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)+
+ at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)+
+ at com.nexaweb.server.servlet.NexawebRequestDispatcher.doClientRequest(NexawebRequestDispatcher.java:346)+
+ at com.nexaweb.server.servlet.NexawebRequestDispatcher.forwardClientRequest(NexawebRequestDispatcher.java:114)+
+ at com.nexaweb.server.servlet.JspProcessor.processRequest(JspProcessor.java:137)+
+ at com.nexaweb.server.servlet.RequestProcessor.dispatchRequest(RequestProcessor.java:463)+
+ at com.nexaweb.server.servlet.RequestProcessor.processClientEvent(RequestProcessor.java:710)+
+ at com.nexaweb.server.services.protocol.NexawebProtocolHandler.handleProcessEventCommand(NexawebProtocolHandler.java:1026)+
+ at com.nexaweb.server.services.protocol.NexawebProtocolHandler.dispatchCommand(NexawebProtocolHandler.java:140)+
+ at com.nexaweb.server.NexawebServer.doService(NexawebServer.java:420)+
+ at com.nexaweb.server.NexawebServer.doGet(NexawebServer.java:335)+
+ at com.nexaweb.server.admin.ServerAdmin.callNexawebServer(ServerAdmin.java:378)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at com.nexaweb.loader.xMethodInvoker.runInThread(xMethodInvoker.java:69)+
+ at com.nexaweb.server.api.admin.ServerAdminProxy.callNexawebServer(ServerAdminProxy.java:551)+
+ at com.nexaweb.redirect.RedirectServlet.doGet(RedirectServlet.java:18)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
+ at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)+
+ at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)+
+ at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)+
+ at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at com.thortech.xl.webclient.security.CSRFFilter.doFilter(CSRFFilter.java:76)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:107)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)+
+ at java.security.AccessController.doPrivileged(Native Method)+
+ at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)+
+ at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)+
+ at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)+
+ at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)+
+ at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)+
+ at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)+
+ at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)+
+ at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)+
+ at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)+
+ at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)+
+ at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)+
+ at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)+
+ at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)+
Caused By: com.thortech.xl.ddm.exception.DDMException: Unable to save dataobject for EVT
+ at com.thortech.xl.ddm.repositories.rdbms.datatypes.data.TableInstance.finishDataObject(TableInstance.java:842)+
+ at com.thortech.xl.ddm.repositories.rdbms.impl.RDBMSRepository.finishdataObject(RDBMSRepository.java:960)+
+ at com.thortech.xl.ddm.engine.visitor.ImportVisitor.dataDependencyVisitComplete(ImportVisitor.java:636)+
+ at com.thortech.xl.ddm.repositories.rdbms.impl.RDBMSRepository.handleDataBaseDependencies(RDBMSRepository.java:685)+
+ at com.thortech.xl.ddm.engine.data.datatypes.SchemaInstance.traverse(SchemaInstance.java:282)+
+ at com.thortech.xl.ddm.engine.SchemaInstanceFacade.performImport(SchemaInstanceFacade.java:436)+
+ at com.thortech.xl.ejb.beansimpl.tcImportOperationsBean.performImport(tcImportOperationsBean.java:1143)+
+ at Thor.API.Operations.tcImportOperationsIntfEJB.performImportx(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.oracle.pitchfork.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:34)+
+ at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)+
+ at com.oracle.pitchfork.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:42)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)+
+ at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)+
+ at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)+
+ at $Proxy342.performImportx(Unknown Source)+
+ at Thor.API.Operations.tcImportOperationsIntf_uawk3z_tcImportOperationsIntfRemoteImpl.__WL_invoke(Unknown Source)+
+ at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)+
+ at Thor.API.Operations.tcImportOperationsIntf_uawk3z_tcImportOperationsIntfRemoteImpl.performImportx(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:85)+
+ at $Proxy360.performImportx(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)+
+ at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)+
+ at $Proxy361.performImportx(Unknown Source)+
+ at Thor.API.Operations.tcImportOperationsIntfDelegate.performImport(Unknown Source)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)+
+ at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)+
+ at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)+
+ at oracle.iam.platform.utils.DMSMethodInterceptor.invoke(DMSMethodInterceptor.java:25)+
+ at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)+
+ at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)+
+ at $Proxy362.performImport(Unknown Source)+
+ at com.thortech.xl.webclient.actions.LoadDeploymentUtilityAction.importSelected(LoadDeploymentUtilityAction.java:3516)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:269)+
+ at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(tcLookupDispatchAction.java:133)+
+ at com.thortech.xl.webclient.actions.tcActionBase.execute(tcActionBase.java:894)+
+ at com.thortech.xl.webclient.actions.tcAction.execute(tcAction.java:213)+
+ at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)+
+ at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)+
+ at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)+
+ at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)+
+ at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:305)+
+ at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)+
+ at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)+
+ at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)+
+ at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
+ at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)+
+ at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)+
+ at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)+
+ at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184)+
+ at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)+
+ at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:253)+
+ at com.nexaweb.server.servlet.NexawebRequestDispatcher.doClientRequest(NexawebRequestDispatcher.java:346)+
+ at com.nexaweb.server.servlet.NexawebRequestDispatcher.forwardClientRequest(NexawebRequestDispatcher.java:114)+
+ at com.nexaweb.server.servlet.JspProcessor.processRequest(JspProcessor.java:137)+
+ at com.nexaweb.server.servlet.RequestProcessor.dispatchRequest(RequestProcessor.java:463)+
+ at com.nexaweb.server.servlet.RequestProcessor.processClientEvent(RequestProcessor.java:710)+
+ at com.nexaweb.server.services.protocol.NexawebProtocolHandler.handleProcessEventCommand(NexawebProtocolHandler.java:1026)+
+ at com.nexaweb.server.services.protocol.NexawebProtocolHandler.dispatchCommand(NexawebProtocolHandler.java:140)+
+ at com.nexaweb.server.NexawebServer.doService(NexawebServer.java:420)+
+ at com.nexaweb.server.NexawebServer.doGet(NexawebServer.java:335)+
+ at com.nexaweb.server.admin.ServerAdmin.callNexawebServer(ServerAdmin.java:378)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)+
+ at java.lang.reflect.Method.invoke(Method.java:601)+
+ at com.nexaweb.loader.xMethodInvoker.runInThread(xMethodInvoker.java:69)+
+ at com.nexaweb.server.api.admin.ServerAdminProxy.callNexawebServer(ServerAdminProxy.java:551)+
+ at com.nexaweb.redirect.RedirectServlet.doGet(RedirectServlet.java:18)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
+ at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)+
+ at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)+
+ at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)+
+ at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at com.thortech.xl.webclient.security.CSRFFilter.doFilter(CSRFFilter.java:76)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:107)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)+
+ at java.security.AccessController.doPrivileged(Native Method)+
+ at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)+
+ at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)+
+ at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)+
+ at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)+
+ at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)+
+ at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
+ at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)+
+ at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)+
+ at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)+
+ at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)+
+ at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)+
+ at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)+
+ at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)+
+ at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)+
+ at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)+
Has anyone attempted this and also failed or succeeded, or done something similar? I'd like to be able to use the Deployment Manager to create adapters because it's easier than dealing with the design console, especially for multiple adapters.
I can also post the xml file I'm using if anyone would like to see it.
Edited by: 939908 on May 29, 2013 11:33 AM
Edited by: 939908 on May 29, 2013 11:34 AMXML file I'm trying to import:
<?xml version='1.0' encoding='UTF-8'?>
<xl-ddm-data database="jdbc:oracle:thin:@hostname:1521/serviceName" description="Active Directory adapter" user="xelsysadm" version="2.0.2.1">
<EventHandler name="adpADTESTADAPTER" repo-type="RDBMS" subtype="TaskAdapter">
<EVT_POST_INSERT>0</EVT_POST_INSERT>
<EVT_POST_UPDATE>0</EVT_POST_UPDATE>
<EVT_POST_DELETE>0</EVT_POST_DELETE>
<EVT_PRE_DELETE>0></EVT_PRE_DELETE>
<EVT_PRE_UPDATE>0</EVT_PRE_UPDATE>
<EVT_PRE_INSERT>0</EVT_PRE_INSERT>
<EVT_PACKAGE>com.thortech.xl.dataobj.rulegenerators</EVT_PACKAGE>
<Adapter name="AD Test Adapter" repo-type="RDBMS">
<ADP_STATUS>OK</ADP_STATUS>
<ADP_DESCRIPTION>Simple test adapter</ADP_DESCRIPTION>
<ADP_TYPE>P</ADP_TYPE>
<ADP_DISABLED>0</ADP_DISABLED>
<ADP_BUILD>0</ADP_BUILD>
<AdapterTask name="Run Simple Test" repo-type="RDBMS">
<ADT_SEQUENCE>0</ADT_SEQUENCE>
<ADT_TYPE>JAVA</ADT_TYPE>
<AdapterTaskParam name="::~~::1:Output:method" repo-type="RDBMS">
<ATP_SEQUENCE>1</ATP_SEQUENCE>
<ATP_TYPE>String</ATP_TYPE>
<ATP_IMAGE>parameter.gif</ATP_IMAGE>
<ATP_IN_OUT_FLAG>Output</ATP_IN_OUT_FLAG>
<ATP_JAVA_METHOD_TYPE>method</ATP_JAVA_METHOD_TYPE>
<AdapterDataMapping id="ADM1337" repo-type="RDBMS">
<ADM_DISPLAY_VALUE>Return variable (Adapter Variable)</ADM_DISPLAY_VALUE>
<ADM_MAP_TO>Adapter Variables</ADM_MAP_TO>
<ADM_MAP_QUALIFIER>Return variable</ADM_MAP_QUALIFIER>
<ADM_ADV_KEY Adapter="AD Test Adapter" AdapterVariable="Adapter return value" EventHandler="adpADTESTADAPTER"/>
</AdapterDataMapping>
</AdapterTaskParam>
<AdapterJavaTask repo-type="RDBMS">
<ADJ_STATIC>1</ADJ_STATIC>
<ADJ_CONSTRUCTOR>0 public com.test.SimpleTest()</ADJ_CONSTRUCTOR>
<ADJ_METHOD>simpleTest</ADJ_METHOD>
<ADJ_METHOD_DISPLAY>14 public java.lang.String com.test.SimpleTest.simpleTest()</ADJ_METHOD_DISPLAY>
<ADJ_API_NAME>com.test.SimpleTest</ADJ_API_NAME>
<ADJ_JAR_FILE>SimpleTest.jar</ADJ_JAR_FILE>
<RLO_KEY ExternalDirectory="JavaTaskJar"/>
</AdapterJavaTask>
</AdapterTask>
<AdapterVariable name="Adapter return value" repo-type="RDBMS">
<ADV_DESC>Return variable</ADV_DESC>
<ADV_DISPLAY_VALUE>Return variable</ADV_DISPLAY_VALUE>
<ADV_MAP_TO>USED</ADV_MAP_TO>
<ADV_DATA_TYPE>Object</ADV_DATA_TYPE>
</AdapterVariable>
</Adapter>
</EventHandler>
</xl-ddm-data>
Edited by: 939908 on May 30, 2013 6:50 AM -
BizTalk 2013 R2 - WC-Custom Adapter SAP-Binding: Unhandeld exception on failure tests
Dear Mr./Ms.
We have set up a test environment with BizTalk 2013 R2 Developer edition.
And we have also set up the SAP adapter following this blog
https://sandroaspbiztalkblog.wordpress.com/2015/03/04/biztalk-server-20132013-r2-step-by-step-wcf-sap-adapter-installation-guide/#comments
.But instead we used a WCF-Custom adapter with SAP-Binding
Everthing works fine if BizTalk can connect to SAP. But if we do some failure test, like giving in a wrong password. We get next error in the event viewer:
Application: BTSNTSvc64.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.CallbackException
Stack:
at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredAsyncResult.SignalFinished(System.Object, System.Exception)
at Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredOutboundChannel`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].AsyncRequest(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
We would expect that we get some kind of authentication error and a suspended message. But Instead the host instance crash and message stays in process. Thanks in advance.
Kind regards
Benny Verhamme
benny verhamme signedWe would expect that we get some kind of authentication error and a suspended message. But Instead the host instance crash and message stays in process. Thanks in advance.
Hi Benny,
Thanks for your feedback in BizTalk forum.
As you mentioned above, we will receive an unhandled exception when we did something wrong during the procedure. I'm afraid that this is "by design", if this request is urgent for you, you could consider contact support directly(http://support.microsoft.com
). Thanks for your understanding.
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
How to get Alerts mail for adapter engine errors in SAP PI 7.0
Hi Friends,
I configured Alerts in PI 7.0. with the help of t-code u2018ALRTCATDEF and created a new alert catergory.
In container tab i have mentioned all give below elements.
SXMS_MSG_GUID, SXMS_RULE_NAME, SXMS_ERROR_CAT, SXMS_ERROR_CODE, SXMS_FROM_PARTY, SXMS_FROM_SERVICE, SXMS_FROM_NAMESPACE, SXMS_FROM_INTERFACE, SXMS_TO_PARTY, SXMS_TO_SERVICE, SXMS_TO_NAMESPACE,SXMS_TO_INTERFACE
I am getting alerts when I manually test the alerts configurations by running the report u2018RSALERTTESTu2019.
I am getting mail as :
Alert ID: ##00009##
Dear Administrator,
This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
Message ID:
Interface:
NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
Double click on that message ID and click on error in left hand tree.
Please take appropriate action in co-ordination with respective functional and BASIS consultant.
But When I am getting a error , I am not getting an alert mail. Right now iam doing in XI Development.
I am not getting an Alert mail , when my message is in status of : System Error . Error catergory is : XI_J2EE_ADAPTER_JDBC.
Kindly tell how to get alert mail for error catergory : XI_J2EE_ADAPTER_JDBC and in Adapter engine errors.
How to get alert mail when my message is failed with any reason in Adapter engine.
Waiting for quick replay. Please help me out.
Regards,
Ahmed.Hi thanks for quick reply.
As per your given link : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14877. [original link is broken]
I have done all these steps. But still little problem.
as per link he is getting Error description , error message id , alert rule..
In my case I am not getting these information. when my messages failed. When I am doing manully testing the alert getting an mail as :
Alert ID: ##00009##
Dear Administrator,
This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
Message ID:
Interface:
NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
Double click on that message ID and click on error in left hand tree.
Please take appropriate action in co-ordination with respective functional and BASIS consultant.
Is it okay the body of mail??.
I am not getting alert mail when my messages failed in adapter engine and Integration Engine.
Ex my message is failed in AE:as below.
My messages flow as : SAP --> XI --> DB.
Messages is success (in ECC moni)> XI moni also success> XI Adapter engine getting error as (Status: System Error) and (Error Category : XI_J2EE_ADAPTER_JDBC).
Regards,
Ahmed. -
MFL.convertToXml() gives 'Internal Error' in custom adapter
Has anyone seen the MFL.convertToXml() fail with:
IllegalStateException: Internal Error, current node is null
dies at com.bea.nonxml.readers.NonXMLReaderVisitor.nextToken(NonXMLReaderVisitor.java:110)
Anyone got source to this?
I call this method from within a custom adapter.
I have an extremly simple MFL file as follows,
Note that I added a 'IgnoreTheRest' at the en, to see if I could simplify it.
<?xml version='1.0' encoding='US-ASCII'?>
<!DOCTYPE MessageFormat SYSTEM 'mfl.dtd'>
<MessageFormat name='MsgNoBits.h.2' version='2.02'>
<!-- C declaration of message_id: unsigned short -->
<FieldFormat name='message_id.2' type='UBigEndian2'/>
<!-- C declaration of id: unsigned short -->
<FieldFormat name='id.2' type='UBigEndian2'/>
<!-- C declaration of num_bytes: unsigned long -->
<FieldFormat name='num_bytes.2' type='UBigEndian4'/>
<FieldFormat name='IgnoreTheRest' type='Filler' optional='y' length='1' repeat='*'>
</FieldFormat>
</MessageFormat>Not really...
Just worked around it by doing the MFL.convertToXml() inside the ejb container.
The way you get the binary data through the JCA to the container is by converting the binary data to a HexBinary XML type. (if you find another way please let me know)
Pull out the binary once you receive it ( I use a JPD ). Then perform the translation. I think its very inefficient since you have to do bin-hex-bin-xml XML crap, but it works.
heres the hexbinary snippet you use for your event definition.
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="wlai/XXX_event"
xmlns="wlai/XXXAppView_XXX_event"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="XXXData"
type="xsd:hexBinary"/> -
Deployment Error on sap-j2ee engine
Hi
I build an EJB project,Web project and added these to EAR project and built an '.ear' file. When i tried to deploy on sapj2ee engine. I got the following deployment error.
My j2ee engine is up and running. What went wrong?
Help me,
Thanks
==========
May 24, 2006 5:39:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp22811JCP_EAR.ear
Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.24.15.58.19':
Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear":
java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.24.15.58.19\temp22811JCP_EAR.ear to J2EE 1.3.
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear: JCP_EJB.jar,Please check the ear content.
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
... 30 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Deployment exception : The deployment of at least one item abortedHi Amol!
The password is admin for SDM, i redployed by building '.ear' file again.
You suggested to deploy the ear file on SDM remote gui, how to do that?
help me
Thanks
==========
I got the error as:
May 25, 2006 11:22:11 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp11022JCP_EAR.ear
Aborted: development component 'JCP_EAR'/'sap.com'/'localhost'/'2006.05.25.11.17.51':
Caught exception during access of archive "D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear":
java.lang.RuntimeException: ERROR: Cannot initialize EARReader: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.Exception is: com.sap.engine.services.deploy.exceptions.BaseIOException: Cannot convert EAR D:\usr\sap\QN7\DVEBMGS00\SDM\root\origin\sap.com\JCP_EAR\localhost\2006.05.25.11.17.51\temp11022JCP_EAR.ear to J2EE 1.3.
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:185)
at com.sap.engine.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:444)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.initDeployManager(EngineApplOnlineDeployerImpl.java:300)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:134)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:119)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:88)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: The following archives that aredescribed in the ear descriptor are not found in the ear: JCP_EJB.jar,Please check the ear content.
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.checkDescriptor(ExtendedEARReader.java:805)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.getDescriptor(ExtendedEARReader.java:324)
at com.sap.engine.services.deploy.extended.ear.ExtendedEARReader.<init>(ExtendedEARReader.java:87)
at com.sap.engine.services.deploy.converter.EARConverter.convert(EARConverter.java:85)
... 30 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Deployment exception : The deployment of at least one item aborted -
Troubles with the creation of New Custom Adapter for NW 7.1
Hi guys !!!
I have some troubles with the creation of a new custom adapter for NW 7.1. I have followed some pdf and notes, like :
[Upgrade an SAP NetWeaver PI 7.0 Adapter to SAP NetWeaver PI 7.1|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0667f56-96c7-2b10-0e9a-c40fbd523f4d]
note : 1004000
I have all the materials to make the custom Adapter ( like file .sca with all .rar and .sda , like file sample_ra.rar with all the file .java, like all the libs for the projects ) and I have make it !!! But, when I try do deploy it, i recieve a warning that i don't understand, this is the warning :
S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 1
Failed deployments: 0
~~~~~~~~~~~~~~~~~~~
1. File:C:Users
maienzaDesktopCreazione del SDAPI71_AF_myFirstCustomAdapter_ver_2.0.sda
Name:PI71_AF_myFirstCustomAdapter_ver_2.0
Vendor:sap.com
Location:SAP AG
Version:7.1007.20090310105326.0000
Deploy status:Warning
Version:NEW
Description:
1. Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0.
No one of the [EJBContainer] containers, which processed it, returned deployed component names.
The registered containers in this moment were [CTCContainer, com.sap.caf.um.metadata, com.sap.security.ume, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:149)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:Warning
I have see in the nwa if there are some applications or services that are stopped but all the necessary it's started, just one question : in the pdf for upgrade from 7.0 to 7.1 no one speaks about ejBean or about a creation of it ... it's necessary an ejBean ?? Beacause in the file .sda of the file .sca that i have downloaded there are more of the adapter with ejBean ....
AntonelloHi,
the adapter metadata it's been created but my service is still stopped; when I try to start it, in the NDWS -> Deploy view -> tab Repositary view, I receive this errors, one after the other, cause I try to start it 3 times and in each time I received 3 differents errors :
Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.container.DeploymentException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/applicationjars
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.makeStartInitially(ContainerInterfaceImpl.java:771)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.lcm.impl.RemoteLCMImpl.start(RemoteLCMImpl.java:45)
at com.sap.engine.services.dc.lcm.impl.RemoteLCMImplp4_Skel.dispatch(RemoteLCMImplp4_Skel.java:233)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.services.ejb3.container.ActionException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/applicationjars
at com.sap.engine.services.ejb3.container.FSMakeFolder.perform(FSMakeFolder.java:48)
at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
... 30 more
Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.container.DeploymentException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/jars
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.makeStartInitially(ContainerInterfaceImpl.java:771)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.makeStartInitially(StartInitiallyTransaction.java:184)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:145)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.lcm.impl.RemoteLCMImpl.start(RemoteLCMImpl.java:45)
at com.sap.engine.services.dc.lcm.impl.RemoteLCMImplp4_Skel.dispatch(RemoteLCMImplp4_Skel.java:233)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.services.ejb3.container.ActionException: Unable to create folder /usr/sap/DXI/DVEBMGS00/j2ee/cluster/apps/sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0/EJBContainer/jars
at com.sap.engine.services.ejb3.container.FSMakeFolder.perform(FSMakeFolder.java:48)
at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
... 30 more
Exception has been returned while the 'sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 3999650:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5082] Exception while validating application sap.com/PI71_AF_myFirstCustomAdapter_ver_2.0.
No one of the [EJBContainer] containers, which processed it, returned deployed component names.
The registered containers in this moment were [CTCContainer, com.sap.caf.um.metadata, com.sap.security.ume, com.sap.security.login-modules, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, MigrationContainer, Monitoring Configurator, dbschemacontainer, appclient, orpersistence, PortalRuntimeContainer, JDBCConnector, EJBContainer, metamodelrepository, webservices_container, scheduler~container, ConfigurationsContainer, Content Container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
at com.sap.engine.services.deploy.server.utils.ValidateUtils.missingDCinDIValidator(ValidateUtils.java:80)
at com.sap.engine.services.deploy.server.application.StartInitiallyTransaction.prepare(StartInitiallyTransaction.java:149)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitiallyGlobal(StartTransaction.java:449)
at com.sap.engine.services.deploy.server.application.StartTransaction.doStartInitially(StartTransaction.java:437)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
at com.sap.engine.services.dc.lcm.impl.RemoteLCMImpl.start(RemoteLCMImpl.java:45)
at com.sap.engine.services.dc.lcm.impl.RemoteLCMImplp4_Skel.dispatch(RemoteLCMImplp4_Skel.java:233)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) -
Adapter Module Error-Sending excel file as an attachment of the mail
Hi ,
My scenario is as follows
1)I am sending an excel file as an attachment of the mail.I need to read that excel attachment as a payload.
So mail adapter is used in sender side.
To configure this, have used standard PayloadSwapBean module with proper module key.
Next to convert excel to XML another custom adapter module is being used.
Both this adapter module , I configured into the CC of sender mail adapter.
The order in which adapter modules are being used in the sender CC are as follows
1)localejbs/AF_Modules/PayloadSwapBean
2)localejbs/MDPExcelToXMLConversion
3)sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean
MDPExcelToXMLConversion-Custom adapter module written to convert excel to xml.
I am getting the following error
exception caught during processing mail message [4899]com.sap.aii.af.lib.mp.module.ModuleException
And also,
no messages in coming MONI of PI.
Pls suggest what to do.
Thanks
AyanShabarish,
Will the ordering in which the adapter modules(In this case there are two-PayloadSwapBean & MDPExcelToXML) are appearing into Module tab of sender adapter matter?
Firstly, what is happenning
1)If I take out the custom adapter module MDPExcelToXML and put only PayloadSwapBean then it is successfully converting mail attachment into the main Payload i.e PayloadSwapBean module is working.
2)Nextly, my local code( i.e java code without including standard Module specific method like ejbActivate(),ejbPassivate(),process() etc etc.)) for MDPExcelToXML is successfuly converting the excel file into the XML file.Then I am making the local code into adapter module specific code and deploying that.
A few question arises here,
Do I need to do any specific configurations here in PI for this particular things.Maybe both the adapter module is clashing with each other.
And also using tracing and logging into my custom adapter module code.Getting the following error,
java.io.IOException: Unable to read entire header; 116 bytes read; expected 512 bytes#
Thanks
Ayan
Maybe you are looking for
-
Hey, I have $2350-2400 and I want some proper guidance for the macbook pro
HEY!!! Guys I will try to make this as easy as possible! First let me tell you I am 15, I love graphics, music and literature and I have no credit card, my iTunes account has no money, I'm using an account that doesn't require credit cards! So (ugh)
-
Your reviews of the standard articles by forum junkies that just shoot out links of more engineering pages like this one are resulting in slamming the mouse, pounding the keyboard and cussing aloud that even your cat probably won't be emerging for a
-
When playing electric guitars and basses I'm having problems with hum: 1--noise in my amps (amps are solid state) 2--with guitars or basses plugged directly into a usb interface, there is hum...more hum when the iBook is plugged in than when it is ru
-
Apps freeze and wont restart w/o a hard reboot
Model Name: iMac Model Identifier: iMac7,1 Processor Name: Intel Core 2 Duo Processor Speed: 2.4 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 4 MB Memory: 4 GB Here is the problem: I close an app like Dreamweaver or Excel The app st
-
ORA-04091: table OBJ_SIGN_TRANS is mutating, trigger/function may not..
Hi , I m getting table mutating error while trying to update this table, i m doing transaction signing from Java mehtod, table has 2 triggers, whlie updating this table i m facing error. Triggers are mentioned bellow including a package which i m usi