1 Reply Latest reply on Oct 11, 2011 2:44 PM by 882069

    OEG Design for dynamic routing


      In the current OEG project, we're thinking of best usability of OEG design/development based on the following scenario:

      The architecture(sychonized transaction):
      request flow: CLIENT ---> OEG --> OSB
      respnse flow: OSB --> OEG --> CLIENT

      We have 10 OSB services define on OSB side(let's call them OSB Services), which includes:


      At OEG side, we are thinking of 10 OEG service defined as the entry points to 10 OSB services(1:1 mapping between OEG services and OSB services), OEG services exposed to client, including:

      https://OEG_host:OEG_port/getDocument (will be route to https://OSB_host:OSB_port/getDocument)
      https://OEG_host:OEG_port/getDocumentList(will be route to https://OSB_host:OSB_port/getDocumentList)

      But for the policies of processing each OEG service - actually they are much similiar, all following procedure:
      1) Message decryption
      2) Write log
      3) Routing to OSB Service
      4) Write log

      So we were thinking of just develop one common policy(maybe a global policy?) for 10 OEG services, may I have the idea about HOW could I do dynamic routing to different OSB services in a common policy ?

        • 1. Re: OEG Design for dynamic routing
          Your approach sounds right, certainly having a 1:1 mapping between virtualised service in the OEG and the OSB makes things simple.

          Place the decryption and logging the global request policy
          Have the WS-Filter run as normal to do XSD and routing
          Place the logging of response in a global respone policy
          1 person found this helpful