1 Reply Latest reply on May 3, 2006 12:11 PM by 159563

    How to use the BES in the Oracle Applications with Interconnect???

      Some Distribuited DBs with Customer Data to be integrated in a Single Customer Data Hub.
      The implementation is:
      Oracle Interconnect as HUB between DB1, DB2...DBn and Customer Data Hub. For the DBs we use the DB Adapter, on the CDH side we have the Oracle Application Adapter.

      The flow starting from any DB to CDH was implemented without problems (Publish in DBs, Subscribe in CDH, using iStudio). Now we have big problems to implement the other side (Publish in CDH, Subscribe in DBs). We understand that we have to use the BES in the CDH, "subscribing" to the events like "oracle.apps.ar.hz.Person.create", but HOW can we do this in iStudio? We tried to create a Publish Event in iStudio, using the Workflow BES message type, but when we do the "Export PL/SQL" procedure, we got a PL/SQL package without any procedure/function, so it seems that we missed something important. We dind't understand if we have to implement a specific workflow to link to Oracle Application BES, the documentation about the Oracle Application Adapter with BES is very short and without hints.

      We are currently blocked on this issue, so any hint about it?
      Thanks in advance.

        • 1. Re: How to use the BES in the Oracle Applications with Interconnect???
          iStudio dosn't generate a code for the BES subsriptuions, and I think it shouldn't:-)

          To implement publish from OEBS, first you are to choose the way, you'll be using for connecting with InterConnect: this may be a queue, or PL/SQL procedure in DB-adapter style.

          You see, publishing from OEBS have several phases:
          1) Catch the event you want (either Event in BES, or trigger, or smth else)
          2) Collect (select) the data you want to publish (write PL/SQL procedure for collecting all the data you want to publish and write a call to it either in Subscription for Event in BES or in trigger, etc.). Note that Event in BES itself dosn't collect any data! It got only several IDs of corresponding tables.
          3) Transfer (publish) collected data to OEBS adapter (either second Subscription for the Event in BES, wich will do Send to Agent (actually - put in queue) or PL/SQL publish in DB-adapter style (oai.agent.publish()... etc.))

          When publish from OEBS in iStudio you have 4 choises - but don't beleave - actially this is 2 choises: Table API, and Queue (3 others)
          Table API - is DB-adapter style
          Queue - is AQ-adapter style

          Decide which way you want to use and choose it.

          All the iStudio do - generate PL/SQL for Publish (pub_Upd_BlanketType_fr_OEBS_OA) in case you select Table API path. Just as DB adapter do when you publish from it.
          All the other - you are to do youself.

          Find Event in BES, write PL/SQL for collecting data, create Subscription for the Event calling this PL/SQL and finally create second Subscription for the Event calling ether PL/SQL generated by iStudio (Table API way) or putting the data to queue (choose Send to Agent in subscription instead of PL/SQL procedure name)

          To make Subscriptions in BES you are to login as SYSADMIN to OEBS.

          Good luck!