Announcement

Collapse
No announcement yet.

inbound transmision into OTM using BPEL

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • inbound transmision into OTM using BPEL

    Hi all,

    can anyone guide me the steps to get an inbound transmission (say tranbsorder) into OTM using BPEL.
    Suppose we have a csv file with the order fields or say deliverieds field. Then we map it into OTM tables using BPEL.what next? Do we need to invoke a servlet using BPEL (the transformer or any other servlet)?

    Can anyone give the steps for getting one inbound transmission into OTM using BPEL?

    any help is highly appreciated

    Regards

  • #2
    Re: inbound transmision into OTM using BPEL

    In order to input integration into OTM from any system, you'll need to transform the data into G-Log XML, rather than mapping to tables as you would with EBS. From that point, you post it to the OTM integration servlet (http://otm.mavenwire.com/GC3/glog.integration.servlet.WMServlet) and get your ACK, including the OTM transmission number.

    At that point, OTM will take over, store the XML and then process it as in incoming integration.

    --Chris

    Comment


    • #3
      Re: inbound transmision into OTM using BPEL

      Thanks Chris for the quick input....but what we are trying here is we got a csv file which we need to get into OTM using BPEL.......For that we are trying to do the follwoing steps..please kindly help us if the steps are correct and what more needs to be added:-

      1. Get the mandatory fields in the CSV (delivery and delievry lines) like locations, itmes, customer into OTM first using BPEL
      2.Then use the delivery and delivery lines field for mapping into OTM.This will be done by mapping the fields of the CSV with OTM table
      3.Next invoke the transformer servlet using BPEL and deploye the BPEL process into OTM.

      Chris can you kindly elaobrate on the mentione dsteps as to what else or anything else we need to do.

      The whole idea is to demonstrate that we can bring any inbound transmission into OTM using BPEL..not using CSV upload from UI, or httppost.

      Please kindly help in this .

      rgds
      Mithun Banerjee

      Comment


      • #4
        Re: inbound transmision into OTM using BPEL

        Mithun,

        The steps I listed are to post integration to OTM (which must be in XML format) -- not to upload the CSV directly to OTM. So, you must handle the transformation of the initial CSV file into G-Log's XML format within BPEL, do all of your data validation, etc. OTM will not transform the data for you -- this is how it differs from EBS.

        Then post the resultant XML file to OTM using WMServlet. Again, this servlet is meant primarily to handle incoming integration posts from an integration server (BPEL or otherwise).

        --Chris

        Comment


        • #5
          Re: inbound transmision into OTM using BPEL

          thanks a lot chris for your guidance in this matter........

          Comment


          • #6
            Re: inbound transmision into OTM using BPEL

            Hi Chris,

            I am also working on the similary task where i need to send bulk data into OTM using the servlet glog.integration.servlet.DirLoadServlet.

            But I am not sure of how to invoke a servlet from a BPEL Process (servlets like WMServlet or DirLoadServlet.

            Kindly provide me information.

            Ashok G
            Regards

            Ashok

            Comment


            • #7
              Re: inbound transmision into OTM using BPEL

              Chris, carrying on from Ashok's discussion... can you kindly help with our query which we are having while following the steps mentioned by you.We have been able to invoke the servlet but we did not set any property in glog.properties file for this.Is this necessary and if yes can you kindly let me know what do we need to set in the glog .properties for invoking the servlet.
              Also since here we are writing our own BPEL process(not using the standard one) so how do we get the transmission acknowledgement from OTM.what needs to be done to achive this.

              Comment


              • #8
                Re: inbound transmision into OTM using BPEL

                Hello,

                First - unless you're using the stock EBS/OTM integration, you shouldn't have to set anything in the glog.properties file. Could you provide more details on this - as I'm not sure what property you were expecting to set.

                The easiest way to understand how to process integration into OTM from EBS may be to analyze the default EBS/OTM integration flows and simply use them as a reference. Basically, once you invoke the http post in order to post your integration to the servlet (any of the OTM integration servlets - though WMServlet is the most common) - then OTM should respond back with the transmission number - which will act as your transmission acknowledgement.

                This is a simple HTTP Post operation from within BPEL and shouldn't require any special configuration just for OTM.

                I hope this helps!

                --Chris

                Comment


                • #9
                  Re: inbound transmision into OTM using BPEL

                  hi Chris,

                  Thanks for the prompt reply.....the error it is showing while invoking the servlet is given below:-
                  "bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
                  -<part name="summary">
                  <summary>
                  com.collaxa.cube.ws.wsif.providers.http.WSIFOperat [email protected] : Could not invoke 'PostMessage'; nested exception is: oracle.xml.parser.v2.XMLParseException: Start of root element expected.</summary>
                  </part>
                  -<part name="detail">
                  <detail>
                  oracle.xml.parser.v2.XMLParseException: Start of root element expected.</detail>
                  </part>
                  </bindingFault"

                  The roort element mentioned in the xml is "Transmission".
                  Please can you help us with this.

                  Comment


                  • #10
                    Re: inbound transmision into OTM using BPEL

                    Hello - can you ensure that you've uncommented the following line in the OTM glog.properties files ($OTM_HOME/glog/config/glog.properties) on each OTM server and have restarted the OTM instance?
                    Code:
                    !include ebs.properties
                    --Chris

                    Comment


                    • #11
                      Re: inbound transmision into OTM using BPEL

                      Thanks chris for your prompt reply........we will get back in case of any further issues.

                      Comment


                      • #12
                        Re: inbound transmision into OTM using BPEL

                        chris as suggested we have uncommented the line in the OTM glog.properties files ...now using or custome BPEL process we are able to get the inbound transmission for PO into OTM but with an error in transmission.The tarnsmission report throws the follwoing error:-
                        "CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION: java.lang.IllegalStateException: Failed to parse the specified XML java.lang.IllegalStateException: Failed to parse the specified XML at glog.integration"

                        Can you please help us as to why this error is showing and what needs to be done to rectify this one.

                        Comment


                        • #13
                          Re: inbound transmision into OTM using BPEL

                          I'm not sure why this is occurring, unless the XML is somehow invalid or not being translated correctly by BPEL. Have you opened an SR with Oracle yet? If so, please update us on the progress, so we can all learn from the issue.

                          Thanks,
                          Chris

                          Comment


                          • #14
                            Re: inbound transmision into OTM using BPEL

                            I have the same XML Parse exception when using oracle BPEL to integrate with OTM. can you please let me know how you resolved your issue?

                            Comment

                            Working...
                            X