Setting Up Oracle Workflow

Setting Up Oracle Workflow
Overview
Copyright © Oracle Corporation, 2004. All rights reserved.
Setting Up Oracle Workflow 517727198.doc

Effective Paradigm_effective Page 1 of 64 Rev Paradigm_revision
System References
None
Distribution
Job Title*
Ownership
The Job Title [[email protected]?Subject=EDUxxxxx] is responsible for ensuring that
this document is necessary and that it reflects actual practice.

Schedule: Timing Topic

100 minutes Lecture
30 minutes Practice
130 minutes Total

Objectives

Required Setup Steps
Required Setup Steps

1. Set system-wide preferences and default user preferences for your installation of Oracle
Workflow using the Workflow Configuration page in Oracle E-Business Suite or the Global
Workflow Preferences page in standalone Oracle Workflow.
2. Ensure that a directory service is set up to provide information about the individuals and
roles in your organization who may utilize Oracle Workflow functionality and receive
workflow notifications..
3. If you are using the standalone version of Oracle Workflow and your Workflow server is
installed on a UNIX platform, define an environment variable called WF_RESOURCES.
4. Set up background Workflow engines to manage the load on the primary Workflow Engine
by processing deferred and timed out activities and stuck processes.
5. Configure the Business Event System for event communication.
For more information, refer to the Setting Up Oracle Workflow chapter in the Oracle
Workflow Administrator’s Guide.

Step 1 Setting Global Workflow Preferences
Setting Global Workflow Preferences

Use a Web browser to navigate to the Workflow Configuration page, using a responsibility and
navigation path specified by your system administrator. Some possible navigation paths in the
seeded Workflow responsibilities are:
• Workflow Administrator Web Applications: Administration > Workflow Preferences
• Workflow Administrator Web (New): Administration > Workflow Preferences
• Workflow Administrator Event Manager: Administration > Workflow Preferences
You can also navigate to the Workflow Configuration page from other Oracle Workflow
administrator Web pages by choosing the Administration tab or selecting the Administration
link at the end of the page.
You must have workflow administrator privileges to set global workflow preferences in the
Workflow Configuration page. If you do not have administrator privileges, you can view
global workflow preferences, but you cannot modify them.
Workflow Administrator
Select the role to which you want to assign workflow administrator privileges. If you want all
users and roles to have workflow administrator privileges, such as in a development
environment, enter an asterisk (*).

LDAP
If you are integrating with Oracle Internet Directory, specify the Lightweight Directory Access
Protocol (LDAP) server information for the LDAP directory to which you will connect. If you
already configured these parameters while installing Oracle Application Server with Oracle E-
Business Suite, Oracle Workflow displays those values here. For more information, see:
Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i
(OracleMetaLink note 233436.1) and Integrating Oracle E-Business Suite Release 11i with
Oracle Internet Directory and Oracle Single Sign-On (OracleMetaLink note 261914.1).
• Host - The host on which the LDAP directory resides.
• Port- The port on the host.
• Username - The LDAP user account used to connect to the LDAP server. This user name
must have write privileges and is required to bind to the LDAP directory.
• Old Password - Enter your current LDAP password. Oracle Workflow validates this
password before letting you change it.
• New Password - Enter the new LDAP password you want to use. The password must be at
least five characters long.
• Repeat Password - Enter your new LDAP password again in this field to confirm it. You
must enter exactly the same value that you entered in the New LDAP Password field.
• Change Log Base Directory - The LDAP node under which change logs are located.
• User Base Directory - The LDAP node under which user records can be found.
Local System
Specify the system name for the database where this installation of Oracle Workflow is
located, to identify it in the Business Event System. Oracle Workflow automatically creates the
system definition for this database in the Event Manager during installation.
Select the execution status for the local system.
• Enabled – Subscriptions are executed on all events. Oracle Workflow sets the system status
to Enabled by default.
• Local Only – Subscriptions are executed only on events raised on the local system.
• External Only – Subscriptions are executed only on events received by inbound agents on
the local system.
• Disabled – No subscriptions are executed on any events.
Default Notification Style
Specify whether Oracle Workflow should send e-mail notifications to users, and if so, in what
format. A user can override this default setting by specifying a different notification style in his
or her individual Oracle E–Business Suite preferences.
• HTML mail with attachments
• Plain text mail with HTML attachments
• Plain text mail
• Plain text summary mail
• Do not send me mail
• HTML mail
• HTML summary mail

Browser Signing DLL Location
Specify the location of the Capicom.dll file that is used for Web page operations with
encryption in the Microsoft Internet Explorer browser. This preference is required only if you
plan to use certificate-based digital signatures to confirm notification responses, and your users
access Oracle Applications with Microsoft Internet Explorer. By default, this preference is set
to a URL at which the Capicom.dll file can be downloaded from Microsoft’s Web site. In most
cases, you do not need to change this setting. However, you can update this preference if the
location of the Capicom.dll file changes, or if you choose to store a copy of the file on your
local network and point to that location instead.
JInitiator
Review details about the JInitiator plugin in your Oracle E-Business Suite installation. Oracle
Workflow uses JInitiator to launch Oracle Applications forms linked to notifications.
• Class ID – The class identifier for this version of JInitiator.
• Download Location – The location where the JInitiator executable is staged for download
to users’ client machines.
• Version – The JInitiator version number.
For more information, refer to OracleMetaLink note 162488.1, ”Complete Guide to JInitiator
for Oracle’s E–Business Suite: 11.5.x (11i).”
Instructor Note
The Lightweight Directory Access Protocol (LDAP) is a standard, extensible directory access
protocol. It is a common language that LDAP clients and servers use to communicate. LDAP
was conceived as an internet–ready, lightweight implementation of the International
Standardization Organization (ISO) X.500 standard for directory services. It requires a minimal
amount of networking software on the client side, which makes it particularly attractive for
internet–based, thin client applications. For more information, see the Oracle Internet
Directory Administrator’s Guide.

