Previous	Next		Contents	Index	Glossary

How can I verify my Oracle Workflow installation?

How can I manually set the Oracle Workflow Web agent?

sqlplus <username>/<pwd> @wftoken WF_WEB_AGENT <web_agent_value>

Replace <web_agent_value> with the Oracle Workflow web agent name in the following format:

http://<host:portID>/pls/wf

where <host:portID> represents the host server and TCP/IP port number on which your Web listener accepts requests and wf is the default Database Access Descriptor (DAD) created during the Oracle Workflow middle tier installation.

How can I verify the Oracle Workflow virtual directory mappings?

• Oracle Workflow requires a virtual directory mapping called /OA_JAVA/ in your Web listener that points to the Oracle Workflow JAR files on your file system. The JAR files are in a directory called ORACLE_HOME/jlib. The Oracle Universal Installer automatically installs the Java code in this directory when you install or upgrade the Oracle Workflow middle tier components.

• Oracle Workflow requires a virtual directory mapping called /OA_MEDIA/ that points to the Oracle Workflow icon area on your file system. The icon area is ORACLE_HOME/wf/java/oracle/apps/fnd/wf/icons/, within your middle tier Oracle home. All icon and gif files that are required by the Oracle Workflow Web interface must be stored in the /OA_MEDIA/ virtual directory.

• Oracle Workflow requires a virtual directory mapping called /OA_DOC/ that points to the Oracle Workflow documentation area on your file system. The documentation area is ORACLE_HOME/wf/doc. This area contains the context-sensitive HTML help files for Oracle Workflow Web pages.

• On UNIX:

Alias /OA_JAVA/ "$ORACLE_HOME/jlib/"

Alias /OA_MEDIA/ "$ORACLE_HOME/wf/java/oracle/apps/fnd/wf/icons/"

Alias /OA_DOC/ "$ORACLE_HOME/wf/doc/"

For example:

...

#

# Aliases: Add here as many aliases as you need (with no limit). 

# The format is

# Alias fakename realname

#

...

Alias /OA_JAVA/ "/oracleas/jlib/"

Alias /OA_MEDIA/ "/oracleas/wf/java/oracle/apps/fnd/wf/icons/"

Alias /OA_DOC/ "/oracleas/wf/doc/"

...

• On Windows:

Alias /OA_JAVA/ "ORACLE_HOME\jlib/"

Alias /OA_MEDIA/ "ORACLE_HOME\wf\java\oracle\apps\fnd\wf\icons/"

Alias /OA_DOC/ "ORACLE_HOME\wf\doc/"

For example:

...

#

# Aliases: Add here as many aliases as you need (with no limit). 

# The format is

# Alias fakename realname

#

...

Alias /OA_JAVA/ "C:\oracleas\jlib/"

Alias /OA_MEDIA/ "C:\oracleas\wf\java\oracle\apps\fnd\wf\icons/"

Alias /OA_DOC/ "C:\oracleas\wf\doc/"

...

Ensure that you add a trailing slash to each alias name and physical directory path. After adding the aliases, restart Oracle HTTP Server.

How can I ensure that icons appear on Oracle Workflow pages?

How can I access the online help for Oracle Workflow pages?

You can now view the HTML help using a Web browser. Choose the Help button on any Oracle Workflow Web page to access the HTML help. You can also access any HTML help file directly by appending its virtual path to your Web listener base URL. The path for the contents page of the Oracle Workflow help is:

http://host:portID/OA_DOC/lang/wf/toc.htm

If you want to add custom help, you can replace the ORACLE_HOME/wf/doc/lang/wfcust/wfcust.htm placeholder file with your own help material. The HTM file that is the main entry point for your custom help must be named wfcust.htm and must contain an anchor named contents. Your custom help will be accessible through the Custom Help link on the contents page of the Oracle Workflow help, or you can access your custom help directly through the following path:

http://host:portID/OA_DOC/lang/wfcust/wfcust.htm

You can also view context-sensitive help for the Oracle Workflow Builder in Winhelp format by choosing Contents from the Help menu within the Oracle Workflow Builder.

How can I change Oracle Workflow configuration parameters after installation?

You can update the configuration parameters for the Workflow Notification Mailer using the notification mailer configuration wizard in Oracle Workflow Manager. If you installed Oracle Workflow along with Oracle Application Server, access Oracle Workflow Manager from the Oracle Enterprise Manager Application Server Control. If you installed Oracle Workflow along with Oracle Database, access Oracle Workflow Manager as part of the Oracle Enterprise Manager Database Control. For more information, see the Oracle Workflow Manager online help.

