Creating Subscriber Code Using the Content Management Event Framework

Using the Content Management Event Framework 16-11

16.3.4 Examining CMEF Events

Use the CMEF Events page Figure 16–5 to examine the subscribers that have been added to the WWSBR_EVENTS_Q queue. To access the CMEF Events page, perform the following steps:

1. Login to your portal as the portal schema owner.

2. Enter the following URL in the browser Address field:

http:host:portportalplsdadschema.wwsbr_event_dbg.show ■ host is the machine on which your portal middle tier is installed. ■ port is the port used by your portal ■ dad is the Database Access Descriptor DAD for your Oracle Portal installation. ■ schema is the schema in which Oracle Portal is installed. Figure 16–5 CMEF Events Page

16.3.5 Running a CMEF Subscriber

To run a subscriber, issue the command shown in Example 16–7 at a SQL prompt. Example 16–7 Running a Subscriber begin subscriber procedure; end; Note: The CMEF Events page is not supported by Oracle, but it is included within Oracle Portal for debugging purposes. It is only accessible by the portal schema owner. 16-12 Oracle Fusion Middleware Developers Guide for Oracle Portal

16.3.6 CMEF Message Payload

Every Oracle Portal user interface or PLSQL content management action falls under one of the three main CMEF events: INSERT, UPDATE, DELETE. States provide more meaning to events. For example, the following types of ADDINSERT ITEM events: ■ Add an item and publish it immediately. ■ Add an item and publish it at a later date. ■ Add an item that requires approval, because the user has Manage Items With Approval privileges. For a detailed list of the actions and related events and states, refer to Appendix G, Content Management Event Framework Events . Each CMEF event has an associated CMEF message payload as shown in Table 16–2 . Table 16–2 CMEF Message Payload Properties Message Property Type Description ACTION VARCHAR230 The portal action that triggered the event. RAW_EVENT VARCHAR230 The event produced as a result of the portal action. STATE VARCHAR230 Provides additional information related to the event. OBJECT_ID NUMBER The ID of the object to which the event relates for example, item, page, category, and so on. OBJECT_SITE_ID NUMBER The ID of the page group to which the object belongs. OBJECT_LANGUAGE VARCHAR230 The session language. NULL if the action is independent of language. PAGE_ID NUMBER For items, the ID of the page on which the item appears. NULL for other objects. PAGE_SITE_ID NUMBER For items, the ID of the page group to which the page identified in PAGE_ID belongs. NULL for non-item related events. OBJECT_CLASS VARCHAR230 Records the class of object about which an event has been raised. EVENTS_USER VARCHAR2256 The name of the user who performed the portal action. EVENTS_DATE VARCHAR260 The date on which the event occurred. Format: dd-mon-yyyy HH12:MI PM ID1 OVERLOADED NUMBER For items, the item type ID. For pages, the page type ID. For item and page types, the base type ID.