Step 1 Setting Global Workflow Preferences
Setting Global Workflow Preferences

To access the Global Workflow Preferences Web page for standalone Oracle Workflow, use a
Web browser to connect to the Oracle Workflow home page at the following URL:
<webagent>/wfa_html.home
Replace <webagent> with the base URL of the Web agent configured for Oracle Workflow in
your Web server. Then choose the Global Preferences link.
Note: You must have workflow administrator privileges to access the Global Workflow
Preferences Web page.
Workflow Administrator
Enter the role with workflow administrator privileges. If you want all users and roles to have
workflow administrator privileges, such as in a development environment, enter an asterisk (*).
Workflow Web Agent
Enter the base URL of the Oracle Web agent you defined for Oracle Workflow in Oracle
HTTP Server.
Local System

When you install Oracle Workflow, the database where the installation is located is
automatically defined as a system in the Event Manger and set as the local system in the Global
Workflow Preferences page.
System Status
• 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.
Oracle Workflow sets the system status to Enabled by default. After you finish setting up the
Business Event System, change the setting to the status you want for event processing.
LDAP
Enter Lightweight Directory Access Protocol (LDAP) preferences if you are implementing
Oracle Internet Directory synchronization
Note: In standalone Oracle Workflow, if you choose Oracle Internet Directory synchronization
and enter LDAP preferences during installation, those values are automatically set in these
fields in the Global Workflow Preferences page.
• Specify the 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.
• 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.
- Old LDAP Password - Enter your current LDAP password. Oracle Workflow validates
this password before letting you change it.
- New LDAP Password - Enter the new LDAP password you want to use. The password
must be at least five characters long.
- Repeat LDAP Password - Enter your new LDAP password again in this field to
confirm it. You must enter exactly the same value that you entered in the New LDAP
Password field.
• Specify the directories for the change log and the user records.
- LDAP Changelog Base Directory - The LDAP node under which change logs are
located.
- LDAP User Base Directory - The LDAP node under which user records can be found.
Language and Territory
If you are using standalone Oracle Workflow, select the NLS_LANGUAGE and
NLS_TERRITORY combination that defines the default language-dependent behavior and
territory-dependent formatting of your users’ notification sessions.
Date Format
If you are using standalone Oracle Workflow, specify an Oracle Database-compliant date
format that defines the default date format for the workflow database sessions of all users.

Document Home Node
This functionality is reserved for future use.
Send me electronic mail notifications
Select the default notification preference for all users:
• HTML mail with attachments
• Plain text mail with HTML attachments
• Plain text mail
• Plain text summary mail
• Do not send me mail
• HTML mail
Note: The “HTML summary mail” preference is not applicable for standalone Oracle
Workflow.
Note: The language, territory, and notification preference settings in the Global Preferences
and User Preferences Web pages are valid only if your directory service views map the
Language, Territory, and Notification_Preference columns to the Oracle Workflow preferences
table.

Step 2 Setting Up an Oracle Workflow Directory Service
Setting Up an Oracle Workflow Directory Service

In the predefined directory service implementations, Oracle Workflow automatically creates
directory service views to integrate with the appropriate directory repository.
Note: If you integrate with Oracle Database users and roles as your directory repository in
standalone Oracle Workflow, you should modify the default views to add e-mail addresses
for these users if you want them to be able to receive e-mail notifications.
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.



For details on the patches that are currently available to automate synchronization of user and
role information from various modules, please refer to OracleMetaLink note 171703.1,
Implementing Oracle Workflow Directory Service Synchronization.
The concurrent program is provided as an interim method to synchronize the Workflow local
tables with the user and role information stored in the product application tables until each
affected product performs the synchronization automatically.
The Synchronize Workflow LOCAL Tables request set contains ten instances of the
Synchronize WF Local Tables program, one for each originating system. You can use this
request set to submit requests for all the originating systems at once. By default, this request set
is scheduled to run once a day to provide a minimal level of synchronization. You can modify
the schedule for the request set to perform synchronization more frequently.
You only need to run the bulk synchronization program for products for which you do not have
an incremental synchronization patch installed. After applying the patch for a product, you no
longer need to run the program for originating systems owned by that product.
Use the Submit Requests form to submit the request set or concurrent program. Enter the
following parameters:

