Announcement

Collapse
No announcement yet.

Transmission Manager - sequence of processing

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

  • Transmission Manager - sequence of processing

    We have noticed that the transmission manager processes data in no particular sequence. We would like to have it process as fist in first out. There is any why of setting the system to do this.

    Any assistance would be appreciated.

    Thanks
    Chris

  • #2
    Re: Transmission Manager - sequence of processing

    Could you explain with an example? What is the contents of your transmission? Why is FIFO required?

    Comment


    • #3
      Re: Transmission Manager - sequence of processing

      This is a question that our company has also. We send new Location and OrderRelease messages as separate transmissions and the OrderRelease references the Location. Even though the OrderRelease message is sent second, it is processed before the location is added, which results in an error.

      Before we modify our code to send these in the same transmission that keeps them in sequence, we were wondering if there was a way to have OTM process them in order. (Is this multi-threaded, where we can configure only one thread?)

      Thank you,
      Lisa

      Comment


      • #4
        Re: Transmission Manager - sequence of processing

        The most common option to send an order interface with a new location, is to embed the location in the ReleaseXML. Second option is to create two transactions in the same transmission. Note that choosing your option is very much depending on your individual situation and your order management system, so I'd need some more information about that before giving you the best advice.

        I don't know the technical details about how OTM processes transmissions/threads; perhaps someone else can comment on this, or you can try asking Oracle Support.

        Lourens

        Comment


        • #5
          Re: Transmission Manager - sequence of processing

          How many transmissions you are receiving a day? Using single thread may impact performance badly.
          But, if you are willing to use single thread, you may use glog.webserver.event.EventDiagServlet to shrink thread of publishWait queue, by clicking "Kill" button.

          Please note that this approach is only changing number of thread dynamically.
          Once you have tested and would like to change thread number permanently, you can modify glog.properties on OTM App server.
          Code:
          [COLOR=darkgreen]#--------------------------------------------------------------------[/COLOR]
          [COLOR=darkgreen]# Custom Thread Properties - Beginning[/COLOR]
          [COLOR=darkgreen]#--------------------------------------------------------------------[/COLOR]
          [COLOR=darkgreen]# Place all thread changes and properties here.[/COLOR]
          [COLOR=darkgreen]# This section will be used during GC3 Upgrades[/COLOR]
          [COLOR=darkgreen]#--------------------------------------------------------------------[/COLOR]
           
          [B]!remove [FONT=Courier New]glog.workflow.topicGroup=publishWait,4[/FONT][/B]
          [FONT=Courier New][FONT=Courier New][B]glog.workflow.topicGroup=publishWait,1[/B][/FONT][/FONT]
           
          [COLOR=darkgreen]#--------------------------------------------------------------------[/COLOR]
          [COLOR=darkgreen]# Custom Thread Properties - End[/COLOR]
          [COLOR=darkgreen]#--------------------------------------------------------------------[/COLOR]
          Last edited by josephliang; September 4, 2009, 13:21.
          --
          Joseph Liang
          MavenWire APAC
          http://www.mavenwire.com/

          Comment

          Working...
          X