Previous	Next		Contents	Index	Glossary

1. Use a web browser to connect to the Oracle Workflow home page, then choose the Global Preferences link:

	<webagent>/wfa_html.home

Alternatively, you can connect directly to the Global Preferences web page:

	<webagent>/wf_pref.edit?edit_defaults=Y

<webagent> represents the base URL of the web agent you configured for Oracle Workflow in your Web server.

Attention: These are secured pages, so if you have not yet logged on as a valid user in the current web session, you will be prompted to do so before the page appears.

2. The Global Preferences web page displays a summary of your current global preferences. Choose Update to modify these preferences.

3. In the Workflow Administrator field, use the list of values to select the role to which you want to assign workflow administrator privileges. Any user associated with this role can run the Oracle Workflow Find Processes web page, which provides full access to Oracle Workflow's administration features. In addition, any user in the administration role can view any other user's notifications and access the Event Manager web pages.

If you want all users and roles to have workflow administrator privileges, such as in a development environment, enter an asterisk (*) in the Workflow Administrator field. See: Setting Up an Oracle Workflow Directory Service.

Note: To find out which role currently has workflow administrator privileges, without accessing the Global Workflow Preferences page, you can use the following command:

		select text 

		from wf_resources

		where name = 'WF_ADMIN_ROLE';

After installing Oracle Workflow, you should change the Workflow Administrator preference from the default setting to the role that you want to have administrator privileges.

• For the standalone version of Oracle Workflow, the default setting after installation is an asterisk (*). You can log in as any user to access the Global Workflow Preferences page and specify the preferences you want.

• For the version of Oracle Workflow embedded in Oracle Applications, the default setting after installation is SYSADMIN. You must log in as the SYSADMIN user to access the Global Workflow Preferences page and specify the preferences you want.

Note: The SYSADMIN role is different than the role associated with the System Administrator responsibility in Oracle Applications. If you want to assign workflow administrator privileges to this or any other Oracle Applications responsibility, you must set the Workflow Administrator preference to the internal name of the Workflow role associated with that responsibility.

You can query the WF_ROLES view to find the role name for a responsibility. For example, to find the role names for various administrator responsibilities in Oracle Applications, use the following command:

		select name, display_name

		from wf_roles

		where display_name like '%Admin%';

If you set the Workflow Administrator preference to the role name of a responsibility, then any Oracle Applications user with that responsibility will have workflow administrator privileges.

4. In the Workflow Web Agent field, enter the base URL of the Oracle web agent you defined for Oracle Workflow in Oracle HTTP Server.

Caution: The list of values fields that are implemented in many of Oracle Workflow's web pages will not function properly unless you specify the base URL of your Oracle Workflow web agent in this field.

The base URL should look like this if you are using Oracle HTTP Server as your Web server:

	http://<server.com:portID>/pls/<DAD_name>

<server.com:portID> represents the server and TCP/IP port number on which your web listener accepts requests and <DAD_name> represents the name of the DAD you configured for the Oracle Workflow database schema.

See your Oracle HTTP Server documentation for more information.

Attention: If you are using the version of Oracle Workflow embedded in Oracle Applications, you should also edit the APPS_WEB_AGENT profile option.

5. If you are using the version of Oracle Workflow embedded in Oracle Applications, enter the Jinitiator plugin class ID, download location, and version number. This information is required for Oracle Workflow to launch Oracle Applications forms linked to notifications and to display the Workflow Monitor. See: Setting the Socket Listener Profile Options.

6. The Local System field displays the system name for the database where this installation of Oracle Workflow is located. Oracle Workflow automatically creates the system definition for this database in the Event Manager during installation. The Business Event System treats this system as the local system and all others as external systems. See: Systems.

Note: The Local System setting is specific to this installation of Oracle Workflow and is not included when Business Event System data is replicated to other systems.

7. In the System Status field, use the list of values to select the Business Event System status that you want to assign to the local system.

• Enabled--Subscriptions are executed on all events.

• Local Only--Subscriptions are executed only on events raised on the local system.

• External Only--Subscriptions are executed only on events received from external systems.

• Disabled--No subscriptions are executed on any events.

Note: Oracle Workflow sets the system status to Enabled by default. After you finish setting up the Business Event System, you can change the setting to the status you want for event processing.

Note: The System Status setting is specific to this installation of Oracle Workflow and is not included when Business Event System data is replicated to other systems.

8. If you are implementing Oracle Internet Directory (OID) synchronization, specify the Lightweight Directory Access Protocol (LDAP) server information for the LDAP directory to which you want to connect.

• LDAP Host--The host on which the LDAP directory resides.

• LDAP Port--The port on the host.

9. If you are implementing OID synchronization, specify the LDAP user account used to connect to the LDAP server. This LDAP user account must have write privileges.

• LDAP User Name--The LDAP user. This user name is required to bind to the LDAP directory. For example:

		cn=orcladmin

• LDAP Password--The LDAP password. The password is stored in encrypted form.

10. If you are implementing OID synchronization, specify the directories for the change log and the user records.

• LDAP Changelog Base Directory--The LDAP node under which change logs are located. For example:

		cn=changelog

• LDAP User Base Directory--The LDAP node under which user records can be found. For example:

		cn=Base, cn=OracleSchemaVersion 

11. In the Language and Territory fields, use the list of values to select the NLS_LANGUAGE and NLS_TERRITORY combination that defines the default language-dependent behavior and territory-dependent formatting of your users' notification sessions.

12. In the Date Format field, specify an Oracle8i-compliant date format that defines the default date format for the workflow database sessions of all users. An example of an Oracle8i-compliant date format is DD-Mon-RRRR. If you do not specify a date format, then the date format defaults to DD-MON-YYYY.

Note: Oracle Workflow may include a time element when relevant for certain displayed dates, even if you do not include a time format with your date format. If you specify a time format along with your date format, then in those situations when Oracle Workflow displays a time element, you will see two time elements following your date.

13. In the Document Home Node field, use the list of values to select the default Document Management repository that users access when they attempt to attach or access an attached document management document. (This functionality will be supported in a future release.)

14. In the 'Send me electronic mail notifications' field, use the list of values to select a notification preference:

• HTML mail--Send notifications as HTML e-mail. Users must read their mail using an HTML e-mail viewer.

• Plain text mail with HTML attachments--Send notifications as plain text e-mail but include the HTML-formatted version of the notifications as attachments.

• Plain text mail--Send notifications as plain text e-mail.

• Plain text summary mail--Send a summary of all notifications as plain text e-mail. Users must use the Notifications web page to take action on individual notifications.

• Do not send me mail--Do not send the notifications as e-mail. Users must view the notifications and take action from the Notifications web page.

15. Click OK once you are satisfied with your changes.

Note: These global language, territory, document home node, and notification preferences are saved to the Oracle Workflow Preferences table for a special user name called -WF_DEFAULTS-. The workflow administrator role, workflow web agent, local system, and LDAP information is saved to the Workflow Resources table.

Copyright © 2002 Oracle Corporation.
All Rights Reserved.