How can I access existing user information after integrating with Oracle Internet Directory?

Oracle Internet Directory provides a migration tool called ldifmigrator. To use this tool, you must extract your user information from the database into an intermediate LDAP Data Interchange Format (LDIF) file, with substitution variables wherever necessary. The ldifmigrator tool converts the intermediate entries in the file to actual LDIF entries by replacing the variables based on arguments provided at runtime or information retrieved from the LDAP directory. The LDIF file produced by the ldifmigrator can then be uploaded into Oracle Internet Directory using Oracle Internet Directory bulk tools.

For more information about the ldifmigrator, the format required for the intermediate LDIF file, and Oracle Internet Directory bulk upload tools, see: Appendix A: Syntax for LDIF and Command-Line Tools, Oracle Internet Directory Administrator's Guide.

How can I load the DBMS_LDAP package?

sqlplus "SYS/<SYS password> as sysdba" @$ORACLE_HOME/rdbms/admin/catldap.sql

After loading DBMS_LDAP, recompile the Oracle Workflow schema. See: Oracle Database Supplied PL/SQL Packages and Types Reference.

How can I give database users access to the Oracle Workflow Web pages?

How can I change my directory service implementation after installation?

   To convert from Oracle Database users to Oracle Internet Directory:

1. Ensure that the DBMS_LDAP PL/SQL package is loaded in your database. This package contains the functions and procedures that can be used to access data from LDAP servers and is required for LDAP synchronization. To check whether the DBMS_LDAP package is already installed, connect to SQL*Plus and use the following command:

	desc DBMS_LDAP

If the DBMS_LDAP package does not already exist, load it manually by running the catldap.sql script located in the <ORACLE_HOME>/rdbms/admin directory. Run this script as the SYS user. For example, use the following command:

	sqlplus "SYS/<SYS password> as sysdba" 

	@$ORACLE_HOME/rdbms/admin/catldap.sql

2. Run the <ORACLE_HOME>/wf/sql/wfdircsv.sql script to implement Oracle Workflow directory service views that support OID integration. For example, use the following command:

	sqlplus owf_mgr/<passwd> @$ORACLE_HOME/wf/sql/wfdircsv.sql

3. Load the appropriate version of the WFA_SEC package, which contains Oracle Workflow security functions and procedures. To load this package, log on to SQL*Plus as the Oracle Workflow database user and run the <ORACLE_HOME>/wf/sql/wfsecssb.sql script. For example, use the following command:

 	sqlplus owf_mgr/<passwd> @$ORACLE_HOME/wf/sql/wfsecssb.sql

4. Update the Database Access Descriptor (DAD) for Oracle Workflow in the Oracle HTTP Server dads.conf file, specifying the following parameters. You can either use Oracle Enterprise Manager to update the DAD or edit the dads.conf file directly. The DAD should be named /pls/your_Workflow_DAD. For example: /pls/wf

• PlsqlDatabaseUsername - Oracle Workflow schema

• PlsqlDatabasePassword - Oracle Workflow schema password

• PlsqlDatabaseConnectString - Database connect string

• PlsqlDefaultPage - wfa_html.home

• PlsqlSessionStateManagement - StatelessWithResetPackageState

• PlsqlAuthenticationMode - Basic

5. Protect the Oracle Workflow DAD by adding the following entry in your mod_osso configuration file. Replace your_Workflow_DAD with the name of your DAD.

	<Location /pls/your_Workflow_DAD>

	   require valid-user

	   authType Basic

	</Location>

For more information, see: Developing Applications Using mod_osso, Oracle Identity Management Application Developer's Guide.

After you update the DAD and the mod_osso configuration file, restart Oracle HTTP Server.

6. Set the following LDAP preferences in the Global Workflow Preferences page. See: To Set Global Preferences for Standalone Oracle Workflow.

• LDAP Host

• LDAP Port

• LDAP User Name

• LDAP Password

• LDAP Changelog Base Directory

• LDAP User Base Directory

7. Migrate your existing Workflow user information to Oracle Internet Directory. See: How can I access existing user information after integrating with Oracle Internet Directory?.

8. Perform an initial synchronization of your Oracle Workflow directory service with OID by running the WF_LDAP.Synch_all( ) API. Because Synch_all( ) retrieves information for all users stored in OID, you should use this function only once during setup. If necessary, however, you can also run Synch_all( ) as required for recovery or cleanup.

