Skip Headers

Oracle Application Server InterConnect Installation Guide
10g (9.0.4)
Part Number B10693-01
Go To Documentation Library
Home		 Go To Table Of Contents
Contents		 Go To Index
Index

Go to previous page Go to next page

3
Integrating Oracle Workflow with OracleAS InterConnect

This chapter describes how to integrate Oracle Workflow with OracleAS InterConnect.

Topics discussed are:

Overview

You can install Oracle Workflow to integrate with OracleAS InterConnect in the following two ways:

Installation Process

To install Oracle Workflow from an OracleAS ProcessConnect home, perform the following steps:

Step 1 Install OracleAS Metadata Repository

Install the OracleAS Metadata Repository in an existing 9.2 database using the Oracle Application Server Repository Creation Assistant (OracleAS RepCA). OracleAS Metadata Repository contains the Oracle Workflow schema.

See Also:

Oracle Application Server 10g Installation Guide

Step 2 Install OracleAS ProcessConnect

Install OracleAS ProcessConnect on the middle-tier, selecting the OracleAS Metadata Repository you installed in step 1 "Install OracleAS Metadata Repository" to use with this Oracle Application Server middle-tier. Oracle Workflow files are silently installed in the middle-tier Oracle home along with OracleAS ProcessConnect.

See Also:

Oracle Application Server ProcessConnect Installation Guide for installation procedures.

Step 3 Run Oracle Workflow Configuration Assistant

Run the Workflow Configuration Assistant to configure Oracle Workflow.

After Oracle Workflow is installed and configured, you can also optionally run the Workflow Configuration Assistant again with the Add Language option to load additional languages into your Oracle Workflow server database. To do so, perform the following steps:

  1. (Optional) If you want to configure the Java-based notification mailer service component called the Workflow Notification Mailer, add the following parameters to the wfinstall.csh script:

    • iasname: schema_name.machine_name

    • iasport: Database listener port

    • iassid: Database SID

    • iasmachine: Machine name

    • jdbcconnnode: Connection with remote database.

    • fileupdate: Updates file. This is required to configure the Java mailer.

    For example: 

    /iasname M21_MidTier.hsunnab05 /iasport 1521 /iassid Ora92 /iasmachine 
machine.us.oracle.com /jdbcconnnode machine.us.oracle.com:1521:Ora92  
/fileupdate true
  2. Start the Workflow Configuration Assistant.

    • UNIX: ORACLE_HOME/wf/install/wfinstall.csh

    • Windows: ORACLE_HOME\wf\install\wfinstall.bat

  3. In the Oracle Workflow Configuration Assistant window, enter the following user information:

  4. To integrate with Oracle Internet Directory (OID) and Oracle Application Server Single Sign-On as your directory repository for Oracle Workflow, select the Enter LDAP Parameters check box and choose Get LDAP Values.

    Note:

    If you are upgrading an existing installation of Oracle Workflow in which you already implemented OID integration, you must re-enter your LDAP values here to preserve the OID integration during the upgrade.

    Enter the following Lightweight Directory Access Protocol (LDAP) server information for the LDAP directory to which you want to connect. After the initial installation, you can update these values if necessary in the Global Workflow Preferences Web page.

    See Also:

    Oracle Workflow Administrator's Guide for information on setting up Oracle Workflow.

    • Host Name: Host on which your LDAP directory resides.

    • Port No.: Port of the host. This port must be a non-Secure Sockets Layer (non-SSL) port.

    • User Name: 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, for example, cn=orcladmin.

    • Old Password: Enter the password for the LDAP user account. LDAP password values are masked as asterisks in the display and are stored in encrypted form.

    • Log Base: LDAP node under which change logs are located. For example: cn=changelog.

    • User Base: LDAP node under which user records can be found. For example: cn=Base, cn=OracleSchemaVersion.

    Then click OK.

    If you enter values for these LDAP options, the Oracle Workflow Configuration Assistant automatically implements Oracle Workflow directory service views that support OID integration for you. Additionally, it installs the appropriate WFA_SEC Workflow security package. Finally, the Oracle Workflow Configuration Assistant also automatically sets up Oracle Application Server Single Sign-On integration for you by protecting the Database Access Descriptor (DAD) for Oracle Workflow in the mod_osso configuration file within your Oracle HTTP Server installation.

    Note:

    After setting up integration with OID during installation, you must use the WF_LDAP APIs to synchronize your Oracle Workflow directory service with OID. For instructions, refer to Oracle Workflow Administrator's Guide.

  5. If you do not want to integrate with OID, then leave the Enter LDAP Parameters check box blank. In this case directory service views that use Oracle database users and roles as your directory repository will be automatically implemented for you by default. 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.

    Note:

    When the Oracle Workflow Configuration Assistant implements the directory service views using Oracle database users and roles as your directory repository, it 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 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. The wfdirouv.sql script is located in the Oracle Workflow sql subdirectory within your ORACLE_HOME. For more information, refer to Oracle Workflow Administrator's Guide.

  6. To enter configuration parameters for the seeded Java-based notification mailer service component called the Workflow Notification Mailer, select the Enter Mailer Parameters check box and choose Get Mailer Values. Enter values for the following parameters:

    • Inbound Mail Server: Name of the inbound IMAP mail server.

    • IMAP User Name: User name of the mail account that the notification mailer uses to send and receive e-mail messages.

    • HTML Agent Name: Base URL that identifies the Web agent defined for Oracle Workflow in Oracle HTTP Server. Oracle Workflow uses this URL to display its Web pages. The notification mailer also uses this URL to support e-mail notifications with HTML attachments. The HTML agent should be specified in the following format: 

      http://<server.com:port>/pls/wf

      where <server.com:port> represents the server and TCP/IP port number on which your web listener accepts requests, and wf is the DAD created for Oracle Workflow.

      Note:

      You must always enter a value for the HTML Agent Name, because Oracle Workflow requires this URL to display its Web pages.

    • Outbound Host Name: Name of the outbound SMTP mail server.

    • Reply To: Address of the e-mail account that receives incoming messages, to which notification responses should be sent.

    Then choose OK.

    After the initial installation, you can update the notification mailer configuration values if necessary in the Oracle Workflow Manager component of the Oracle Enterprise Manager Application Server Control. You can also update the HTML agent value for Oracle Workflow in the Global Workflow preferences Web page.

    See Also:

    Oracle Workflow Administrator's Guide for information on Oracle Workflow Manager online help and setting up Oracle Workflow.

  7. To change the tablespace assigned to the Oracle Workflow database account, select the Change Tablespace check box. Then select an existing tablespace from the list of values.

  8. Choose Submit to begin the configuration. You can also choose Quit to exit the Workflow Configuration Assistant without performing the configuration.

  9. When the configuration is complete, a confirmation window appears. Choose OK.