• Parallel Processes - Enter the number of parallel processes to run. The default value for this
parameter is 1. However, if your hardware resources allow, you can optionally set this
parameter to a higher value in order to parallelize the queries during execution of the
program.
• Logging - Select the logging mode you want. This mode determines whether redo log data
is generated for database operations performed by the bulk synchronization process. The
default value for this parameter is LOGGING, which generates redo log data normally.
You can optionally set the logging mode to NOLOGGING to suppress redo log data,
obtaining a performance gain. Without this redo log data, however, no media recovery is
possible for the Workflow directory tables and indexes.
• Orig System (single concurrent program only) - Select the name of the originating system
whose user and role information you want to synchronize with the WF_LOCAL tables.
You can select the following systems:
- AMV_APPR - MarketView Approvals
- AMV_CHN - MarketView Channels
- ENG_LIST - Engineering Approval List
- FND_RESP - FND Responsibilities
- FND_USR - FND Users
- GBX - Federal HR Group Boxes
- HZ_GROUP - TCA Groups
- HZ_PARTY - TCA Parties
- PER_ROLE - HR People
- POS - HR Positions
For more information, refer to Submitting a Request Set, Oracle Applications User’s Guide.
Note: You cannot use bulk synchronization for an originating system that has been enabled for
role hierarchies. Systems that use role hierarchies must perform incremental synchronization.


With single sign-on, a user who is logged into any participating Oracle Application Server
component is automatically authenticated when accessing any other participating component
and does not need to log in again.
If you choose to integrate with Oracle Internet Directory, you should maintain synchronization
between your Workflow directory service and Oracle Internet Directory. For more information,
see optional setup step 2.
Instructor Note
Integration with Oracle Internet Directory, LDAP, and SSO is available for Oracle E-Business
Suite, but this integration is not owned by Oracle Workflow. For more information, see
OracleMetaLink note 150832.1, “Implementing Single Sign-On for Oracle Applications 11i
with Login Server Authentication Using Oracle Internet Directory”.

Step 3 Setting the WF_RESOURCES Environment Variable

Step 4 Running Background Engines
Running Background Engines

You can set up as many background engines as you need, but if you set up only one, then that
background engine must handle both deferred and timed out activities as well as stuck
processes. That is, the process_deferred, process_timeout, and process_stuck parameters must
all be TRUE.
Generally, you should run a separate background engine to check for stuck processes at less
frequent intervals than the background engine that you run for deferred or timed out activities,
normally not more often than once a day. Run the background engine to check for stuck
processes when the load on the system is low. Do not run more background engines
concurrently than your server CPU can handle while running other applications.


Running Background Engines

Background Engine Parameters
• itemtype: Optional item type to restrict this engine to activities associated with that item
type.
• minthreshold: Optional minimum cost that an activity must have for this background
engine to execute it, in hundredths of a second.
• maxthreshold: Optional maximum cost an activity can have for this background engine to
execute it, in hundredths of a second.
• process_deferred: Specify TRUE or FALSE to indicate whether the engine should check
for deferred activities.
• process_timeout: Specify TRUE or FALSE to indicate whether the engine should check for
timed out activities.
• process_stuck: Specify TRUE or FALSE to indicate whether the engine should check for
stuck processes.

Step 5 Configuring the Business Event System

Step 5 Event Message Communication
Event Message Communication

To send an event message, Oracle Workflow places the event message on a local outbound
agent’s queue. You must schedule propagation to deliver the message from there to the
designated inbound agent’s queue.
To receive an event message in Oracle Workflow, you must run an agent listener to dequeue
the message from the inbound agent’s queue for Oracle Workflow to process. A component of
the Event Manager called the Event Dispatcher then searches for and executes subscriptions to
the event.

Step 5 Setting Up Database Links and Queues
Setting Up Database Links and Queues

Database Links
When you set up database links for use by the Business Event System, you should fully qualify
each database link name with the domain name.
Queues
In addition to the standard queues provide by Oracle Workflow, you can also set up your own
queues for event message propagation. To set up a queue, you must create the queue table,
create the queue, and start the queue.
Oracle Workflow provides a sample script called wfevquec.sql which you can modify to set up
queues, as well as a sample script called wfevqued.sql which you can modify to drop queues.
These scripts are located on your server in the ORACLE_HOME/wf/sql directory for
standalone Oracle Workflow, or in the $FND_TOP/sql directory for Oracle E-Business Suite.
If you define a queue with a payload type other than the standard WF_EVENT_T Workflow
format or the JMS Text message format, you must create a queue handler to translate between
WF_EVENT_T and the format required by the queue.

Step 5 Checking Database Parameters
Checking Database Parameters

• JOB_QUEUE_PROCESSES - This parameter defines the number of SNP job queue
processes for your instance. Oracle Workflow requires job queue processes to handle
propagation of Business Event System event messages by AQ queues and for notification
mailers. The recommended number of processes for Oracle Workflow is ten or more. The
maximum number of processes is 36 in Oracle8i Database and 1000 in Oracle9i Database
and higher.
• AQ_TM_PROCESSES - This parameter enables the time manager process in Oracle
Advanced Queuing (AQ). The time manager process is required by Oracle Workflow to
monitor delay events in queues, as in the case of the Oracle Workflow standard Wait
activity, and for notification mailers. The recommended number of time manager processes
for Oracle Workflow is two or more.

Step 5 Scheduling Agent Listeners
Scheduling Agent Listeners

