Previous	Next		Contents	Index	Glossary	Library

   Step 1: If you are using the standalone version of Oracle Workflow, you must map Oracle Workflow's directory service to the users and roles currently defined in your organization's directory repository by constructing views based on those database tables. The Notification System uses these views to send notifications to the performers specified in your activities. Your roles can be either individual users or a group of users. Oracle Workflow provides example directory services views that you can modify and reload. See: Setting Up an Oracle Workflow Directory Service.

   Step 2: If you are using the standalone version of Oracle Workflow, you must create a view called WF_LANGUAGES that identifies the languages defined in your Oracle7 installation. Oracle Workflow uses this view to create in its translation tables, a row that maps to a row found in its non-translated base table for each installed language. See: Creating the WF_LANGUAGES View.

   Step 3: If you are using the standalone version of Oracle Workflow, you must define an environment variable called WF_RESOURCES. See: Setting the WF_RESOURCES Environment Variable.

   Step 4: After you install and configure Oracle WebServer, identify the Web Agent to be used by Oracle Workflow. See: Identifying the Oracle Web Agent used by Oracle Workflow.

   Step 5: Once you define your Oracle Workflow directory service, you need to identify the role that should have access to Oracle Workflow's administration features such as the Find Processes web page. See: Identifying the Oracle Workflow Administration Role.

   Step 6: Configure Oracle WebServer to point to the Java code required to run the Workflow Monitor and optionally customize the company logo that appears in Oracle Workflow's web pages. See: Setting Up the Workflow Monitor and Oracle Workflow's Web Pages.

   Step 7: If you are using the standalone version of Oracle Workflow, secure your Workflow database connection using Oracle WebServer security. See: Secure the Workflow Database Connection Descriptor.

   Step 8: Set up the Notification Mailer program so that users can receive notifications by E-mail if that is an option you are providing to your users. See: Implementing the Notification Mailer.

   Step 9: Set up background Workflow Engines to control the load and throughput of the primary Workflow Engine on your system. You can specify the cost threshold level of your primary and background engines to determine the activities an engine processes and the activities an engine defers. See: Setting Up Background Workflow Engines.

   Step 10: You can modify the templates for your electronic mail notifications. See: Modifying Your Message Templates.

   Step 11: You can include additional icons to your Oracle Workflow Icons subdirectory to customize the diagrammatic representation of your workflow processes. Use custom icons to provide meaningful symbols for each activity you define. See: Adding Custom Icons to Oracle Workflow.

You can also use the Workflow Definitions Loader to load workflow process definitions from flat files to the database without using Oracle Workflow Builder. See: Using the Workflow Definitions Loader.