Installation of Oracle Application Server for Oracle Workflow Option
Step 1. Install Oracle Application Server 4.0.7 or higher on a server machine.
Refer to your Oracle Application Server installation documentation for more information.
Step 2. Create at least one HTTP listener for Oracle Workflow and make note of its name and base URL.
Refer to your Oracle Oracle Application Server documentation for instructions on how to create a Web listener.
The base URL should have the following format, where <server_name>and <portID> represent the server and TCP/IP port number on which your web listener accepts requests:
http://<server_name>[:<portID>]/
For example:
http://prod.company.com/
http://test.company.com:8000/
Step 3. Install the Oracle Application Server PLSQL Toolkit.
1. From the Oracle Application Server home page, choose OAS Utilities to connect to the Oracle Application Server Utilities page.
2. In the navigation tree in the left-hand frame, expand Utilities and then Install node. Choose "PLSQL Toolkit".
3. In the Install PLSQL Toolkit page enter the required information for the SYS account. See your Oracle DBA if you need more information. Choose Apply when you are done.
Step 4. Create an Oracle Application Server Database Access Descriptor (DAD) for the Oracle Workflow Schema and register the DAD with a PL/SQL Cartridge.
1. From the Oracle Application Server home page, choose OAS Manager to connect to the Oracle Application Server Manager page.
2. In the navigation tree in the left-hand frame, expand Oracle Application Server, then choose DB Access Descriptor.
3. In the DB Access Descriptor page, choose the "+" icon from the toolbar to display the "DAD: Add" dialog window.
4. Enter the values appropriate for your schema in the DAD: Add page.
DAD Name <DAD_name>
Database User <wf_username>
Database User Password <wf_password>
Confirm Password <wf_password>
Database Location <host_server>
...
Check the option "Store the user name and password in the DAD" and then choose Apply.
5. Enter your DBA account information and choose Apply to create the DAD. Choose OK on successful completion.
6. In the navigation tree in the left-hand frame, choose Applications to display the Applications screen in the right frame.
7. In the Applications screen, choose the "+" icon from the toolbar to display the "Add Application" dialog window.
8. In the Add Application dialog, specify the following:
Application Type: PL/SQL
Configure Mode: Manually
Choose Apply to display the "Add Application" dialog window.
9. In the Add Application dialog, enter the following suggested values for Oracle Workflow:
Application Name: WF
Display Name: Workflow
Application Version: 2.5.2
When you choose Apply, a Success dialog box appears.
10. In the Success dialog box, choose the Add Cartridge to Application button to display the Add PLSQL Cartridge dialog window.
11. In the Add PLSQL Cartridge dialog, enter values appropriate for Oracle Workflow. The following lists shows some suggested values:
Cartridge Name: WF252
Display Name: WORKFLOW 2.5.2
Virtual Path: /wf252
Physical Path: <Retain Default>
DAD Name: <DAD_name>
Choose Apply when you are done.
12. In the left-hand frame, select the site node of the navigator tree to return to the Oracle Application Server Manager home page. Select All in the right-hand frame, then choose the Reload icon from the toolbar to put your new configuration changes into effect.
This step enables you to access your PL/SQL agent by appending the virtual path specified above to your web listener base URL as follows:
http://<server_name>[:<portID>]/<virtual_path>
http://prod.company.com/wf252
To invoke Oracle Workflow's web services, you simply append the appropriate procedure and arguments to this new base URL. For example, to access the Worklist web page, you would connect to the URL:
http://<server_name>[:<portID>]/<virtual_path>/wfa_html.home
Step 5. Protect the Workflow PL/SQL Cartridge Virtual Path.
Oracle Workflow's web pages rely on the user authentication feature of Oracle Web Application Server to provide security. To ensure that only authorized users can access workflow processes, the URLs that generate Oracle Workflow's web pages must be protected by the Oracle Web Application Server authentication feature. Refer to your Oracle Web Application Server documentation for more details.
1. From the Oracle Application Server home page, choose OAS Manager to connect to the Oracle Application Server Manager page.
2. First expand site node of the navigation tree in the left-hand frame, then expand "Oracle Application Server", followed by "Security".
3. Under Security, select either Basic, Digest, or Basic_Oracle to define the authentication and restriction schemes for your PL/SQL cartridges.
Basic authentication allows you to assign passwords to users, assign users to groups, and define sets of users and groups, called realms. You can then assign the users, groups, and realms to specific files and directories, requiring requestors to provide a username and password to gain access. Basic authentication sends unencrypted passwords across the network, making this method subject to subversion. Basic authentication is not recommended when security is critical.
Digest authentication is the same as basic authentication except that it sends passwords encrypted across the network in the form of a cryptographic checksum, also called a digest. You should use this scheme whenever authentication is required, although some older web browsers may not support it.
Basic_Oracle, also called Database Authentication, allows you to authenticate the username and password pair against a database by using the username and password to log on to an Oracle RDBMS. The realm of database authentication consists of two parts: a Database Access Descriptor (DAD) and optionally a database role. The DAD identifies the database to check against. The username and password, if available in the DAD, is ignored. The database role allows that only a subset of database users (those who have the privilege to assume the role) be authenticated.
4. If you select either Basic or Digest authentication, enter usernames and passwords for your users, assign your users to a group, then assign the group to a realm for your authentication method.
If you select Oracle_Basic authentication, assign groups to a realm, then for each group, specify the DAD to check against, and optionally specify the roles to be authenticated.
5. To protect the virtual path for your PLSQL cartridge, in the navigator tree, expand the site node, then expand "Applications".
6. In the navigator tree, under Applications, expand the Oracle Workflow application you defined earlier. Expand Cartridges, then expand the cartridge you want to protect. Finally, expand Configuration, and select Virtual Path to display the Virtual Paths form in the right-hand frame for your PL/SQL cartridge.
7. In the Virtual Paths form enter the following values in the Protection section:
Virtual Path Scheme Realm
<virtual_path> <Basic/Digest/Basic_Oracle> <realm_name>
Attention: All virtual paths must include a trailing slash, such as /wf252/.
Choose Apply when you are done.
8. In the left-hand frame, select the site node from the navigator tree to return to the Oracle Application Server Manager home page. Select All in the right-hand frame, then choose the Reload icon from the toolbar to put your new configuration changes into effect.