The Generic Service Component Framework is a facility that helps to simplify and automate
the management of background Java services.
Agent listener service components, managed through Oracle Workflow Manager, are the most
automated and robust way to run agent listeners. However, Oracle Workflow also provides an
administrative script named wfagtlst.sql that you can use to run an agent listener, or you can
run the WF_EVENT.Listen API directly in SQL*Plus. These methods are intended primarily
for testing and debugging purposes.
Note: Java agent listeners are available only in Oracle E-Business Suite.

Step 5 Scheduling Agent Listeners
Scheduling Agent Listeners

Seeded PL/SQL agent listeners:
• Workflow Deferred Agent Listener - Handles messages on WF_DEFERRED to support
deferred subscription processing.
• Workflow Deferred Notification Agent Listener - Handles notification messages on
WF_DEFERRED to support outbound notification processing.
• Workflow Error Agent Listener - Handles messages on WF_ERROR to support error
handling for the Business Event System.
• Workflow Inbound Notifications Agent Listener - Handles messages on
WF_NOTIFICATION_IN to support inbound e-mail notification processing.
Seeded Java agent listeners:
• Workflow Java Deferred Agent Listener - Handles messages on WF_JAVA_DEFERRED
to support deferred subscription processing in the middle tier.
• Workflow Java Error Agent Listener - Handles messages on WF_JAVA_ERROR to
support error handling for the Business Event System in the middle tier.

In Oracle E-Business Suite, Oracle XML Gateway also provides PL/SQL agent listeners
named ECX Inbound Agent Listener and ECX Transaction Agent Listener, and a Java agent
listener named Web Services IN Agent. See: Oracle XML Gateway User's Guide.
You can optionally create additional agent listener service components. For example, you can
configure agent listeners for other inbound agents that you want to use for event message
propagation, such as the standard WF_IN and WF_JMS_IN agents, or any custom agents. You
can also configure an agent listener service component that only processes messages on a
particular agent that are instances of a specific event.

Step 5 Scheduling Propagation
Scheduling Propagation
If you want to use the standard WF_OUT and WF_JMS_OUT agents or custom agents for
event message propagation, ensure that you schedule propagation for those agents.

For information about using Oracle Enterprise Manager to schedule AQ propagation, refer to
Oracle Enterprise Manager Support, Oracle Application Developer’s Guide – Advanced
Queuing and Distributed Management, Oracle Enterprise Manager Administrator’s Guide.

Propagation Schedule Parameters
• queue_name: The queue associated with the local outbound agent for which you want to
schedule propagation. Specify the queue name prefaced by the schema that owns the queue,
in the following format: <schema>.<queue>
- In Oracle E-Business Suite, the standard Workflow queues are usually owned by the
APPLSYS schema.
- In standalone Oracle Workflow, the standard Workflow queues are usually owned by
the OWF_MGR schema.
• destination: The database link to the remote system to which you want to propagate
messages. To propagate messages to another queue on the local system, enter the
destination NULL. The default value is NULL.
• start_time: The initial start time for the propagation window.
• duration: The duration of the propagation window, in seconds
• next_time: A date function to compute the start of the next propagation window from the
end of the current window. For example, to start the window at the same time every day,

next_time should be specified as 'SYSDATE + 1 - duration/86400'. If this value is NULL,
then propagation is stopped at the end of the current window and is not run repeatedly. The
default value is NULL.
• latency: A latency time in seconds to specify how long you want to wait, after all messages
have been propagated, before rechecking the queue for new messages to the destination.
The latency represents the maximum wait time during the propagation window for a
message to be propagated after it is enqueued. To propagate messages as soon as possible
after they are enqueued, enter a latency of zero. The default latency is 60 seconds.
Refer to Guided Demonstration – Scheduling Agent Listeners and Propagation
[LAB23BBY]

Step 5 Synchronizing License Statuses in Oracle E-Business
Suite
Synchronizing License Statuses

This step is required only for Oracle E-Business Suite. You can use the License Manager AD
utility to review which products you currently have licensed. See: License Manager, Oracle
Applications AD Utilities Reference Guide.
Use the Submit Requests form in Oracle Applications to submit the Synchronize Product
License and Workflow BES License concurrent program (FNDWFLIC). This program does
not require any parameters. See: Submitting a Request, Oracle Applications User’s Guide.
If you upgrade from an Oracle E-Business Suite release earlier than Release 11.5.9, you should
run the Synchronize Product License and Workflow BES License concurrent program once
after the upgrade to update the license status of the existing events and subscriptions in your
Event Manager. Otherwise, subscriptions may not be correctly processed after the upgrade.
Subsequently, when you license a product, Oracle Workflow automatically updates the license
status for all the events and subscriptions owned by that product.
Note: Any events and subscriptions that you define with a customization level of User are
always treated as being licensed.

Step 5 Cleaning Up the WF_CONTROL Queue
Cleaning Up the WF_CONTROL Queue

