Oracle Portal Actions and CMEF Events
16.3.7.2.2 Adding an Item That Requires Approval If approvals and notifications are
enabled for a page or page group, and a user with Manage Items With Approval privileges, adding an item to a page produces the following message payload: If you want your subscriber to respond to this action, perform the following check: if message.action = SUBMIT_ITEM_FOR_APPROVAL and message.object_class = ITEM and message.raw_event = INSERT and message.state = NOT_PUBLISHED then . . . end if;16.3.7.2.3 Approving an Item Approving an item triggers either an INSERT or UPDATE
event, which may also be followed by either a DELETE or UPDATE event depending upon whether or not versioning is enabled. Item approved; versioning disabled This is the simplest case. If the item still has approval steps to pass through, then an UPDATE event is triggered: If the item has completed all approval steps, then an INSERT event is triggered: Item approved; versioning enabled; current version overwritten If item versioning is set to Simple at the page or page group level, and a user selects Overwrite Current Version when editing an item, on approval of the item, two events are generated. The first event is for the item that is approved, and a second DELETE event for the item that is overwritten as a result of the item being approved: Action Event State Object Class SUBMIT_ITEM_FOR_ APPROVAL INSERT NOT_PUBLISHED ITEM Action Event State Object Class APPROVE_ITEM_ STEP UPDATE GENERAL ITEM Action Event State Object Class APPROVE_ITEM INSERT PUBLISHED ITEM Action Event State Object Class APPROVE_ITEM INSERT PUBLISHED ITEM APPROVE_ITEM DELETE PURGED ITEM Using the Content Management Event Framework 16-17 Item approved; versioning enabled; new and current version If item versioning is set to Audit at the page or page group level, or it is set to Simple and a user selects Add Item As New And Current Version, on approval of the item an INSERT event is generated. An UPDATE event is also generated that is related to marking the previous version of the item as UNPUBLISHED: If you are writing a subscriber that sends a notification when an item is approved or has passed through a stage of being approved, you should perform the following check: -- If an item is approved. if message.action = APPROVE_ITEM and message.object.class = ITEM and message.raw_event = INSERT and message.state = PUBLISHED then . . . -- If an item has passed an approval step. elsif message.action = APPROVE_ITEM_STEP and message.object_class = ITEM and message.raw_event = UPDATE and message.state = PUBLISHED then . . . end if; Item approved, versioning enabled; new but not current version An INSERT event occurs for the item that is added, but the state of the item is marked as NOT_PUBLISHED to indicate that it is not published as the current version:16.3.7.2.4 Applying a Category or Perspective to an Item Applying a different category or
perspective to an item produces the same message payload as editing an item: If you want your subscriber to respond to this action, perform the following check: if message.action = EDIT_ITEM and message.object_class = ITEM and message.raw_event = UPDATE and message.state = GENERAL then Action Event State Object Class APPROVE_ITEM INSERT PUBLISHED ITEM APPROVE_ITEM UPDATE UNPUBLISHED ITEM Action Event State Object Class APPROVE_ITEM INSERT NOT_PUBLISHED ITEM Action Event State Object Class EDIT_ITEM UPDATE GENERAL ITEM Note: No specific event is generated when the category or perspectives applied to an item are changed, and no additional information is provided. 16-18 Oracle Fusion Middleware Developers Guide for Oracle Portal . . . end if;16.3.7.2.5 Deleting an Item Deleting an item from a page group that retains deleted
items that is, items are marked for deletion, but not actually deleted produces the following message payload: Deleting an item from a page group that does not retain deleted items that is, deleted items are immediately and permanently removed produces the following message payload: Your subscriber can use the state value within the message payload to determine what type of delete action occurred: if message.action = DELETE_ITEM and message.object_class = ITEM and message.raw_event = DELETE then . . . -- If item is in a page group that does not actually delete items. if message.state = MARKED_FOR_DELETE then . . . -- If item is in a page group that actually deletes items. elsif message.state = PURGED then . . . end if; end if;16.4 Installing the Examples
If you would like to deploy and use the examples within the next few sections, we recommend that you create them in a separate schema, called CMEFSAMPLES. To create this schema, use the following steps:1. Create the database schema CMEFSAMPLES. You need to do this as the SYS user,
since you need to grant permissions packages to which only SYS has access. This database schema must be in the same database as that in which the Oracle Portal repository resides. For example: connect as sysdba drop user cmefsamples cascade; create user cmefsamples identified by oracle1 default tablespace users temporary tablespace temp; grant connect, resource to cmefsamples;2. As the SYS schema, grant the following privileges to CMEFSAMPLES:
connect as sysdba grant create table to cmefsamples; Action Event State Object Class DELETE_ITEM DELETE MARKED_FOR_ DELETE ITEM Action Event State Object Class DELETE_ITEM DELETE PURGED ITEM Using the Content Management Event Framework 16-19 grant create sequence to cmefsamples; grant create view to cmefsamples; grant create procedure to cmefsamples; grant create trigger to cmefsamples; grant create indextype to cmefsamples; grant create synonym to cmefsamples; grant create public synonym to cmefsamples; grant create database link to cmefsamples; grant create public database link to cmefsamples; grant execute on dbms_utility to cmefsamples; grant aq_administrator_role to cmefsamples; grant aq_user_role to cmefsamples; grant execute on dbms_aqadm to cmefsamples; grant execute on dbms_aq to cmefsamples; grant execute on aq_agent to cmefsamples; grant execute on dbms_job to cmefsamples; execute dbms_aqadm.grant_type_accesscmefsamples; execute dbms_aqadm.grant_system_privilegeENQUEUE_ANY,cmefsamples,FALSE; execute dbms_aqadm.grant_system_privilegeDEQUEUE_ANY,cmefsamples,FALSE; execute dbms_aqadm.grant_system_privilegeMANAGE_ANY, cmefsamples, FALSE; EXECUTE DBMS_AQADM.GRANT_QUEUE_PRIVILEGEENQUEUE,portal.WWSBR_EVENT_ Q,cmefsamples, FALSE; EXECUTE DBMS_AQADM.GRANT_QUEUE_PRIVILEGEDEQUEUE,portal.WWSBR_EVENT_ Q,cmefsamples, FALSE; 3. Grant the CMEFSAMPLES schema the permission to call the Oracle Portal PLSQL APIs. For information about how to do this, refer to Section 9.3, Providing Access to the APIs and Secure Views . 4. Log in to the portal schema and grant permissions on the following: EXECUTE DBMS_AQADM.GRANT_QUEUE_PRIVILEGEDEQUEUE,WWSBR_EVENT_ Q,cmefsamples, FALSE; grant execute on wwsbr_event_q_access to cmefsamples; grant execute on wwpob_page_util to cmefsamples; grant select on wwsbr_all_folders to cmefsamples; grant execute on wwsbr_thing_types to cmefsamples; grant execute on wwv_thingdb to cmefsamples; grant execute on wwsbr_event to cmefsamples; 5. Log in to the CMEFSAMPLES schema and run the following: sqlplus cmefsamplespassword create synonym aq_agent for sys.aq_agent; You can download the code for the following examples from OTN: http:www.oracle.comtechnologyproductsiasportalfilescm_overview_ 10g1014_cmef_samples.zip16.5 Example: Portal Object Event Logging
The LOG_PORTAL_EVENT subscriber in Example 16–9 listens to CMEF events and then writes them to a log database table called CMEF_LOG_TABLE Example 16–8 . 16-20 Oracle Fusion Middleware Developers Guide for Oracle Portal Example 16–8 The CMEF_LOG_TABLE create table cmef_log_table action varchar230, event varchar230, state varchar230, object_type varchar230, object_id number, object_site_id number, object_language varchar230, page_id number, page_site_id number, performed_by varchar230 Example 16–9 The LOG_PORTAL_EVENT Subscriber create or replace procedure log_portal_event as agent_list dbms_aq.aq_agent_list_t; wait_time integer := 5; agent_w_message sys.aq_agent; dequeue_options dbms_aq.dequeue_options_t; message_properties dbms_aq.message_properties_t; message_handle raw16; message portal.wwsbr_event; l_subscriber varchar230 := CMEF_LOG_PORTAL_EVENT; l_queue varchar230 := PORTAL.WWSBR_EVENT_Q; l_mode binary_integer := dbms_aq.REMOVE; begin agent_list1 := sys.aq_agentl_subscriber, l_queue, null; loop -- Wait for messages. dbms_aq.listen agent_list = agent_list, wait = wait_time, agent = agent_w_message ; if agent_w_message.name = l_subscriber then dequeue_options.wait := dbms_aq.NO_WAIT; dequeue_options.consumer_name := l_subscriber; dequeue_options.navigation := dbms_aq.FIRST_MESSAGE; dequeue_options.dequeue_mode := l_mode; dbms_aq.dequeue queue_name = l_queue, dequeue_options = dequeue_options, message_properties = message_properties, payload = message, msgid = message_handle ; insert into cmef_log_table values message.action, message.raw_event, message.state, message.object_class, message.object_id, message.object_site_id, message.object_language, message.page_id, message.page_site_id, message.events_user Using the Content Management Event Framework 16-21 ; commit; end if; end loop; end; The LOG_PORTAL_EVENT subscriber continuously listens for events on the WWSBR_EVENT_Q queue until the wait time of 5 seconds as specified in the wait_ time variable is reached. It then dequeues CMEF events in REMOVE mode and then inserts the message payload values into the log table. You could use the code in Example 16–9 to build an HTML page that displays the results of the log table. For example, the table in Figure 16–6 shows the CMEF message payload for an edit item action: Figure 16–6 HTML Table Displaying CMEF Message Payload Values The properties of the CMEF message payload for example, message.raw_event are described in Section 16.3.6, CMEF Message Payload . If you want the LOG_PORTAL_EVENT subscriber to continually remove messages off the WWSBR_EVENT_Q queue, then you need to remove the following from Example 16–9 : dbms_aq.listen agent_list = agent_list, wait = wait_time, agent = agent_w_message ; if agent_w_message.name = l_subscriber then dequeue_options.wait := dbms_aq.NO_WAIT; dequeue_options.consumer_name := l_subscriber; dequeue_options.navigation := dbms_aq.FIRST_MESSAGE; dequeue_options.dequeue_mode := l_mode; END IF; Example 16–10 shows how to add the LOG_PORTAL_EVENT subscriber created in the previous section to the WWSBR_EVENT_Q queue. Example 16–10 Adding the LOG_PORTAL_EVENT Subscriber to WWSBR_EVENT_Q declare subscriber sys.aq_agent; begin subscriber := sys.aq_agentCMEF_LOG_PORTAL_EVENT, null, null; dbms_aqadm.add_subscriber queue_name = portal.wwsbr_event_q, subscriber = subscriber ; end; To run the LOG_PORTAL_EVENT subscriber, issue the command shown in Example 16–11 .Parts
» Oracle Fusion Middleware Online Documentation Library
» Introduction to Portal Development Understanding Portlets
» Portlet Anatomy Oracle Fusion Middleware Online Documentation Library
» Out-of-the-Box Portlets Portlet Resources
» Other Sources of Prebuilt Portlets Web Clipping
» Portlet Builder Portlet Resources
» JSF Portlets Portlet Resources
» Programmatic Portlets Portlet Resources
» The Portlet Technologies Matrix
» Web Clipping OmniPortlet General Suitability
» Java Portlets Portlet Builder
» PLSQL Portlets General Suitability
» Java Portlets Expertise Required
» Web Providers Deployment Type
» WSRP Producers Deployment Type
» The user requests a portal page from the Web browser by entering a URL in the
» The Parallel Page Engine PPE, which resides in the Oracle Application Servers
» Database Providers Provider Registration
» PLSQL Portlets Development Tool
» OmniPortlet and Web Clipping Java Portlets Portlet Builder PLSQL Portlets
» Web Clipping OmniPortlet User Interface Flexibility
» Java Portlets and PLSQL Portlets
» Web Clipping OmniPortlet Java Portlets
» PLSQL Portlets Ability to Capture Content from Web Sites
» Web Clipping OmniPortlet Java Portlets Portlet Builder
» Public Portlet Parameters Support
» OmniPortlet, Web Clipping, and Portlet Builder
» Web Clipping and OmniPortlet Java Portlets Portlet Builder PLSQL Portlets
» Web Clipping OmniPortlet Java Portlets PLSQL Portlets
» Introduction to OmniPortlet Oracle Fusion Middleware Online Documentation Library
» Source The OmniPortlet Wizard
» Filter The OmniPortlet Wizard
» View Layout The OmniPortlet Wizard
» Edit Defaults mode The OmniPortlet Wizard
» Portlet Parameters and Events
» Adding an OmniPortlet Instance to a Portal Page Building an OmniPortlet Based on a Web Service
» Building an OmniPortlet Based on a Spreadsheet CSV
» Building an OmniPortlet Based on an XML Data Source
» Building an OmniPortlet Based on a Web Page Data Source
» Under New Page Parameter, in the Parameter Name field, enter zip, then click
» For the fourth OmniPortlet in the list, follow the same steps to set Param1 to the
» Set the Page Input as shown in Click OK.
» Building an OmniPortlet Using the HTML Layout
» Above the Web Clipping portlet, click the Edit Defaults icon, as shown in
» In the URL Location field, enter the location of the starting Web page that links to Click Start.
» At the top left of the section of the Web content you want to clip, click Choose.
» In the Find a Web Clipping page, click OK to display the selected Web clipping in
» In the Default Value field, enter a value to use by default for the parameter.
» Select Basic Authentication as the authentication method.
» In the Additional Fields section, you can enter names and values of any Click OK.
» At the top left of the section of the Web content you want to clip, click Choos
» Click Select to confirm that the search result section is the one you want to clip.
» Because the content displayed in the portlet was reached by entering information
» In the parameters table, make the following changes:
» Click OK to display the default search results in the Web Clipping portlet on your
» In the Editing Views section, click View Page.
» In the Web Clipping portlet header, click Personalize, as shown in
» In the page that displays, scroll down to the Inputs section. Notice that the
» Click OK. Personalizing a Web Clipping Portlet
» Verify that the Web provider that contains the URL-based portlets you want to
» Find existing URL-based portlets.
» Performing the Migration Migrating from URL-Based Portlets
» Post-Migration Configuration Migrating from URL-Based Portlets
» Maintaining Migrated Portlets Migrating from URL-Based Portlets
» Current Limitations for Web Clipping
» User preference: Guidelines for Show Modes
» Instance defaults: Guidelines for Show Modes
» Guidelines for Edit Defaults Mode Options The following guidelines should
» Guidelines for Buttons in Edit Defaults Mode For consistency and user
» Preview Mode JPS and PDK-Java Full Screen Mode PDK-Java
» Help Mode JPS and Oracle Portal
» Link Mode PDK-Java Portlet defaults
» Guidelines for Navigation within a Portlet
» Guidelines for JavaScript Guidelines for Writing Java Portlets
» Guidelines for Mobile Portlets
» Introduction to Java Portlet Specification JPS and WSRP
» Click Next. Creating a JSR 168 Portlet
» Click OK. Repeat the preceding steps if you want to add more customization
» In the Description field, enter a description for the security role, explaining the Click OK.
» Initialization parameters provide the Web application developer, who decides
» In the Name field, enter a unique name for the initialization parameter. Use only
» In the Value field, enter a default value for the parameter.
» In the Description field, enter a description for the parameter.
» To delete an initialization parameter, select it in the table and click Remove.
» Click Next to display the Finish page.
» Click Finish to generate the files for your portlet. The following files should be
» Adding Portlet Logic to Your JSR 168 Portlet
» In the Application Navigator, right-click the project that contains your portlet and
» In the Deployment Profile Name field, enter a meaningful name for the
» Click OK. Deploying Your JSR 168 Portlet to the Oracle WebLogic Server
» When the Deployment Finished message displays in the Deployment Log at the
» Click Next to display the Portal Registration Property Values page
» Click Finish. You should see a Registration Confirmation page similar to the one
» Registering WSRP Producers in Enterprise Configurations
» Introduction to Oracle PDK-Java
» Click Next to display the General Portlet Information Page.
» Click Next to display the Public Portlet Events page
» Click the link underneath Service Name.
» In the New Gallery, expand the General category and select Deployment Profiles.
» In the Items list, select WAR File and click OK. The Create Deployment Profile --
» Click OK. The WAR Deployment Profile Properties dialog box opens.
» Under Web Application’s Context Root, select Specify Java EE Web Context Root
» Select the Contributors node under WEB-INFlib.
» Select Portlet Development. Deploying Your Oracle PDK-Java Portlet to an Application Server
» Click OK. The Project Properties dialog opens.
» Click OK. Deploying Your Oracle PDK-Java Portlet to an Application Server
» In the Application Navigator, right-click your project and select Deploy, then
» If you are not already on the Portal Builder page, click the Builder link in the
» In the Remote Providers portlet, click Register a Provider to display the Register
» In the Name field, enter the name of the provider. The name must not be more
» In the Display Name field, enter a name to display for the provider when it is
» In the Timeout field, enter the number of seconds Oracle Portal should try to
» In the Timeout Message field, enter the message to display when Oracle Portal
» From the Implementation Style list, select Web.
» Click Next to display the Define Connection page
» In the Domain Structure tree, select Deployments.
» Click the Targets tab, and select AdminServer and WLS_WSRP from the Servers Click Save.
» In Oracle JDeveloper, double-click the view.jsp file for your JPS-Standard
» Add the code that is indicated in bold in the following snippet:
» Open edit.jsp in the visual designer and click the Design tab. Notice that the
» Click the Design tab to see the new form field that you just added
» Updating the XML Provider Definition
» Viewing the Portlet Under Web Content, htdocs\myportlet, create an HTML page called
» Click the magnifying glass icon next to the portlet and a preview window similar
» Reviewing the Generated Code The wizard creates the following code for you by
» Modifying the Generated Code The JSP contains an input field for the portlet
» Implementing Personalization for Show Pages
» Edit your Show page and import NameValuePersonalizationObject and
» Preference Information Within the XML Provider Definition
» Portlet URL Types Intraportlet links refer to the Oracle Portal page on which
» Building Links with the Portlet URL Types To build links with the URL
» Building Forms with the Portlet URL Types Use of portlet parameters in forms is
» Implementing Navigation within a Portlet You can implement navigation within a
» Submitting Events Go to the Parameter tab of the page properties. Note that parameters should be
» You can append a parameter value to the URL and the portlet displays the value
» When you click the link, that value is passed to the Parameter portlet on its page
» Go to the provider deployment in the Oracle WebLogic Administration Console,
» Creating Private Events Enhancing PDK-Java Portlets
» Ensure you are logged in to an Oracle Portal instance with privileges to create
» Create a new portal page, ensuring it is visible to PUBLIC.
» Add your Java portlet to the page.
» Make a note of the direct URL to your new Portal page.
» Now log out of the Portal instance by clicking the Logout link.
» Oracle Portal Server Security
» HTTPS Communication Directly access the Portal page by entering the URL noted in Step 4 into your
» Implementing Oracle Internet Directory Security PDK-Java provides a set of
» Viewing Your Portlets After you secure your provider with Oracle Internet
» Ensure you are logged in to an Oracle Portal instance as a user who is a member of
» Use an existing page or create a new one, ensuring it is visible to PUBLIC.
» Make a note of the direct URL to your new page.
» Click Logout. Implementing Portlet Security
» The portlet instance is the portlet on a page with the default personalizations made
» Create a stock portlet and implement the Show mode with the following
» Create two regions on a sample page and add My Stock Portlet to the first region.
» Securing Provider Communications If the security of exportingimporting
» Disabling ExportImport of Personalizations The JNDI variable,
» Obfuscating Data for Transport Automatic By default, personalization data is
» Exporting by Reference Example To export by reference rather than exporting
» Expiry-based Caching Enhancing Portlet Performance with Caching
» Invalidation-based Caching: Enhancing Portlet Performance with Caching
» You have followed through and understood
» Activating Caching You built a portlet using the wizard and successfully added it to a page.
» Configuring the Provider Servlet To enable invalidation-based caching, you must
» Defining the Oracle Web Cache Invalidation Port If you are using an Oracle
» Configuring the XML Provider Definition Using a combination of tags in
» Manually Invalidating the Cache You may want the cached version of the portlet
» Enhancing Portlets for Mobile Devices
» Writing Multilingual Portlets Enhancing PDK-Java Portlets
» Oracle Portal and the Apache Struts Framework
» Creating an Oracle Application Development Framework ADF Portlet
» Portlet Show Modes Guidelines for Creating PLSQL Portlets
» Recommended Portlet Procedures and Functions
» Implementing the Portlet Package
» Open starter_provider2.pks in an editor.
» Save and close starter_provider2.pkb.
» Creating and Accessing a Preference Store
» Implementing a Session Store
» Passing Private Parameters Passing Page Parameters and Mapping Public Portlet Parameters
» Retrieving Parameter Values Using Parameters
» Identify the piece of information you require for your functionality.
» Use the appropriate method from wwctx_api to get and optionally set this value.
» Open the services_portlet.pkb file in an editor.
» Find the get_portlet_info function.
» Notice the usage of wwctx_api.get_user to derive the user information and set
» wwctx_api.get_user is used similarly in various places throughout
» Another example of getting context information occurs in the is_runnable
» Using Security Implementing Portlet Security
» Coding Security Implementing Portlet Security
» Indicate to Oracle Portal that it must generate specific headers for Oracle Web
» Determine whether you want to use system or user level caching. Set the
» Optionally, set up validation- or expiry-based caching as well.
» Add invalidation logic to your portlet where needed for example, when the
» Configuring and Monitoring the Cache
» Implementing Validation-Based Caching Improving Portlet Performance with Caching
» Implementing Expiry-Based Caching Improving Portlet Performance with Caching
» Implementing Invalidation-Based Caching Improving Portlet Performance with Caching
» Using Error Handling Implementing Error Handling
» Adding Error Handling Implementing Error Handling
» Add the event object, with an appropriate domain and subdomain combination,
» Register the log event record by using wwlog_api_admin.add_log_registry.
» Use start_log and stop_log to mark the events you want to log in your code.
» Adding Event Logging Implementing Event Logging
» Using Multilingual Support Writing Multilingual Portlets
» Adding Multilingual Support Writing Multilingual Portlets
» Registration Prerequisites Provider Record Input Registration Example
» Overview Oracle Fusion Middleware Online Documentation Library
» Secure Content Repository Views
» Terminology Content Management APIs
» Providing Access to the APIs and Secure Views
» Using Constants Guidelines for Using the APIs
» Resetting CMEF Global Variables
» Code Samples Oracle Fusion Middleware Online Documentation Library
» Setting the Session Context API Parameters
» Editing Page Properties Oracle Fusion Middleware Online Documentation Library
» Setting Item Attributes Editing Content
» Editing an Item Editing Content
» Moving an Item to a Different Page Moving Pages
» Moving Categories and Perspectives
» Deleting Items Deleting Content
» Deleting Pages Deleting Content
» Creating Pages Oracle Fusion Middleware Online Documentation Library
» Creating Categories and Perspectives
» Creating Items Oracle Fusion Middleware Online Documentation Library
» Setting Perspectives Attributes of Pages and Items
» Approving and Rejecting Items
» Searching For Items Across All Page Groups
» Searching For Pages in Specific Page Groups
» Searching For Items By Attribute
» Creating a Directory for the XML File
» Creating an XML File from a CLOB
» Generating Search Results in XML Workaround for get_item_xml
» Click Next. On the View page, select Tabular for the Layout Style, then click Next.
» Introduction to Multi-Lingual Support
» Querying the Default Language
» Setting the Session Language Modifying an Existing Translation Creating a Translation for an Item
» Translations and Item Versioning
» Retrieving Object Privileges Oracle Fusion Middleware Online Documentation Library
» Granting Page Level Privileges
» Removing Page Level Privileges
» Granting Item Level Privileges
» Removing Item Level Privileges
» Inheriting Item Level Privileges from the Page
» Enqueuing Messages How Does the Content Management Event Framework Work?
» Subscribers and Dequeuing Messages
» Exception Handling Listening for Messages
» Creating Subscriber Code Using the Content Management Event Framework
» In the toolbar at the top of the page, click the Properties link next to Page Group.
» Click the Configure tab to bring it forward.
» To enable CMEF, select the Enable Content Management Event Framework check
» Click OK to save your changes.
» Click Close to return to the page.
» Adding a Subscriber to WWSBR_EVENT_Q Running a CMEF Subscriber
» CMEF Message Payload Using the Content Management Event Framework
» Oracle Portal Actions and CMEF Events
» What Is the Content Management Event Framework? Installing the Examples
» Example: Portal Object Event Logging
» Example: Item Validation Oracle Fusion Middleware Online Documentation Library
» Integrating Workflow with Oracle Portal
» Example Overview Example: Integrating External Workflow
» Section 16.8.3.2, Grant Users the Manage Items With Approval Privileges
» Section 16.8.3, Run Scripts Required for the CMEF Workflow Integration
» Section 16.8.3.4, Create Subscriber and Check Procedures
» Section 16.8.3.5, Register the WF_CHECKURL Process with Oracle Workflow
» Enable Approvals and Notifications in Oracle Portal
» To enable approvals and notifications, select the Enable Approvals and
» Grant Users the Manage Items With Approval Privileges
» Go to any page in the page group and switch to Edit mode.
» Click the Approval tab to bring it forward.
» Select the Require Approval for All Users check box
» Create Subscriber and Check Procedures
» Log in to the CMEFSAMPLES schema and run the following: Start a new workflow project.
» Add the CMEF_WORKFLOW Subscriber to the WWSBR_EVENT_Q Queue
» Set the definition value in the provider_name.properties file that is
» From the WebLogic Server menu, choose Application Deployment, and then
» Click Continue. The URL mapping for Web Modules displays. The mappings will
» Click Next. Detailed Example Description
» In the Application Attributes section, for Application Name, enter the application
» Expand Deployment Plan. Detailed Example Description
» Click Deploy. Detailed Example Description
Show more