C
Oracle9iAS InterConnect Installation and Configuration

This appendix guides you through the steps for the Oracle9iAS InterConnect installation. The topics include:

• Oracle9iAS InterConnect Installation Overview

• Starting the Oracle9iAS InterConnect Installation

• Oracle9iAS InterConnect Hub Installation

• Oracle9iAS InterConnect Adapter Installation

• Oracle9iAS InterConnect Development Kit Installation

• Oracle9iAS InterConnect Management Infrastructure Installation

• How to Start Oracle9iAS InterConnect

• How to Change Passwords for the Oracle9iAS InterConnect and Oracle Workflow Schemas

• How to Create Multiple Repository Schemas in the Same Database

C.1 Oracle9iAS InterConnect Installation Overview

Oracle9iAS InterConnect is a hub-and-spoke, end-to-end integration solution. This section describes the following topics:

• Oracle9iAS InterConnect Installation Types

• Dependent Products and Topologies

• Hardware Requirements

• Software Requirements

• Multiple Oracle9iAS InterConnect Components on One Machine

C.1.1 Oracle9iAS InterConnect Installation Types

Oracle9iAS InterConnect has different installation types, depending on what you are installing:

Table C-1 Oracle9iAS InterConnect Installation Types

Installation Type	Description
Hub	Installs the InterConnect repository and Oracle Workflow. This is typically installed on top of an Oracle9i Application Server (Oracle9iAS) middle tier and serves as the central node for the integrated environment.
Adapter	Installs Oracle9iAS InterConnect adapters. You get to select which adapter you want to install. The adapters are typically installed on spoke machines and serve as the interface from applications to the hub.
Development Kit	Installs iStudio (Windows NT/2000 only) and the InterConnect Development Kit. The development kit is typically installed on a separate machine from the hub and the adapters, and provides mechanisms to model and create new InterConnect integrations.
Oracle9iAS InterConnect Management Infrastructure	Installs the Enterprise Manager Java console along with the Oracle9iAS InterConnect console plug-in. This is typically installed on a separate machine from the hub and allows you to manage the Oracle9iAS InterConnect environment.

These installation types appear in the installer in the Install Types screen.

C.1.2 Dependent Products and Topologies

You can run Oracle9iAS InterConnect in three different topologies.

• In the recommended topology, you run Oracle9iAS InterConnect with Oracle9iAS. See Section C.1.2.1, "Topology 1 (with Oracle9iAS)".

• In the second topology, you run Oracle9iAS InterConnect with an Oracle database. See Section C.1.2.2, "Topology 2 (with Oracle database)".

• In the third topology, you run Oracle9iAS InterConnect with the Oracle9iAS Infrastructure database. See Section C.1.2.3, "Topology 3 (with Oracle9iAS Metadata Repository)".

C.1.2.1 Topology 1 (with Oracle9iAS)

Running Oracle9iAS InterConnect with Oracle9iAS is the recommended topology. In this topology, you need the following:

• Install Oracle9iAS Infrastructure and one of the Oracle9iAS installation types (J2EE and Web Cache, Portal and Wireless, Business Intelligence and Forms, or Unified Messaging).

• Install Oracle9iAS InterConnect hub (Oracle Workflow included) in the same Oracle home as your Oracle9iAS installation.

The following figure shows the recommended topology. Oracle9iAS InterConnect hub uses the Oracle9iAS Infrastructure database as the hub database.

Figure C-1 Recommended Topology with Oracle9iAS

Text description of the illustration install_oaia.gif

C.1.2.2 Topology 2 (with Oracle database)

In this topology, you need an Oracle8i or Oracle9i database. Oracle9iAS InterConnect uses the database as the hub database to store its schemas. In this topology, you need the following:

• Install Oracle9iAS InterConnect hub (Oracle Workflow included) on the same machine as the Oracle database or on a different machine. If you are installing Oracle9iAS InterConnect hub on the same machine as the database, you must install it in an Oracle home separate from the Oracle database.

The following figure shows such a topology.

Figure C-2 Topology with Oracle9i Database

Text description of the illustration install_oai2.gif

C.1.2.3 Topology 3 (with Oracle9iAS Metadata Repository)

This topology is similar to Topology 1 in that Oracle9iAS InterConnect uses the Oracle9iAS Infrastructure database as the hub database. The difference between the two topologies is that in Topology 3, you install only the Infrastructure from Oracle9iAS; you do not install Oracle9iAS installation types in the middle tier. You can use this topology if you do not wish to use Oracle9iAS.

The following figure shows such a topology.

Figure C-3 Topology with Oracle9iAS Metadata Repository

Text description of the illustration install_oai3.gif

C.1.2.4 Setup Recommendations Common to All Topologies

For all topologies, you have to perform the following steps:

• Install the adapters:

  Install the adapters on the same machines as the applications they connect to, provided they are hosted on a platform that supports Oracle9iAS InterConnect. These machines are known as Oracle9iAS InterConnect Spoke machines.

  If the adapters are not on the same machines as the applications, assign one spoke machine per application. You can have one spoke machine for all applications if it meets your throughput needs.

• Assign one machine for the Development Kit installation or use the hub or one of the spoke machines.

• Assign one machine for Oracle9iAS InterConnect Management Infrastructure or use the hub or one of the spoke machines.

C.1.3 Hardware Requirements

Note: Do not run an install on a UNIX computer using Exceed on a remote machine. This can cause problems during install.

C.1.3.1 Hardware Requirements for the Hub Machine

If you are installing Oracle9iAS InterConnect hub on a machine that also contains Oracle9iAS, the machine should already meet the requirements listed in Section 2.1, "Hardware Requirements".

If you are installing Oracle9iAS InterConnect hub on a machine that does not have an Oracle9i Application Server installation, the machine should meet the requirements listed in Table C-2.

Table C-2 Hardware Requirements for the Hub Machine (non-Oracle9iAS)

Hardware	Windows NT/2000	UNIX
Memory	500 MB	500 MB
Service Pack	4.0 Service Pack 6 or later	n/a
Disk Space	10 GB	10 GB
CD-ROM Device	A CD-ROM drive to install, or the ability to access a CD-ROM device over the network	A CD-ROM drive to install, or the ability to access a CD-ROM device over the network

C.1.3.2 Hardware Requirements for the Spoke Machine

Table C-3 lists the hardware requirements for the spoke machine (for adapters).

Table C-3 Hardware Requirements for the Spoke Machine

Hardware	Windows NT/2000	UNIX
Memory	256 MB	256 MB
Service Pack	4.0 Service Pack 6 or later	n/a
Disk Space	500 MB	500 MB

C.1.3.3 Hardware Requirements for Development Kit Machines

Table C-4 lists the hardware requirements for Development Kit machines.

Table C-4 Hardware Requirements for Development Kit Machines