The WF_CONTROL agent is used for internal processing only. You should not place custom
event messages on this queue.You do not need to schedule propagation for the
WF_CONTROL agent, because the middle tier processes that use WF_CONTROL dequeue
messages directly from its queue. However, this queue should be cleaned up periodically.
When a middle tier process for Oracle E-Business Suite or for standalone Oracle Workflow
starts up, it creates a JMS subscriber to the WF_CONTROL queue. If a middle tier process
dies, however, the corresponding subscriber remains in the database. For more efficient
processing, you should ensure that WF_CONTROL is periodically cleaned up by removing the
subscribers for any middle tier processes that are no longer active. The recommended
frequency for performing cleanup is every twelve hours.
• In Oracle E-Business Suite, use Oracle Workflow Manager to manage the Workflow
Control Queue Cleanup (FNDWFBES_CONTROL_QUEUE_CLEANUP) concurrent
program, which uses the WF_BES_CLEANUP.Cleanup_Subscribers() API to perform the
necessary cleanup. This concurrent program is scheduled to run every twelve hours by
default. The program does not require any parameters.

• In standalone Oracle Workflow, use Oracle Workflow Manager to submit a control queue
cleanup database job that runs the WF_BES_CLEANUP.Cleanup_Subscribers() API to
perform the necessary cleanup.

Optional Setup Steps
Optional Setup Steps

1. Partition certain Workflow tables for performance gain.
2. If you are using standalone Oracle Workflow, synchronize the user information in your
Workflow directory service with Oracle Internet Directory and implement single sign-on
integration.
3. Set up additional languages if you want to use Oracle Workflow in languages other than
English.
4. Set up one or more notification mailers if you want to allow your users to receive
notifications by e-mail.
5. Customize the templates for your e-mail notifications.
6. If you are using Oracle E-Business Suite, you can give users access to the Advanced
Worklist and Personal Worklist Web pages from any responsibility you choose.
7. If you are using Oracle E-Business Suite, you can use the WF: Notification Reassign Mode
profile option to control which reassign modes are available to users from the Notification
Details page.

8. If you are using Oracle E-Business Suite, you can control the item types for which users
can define vacation rules, using the WF: Routing Rule Item Types lookup type and the WF:
Vacation Rules – Allow All profile option.
9. If you are using Oracle E-Business Suite, you can set up users to enable electronic
signatures in notification responses.
10. Customize the company logo that appears in Oracle Workflow’s Web pages.
11. Include additional icons in your Oracle Workflow icons subdirectory to customize the
diagrammatic representation of your workflow processes.
12. Start the Java Function Activity Agent if you are using the standalone version of Oracle
Workflow and you want to run external Java function activities.

Optional Step 1 Partitioning Workflow Tables
Partitioning Workflow Tables

The wfupartb.sql and wfupart.sql scripts partition the following tables:
• WF_ITEM_ACTIVITY_STATUSES
• WF_ITEM_ACTIVITY_STATUSES_H
• WF_ITEM_ATTRIBUTE_VALUES
• WF_ITEMS
The scripts recreate the following indexes:
• WF_ITEM_ACTIVITY_STATUSES_PK
• WF_ITEM_ACTIVITY_STATUSES_N1
• WF_ITEM_ACTIVITY_STATUSES_N2
• WF_ITEM_ACTIVITY_STATUSES_H_N1
• WF_ITEM_ACTIVITY_STATUSES_H_N2
• WF_ITEM_ATTRIBUTE_VALUES_PK
• WF_ITEMS_PK
• WF_ITEMS_N1

• WF_ITEMS_N2
• WF_ITEMS_N3

Optional Step 2 Synchronizing with Oracle Internet Directory
Synchronizing with Oracle Internet Directory

At the end of the standalone Oracle Workflow installation, if you choose to implement Oracle
Internet Directory integration, the Workflow Configuration Assistant runs the
WF_LDAP.Synch_all API. This function retrieves all the existing user information from
Oracle Internet Directory, based on the LDAP directory information specified in the global
Workflow preferences. The user information is then loaded into the WF_LOCAL_ROLES
table.
Subsequently, you must maintain the synchronization between your Workflow directory
service and Oracle Internet Directory by retrieving and loading only changed Oracle Internet
Directory user information. It is recommended that you update the user information every ten
minutes. You can use either WF_LDAP.Synch_changes or WF_LDAP.Schedule_changes to
retrieve changed user information from Oracle Internet Directory. WF_LDAP.Synch_changes
identifies and retrieves LDAP user changes in Oracle Internet Directory, including creation,
modification, and deletion, by querying the LDAP change log records. The changed user
information is then loaded into the WF_LOCAL_ROLES table.
You can use WF_LDAP.Synch_changes to perform a single update. To continue updating user
information periodically, use WF_LDAP.Schedule_changes. This procedure submits a
database job using the DBMS_JOB utility to run WF_LDAP.Synch_changes repeatedly at an

interval that you specify. The default interval, which is also the recommended frequency to
check for updates, is ten minutes.

Optional Step 3 Setting Up Additional Languages
Setting Up Additional Languages

Note: You can only display languages that require a multibyte character set if your database
uses a character set that supports these languages, such as UTF8.
Displaying Oracle Workflow Web Pages in Other Languages
• For Oracle Workflow embedded in Oracle E-Business Suite, you select and install
additional languages as part of the Oracle E-Business Suite installation. Users can set their
language preference to an installed language through the Personal Homepage.
• For standalone Oracle Workflow, the server installation and upgrade are available only in
English. To support access to Oracle Workflow Web pages in another language, you must
load that language after the installation using the Oracle Workflow Configuration
Assistant. See the installation documentation for your release and platform. If you have
multiple languages loaded for Oracle Workflow, as a workflow administrator, you can
specify the default language that your users’ Web sessions display by setting the Language
preference in the Global Workflow Preferences page. Individual users can override the
default language by setting the Language preference in the User Preferences Web page.
Creating and Viewing Workflow Definitions in Other Languages using Oracle Workflow
Builder

