|
Oracle® BPEL Process Manager Installation Guide
10g Release 2 (10.1.2) for Solaris Operating Environment (SPARC), Linux x86, and Microsoft Windows Part No. B25760-05 |
|
 Previous |
 Next |
|
Oracle® BPEL Process Manager Installation Guide
10g Release 2 (10.1.2) for Solaris Operating Environment (SPARC), Linux x86, and Microsoft Windows Part No. B25760-05 |
|
|
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
|
Note: The installation procedures in this chapter are only for performing a completely new installation of Oracle BPEL Process Manager.If you are migrating from an Oracle BPEL Process Manager release 10.1.2.0.0 installation to release 10.1.2.0.2, do not follow the instructions in this chapter. Instead, see Chapter 5, "Oracle BPEL Process Manager Migration" for procedures. |
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_OC4J.txt—The readme file for this release, which contains important information
bpel_oc4j—The directory that contains software to install
doc—The directory that contains this installation guide
sql—The directory that contains the Oracle Application Server Metadata Repository 10.1.2.0.2 upgrade script:
upgrade_202_203_oracle.sql
This script automatically executes sensor_oracle.sql (also located in the sql directory).
Installation Tasks Summary and Where to Find Procedures
Table 2-1 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.
|
Note: If you plan to install Oracle BPEL Process Manager for Developers on Windows with Oracle Database Lite, then you can go directly to "Installing Oracle BPEL Process Manager for Developers". The preinstallation tasks in Table 2-1 are not required. |
Table 2-1 Oracle BPEL Process Manager for Developers
| For Database | Follow These Steps... | See Also... |
|---|---|---|
| Oracle Database 10g
or Oracle9i Database or Microsoft SQL Server
|
|
Oracle Database Installation Guide 10g
or Oracle Database Installation Guide 9i for your platform or Appendix A, "Using Microsoft SQL Server as the Dehydration Store" |
|
||
|
"Installing Oracle BPEL Process Manager for Developers" of this guide | |
|
"Step 2: May be Needed - Configure Oracle BPEL Process Manager to Use Your Oracle Database" of this guide
or Appendix A, "Using Microsoft SQL Server as the Dehydration Store" |
Table 2-2 provides an overview of installation tasks to perform for Oracle BPEL Process Manager for OracleAS Middle Tier.
Table 2-2 Oracle BPEL Process Manager for OracleAS Middle Tier
| For | Follow These Steps... | See Also... |
|---|---|---|
| Oracle Database 10g or Oracle9i Database
or Oracle Application Server Metadata Repository or Microsoft SQL Server |
|
Oracle Database Installation Guide 10g
or Oracle Database Installation Guide 9i for your operating system or Oracle Application Server Installation Guide for your operating system or Appendix A, "Using Microsoft SQL Server as the Dehydration Store" |
|
"Step 2: Run the Oracle Application Server Metadata Repository Creation Assistant on the Oracle Database"
or "Step 4: Upgrade the BPEL Schema Version" or Appendix A, "Using Microsoft SQL Server as the Dehydration Store" |
|
| Oracle Application Server Installation Guide for your operating system | ||
| "Installing Oracle BPEL Process Manager for OracleAS Middle Tier" of this guide |
Depending on the platform and 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 plan to use Oracle Database Lite as your dehydration store, 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 for this purpose, then you do not need to reinstall the database.)
Complete the following steps on UNIX:
For Oracle BPEL Process Manager for OracleAS Middle Tier, the preinstallation steps are as follows:
Step 1: Install the Database - If Not Already Installed
These steps are required for an Oracle Database:
These steps are required for Oracle Application Server Metadata Repository:
This section lists the preinstallation steps to follow for Oracle BPEL Process Manager installation. Perform the steps that are appropriate and necessary for your install type, as described earlier in "Steps for Oracle BPEL Process Manager for Developers" and "Steps for Oracle BPEL Process Manager for OracleAS Middle Tier".
One of the following databases is required as a dehydration store for Oracle BPEL Process Manager for OracleAS Middle Tier:
An Oracle Database
An Oracle Database can be used as a dehydration store for Oracle BPEL Process Manager for Developers on UNIX platforms.
Oracle Application Server Metadata Repository
Microsoft SQL Server
At this time, the only non-Oracle database supported as a dehydration store database is Microsoft SQL Server.
If you already have an Oracle Database that meets the requirements listed in "Supported Databases" , then you do not need to reinstall the database. Otherwise, install or upgrade before you proceed.
|
See Also:
|
Oracle Application Server Metadata Repository
|
Note: As a general best practice, Oracle recommends that you use an Oracle Database on which you run Oracle Application Server Metadata Repository Creation Assistant as the dehydration store database instead of using the Oracle Application Server Metadata Repository installed with Oracle Application Server Infrastructure. |
An Oracle Application Server installation can serve as the BPEL Process Manager dehydration store in these topologies:
Oracle Application Server Metadata Repository only
Oracle Application Server Metadata Repository with Oracle Identity Management
The steps are as follows:
Install an Oracle Application Server Metadata Repository based on Oracle Application Server 10.1.2.0.2.
Run the upgrade script to upgrade the BPEL schema from version 2.0.2 to version 2.0.3 in "Step 4: Upgrade the BPEL Schema Version".
|
See Also:
|
Microsoft SQL Server
At this time, the only non-Oracle database supported as a dehydration store database is Microsoft SQL Server.
|
Note: This step is not meant for use when the Oracle Application Server Metadata Repository installed with Oracle Application Server Infrastructure is the dehydration store. |
Run the Oracle Application Server Metadata Repository Creation Assistant to create the database user and schema. Oracle Application Server Metadata Repository Creation Assistant creates the default user orabpel, the default password orabpel, and the tablespace orabpel in the Oracle Database.
If you previously installed Oracle BPEL Process Manager for Developers and you already ran Oracle Application Server Metadata Repository Creation Assistant on this Oracle Database, then you do not need to run it again.
If you already have an Oracle BPEL Process Manager user (orabpel) in the target database, then stop all sessions, activities, and transactions for the user before running Oracle Application Server Metadata Repository Creation Assistant. This involves shutting down Oracle BPEL Server, Oracle BPEL Console, and JDeveloper BPEL Designer.
Oracle recommends that you create the orabpel tablespace with auto segment space management turned on. This enables you to conveniently reclaim free space in the dehydration store.
|
See Also:
|
|
Note: Unlocking theorabpel account is necessary if you are installing Oracle BPEL Process Manager for an Oracle Application Server Metadata Repository without Oracle Identity Management (the repository is not registered with Oracle Internet Directory). If the repository is registered with Oracle Internet Directory, the account is not locked; instead, you must find out the password to proceed with "Step 4: Upgrade the BPEL Schema Version". Instructions for both situations, whether or not the Oracle Application Server Metadata Repository is registered with Oracle Internet Directory, are provided here.
|
If the Oracle Application Server Metadata Repository is not registered with Oracle Internet Directory, you must unlock the Oracle BPEL Process Manager user account orabpel and unlock the schema password as follows:
Start SQL*Plus:
sqlplus /nolog
Connect to the OracleAS Metadata Repository:
CONNECT / AS SYSDBA
Unlock the Oracle BPEL Process Manager account:
ALTER USER orabpel IDENTIFIED BY orabpel ACCOUNT UNLOCK;
For security reasons, Oracle recommends that you then change the account password:
ALTER USER orabpel IDENTIFIED BY new_orabpel_passwd;
If installing on an Oracle Application Server Metadata Repository with Oracle Identity Management (that is, the repository is registered with Oracle Internet Directory), the Oracle BPEL Process Manager orabpel user account is not locked and the password does not require changing. Instead, you must first obtain the orabpel account password with a tool like ldapsearch; obtaining the password enables you to log in as orabpel/random_password.
ldapsearch can be used as follows:
ldapsearch Syntax:
$Oracle_Home/bin/ldapsearch -h oid_host -p oid_port -D "cn=orcladmin" -w orcladmin_passwd -b "orclresourcename=ORABPEL, orclreferencename=oid_global_db_name, cn=ias infrastructure databases, cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=top" orclpasswordattribute
ldapsearch Example:
$Oracle_Home/bin/ldapsearch -h sti6rb03.idc.oracle.com -p 389 -D "cn=orcladmin" -w welcome1 -b "orclresourcename=ORABPEL, orclreferencename=orcloid.idc.oracle.com, cn=ias infrastructure databases, cn=ias, cn=products, cn=oraclecontext" -s base "objectclass=top" orclpasswordattribute
|
See Also: The following documentation for details on usingldapsearch:
|
|
Note: This step is only required if you are using the 10.1.2.0.2 Oracle Application Server Metadata Repository installed with Oracle Application Server Infrastructure. Ignore this step if you manually ran Oracle Application Server Metadata Repository Creation Assistant on an Oracle Database in "Step 2: Run the Oracle Application Server Metadata Repository Creation Assistant on the Oracle Database". |
Locate the SQL*Plus script to upgrade the BPEL Process Manager schema. The script is located in the sql directory of the Oracle BPEL Process Manager CD-ROM and is named upgrade_202_203_oracle.sql.
Run the script against your Oracle Application Server Metadata Repository as follows (see the Note at the beginning of this step before proceeding):
Log in to SQL*Plus and connect as the orabpel user.
If installing on an Oracle Application Server Metadata Repository without Oracle Identity Management (that is, the repository is not registered with Oracle Internet Directory), connect this way:
CONNECT orabpel/orabpel_password
If installing on an Oracle Application Server Metadata Repository with Oracle Identity Management (that is, the repository is registered with Oracle Internet Directory), connect this way:
CONNECT orabpel/random_password
Execute the upgrade script:
@upgrade_202_203_oracle.sql
This script automatically executes the sensor_oracle.sql script (also located in the sql directory). If you copy upgrade_202_203_oracle.sql to a different directory in order to execute it, ensure that sensor_oracle.sql is also copied to the same directory.
Install Oracle Application Server 10g Release 2 (10.1.2.0.2) and select the J2EE and Web Cache installation type or the Portal and Wireless installation type.
|
Note: If you are using Oracle Application Server Metadata Repository 10.1.2.0.2 as your dehydration store, ensure that you associate an Oracle Application Server installation type with it before installing Oracle BPEL Process Manager for OracleAS Middle Tier. |
|
See Also: Oracle Application Server Installation Guide for your operating system |
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 preinstallation steps, you are ready to continue with the installation.
Follow the instructions in one of these sections to install BPEL Process Manager:
This installation type installs both 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 you want to install Oracle BPEL Process Manager.
Insert the Oracle BPEL Process Manager CD-ROM.
Start Oracle Universal Installer from the bpel_oc4j directory of the CD-ROM as follows:
| On... | Do This... |
|---|---|
| UNIX | Enter the following command at the operating system prompt:
|
| Windows | Double-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.
In the Destination fields, 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.
|
Note: Do not use an existing home name and directory path. |
Enter the Name and Path as shown in these examples:
UNIX example:
Name: BPELPM1012 Path: /home/oracle/BPELPM1012
Windows example:
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 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 browser has been configured for Proxy Server information under LAN Settings on the Connections tab.If your browser 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 2-3.
Table 2-3 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 Tasks for Oracle BPEL Process Manager".
Before installing Oracle BPEL Process Manager on an OracleAS Middle Tier, recall from "Preinstallation Tasks for Oracle BPEL Process Manager" that you must already have one of the following databases installed for use as a dehydration store for Oracle BPEL Process Manager for OracleAS Middle Tier:
An Oracle Database on which the Oracle Application Server Metadata Repository Creation Assistant has been executed to create the necessary database user and schema (see "Step 2: Run the Oracle Application Server Metadata Repository Creation Assistant on the Oracle Database")
An Oracle Application Server Metadata Repository installed with Oracle Application Server Infrastructure on which the version upgrade script has been executed (see "Step 4: Upgrade the BPEL Schema Version")
Microsoft SQL Server (see Appendix A, "Using Microsoft SQL Server as the Dehydration Store")
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.
If installing the Oracle BPEL Process Manager for OracleAS Middle Tier installation type into an Oracle home directory that includes the Portal and Wireless middle tier type, ensure that Oracle Internet Directory is already running. Otherwise, Oracle BPEL Process Manager for OracleAS Middle Tier does not install successfully.
Log on to the host on which you want to install Oracle BPEL Process Manager components.
Insert the Oracle BPEL Process Manager CD-ROM.
Start Oracle Universal Installer from the bpel_oc4j directory of the CD-ROM as follows:
| On... | Do This... |
|---|---|
| UNIX | Enter the following command at the operating system prompt:
|
| Windows | Double-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.0.2 J2EE and Web Cache or Portal and Wireless is located.
Do not accept the default name and path. The installer looks for the Oracle Application Server 10.1.2.0.2 J2EE and Web Cache or Portal and Wireless instance. If you specify an incorrect path, the Dependencies alert appears. Enter the name and path as shown in these examples.
UNIX example:
Name: Home1 Path: /home/oracle/OraHome_1
Windows example:
Name: Home1 Path: C:\OraHome_1
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.
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 2-3.
The Choose the Dehydration Database type screen appears.
Depending on the database you previously configured as the dehydration store, choose one of the following, then click Next.
Oracle Database
Metadata Repository
Non-Oracle Database
At this time, the only non-Oracle database supported as a Oracle BPEL Process Manager dehydration store is Microsoft SQL Server. If you select this option, the Summary screen appears. Go to Step 16.
The Specify Dehydration Database Information screen appears.
Provide the details as described in the following table:
| Information | Description | Example |
|---|---|---|
| Password for BPEL Process Manager Schema (ORABPEL): | The password assigned to the user orabpel. You may have changed this password during preinstallation tasks.
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 or Portal and Wireless. |
|
Click Next. (Note that it takes a few minutes for the database connection to be established.)
If you selected a dehydration store that is not configured with the Identity Management Access option, the installation continues after Step 15.
If you selected the Identity Management Access option for the dehydration store, the Specify Login for Oracle Internet Directory screen appears.
Enter either the Oracle Internet Directory super user name or the name of a single sign-on user with the install privilege.
Click Next.
The Install Demo Users screen appears. This option enables Oracle Internet Directory to be used as the identity service LDAP-based JAZN provider.
|
Note: See the Oracle BPEL Process Manager Developer's Guide for details about identity services and the demo user community. |
Select Yes if you want to automatically install the identity service users, application roles, and groups into Oracle Internet Directory during installation.
Select No if you want to install only the system users and application roles. The demo user community and enterprise groups are not installed; you can later install them manually.
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, first complete the required postinstallation steps and then complete the additional steps depending on the type of installation you are performing. The steps are described in these sections:
Postinstallation Steps for Oracle BPEL Process Manager (All Installations)
Postinstallation Steps for Oracle BPEL Process Manager for Developers
Postinstallation Steps for Oracle BPEL Process Manager for OracleAS Middle Tier
|
Note:
|
Complete these procedures for all installations of Oracle BPEL Process Manager, including the Developer and OracleAS Middle Tier versions:
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 the Oracle BPEL Admin Console. The password for Oracle BPEL Admin Console is automatically set to oracle. Change this password immediately after installation.
If using a Metadata Repository, and the Metadata Repository and Oracle Internet Directory reside in the same database, then change the password in both places.
|
See Also: Oracle BPEL Process Manager Developer's Guide for procedures on changing the domain and Oracle BPEL Admin Console passwords |
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 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, pager, fax, and short message service (SMS) channels, then the wireless service settings must be configured as described in the section on configuring the wireless service provider for voice in the Oracle BPEL Process Manager Notification Service chapter of Oracle BPEL Process Manager Developer's Guide.
**4701941After installing on a UNIX platform such as Solaris or Linux, add orabpel/bin to the path. This enables you to run useful commands such as obant.sh and obversion.sh, and also facilitates the deployment and running of samples.
See Table 2-4 for information on how to enable access to the developer prompt.
Follow these steps only if you are using Oracle BPEL Process Manager for Developers:
Step 2: May be Needed - Configure Oracle BPEL Process Manager to Use Your Oracle Database
Step 3: May be Needed - On Windows Only, Configure Startup/Shutdown Files to Use Oracle Database
Step 4: Optional - Configure JDeveloper BPEL Designer to Use Online Help from a Local Disk
You must add the hostname of your computer to the Oracle JDeveloper preference settings. If you do not, you can receive parsing errors when selecting a WSDL file on the WSDL Chooser window while creating a partner link. Additionally, this step ensures that you can access the online help from the Oracle JDeveloper Web site on the Oracle Technology Network. Follow these steps:
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:
If you installed Oracle BPEL Process Manager for Developers on UNIX, or
If you are using an Oracle Database as your dehydration database on Windows, or
If you require multibyte character set support
To configure an 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. 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.
|
Note: This step is needed if you performed Step 2. |
For Windows only, if you are using an Oracle Database, then you must configure startorabpel.bat and shutdownorabpel.bat to use an Oracle Database instead of Oracle Database Lite.
|
Note: This procedure only applies for Windows installations. |
Follow these steps for startorabpel.bat:
Find the startorabpel.bat file located in the bin folder under the destination path that you specified during installation. For example:
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 the line that starts Oracle Database Lite as shown:
@rem start /d "C:\BPELPM1012\integration\orabpel\bin" /min /realtime start_olite.bat
Save the startorabpel.bat file.
Repeat similar steps for shutdownorabpel.bat:
Find the shutdownorabpel.bat file located in the bin folder under the destination path that you specified during installation. For example:
C:\BPELPM1012\integration\orabpel\bin
Make a backup copy of the shutdownorabpel.bat file.
Edit the shutdownorabpel.bat file as follows:
Remove or comment out the line that stops Oracle Database Lite as shown:
@rem start /min /d "C:\BPELPM1012\integration\orabpel\bin\kill_olite.bat"
Save the shutdownorabpel.bat file.
The steps in this section are optional and are 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 must 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. |
Follow these steps only if you are using Oracle BPEL Process Manager for OracleAS Middle Tier.
Step 1: Mandatory - Restart Oracle Enterprise Manager 10g Application Server Control Console
Step 2: Mandatory - If Using Oracle Identity Management - Restart Oracle BPEL Process Manager
Step 3: Optional - Configuring SSL Support for Oracle Internet Directory
Step 4: Change the orabpel User Password in the data-sources.xml File
Stop and restart Oracle Enterprise Manager 10g Application Server Control Console as follows:
emctl stop em emctl start em
If you are using Oracle BPEL Process Manager with Oracle Identity Management, you must restart Oracle BPEL Process Manager after installation. The restart ensures that Oracle Internet Directory is correctly configured.
Use opmnctl to stop and restart Oracle BPEL Process Manager:
Oracle_Home\opmn\bin\opmnctl stopproc ias-component=OraBPEL Oracle_Home\opmn\bin\opmnctl startproc ias-component=OraBPEL
If during the Oracle Application Server Metadata Repository and middle tier installations, you specified that Oracle Application Server components connect to Oracle Internet Directory through secure socket layer (SSL) connections, you must enable your Oracle BPEL Process Manager SSL port as a postinstallation task.
Perform the following steps:
Update the Oracle_Home\j2ee\OC4J_BPEL\config\jazn.xml file as follows (changes shown in bold):
Enter the SSL port number you are using (for this example, 636)
Add the property name line that enables SSL support
For example:
<jazn provider="LDAP" location="ldap://example.com:636" default-realm="us"> <property name="ldap.user" value="cn=orcladmin"/> <property name="ldap.password" value="!welcome1"/> <property name="ldap.protocol" value="ssl"/> </jazn>
Update the Oracle_Home\integration\orabpel\system\services\config\is_config.xml file as follows (changes shown in bold):
Enter the SSL port number you are using (must be the same number as entered in Step 1)
Add the property name line that enables SSL support
For example:
<BPMIdentityServiceConfig xmlns="http://www.oracle.com/pcbpel/identityservice/isconfig">
<provider providerType="JAZN" name="oid" >
<connection url="ldap://example.com:636" binddn="cn=orcladmin"
password="welcome1" encrypted="false">
<property name="securityProtocol" value="ssl" />
</connection>
</provider>
</BPMIdentityServiceConfig>
You must perform this step if you changed the password in "Step 3: Unlock the orabpel Account and Change the Password" for an Oracle Application Server Metadata Repository that is not registered with Oracle Internet Directory. The data-sources.xml file must also be updated to include this same password. This file defines how to connect to the dehydration store database with the orabpel user account and its password.
See the following step based on how you want to display the password in the data-sources.xml file:
Follow these steps to display a clear text password in the data-sources.xml file.
Use a text edit to open the data-sources.xml file located in the following directory:
Oracle_Home\j2ee\OC4J_BPEL\config
Go to the BPELServerDataSource section.
Change the value for the password attribute from:
password="->pwForOrabpel"
to the same password as entered in Step 4. For example:
password="->mynewpassword"
Save your changes.
Follow these steps to not display a clear text password in the data-sources.xml file; the password is instead indirectly referenced.
Log into the Oracle Enterprise Manager 10g Application Server Control Console.
Go to OC4J_BPEL > Administration > Security.
Find the user named jazn.com/pwForOrabpel in the User section.
Click on the link to change the password to the one entered in Step 4. The password is case sensitive and must exactly match the one set in Step 4. Otherwise, Oracle BPEL Console does not display the domains.
Click Apply.
This associates the password with the pwForOrabpel value of the password attribute in the data-sources.xml file.
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 2-4 provides instructions for accessing the various components.
Table 2-4 Accessing Oracle BPEL Process Manager Components
|
See Also:
|
This section provides information about globalization and optional considerations. It includes these sections:
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 messages from Oracle BPEL Server in the server locale on certain pages. To avoid mixed languages being displayed, ensure 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 the 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 2-5 shows the directory structure that is created after completing installation.
Table 2-5 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 > 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. It includes these topics:
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 (Oracle BPEL Process Manager for OracleAS Middle Tier)
Oracle_Home\integration\orabpel\system\appserver\oc4j\j2ee\home\config (Oracle BPEL Process Manager for Developers)
The default value of the transaction-config timeout parameter is "60000" milliseconds, or one minute, which may not be optimal for your server load.
A related parameter, syncMaxWaitTime, resides in the domain configuration file domain.xml, which is located in Oracle_Home\integration\orabpel\domains\default\config (for both Oracle BPEL Process Manager for OracleAS Middle Tier and Oracle BPEL Process Manager for Developers).
In general, syncMaxWaitTime should always be less than transaction-config timeout in the server.xml file.
To change the transaction-config timeout parameter value:
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" />
You can change the syncMaxWaitTime parameter value by using the Oracle BPEL Admin Console. Alternatively, you can change the syncMaxWaitTime setting manually, as follows:
Open the file domain.xml in a text editor.
Find the line for the syncMaxWaitTime parameter. 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 store 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 value in the opmn.xml file to 3 or 4 minutes.
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.
If you copy upgrade_202_203_oracle.sql to a different directory in order to execute it, ensure that sensor_oracle.sql is also copied to the same directory. The upgrade_202_203_oracle.sql script automatically executes the sensor_oracle.sql script. If both scripts are not in the same directory, execution fails.
Also ensure that you do not run these SQL scripts from a directory path that includes spaces (for example, C:\Documents and Settings\mydesktop). Spaces in the directory path can cause execution to fail.
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 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 then 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
This section explains how you can periodically reclaim free space in the dehydration store and manage the future growth of the store.
Oracle recommends that you create the orabpel tablespace with auto segment space management turned on. This enables you to conveniently reclaim free space in the dehydration store.
With auto segment space management turned on, use the following commands to regain free space (in this example, for the cube_scope table):
alter table cube_scope enable row movement; alter table cube_scope shrink space compact; alter table cube_scope shrink space; alter table cube_scope disable row movement;