Hardware	Windows NT/2000	UNIX
Memory	128 MB	n/a
Service Pack	4.0 Service Pack 3 or later	n/a
Disk Space	500 MB	n/a

See Also: Oracle Workflow Guide for hardware requirements

C.1.4 Software Requirements

This section describes:

• Operating System Requirements

• JRE Requirements

• Notification Mailer (optional)

C.1.4.1 Operating System Requirements

The hub machine, the spoke machine, and iStudio run on the following operating systems:

• Sun SPARC Solaris 2.6, 2.7, 2.8 (32-bit)

• Windows NT 4.0, with Service Pack 6a or above

• Linux RedHat 7.1

• IBM AIX 4.3.3, 64-bit only

• Compaq Tru64 UNIX 5.0a, 5.1, 5.1a

• HP-UX 11.0, 11i (64-bit only)

C.1.4.2 JRE Requirements

Oracle9iAS InterConnect runs on JRE 1.3.1.

JRE is bundled with Oracle9iAS on Sun SPARC Solaris or Windows NT. When you install Oracle9iAS on these platforms, it installs JRE for you. If you are installing Oracle9iAS on other platforms, you have to download and install JRE prior to installing Oracle9iAS. See the platform-specific installation guide for details.

C.1.4.3 Solaris Patches

See Section 2.2, "Operating System Requirements" for a list of required patches.

C.1.4.4 Notification Mailer (optional)

The Notification Mailer is required only if you are using Oracle Workflow. If you are not using Oracle Workflow, you can skip this section.

The notification component of Oracle Workflow includes a program called the Notification Mailer. This program communicates notifications to users via e-mail and interprets responses. The Notification Mailer has implementations that can integrate directly with UNIX sendmail or MAPI-compliant mail applications.

• The UNIX sendmail implementation is installed automatically during the Oracle Workflow Server installation process. This implementation requires UNIX sendmail to be installed on the same server as Oracle Workflow.