• Set the NLS_LANG environment variable for the new language, territory, and encoded
character set that you want to use for the workflow definition. Specify the value for
NLS_LANG in the following format: LANGUAGE_TERRITORY.CHARSET Use the
Registry Editor on your PC to set the NLS_LANG environment variable:
- Choose Run from the Start menu on your PC.
- Enter the command to run the Registry Editor and choose OK. The command depends
on your version of Windows; for example, it may be regedit or regedit32.
- Drill down to My Computer > HKEY_LOCAL_MACHINE > Software > Oracle, and
then to the Oracle home where the Workflow Builder is installed.
- Select the NLS_LANG variable and choose Modify from the Edit menu.
- Enter the value you want and choose OK.
- Exit the Registry Editor.
• Start Oracle Workflow Builder. Create a translated version of your workflow definition and
save it as a flat file (.wft), or open and view a workflow definition that is already translated.
Loading Workflow Definitions in Other Languages to a Database
• Ensure that the language you want is set up in the database.
- For Oracle E-Business Suite, you select and install additional languages as part of the
Oracle E-Business Suite installation.
- For standalone Oracle Workflow, use the Workflow Configuration Assistant to select
and install additional languages.
• Before running the Workflow Definitions Loader program to load a translated workflow
definition to your database, you must set the NLS_LANG environment variable to the
appropriate territory and character set for the workflow definition you want to load. The
character set must match the character set encoding used to create the workflow definition
file, which is determined by the NLS_LANG value that was set on the client PC before
the .wft file was created in the Workflow Builder. To set NLS_LANG before running the
Workflow Definitions Loader, use the following format: _TERRITORY.CHARSET
Note that it is important to include the underscore (_) before the territory name and the
period (.) between the territory name and the character set name in the NLS_LANG value.
You do not need to include the language in this NLS_LANG value because the Workflow
Definitions Loader uses the language specified within the .wft file to determine the
language to load.
• Before using the Workflow Builder to save a translated workflow definition to your
database, you must set the NLS_LANG environment variable to the appropriate language,
territory, and character set. If you are saving several workflow definitions in different
languages, you must reset NLS_LANG for each language.
Sending E-mail Notifications in Other Languages
• Determine whether Oracle has translated the e-mail notification templates to the language
you wish to set by checking for the file containing the templates in the appropriate
language subdirectory, $ORACLE_HOME/wf/res/<lang> for the standalone version of
Oracle Workflow or $FND_TOP/import/<lang> for the version of Oracle Workflow
embedded in Oracle E-Business Suite. The standard templates are delivered in a file called
wfmail.wft.

• If the e-mail templates are available for the desired language, Oracle Workflow uses the
language preference for the notification recipient to determine the language for an e-mail
notification.

Optional Step 4 Implementing Notification Mailers


Implementing Notification Mailers

Users can receive e-mail notifications using various e-mail clients, although notifications may
be displayed differently in different clients, depending on the features each client supports.
Oracle Workflow fully supports Multi-purpose Internet Mail Extensions (MIME) encoded
messages. This means that a notification mailer can exchange messages with workflow users
containing languages with different character sets and multimedia encoded content.

Optional Step 5 Customizing Message Templates
Customizing Message Templates

Message templates are defined in the System: Mailer item type, stored in a file named
wfmail.wft. It is not recommended to modify the standard templates. However, you can choose
to use the alternative templates provided by Oracle Workflow instead of the default templates,
or you can also create your own custom templates in the System: Mailer item type. For more
information, refer to the Setting Up Oracle Workflow chapter in the Oracle Workflow
Administrator’s Guide.
You can implement alternative standard or custom templates in the following ways:
• Assign the templates you want to a particular notification mailer service component in the
mailer configuration parameters. The templates assigned to a mailer override the default
System: Mailer templates.
• Assign the templates you want to a particular notification in a workflow process by
defining special message attributes. In this case the templates assigned to the notification
override both the templates assigned to a mailer and the default System: Mailer templates.

Optional Step 5 Customizing Message Templates
Customizing Message Templates

The following standard message templates are used by default. An asterisk (*) marks the
templates for which Oracle Workflow also provides an alternative version.
• * Open Mail (Templated): For notifications that require a response when you are using the
templated response method
• * Open Mail (Direct): For notifications that require a response when you are using the
direct response method
• * Open Mail for Outlook Express: For notifications that require a response, if you use an e-
mail application such as Microsoft Outlook Express as your e-mail client
• * Open FYI Mail: For notifications that do not require a response
• View From UI: For response-required notifications whose content you do not want to send
in e-mail
• View FYI From UI: For notifications that do not require a response, whose content you do
not want to send in e-mail
• URL Attachment: Creates the Notification References attachment for HTML-formatted
notification messages that include URL attributes with Attach Content checked