Use the following commands to run Synch_all( ):

	declare

	  res boolean := FALSE;

	begin



	  res := wf_ldap.synch_all();

	  if (res) then

	    dbms_output.put_line('succeeded');

	  else

	    dbms_output.put_line('failed ');

	  end if;

	end;

	/

9. Use the WF_LDAP.Schedule_Changes API to periodically synchronize your Oracle Workflow directory service with OID. See: Synchronizing Workflow Directory Services with Oracle Internet Directory.

   To convert from Oracle Internet Directory to Oracle Database users:

1. Stop any database jobs you have scheduled to execute the WF_LDAP APIs to synchronize your Oracle Workflow directory service with OID. See: Synchronizing Workflow Directory Services with Oracle Internet Directory.

2. Update the Database Access Descriptor (DAD) for Oracle Workflow in the Oracle HTTP Server dads.conf file, specifying the following parameters. You can either use Oracle Enterprise Manager to update the DAD or edit the dads.conf file directly. The DAD should be named /pls/your_Workflow_DAD. For example: /pls/wf

• PlsqlDatabaseConnectString - Database connect string

• PlsqlDefaultPage - wfa_html.home

• PlsqlSessionStateManagement - StatelessWithResetPackageState

• PlsqlAuthenticationMode - Basic

Ensure that you do not specify a database user name or password, in order to enable mod_plsql database authentication.

3. Delete the entry for your Workflow DAD from the mod_osso configuration file.

After you update the DAD and the mod_osso configuration file, restart Oracle HTTP Server.

4. Run the <ORACLE_HOME>/wf/sql/wfdirouv.sql script to map the Oracle Workflow directory service views to your Oracle Database users and roles. For example, use the following command:

 	sqlplus owf_mgr/<passwd> @$ORACLE_HOME/wf/sql/wfdirouv.sql

The wfdirouv.sql script sets each native Oracle Database user's e-mail address to the user's respective username. As a minimal setup step, you should edit the script to either link your native Oracle Database 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. See: Integrating Oracle Workflow Directory Services with Oracle Database Users,

5. Load the appropriate version of the WFA_SEC package, which contains Oracle Workflow security functions and procedures. To load this package, log on to SQL*Plus as the Oracle Workflow database user and run the <ORACLE_HOME>/wf/sql/wfsecwsb.sql script. For example, use the following command:

	sqlplus owf_mgr/<passwd> @$ORACLE_HOME/wf/sql/wfsecwsb.sql

6. Clear the following LDAP preferences in the Global Workflow Preferences page. See: To Set Global Preferences for Standalone Oracle Workflow.

• LDAP Host

• LDAP Port

• LDAP User Name

• LDAP Password

• LDAP Changelog Base Directory

• LDAP User Base Directory

How can I access the Oracle Workflow demonstration users?

For security reasons, the installation process automatically locks the demonstration user accounts after they are created. Before you can begin using the accounts, you must unlock them using a script called wfdemoul.sql. This script is located in the ORACLE_HOME/wf/demo directory. Connect to the SYSTEM database account using SQL*Plus and run the script using the following command:

sqlplus SYSTEM/<SYSTEM pwd> @wfdemoul

See your Oracle DBA if you need more information about the SYSTEM account and password.

• If you are using Oracle Database users and roles as your directory repository, then the Workflow installation creates the demonstration users as database accounts. In this case you can authenticate yourself with a demonstration database username and password to access Oracle Workflow Web pages.

• If you chose to integrate with Oracle Internet Directory as your directory repository by entering LDAP values in the Oracle Workflow Configuration Assistant, then the demonstration users are created as ad hoc users in the Workflow local directory service tables. In this case you must migrate the user information for the demonstration users to Oracle Internet Directory before you can access Oracle Workflow Web pages with these user names and passwords. See: How can I access existing user information after integrating with Oracle Internet Directory?.

How can I enable custom packages in the Oracle Workflow DAD?

How can I ensure that propagation is executed for Business Event System queues?

How can I manually register files for an Oracle Workflow client installation?

If you encounter this error, close the error message and proceed with the installation. After the installation is complete, register the specified file manually by running the following command from a DOS prompt:

regsvr32 path\filename  

Replace path with the path to the file and filename with the name of the file to register. The wfnvg.ocx file is normally located in the ORACLE_HOME\bin directory.

How can I modify the font in Oracle Workflow Builder?