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

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

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

Similar Messages

  • Seeburger SFTP - Message Transformation Bean Issue

    Using Seeburger SFTP adapter to read a tab delimited file. File is being successfully read; however, content conversion need to be performed to convert the file content to XML.  Thus, using Message Transformation Bean with the following module parameters.  
    Issue: It is reading the file as is u2013 there is not content conversion is being performed. 
    Processing Sequence:
    1      localejbs/Seeburger/solution/sftp                Local Enterprise Bean     solutionid
    2     localejbs/AF_Modules/MessageTransformBean          Local Enterprise Bean     mtb
    3     localejbs/CallSapAdapter                    Local Enterprise Bean     exit
    Module Configuration:
    mtb          Transform.Class                          com.sap.aii.messaging.adapter.Conversion
    mtb           Transform.ContentType               text/xml;charset=utf-8
    mtb          xml.conversionType               SimplePlain2XML
    mtb          xml.documentName               XXX_EXPENSES_mt
    mtb          xml.fieldContentFormatting     trim    
    mtb          xml.fieldNames                    FIELD1,FIELD2,FIELD3,FIELD4
    mtb          xml.fieldSeparator               '0x09'
    mtb          xml.processFieldNames               fromConfiguration
    mtb          xml.structureTitle               RECORD
    The following the noticeable details on CC:
    Error type: TASK_ERROR >> Error date: 12/5/10 12:42 PM >> Description: Polling finished with errors. 1 file initiated. 1 file not polled due to errors.
    Message initiated succesfully
    Error type: TASK_ERROR >> Error date:  >> Description: File <amex.dat> could not be polled  from directory </usr/sap/interfaces/FTP1/send> on host <sapdv1ci>; Reason: removeFile: File xxx.dat could not be removed. SftpStatusCode: SSH_FX_NO_SUCH_FILE; Reason: No such file
    Any help is greatly appreciated.
    Thanks

    Check the following...
    1. Make sure you don't have any scripts running at your target folder.
    Example: If you are reading your file from TEST folder make sure you don't have any scripts running here.
    2. In File Setting section make sure you uncheck Delete file checkbok.
    Regards
    Srikanth Baki

  • Error using Message Transform Bean in SimplePlain2XML in file sender

    Hi guys.
    Im using  Message Transform Bean to convert from file to xml in file sender.
    My structure look like this:
    ROW (1..n)
    >TRANSPORTES (1)
    >ENTREGAS (1..n)
    And I have configured the module like this:
    AF_Modules/MessageTransformBean - transform
    transform - Transform.Class - com.sap.aii.messaging.adapter.Conversion
    transform - xml.ENTREGAS.endSeparator - 'nl'
    transform - xml.ENTREGAS.fieldFixedLengths - 1,30
    transform - xml.ENTREGAS.fieldNames - TIPO,NUM_ENTREGA
    transform - xml.ENTREGAS.keyFieldValue - E
    transform - xml.TRANSPORTES.endSeparator - 'nl'
    transform - xml.TRANSPORTES.fieldFixedLengths - 1,30
    transform - xml.TRANSPORTES.fieldNames - TIPO,NUM_TRANSPORTE
    transform - xml.TRANSPORTES.keyFieldValue - T
    transform - xml.conversionType - SimplePlain2XML
    transform - xml.documentName - MPrueba_Zip
    transform - xml.documentNamespace - http:/XXXXXX.es/XXXX/sap/prueba
    transform - xml.keyFieldName - TIPO
    transform - xml.processFieldNames - fromConfiguration
    transform - xml.recordsetName - row
    transform - xml.recordsetStructure - TRANSPORTES,1,ENTREGAS,*
    Im getting this error and I don´t know why:
    Error: com.sap.aii.messaging.adapter.trans.TransformException: Transformer Conversion3.0.5227 Error initializing Class: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.fieldFixedLengths' or 'xml.fieldSeparator' is missing (4409) Parameter 'xml.fieldNames' is missing (4403) ; nested exception caused by: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: (4408) Parameter 'xml.fieldFixedLengths' or 'xml.fieldSeparator' is missing (4409) Parameter 'xml.fieldNames' is missing (4403)
    Why am i doing wrong?????
    Thanks a lot!!!

    Hi
    For Complex conversion you have to use xml.conversionType as "StructPlain2XML"
    http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
    Regards
    Ramg

  • Error while using Message transform Bean

    Hi All,
    I am using message transform bean in the receiver channel. The structure I have used is as follows.
    Transform.Class    com.sap.aii.messaging.adapter.Conversion
    Transform.ContentType    text/xml;charset=utf-8
    xml.conversionType   SimplePlain2XML
    xml.documentName      MT_DataExtract
    xml.documentNamespace    http://ce.corp.com/xi/ACA/HR_INT_XXX/EmployerReporting
    xml.endSeperator   'nl'
    xml.fieldNames     pernr,l_name,f_name,m_name,perid,p_subarea,e_group,e_subgroup,status,c_code,pa_text,str_add,h_city,h_state,h_zcode,z1_org,z2_org,rep_hours
    xml.fieldSeperator   ,
    xml.singleRecordType      Employee_Details
    XML structure would be as
    <Employee_Details> 
    <pernr></pernr>
    - <l_name></l_name>  <f_name></f_name>
    <m_name />
    <perid></perid>
    <p_subarea></p_subarea>
    <e_group></e_group>
    <e_subgrp></e_subgrp>
    <status></status>
    <c_code></c_code>
    <pa_text></pa_text>
    <str_add></str_add>
    <h_city></h_city>
    <h_state></h_state>
    <h_zcode></h_zcode>
    <z1_org></z1_org>
    <z2_org></z2_org>
    <rep_hours></rep_hours>
    </Employee_Details>
    I am getting error as Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.lib.util.configuration.ConfigurationExceptionSet: The following configuration errors were detected: - Either recordTypes or singleRecordType needs to be set .
    Please help me to resolve this error.
    Thanks,
    Shankul

    It's not just that parameter, Please change your configuration as explained in the blog i shared.
    There is a example which has expected structure and the conversion parameters.
    Your target xml should be like below.
    The XML structure of the source file should follow the same structure as the result of the SimplePlain2XML conversion.
    <resultset>
    <row>
    <column-name1>ABC</column-name1>
    <column-name2>12345</column-name2>
    <column-name3>Text1</column-name3>
    </row>
    <row>
    <column-name1>XYZ</column-name1>
    <column-name2>67890</column-name2>
    <column-name3>Text2 Text3</column-name3>
    </row>
    </resultset>
    Examples of Content Conversion Using MessageTransformBean (SAP Library - SAP Exchange Infrastructure)

  • Seeburger AS2 Adapter sending message error

    I have configured a FAck scenario as described by the Seeburger Manual and am testing a AS2 messaging scenario with a vendor (basically the inbound EDI message is passed to the Seeburger splitter to create a new message for the inbound order, and then the existing payload is mapped to a Funcational Acknowledgement and sent back to the vendor).  I receive the message fine and the message split to create the order works fine, however when the FAck is passed to the AS2 receiver adapter (for transmission to the 3rd party) I get the following error:
    LOCATION [null, null, 91fcf4f0-5223-11dd-9c8d-5cd90a641602] >> ERROR TYPE [, COMPONENT_ERROR, not retryable, not fatal]] >> DESCRIPTION [AS2 Adapter failure >> MID
    MID <[email protected]22.2> already exists. - Duplicate will not be sent [LOC: com.seeburger.as2.component.AS2Client.storeMID]
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent
    I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
    If I extract the same inbound message from the payload and pass it in using a file adapter (rather than the AS2 sender adapter) then the functional acknowledgement is created and transmitted to the vendor without any issues ... 
    Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
    Regards,
    Jason

    Hello ,
    same issue occurred in my system
    Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent
    I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
    Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
    Please advise asap.

  • How to deal Inhouse files using Seeburger AS2 adapter...!!!

    Hi all,
    Has anyone managed to configure the Seeburger AS2 adapter for XI successfully to process multiple inbound message types.
    We have an issue here with inbound messages being received by the AS2 adapter. We currently have it configured for inbound deliveries(Which deals with EDI files) which is working fine. The issue is that we would now like to send other messages as well. It seems the AS2 adapter only looks at the sender/receiver party combination to determine the correct sender agreement, but does not look at the message type which is a limitation. I have heard mention of a splitter module which can be used to distinguish between different messages and pass them to the correct sender agreement for processing, information on this is thin on the ground to non existent.
    I have few custom Inhouse files where i need to recieve through AS2 adapter.
    I need to differentiate the messages hitting to my communication channel.
    ex:
    1st message will be having
    HDR PICKS
    2nd message will be having
    HDR PURCH
    so based on the second field which has "PICKS" or "PURCH" , i need to pass the message to run the corresponding map.
    How i need to configure to acheive these kind of custom Inhouse files through AS2 adapter??
    Do i need to use splitter for these as well?? If yes how i need to use?
    Is there any setting we can make at Sender AS2 adapter to differentiate each message??
    Waiting for the answers.
    Kindly reply if anyone knows.
    Thanks&Regards
    Seema.

    Hi,
    i have setup a scenario with edifact (different message types) using as2.
    first i had to create a mapping using bic.
    edifact_xxxx
    in: edifact_service
    out: functional acknowledgement.
    in the mapping code i adjusted the called mapping, standard it will use see* changed it to e2x* (custom mapping)
    in your case using flatfiles maybe you should take a look at the VDA structure, these files are also defined under inhouse.
    when you define a input file adapter are you getting a classifier message?
    like
    <classifier><type>Edifact</type><classifierMappingID>XXXX</classifierMappingID><encoding>US-ASCII</encoding><additionalIdentifier></additionalIdentifier></classifier>

  • SEEBURGER AS2 Adapter Security

    Hello,
    I am running into an issue on the install of the SEEBURGER AS2 Adapter.  We currently have other AS2 communication software in place, which are in our DMZ for security purposes. However, we do not want to put our SAP XI server in the DMZ because we would like it more protected. We are getting around this problem by using a reverse proxy scenario to get it through our firewall.
    Is there a more effecient way to install the SEEBURGER AS2 adapter without exposing the entire SAP XI server to the DMZ?
    Thank you, any help or advice would be appreciated.

    Hi Carley,
    I will tell you something about Seeburger Adapters in detail, Just see if it helps...
    Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
    These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
    Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
    The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
    1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
    2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
    3. create a one to one mapping between input en output.
    4. export the metadata in xsd or sda format for import in XI
    5. generate an SDA which can be deployed in XI and used as a module.
    Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    Regards,
    Abhy

  • Content based receiver determination with Seeburger AS2 adapter

    We are planning to use the Seeburger AS2 adapter on our XI 3.0 installation to post custom XML documents to XI from external business partners.  The problem we have is to do the receiver and interface determination based on the xml message type that is submitted.  How can we identify what is the name of the root xml node (which is representing the message type that was submitted to us) during the receiver determination and specify conditions for the receiver determination based on this?  We can not use the Seeburger Classifier module here as this is only determining the mapping name to be used for an EDI conversion but can not handle any type of XML message.

    Rudy,
    I think the easiest way would still be the ReceiverDetermination and creating an XSD that contains the main important TAGs from the different messages.
    That should allow you to test for the existing of certain important TAGs or check the value of some TAGS.
    I don´t know about aedaptive-adapters, but I don´t think that they are Drummond-Certified. Check out...
    http://www.drummondgroup.com/html-v2/as2-companies.html
    Without this certification, a lot of your partners might not allow you to use this adapter if you wanna make AS2 with them.
    Greetings
    Stefan

  • Seeburger AS2 Adapter - How to extract copy of file sent out ?

    Hi Experts,
    The scenario is SAP R/3 sends idoc to PI.  PI converts this into a flat file and sends to Trading Partner through Seeburger AS2 adapter.
    We can trace the message content in XML format within PI using SXMB_MONI or RWB.   How to extract a copy of the Flat file converted by AS2 adapter and sent to Trading Partner ?
    Thanks very much for you help !
    Thanks,
    Rukmani

    >>Was hoping for a method that does not need additional coding.
    None of the two methods I suggest require coding. First method just require adding 1 line in module config in your communication channel. Second method requires one addition config in receiver determination and agreements.
    >>is there a way to get the converted message content from SeeBurger Workbench even for successful messages ?
    No. If you have purchased Message Tracking, then you could configure that for your scenarios to view payloads. However, this method will definitely need some coding.
    Regards,
    Prateek Raj Srivastava

  • Client Auth  and SSL with Seeburger AS2 adapter

    Hello All,
    We are using the Seeburger AS2 adapter in our landscape and I am in the process of setting the same up and have made quite some progress in all my issues.
    and I  hope that you will be able to help me out.
    1. Server SSL on Receiver AS2 adapter
    I am sending a message from XI using the Receiver AS2 adapter to my AS2 test tool using Server SSL.
    This is working perfectly fine. In my AS2 adapter I have selected HTTPS as the protocol and the message goes via SSL to the target test tool, is processed and the MDN comes back to XI perfectly.
    The issue here is :
    Irrespective of what is provided in the Server Certificate ( Keystore) , the message goes to my target test tool. I even left this field blank with no certificate entry and still the SSL connection was established and the message went to the target system.
    Is there no validation that XI does here? I am lost what is the use of this entry Server Certificate if XI blindly accepts all SSL connections.
    I am using a Decentral Adapter Engine with LoadBalancer.
    2. Client Auth on Receiver AS2 Adapter
    I tried to perform Client Authentication by proving my Server's private key in the AS2 adapter. The corresponding public key is loaded in my partner's Keystore.
    XI error's with the error "SSL handshake failed - Bad Certificate" .
    I am not sure why XI is erroring out here and I have a feeling that I have misunderstood the use of the fields in the AS2 adapter,
    Server Certificate ( Keystore) and Private Key for Client Authentication.
    Has anyone tried this? If further details are needed, I will be able to furnish the same.
    Regards,
    Bhavesh

    Hello Jens,
    Thanks for your reply.
    1. The Encryption and Signature part of the Interface is working absolutely fine and I use the same concept highlighted by you - The Sender always signs the message with his private key and encrypts with message with the partner's public key in the corresponding agreement.
    2. Server SSL is also working perfectly fine, i.e, when XI initiates the connection the SSL connection is established to the partner.
    3. Mutual Auth was the issue where I was getting the bad certificate issue.
    To investigate further I moved the same setup to my Central Adapter Engine and all the issues I had described above seem to have vanished and things work exactly as I was expecting, ie.
    The field : Server Certificate (Keystore) is used to provide the Target System's Server SSL's public Certificate.
    The field : Private Key for Client Authentication is used where XI provides its own Server SSL's private key for Mutual / Client Authentication.
    The problem seems to be with my Decentral Adapter engine and not my central adapter engine and so I guess,
    1. I either have the incorrect certificates on my Decentral Adapter Engine.
    2. I also have 2 instances of a Decentral Adapter Engine with a Webdispatcher and so maybe the 2 Visual Admin's of the 2 Decentral AE are inconsistent.
    3. Maybe it was just a long day and I did something wrong
    Will investigate further for the root cause but I am glad that my concepts remain intact and things do work as I expected them to work.
    A blog on all this is on the cards sometime soon.
    Cheers,
    Bhavesh

  • AS2 system integration without using Seeburger AS2 adapter

    Hi, All:
    One of business partner need to have AS2 transport protocol to communicate with, my question is, can we integrate with business partner without going Seeburger AS2 adapter ?
    Thanks
    Liang

    I think that is not possible. If it were, we wouldn't need anymore the Seeburger adapter and could write our own modules...
    Here have a look at this.
    /people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
    And this.
    https://websmp202.sap-ag.de/~sapidb/012006153200000124082007E/SAPXI30_AS2Adapter.pdf
    AS2 adapter
    Edited by: Arman Eker on Apr 7, 2010 5:19 PM

  • Seeburger AS2 Adapter: "MDN not signed"

    Dear all,
    we just updated our test system from XI 3.0 to PI 7.1. Now we are facing a problem with our Seeburger AS2 Adapter.
    I sent out a message via AS2 and get the follwing error message in Seeburger AS2 Monitor:
    "MDN not signed"
    In the Receiver Communication Channel I checked the Option "Sign MDN". In XI 3.0 this Scenario was working perfectly. So I contacted our communication partner and asked them if our AS2 message really contained a request for a signed MDN. Our commnucation partner confirmed and sent the MDN as text file to me. This text file shows that the MDN is signed. So it seems that the Seeburger AS2 adapter does not notice that the received MDN is a signed one. But why? Do you have an idea?
    Just for testing purposes I unchecked the "Signe MDN" option. In this case the transmission finished successfully.
    Who can help?
    Thanks
    Michael

    Dear Vikrant,
    many thanks for your reply. But I am not sure if we are really facing the same issue as you described it in your article.
    Currently we have this situation:
    When I send out a message the Seeburge Workbench provides only the following error message:
    "MDN not signed"
    Via the Recovery Monitor I can check the received MDN. Here I can see that the MDN is signed and positive.
    In the Runtime Workbench I checked the following:
    1. In the Message Monitor (Adapter engine) the message is in status "System Error". Here are the details:
    Message could not be forwarded to the JCA adapter. Reason: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
    Adapter Framework caught exception: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
    Delivering the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received..
    2. The Communication Channel Monitor shows the following error messages:
    Error type: REPORT_ERROR >> Error date: 12/14/10 12:02 PM >> Description: MDN not signed [12/14/10 12:02 PM]
    Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: Negative synchron MDN received., SEEBURGER AS2: Negative synchron MDN received.
    I do not understand why the MDN is recognized as negative and unsigned even if the plain text version of the MDN shows that it is signed and positive.
    In your article you recommend to create a sender communication channel for MDN and a corresponding sender agreement. We already did that in XI 3.0 to forward the MDN as STATUS IDOC to SAP ECC.
    Maybe you have an additional idea?
    Thanks
    Michaek

  • Seeburger AS2 Adapter scenario ?

    Hi Frnds,
    I want See Burger ,AS2 Adapter end to end scenario with screen shots, If anybody know link or having end to end scenario pls share to me its too urgent.
    Regards,
    Ravi kumar

    Hi ,
    Ravi, I am also looking for seeburger scenario, i got information from forum, i providing info, i hope it will give some idea... if its not excuse me....
    The SEEBURGER FTP/VAN Adapter is responsible for transmitting files according to the File Transfer Protocol, with the particular support of various VANs. This protocol was installed as a user gateway protocol by several of the largest VAN providers, such as IBM, GE and Sterling IIB and Sterling Commerce.
    The FTP/VAN adapter must be configured in the configuration part of the Integration Builder. The adapter is based on the Adapter Framework and is executed by the SAP J2EE Adapter Engine.
    The FTP/VAN Adapter supports the following protocols:
    • IBMIE VAN, all report options.
    • GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
    • EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
    • Sterling Commerce and Sterling IIB.
    • MCI EDI*Net.
    The following FTP options are supported:
    • SSL, both IMPLICIT and AUTH_TLS support, server authentication.
    • All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
    • Active and Passive connection modes.
    • "KeepAlive" feature.
    • Binary, ASCII and custom transfer types.
    Seeburger adapters like OFTPS,AS2,X400 are used for B2B scenario where the file is coming through WAn network or mailbox. As XI dont have capability to convert the EDIFACT format file to XML the same work will be done by seeburger adapters.
    The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
    Supported EDI formats include:
    • ANSI
    • EDIFACT
    • INHOUSE
    • IDOC
    • XML Schema
    • XML DTD
    • CSV
    • Delimited Data
    • positional data
    • SWIFT
    • EANCOM
    and many more.
    See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
    AS2 vs OFTPS:
    AS2 & OFTPS
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    Please see the below blogs
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Details on XI EDI adapter from seeburger
    Check this for Conversions-
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration
    https://www.sdn.sap.com/irj/sdn/forums
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Details on XI EDI adapter from seeburger
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    EDI Adapter by SeeBurger
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
    B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
    Integrating XI with SeeBurger
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
    Regards,
    Raj

  • 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

  • Seeburger AS2 Adapter - Cookie Control

    Hello together,
    on my current project I am facing this kind of problem during AS2 communication:
    Our partner provides us a cookie containing a session ID. Using this cookie we are able to send messages to our partner. This cookie has no expiration date, because we should be able to send messages for an unknown amount of time, and if it had an expiration date, some messages would fail for no logical reason.
    On the partner side, though, the sessionIDs are invalidated after 600 seconds of inactivity. This is done for security reasons, as it is considered that after this amount of inactivity, the connection must end.
    When we tried to connect after 10 minutes, using this cookie with the old sessionID, the response is an invalid SessionID or session expired.
    Our partner suggested to delete the cookie after sending messages. But on the AS2 adapter configuration I see no option for cookie control.
    Any ideas? Keep in mind that our partner would rarely change its setup.
    With kind regards
    Frank Opitz

    Am not sure but do AS2 adapters have a Cookie Option? Or are you talking about Http Keep Alive option?
    Can you try to disable this option in the Receiver As2 adapter and give it a shot?
    Regards
    Bhavesh

Maybe you are looking for