• * Canceled Mail: Informs the recipient that a notification is canceled
• * Invalid Mail: Informs the recipient that the response to the notification is invalid
• * Closed Mail: Informs the recipient that a previously sent notification is now closed
• Summary Mail: For notification summaries in standalone Oracle Workflow
• Summary Mail (HTML): For notification summaries in Oracle E-Business Suite
• Warning Mail: Informs the recipient of unsolicited mail that he or she sent
• Signature Required Mail: For notifications that require an electronic signature in the user’s
response; users must respond to such notifications through the Notification Details Web
page rather than by e-mail
• Signature Warning Mail: Informs the recipient that an e-mail notification response was not
valid because the notification required an electronic signature to be entered through the
Notification Details Web page
• Secure Mail Content: For notifications that include sensitive content that cannot be sent in
e-mail for security reasons; users must view and respond to such notifications through the
Notification Details Web page rather than by e-mail
• * Open Mail (More Information Request): For requests for more information about a
notification from one user to another user
• Open Mail (More Information Request for Outlook Express): For requests for more
information about a notification from one user to another user, if you use an e-mail
application such as Microsoft Outlook Express as your e-mail client
• Invalid Open Mail (More Information Request): Informs the recipient that the response to a
request for more information is invalid

Optional Step 6 Adding Worklist Functions to User
Responsibilities
Adding Worklist Functions to User Responsibilities

Add the following functions to the responsibilities from which you want users to access the
corresponding pages:
• Advanced Worklist: WF_WORKLIST
• Personal Worklist: WF_WORKLIST_CUSTOM
The Advanced Worklist is seeded on the menu for the Workflow User Web Applications
responsibility by default. You can also add the Advanced Workflow Worklist function to other
responsibilities from which you want users to access notifications.
The Personal Worklist is an optional feature that is not seeded on any Oracle E-Business Suite
menu. If you want users to access this version of the Worklist, you must first add the Personal
Worklist function to the menu for a responsibility assigned to those users.

Optional Step 7 Setting the Notification Reassign Mode
Setting the Notification Reassign Mode

The WF: Notification Reassign Mode profile option is available only in Oracle E-Business
Suite. This profile option controls the reassign modes available to users from the Advanced
Worklist, the Personal Worklist, and the Response section of the Notification Details page.
• Delegate – This mode lets users give another user authority to respond to a notification on
their behalf, while still retaining ownership of the notification themselves. For example, a
manager might delegate all vacation scheduling approvals to an assistant.
• Transfer – This mode lets users give another user complete ownership of and responsibility
for a notification. For example, users might select this option if they should not have
received a certain notification and they want to send it to the correct recipient or to another
recipient for resolution. A transfer may have the effect of changing the approval hierarchy
for the notification. For example, a manager might transfer a notification about a certain
project to another manager who now owns that project.
• Reassign – This setting provides users access to both the Delegate and Transfer reassign
modes. The Reassign setting is the default value for the WF: Notification Reassign Mode
profile option.

Optional Step 8 Setting Up Vacation Rule Options
Setting Up Vacation Rule Options

Adding Item Types for Vacation Rules
• By default, the list of item types a user can select when creating a vacation rule displays
those item types for which the user has previously received at least one notification. You
can also choose to add item types that you want to appear in the list for all users. In this
way you can allow users to create rules to handle any notifications they may receive from
those item types in the future.
• To add an item type to the list, define the internal name of the item type as a lookup code
for the WF: Routing Rule Item Types lookup type.
- Navigate to the Application Object Library Lookups window in the Application
Developer responsibility.
- Query the WF_RR_ITEM_TYPES lookup type with the meaning WF: Routing Rule
Item Types in the Application Object Library application.
- Define the item type you want as a new lookup code for this lookup type. Ensure that
you enter the item type internal name in the Code field exactly as the name is defined in
your database.
Allowing Vacation Rules that Apply to All Item Types

• Use the WF: Vacation Rules – Allow All profile option to determine whether the list of
item types for vacation rules includes the ”All” option. The ”All” option lets users create a
generic rule that applies to notifications associated with any item type.
- Enabled - The ”All” option appears in the list of item types for vacation rules. This is
the default value.
- Disabled – Users must always specify the item type to which a vacation rule applies.
• After changing the value of this profile option, you must stop and restart Oracle HTTP
Server for the change to take effect.

Optional Step 9 Setting Up for Electronic Signatures
Setting Up for Electronic Signatures

Electronic signatures are supported in Oracle E-Business Suite only.
Implementing Password-based Signatures with Single Sign-On
Oracle Workflow supports password-based signatures for notifications based on Oracle
Application Object Library (FND) passwords. If you maintain your directory service based on
Oracle Application Object Library users and passwords, no additional setup is required.
However, if you implement single sign-on for your site through Oracle Internet Directory, you
must perform the following steps.
• Set the Applications SSO Login Types profile option to either Local or Both at user level
for all users who need to enter password-based signatures.
• Ensure that these users have valid passwords defined in Oracle Application Object Library.
For more information, see: Integrating Oracle E–Business Suite Release 11i with Oracle
Internet Directory and Oracle Single Sign-On (OracleMetaLink note 261914.1).
Loading Certificates for Digital Signatures
• Before users can sign responses with their X.509 certificates, you must load these
certificates into your Oracle E-Business Suite database using the Workflow Certificate
Loader. When you load a certificate, you must also specify the Oracle Applications user to

