|
Oracle® Application Server Integration Installation Guide
10g Release 2 (10.1.2) for Solaris Operating Environment (SPARC), Linux x86, and Microsoft Windows Part No. B16226-02 |
|
 Previous |
 Next |
|
Oracle® Application Server Integration Installation Guide
10g Release 2 (10.1.2) for Solaris Operating Environment (SPARC), Linux x86, and Microsoft Windows Part No. B16226-02 |
|
|
Previous |
Next |
This chapter provides the requirements and procedures for installing Oracle BPEL Process Manager.
This chapter contains the following topics:
Postinstallation Verification Tasks for Oracle BPEL Process Manager
Troubleshooting Oracle BPEL Process Manager Installation and Configuration
Oracle BPEL Process Manager provides a user-friendly and reliable solution for designing, deploying, and managing BPEL processes. When you install Oracle BPEL Process Manager, you are given two installation types, as shown in Table 1-1.
Table 1-1 Oracle BPEL Process Manager Installation Types
| Installation Type | Description |
|---|---|
| Oracle BPEL Process Manager for Developers | Provides a single environment for designing and running BPEL processes. The included components are JDeveloper BPEL Designer and BPEL Process Manager. This installation type is configured with an embedded Oracle Application Server Containers for J2EE and, on Windows only, uses Oracle Database Lite as its database. |
| Oracle BPEL Process Manager for OracleAS Middle Tier | Provides a standards-based environment for running processes designed using BPEL. This runtime environment includes Oracle BPEL Server, runtime services, and adapters. This installation type requires that an Oracle Application Server 10g J2EE middle tier already be installed in the chosen Oracle home. |
Oracle BPEL Process Manager consists of the key components shown in Figure 1-1. Oracle BPEL Process Manager runs standard BPEL processes. You deploy BPEL processes to Oracle BPEL Server.
The following components are included with Oracle BPEL Process Manager.
BPEL Designer—a graphical and user-friendly way to model, edit, design, and deploy BPEL processes. BPEL Designer also enables you to view and modify the BPEL source code. This component is available with Oracle JDeveloper or as a plug-in on the Eclipse Platform version 3.0GA and gets installed with Oracle BPEL Process Manager for Developers.
Oracle BPEL Server—the server to which you deploy the BPEL process that you design and that contains human workflow, technology adapters, and notification services components.
Oracle BPEL Console—the console from which you run, manage, and test your deployed BPEL process. Oracle BPEL Console provides a Web-based interface for management, administration, and debugging of processes deployed to Oracle BPEL Server.
Oracle Database Lite, on Windows—the database that holds your BPEL schema. This option gets installed with Oracle BPEL Process Manager for Developers on Windows only. For UNIX platforms and if you are using a multibyte character set, you must configure an Oracle database to test your deployed BPEL processes. See "Preinstallation Tasks for Oracle BPEL Process Manager" for details about configuring an Oracle database.
|
See Also:
|
Installation scenarios are described in the following sections:
|
Note: For information about other installation configurations, see:
|
Oracle BPEL Process Manager for Developers provides a design and standalone test environment. With this option, you design your process and then perform preproduction deployment and testing. Once you are ready to deploy a production version, you use the OracleAS Middle Tier option to deploy the BPEL process.
When you select Oracle BPEL Process Manager for Developers, you get these components:
JDeveloper BPEL Designer
BPEL Server
Oracle BPEL Console
Oracle Database Lite, on Windows only
Oracle BPEL Process Manager for OracleAS Middle Tier provides robust production components for running BPEL processes. Before installation, you configure your Oracle database for use with Oracle BPEL Process Manager by running the Integration Repository Creation Assistant (IRCA). This release of Oracle BPEL Process Manager does not support using OracleAS Metadata Repository.
When you select Oracle BPEL Process Manager for OracleAS Middle Tier, you get these components:
Oracle BPEL Server
Oracle BPEL Console
This section provides an overview of installation tasks to perform based on the type of installation used for Oracle BPEL Process Manager, and provides references to procedures for performing these tasks.
The Oracle BPEL Process Manager product CD-ROM contains the following files and directories at the top level:
README_BPEL.txt—The readme file for this release, which contains important information.
bpel—The directory that contains software to install.
doc—The directory that contains this installation guide.
IRCA.zip—The Integration Repository Creation Assistant zip archive, which is discussed later in this document.
Installation Tasks Summary and Where to Find Procedures
Table 1-2 provides a summary of installation tasks to perform for Oracle BPEL Process Manager for Developers if you plan to use an Oracle Database instead of Oracle Database Lite.
Table 1-3 provides an overview of installation tasks to perform for Oracle BPEL Process Manager for OracleAS Middle Tier.
|
Note: If you plan to install Oracle BPEL Process Manager for Developers on Windows, then you can go directly to "Installing Oracle BPEL Process Manager for Developers". There are no preinstallation tasks. |
Table 1-2 Oracle BPEL Process Manager for Developers
| For Database | Follow These Steps... | See Also... |
|---|---|---|
| Oracle Database 10g (10.1)
or Oracle9i Database release 9.2.0.5.0 or later |
Oracle Database Installation Guide 10g
or Oracle Database Installation Guide 9i for your platform |
|
|
|
"Step 4: Download and Apply Mandatory Patches"
|
|
|
|
|
"Installing Oracle BPEL Process Manager for Developers" of this guide |
|
|
|
"Step 3: Optional - Configure Oracle BPEL Process Manager to Use Your Oracle Database" of this guide |
Table 1-3 Oracle BPEL Process Manager for OracleAS Middle Tier
| For Database | Follow These Steps... | See Also... |
|---|---|---|
| Oracle Database 10g (10.1) or Oracle9i Database release 9.2.0.5.0 or later | Oracle Database Installation Guide 10g
or Oracle Database Installation Guide 9i for your operating system |
|
|
|
"Step 4: Download and Apply Mandatory Patches"
|
|
|
|
|
Oracle Application Server Installation Guide for your operating system |
|
|
"Installing Oracle BPEL Process Manager for OracleAS Middle Tier" of this guide |
Table 1-4 describes the system requirements for Oracle BPEL Process Manager
Table 1-4 Oracle BPEL Process Manager System Requirements
Table 1-5 lists information about Oracle Database for your Oracle BPEL Process Manager installation.
You may use your existing Oracle database, if it meets the requirements shown in Table 1-5.
Table 1-5 Supported Oracle Databases
| Oracle Database | Oracle BPEL Process Manager for Developers | Oracle BPEL Process Manager for OracleAS Middle Tier |
|---|---|---|
| Oracle Database Lite | Included on Windows installations only
Refer to the note in this section about multibyte character set support |
n/a |
| Oracle Database 10g
|
Recommended for UNIX installations | Recommended |
| Oracle9i Database release 9.2.0.5.0 or later | Supported | Supported |
Depending on the platform and Oracle database that you plan to use, complete the following procedures that apply to your installation.
|
Note: On the Windows platform, Oracle Database Lite is included with the installation. If you use this configuration, skip the preinstallation procedures in this section and go directly to "Installing Oracle BPEL Process Manager for Developers". |
On UNIX platforms, an Oracle Database is required for Oracle BPEL Process Manager for Developers. (If you already have an Oracle database that meets this requirement, then you do not need to reinstall the database.)
For UNIX platforms, complete the following steps:
For Oracle BPEL Process Manager for OracleAS Middle Tier, the preinstallation steps are as follows:
Step 1: Install the Oracle Database - If Not Already Installed
Step 5: If Installing on a Cold Failover Cluster (CFC) Middle Tier
An Oracle database is required to be your dehydration store for all Oracle BPEL Process Manager instances. If you already have an Oracle database that meets the requirements, then you do not need to reinstall the database. Otherwise, install or upgrade before you proceed.
|
See Also:
|
Run IRCA to create the database user and schema. IRCA creates the default user orabpel and the default password orabpel on the tablespace ORABPEL that it creates in the Oracle database.
If you previously installed Oracle BPEL Process Manager for Developers and you already ran IRCA on this Oracle database, then you do not need to run IRCA again.
If you already have an Oracle BPEL Process Manager user (orabpel) in the target database, then stop all sessions, activity, and transactions for the user before running IRCA.
You must run IRCA from the host where your Oracle database is installed, and your database must be up and running before you run IRCA.
IRCA is located in the root directory on the Oracle BPEL Process Manager product CD-ROM in IRCA.zip.
IRCA does not support Oracle Application Server Metadata Repository.
To run IRCA:
Copy IRCA.zip to the host where the Oracle database is installed.
Extract IRCA.zip to a temp directory of the host system, being sure to preserve path information.
From a command window, run irca.bat on Windows or irca.sh on UNIX.
Provide the database details shown in Table 1-6 when prompted. Be sure to record the information that you provide because you need this in subsequent installation steps.
|
Important: Change theorabpel user password after you run IRCA, and make a note of your new password for subsequent steps.
|
Table 1-6 IRCA Prompts for Information
| Prompt | Description | Example |
|---|---|---|
| Enter Database Oracle Home | Your Oracle_Home
|
C:\OraHome_1\
|
Enter JDK 1.4 location <default path>
|
Accept the default path for the Oracle database. Otherwise, if you downloaded JDK 1.4 separately, then give its location. | C:\oracle\product\10.1.0\Db_1\jdk
|
| Enter database host [localhost] | The full name or IP address of your database host. | hr1-pc.us.acme.com
or
|
| Enter database port [1521] | The database listener port. The default is 1521. | 1521
|
| Enter database service name [orcl] | The service name that you specified when you installed the database. The default service name is orcl, which may be prepended to the fully qualified domain name (FQDN) for your database.
Note that this is not the SID. If you are not sure, then run the SQL*Plus command |
orcl
or
|
| Enter sys password | The database sys user password.
|
8x9cv55
|
Install Oracle Application Server 10g Release 2 (10.1.2) and select the J2EE and Web Cache installation type.
|
See Also: Oracle Application Server Installation Guide for your operating system |
|
Note: The patch described in this section must be applied prior to installing Oracle BPEL Process Manager for OracleAS Middle Tier |
You must download and install the patch described in this procedure before you install the product. The file README.txt included in the zip archive that you download provides more information about this patch.
To download the patch:
Log in to:
http://metalink.oracle.com
Select Patches and Updates from the navigation bar.
Select Simple Search.
Search by Patch Number for 4343748. This patch is generic for all platforms, so accept the default for the Platform or Language field.
To apply the patch:
Unzip ppatch_number_101200_GENERIC.zip to a temporary directory such as temp and specify All files and Use folder names.
The subdirectories and files are extracted to a directory named for the patch number in the location that you specified (for example, \4343748). The README.txt file is located in this directory.
Open a command window.
Set Oracle_Home to the Oracle home that needs to be patched.
Set your environment PATH to include Oracle_Home/OPatch.
Stop all process running from the Oracle_Home.
Change to the patch_number directory.
Enter the command:
opatch apply
If you have any problems installing this patch, call Oracle Support Services.
If you are installing on a Cold Failover Cluster (CFC) middle tier, the following steps are required after installation of the middle tier and before you install Oracle BPEL Process Manager.
Configure the middle tier for a CFC environment.
See Oracle Application Server Installation Guide for your operating system for this step.
Check the Midtier_Home/config/ias.properties file and make sure that the value of the property VirtualHostName is correct for the VirtualHostName of the CFC middle tier.
After you complete the steps in this section, you are ready to continue with the installation.
Follow these instructions to install BPEL Process Manager:
This installation type installs both the JDeveloper BPEL Designer and Oracle BPEL Process Manager.
Ensure that all preinstallation tasks and requirements described in "Preinstallation Tasks for Oracle BPEL Process Manager" have been completed.
Log on to the host on which to install Oracle BPEL Process Manager components.
Insert the Oracle BPEL Process Manager CD-ROM.
Start Oracle Universal Installer from the bpel directory of the CD-ROM as follows:
| On... | Do This... |
|---|---|
| UNIX | Enter the following command at the operating system prompt:
|
| Windows | Click setup.exe.
|
The Welcome screen appears.
Click Next.
If your host is detected to be part of a cluster, the Specify Hardware Cluster Installation Mode screen appears. Select Noncluster Installation. This installs Oracle BPEL Process Manager on this node only, and not as part of a cluster node. Do not select Cluster Installation.
The Specify File Locations screen appears.
Accept the default Name and Path, or specify a new Oracle home name and directory path in which to install Oracle BPEL Process Manager components.
Do not use an existing home name and directory path.
On UNIX:
Name: BPELPM1012 Path: /home/oracle/BPELPM1012
On Windows:
Name: BPELPM1012 Path: C:\Oracle\BPELPM1012
Do not change the directory path in the Source field. This is the location of installation files.
Click Next.
The Select Installation Type screen appears.
Table 1-1, "Oracle BPEL Process Manager Installation Types" describes the available installation types.
Select BPEL Process Manager for Developers and click Next.
The Specify Outgoing HTTP Proxy Information screen appears.
|
Note: This information is automatically filled in on Windows platforms if your Internet Explorer has been configured for Proxy Server information under LAN Settings on the Connections tab.If your Internet Explorer is using Automatic Configuration of proxies, then you must fill in this information. |
If you have a direct connection to the Internet and do not use a proxy server, or if you accept the default information, then click Next.
Otherwise, enter the information as shown in Table 1-7.
Table 1-7 Outgoing HTTP Proxy Information
| Field | Description | Example |
|---|---|---|
| HTTP Proxy Host | Enter the name of the proxy server host. | www-proxy.us.acme.com
|
| HTTP Proxy Port | Enter the port number of the proxy server host. | 80
|
| Bypass proxy for addresses | Enter an address that bypasses the proxy. You may enter more than one address, separating each with a semi-colon (;). | *.us.acme.com;*.us.acme.com;<local>
Note: The |
The Summary screen appears.
Click Install.
The Install screen appears showing the installation progress.
When installation completes, the End of Installation screen appears with information for your review.
Click Exit and confirm when prompted.
The Getting Started page appears.
This completes the installation procedures. Verify the installation, as described in "Postinstallation Verification Tasks for Oracle BPEL Process Manager".
To install Oracle BPEL Process Manager for OracleAS Middle Tier:
Ensure that all preinstallation tasks and requirements described in "Preinstallation Tasks for Oracle BPEL Process Manager" have been completed.
Log on to the host on which to install Oracle BPEL Process Manager components.
Insert the Oracle BPEL Process Manager CD-ROM.
Start Oracle Universal Installer from the bpel directory of the CD-ROM as follows:
| On... | Do This... |
|---|---|
| UNIX | Enter the following command at the operating system prompt:
|
| Windows | Click setup.exe.
|
The Welcome screen appears.
Click Next.
If your host is detected to be part of a cluster, the Specify Hardware Cluster Installation Mode screen appears. Select Noncluster Installation. This installs Oracle BPEL Process Manager on this node only, and not as part of a cluster node. Do not select Cluster Installation.
The Specify File Locations screen appears.
Select the Oracle home name and directory path where Oracle Application Server 10.1.2 J2EE and Web Cache is located.
Do not accept the default Name and Path. The installer looks for the Oracle Application Server 10.1.2 J2EE and Web Cache instance. If you specify an incorrect path, the Dependencies alert appears.
On UNIX:
Name: Home1 Path: /home/oracle/OraHome_1
On Windows:
Name: Home1 Path: C:\OraHome_1
Do not change the directory path in the Source field. This is the location of installation files.
Select BPEL Process Manager for OracleAS Middle Tier and click Next.
The Specify Outgoing HTTP Proxy Information screen appears.
If you have a direct connection to the Internet and do not use a proxy server, or if you accept the default information, then click Next.
Otherwise, enter the information as shown in Table 1-7, "Outgoing HTTP Proxy Information".
The Specify Instance Repository Information screen appears.
In the Specify Instance Repository Information screen, provide the details as described in the following table:
| Information | Description | Example |
|---|---|---|
| Password for BPEL Process Manager Schema (ORABPEL): | The password that IRCA assigns to the user orabpel. You changed this password after you ran IRCA.
For information about the |
********
|
| Hostname:Port | The full name or IP address of your database host and the listener port. The default listener port is 1521.
|
my-pc.acme.com:1521
or
|
| Service Name: | The service name that you specified when you installed the database. The default service name is orcl, which may be prepended to the fully qualified domain name (FQDN) for your database.
Note that this is not the SID. If you are not sure, then run the SQL*Plus command |
orcl
or
|
| ias_admin Password: | The password for the Oracle Application Server middle tier in which you are installing. You specified this password when you installed Oracle Application Server with J2EE and Web Cache. | *******
|
Click Next. (Note that it takes a few minutes for the database connection to be established.)
The Summary screen appears.
Click Install.
The Installation Progress screen appears for a few seconds, and then the Configuration Assistants screen appears with Oracle BPEL Process Manager Configuration Assistant.
When installation completes, the End of Installation screen appears with information for your review.
Click Exit and confirm when prompted.
The Getting Started page appears.
This completes the installation procedures. Verify the installation, as described in "Postinstallation Verification Tasks for Oracle BPEL Process Manager".
After installing Oracle BPEL Process Manager, complete the following required tasks and then complete the additional tasks depending on the type of installation you are performing.
Required Postinstallation Steps for Oracle BPEL Process Manager
Postinstallation Steps for Oracle BPEL Process Manager for Developers
Postinstallation Step for Oracle BPEL Process Manager for OracleAS Middle Tier
|
Note:
|
Complete these procedures for all installations of Oracle BPEL Process Manager.
It is important to change default passwords before you start using the product.
A domain named default is automatically installed with Oracle BPEL Process Manager. The initial password for this domain is bpel. Change this password immediately after installation is complete.
You create BPEL domains and configure Oracle BPEL server properties from Oracle BPEL Admin Console. The password for Oracle BPEL Admin Console is automatically set to oracle. Change this password immediately after installation.
|
See Also: Oracle BPEL Process Manager Developer's Guide for procedures on changing passwords |
In order to use the notification service and workflow applications, you must complete the following steps.
Configure the e-mail server settings as described in Oracle BPEL Process Manager Developer's Guide in the Oracle BPEL Process Manager Notification Service chapter. The e-mail server settings are used to send and receive e-mails by the Notification and Workflow services.
Acting on workflow tasks through e-mail requires that you configure the actionable e-mail account as described in Oracle BPEL Process Manager Developer's Guide in the Oracle BPEL Process Manager Workflow Services chapter.
If the notification service is to be used to send notifications using voice or short message service (SMS) channels, then the wireless service settings must be configured as described in the section that describes configuring the wireless service provider for voice in the Oracle BPEL Process Manager Notification Service chapter of Oracle BPEL Process Manager Developer's Guide.
Oracle BPEL Process Manager ships with a large set of samples that demonstrate various features of the product. Update your samples immediately following installation to ensure that you have the latest.
The samples are updated frequently to correct known issues, update and add new readme files, and add new samples. The latest samples update can be found at:
http://www.oracle.com/technology/bpel
Please make it a point to visit the Oracle BPEL Process Manager Web site for updates on a periodic basis.
|
Note: Oracle BPEL Process Manager must be restarted for changes to take effect. |
The procedures in this section are necessary only if you are using Oracle BPEL Process Manager for Developers.
Step 3: Optional - Configure Oracle BPEL Process Manager to Use Your Oracle Database
Step 4: Optional - Configure the Startup File to Use the Oracle database
Step 5: Optional - Configure JDeveloper BPEL Designer to Use Online Help from a Local Disk
|
Note: The patch described in this section must be applied after installing Oracle BPEL Process Manager for Developers and before you use the product. |
You must download and install the patch described in this procedure before you start Oracle BPEL Process Manager Server for the first time. The file README.txt included in the zip archive that you download provides more information about this patch.
To download the patch:
Log in to:
http://metalink.oracle.com
Select Patches and Updates from the navigation bar.
Select Simple Search.
Search by Patch Number for 4369818. This patch is generic for all platforms, so accept the default for the Platform or Language field.
To apply the patch:
Unzip ppatch_number_101200_GENERIC.zip to a temporary directory such as temp and specify All files and Use folder names.
The subdirectories and files are extracted to a directory named for the patch number in the location that you specified. The README.txt file is located in this directory.
Open a command window.
Set Oracle_Home to the Oracle home that needs to be patched.
Set your environment PATH to include Oracle_Home/OPatch.
Stop all processes running from the Oracle_Home.
Change to the patch_number directory.
Enter the command:
opatch apply
If you have any problems installing this patch, call Oracle Support Services.
You must add the hostname of your computer to the Oracle JDeveloper preference settings. If you do not do this, you can receive parsing errors when selecting a WSDL file on the WSDL Chooser window while creating a partner link. Additionally, this procedure ensures that you can access the online help from the Oracle JDeveloper Web site on the Oracle Technology Network.
Select Preferences from the Tools main menu.
Click Web Browser and Proxy.
Enter the hostname of your host in the Exceptions field. For example, if your hostname is myhost-pc:
us.acme.com|*.us.acme.com|localhost|127.0.0.1|myhost-pc
Ensure that localhost appears in the Exceptions field.
Click OK.
This procedure is required for Oracle BPEL Process Manager for Developers on UNIX, if you want to use an Oracle database as your dehydration database on Windows, or if you require multibyte character set support.
To configure the Oracle database to use Oracle BPEL Process Manager:
Find the Oracle BPEL Process Manager data-sources.xml file located in the config directory under the destination path that you specified during installation. For example, on Windows:
C:\BPELPM1012\integration\orabpel\system\appserver\oc4j\j2ee\home\config
Make a backup copy of the data-sources.xml file.
Edit the data-sources.xml file in a text editor as follows.
Search for the heading Use this datasource to connect to Oracle 9i.
Uncomment the data-source elements under this heading.
Edit the connection parameters indicated in bold in this example.
<!-- Use this datasource to connect to Oracle 9i --> <data-source class="com.evermind.sql.DriverManagerDataSource" name="BPELServerDataSource" location="loc/BPELServerDataSource" xa-location="BPELServerDataSource" ejb-location="jdbc/BPELServerDataSource" connection-driver="oracle.jdbc.OracleDriver" max-connections="50" min-connections="10" connection-retry-interval="30" max-connect-attempts="10" url="jdbc:oracle:thin:username/password@host:port:sid"/>
where the default username is orabpel and the default password is orabpel. The host is the fully qualified name or IP address of the host on which you installed Oracle Database 10g or Oracle9i Database release 9.2.0.5.0 or later. The default port number is 1521.
An example of the connection parameters is:
url="jdbc:oracle:thin:orabpel/orabpel@DB_Host:1521:DB_SID"/>
Search for the heading Use these datasources to connect to Oracle Lite.
Comment out the entire section under this heading. For example:
<!-- Use these datasources to connect to Oracle Lite -->
<!--
<data-source class="com.evermind.sql.DriverManagerDataSource"
name="BPELServerDataSource"
location="loc/BPELServerDataSource"
xa-location="BPELServerDataSource"
ejb-location="jdbc/BPELServerDataSource"
connection-driver="oracle.lite.poljdbc.POLJDBCDriver"
username="system"
password="any"
max-connections="30"
min-connections="10"
...
-->
Save the data-sources.xml file.
For Windows only, if you are using the Oracle database, then you must configure startorabpel.bat to use the Oracle database instead of Oracle Database Lite. This procedure only applies for Windows installations.
Find the startorabpel.bat file located in the bin folder under the destination path that you specified during installation. For example, on Windows:
C:\BPELPM1012\integration\orabpel\bin
Make a backup copy of the startorabpel.bat file.
Edit the startorabpel.bat file as follows:
Remove or comment out two lines that call Oracle Database Lite as shown.
@rem call "C:\BPELPM1012\integration\orabpel\bin\kill_olite.bat"
and
@rem start /d "C:\BPELPM1012\integration\orabpel\bin" /min /realtime start_olite.bat
Save the startorabpel.bat file.
The procedure in this section is optional and only helpful if you want to use online help from a local disk. Online help for Oracle JDeveloper is available from the Oracle JDeveloper Web site. Therefore, to use the most current online help from the Web, ensure that you have an external connection to access the files.
To install the online help to use locally:
Download jdev1012_doc.zip from the Oracle JDeveloper documentation page on Oracle Technology Network at:
Install the documentation into Oracle JDeveloper by extracting the files into the directory where Oracle JDeveloper is installed.
The jdev_install\jdev\doc\ohj directory is created, as well as the jdev_install\jdev\tutorials directory.
From the JDeveloper BPEL Designer Tools menu, select Preferences and then Documentation.
Select Use Local Documentation.
If you install the documentation into any other local directory, then you need to configure the location in JDeveloper as follows:
Start JDeveloper BPEL Designer.
Select Tools > Preferences > Documentation from the JDeveloper main menu.
Select Use Local Documentation.
Set the full path to where the local documentation is installed.
Click OK.
|
Note: Oracle BPEL Process Manager must be restarted for changes to take effect. |
This section helps you verify your installation of Oracle BPEL Process Manager. Completing these steps help confirm a fully functional installation of the various installed components.
Table 1-8 provides instructions for accessing the various components.
Table 1-8 Accessing Oracle BPEL Process Manager Components
|
See Also:
|
Follow these steps to successfully install Oracle BPEL Process Manager on a processor farm or server cluster.
|
See Also: Oracle Application Server Installation Guide for your operating system |
Install Oracle Application Server 10g Release 2 (10.1.2) on server 1.
Install Oracle Application Server 10g Release 2 (10.1.2) on server 2.
Go to Oracle Enterprise Manager 10g Application Server Control Console of the first middle tier (server 1), and perform the following steps:
Go to OracleAS Infrastructure and configure a farm repository. You may create a file-based repository.
Note the ID of the farm repository you just created.
After you configure the farm repository, stop all Oracle Process Manager and Notification Server (OPMN) processes and stop Oracle Enterprise Manager 10g Application Server Control Console on middle tier server 1.
Start OPMN and Application Server Control Console again on middle tier server 1. This synchronizes the farm repository.
Go to Application Server Control Console on the second middle tier (server 2), and perform the following steps:
Go to OracleAS Infrastructure and configure a farm repository. You may create a file-based repository
Click Add to an existing Farm repository and Provide the repository Id at joining time.
Stop all OPMN and Application Server Control Console for middle tier servers 1 and 2.
Start OPMN and Application Server Control Console again on middle tier servers 1 and 2.
Install Oracle BPEL Process Manager on middle tier server 1.
Using Application Server Control Console, create a cluster on middle tier server 1.
Add middle tier server 1 to the cluster.
Perform a stop and start of OPMN and Oracle Enterprise Manager 10g Application Server Control Console on all farm members. This ensures that the farm repositories are still synchronized.
Install Oracle BPEL Process Manager on middle tier server 2.
Add middle tier server 2 to the cluster. (This step takes a long time to complete.)
This section provides information about globalization and optional considerations.
Oracle BPEL Console is available in the following languages: French, German, Italian, Spanish, Portuguese, Japanese, Korean, Simplified Chinese, and Traditional Chinese. JDeveloper BPEL Designer is only available in English and Japanese. Oracle BPEL Console and JDeveloper BPEL Designer retrieve and display text message from Oracle BPEL Server in the server locale on certain pages. To avoid mixed languages being displayed, make sure Oracle BPEL Console and Oracle BPEL Server are using the same locale.
You can determine the version number of Oracle BPEL Process Manager for support purposes.
To check your JDeveloper BPEL Designer version:
Start JDeveloper BPEL Designer and select About from the Help menu. Look for the line BPEL Designer.
To check the Oracle BPEL Server version on Windows:
Select Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager 10.1.2 and select Developer Prompt.
Enter obversion at the command prompt.
To check the Oracle BPEL Server version on UNIX:
Go to $ORACLE_HOME/integration/orabpel/bin and run obversion.sh.
Table 1-9 shows the directory structure that is created after completing the installation of JDeveloper BPEL Designer and Oracle BPEL Process Manager.
Table 1-9 Directory Structure for Oracle BPEL Process Manager Installed Components
| This Directory | Contains... |
|---|---|
cfgtoollogs
|
Oracle Universal Installer configuration tools logs. |
diagnostics
|
Oracle Universal Installer diagnostic information. |
integration
|
These subdirectories: |
Note: This directory is installed with the BPEL Process Manager for Developers option only |
|
|
|
integration/orabpel
|
These subdirectories: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
inventory
|
Oracle installed products. |
jdk
|
The required Java Developer's Kit version. |
jre
|
Java runtime environment files and libraries. |
lib
|
Servlet jar file. |
OPatch
|
The opatch utility and files to help patch components within this product.
|
oui
|
Oracle Universal Installer. |
perl
|
The required version of Perl for the opatch utility.
|
Follow these instructions to deinstall Oracle BPEL Process Manager:
Start Oracle Universal Installer.
| On... | Do This... |
|---|---|
| UNIX | Enter the following command at the operating system prompt:
|
| Windows | Select Start > All Programs > Oracle - Oracle_Home > Oracle Installation Products > Oracle Universal Installer |
Select Deinstall Products.
Expand the Oracle home that contains the products to deinstall.
Select Oracle BPEL Process Manager.
Click Yes when prompted.
The deinstallation does not remove files created after installation (for example, project files, server files, log files, and so on). You must manually remove these files and directories. Oracle recommends that you delete the integration directory under your Oracle home after backing up any required files.
|
Note:
|
This section contains troubleshooting tips and information for issues that you can encounter.
The server timeout value is specified by the transaction-config timeout parameter in the server.xml file located in Oracle_Home\j2ee\OC4J_BPEL\config. The default value of the transaction-config timeout parameter is "60000" milliseconds, or one minute, which may not be optimal for your server load.
This value can be adjusted along with the syncMaxWaitTime in the domain configuration file domain.xml, which is located in Oracle_Home\integration\orabpel\domains\default\config\. In general, syncMaxWaitTime should always be less than transaction-config timeout in server.xml.
To change the transaction-config timeout parameter:
Go to Oracle_Home\j2ee\OC4J_BPEL\config\, and open the file server.xml in a text editor.
Find the line for the transaction-config timeout parameter. For example:
<transaction-config timeout="60000" />
Change the value to a greater duration. An example that sets the duration to five minutes is as follows:
<transaction-config timeout="300000" />
Change the syncMaxWaitTime parameter through Oracle BPEL Admin Console. Alternatively, to change the syncMaxWaitTime setting manually:
Go to Oracle_Home\integration\orabpel\domains\default\config\ and open the file domain.xml in a text editor.
Find the line for syncMaxWaitTime. For example:
<property id="syncMaxWaitTime">
Change the value to a greater duration, making sure that this is less than the duration you set for transaction-config timeout. For example:
<property id="syncMaxWaitTime">
<name>Delivery result receiver maximum wait time</name>
<value>120</value>
The default is 45 seconds, and in this example the duration is changed to 120 seconds, or three minutes.
Alternatively, you can reduce the database activity to the BPEL dehydration database. For example, you can change the AuditLevel value to "production" to reduce the database activity. However, doing so takes away some of the useful information from the Console Audit instances details in the Oracle Enterprise Manager 10g Application Server Control Console.
With slow processors, heavily loaded systems, or very large numbers of business processes, Oracle Application Server Containers for J2EE (OC4J) may time out while Oracle BPEL Process Manager is shutting down. If this occurs, then Oracle Enterprise Manager 10g Application Server Control Console displays an error message.
To prevent Oracle Application Server Containers for J2EE from timing out with Oracle BPEL Process Manager, you can increase the Stop Timeout parameter in opmn.xml to 3 or 4 minutes.
In environments where your data files are not stored as regular text, create the ORABPEL tablespace prior to running IRCA. For example, if your data files reside on a raw file system, or Veritas, then IRCA cannot create the ORABPEL tablespace. However, if you manually create the tablespace and then run IRCA, it automatically detects that the tablespace exists and continues to configure the user and schema. Note that IRCA runs properly with Automatic Storage Management (ASM).
To create the ORABPEL tablespace manually, use the following SQL statements:
CREATE TABLESPACE ORABPEL
DATAFILE '/dev/vx/rdsk/dg2/1024m_6' SIZE 100M
AUTOEXTEND ON NEXT 30M MAXSIZE UNLIMITED;
The metrics for Start Time, CPU Usage, and Memory Usage for Oracle BPEL Process Manager are displayed as "Not Yet Available" in Oracle Enterprise Manager 10g Application Server Control Console. To see these metrics for Oracle BPEL Process Manager, go to the page for Oracle Application Server Containers for J2EE.
Oracle BPEL Console uses the Oracle Application Server Web Cache port in this release. Therefore, both Oracle HTTP Server and Oracle Application Server Web Cache must be running in order for BPEL server processes to be available. You can start these processes from Oracle Enterprise Manager 10g Application Server Control Console by selecting the process and clicking Start.
Alternatively, you can start the processes from the Developer Prompt as follows.
To start Oracle HTTP Server, enter:
opmnctl startproc process-type=HTTP_server
To start Oracle Application Server Web Cache, enter:
opmnctl startproc process-type=WebCache
