2 Replies Latest reply: Jul 28, 2009 5:39 PM by user753546 RSS

    How to config data tier separately of WLS domain

    jlaci1
      Helo,

      We plan our new OCCAS landscape, and have a config question: how can we configure engine tier servers to use explicit data tier servers, not all that configured in the domain?

      It seems that Oracle unfortunately mixed two concetps in OCCAS: Weblogic administration domain and SIP data tier configuration.

      Is it possible to separate the two thing?

      Regards.,
      LJ
        • 1. Re: How to config data tier separately of WLS domain
          graham - oracle
          Hi LJ, you may want to post over on the new My Oracle Support Communications Community which is moderated by and responded to by Oracle Support and accessible by Oracle customers. Many new features will be developed for the Community in the coming months, please come and check it out at https://metalink.oracle.com/CSP/ui/index.html

          Regards
          Graham

          Edited by: user603014 on Jun 30, 2009 11:07 AM
          • 2. Re: How to config data tier separately of WLS domain
            user753546
            Well the specific answer is that engines can't be configured to use specific datatier servers. Engines communicate with all the partitions in datatier in a domain.

            In a replicated domain we have

            1. Engine Tier (consists of engines and these act as sip servlet container(s) and handle the SIP traffic)
            2. Data Tier (consists of replicas and it is here that engines stored the call data once a sip message is handled. It acts as in memory cache for call state)

            Data Tier essentially consists of partitions and each partition has one or more replicas which contains redundant data for Fault Tolerance purposes.

            So engines communicate with each configured partition and call load is distributed across partitions. There is no way to have engines talk to a specific partition only.
            But for a specific call affinity is maintained. What i mean is that if initial Invite was received by engine and cal state got stored in partition1 of datatier, then engine always consults that partition for all subsequent calls (with same call-id and in dialog) and also for timers.

            Hope it helps.