whom that certificate is assigned. Oracle Workflow uses this information to validate that
the user attempting to sign with a certain certificate is the same user to whom that
certificate is assigned.
• A user can have more than one certificate assigned to him or her. However, each certificate
can only be assigned to one user. Additionally, after you have loaded a certificate for a
user, you cannot delete it from the database or assign it to a different user. If a certificate is
incorrectly assigned, the user to whom it belongs must revoke it and obtain a new
certificate instead.
• You must load a user’s personal certificate, the root certificate of the certificate authority
that issued the personal certificate, and any intermediate certificates required for this type
of personal certificate.
• Run the loader by running Java against
oracle.apps.fnd.wf.DigitalSignature.loader.CertificateLoader. You can load several
certificates at once by listing the information for all the certificates in a data file for the
loader. You can also load a single certificate by specifying the certificate information in the
command line for the loader.
Note: Oracle Workflow does not provide a framework for certificate provisioning. Oracle
Workflow’s digital signature support assumes that certificate provisioning is already part of
your infrastructure.

Optional Step 10 Customizing the Workflow Web Page Logo
Customizing the Workflow Web Page Logo

Note: /OA_MEDIA/ is a virtual directory mapping defined in your Web server when Oracle
Workflow is installed.

Optional Step 11 Adding Custom Icons
Adding Custom Icons

If you create custom icons to include in your Oracle Workflow Builder process definition, and
you want the custom icons to appear in the Workflow Monitor when you view the process, you
must do the following:
1. Convert the custom icon files (.ico) to gif format (.gif).
2. Copy the .gif files to the physical directory associated with your Web server’s
/OA_MEDIA/ virtual directory, so that the Workflow Monitor can access them.
Note: /OA_MEDIA/ is a virtual directory mapping defined in your Web server when Oracle
Workflow is installed.

Optional Step 12 Starting the Java Function Activity Agent
Starting the Java Function Activity Agent

To run the Java Function Activity Agent, you must have Java Development Kit (JDK) Version
1.4 installed.
Note: The Java Function Activity Agent is currently only available for standalone Oracle
Workflow. This functionality is not currently available for Oracle E-Business Suite.
Starting the Java Function Activity Agent From a Script
The scripts to start the Java Function Activity agent are called wfjvlsnr.csh, for UNIX, and
wfjvlsnr.bat, for Windows, and are located on your server in the ORACLE_HOME/wf/admin
directory. If you define your own external Java function activities, you must include the path to
the JAR files containing your custom Java classes in the scripts. Then you can run the scripts
with your Oracle Workflow database account and the database connect string to submit the
Java Function Activity Agent.
Starting the Java Function Activity Agent Manually
To start the Java Function Activity Agent manually, run JRE against
'oracle.apps.fnd.wf.WFFALsnr', specifying your CLASSPATH, the user name of your Oracle
Workflow database account, and the database connect string. The CLASSPATH must point to

the Java Runtime Environment, the directory containing the Workflow JAR files, the Oracle
XML parser, the Oracle JDBC implementation, and the following Workflow JAR files:
• wfjava.jar - The Java Function Activity Agent
• wfapi.jar - Workflow Java APIs
• The Share JAR file - Utilities referenced by the Workflow Java APIs
• The Ewt JAR file - Utilities referenced by the Workflow Java APIs
• The Swing JAR file - Optional additional utilities
• fndctx.jar - Utilities referenced by the Workflow Java APIs
If you define your own external Java function activities, you must also include the JAR files
containing your custom Java classes in the CLASSPATH.
Stopping the Java Function Activity Agent
Normally, the Java Function Activity Agent runs as a perpetual job. However, you can stop the
agent by running a script called wfjvstop.sql, located in the ORACLE_HOME/wf/admin/sql
directory on your Oracle Workflow server.

Version Compatibility

Review Questions

Review Questions
Review Questions and Solutions

1. What are the required setup steps for Oracle Workflow?
• Set your global workflow preferences.
• Ensure that your directory service is set up.
• Define an environment variable called WF_RESOURCES (standalone Oracle
Workflow on a UNIX platform only).
• Set up background engines.
• Configure the Business Event System for event communication.
2. What are the optional setup steps for Oracle Workflow?
• Partition Workflow tables for performance gain.
• Integrate your directory service with Oracle Internet Directory and single sign-on
(standalone Oracle Workflow only).
• Set up additional languages.
• Set up notification mailers.
• Customize the templates for your e-mail notifications.

• Add the Advanced Worklist or Personal Worklist to users’ responsibilities (Oracle E-
Business Suite only).
• Set the WF: Notification Reassign Mode profile option (Oracle E-Business Suite only).
• Control the item types for which users can define vacation rules (Oracle E-Business
Suite only).
• Set up users to enable electronic signatures in notification responses (Oracle E-
Business Suite only).
• Customize the company logo that appears in Oracle Workflow’s Web pages.
• Include custom icons in your Oracle Workflow icons subdirectory.
• Start the Java Function Activity Agent (standalone Oracle Workflow only).

Summary


Setting Up Oracle Workflow

Uploaded by

Copyright:

Available Formats

Setting Up Oracle Workflow

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Setting Up Oracle Workflow

Uploaded by

Copyright:

Available Formats

Setting Up Oracle Workflow

Copyright © Oracle Corporation, 2004. All rights reserved.