Setting the Socket Listener Profile Options

The Notification Details web page can display an attached form icon to support form attributes in a notification message. Oracle Applications users can launch the Oracle Workflow Notification Worklist from their Oracle Applications menus.

From the Worklist, users can select a notification link to display the contents of a notification in the Notification Details page. If the

notification details display an attached form icon, users can choose that icon to launch an Oracle Applications form.

Before Oracle Workflow can launch the form from the Notification Details page, it must check for appropriate context information with Oracle Applications. To accomplish this, the socket listener on the form side must be active.

You can activate the Oracle Applications socket listener by setting the Socket Listener Activated profile option to Yes using the System Profile Values Window.

In addition, the Workflow Administrator needs to specify the following token values in $FND_TOP/resource/<language>/wfcfg.msg for the Java plugin:

WF_CLASSID <Class ID for Jinitiator>

(Required if you are using Microsoft Internet Explorer.) WF_PLUGIN_DOWNLOAD <Plugin location>

(Such as http://<server>/OA_JAVA/.) WF_PLUGIN_VERSION <Plugin version>

(Such as 1.1.7.27.)

Run the Workflow Resource Generator to load the contents of wfcfg.msg into the WF_RESOURCES table.

You can also set these three values in the Global Preferences page. See:

To Set Global User Preferences: page 2 – 14.

You must also set the Socket Listener Port profile option to the port at which Oracle Workflow should launch attached forms. This profile option can be set to different ports for different users.

If the socket listener port is not set at user level, Oracle Workflow launches attached forms at the default port set for the site. However, if users have set different ports, Oracle Workflow launches the forms for each user at the specified port. By using different socket listener ports, two different users logged into Oracle Applications on the same machine can both launch attached forms at the same time without interference from each other.

Context: You need to perform this step only once.

See: Overview of Setting User Profiles: Oracle Applications System Administrator’s Guide

See: To run the Workflow Resource Generator: page 8 – 105.

Step 7

☞

Setting the WF_RESOURCES Environment Variable

If you are using the standalone version of Oracle Workflow and your Workflow server is installed on a UNIX platform, you must set an environment variable called WF_RESOURCES to point to the

language–dependent Oracle Workflow resource file (wf<language>.res).

The resource file generally resides under the res subdirectory of your Oracle Workflow server directory structure.

Attention: Do not enclose environment variable values in double quotes (” ”) as this is not supported.

You do not need to set this environment variable if your Workflow server is installed on the Windows NT platform. The Workflow server installation on Windows NT automatically sets a WF_RESOURCES environment variable that identifies the path of the wf<language>.res file.

You also do not need to set this environment variable if you are using the version of Oracle Workflow embedded in Oracle Applications. For Oracle Applications, the path of the language–dependent Oracle Workflow resource file is $FND_TOP/$APPLRSC/wf<language>.res.

Context: You need to perform this step only once.

Step 8

☞

☞

Defining Document Management Repositories

Attention: Document management functionality will be supported in a future release. This description of the Oracle Workflow web pages for defining document management repositories is provided for reference only.

Oracle Workflow will provide seamless open integration with Oracle’s third party document management (DM) integration partners. Oracle Workflow communicates with these DM systems through a web server agent interface. You should be able to identify your DM system’s web server using the syntax <protocol>://<server:port>/.

To register the DM system with Oracle Workflow, use the Oracle Workflow Document Nodes web page to identify the DM system as a document node. Oracle Workflow uses the document node as the gateway to a specific document management system and uses the information defined in the node to construct the URLs that display the document management system documents.

Context: You need to perform this step only once.

" To Define a Document Node

1. Use a web browser to connect to the Oracle Workflow home page and choose the Document Nodes link, if you have workflow administrator privileges:

<webagent>/wfa_html.home

Alternatively, if you have workflow administrator privileges, you can connect directly to the Document Management Nodes web page:

<webagent>/fnd_document_management.dm_nodes_display

<webagent> represents the base URL of the web agent configured for Oracle Workflow in your Web server. See: Setting Global User Preferences: page 2 – 14.

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 Document Management Nodes web page displays a summary of any previously defined document management nodes. The summary displays the DM system node name, DM system version number, node ID, node description, and web server for the DM system. Also shown is the name of the DM system product, the DM product vendor and the DM system version number.

3. You can click on a node name link to edit the details of a node or choose Create Node to define a new node in the Document Nodes web page.

4. In the Document Nodes web page, enter or edit the name and description of the node.

5. Enter or edit the web server agent for the document management system. The syntax should be <protocol>://<server:port>.

6. Choose the document management product name for this node.

This is the name that represents the node for all users who wish to link documents to their workflow processes.

7. Choose OK to update or define the node.

Once you define a node, the browser returns you to a reloaded Document Management Nodes web page. Oracle Workflow assigns a node ID for the new node.

8. You can also delete a node by clicking on the Delete icon in the Delete column.

Caution: Before you delete a node, you should ensure that no Document–type attributes currently reference the node.