• The MAPI-compliant implementation is installed on your Windows NT PC using the Oracle Universal Installer from the Oracle9iAS Client CD. This implementation requires a Windows NT MAPI-compliant mail application installed on the PC that is acting as your mail server.

  The MAPI-compliant implementation is available with Oracle9iAS for Windows NT only. It is not available with Oracle9iAS for Solaris.

  Note: The Microsoft Outlook E-mail Security Update that was released on June 7, 2000 desupports the MAPI Common Messaging Calls (CMC) interface used by the Oracle Workflow MAPI Mailer. (See: OL2000: Developer Information About the Outlook E-mail Security Update, http://support.microsoft.com/support/kb/articles/Q262/7/01.ASP.) As a result, the Oracle Workflow MAPI Mailer is not certified on any Microsoft Windows platforms where this Microsoft Outlook E-mail Security Update or above has been applied. The Oracle Workflow MAPI Mailer is not certified on Windows XP. Oracle Workflow customers running on NT/2000 are certified to install the UNIX version of the Oracle Workflow Notification Mailer (on UNIX) and connect to a Oracle Workflow Server database running on NT/2000.

C.1.5 Multiple Oracle9iAS InterConnect Components on One Machine

The installer does not allow you to install more than one of the same Oracle9iAS InterConnect component per Oracle home. When you install the same component the second time, it deinstalls the first installation before doing the second installation. For example, you cannot install more than one database adapter in one Oracle home.

You have two options if you need to install more than one instance of the same component on the same machine:

• Define multiple Oracle homes on the machine and install the component in each Oracle home. When you install a component the second time, choose a different Oracle home than the one where you first installed it.

• Use the copyAdapter script located in <ORACLE_HOME>/oai/9.0.2/bin/. to install multiple adapters of the same type in the same Oracle home.

  Usage:

  copyAdapter <app1> <app2>
  
  

  The script creates an adapter app2 that is of the same type as app1. If you want to service a different application with this adapter, you need to edit the application connectivity information in the adapter.ini file accordingly.

C.2 Starting the Oracle9iAS InterConnect Installation

You perform the following steps in the Oracle Universal Installer to display the Install Types screen, which enables you to select the install type you want. See Section C.1.1, "Oracle9iAS InterConnect Installation Types" for descriptions of the types.

1. Insert the CD-ROM in your CD-ROM drive.

2. Start the Oracle Universal Installer:
   • On Windows NT, double-click on setup.exe.

   • On UNIX, type runInstaller.

   The Welcome screen displays.

3. Oracle Universal Installer Welcome Screen

   The Welcome screen provides information about the Oracle Universal Installer.

   1. Review the Oracle Universal Installer Welcome screen. The following buttons appear on the screen:
      • Deinstall Products: Deinstall individual components or the entire product. This button appears only on the Welcome screen.

      • About Oracle Universal Installer: View the version number of the installer in use.

      • Exit: Quit the installation process and exit the installer.

      • Help: Access detailed information about the functionality of each screen.

      • Installed Products: View currently installed products or to deinstall the entire product or components.

      • Previous: Return to the previous screen.

      • Next: Proceed to the next screen.

   2. Click Next.

4. File Locations Screen
   1. Enter the following in the fields provided:

      Field	Value
      Source	The default value displays; do not change this value.
      Destination	Enter or select an existing Oracle home name and directory path.

   2. Click Next.

5. Oracle9iAS InterConnect Install Types Screen
   1. Select the Oracle9iAS InterConnect type from the following:
      • Oracle9iAS InterConnect Hub

      • Oracle9iAS InterConnect Adapters

      • Oracle9iAS InterConnect Development Kit

      • Oracle9iAS InterConnect Management Infrastructure

      See Section C.1.1, "Oracle9iAS InterConnect Installation Types" for information about these installation types.

   2. Click Next.

      Table C-5 directs you to the installation information for the components selected on this screen.

      Table C-5 Component-Specific Installation Information

      To install this component	See this section
      Hub	Section C.3, "Oracle9iAS InterConnect Hub Installation"
      Adapters	Section C.4, "Oracle9iAS InterConnect Adapter Installation"
      Development Kit	Section C.5, "Oracle9iAS InterConnect Development Kit Installation"
      Management Infrastructure	Section C.6, "Oracle9iAS InterConnect Management Infrastructure Installation"

C.3 Oracle9iAS InterConnect Hub Installation

The hub installation installs Oracle Workflow Server and the InterConnect repository. This section contains the following topics:

• Oracle9iAS InterConnect Hub Pre-Installation Steps

• Oracle9iAS InterConnect Hub Installation Steps for Topologies 1 and 3

• Oracle9iAS InterConnect Hub Installation Steps for Topology 2

• Oracle9iAS InterConnect Hub Post-Installation Steps (required for Oracle Workflow users only)

C.3.1 Oracle9iAS InterConnect Hub Pre-Installation Steps

These steps apply only to Topology 2.

1. Verify the values of the following parameters in the init.ora file for the metadata repository database:
   • AQ_TM_PROCESSES: Oracle Workflow requires the time manager process in Oracle9i Advanced Queuing (AQ) to monitor delay events in queues, as in the case of the Oracle Workflow standard Wait activity. The minimum recommended number of time manager processes for Oracle Workflow is one. Verify that the AQ_TM_PROCESSES parameter is set in the init.ora file. For example:

     AQ_TM_PROCESSES = 1
     
     

   • JOB_QUEUE_PROCESSES: Oracle Workflow leverages Oracle9i Advanced Queuing, which requires job queue processes to handle message propagation. You must start at least one job queue process to enable message propagation. The minimum recommended number of processes for Oracle Workflow is two and may need to be increased to five or ten if not enough processes are available for propagation. Verify that the JOB_QUEUE_PROCESSES parameter is set in the init.ora file to specify the number of SNP job queue processes for your instance. For example:

     JOB_QUEUE_PROCESSES = 10
     
     

   You can either modify these parameters in the init.ora file and restart your database to make the changes effective, or you can use the ALTER SYSTEM statement to dynamically modify the parameter values for the duration of the instance. For more information, refer to Oracle9i Reference and Oracle9i Application Developer's Guide - Advanced Queuing.

2. (Oracle Workflow only) Ensure that there are no users accessing the Oracle Workflow server. Otherwise, locks in the database prohibit a successful upgrade.

3. (Oracle Workflow only) If you have an existing Oracle Workflow server, check that it is release 2.6.0 or higher. If you have an earlier version, you need to upgrade it to release 2.6 before you can upgrade to 2.6.2.

C.3.2 Oracle9iAS InterConnect Hub Installation Steps for Topologies 1 and 3

When you install the hub on a machine with Oracle9iAS, you see a dialog that enables you to reset the password for the oaihub902 and owf_mgr schemas. This dialog displays after you select Oracle9iAS InterConnect Hub on the Oracle9iAS InterConnect Install Types screen.

1. Select Oracle9iAS InterConnect Hub from the Oracle9iAS InterConnect Install Types screen.

   See Section C.2, "Starting the Oracle9iAS InterConnect Installation" for instructions on how to display the Install Types screen.

2. Oracle9iAS Metadata Repository: Enter Oracle Internet Directory Administrator Password Screen

   In this screen, enter the password of the Oracle Internet Directory administrator (cn=orcladmin) so that the installer can retrieve configuration information.

   1. Enter or view information in the following fields:
      • OiD Hostname: This field is filled in for you and cannot be changed. It displays the machine running Oracle Internet Directory.

      • OiD Port: This field is filled in for you and cannot be changed. It displays the port number for Oracle Internet Directory.

      • OiD DN: This field is filled in for you and cannot be changed. It displays the distinguished name (DN) of the Oracle Internet Directory administrator (cn=orcladmin).

      • OiD Password: Enter the Oracle Internet Directory administrator's password in this field.

   2. Click Next.

3. Change Oracle9iAS InterConnect Schema Password Screen

   To properly configure all pieces of the Oracle9iAS InterConnect installation, you must create a new password for the Oracle9iAS InterConnect schemas.

   1. Enter information in the following fields:
      • Database: This field is filled in for you. It points to the metadata repository database.

      • Schema Names: This field is also filled in for you. It specifies the schema names: oaihub902 and owf_mgr.

      • Password: The new password for the schemas. You will need the new password to install other Oracle9iAS InterConnect components.

        Note that the same password is used for both oaihub902 and owf_mgr schemas.

      • Confirm Password: Reenter the new password.

   2. Click Next.

4. Summary Screen

   This screen displays the selections made on previous screens. Review the selections and click Install.

When the installation is complete, the file <ORACLE_HOME>/oai/9.0.2/hub/hub.ini is empty. This is the correct result of the installation.

C.3.3 Oracle9iAS InterConnect Hub Installation Steps for Topology 2

When you install the hub on a machine that does not have Oracle9iAS, you see two dialogs: one dialog enables you to specify the database to use as the hub database, and the second dialog enables you to set the password for the Oracle9iAS InterConnect schema.

These dialogs display after you select Oracle9iAS InterConnect Hub on the Oracle9iAS InterConnect Install Types screen.

Note that the installer does not permit you to install Oracle9iAS InterConnect hub in the same Oracle home as the database. You have to select another Oracle home.

If you have an existing Workflow Server setup, you need to migrate it to Oracle9iAS Workflow Server after the hub install. The Oracle9iAS Workflow Server is installed as part of InterConnect Hub install. See the Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 Guide for more information on Workflow Migration.

1. Select Oracle9iAS InterConnect Hub from the Oracle9iAS InterConnect Install Types screen.

   See Section C.2, "Starting the Oracle9iAS InterConnect Installation" for instructions on how to display the Install Types screen.

2. Oracle9iAS InterConnect Hub Database Screen - Specify database connection information
   1. Enter database connection information in the following fields:
      • Host Name: The host name for the database. The default is localhost.

      • Port Number: The port number for the database. The default is 1521.

      • Database SID: The SID for the database. The default is iasdb.

   2. Click Next.

3. Oracle9iAS InterConnect Metadata Repository - Set Schema Passwords
   1. Enter information in the following fields:
      • Database: The database indicated on the previous screen. The value is entered as host:port:sid.

      • Schema Names: The schema name for the database: oaihub902.

      • Password: The new password for the schema.

      • Confirm Password: Reenter the new password.

   2. Click Next.

   The Summary screen displays.

4. Create the Oracle9iAS InterConnect schema in the hub database.

   See $ORACLE_HOME/oai/9.0.2/repository/post_installation.txt for instructions on how to do this. You do not have to run this step in Topology 1 and 3 because the schema was created for you automatically.

5. (required for Oracle Workflow users only) Create the Oracle Workflow schema in the hub database using the Oracle Workflow Configuration Assistant. For details, see the Oracle Workflow Guide.

C.3.4 Oracle9iAS InterConnect Hub Post-Installation Steps (required for Oracle Workflow users only)

If you are using Oracle Workflow, you need to perform the steps in this section after installing Oracle9iAS InterConnect hub. The hub installation installs Oracle Workflow automatically; if you are not planning to use Oracle Workflow, you can skip this section.

Note: The workflow.log file produced during installation and configuration of Oracle Workflow may contain sensitive information. To protect this sensitive information, you can delete the file after the installation is complete or change the permissions for the file so that only authorized administrators can access it.

The post-installation steps are:

• Step 1: "Run Oracle Workflow Configuration Assistant"

• Step 2: "Create a database access descriptor (DAD) for Oracle Workflow"

• Step 3: "Verify Oracle Workflow virtual directory mappings"

• Step 4: "Set up Oracle Workflow HTML help"

• Step 5: "Set up a directory service for Oracle Workflow"

• Step 6: "Implement Oracle Internet Directory integration (optional)"

• Step 7: "Verify your base URL"

• Step 8: "Install additional languages (optional)"

• Step 9: "Configure Oracle Workflow with Oracle9iAS InterConnect"

• Step 10: "Perform generic configuration steps"

Step 1 Run Oracle Workflow Configuration Assistant

Note: This step is required for Topology 2 users only. If you are using Topologies 1 or 3, you can skip this step.

You need to run this step if you are upgrading Oracle Workflow, or if you need to reconfigure a new installation.

If you are installing Oracle Workflow for the first time, Oracle Universal Installer automatically loads Oracle Workflow into your database.

If you are upgrading an existing installation of Oracle Workflow, or if you need to reconfigure Oracle Workflow, you can run Oracle Workflow Configuration Assistant manually.

Before you run Oracle Workflow Configuration Assistant, you should close other applications you may have running, including Java applications, Oracle-based applications, and any other applications that consume large amounts of memory, hard disk space, or CPU time. However, you should not close any components of the Oracle9i database where you want to load Oracle Workflow.

When you run Oracle Workflow Configuration Assistant on Windows, several command windows open and close automatically. You should ignore these windows. You must not manually close any of these command windows, or you will interrupt the configuration process.

To configure Oracle Workflow:

Note: To upgrade to Release 2.6.2, your existing Oracle Workflow Server must be Release 2.6.0 or higher. If you have an earlier version, you must upgrade it to Release 2.6 before you can upgrade to Release 2.6.2.

1. Start the Oracle Workflow Configuration Assistant using the following commands:
   • On UNIX, run: $ORACLE_HOME/wf/install/wfinstall.

   • On Windows NT, run:%ORACLE_HOME%\wf\install\wfinstall.bat.

2. In the Oracle Workflow Configuration Assistant window, enter the following user information:
   • Workflow Account: The user name of your Oracle Workflow database account. The default account for a new installation is OWF_MGR.

   • Workflow Password: The password for your Oracle Workflow database account. This password must be the same as the password for the oaihub902 schema.

     Note: If you are performing a new installation of Oracle Workflow, Oracle Workflow Configuration Assistant creates a new database account for Oracle Workflow with the user name and password you specify. This password must be the same as the password for the oaihub902 schema. The default tablespace for this account is USERS, and the temporary tablespace is TEMP. If you are upgrading an existing installation of Oracle Workflow, you should enter the user name and password for your existing Oracle Workflow database account.

   • SYS Password: Your SYS password. See your Oracle DBA if you need more information.

   • SYSTEM Password: Your SYSTEM password. See your Oracle DBA if you need more information.

   • Install Option: Select Upgrade to upgrade an existing installation of Oracle Workflow.

   • Language Selection: Leave blank. This information is only required for the Add Language install option. See Step 8: "Install additional languages (optional)".

   • Connect Method: Select Local to connect to a local database using the Oracle SID, or select Remote to connect to a remote database through Oracle Net using LOCAL on Windows or TWO_TASK on UNIX.

   • Connect String: If you choose the Remote connect method, enter the connect string for the remote database.

3. Click Submit to begin the configuration. You can also click Quit to exit Oracle Workflow Configuration Assistant without performing the configuration.

4. When the configuration is complete, a confirmation window appears. Click OK.

5. You can check the status of the configuration by reviewing the workflow.log file in the wf/install subdirectory within your Oracle home.

   Note: The workflow.log file produced during installation and configuration of Oracle Workflow may contain sensitive information. To protect this sensitive information, you can delete the file after the installation is complete or change the permissions for the file so that only authorized administrators can access it.

Step 2 Create a database access descriptor (DAD) for Oracle Workflow

Oracle Workflow requires Oracle HTTP Server as your Web server. The Web server must be able to access the Oracle Workflow Java area, the Oracle Workflow icon area, and the Oracle Workflow documentation area.

After installing Oracle HTTP Server and Oracle Workflow, you must create a database access descriptor (DAD) for Oracle Workflow in Oracle HTTP Server.

1. Using your web browser, navigate to the Oracle Enterprise Manager Web site.

   http://<host_name>:<port_number>/
   
   

   For example:

   http://test:1810/
   
   

2. Log in using the Oracle9iAS administrator username and password.

   The default username for the administrator is ias_admin. The default password was specified during the installation of Oracle9iAS.

3. In the Oracle9iAS Farm Home Page, select your application server instance.

4. In the Oracle9iAS Instance Home Page, select "HTTP Server" in the System Components section.

5. In the HTTP Server page, select "PL/SQL Properties" in the Administration section.

6. In the mod_plsql Services page, select the Create button in the DAD Status region to create a new DAD.

7. In the Create DAD: DAD Type page, select General and click Next.

8. In the Create DAD: Database Connection page, enter the following settings:
   • DAD Name: pls/<your_Workflow_DAD>

   • Database Connection String: <CONNECT_STRING>

   • Default Page: wfa_html.home

   • Authentication Mode: Basic

   Click Next.

   Note: Be sure you leave the Database Username and Database Password null to enable mod_plsql database authentication. You can also leave any remaining settings blank.

9. In the Create DAD: Document, Alias and Session page, select Stateless-ResetPackageState in the Session State Management field. Leave the remaining settings blank. Click Next.

10. In the Create DAD: Advanced page, leave all the settings blank and click Finish.

    Oracle Enterprise Manager displays your new DAD in the DAD Status section of the mod_plsql Services page.

11. Restart Oracle HTTP Server.

    For more information, see the Oracle HTTP Server Administration Guide.

12. To access Oracle Workflow's web services, navigate to the following URL:

    http://<server_name>[:<portID>]/pls/<your_Workflow_DAD>/wfa_html.home
    
    

    Note: The icons on the Oracle Workflow Web pages appear as broken images if the virtual directory mapping to the Oracle Workflow icon area has not been added. See Step 3: "Verify Oracle Workflow virtual directory mappings".

Step 3 Verify Oracle Workflow virtual directory mappings

Oracle Workflow requires the following virtual directory mappings:

Virtual directory	Physical directory	Description
/OA_JAVA/	<ORACLE_HOME>/jlib/	Points to the directory that contains Oracle Workflow JAR files
/OA_MEDIA/	<ORACLE_HOME>/wf/java/oracle/apps/fnd/wf/icons/	Points to Oracle Workflow icons and other graphics used by the Oracle Workflow Web interface
/OA_DOC/	<ORACLE_HOME>/wf/doc/	Points to the documentation

If you installed Oracle HTTP Server and Oracle Workflow in the same Oracle home, the virtual directory mappings are set by default. Verify these mappings and add them, if necessary.

To add the virtual directory mappings in Oracle HTTP Server:

1. Add aliases for the jlib directory and the Oracle Workflow icon and doc directories to the <ORACLE_HOME>/Apache/Apache/conf/httpd.conf or httpds.conf file.

   The Alias directive has the following format:

   Alias <fakename> <realname>
   
   

   Examples (UNIX):

   Alias /OA_JAVA/ "/oracle9ias/jlib/"
   Alias /OA_MEDIA/ "/oracle9ias/wf/java/oracle/apps/fnd/wf/icons/"
   Alias /OA_DOC/ "/oracle9ias/wf/doc/"
   
   

   Examples (Windows NT):

   Alias /OA_JAVA/ "C:\oracle9ias\jlib/"
   Alias /OA_MEDIA/ "C:\oracle9ias\wf\java\oracle\apps\fnd\wf\icons/"
   Alias /OA_DOC/ "C:\oracle9ias\wf\doc/"
   

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

2. Restart Oracle HTTP Server.

Step 4 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 Guide.

To set up the HTML help, unzip the <ORACLE_HOME>/wf/wfdoc262.zip 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. Verify this mapping and add it, if necessary.

1. Use an unzip utility to extract the doc directory tree from the <ORACLE_HOME>/wf/wfdoc262.zip file.

   You need at least 5 Mb of free disk space to extract the zip file.

   Extract the files to <ORACLE_HOME>/wf/. You should get the following subdirectories:

   Directory	Contents
   <ORACLE_HOME>/wf/doc/<lang>/wf	Oracle Workflow Guide
   <ORACLE_HOME>/wf/doc/<lang>/wfcust	Custom Help. You can add your own customized Workflow help in this directory.

   Alternatively, you can install the doc directory tree on a PC file system. Create a directory for the HTML help on your PC. Then transfer the HTML help zip file to the new directory on your PC. Use an unzip utility to extract the doc directory tree from the zip file in that directory.

2. (optional) After extracting the doc directory tree, you can remove the zip file.

3. Verify that you have a virtual directory mapping called /OA_DOC/ in your web listener. See Step 3: "Verify Oracle Workflow virtual directory mappings".

4. Try accessing 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 Guide is:

   http://<server_name>[:<portID>]/OA_DOC/<lang>/wf/toc.htm
   
   

   The path for the contents page of your Oracle Workflow Custom Help is:

   http://<server_name>[:<portID>]/OA_DOC/<lang>/wfcust/wfcust.htm
   
   

5. (optional) 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 Guide.

Step 5 Set up a directory service for Oracle Workflow

Note: See the section "Setting up an Oracle Workflow Directory Service" in Chapter 2 of the Oracle Workflow Guide for more details.

You must map Oracle Workflow directory service views to your organization's users and roles. The directory service views are WF_USERS, WF_ROLES, and WF_USER_ROLES.

Oracle Universal Installer automatically executes the <ORACLE_HOME>/wf/sql/wfdirouv.sql script to map the directory service views to your native Oracle database users and roles. This script bases the views on the tables DBA_USERS, WF_LOCAL_USERS, DBA_ROLES, and WF_LOCAL_ROLES.

To map Oracle Workflow directory service views, do one of the following:

• Create your own script or customize and rerun the wfdirouv.sql script to map the directory service views to the users and roles defined in your organization's directory repository.

  The wfdirouv.sql script sets each native Oracle user's e-mail address to the user's respective username. As a minimal setup step, edit the 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 should change are EMAIL_ADDRESS in WF_USERS and EMAIL_ADDRESS in WF_ROLES.

  OR

• Run the <ORACLE_HOME>/wf/sql/wfdircsv.sql script to map the directory service views only to the WF_LOCAL_USERS and WF_LOCAL_ROLES tables.

  Note: If you want to implement Oracle Internet Directory integration, you must run the wfdircsv.sql script, because only the WF_LOCAL_USERS table is synchronized with Oracle Internet Directory.

After setting up your directory service, run the wfdirchk.sql script in SQL*Plus to verify the integrity of your directory service data model. The script is located on your Oracle Workflow server in the Oracle Workflow admin/sql subdirectory. See the "Workflow Administration Scripts" chapter of the Oracle Workflow Guide for more information.

Step 6 Implement Oracle Internet Directory integration (optional)

Note: See the section "Synchronizing Workflow Directory Services with Oracle Internet Directory" in Chapter 2 of the Oracle Workflow Guide for more details.

You can optionally implement LDAP integration and single signon for Oracle Workflow through Oracle Internet Directory and Oracle9iAS Single Sign-On Server.

To implement Oracle Internet Directory integration:

1. Ensure that Oracle Internet Directory, Oracle9iAS Single Sign-On Server, and Oracle Portal are installed.

2. Ensure that mod_osso is installed and configured with Oracle HTTP Server. For more information, see "Developing Applications for Mod_osso" in the Oracle9iAS Single Sign-On Application Developer's Guide.

   You must protect the Database Access Descriptor you created by adding the following entry in your mod_osso configuration file (replace "your_Workflow_DAD" with the name of the DAD you created in Step 2: "Create a database access descriptor (DAD) for Oracle Workflow"):

   <Location /pls/your_Workflow_DAD>
     require valid-user
     authType Basic
   </Location>
   
   

3. Run the <ORACLE_HOME>/wf/sql/wfdircsv.sql script to map the directory service views only to the WF_LOCAL_USERS and WF_LOCAL_ROLES tables.

   WF_LOCAL_USERS is the only table that is synchronized with Oracle Internet Directory. Only users are maintained through Oracle Internet Directory, not Oracle Workflow roles.

4. If you are upgrading a previous installation of Oracle Workflow, migrate existing Oracle Workflow user information to Oracle Internet Directory.

   You must perform a one-time migration of existing Oracle Workflow user information to Oracle Internet Directory to enable single signon 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 Oracle Internet Directory.

   Oracle Internet Directory provides a migration tool called ldifMigrator. To use this tool:

   1. 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.

   2. Upload the LDIF file produced by ldifMigrator 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" in the Oracle Internet Directory Administrator's Guide.

5. Load the following PL/SQL packages required for LDAP synchronization:
   • DBMS_LDAP: This package contains the functions and procedures that can be used to access data from LDAP servers. If this package is not already installed, you must load it manually. To check whether the package is installed, connect to SQL*Plus and use the following command:

     desc DBMS_LDAP
     
     

     If the package does not exist, load it manually by running the <ORACLE_HOME>/rdbms/admin/catldap.sql script. 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
     
     

   • WFA_SEC: This package contains Oracle Workflow security functions and procedures. To load this package, run the <ORACLE_HOME>/wf/sql/wfsecwsb.sql script. Run this script as the Oracle Workflow user. For example, use the following command:

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

6. Use the WF_LDAP APIs to synchronize your Oracle Workflow directory service with Oracle Internet Directory.

   For details, see "Synchronizing Oracle Workflow Directory Services with Oracle Internet Directory" and "Setting Up Oracle Workflow"in the Oracle Workflow Guide.

Step 7 Verify your base URL

To invoke Oracle Workflow Web services, you simply append the appropriate procedure and arguments to your base URL. Once you define your Web security and Web users, you can verify your base URL by connecting to the Oracle Workflow home page as a valid user:

http://<server_name>[:<portID>]/pls/<your Workflow DAD>/wfa_html.home

When using Oracle HTTP Server, you can authenticate yourself with a database username and password. 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 and creates these same users as database accounts. The users are: sysadmin, wfadmin, blewis, cdouglas, kwalker, and spierson. To set passwords for these accounts, connect to the SYSTEM database account using SQL*Plus and specify a password for each account using the ALTER USER command. For more information, see: ALTER USER, Oracle9i SQL Reference.

With Oracle HTTP Server, you can authenticate your connection to an Oracle Workflow Web page with any of these database usernames and passwords. Public grants and synonyms were created so that these database accounts have full access to the Oracle Workflow Web-based user interface.

Note: For security reasons, the installation process locks these user accounts after creating them. Before you can use the accounts, you must unlock them using the script <ORACLE_HOME>/wf/demo/wfdemoul.sql. 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.

Step 8 Install additional languages (optional)

The Oracle Workflow server installation and upgrade are available only in English. To support access to Oracle Workflow in another language, you must load that language after the installation and configuration steps using Oracle Workflow Configuration Assistant.

Note: Before you run Oracle Workflow Configuration Assistant, you should close other applications you may have running, including Java applications, Oracle-based applications, and any other applications that consume large amounts of memory, hard disk space, or CPU time. However, you should not close any components of the Oracle9i database where you want to load Oracle Workflow.

When you run the Oracle Workflow Configuration Assistant on Windows, several command windows open and close automatically. You should ignore these windows. You must not manually close any of these command windows, or you will interrupt the configuration process.

To load additional languages:

1. Start Oracle Workflow Configuration Assistant:
   • On UNIX, run: $ORACLE_HOME/wf/install/wfinstall.

   • On Windows NT, run: %ORACLE_HOME%\wf\install\wfinstall.bat.

2. In the Oracle Workflow Configuration Assistant window, enter the following user information:
   • Workflow Account: The user name of your Oracle Workflow database account. The default Oracle Workflow account for a fresh installation is OWF_MGR.

   • Workflow Password: The password for your Oracle Workflow database account.

   • SYS Password: Your SYS password. See your Oracle DBA if you need more information.

   • SYSTEM Password: Your SYSTEM password. See your Oracle DBA if you need more information.

   • Install Option: Select Add Language.

   • Language Selection: Select the language abbreviation for the language you want to add. For a list of standard language abbreviations in Oracle9i, see "Locale Data" in the Oracle9i National Language Support Guide.

   • Connect Method: Select Local to connect to a local database using the Oracle SID, or select Remote to connect to a remote database through Oracle Net using LOCAL on Windows or TWO_TASK on UNIX.

   • Connect String: If you choose the Remote connect method, enter the connect string for the remote database.

3. Click Submit to begin the configuration. You can also click Quit to exit the Oracle Workflow Configuration Assistant without performing the configuration.

4. When the configuration is complete, a confirmation window appears. Click OK.

5. You can check the status of the configuration by reviewing the workflow.log file located in the wf/install subdirectory within your Oracle home.

   Note: The workflow.log file produced during installation and configuration of Oracle Workflow may contain sensitive information. To protect this sensitive information, you can delete the file after the installation is complete or change the permissions for the file so that only authorized administrators can access it.

Step 9 Configure Oracle Workflow with Oracle9iAS InterConnect

The steps in this section are specific to configuring Oracle Workflow to run with Oracle9iAS 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 "Scheduling Listeners for Local Inbound Agents" in the Oracle Workflow Guide for details.

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 these values:

   Field	Value
   System	<your_workflow_system>
   Source Type	External
   Event Filter	the event you are creating the subscription for (one of the three listed above)
   Status	Enabled
   Rule Data	Key
   Rule Function	wf_event_functions_pkg.receive
   Description	Oracle9iAS InterConnect Subscription

   See Also: "To Define an Event Subscription" in Oracle Workflow documentation

Step 10 Perform generic configuration steps

The configuration steps in this section are generic to Oracle Workflow (that is, these steps are not specific to using Oracle Workflow with Oracle9iAS InterConnect).

1. Configure the default global user preferences for your enterprise.

   See the section "Step 2: Setting Global User Preferences" in Chapter 2 of the Oracle Workflow Guide for details.

2. Create a view called WF_LANGUAGES that identifies the languages defined in your Oracle9i installation.

   The wfdirouv.sql script run by the Oracle Universal Installer automatically creates a sample WF_LANGUAGES view. If you want to use this view, you should verify it first by connecting to SQL*Plus using your Oracle Workflow database account and querying the view for all languages defined in your Oracle9i installation.

   See the section "Step 5: Creating the WF_LANGUAGES View" in Chapter 2 of the Oracle Workflow Guide for details.

3. If your Oracle Workflow Server is installed on a UNIX platform, define an environment variable called WF_RESOURCES.

   See the section "Step 7: Setting the WF_RESOURCES Environment Variable" in Chapter 2 of the Oracle Workflow Guide for details.

4. Initiate background Oracle Workflow engines to process deferred work and timed out activities.

   See the section "Step 9: Setting up Background Workflow Engines" in Chapter 2 of the Oracle Workflow Guide for details.

5. (optional) Customize Oracle Workflow.

   You may need to perform these customizations, depending on the feature that you want to implement. The following table lists the steps, along with a pointer to the section in the Oracle Workflow Guide where you can find instructions on how to perform the step.

   Table C-6 Optional steps for customizing Oracle Workflow

   Step	See this section in the Oracle Workflow Guide:
   Configure and run the Notification Mailer program to allow users to receive e-mail notifications or e-mail notification summaries.	Section "Step 10: Implementing the Notification Mailer" in Chapter 2
   Customize e-mail notification templates.	Section "Step 11: Modifying Your Message Templates" in Chapter 2
   Customize the logo displayed on Oracle Workflow Web pages.	Section "Step 12: Customizing the Logo on Oracle Workflow's Web Pages" in Chapter 2
   Add custom icons to Oracle Workflow.	Section "Step 13: Adding Custom Icons" in Chapter 2
   Start the Java Function Activity Agent to run external Java functions.	Section "Step 14: Setting up the Java Function Activity Agent" in Chapter 2
   Set up database links and queues for the Business Event System to communicate events between systems.	Section "Step 15: Setting up the Business Event System" in Chapter 2
   Schedule Business Event System listeners and propagations to receive and send event messages.	Chapter 13, "Managing Business Events"
   Set up event subscriptions to synchronize Business Event System data on different systems.	Chapter 13, "Managing Business Events"

C.4 Oracle9iAS InterConnect Adapter Installation

To install any number of the Oracle9iAS InterConnect adapters, start the Oracle Universal Installer and complete the following steps.

1. Installation Types Screen
   1. Select Oracle9iAS InterConnect Adapters.

   2. Click Next.

2. Available Product Components Screen
   1. Select the adapter you want to install. The following components are available:
      • Oracle9iAS InterConnect AQ Adapter

      • Oracle9iAS InterConnect Database Adapter

      • Oracle9iAS InterConnect FTP Adapter

      • Oracle9iAS InterConnect HTTP Adapter

      • Oracle9iAS InterConnect MQ Series Adapter

      • Oracle9iAS InterConnect SMTP Adapter

      • Oracle9iAS InterConnect PeopleSoft 7.5x Adapter

      • Oracle9iAS InterConnect SAP R/3 Adapter

      • Oracle9iAS InterConnect CICS Adapter

      • Oracle9iAS InterConnect Siebel 2000 Adapter

      • Oracle9iAS InterConnect JDEdwards Adapter

      See Table C-7 for component-specific installation steps.

      Table C-7 Component-Specific Installation Information

      Adapter	Installation Instructions
      AQ	Oracle9iAS InterConnect Adapter for AQ Installation and User's Guide
      Database	Oracle9iAS InterConnect Adapter for DB Installation and User's Guide
      FTP	Oracle9iAS InterConnect Adapter for FTP Installation and User's Guide
      HTTP	Oracle9iAS InterConnect Adapter for HTTP Installation and User's Guide
      MQ Series	Oracle9iAS InterConnect Adapter for MQ Series Installation and User's Guide
      SMTP	Oracle9iAS InterConnect Adapter for SMTP Installation and User's Guide
      PeopleSoft 7.5x	Oracle9iAS InterConnect Adapter for PeopleSoft 7.5x Installation and User's Guide
      SAP R/3	Oracle9iAS InterConnect Adapter for SAP R/3 Installation and User's Guide
      CICS	Oracle9iAS InterConnect Adapter for CICS Installation and User's Guide
      Siebel 2000	Oracle9iAS InterConnect Adapter for Siebel 2000 Installation and User's Guide
      JDEdwards	Oracle9iAS InterConnect Adapter for JDEdwards Installation and User's Guide

   2. Click Next.

C.5 Oracle9iAS InterConnect Development Kit Installation

This section describes how to install the Oracle9iAS InterConnect development kit.

In Oracle9iAS for Solaris, the Oracle Workflow Client includes Oracle Workflow Builder.

In Oracle9iAS for Windows NT, the Oracle Workflow Client includes Oracle Workflow Builder and the MAPI-compliant Notification Mailer.

C.5.1 Installing the Development Kit

If you want to write your own custom Oracle9iAS InterConnect Adapter, you must install the Development Kit in a new Oracle home. This installs all dependencies. If you have not installed the Oracle9iAS InterConnect hub, you need to do so before proceeding with this installation.

Perform the following steps to install the Development Kit:

1. Available Product Components Screen
   1. Select Oracle9iAS InterConnect Development Kit.

   2. Click Next.

2. Oracle9iAS InterConnect Hub Database Screen - Specify database connection information

   Note that this screen appears only when ALL of the following conditions are met:

   • You are installing the Development Kit on the Solaris platform.

   • The Oracle home in which you are installing the Development Kit does not have any Oracle9iAS InterConnect components.

   • You are installing the Development Kit on a machine that is not a middle-tier machine for Oracle9iAS.

   Enter the following information about the Oracle9iAS InterConnect hub (usually an Oracle9iAS Metadata Repository) to use.

   • Host Name: The host name of the Oracle9iAS InterConnect hub. The default is the current host.

   • Port Number: The port number of the Oracle9iAS InterConnect hub. The default is 1521.

   • Database SID: The database SID. The default is iasdb1.

   • Password: The password for the Oracle9iAS InterConnect hub. The default is blank.

3. Summary Screen

   Review the selections made on previous screens and click Install.

   The Development Kit is installed on your machine in the following directory:

   Platform	Directory
   Windows NT	%ORACLE_HOME%\oai\9.0.2\sdk
   UNIX	$ORACLE_HOME/oai/9.0.2/sdk

4. Configure Oracle Net using the Oracle Net Configuration Assistant. Follow the directions in the configuration assistant to complete the configuration.

C.5.2 Oracle9iAS InterConnect Development Kit Post-Installation Steps

Perform these steps after installing Oracle Workflow Client only if you are using Oracle Workflow.

Step 1 Set up the Oracle Workflow HTML help

When you install Oracle Workflow Builder, the 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\wfdoc262.zip. To view the HTML help, extract the doc directory tree from the zip file to your file system:

1. Use an unzip utility to extract the doc directory tree from the zip file within the Workflow directory.

   You need at least 5 Mb of free disk space to extract the zip file.

   Extract the files to <ORACLE_HOME>/wf/. You should get the following subdirectories:

   Directory	Contents
   <ORACLE_HOME>\wf\doc\<lang>\wf	Oracle Workflow Guide
   <ORACLE_HOME>\wf\doc\<lang>\wfcust	Custom Help. You can add your own customized Workflow help in this directory.

2. (optional) After extracting the doc directory tree, you can remove the zip file.

3. You can now view the HTML help using a Web browser.

   The path for the contents page of the Oracle Workflow Guide is:

   <ORACLE_HOME>\wf\doc\<lang>\wf\toc.htm
   
   

   The path for the contents page of your Oracle Workflow Custom Help is:

   <ORACLE_HOME>\wf\doc\<lang>\wfcust\wfcust.htm
   
   

4. (optional) To add custom help, 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 Guide.

Step 2 Modify fonts in Oracle Workflow Builder (optional)

If you are installing Oracle Workflow Builder in another language, such as Japanese, you can modify the font used by the windows in Oracle Workflow Builder to a font that is appropriate for your language. Any change you make applies to all windows within the program.

1. Choose Font from the View menu in Oracle Workflow Builder to display the Fonts properties page.

2. Select the font you want to use in the labels for your icons and in the navigator tree. The Sample region shows the appearance of the font you select. For example, when using Oracle Workflow Builder in Japanese, you might choose the font MS PGothic.

3. Select the font style: Regular, Bold, Italic, or Bold Italic. Some fonts have a limited selection of font styles.

4. Select the font size. Some fonts have a limited selection of font sizes.

5. Select the Underline or Strikeout check boxes to apply those effects.

6. Click OK when you are finished.

7. Close and restart Oracle Workflow Builder. The new font settings should then take effect.

Step 3 Review documentation for custom adapters (optional)

If you need to create custom adapters and browsers, see the documentation in <ORACLE_HOME>/oai/9.0.2/sdk/cookbook.zip.

C.6 Oracle9iAS InterConnect Management Infrastructure Installation

Oracle9iAS InterConnect Management Infrastructure is required for managing InterConnect components.

In Topology 1 and 3, Oracle Management Server was installed as part of the Oracle9iAS Infrastructure installation. The remaining step is to install the Oracle9iAS InterConnect Management Infrastructure; see instructions below.

In Topology 2, you need to install both Oracle9iAS InterConnect Management Infrastructure and Oracle Management Server:

• Install Oracle Management Server in the hub database's Oracle home. If you already have an existing Oracle Management Server, you can upgrade it. See the Oracle9i Application Server: Migrating from Oracle9i Application Server 1.x.

• Install Oracle9iAS InterConnect Management Infrastructure; see instructions below.

To install Oracle9iAS InterConnect Management Infrastructure:

1. Available Product Components Screen
   1. Select Oracle9iAS InterConnect Management Infrastructure.

   2. Click Next.

2. Summary Screen

   Review the selections made on previous screens and click Install.

3. Configure Oracle Net using the Oracle Net Configuration Assistant. Follow the directions in the configuration assistant to complete the configuration.

4. See the file <ORACLE_HOME>/oai/9.0.2/console/post_installation.txt for post-installation steps.

C.7 How to Start Oracle9iAS InterConnect

The following sections describe how to start Oracle9iAS InterConnect.

C.7.1 Topology 1 and 3

1. Start the hub database. This is also the Oracle9iAS Infrastructure database.

2. Start the hub database listener.

3. Start Oracle Internet Directory.

   See the Oracle Internet Directory Administrator's Guide for details.

4. Start Oracle Management Server.

5. Start InterConnect Repository.

   Note: On both Windows NT and UNIX, you must run the start command from the repository directory, as indicated below.

   On UNIX, you use the start command.

   cd $ORACLE_HOME/oai/9.0.2/repository
   ./start
   
   

   On Windows NT, you can use the start.bat command or you can use the NT service for the repository:

   cd %ORACLE_HOME%\oai\9.0.2\repository
   .\start.bat
   
   

6. Use iStudio to design integration metadata.

   To start iStudio, use the following shortcut from the Start menu:

   Start > Programs > Oracle - ORACLE_HOME_NAME > Application Development

7. Start adapter(s).

   See the corresponding adapter documentation.

8. Start Oracle Enterprise Manager (installed as a part of Management Infrastructure).

C.7.2 Topology 2

1. Start the hub database. This is the Oracle8i or Oracle9i database.

2. Start the hub database listener.

3. Start Oracle Management Server.

4. Start InterConnect Repository.

   Note: On both Windows NT and UNIX, you must run the start command from the repository directory, as indicated below.

   On UNIX, you use the start command.

   cd $ORACLE_HOME/oai/9.0.2/repository
   ./start
   
   

   On Windows NT, you can use the start.bat command or you can use the NT service for the repository:

   cd %ORACLE_HOME%\oai\9.0.2\repository
   .\start.bat
   
   

5. Use iStudio to design integration metadata.

   To start iStudio, use the following shortcut from the Start menu:

   Start > Programs > Oracle - ORACLE_HOME_NAME > Application Development

6. Start adapter(s).

   See the corresponding adapter documentation.

7. Start Oracle Enterprise Manager (installed as a part of Management Infrastructure).

C.8 How to Change Passwords for the Oracle9iAS InterConnect and Oracle Workflow Schemas

You might need to change the passwords of the oaihub902 and owf_mgr schemas on a regular basis, depending on your company's security policy. How you change the passwords depends on the topology of your setup.

oaihub902 is the schema for Oracle9iAS InterConnect, and owf_mgr is the schema for Oracle Workflow.

C.8.1 Topology 1 and 3

To change passwords of the oaihub902 and owf_mgr schemas in the Infrastructure database:

1. Obtain the necessary system privileges to change schema passwords in the Infrastructure database.

   See the Oracle9iAS Administration Guide for details on changing schema passwords in the Infrastructure database.

2. Encrypt the new password using the encrypt utility in the $ORACLE_HOME/oai/9.0.2/bin directory.

   Run encrypt. The command prompts you to enter the password to encrypt.

3. Update the appropriate parameter in the .ini files with the encrypted password:

   Table C-8 Update files with encrypted password

   Enter the encrypted password for this schema	In this parameter	In this file	On these machines
   oaihub902	encrypted_hub_password	$ORACLE_HOME/oai/9.0.2/hub/hub.ini	Non-middle tier or Infrastructure machines
   owf_mgr	encrypted_aq_bridge_password	$ORACLE_HOME/oai/9.0.2/workflow/adapter.ini	Middle tier or Infrastructure machine

C.8.2 Topology 2

To change passwords of the oaihub902 and owf_mgr schemas in the Oracle database:

1. Obtain the necessary system privileges to change schema passwords in the database.

   See the Oracle database documentation for details on changing schema passwords.

2. Encrypt the new password using the encrypt utility in the $ORACLE_HOME/oai/9.0.2/bin directory. This is the InterConnect Oracle home (as opposed to the database Oracle home).

   Run encrypt. The command prompts you to enter the password to encrypt.

3. Update the appropriate parameter in the .ini files with the encrypted password: This is the InterConnect Oracle home (as opposed to the database Oracle home).

   Table C-9 Update files with encrypted password

   Enter the encrypted password for this schema	In this parameter	In this file	On these machines
   oaihub902	encrypted_hub_password	$ORACLE_HOME/hub/hub.ini	All machines
   owf_mgr	encrypted_aq_bridge_password	$ORACLE_HOME/workflow/adapter.ini	Hub machine

C.9 How to Create Multiple Repository Schemas in the Same Database

You created the first schema in the repository database when you ran the hub installation for any of the three topologies. If you need a second schema in the repository database, you can create it by following this procedure:

1. Run the installation procedure for topology 2, which is described in Section C.3.3, "Oracle9iAS InterConnect Hub Installation Steps for Topology 2".

   When the installer prompts you for database information, you enter hub information (database host, port, and SID) that is identical to the hub information in the first install.

2. Make a copy of the following files so that you have a copy of the original. You will be making changes to these files:
   • ORACLE_HOME/oai/9.0.2/repository/hubschema

   • ORACLE_HOME/oai/9.0.2/repository/oaiexport

   • ORACLE_HOME/oai/9.0.2/repository/oaiimport

   • ORACLE_HOME/oai/9.0.2/repository/sql/hub1.sql

   • ORACLE_HOME/oai/9.0.2/repository/sql/deinstall_schema.sql

   • ORACLE_HOME/oai/9.0.2/hub/hub.ini

3. Replace all occurrences of "oaihub902" with the name of the new schema in the original files.

   For example, if you want the new schema to be called "oaihub", you would replace "oaihub902" with "oaihub".

4. Execute the modified hubschema script to create the new hub user ("oaihub" in this example) in the hub database.

5. Run post-installation steps as described in Section C.3.4, "Oracle9iAS InterConnect Hub Post-Installation Steps (required for Oracle Workflow users only)".