| Oracle® BPEL Process Manager Installation Guide 10g Release 3 (10.1.3.1.0) for UNIX and Microsoft Windows Part Number B28980-03 |
|
|
View PDF |
| Oracle® BPEL Process Manager Installation Guide 10g Release 3 (10.1.3.1.0) for UNIX and Microsoft Windows Part Number B28980-03 |
|
|
View PDF |
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
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.
Note:
A silent installation option is available. See "Silent Installation of Oracle BPEL Process Manager".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
Installation Tasks Summary and Where to Find Procedures
The remainder of this section provides an overview of installation tasks for Oracle BPEL Process Manager for OracleAS Middle Tier.
Note:
The Integration Repository Creation Assistant referenced in Table 2-1 is a utility that creates the Oracle BPEL Process Manager user and schema in the Oracle Database. For more information, see Appendix A, "Integration Repository Creation Assistant".Table 2-1 provides an overview of installation tasks to perform for Oracle BPEL Process Manager for OracleAS Middle Tier.
Table 2-1 Oracle BPEL Process Manager for OracleAS Middle Tier
| For | Follow These Steps... | See Also... |
|---|---|---|
|
Oracle Database 10g or Oracle9i Database release 9.2.0.7.0 |
|
Oracle Database Installation Guide 10g or Oracle Database Installation Guide 9i for your operating system |
|
"Step 2: Run the Integration Repository Creation Assistant on the Database" |
||
|
Oracle Application Server Installation Guide for your operating system |
||
|
"Installation Tasks for Oracle BPEL Process Manager" |
This section describes the preinstallation steps for Oracle BPEL Process Manager for OracleAS Middle Tier, which are as follows:
Step 1: Install the Oracle Database - If Not Already Installed
Step 2: Run the Integration Repository Creation Assistant on the Database
Step 4: If Installing on a Cold Failover Cluster (CFC) Middle Tier
Note:
This document provides installation details only for Oracle BPEL Process Manager for OracleAS Middle Tier. For information about installing Oracle BPEL Process Manager with Oracle SOA Suite, see the Oracle Application Server 10g Release 3 (10.1.3.1.0) Installation Guide for your platform.This section provides details of the preinstallation steps to follow when installing 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:
Oracle9i Database Server
Oracle Database 10g
See Also:
"Dehydration Store Maintenance"If you already have an Oracle Database that meets the requirements listed in "Available Databases", then you do not need to reinstall the database. Otherwise, install or upgrade before you proceed.
See Also:
Oracle Database Installation Guide for Microsoft Windows (32-Bit)
Oracle Database Installation Guide for Linux x86
Oracle Database Installation Guide for Solaris Operating System (SPARC 64-Bit)
Run the Integration Repository Creation Assistant (IRCA) to create the database user and schema. IRCA creates the default user orabpel, the default password orabpel, and the tablespace orabpel in the Oracle Database.
For details about how to run the IRCA utility, see Appendix A, "Integration Repository Creation Assistant".
Note that:
If you previously installed Oracle BPEL Process Manager and you already ran Integration 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 Integration Repository Creation Assistant. This involves shutting down Oracle BPEL Server, Oracle BPEL Control, and Oracle JDeveloper.
Oracle recommends that you enable automatic segment space management when creating the orabpel tablespace. This enables you to conveniently reclaim free space in the dehydration store.
See Also:
"Dehydration Store Maintenance"Oracle BPEL Process Manager must be installed on Oracle Application Server 10g Release 3 (10.1.3.1.0). Options include:
Install Oracle Application Server 10g Release 3 (10.1.3.1.0) and select the J2EE Server installation type or the J2EE and Web Server installation type.
See Also:
Oracle Application Server Installation Guide for your operating systemor
Upgrade an existing Oracle Application Server 10g Release 3 (10.1.3) Middle Tier
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 Microsoft Windows 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.
The Oracle BPEL Process Manager installation does not support IPv6 addressing. If IPv6 is enabled on the target machine, disable it prior to installing BPEL Process Manager. You can enable IPv6 after installation.
After you complete the preinstallation steps, you are ready to continue with the installation.
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 a database installed for use as a dehydration store for Oracle BPEL Process Manager for OracleAS Middle Tier. This must be an Oracle Database on which the Integration Repository Creation Assistant has been executed to create the necessary database user and schema (see "Step 2: Run the Integration Repository Creation Assistant on the Database").
Note:
If you are configuring Oracle BPEL Process Manager in a disaster recovery environment that uses host aliases, see "Configuring Oracle BPEL Process Manager for OracleAS Middle Tier in Disaster Recovery Environments" for configuration information you will need to provide during installation.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 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/Linux |
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 the Oracle Application Server 10.1.3.1.0 J2EE and Web Server or J2EE Server instance is located.
Do not accept the default name and path. Instead, ensure that it points to the Oracle home where the Oracle Application Server 10.1.3.1.0 J2EE and Web Server or J2EE Server instance is installed. If you specify an incorrect path, the Dependencies alert appears. Enter the name and path as shown in these examples.
UNIX/Linux example:
Name: OraBPEL Path: /home/oracle/OraBPEL
Windows example:
Name: OraBPEL Path: C:\OraBPEL
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.
Note:
BPEL Process Manager for Developers is not a supported option. To install Oracle BPEL Process Manager as part of the Oracle SOA basic installation for preproduction testing purposes, see the Oracle Application Server Installation Guide 10g Release 3 (10.1.3.1.0) for your platform.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-2.
Note:
This information is automatically filled in 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.
On platforms other than Windows, proxy information can be manually set in the opmn.xml file.
Table 2-2 Outgoing HTTP Proxy Information
The Specify Database screen appears.
Provide the details as described in the following table:
| Information | Description | Example |
|---|---|---|
| Database Type | This must be an Oracle Database. | |
| Hostname and 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
|
| ORABPEL Schema Password | The password assigned to the user orabpel. You may have changed this password during preinstallation tasks.
For information about the |
Click Next.
Note:
It takes a few minutes for the database connection to be established.The Administration Settings screen appears.
Specify the administrator password. This must match the password of the Oracle Application Server administrator (username oc4jadmin).
The Summary screen appears.
Click Install.
The Installation Progress screen appears for a few seconds, and then the Configuration Assistants screen appears, listing the following:
The Oracle BPEL Process Manager Configuration Assistant
The Oracle Process Manager and Notification Server Configuration Assistant
The installer automatically executes each configuration assistant in sequence, displaying the progress in the Status column. No action is required on this screen.
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".
If you are configuring Oracle BPEL Process Manager in a disaster recovery environment that uses host aliases, specify those aliases in the Bypass proxy for addresses field of the Specify Outgoing HTTP Proxy Information window during Oracle BPEL Process Manager for OracleAS Middle Tier installation.
Silent installation eliminates the need to monitor the Oracle BPEL Process Manager installation because there is no graphical output and no input by the user.
To perform a silent installation, you must provide information specific to your installation in a response file. Response files are text files that you can create or edit in a text editor.
A sample response file is shown here:
RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME="svrtech"
FROM_LOCATION=/mount_point/Disk1/stage/products.xml
ORACLE_HOME=/scratch/aime2/work/soa173
ORACLE_HOME_NAME=soa173
SHOW_SPLASH_SCREEN=false
SHOW_WELCOME_PAGE=false
SHOW_INSTALL_PROGRESS_PAGE=false
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_CUSTOM_TREE_PAGE=false
SHOW_SUMMARY_PAGE=false
SHOW_REQUIRED_CONFIG_TOOL_PAGE=false
SHOW_OPTIONAL_CONFIG_TOOL_PAGE=false
SHOW_RELEASE_NOTES=false
SHOW_ROOTSH_CONFIRMATION=false
SHOW_END_SESSION_PAGE=false
SHOW_EXIT_CONFIRMATION=false
NEXT_SESSION=false
NEXT_SESSION_ON_FAIL=false
SHOW_DEINSTALL_CONFIRMATION=false
SHOW_DEINSTALL_PROGRESS=false
SHOW_IAS_COMPONENT_CONFIG_PAGE=false
ACCEPT_LICENSE_AGREEMENT=true
RESTART_SYSTEM=<Value Unspecified>
CLUSTER_NODES=<Value Unspecified>
OUI_HOSTNAME=isunnat04.us.oracle.com
PreReqConfigSelections=""
n_ValidationPreReqConfigSelections=0
TOPLEVEL_COMPONENT={"oracle.tip.pcbpel","10.1.3.0.0"}
DEINSTALL_LIST={"oracle.tip.pcbpel","10.1.3.0.0"}
COMPONENT_LANGUAGES={"en"}
INSTALL_TYPE=installtype_Server
sl_HTTPProxyInfoConfig={"www-proxy.us.oracle.com","80","*.oracle.com;*.us.oracle.com"}
s_configProxyOptions="-http-proxy-required true -http-proxy-host www-proxy.us.oracle.com -http-proxy-port 80 -http-no-proxy-for *.oracle.com;*.us.oracle.com"
nValidationHTTPProxyInfoConfig=0
oracle.tip.pcbpel.midtier:sl_MdConnect={"Oracle Database", "myhost.us.oracle.com:1521", "", "", "db1234.us.oracle.com", "", "orabpel", ""}
oracle.tip.pcbpel.midtier:s_DBHost="myhost.us.oracle.com"
oracle.tip.pcbpel.midtier:s_DBPort="1521"
oracle.tip.pcbpel.midtier:s_DBPasswd="orabpel"
oracle.tip.pcbpel.midtier:s_DBSid="db1234.us.oracle.com"
oracle.tip.pcbpel.midtier:iASinstancePW="welcome1"
oracle.tip.pcbpel.midtier:bMaskValidationMD=false
oracle.tip.pcbpel.midtier:nValidationMD=0
oracle.tip.pcbpel.midtier:n_choosedb=0
oracle.tip.pcbpel.midtier:s_dbVendor="oracle"
oracle.tip.pcbpel.midtier:bMaskValidationAdminInfo=false
oracle.tip.pcbpel.midtier:n_validateAdminDialogInfo=0
oracle.tip.pcbpel.midtier:sl_adminDialogReturn={"welcome1", "", "default_group^oc4j_soa", "", ":", ""}
You can copy and paste this example file into a text editor, replacing the parameters with their correct values. Use a file type .rsp when creating the file.
After the file is ready, run the installer using the -silent parameter to perform a silent installation. The syntax is as follows:
Windows
setup.exe -silent -responseFile absolute_path_and_filename_to_responsefile
Unix/Linux
runInstaller -silent -responseFile absolute_path_and_filename_to_responsefile
See Also:
Silent and Non-Interactive Installation in the Oracle Application Server Installation Guide for details about silent installations.After installing Oracle BPEL Process Manager, complete the postinstallation steps described in these sections:
Step 2: Recommended - Configure Notification and Workflow for Oracle BPEL Process Manager
Step 6: Recommended - Add Oracle BPEL Process Manager for OracleAS Middle Tier Memory Settings
Note:
Important information about Oracle BPEL Process Manager configuration is provided in Oracle_Home/install/bpelsetupinfo.txt.
For the full log of installation details, see the installActionsdate_time.log file, where the date and time are specified as yyyy-mm-dd_hr-mm-ss. This file is located under c:\Program Files\Oracle\Inventory\logs\ on Windows and Oracle_user_home/oraInventory/logs/ on UNIX/Linux.
It is important to change all default passwords before you start using the product.
Two user accounts, named default and bpeladmin, are automatically created with your Oracle BPEL Process Manager installation. The initial password for both accounts is welcome1. Change the password on both accounts immediately after installation is complete.
The bpeladmin user provides access to all domains.
See Also:
Oracle Application Server Administrator's Guide for procedures on changing the domain and Oracle BPEL Control passwordsTo use the notification service and workflow applications, you must complete the following steps:
Configure the e-mail server settings as described in the Service Configuration section of the Oracle BPEL Process Manager Administrator's Guide. 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 the Services Configuration section of the Oracle BPEL Process Manager Administrator's Guide.
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 Services Configuration section of the Oracle BPEL Process Manager Administrator's Guide.
After installing on a UNIX or Linux platform, add Oracle_Home/bpel/bin to the path. This enables you to run useful commands such as ant.sh and obversion.sh, and also facilitates the deployment and running of samples.
See Table 2-3 for information on how to enable access to the developer prompt.
If you disabled IPv6 on the target host prior to installation, you can now enable it.
Oracle JDeveloper, a graphical and user-friendly way to model, edit, design, and deploy BPEL processes, is not included with Oracle BPEL Process Manager. You must download and install Oracle JDeveloper 10.1.3.1 Studio, available on the companion CD, to work with Oracle BPEL Process Manager projects.
Note:
Do not install Oracle JDeveloper into a directory path that includes a space (for example, inC:\Program Files\JDev). If you do, you receive an error when you compile BPEL processes.After installing Oracle BPEL Process Manager for OracleAS Middle Tier, ensure that you increase the MaxPermSize value from 128 to 256 in the Oracle SOA Suite Oracle_Home\opmn\conf\opmn.xml file:
<ias-component id="default_group">
<process-type id="home" module-id="OC4J" status="enabled">
<module-data>
<category id="start-parameters">
<data id="java-options" value="-Xrs -server
-XX:MaxPermSize=256M -ms512M -mx1024M -XX:AppendRatio=3 ..>
For related information, see "OutOfMemory Error".
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-3 provides instructions for accessing the various components.
Table 2-3 Accessing Oracle BPEL Process Manager Components
| To Access The... | On Windows... | On UNIX/Linux... |
|---|---|---|
|
To start Oracle BPEL Server: Select Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager > Start BPEL PM Server To stop Oracle BPEL Server: Select Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager > Stop BPEL PM Server |
To start Oracle BPEL Server: Use either the See "Starting and Stopping Components" in the Oracle Application Server Administrator's Guide for details. To stop Oracle BPEL Server: Use either the See "Starting and Stopping Components" in the Oracle Application Server Administrator's Guide for details. |
|
|
First start Oracle BPEL Server. To start Oracle BPEL Control:
You can also start Oracle BPEL Control from your Web browser using the URL for your installation, which can be found in |
First start Oracle BPEL Server. To start Oracle BPEL Control:
|
|
|
Developer Prompt for easy access to samples |
Select Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager > Developer Prompt to open up a command prompt at the |
Set the Developer Prompt in the Bourne shell:
|
|
Oracle BPEL Process Manager Samples and Tutorials |
For details about BPEL samples and additional tutorials available for use: Select Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager > Getting Started with Samples |
Log into the following URL using your Web browser:
|
|
Oracle BPEL Worklist Application |
To access the login window for Oracle BPEL Worklist Application: Select Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager > Worklist Application You may also start Oracle BPEL Worklist Application from your Web browser using the URL for your installation, which is found in |
First start Oracle BPEL Server. To start Oracle BPEL Worklist Application:
|
This section provides information about globalization and optional considerations. It includes these sections:
Oracle BPEL Control is available in the following languages: French, German, Italian, Spanish, Portuguese, Japanese, Korean, Simplified Chinese, and Traditional Chinese. Oracle JDeveloper is only available in English and Japanese. Oracle BPEL Control and Oracle JDeveloper 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 Control and Oracle BPEL Server are using the same locale.
You can determine the version number of Oracle BPEL Process Manager and Oracle JDeveloper for support purposes.
To check the Oracle BPEL Server version on Windows:
Select Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager and select Developer Prompt.
Enter obversion at the command prompt.
To check the Oracle BPEL Server version on UNIX/Linux:
Go to Oracle_Home/bpel/bin and run obversion.sh.
To check the Oracle JDeveloper version:
Start Oracle JDeveloper and select About from the Help menu. Click the Version tab, and look for the line BPEL Designer.
Note:
Oracle JDeveloper 10.1.3.1 Studio is not installed with Oracle BPEL Process Manager and must be downloaded and installed separately. Oracle JDeveloper 10.1.3.1 Studio is also available on the companion CD for Oracle BPEL Process Manager.Table 2-4 shows the directory structure that is created under the bpel directory after completing installation.
Table 2-4 Directory Structure for Oracle BPEL Process Manager Installed Components
| This Directory | Contains... |
|---|---|
|
|
The top-level directory for the Oracle BPEL Process Manager installation. It contains these subdirectories: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This section contains the following topics:
To ensure that BPEL references are removed from the OracleAS Middle Tier, you must run some deinstall-related scripts prior to performing the deinstallation steps. Refer to the Oracle_Home/bpel/install/README.deinstall.txt file for instructions.
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. You must manually remove these files and directories. Review the obsetenv.bat and devprompt.bat files located in Oracle_Home/bpel/bin for more information about how to do this. Oracle recommends that you delete the bpel directory under your Oracle home after backing up any required files.
After running the pre-deinstall scripts and deinstalling Oracle BPEL Process Manager, restart Oracle Process Manager and Notification Server using the opmnctl stopall and opmnctl startall commands. This ensures that other OC4J applications, like Oracle Enterprise Manager 10g, are in a usable state after you deinstall Oracle BPEL Process Manager.
Note:
If you want to deinstall and reinstall Oracle BPEL Process Manager in the same Oracle home, ensure that you first remove files and subdirectories under Oracle_Home/bpel before performing the Oracle BPEL Process Manager reinstallation.
You cannot deinstall and then reinstall within the same Oracle home during the same OUI install session. You must exit the OUI after deinstallation, clean out the directory structure, and then restart a fresh installation.
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-timeout parameter, which is located in Oracle_Home\bpel\system\appserver\oc4j\j2ee\home\config\transaction-manager.xml.
The default value of the transaction-timeout parameter is 30 seconds, 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\bpel\domains\DOMAIN_NAME\config.
In general, syncMaxWaitTime should always be less than transaction-timeout in the transaction-manager.xml file.
To change the transaction-config timeout parameter value:
Open the server.xml file 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 Oracle BPEL Control. 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 two 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.
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 Containers for J2EE.
Oracle HTTP Server must be running for BPEL server processes to be available. You can start this server process from Oracle Enterprise Manager 10g Application Server Control Console by selecting the process and then clicking Start.
Alternatively, you can start the Oracle HTTP Server process from the developer prompt as follows:
opmnctl startproc process-type=HTTP_server
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;
On Windows 2000, the developer prompt can fail to display when selecting Start > All Programs > Oracle - Oracle_Home > Oracle BPEL Process Manager > Developer Prompt. This is a known classpath length issue with Windows 2000. For the developer prompt to successfully display, you must shorten your classpath. For example, when you install Oracle BPEL Process Manager, limit the length of the directory path of your Oracle Home.
On Windows platforms, do not attempt to apply multiple installations of the SOA Basic installation type on the same host. This is because multiple installations would require multiple versions of Oracle Database Lite on the same host, which is not supported.
If you need a newer version, first uninstall the original installation, then reinstall.
You cannot use the same dehydration store for multiple Oracle BPEL Process Manager installations for different releases. For example, Oracle BPEL Process Manager 10.1.3.1.0 and 10.1.2.0.2 cannot share the same Oracle Database.
This section provides information specific to Mozilla/Firefox security settings.
Due to some security restrictions in Firefox and Mozilla browsers, some tasks require explicit permission. To enable users to ask for that permission, the following Mozilla/Firefox preference must be set to true:
signed.applets.codebase_principal_support = true
The effect of this setting is that code which executes and asks for a certain privilege, and is given that privilege, will run with it in the context of the currently executing stack frame and all called frames. Access is not granted to the lower stack frames from the point of privilege grant.
To set this property:
Open a new tab, and type about:config in the location/address field.
Find the preference signed.applets.codebase_principal_support.
Right-click over it to get the context menu and choose Toggle so that the preference has the value true.
Modal dialogs cannot exist in Mozilla/Firefox unless a UniversalBrowserWrite permission is granted to the calling script. This is encountered in some places in Oracle BPEL Control. Unless you grant this privilege, the code will not run; instead, the browser will ask you for that privilege when such code is to be executed.
A copy-to-clipboard feature exists in some places in Oracle BPEL Control to help in moving XML document data to and from other editors. Mozilla and Firefox do not grant access (either read or write) to the system clipboard unless the UniversalXPConnect privilege is granted.
Out-of-memory errors can have many different causes, including hardware configuration, software configuration, JDK versions, and so on. For example, when too many Java classes must be loaded, you may receive the following error:
Java.lang.OutOfMemoryError: PermGen space
After installing Oracle BPEL Process Manager for OracleAS Middle Tier, ensure that you increase the MaxPermSize value from 128 to 256 in the Oracle SOA Suite Oracle_Home\opmn\conf\opmn.xml file:
<ias-component id="default_group">
<process-type id="home" module-id="OC4J" status="enabled">
<module-data>
<category id="start-parameters">
<data id="java-options" value="-Xrs -server
-XX:MaxPermSize=256M -ms512M -mx1024M -XX:AppendRatio=3 ..>
