|Oracle Workflow Administrator's Guide|
Part Number B10283-02
Oracle Workflow requires a directory service to provide information about the individuals and roles in your organization who may utilize Oracle Workflow functionality and receive workflow notifications. Oracle Workflow references this user and role information through the following three views.
Note: A role can contain only individual users as its members. It cannot contain another role.
See: Workflow Directory Service Views.
Oracle Workflow provides predefined directory services for you that are implemented by default during installation.
You can also create your own directory service by defining custom views with the required columns. However, note that only the predefined directory services provided by Oracle Workflow are supported by Oracle. See: Oracle Workflow Support Policy, Oracle Workflow Developer's Guide.
Oracle Workflow provides two local directory repository tables called WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES. These tables should always be included in any implementation of the WF_USERS, WF_ROLES, and WF_USER_ROLES views.
For the standalone version of Oracle Workflow, if you are integrating with OID, the Workflow local tables store user information that is retrieved from and synchronized with OID, as well as Workflow role information that is entered and stored locally. If you are integrating with Oracle Database users or a custom directory service repository, you can use these tables to store ad hoc users and roles not included in your existing tables. You can create such ad hoc users and roles in the Workflow local tables by calling the appropriate Workflow directory service PL/SQL APIs.
Note: If you implement OID integration, you must not create ad hoc users in the Workflow local tables, because you risk discrepancies in your user information and unpredictable results if you use any tool other than OID to maintain users after integrating with OID. You can still use ad hoc roles, however, since Workflow roles are not maintained through OID. See: Synchronizing Workflow Directory Services with Oracle Internet Directory.
For Oracle Workflow embedded in Oracle Applications, the Workflow local tables now store denormalized user and role information originating from various other Oracle Applications modules, so that the directory service views can access this information with good performance. You can also use these tables to store ad hoc users and roles by calling the appropriate Workflow directory service PL/SQL APIs.
In both standalone Oracle Workflow and Oracle Applications, you should periodically purge users and roles from the Workflow local tables after they have expired in order to improve performance. See: Directory, Oracle Workflow API Reference.
Context: You need to perform this step only once.
Workflow Directory Service APIs, Oracle Workflow API Reference
Ad Hoc Users and Roles, Oracle Workflow Developer's Guide
Setting Up a Directory Service for Standalone Oracle Workflow
Setting Up a Directory Service for Oracle Workflow Embedded in Oracle Applications
Workflow Directory Service Views
Oracle Workflow Security