This content has been marked as final. Show 1 reply
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.