Req Custom adapter  implementation

Hi,
I am new to SUN IDM 8.1, I need to write custom resource adapter, appreciated in advance if some one help me the steps I need to follow?
Thanks
Sudarsan

When you change adapter type and adapter namespace, you have to adjust
- the ra.xml
- the reference in the adapter code (SPIManagedConnectionFactory.java and XIConfiguration.java)
- the adapter meta meta data object
All references must be identical

Similar Messages

  • Can Wcf-Custom Adapter implement Wcf-WebHttp Functionality?

    Can the Wcf-Custom adapter implement the same functionality as the Wcf-WebHttp adapter in BizTalk 2013? In particular, can it provide the same functionality as the operation map and the variable map? If not, is there any other way to provide Wcf-WebHttp
    functionality without hosting an adapter in IIS with an isolated host?
    Thanks!

    Yes, but...
    You can set the mappings on outgoing messages with some new Context Properties.  This describes how to do it on a Dynamic Port, but it should work the same on a static port. 
    http://masteringbiztalkserver.wordpress.com/2013/11/11/calling-restful-service-using-dynamic-send-ports-biztalk-2013/
    The receive side is a bit different since I'm 97% sure all the mapping happens in the BizTalk Adapter (WS-WebHttp) not any of the binding elements.
    However, you can essentially replicate that functionality with a Custom Pipeline Component.  In that case you would use the WCF-Custom Adapter with the webHttpBinding.

  • How to invoke a custom adapter from a BPEL process

    Hi guys,
    I've implemented a custom outbound adapter and deployed successfully on Weblogic V.10.3.4.
    My current installation also consists of Oracle SOA Suite 11g / JDeveloper 11g (11.1.1.4.0)
    In the Weblogic administrator's console,
    *1.* I navigated to:
    Summary of Deployments -> AdapterName -> Configuration -> Outbound Connection Pools
    *2.* Selected: javax.resource.cci.ConnectionFactory and added new JNDI name for Outbound Connection Instance: "*eis/HelloWorld*"
    My task is to invoke the custom adapter from a BPEL process.
    I altered the customAdapter-config.xml so as to be able to use custom adapter wizard from JDeveloper's "Service Adapters" palette,
    and fullfilled the custom adapter wizard's fields accordingly. The 3rd step of the wizard requires Connection Information.
    I added: "*eis/HelloWorld*" in the "*Connection Factory Location*" field.
    Deployed BPEL process successfully, but testing failed due to binding.jca-12510 error:
    "The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/HelloWorld'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/HelloWorld. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server "I tried to apply (just for testing) "eis/FileAdapter" in the "Connection Factory Location" field of the custom adapter wizard,
    and BPEL successfully invoked the adapter.
    Any ideas ?
    Thanks,
    George

    George, What deployment do you have this associated with?
    - D.J.

  • 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 ....
    Antonello

    Hi,
    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)

  • Error in Custom Adapter

    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 AM

    Hi,
    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

  • When to use Custom Adapter, Event Beans and Spring beans

    Hi,
    I have basic question on when or on what basis/scenario the Custom Adapter, Event Beans or Spring beans should be used.
    All three has same implementation methods.
    Please help me in understanding when to use Custom Adapters, Event Beans or Spring beans.
    Thanks,
    Sri
    Edited by: 897694 on Mar 7, 2012 8:12 AM

    custom adapters:
    you have to use a custom adapter when you don't find any adapter in ocep which will serve your purpose.
    Most of the times you use an adapter to connect the application with external things like http server, etc It can be both to listen the events or to send the events outside.
    Event Beans:
    This type of beans does most of the work that an adapter code does but in convention beans are not used to connect the application with external stuff
    You can use Beans as event sink etc In this case using an using an adapter is not suggestable.
    If you implement Interfaces like Initializing Bean for an adapter code it won't work properly, you have to use an event Bean in that case.
    Spring beans:
    Spring beans are used when the bean code doesn't implement EventSink or EventSender.
    These beans are used to enable something (eg: make ${wlevs_dev_home}/abc/a/b.java this path is not understandable by java code unless you override the path using a spring bean)
    Most of the things which doesn't need a connection between components in the application (eg cache loader: you can do this using spring beans and event beans both but spring beans doesn't need a connection with cache)
    Hope this small writeup helps you :)
    Edited by: Patha on Mar 8, 2012 9:10 AM

  • Where are attribute values when developing custom adapter?

    Hello,
    I am developing custom adapter for IDM 8. When the server wants to make reconciliation it calls method listObjects in my case and getUser. I wanted to ask if I am able to get values attributes of user which is passed to this method as parameter. Also how it is in general possible to get values of attributes in these methods. There is schemaMap which Maps names of resource attributes to IDM attributes (their names) but where do I get the values? Thank you very much for help.
    Martin
    PS: I have extended schema so not only AccountId which can be called by accountId = getIdentity(user). I need other atributes too.

    I have assigned work to implement custom adapter that can talk to our target applications? Can you please let me know the steps I need to follow to implement custom connector?
    Thanks
    Sudarsan

  • Adding custom Adapter information Parameters for Oracle Inbound Telephony

    Hello,
    I am implementing a custom adapter for Oracle Inbound telephony. I need to configure a few information parameters for my custom adapter. I am using the "Adapter Server Info <1-6>" fields on the Call Center html administration page (under the "Middleware" section). But I need to configure more than 6 parameters for my adapter. Does anyone know if we can add more "Adapter Server Info" fields?

    You may explore using a BPEL process to set the so header for calling the web service instead of directly calling it from BPMN process.
    Steps.
    1)Create a BPEL process.
    2)Select the checkbox "Expose as a SOAP service"
    3)In the BPEL process, set the SOAP header parameters that are expected by the called web service.
    Refer section
    6.22.2 How to Send SOAP Headers in BPEL
    of
    Oracle® Fusion Middleware
    Developer’s Guide for Oracle SOA Suite
    11g Release 1 (11.1.1.6.3)
    E10224-15
    4)Now in your BPM web service adapter , instead of calling the web service directly, call the web service endpoint of the newly created BPEL process.
    Hope this helps.
    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 Desai

    Hi 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

  • Calling web Service from the Custom Adapter.Is it Possible?

    Hi Experts,
                    I am having requirment in which i have to cal com.sap.aii.mapping.lookup.LookupService for calling web Service from the Custom Adapter.Is it Possible?
    Regards,
    Rajesh.D

    Hi Rajesh..
    Just looking the problem in another angle.. if there is no constraint that you have to use XI specific API to call the web service, why dont you use usual Java API used for calling a web service inside you custom adapter (I have Microsoft background.. donno exactly how it is done in Java,, but in .NET kind of a language it is possible). SInce your adapter is in Java itself and is capable of calling web service.. collect or lookup the data whatever you want and validate...
    Just a thought..
    VJ

  • 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ünchow

    I 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?

  • Class Cast Exception in a custom adapter processing module

    Hi,
    I am trying to create a Custom adapter module in my file adapter as a Local enterprise Bean.
    I have taken the "ConvertCRLFfromToLF" sample given by SAP as a reference, created an EJB module project, and deployed the enterprise archive to the J2EE engine.
    However, i am getting a Class Cast Exception in the Adapter Engine for my communication channel.
    Any help on this will much appreciated.
    Thanks & Regards,
    Renjith.

    HI,
    Managed to solve this..this was due to the additional jars which was included by the Developer Studio in the EAR file. We have to remoce the jars from the EAR, change the application.xml and sap_manifest.mf files to give reference to the jars already deployed in the J2EE engine.
    Thanks & Regards,
    Renjith

  • Developing Custom Adapter in PI by using Sample Adapter provided

    Hi Experts,
    I am developing a custom adapter by looking into below link.
    http://help.sap.com/saphelp_nwpi711/helpdata/en/69/e1e6667710415a9c331ec2e0715561/frameset.htm
    Could anyone please clarify the below Queries.
    1. Which project needs to be created as RAR file. Step1 or Step2 Project folder in NWDS?
    2. How to create the RAR file.
    Thanks in advance...

    Hi Veerendra,
    I was keep on trying the same from so many days. As you told, i have exported project "Test" as jar file and added it to connector module folder. Then, I exported "Test_RAR" as J2EE RAR and it was deployed with the following warnings.
    1. Exception has been returned while the [sap.com/com.test.YourAdapterName.adapter.ra] 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 5429350:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.test.YourAdapterName.adapter.ra].
              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:496)
              at com.sap.engine.services.deploy.server.application.ParallelAdapter.rollbackPart(ParallelAdapter.java:318)
              at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:530)
              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:380)
              at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhases(ParallelAdapter.java:428)
              at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:499)
              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1487)
              at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:806)
              at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:788)
              at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:776)
              at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:105)
              at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:78)
              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:91)
              at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:61)
              at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:866)
              at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:814)
              at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:644)
              at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:363)
              at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:252)
              at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:897)
              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:368)
              at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
              at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
              at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
              at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
              at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
              at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
              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:327)
    Caused by: java.lang.UnsupportedClassVersionError: com/test/YourAdapterName/adapter/ra/SPIManagedConnectionFactory : Unsupported major.minor version 50.0
              at java.lang.ClassLoader.defineClass1(Native Method)
              at java.lang.ClassLoader.defineClass(ClassLoader.java:677)
              at com.sap.engine.boot.loader.ResourceMultiParentClassLoader.loadClassLocal(ResourceMultiParentClassLoader.java:183)
              at com.sap.engine.boot.loader.MultiParentClassLoader.findClassInLoaderGraph(MultiParentClassLoader.java:312)
              at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:271)
              at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:243)
              at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:315)
              at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122)
              at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303)
              at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363)
              at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:345)
              at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:300)
              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:374)
              ... 28 more
    and i have created NameSpace, Adapter metadata using YourAdapterName.xml and also Comm channel in ID. But while checking in Comm Channel monitoring it shows an error like... "No adapter registered for this channel".
    While checking in sdn regarding the warnings in NWDS. It says that "application alias already exists". I couldn't figure it out.
    Please let me know if u have any solution for this. Your reply is highly appreciated.

  • 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
    Haseeb

    hi,
    check this document:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00838345-708c-2a10-1199-9514c0b0a91c
    regards.

  • Seeburger AS2 Adapter implementation in PI 7.1

    HI Experts,
    We have seen lot of implemetation of seeburger adapters in PI 7.0 but didnt got any chance to look ahead for any documents related to seeburger AS2 adapter implementation in PI 7.1 .
    Request if you can please guide or provide some hands on documents which can give the clear overview of how to configure AS2 adapter in PI 7.1 and its parameters.
    Thanks & Regards,
    Abhishek

    Hi,
    refer the blog by prateek:-
    http://wiki.sdn.sap.com/wiki/display/XI/ParametersUsedinModuleProcessingforSeeburgerAS2AdapterforSAP-PI
    u can also refer other blogs for details search on SDN
    http://www.sdn.sap.com/irj/scn/advancedsearch?query=seeburger
    I think everything remains same.
    chirag

Maybe you are looking for