Step 4 Verify Oracle Workflow Web Interface Virtual Directory Mappings (optional)

Note:

In some previous releases, it was necessary to add the virtual directory mappings for Oracle Workflow manually. In release 2.6.3, however, these virtual directory mappings are configured automatically. You should verify the default mappings and add or edit them, if necessary.

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. Oracle Universal Installer automatically installs the Java code in this directory when you install or upgrade the Oracle Workflow Server.

Oracle Workflow also 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. All icon and .gif files that are required by Oracle Workflow's Web interface must be stored in the /OA_MEDIA/ virtual directory.

If you installed Oracle HTTP Server in the same ORACLE_HOME as Oracle Workflow, the /OA_JAVA/ and /OA_MEDIA/ virtual directory mappings are set by default. You should verify these mappings and add them if necessary.

  1. To add the required virtual directory mappings in Oracle HTTP Server, add aliases for the jlib directory and the Oracle Workflow icon area to the ORACLE_HOME/wf/admin/wf.conf file. The path to this configuration file must be included in the ORACLE_HOME/Apache/Apache/conf/oracle_apache.conf file which helps define the behavior of Oracle HTTP Server. Add the aliases using the following format:

    On UNIX: 

    Alias /OA_JAVA/ "<ORACLE_HOME>/jlib/"
Alias /OA_MEDIA/ "<ORACLE_HOME>/wf/java/oracle/apps/fnd/wf/icons/"

    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/"
...

    On Windows: 

    Alias /OA_JAVA/ "<ORACLE_HOME>\jlib/"
Alias /OA_MEDIA/ "<ORACLE_HOME>\wf\java\oracle\apps\fnd\wf\icons/"

    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/"
...

    Note:

    Add a trailing slash to each alias name and physical directory path.

  2. Restart Oracle HTTP Server.

    See Also:

    Oracle HTTP Server Administrator's Guide

Step 5 Set Up Oracle Workflow HTML Help

Oracle Workflow provides access to HTML help from the Help button on each of its Web pages. The HTML help that appears is context-sensitive and provides links to the entire contents of the Oracle Workflow documentation.

When you install Oracle Workflow Server, Oracle Universal Installer copies a .zip file containing the HTML help to the Workflow directory in your Oracle home. The .zip file is ORACLE_HOME/wf/wfdoc.zip. To set up the HTML help, you must extract the doc directory tree from the .zip file and verify that you have a virtual directory mapping called /OA_DOC/ in your Web listener that points to the documentation area on your file system.

