Additional Setup Steps
After you complete the Oracle Workflow installation process, you must perform some additional steps to set up Oracle Workflow for your site. Some of the setup steps are required; other steps are optional, depending on the Oracle Workflow features you want to implement. Refer to the Setting Up Oracle Workflow and the Managing Business Events chapters in the Oracle Workflow Guide for information on how to complete these and other setup steps for Oracle Workflow. The setup steps include:
1. (Required) Configuring the default global user preferences for your enterprise.
2. (Required) Mapping Oracle Workflow's directory service views to your organization's users and roles. Oracle Universal Installer automatically executes the wfdirouv.sql script to map the directory service views to your native Oracle users and roles. You can either create your own script or customize and rerun this script to map the directory service views to the users and roles defined in your organization's directory repository.
Attention: The wfdirouv.sql script sets each native Oracle user's e-mail address to the user's respective username. As a minimal setup step, you should edit the wfdirouv.sql script to either link your native Oracle users to an existing mail directory store through the WF_ROLES view definition or, if the usernames and e-mail account names match, then simply add the domain for your organization, such as '@oracle.com', to the usernames in the WF_USERS view definition. Typically, the columns that you change are EMAIL_ADDRESS in WF_USERS and EMAIL_ADDRESS in WF_ROLES.
3. (Required) Creating a view called WF_LANGUAGES that identifies the languages defined in your Oracle9i installation. The wfdirouv.sql script run by the Oracle Universal Installer automatically creates a sample WF_LANGUAGES view for you. If you want to use this view, you should verify it first by connecting to SQL*Plus using your Workflow database account and querying the view for all languages defined in your Oracle9i installation.
4. (Required) Defining an environment variable called WF_RESOURCES if your Workflow Server is installed on a UNIX platform.
Attention: Do not enclose environment variable values in double quotes (" ") as this is not supported.
5. (Optional) Defining a document management system node for Oracle Workflow if you want to integrate document management attachments in a workflow process.
6. (Required) Initiating background Workflow engines to process deferred work and timed out activities.
7. (Optional) Configuring and running the Notification Mailer program, to allow users to receive e-mail notifications or e-mail notification summaries.
8. (Optional) Customizing e-mail notification templates.
9. (Optional) Customizing the logo displayed on Oracle Workflow's web pages.
10. (Optional) Adding custom icons to Oracle Workflow.
11. (Optional) Starting the Java Function Activity Agent to run external Java functions.
12. (Optional) Setting up database links and queues for the Business Event System to communicate events between systems.
13. (Optional) Scheduling Business Event System listeners and propagations to receive and send event messages.
14. (Optional) Setting up event subscriptions to synchronize Business Event System data on different systems.
