JMS Adapter EJB Add-on

hi
I want to add this code to change  ONLY the JMS_IBM_Last_Msg_In_Group JMS Parameter
any way to do it with EJB after all the messages are sent with the adapter?
Thx,Shai
MQConnectionFactory factory = new MQConnectionFactory();
factory.setQueueManager("QM_host")
MQQueue destination = new MQQueue("default");
destination.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ);
Connection connection = factory.createConnection();
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
MessageProducer producer = session.createProducer(destination);
String groupId = "ID:" + new BigInteger(24 * 8, new Random()).toString(16);
for (int i = 1; i <= 5; i++) {
    TextMessage message = session.createTextMessage();
    message.setStringProperty("JMSXGroupID", groupId);
    message.setIntProperty("JMSXGroupSeq", i);
    if (i == 5) {
        message.setBooleanProperty("JMS_IBM_Last_Msg_In_Group", true);
    message.setText("Message " + i);
    producer.send(message);
connection.close();

Hi Shai,
I'm not too convinced that this is the XI-way to go. The JMS adapter will have its own MQ Connection and handle the communication with JMS (putting the message on the queue, etc.)
I believe, you should try one of the following options (even though I don't know whether they will work):
Set Additional JMS Properties in the Communication Channel configuration (this will only allow a fixed value to be set)
Implement a module that accomplishes this task. However, I don't know if this is supported by the Module Chain.
Have you asked SAP (through an OSS Message) whether this can be accomplishe in a Module?
regards,
Peter

Similar Messages

  • Complex XML to Plain in JMS adapter "Content conversion module"

    Hi!
    I have read the document on "How To… use the content conversion module with XI3.0 J2EE JMS Adapter", and it says only SimpleXML can be converted in the receiver channel.
    I had hoped for a solution at least as good as in the File/ftp adapter, where complex XML can be transformed to files.
    Are there plans to include complex XML conversion in the JMS adapter?
    I can not use the file adapter as I need to change the file name and destination, and that can not be done by adding own module to its single module.
    Any idea how I can achieve what I want?
    To only way I can find, is to create a file using the file/ftp adapter, and then pick it up again and treat all the lines as the same structure (one row = one xml field). Then output this new xml message to file, using the JMS adapter and add any modules with name and destination determination.
    Appreciate any help!
    Regards,
    Oeystein Emhjellen

    Hello,
    Have you tried to use an XSLT mapping within the IE?
    I have, at one customer site, created a XSLT message mapping which converts the  XML to a fixed length ASCII file format. I than added the XSLT message mapping as a second mapping step on the interface mapping.
    In this case I was able to publish a fairly complex fixed length file format to MQ Series via the JMS adapter.
    /Johan

  • How to add the JMS adapter property in BPEL1.1 version

    Hi,
    I am working on the Jms adapter by using BPEL version1.1 and i am want to add some Jms property to send with Jms message.We have option to add the Jms property in BPEL2.0 version. But i am not able to add Jms property in BPEL version1.1.
    Please help me
    SOA 11g : 11.1.1.5

    Thanks for everyone's replies. I am now able to set the parameters for the sequence file, just that I added a property node for the sequence file path and the sequence before loading the parameters. That did the trick and the rest was easy. Also for Goto, with some digging, I was able to add a custom property step if it fails or passes the step. It works like a charm. I'm attaching a modified version of my code in LV 7.0 format.
    Attachments:
    Dynamic Sequence File-1.vi ‏175 KB

  • JMS adapter: Adapter specific message attributes

    Hi,
    I have a synchronous SOAP to JMS (MQ series) scenario where I’m using sync/async bridge (without BPM).
    I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
    The “standard” receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isn’t suitable for correlating anything using the field JMS Correlation ID.
    NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
    Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
    Now the problem isn’t setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key ‘DCJMSCorreleationID’). The problem is to actually have XI correlate the request with the response.
    Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isn’t available, what I figure is that I need to find a MQ message property to use and then use the ‘Set MSProperty to’ part instead – this property surely needs to be large enough to contain the XI message ID.
    So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
    where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (‘Name of reply queue’, 48-byte character string) should be able to hold the XI message ID. So I add ‘MDQR’ in the ‘Specify additional JMS message properties’ and set the ‘Java Type’ to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
    Runtime:
    When looking in MDT I see:
    New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
    I looks like a success! No data is however set in the field when looking at messages being put on MQ.
    If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
    Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
    What does this error mean?
    I have of course clicked ‘Use adapter Specific Message-Attributes’ and also the ‘Specify additional…’. In other words everything look ok in configuration.
    Since I’ve also put a check mark in ‘Fail if adapter specific message attributes is missing’ I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isn’t right – the value of the property never reached MQ.
    Now I’ve tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
    Anybody got some ideas?
    Best Regards,
    Daniel

    Hi Vijay,
    Thanks for your replay,as per your input i creted dynamic configuration method,
    i taget structure  luks like this
       <Data>
           <Mesage>
                 <gl_update>
                      <header>
                            <ean1>
                            <ean2>
                      </header>
                  <gl_update>
           <Message>
    i written UDF and mapped to header element gl_update,
    but i am getting  below error message in MONI
    SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
      <SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
    i think there is no prob with UDF,its executing ,giving warning messages
    help me on this,
    Regaards
    Raj

  • How to hanlde breaked large messages in sender JMS adapter

    Hi,
    I have been asked like 'how can we handle breaked large messages in sender JMS adapter?'and lets say I am getting some messages as it is and some are breaked into small segements for the mesaages that are large....
    do we need to use module,if so is there any standard module that we can use to hanlde this type of scenarios?
    thank you in advance.
    babu

    http://biemond.blogspot.com/2009/10/jms-request-reply-interaction-pattern.html
    if you check the blog of edwin, see his comments at the bottom
    there he gives a suggestion how to add the selector properties to filter on
    and this one is maybe helpfull
    http://blogs.oracle.com/adapters/2010/05/configuring_request-reply_in_jmsadapter.html

  • Error in  JMS Adapter  for MQ series

    We have configured a JMS Adpater to connect to  MQ Serries queue manager running on our local server. The XI Server is a remote server where JMS adapter is deployed.
    Upon deployment we see following string in JMS adapter log -
    Sender channel. Details: com.ibm.mq.jms.MQQueueConnectionFactory
    And the status of Adpater is RED.
    The Adpater is configured in sender mode.
    We have created a local queue in Queme Manger and a Server Connectio  channel which is being used in adpater configuration.
    Please suggest what could be the missing link here.
    Appreciate if you can provide us link s to any docuemtn which details the steps to configure an MQ JMS adapter.
    Thanks,
    Garima

    Hi Garima,
    Please check the following:
    1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
    2. Check the existence of your JMS drivers.
    3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    Any of the above solutions should help you solve the problem.
    Regards,
    Abhy

  • Using JMS adapter with J2ee native queuing system

    Hi there,
    As far as I have understood J2EE contains it's own native queuing system (JMS). Since the J2EE is part of the WAS, shouldn't it be possible to somehow use XI's JMS adapter in conjunction with this native JMS?
    I've tried to search many places in many ways, but haven't been able to find any info. Is it possible at all?
    Hope, some of u guys can help out there:-)
    Regards,
    Daniel

    Hi Keith,
    It looks as if you are in the same situation.
    We have this working very nicely now and I'm happy to share. In fact I was just granted wiki permissions so I can add the information there along with screen shots.
    Informaiton on this configuration is very scattered but I imagine many people would find it useful for integrating with Mainframes without adding any complexity to the legacy environment. Let me come back to you with some more inormation, but for now you can get started with this:
    Insert a module as the 3rd line in your Module Processing Sequence to use AF_Modules/MessageTransformBean and give it a key in order to associate with the parameters you will need to type in below. These parameters are very similar to normal XI File adapter parameters.
    SAP Note 793922 has more info on the parameters... not the greatest reference I know.
    Also this has some info...
    http://help.sap.com/saphelp_nw04/Helpdata/EN/57/0b2c4142aef623e10000000a155106/content.htm
    I'll try and get some screen shots up on the Wiki.

  • XML document conversion to Plain document in XI using JMS Adapter?

    Hi,
    We are trying to send an soap based XML document from ECC to MQSeries 6.0 using PI 7.0. I created receiver communicaiton channel to MQ with the below modules
    1. AF_Modules/MessageTransformBean - Module Key XML2Plain
    2. SAP XI JMS Adapter/ConvertMessageToBinary - Module Key CallJMSService
    3. SAP XI JMS Adapter/SendBinarytoXIJMSService - Module Key Exit
    Module configuration parameters I provided are
    XML2Plain-  Transform.Class com.sap.aii.messaging.adapter.Conversion
                       TransformContentType text/plain;charset=utf-8
                       xml.addHeaderLine 0
                       xml.conversionType SimpleXML2Plain
                       xml.fieldSeparator ,
                       xml.fixedLengthTooShortHandling Cut
    The payload I am using is
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Company xmlns:ns0="http://bnsf.com/hr/tm">
       <Row CCODE="1001" DESC="test company"/>
    </ns0:MT_Company>
    When I test in RWB
    1. The channel monitoring shows green and the below message
    "Successfully connected to destination 'queue:///QL_DAVEOUT?targetClient=1"
    2. RWB shows error message "Error while sending message:invalid content type  for SOAP:TEXT/HTML;HTTP 500 Timeout"
    3. when I look at the message, I see the last message shows as
    "2008-06-16 15:16:44 Success Transform: transforming the payload ..." and I do not see any more messages.
    Can anyone help me here? Thanks in advance

    I changed the payload to
    <xml version="1.0" encoding="UTF-8">
    <ns0:MT_Company xmlns:ns0="http://bnsf.com/hr/tm">
    <row CCODE="1001" DESC="TEST" />
    </ns0:MT_Company>
    this time i am getting
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_SAP_COMPANY_TO_MQ_COMPANY_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17)</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_SAP_COMPANY_TO_MQ_COMPANY_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy220.processFunction(Unknown Source) 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.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy220.processFunction(Unknown Source) 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.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17)(:main:, row=4, col=17) -> com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1872) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1872) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</Trace>

  • Help on Dynamic queue name in JMS Adapter

    Hi Experts,
      Could you please explain how to configure dynamic queue name in JMS Adapter.
    My requirement is i would have to add the date and time to JMS Queue Name in receiver JMS Adapter.
    Thanks in Advance
    Chilla

    hi,
    as it's not in Adapter-Specific Message Properties
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
    looks like you cannot do it with jms adapter in standard
    use proxy or your own adapter instead
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • XI 3.0: Preserve trailer spaces with JMS Adapter

    Hi everybody
    Does anybody knows how it is possible to preserve the trailing spaces in a message coming from JMS adapter?
    I have a fixed-length field that is filled with a left space trailer, but the space is removed by (i think) the adapter.
    Does exists something similar to "whitespace=preserve" for the datatypes???
    Thanks in advance.

    If somebody is interested, just add the
    xml.<structname>.fieldContentFormatting = nothing to the module configuration params.
    I derived this one from the configuration guide of the File Adapter

  • JMS Adapter module content conversion

    Hi,
    I'm developing a module for the jms adapter(sender). My requirement is to parse the XI message(text) using some XML parsing api and do some formatting, logic etc and to make the jms adapter create a xml file with the processed information. Jms File Content Conversion does not suit our requirement and thats the reason we are trying this option.
    My understanding is: Access the  payload in the "process" method of the local ejb, apply XML parsing using JDOM etc, make a xml which should be the output of the jms adapter. This xml will be the xml with my user defined tag elements after content conversion. Can i form this xml and assign to the inputModuleData? Will the jms adapter use this string to create the xml and send to IS? Are there any other parameters to be set or processes to be done?
    Also in which sequence should I put my adapter module in communication channel.
    ================================================
    My code snippet:
    public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData)
            throws ModuleException
              Object obj = null; // Handler to get Principle data
              Message msg = null; // Handler to get Message object
            try
                   obj = inputModuleData.getPrincipalData();
                   msg = (Message)obj;
                   AuditMessageKey amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
                   Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---efore reading payload");
                   try
                        XMLPayload xmlpayload = msg.getDocument();
                        String messageStr = xmlpayload.getText();
                        String inputStr = null;
                        String tags[] = new String[2];
                        String values[] = new String[2];
                        Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---before content conversion");
    String tagvalue1 = messageStr.substring(messageStr.indexOf("BEGIN+"), messageStr.indexOf("'");
    String tagvalue2 = messageStr.substring(messageStr.indexOf("'"), messageStr.lastindexOf("ENDING");
                             tags[0] = "tag1";
                             tags[1] = "tag2";
                             values[0] = tagvalue1 ;
                             values[1] = tagvalue2 ;
                             Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---after content conversion");
                             Document xmldoc = null;
                             DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
                             DocumentBuilder builder = factory.newDocumentBuilder();
                             DOMImplementation impl = builder.getDOMImplementation();
                             org.w3c.dom.Element e = null;
                             Node n = null;
                             xmldoc = impl.createDocument(null, "MT940", null);
                             org.w3c.dom.Element root = xmldoc.getDocumentElement();
                             for(int i = 0; i < tags.length; i++)
                                  e = xmldoc.createElementNS(null, tags<i>);
                                  n = xmldoc.createTextNode(values<i>);
                                  e.appendChild(n);
                                  root.appendChild(e);
                             Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---before dom creation");
                             DOMSource domSource = new DOMSource(xmldoc);
                             ByteArrayOutputStream myBytes = new ByteArrayOutputStream();
                             Result dest = new StreamResult(myBytes);                         
                             TransformerFactory tf = TransformerFactory.newInstance();
                             Transformer serializer = tf.newTransformer();
                             serializer.setOutputProperty("indent", "yes");
                             serializer.transform(domSource, dest);
                             Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---before setting principal data");
                             byte[] docContent = myBytes.toByteArray();
                             if (docContent != null) {
                             xmlpayload.setContent(docContent);
                             inputModuleData.setPrincipalData(msg);
                             Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---after setting principal data");
                   catch(ArrayIndexOutOfBoundsException e)
                        e.printStackTrace();
                   catch(StringIndexOutOfBoundsException e)
                        e.printStackTrace();
                   catch(TransformerException e)
                        e.printStackTrace();
                   catch(Exception e)
                        e.printStackTrace();
            catch(Exception e)
                ModuleException me = new ModuleException(e);
                throw me;
            return inputModuleData;

    This is for sender channel. The doubt in adapter module is in the process block how will I get the main data being read by the jms adapter from the text file.As I am reading text file from websphere MQ, the content of the text file can be obtained thru xmlpayload.getText() or is there any other way.
    obj = inputModuleData.getPrincipalData();
    msg = (Message)obj;
    XMLPayload xmlpayload = msg.getDocument();
    String messageStr = xmlpayload.getText();
    At present I am using my adapter module before call sap adapter, but before sap adapter there are two other modules(toBinary and to Xmb), so shld I place it before both or after both the modules.
    Thanx in advance
    Rachit

  • Regarding Module Configuration of  Receiver JMS Adapter

    Hi,
    Now i am working on IDoc to JMS interface, I am facing complexity in creating the structure in Module tab of Receiver JMS Adapter. Because the target system is expecting fixed length file so i should use the Local EJBs available in Module tab of Receiver JMS adapter and i need to pass the fieldFixedLegth parameters for all the nodes coming from DELVRY01 Idoc. I think creating structure for all the nodes in receiver jms adapter is so complex, If you are having any other alternatives, please share with me.
    The below is the IDoc xml which is coming from source side.
    <?xml version="1.0" encoding="UTF-8" ?>
    <DELVRY01>
    <IDOC BEGIN="1">
    <EDI_DC40 SEGMENT="1">
    <TABNAM>EDI_DC40</TABNAM>
    <MANDT>100</MANDT>
    <DOCNUM>000000000999999</DOCNUM>
    <DOCREL>1145</DOCREL>
    <STATUS>1</STATUS>
    <DIRECT>1</DIRECT>
    <OUTMOD>2</OUTMOD>
    <IDOCTYP>DELVRY01</IDOCTYP>
    <MESTYP>abcde</MESTYP>
    <SNDPOR>efghi</SNDPOR>
    <SNDPRT>LS</SNDPRT>
    <SNDPRN>LMNOP100</SNDPRN>
    <RCVPOR>A000000023</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPRN>TB</RCVPRN>
    <CREDAT>20056556</CREDAT>
    <CRETIM>183734</CRETIM>
    <SERIAL>12345678</SERIAL>
    </EDI_DC40>
    <E1EDL20 SEGMENT="1">
    <VBELN>006456451</VBELN>
    <VSTEL>4656</VSTEL>
    <VKORG>1665</VKORG>
    <ABLAD>ABCDEDFJSDFDF</ABLAD>
    <ROUTE>DFSDF</ROUTE>
    <VSBED>08</VSBED>
    <BTGEW>3.000</BTGEW>
    <NTGEW>333.000</NTGEW>
    <GEWEI>NNN</GEWEI>
    <VOLUM>450.190</VOLUM>
    <VOLEH>DMBG55TERTQ</VOLEH>
    <ANZPK>00000</ANZPK>
    <XABLN>0001995346331</XABLN>
    <LIFEX>N</LIFEX>
    <E1EDL22 SEGMENT="1">
    <VSTEL_BEZ>ABCDEFGHIIJFLD</VSTEL_BEZ>
    <VKORG_BEZ>SDFKJSDFSDF</VKORG_BEZ>
    <ROUTE_BEZ>FSDNFKSDJFKJASDKFJSDJFL</ROUTE_BEZ>
    <VSBED_BEZ>FNSDKFSD,F,MSDF,</VSBED_BEZ>
    </E1EDL22>
    <E1EDL21 SEGMENT="1">
    <KDGRP>10545</KDGRP>
    <BEROT>teGHGHst FGHHFGHXI </BEROT>
    <TRAGR>0001</TRAGR>
    <E1EDL23 SEGMENT="1">
    <LFART_BEZ>Outbound delivery</LFART_BEZ>
    <KDGRP_BEZ>LPHG Wholesale</KDGRP_BEZ>
    <TRAGR_BEZ>On HHFH</TRAGR_BEZ>
    </E1EDL23>
    </E1EDL21>
    <E1EDL18 SEGMENT="1">
    <QUALF>ORI</QUALF>
    </E1EDL18>
    <E1ADRM1 SEGMENT="1">
    <PARTNER_Q>AG</PARTNER_Q>
    <PARTNER_ID>00000GHF12889</PARTNER_ID>
    <LANGUAGE>EN</LANGUAGE>
    <FORMOFADDR>Makro SA</FORMOFADDR>
    <TELEPHONE1>041 3600TERTE605-C...</TELEPHONE1>
    <TELEFAX>041 36006TRT47</TELEFAX>
    <COUNTRY1>ZHFGHA</COUNTRY1>
    <REGION>EHGHC</REGION>
    <E1ADRE1 SEGMENT="1">
    <EXTEND_Q>100</EXTEND_Q>
    <EXTEND_D>6HG15FGHFG05006416</EXTEND_D>
    </E1ADRE1>
    </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
    <PARTNER_Q>WE</PARTNER_Q>
    <PARTNER_ID>00000178E87T</PARTNER_ID>
    <LANGUAGE>EN</LANGUAGE>
    <FORMOFADDR>Makro SA</FORMOFADDR>
    <NAME1>Makro Port Elizabeth Br 14</NAME1>
    <NAME3>t/a Makro SA</NAME3>
    <STREET1>CDFJSDLFJLS d</STREET1>
    <COUNTRY1>ZFSDFA</COUNTRY1>
    <REGION>EFSDFC</REGION>
    <E1ADRE1 SEGMENT="1">
    <EXTEND_Q>100</EXTEND_Q>
    <EXTEND_D>6001534453505006416</EXTEND_D>
    </E1ADRE1>
    </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
    <PARTNER_Q>54OSP</PARTNER_Q>
    <PARTNER_ID>404534501</PARTNER_ID>
    <LANGUAGE>EN</LANGUAGE>
    <COUNTRY1>Z5454A</COUNTRY1>
    </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
    <PARTNER_Q>OSO</PARTNER_Q>
    <PARTNER_ID>1054400</PARTNER_ID>
    <COUNTRY1>Z5453A</COUNTRY1>
    </E1ADRM1>
    <E1EDT13 SEGMENT="1">
    <QUALF>006</QUALF>
    <NTANF>2005455470706</NTANF>
    <NTANZ>000000</NTANZ>
    <NTEND>2005453470706</NTEND>
    <NTENZ>00053454000</NTENZ>
    <ISDD>00000000</ISDD>
    <ISDZ>000000</ISDZ>
    <IEDD>00005340000</IEDD>
    <IEDZ>000000</IEDZ>
    </E1EDT13>
    <E1EDT13 SEGMENT="1">
    <QUALF>003</QUALF>
    <NTANF>20070706</NTANF>
    <NTANZ>000000</NTANZ>
    <NTEND>200705345706</NTEND>
    <NTENZ>000000</NTENZ>
    <ISDD>00000000</ISDD>
    <ISDZ>000053455400</ISDZ>
    <IEDD>00000000</IEDD>
    <IEDZ>000000</IEDZ>
    </E1EDT13>
    <E1EDT13 SEGMENT="1">
    <QUALF>001</QUALF>
    <NTANF>20070706</NTANF>
    <NTANZ>000000</NTANZ>
    <NTEND>20070706</NTEND>
    <NTENZ>000000</NTENZ>
    <ISDD>00000000</ISDD>
    <ISDZ>000000</ISDZ>
    <IEDD>00000000</IEDD>
    <IEDZ>000000</IEDZ>
    </E1EDT13>
    <E1EDT13 SEGMENT="1">
    <QUALF>007</QUALF>
    <NTANF>20070709</NTANF>
    <NTANZ>000000</NTANZ>
    <NTEND>20070709</NTEND>
    <NTENZ>000000</NTENZ>
    <ISDD>00000000</ISDD>
    <ISDZ>000000</ISDZ>
    <IEDD>00000000</IEDD>
    <IEDZ>000000</IEDZ>
    </E1EDT13>
    <E1EDT13 SEGMENT="1">
    <QUALF>010</QUALF>
    <NTANF>20070705</NTANF>
    <NTANZ>000000</NTANZ>
    <NTEND>20705</NTEND>
    <NTENZ>000000</NTENZ>
    <ISDD>00000000</ISDD>
    <ISDZ>000000</ISDZ>
    <IEDD>00000000</IEDD>
    <IEDZ>000000</IEDZ>
    </E1EDT13>
    <E1EDL28 SEGMENT="1">
    <ROUTE>ED545S1</ROUTE>
    <DISTZ>0.000</DISTZ>
    <E1EDL29 SEGMENT="1">
    <ROUTE_BEZ>FKLSDJFLSJDFJSDFJLSDJFLKSD</ROUTE_BEZ>
    </E1EDL29>
    </E1EDL28>
    <E1EDL24 SEGMENT="1">
    <POSNR>000010</POSNR>
    <MATNR>000000000000</MATNR>
    <MATWA>000000000</MATWA>
    <ARKTX>OmFDFS 2kg.</ARKTX>
    <MATKL>FSD5345FSDFLAUND</MATKL>
    <WERKS>10FDF40</WERKS>
    <LGORT>01</LGORT>
    <LFIMG>10545.000</LFIMG>
    <VRKME>C54T</VRKME>
    <LGMNG>10553545.000</LGMNG>
    <MEINS>CT534555345545345</MEINS>
    <NTGEW>1653454.000</NTGEW>
    <BRGEW>181.000</BRGEW>
    <GEWEI>KGM</GEWEI>
    <VOLUM>450.190</VOLUM>
    <VOLEH>DMQ</VOLEH>
    <LADGR>0534543002</LADGR>
    <TRAGR>0001</TRAGR>
    <VKBUR>UF53401</VKBUR>
    <VKGRP>160</VKGRP>
    <VTWEG>00</VTWEG>
    <SPART>00</SPART>
    <GRKOR>000</GRKOR>
    <EAN11>16001085031034</EAN11>
    <POSEX>000000</POSEX>
    <E1EDL25 SEGMENT="1">
    <LGORT_BEZ>Main s53453453454tore</LGORT_BEZ>
    <LADGR_BEZ>Forklift</LADGR_BEZ>
    <TRAGR_BEZ>On pallets</TRAGR_BEZ>
    <VKBUR_BEZ>Gener534534al Trade</VKBUR_BEZ>
    <VKGRP_BEZ>RSM E534 Cape</VKGRP_BEZ>
    <VTWEG_BEZ>FKLSDFKLS</VTWEG_BEZ>
    <SPART_BEZ>FSDFSDFJoducts</SPART_BEZ>
    </E1EDL25>
    <E1EDL26 SEGMENT="1">
    <PSTYV>TAN</PSTYV>
    <MATKL>FGUND</MATKL>
    <PRODH>0125VH</PRODH>
    <UMVKZ>1</UMVKZ>
    <UMVKN>1</UMVKN>
    <KZTLF>B</KZTLF>
    <UEBTO>0.0</UEBTO>
    <UNTTO>0.0</UNTTO>
    <KVGR1>Z4FDFSDFSD</KVGR1>
    <KVGR2>TPS</KVGR2>
    <E1EDL27 SEGMENT="1">
    <PSTYV_BEZ>Standard Item</PSTYV_BEZ>
    <PRODH_BEZ>OmoFFD Regular 8X2kg.</PRODH_BEZ>
    <WERKS_BEZ>ConFSDFgella DC</WERKS_BEZ>
    <KVGR1_BEZ>PE Cust Del</KVGR1_BEZ>
    <KVGR2_BEZ>rd party sales</KVGR2_BEZ>
    </E1EDL27>
    </E1EDL26>
    <E1EDL43 SEGMENT="1">
    <QUALF>C</QUALF>
    <BELNR>FDF</BELNR>
    <POSNR>000010</POSNR>
    <DATUM>FFSDF</DATUM>
    </E1EDL43>
    <E1EDL41 SEGMENT="1">
    <QUALI>54</QUALI>
    <BSTNR>test I Link</BSTNR>
    <BSTDT>00000000</BSTDT>
    <POSEX>000010</POSEX>
    </E1EDL41>
    </E1EDL24>
    </E1EDL20>
    </IDOC>
    </DELVRY01>

    duplicate blog

  • Regarding Module Configuration of JMS Adapter

    Hi,
         Now i am working on IDoc to JMS interface, I am facing complexity in creating the structure in Module tab of Receiver JMS Adapter. Because the target system is expecting fixed length file so i should  use the Local EJBs available in Module tab of Receiver JMS adapter and i need to pass the fieldFixedLegth parameters for all the nodes coming from DELVRY01 Idoc.  I think creating structure for all the nodes in receiver jms adapter is so complex, If you are having any other alternatives, please share with me.
    The below is the IDoc xml which is coming from source side.
       <?xml version="1.0" encoding="UTF-8" ?>
    <DELVRY01>
    <IDOC BEGIN="1">
    <EDI_DC40 SEGMENT="1">
    <TABNAM>EDI_DC40</TABNAM>
      <MANDT>100</MANDT>
      <DOCNUM>000000000999999</DOCNUM>
      <DOCREL>1145</DOCREL>
      <STATUS>1</STATUS>
      <DIRECT>1</DIRECT>
      <OUTMOD>2</OUTMOD>
      <IDOCTYP>DELVRY01</IDOCTYP>
      <MESTYP>abcde</MESTYP>
      <SNDPOR>efghi</SNDPOR>
      <SNDPRT>LS</SNDPRT>
      <SNDPRN>LMNOP100</SNDPRN>
      <RCVPOR>A000000023</RCVPOR>
      <RCVPRT>LS</RCVPRT>
      <RCVPRN>TB</RCVPRN>
      <CREDAT>20056556</CREDAT>
      <CRETIM>183734</CRETIM>
      <SERIAL>12345678</SERIAL>
      </EDI_DC40>
    <E1EDL20 SEGMENT="1">
      <VBELN>006456451</VBELN>
      <VSTEL>4656</VSTEL>
      <VKORG>1665</VKORG>
      <ABLAD>ABCDEDFJSDFDF</ABLAD>
      <ROUTE>DFSDF</ROUTE>
      <VSBED>08</VSBED>
      <BTGEW>3.000</BTGEW>
      <NTGEW>333.000</NTGEW>
      <GEWEI>NNN</GEWEI>
      <VOLUM>450.190</VOLUM>
      <VOLEH>DMBG55TERTQ</VOLEH>
      <ANZPK>00000</ANZPK>
      <XABLN>0001995346331</XABLN>
      <LIFEX>N</LIFEX>
    <E1EDL22 SEGMENT="1">
      <VSTEL_BEZ>ABCDEFGHIIJFLD</VSTEL_BEZ>
      <VKORG_BEZ>SDFKJSDFSDF</VKORG_BEZ>
      <ROUTE_BEZ>FSDNFKSDJFKJASDKFJSDJFL</ROUTE_BEZ>
      <VSBED_BEZ>FNSDKFSD,F,MSDF,</VSBED_BEZ>
      </E1EDL22>
    <E1EDL21 SEGMENT="1">
      <KDGRP>10545</KDGRP>
      <BEROT>teGHGHst FGHHFGHXI </BEROT>
      <TRAGR>0001</TRAGR>
    <E1EDL23 SEGMENT="1">
      <LFART_BEZ>Outbound delivery</LFART_BEZ>
      <KDGRP_BEZ>LPHG Wholesale</KDGRP_BEZ>
      <TRAGR_BEZ>On HHFH</TRAGR_BEZ>
      </E1EDL23>
      </E1EDL21>
    <E1EDL18 SEGMENT="1">
      <QUALF>ORI</QUALF>
      </E1EDL18>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>AG</PARTNER_Q>
      <PARTNER_ID>00000GHF12889</PARTNER_ID>
      <LANGUAGE>EN</LANGUAGE>
      <FORMOFADDR>Makro SA</FORMOFADDR>
      <TELEPHONE1>041 3600TERTE605-C...</TELEPHONE1>
      <TELEFAX>041 36006TRT47</TELEFAX>
      <COUNTRY1>ZHFGHA</COUNTRY1>
      <REGION>EHGHC</REGION>
    <E1ADRE1 SEGMENT="1">
      <EXTEND_Q>100</EXTEND_Q>
      <EXTEND_D>6HG15FGHFG05006416</EXTEND_D>
      </E1ADRE1>
      </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>WE</PARTNER_Q>
      <PARTNER_ID>00000178E87T</PARTNER_ID>
      <LANGUAGE>EN</LANGUAGE>
      <FORMOFADDR>Makro SA</FORMOFADDR>
      <NAME1>Makro Port Elizabeth Br 14</NAME1>
      <NAME3>t/a Makro SA</NAME3>
      <STREET1>CDFJSDLFJLS d</STREET1>
      <COUNTRY1>ZFSDFA</COUNTRY1>
      <REGION>EFSDFC</REGION>
    <E1ADRE1 SEGMENT="1">
      <EXTEND_Q>100</EXTEND_Q>
      <EXTEND_D>6001534453505006416</EXTEND_D>
      </E1ADRE1>
      </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>54OSP</PARTNER_Q>
      <PARTNER_ID>404534501</PARTNER_ID>
      <LANGUAGE>EN</LANGUAGE>
      <COUNTRY1>Z5454A</COUNTRY1>
      </E1ADRM1>
    <E1ADRM1 SEGMENT="1">
      <PARTNER_Q>OSO</PARTNER_Q>
      <PARTNER_ID>1054400</PARTNER_ID>
      <COUNTRY1>Z5453A</COUNTRY1>
      </E1ADRM1>
    <E1EDT13 SEGMENT="1">
      <QUALF>006</QUALF>
      <NTANF>2005455470706</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>2005453470706</NTEND>
      <NTENZ>00053454000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00005340000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>003</QUALF>
      <NTANF>20070706</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>200705345706</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000053455400</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>001</QUALF>
      <NTANF>20070706</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>20070706</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>007</QUALF>
      <NTANF>20070709</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>20070709</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDT13 SEGMENT="1">
      <QUALF>010</QUALF>
      <NTANF>20070705</NTANF>
      <NTANZ>000000</NTANZ>
      <NTEND>20705</NTEND>
      <NTENZ>000000</NTENZ>
      <ISDD>00000000</ISDD>
      <ISDZ>000000</ISDZ>
      <IEDD>00000000</IEDD>
      <IEDZ>000000</IEDZ>
      </E1EDT13>
    <E1EDL28 SEGMENT="1">
      <ROUTE>ED545S1</ROUTE>
      <DISTZ>0.000</DISTZ>
    <E1EDL29 SEGMENT="1">
      <ROUTE_BEZ>FKLSDJFLSJDFJSDFJLSDJFLKSD</ROUTE_BEZ>
      </E1EDL29>
      </E1EDL28>
    <E1EDL24 SEGMENT="1">
      <POSNR>000010</POSNR>
      <MATNR>000000000000</MATNR>
      <MATWA>000000000</MATWA>
      <ARKTX>OmFDFS 2kg.</ARKTX>
      <MATKL>FSD5345FSDFLAUND</MATKL>
      <WERKS>10FDF40</WERKS>
      <LGORT>01</LGORT>
      <LFIMG>10545.000</LFIMG>
      <VRKME>C54T</VRKME>
      <LGMNG>10553545.000</LGMNG>
      <MEINS>CT534555345545345</MEINS>
      <NTGEW>1653454.000</NTGEW>
      <BRGEW>181.000</BRGEW>
      <GEWEI>KGM</GEWEI>
      <VOLUM>450.190</VOLUM>
      <VOLEH>DMQ</VOLEH>
      <LADGR>0534543002</LADGR>
      <TRAGR>0001</TRAGR>
      <VKBUR>UF53401</VKBUR>
      <VKGRP>160</VKGRP>
      <VTWEG>00</VTWEG>
      <SPART>00</SPART>
      <GRKOR>000</GRKOR>
      <EAN11>16001085031034</EAN11>
      <POSEX>000000</POSEX>
    <E1EDL25 SEGMENT="1">
      <LGORT_BEZ>Main s53453453454tore</LGORT_BEZ>
      <LADGR_BEZ>Forklift</LADGR_BEZ>
      <TRAGR_BEZ>On pallets</TRAGR_BEZ>
      <VKBUR_BEZ>Gener534534al Trade</VKBUR_BEZ>
      <VKGRP_BEZ>RSM E534 Cape</VKGRP_BEZ>
      <VTWEG_BEZ>FKLSDFKLS</VTWEG_BEZ>
      <SPART_BEZ>FSDFSDFJoducts</SPART_BEZ>
      </E1EDL25>
    <E1EDL26 SEGMENT="1">
      <PSTYV>TAN</PSTYV>
      <MATKL>FGUND</MATKL>
      <PRODH>0125VH</PRODH>
      <UMVKZ>1</UMVKZ>
      <UMVKN>1</UMVKN>
      <KZTLF>B</KZTLF>
      <UEBTO>0.0</UEBTO>
      <UNTTO>0.0</UNTTO>
      <KVGR1>Z4FDFSDFSD</KVGR1>
      <KVGR2>TPS</KVGR2>
    <E1EDL27 SEGMENT="1">
      <PSTYV_BEZ>Standard Item</PSTYV_BEZ>
      <PRODH_BEZ>OmoFFD Regular 8X2kg.</PRODH_BEZ>
      <WERKS_BEZ>ConFSDFgella DC</WERKS_BEZ>
      <KVGR1_BEZ>PE Cust Del</KVGR1_BEZ>
      <KVGR2_BEZ>rd party sales</KVGR2_BEZ>
      </E1EDL27>
      </E1EDL26>
    <E1EDL43 SEGMENT="1">
      <QUALF>C</QUALF>
      <BELNR>FDF</BELNR>
      <POSNR>000010</POSNR>
      <DATUM>FFSDF</DATUM>
      </E1EDL43>
    <E1EDL41 SEGMENT="1">
      <QUALI>54</QUALI>
      <BSTNR>test I Link</BSTNR>
      <BSTDT>00000000</BSTDT>
      <POSEX>000010</POSEX>
      </E1EDL41>
      </E1EDL24>
      </E1EDL20>
      </IDOC>
      </DELVRY01>

    not related

  • Error publishing large payload in AQ JMS Adapter

    Hi,
    We are usign AQ JMS Adapter and we are publishing payload in AQ JMS Topic thorugh BPEL process.
    Issue is, i'm not able to publish large payload ( xml file of size 4KB) to AQ JMS Topic through asynchronous BPEL process.
    When i post the xml in the BPEL Control, i'm getting the follwoing message:
    "Cannot find the specified instance". I have tried 3-4 times but getting same message all the time
    However, i'm able to publish xml to JMS Topic with synchronous BPEL process.
    Please let me know if there is a way to overcome this issue.
    Thanks in advance

    If the StreamPayload property does not exist, then the default value false is assumed.
    <activation-spec className="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec">
    <property name="QueueName" value="RAW_IN_QUEUE"/>
    <property name="DatabaseSchema" value="SCOTT"/>
    <property name="StreamPayload" value="true"/>
    </activation-spec>
    you can add <property name="StreamPayload" value="true"/>
    to the .jca file but rememeber This property is applicable when processing Raw messages, XMLType messages, and ADT type messages for which a payload is specified though an ADT attribute.

  • Jms adapter not polling messages from jms topic

    Hi
    We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
    <adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
      <connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
      <endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
        <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
          <!--property name="DurableSubscriber" value="XYZ"/-->
          <property name="PayloadType" value="TextMessage"/>
          <!--property name="MessageSelector" value="Target in ('XYZ')"/-->
          <property name="UseMessageListener" value="true"/>
          <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
        </activation-spec>
      </endpoint-activation>
    </adapter-config>
    If we remove Durable subscriber and message selector properties,its able to poll messages.
    Any pointer will help
    thanks in advance
    Baji

    After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
    <property name="UseMessageListener" value="false"/>
    But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
    <property name="DurableSubscriber" value="XYZ"/>
    If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
    Thanks
    Baji

Maybe you are looking for

  • TS4526 Unknown error when trying to play video from netflix or HBO go.

    When I try to play a video from Netflix or HBO go it attempts to load and says unknown error please try again later.  I've been trying this for several days.  I logged out then logged back in with no change.  It seems to play the other apps okay.  I'

  • Reinstalled Pagemaker 7 won't open documents

    In a previous thread I asked about PM7 on Win7 and the recommendation was to not use Win7.  Acting on that suggestion, I switched to an XP Pro machine, reinstalled PM7, and lo and behold, it refuses to open any of the previous documents.  I get the "

  • Scrolling log window guff

    Hi, I've got an app that executes external processes, monitors the output of each, and puts it in a log window. The problem is, when I append to the contents of the JTextArea, I don't know how to set its preferred size correctly so that the JScrollPa

  • L_TA_HINZUFUEGEN with L3 551

    Hi Gurus, During my testing, while I was trying to create a TO document to pick the quantities from delivery I am getting the following error "Update was terminated", this error was comming in the form of SAP Express document (Workflow document) on t

  • Contact Apple in Malaysia via email

    Can anyone let me know how I could contact Apple in Malaysia via email? I have an Iphone4s which reciver speaker stopped working. The phone is only 6 months old and and was bought online from Apple in Malaysia. I live in Sri Lanka and although there