If you installed Oracle HTTP Server in the same ORACLE_HOME as Oracle Workflow, the /OA_DOC/ virtual directory mapping is set by default. You should verify this mapping and add it if necessary.

  1. Use an unzip utility to extract the doc directory tree from the .zip file within the Workflow directory. You need at least 7 Mb of free disk space to extract the .zip file.

    The doc directory tree that is created includes the Oracle Workflow documentation area, ORACLE_HOME/wf/doc, and the following subdirectories:
  2. After extracting the doc directory tree, you can optionally remove the .zip file.

  3. Verify that you have a virtual directory mapping called /OA_DOC/ in your Web listener that points to the new Oracle Workflow documentation area on your file system and add this mapping if necessary.

    • In Oracle HTTP Server, add an alias for the Oracle Workflow documentation area to the ORACLE_HOME/wf/admin/wf.conf file. The path to this configuration file must be included in the ORACLE_HOME/Apache/Apache/conf/oracle_apache.conf file which helps define the behavior of Oracle HTTP Server. Add the alias using the following format:

      On UNIX: 

      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_DOC/ "/oracleas/wf/doc/"
...

      On Windows: 

      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_DOC/ "C:\oracleas\wf\doc/"
...

      Note:

      Be sure to add a trailing slash to each alias name and physical directory path.

    • After adding the alias, restart Oracle HTTP Server.

  4. After the /OA_DOC/ virtual directory mapping is added to your Web listener, you can access the HTML help from the Help button on any Oracle Workflow Web page. 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 online help is: 
    http://<server_name>[:<port>]/OA_DOC/<lang>/wf/toc.htm

    The path for the contents page of your Oracle Workflow custom help is: 

    http://<server_name>[:<port>]/OA_DOC/<lang>/wfcust/wfcust.htm
  5. If you want to add custom help, you can replace the placeholder file in the wfcust directory, wfcust.htm, 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.

Step 6 Migrate Existing User Information to Oracle Internet Directory (optional)

If you are upgrading a previous installation of Oracle Workflow, and you are integrating with Oracle Internet Directory for the first time, migrate your existing Workflow user information to Oracle Internet Directory.

Note:

For a new installation of Oracle Workflow, you do not need to perform this step unless you want to access Oracle Workflow with the user names and passwords of the Workflow demonstration users. To enable access as the demonstration users when Oracle Workflow is integrated with OID, you must first migrate the seeded user information for these users to OID.

You must perform a one-time migration of existing Oracle Workflow user information to OID to enable single sign-on and single administration. Ensure that you migrate all the necessary data from WF_LOCAL_USERS as well as any other user tables in which you previously stored user information. After performing the migration, you should maintain your user information only through OID.

OID 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 OID using OID bulk tools.

See Also:

Oracle Internet Directory Administrator's Guide for more information about the ldifmigrator, the format required for the intermediate LDIF file, and OID bulk upload tools

Step 7 Access Oracle Workflow User Interface

To invoke Oracle Workflow's Web pages, append the appropriate procedure and arguments to the base URL for the Workflow Web agent. After you define your Web security and Web users, you can verify your base URL by connecting as a valid user to the Oracle Workflow home page: 

http://<server.com:port>/pls/your_Workflow_DAD/wfa_html.home

The default name for the Workflow DAD is wf.

Notes:

When you install Oracle Workflow and its demonstration workflow processes, you also install a demonstration data model that seeds a set of demonstration users in the directory service. The users are: sysadmin, wfadmin, blewis, cdouglas, kwalker, and spierson. Their passwords are the same as their usernames. You can authenticate your connection to an Oracle Workflow Web page with any of these user names and passwords. Public grants and synonyms were created so that these users have full access to Oracle Workflow's Web-based user interface.

Oracle Workflow also includes the Oracle Workflow Manager component in Oracle Enterprise Manager, which provides administrative and management tools for Oracle Workflow. If you ran the Workflow Configuration Assistant, after the Oracle Workflow installation and configuration are complete, you can access Oracle Workflow Manager from the Oracle Enterprise Manager Application Server Control.

Step 8 Complete Oracle Workflow Setup

Ensure that you complete all setup steps listed in the "Setting Up Oracle Workflow" chapter in the Oracle Workflow Administrator's Guide.

Step 9 Configure Oracle Workflow with OracleAS InterConnect

Use the following configuration steps to allow Oracle Workflow working with OracleAS InterConnect.

  1. Navigate to your Oracle Workflow home page. Under Global Workflow Preferences, check that the System Status is set to Enabled.

  2. Under Check Setup, listeners for local inbound agents, schedule listeners for Agents WF_IN and WF_ERROR. Setting the listener to run every 10 seconds is recommended. If you would like faster response times, schedule additional listeners rather than lowering the interval between runs.

    See Also:

    Oracle Workflow Administrator's Guide for details on scheduling listeners

  3. Under Event Subscriptions, add three new subscriptions for the following events:

    • oracle.apps.wf.event.agent.create

    • oracle.apps.wf.event.event.create

    • oracle.apps.wf.event.subscription.create

    For each subscription, specify the following values:

Go to previous page Go to next page
Oracle
Copyright © 2003 Oracle Corporation.
All Rights Reserved.
Go To Documentation Library
Home		 Go To Table Of Contents
Contents		 Go To Index
Index