2 Installing Oracle BPEL Process Manager with JBoss or WebLogic Application Servers

This chapter provides the requirements and procedures for installing Oracle BPEL Process Manager with a JBoss Application Server or WebLogic Application Server:

• Oracle BPEL Process Manager Components Overview

• System Requirements for Oracle BPEL Process Manager

• Preinstallation Tasks for Using an Oracle Database

• Installation Tasks for Oracle BPEL Process Manager

• Postinstallation Tasks for Oracle BPEL Process Manager

• Postinstallation Verification Tasks for Oracle BPEL Process Manager

• Globalization for Oracle BPEL Process Manager

• Determining the Version of Your Oracle BPEL Process Manager

• Directory Structure for Oracle BPEL Process Manager

• Deinstallation Tasks for Oracle BPEL Process Manager

• Troubleshooting for Oracle BPEL Process Manager

See Also: The following documentation after completing installation: Oracle BPEL Process Manager Quick Start Guide Oracle BPEL Process Manager Order Booking Tutorial Oracle BPEL Process Manager Developer's Guide

Oracle BPEL Process Manager Components Overview

JBoss is an open source, Java-based application server for use on operating systems that support Java. The BEA WebLogic application server enables you to develop, integrate, secure, and manage distributed service-oriented applications. You can install and use Oracle BPEL Process Manager with the JBoss Application Server or WebLogic Application Server.

The following components are included with Oracle BPEL Process Manager:

• 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. For UNIX platforms and if you are using a multibyte character set, you cannot use this database. Instead, you must configure a different Oracle database to test your deployed BPEL processes. See "Preinstallation Tasks for Using an Oracle Database" and "Postinstallation Tasks for Oracle Databases" for details about configuring an Oracle database.

Note: JDeveloper BPEL Designer, which provides a graphical and user-friendly way to model, edit, design, and deploy BPEL Processes, is not included with Oracle BPEL Process Manager on the JBoss Application Server or WebLogic Application Server. For information on downloading and using JDeveloper BPEL Designer, visit the following URL: http://www.oracle.com/technology/bpel

System Requirements for Oracle BPEL Process Manager

This section describes the system requirements for installing Oracle BPEL Process Manager with the following application servers:

• JBoss Application Server

• BEA WebLogic Application Server

JBoss Application Server

Table 2-1 describes the system requirements for Oracle BPEL Process Manager with the JBoss Application Server.

Table 2-1 Oracle BPEL Process Manager System Requirements

Element	Requirement
JBoss Application Server	Version 3.2.6. This JBoss version is automatically installed with Oracle BPEL Process Manager.
Operating system	Sun SPARC Solaris version 8 or 9 Red Hat Enterprise Linux AS/ES 2.1 and 3.0 SUSE Linux Enterprise Server 8 and 9 Note: These supported versions are for Linux on the x86 architecture. Check the Certify section of OracleMetaLink (http://metalink.oracle.com) for support of these Linux versions on different architectures. Windows 2000 with Service Pack 3 Windows Server 2003 with Service Pack 1 Windows XP
JDK	JDK 1.4.x (JDK 1.4.0 is not supported)
Memory	512 MB RAM minimum (1 GB preferred)
Disk space	500 MB
Swap space	1535 MB minimum
Monitor	Configured to display at least 256 colors

BEA WebLogic Application Server

Table 2-2 describes the system requirements for Oracle BPEL Process Manager with the BEA WebLogic Application Server.

Table 2-2 Oracle BPEL Process Manager System Requirements

Element	Requirement
BEA WebLogic Application Server	Version 8.1.4 must already be installed.
Operating system	Sun SPARC Solaris version 8 or 9 Red Hat Enterprise Linux AS/ES 2.1 and 3.0 SUSE Linux Enterprise Server 8 and 9 Note: These supported versions are for Linux on the x86 architecture. Check the Certify section of Oracle MetaLink (http://metalink.oracle.com) for support of these Linux versions on different architectures. Windows 2000 with Service Pack 3 Windows Server 2003 with Service Pack 1 Windows XP
JDK	JDK 1.4.x (JDK 1.4.0 is not supported)
Memory	512 MB RAM minimum (1 GB preferred)
Disk space	500 MB
Swap space	1535 MB minimum
Monitor	Configured to display at least 256 colors

Supported Databases for Oracle BPEL Process Manager

Table 2-3 lists information about the Oracle database for your Oracle BPEL Process Manager installation.

You may use your existing Oracle database, if it meets the requirements shown in Table 2-3.

Table 2-3 Supported Oracle Databases

Oracle Database	Description
Oracle Database Lite	Included on Windows installations of Oracle BPEL Process Manager only. Oracle Database Lite is best suited for designing a BPEL process and then performing preproduction deployment and testing. Once you are ready to deploy a production version, use the Oracle database. Refer to the note in this section about multibyte character set support.
Oracle Database 10g	Recommended for UNIX installations and production deployments on all operating systems.
Oracle9i Database release 9.2.0.5.0 or later	Supported.

Note: Oracle Database Lite currently does not support multibyte character sets. Therefore, if your locale requires multibyte support, then use the Oracle database instead of Oracle Database Lite.

Supported Web Browsers for Oracle BPEL Console

Oracle BPEL Console requires Internet Explorer 6.0 SP2.

Note: Ensure that cookies are enabled in your Web browser. The Oracle BPEL Console caching mechanism uses cookies to identify user sessions.

Preinstallation Tasks for Using an Oracle Database

Note: If you are using Oracle Database Lite, you can skip this section and proceed to "Installation Tasks for Oracle BPEL Process Manager".

An Oracle database is required to be your dehydration store for all Oracle BPEL Process Manager instances. Oracle Database Lite is automatically installed with Oracle BPEL Process Manager on Windows operating systems only.

For UNIX platforms and if you are using a multibyte character set, you need to configure an Oracle database for your deployed BPEL processes.

Follow these instructions:

• Step 1: Install the Oracle Database - If Not Already Installed

• Step 2: Run Integration Repository Creation Assistant

Step 1: Install the Oracle Database - If Not Already Installed

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.

Step 2: Run Integration Repository Creation Assistant

Run Integration Repository Creation Assistant (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.

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

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

• IRCA is located at the root of the Oracle BPEL Process Manager software media in IRCA.zip.

• IRCA does not support Oracle Application Server Metadata Repository.

To run IRCA:

1. Copy the ZIP file to the host where the Oracle database is installed.

2. Extract the ZIP file to a temp directory of the host system, being sure to preserve path information.

3. From a command window, run irca.bat on Windows or irca.sh on UNIX.

   IRCA starts and prompts you for information.

4. Provide the database details as shown in Table 2-4 when prompted. Be sure to record the information that you provide. You must provide this information later when you configure either JBoss Application Server ("Configure the JBoss Application Server") or BEA WebLogic Application Server ("Configure the BEA WebLogic Application Server") to use the Oracle database as the dehydration store.

   
   

   Important: Change the orabpel user password after you run IRCA, and make a note of your new password.

   
   

   Table 2-4 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 137.1.18.228
   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 show parameter service_names.	orcl or orcl.us.acme.com
   Enter sys password	The database sys user password.	8x9cv55 Note: This is just an example. The password to enter is the one you specified for this account either during or after Oracle database installation.

   
   

Installation Tasks for Oracle BPEL Process Manager

Follow these instructions to install Oracle BPEL Process Manager with the following application servers:

• JBoss Application Server

• WebLogic Application Server

  
  

  Note: The Solaris and Linux instructions in these sections describe the screens that appear and mouse clicks to use when performing an X Windows-based installation. If you are performing a console-based installation (that is, with no graphical user interface), the questions that appear are the same, but the keyboard commands you use to navigate through the installation are different. Be aware of the commands. For example, you press Enter to move to the next set of questions, instead of clicking Next.

  
  

JBoss Application Server

1. Log on to the host on which to install Oracle BPEL Process Manager.

2. Download Oracle BPEL Process Manager for JBoss for the operating system you are using from http://www.oracle.com/technology/bpel:

   Operating System	Name of File to Download
   Windows	as_windows_x86_bpel_jboss_101200.exe
   Solaris	as_sun_bpel_jboss_101200.cpio
   Linux	as_linux_x86_bpel_jboss_101200.cpio

   
   

   Each downloadable file contains the following components:

   • The readme file for this release, which contains important information to read before you begin

   • The Oracle BPEL Process Manager software to install

   • The IRCA.zip file, which is described in "Step 2: Run Integration Repository Creation Assistant"

3. Begin the installation:

   For...	Perform These Steps...
   Windows	Double-click as_windows_x86_bpel_jboss_101200.exe and extract the contents into a temporary directory. Change directories to bpel_jboss in Explorer. Double-click the as_windows_x86_bpel_jboss_101200.exe executable file.
   Solaris and Linux	Extract the downloaded file: cat as_platform_bpel_jboss_101200.cpio | cpio -icd where platform is either sun (for Solaris) or linux_x86 (for Linux) Change directories: cd bpel_jboss Unzip the .gz file: gunzip as_platform_bpel_jboss_101200.bin.gz Set the permissions to make the unzipped file executable: chomod +x as_platform_bpel_jboss_101200.bin Run the file in either of two ways: For X Windows-based installations: ./as_platform_bpel_jboss_101200.bin For console-based installations (no graphical user interface): ./as_platform_bpel_jboss_101200.bin -i console

   
   

   The Introduction screen appears.

4. Review the instructions and click Next.

   The Choose Install Folder window appears.

5. Specify a directory in which to install Oracle BPEL Process Manager and click Next.

   
   

   Note: The examples throughout this chapter use C:\OraBPELPM (for Windows installations) and /home/user_home/OraBPELPM (for Solaris and Linux installations) as the home directory name that you specify. If you specify a different home directory, substitute it as necessary in this chapter.

   
   

   The Choose JDK Folder window appears.

6. Specify a directory in which JDK 1.4.x is installed and click Next. You cannot use JDK 1.4.0. You can download the correct version from the following URL:

   http://java.sun.com/j2se
   
   

   The Specify incoming HTTP port information window appears.

7. Enter the following details and click Next:

   Field	Description	Example
   HTTP Port	The incoming HTTP port number	9700
   HTTPS Port	The incoming secure HTTP port number	9701

   
   

   The Specify outgoing HTTP port information window appears. This window enables you to route outgoing HTTP connections through a proxy server.

8. If a proxy server is required for connecting to the Internet, ensure that the Proxy required for internet check box remains selected.

9. Enter the following proxy server details:

   Field	Description	Example
   HTTP Proxy Host	The name of the proxy server host	www-proxy.us.acme.com
   HTTP Proxy Port	The port number of the proxy server host	80
   Bypass proxy for addresses	The addresses that bypass the proxy (separated by semicolons)	*.acmecorp.com;*.acmeportal.com;<local>

   
   

10. Click Install.

    The Pre-Installation Summary screen appears.

11. Review your selections from the previous screens and click Install.

    After installation completes, the Install Complete screen appears.

12. Click Done.

    The Getting Started with Oracle BPEL Process Manager page appears with instructions on how to get started.

WebLogic Application Server

1. Log on to the host on which to install Oracle BPEL Process Manager.

2. Download Oracle BPEL Process Manager for BEA WebLogic for the operating system you are using from http://www.oracle.com/technology/bpel:

   Operating System	Name of File to Download
   Windows	as_windows_x86_bpel_weblogic_101200.exe
   Solaris	as_sun_bpel_weblogic_101200.cpio
   Linux	as_linux_x86_bpel_weblogic_101200.cpio

   
   

   Each downloadable file contains the following components:

   • The readme file for this release, which contains important information to read before you begin

   • The Oracle BPEL Process Manager software to install

   • The IRCA.zip file, which is described in "Step 2: Run Integration Repository Creation Assistant"

3. Begin the installation:

   For...	Perform These Steps...
   Windows	Double-click as_windows_x86_bpel_weblogic_101200.exe and extract the contents into a temporary directory. Change directories to bpel_weblogic in Explorer. Double-click the as_windows_x86_bpel_weblogic_101200.exe executable file.
   Solaris and Linux	Extract the downloaded file: cat as_platform_bpel_weblogic_101200.cpio | cpio -icd where platform is either sun (for Solaris) or linux_x86 (for Linux) Change directories: cd bpel_weblogic Unzip the .gz file: gunzip as_platform_bpel_weblogic_101200.bin.gz Set the permissions to make the unzipped file executable: chomod +x as_platform_bpel_weblogic_101200.bin Run the file in either of two ways: For X Windows-based installations: ./as_platform_bpel_weblogic_101200.bin For console-based installations (no graphical user interface): ./as_platform_bpel_weblogic_101200.bin -i console

   
   

   The Introduction screen appears.

4. Review the instructions and click Next.

   The Choose Install Folder window appears.

5. Specify a directory in which to install Oracle BPEL Process Manager and click Next.

   The Choose BEA Installation window appears.

6. Select the directory in which the BEA WebLogic Application Server version 8.1.4 is installed and click Next.

   The Specify WebLogic Domain window appears.

7. Accept the default domain name of myorabpel or specify a different name in the Domain Name field and click Next.

   The Choose WebLogic Domain Location window appears.

8. Accept the base directory of user_projects for your domain or specify a different directory and click Next.

   The Choose JDK Folder window appears.

9. Specify a directory in which JDK 1.4.x is installed and click Next. You cannot use JDK 1.4.0. Your BEA WebLogic Application Server version 8.1.4 installation includes an applicable JDK 1.4.x installation that you can use.

   You can also download the correct version from the following URL:

   http://java.sun.com/j2se
   
   

   The Specify incoming HTTP port information window appears.

10. Enter the following details and click Next:

    Field	Description	Example
    HTTP Port	The incoming HTTP port number	9700
    HTTPS Port	The incoming secure HTTP port number	9701

    
    

    The Specify outgoing HTTP port information window appears. This window enables you to route outgoing HTTP connections through a proxy server.

11. If a proxy server is required for connecting to the Internet, ensure that the Proxy required for internet check box remains selected.

12. Enter the following proxy server details:

    Field	Description	Example
    HTTP Proxy Host	The name of the proxy server host	www-proxy.us.acme.com
    HTTP Proxy Port	The port number of the proxy server host	80
    Bypass proxy for addresses	The addresses that bypass the proxy (separated by semicolons)	*.acmecorp.com;*.acmeportal.com;<local>

    
    

13. Click Install.

    The Pre-Installation Summary screen appears.

14. Review your selections from the previous screens and click Install.

    After installation completes, the Install Complete screen appears.

15. Click Done.

    The Getting Started with Oracle BPEL Process Manager page appears with instructions on how to get started.

Postinstallation Tasks for Oracle BPEL Process Manager

Complete the following postinstallation tasks.

• Postinstallation Steps for Oracle BPEL Process Manager

• Postinstallation Tasks for Oracle Databases

Postinstallation Steps for Oracle BPEL Process Manager

Complete these procedures for all installations of Oracle BPEL Process Manager.

• Step 1: Mandatory - Configure the Samples on Solaris and Linux

• Step 2: Recommended - Change Default Passwords

• Step 3: Recommended - Configure Notification and Workflow for Oracle BPEL Process Manager

• Step 4: Mandatory - Download and Apply Patches

Step 1: Mandatory - Configure the Samples on Solaris and Linux

You must configure the samples shipped with Oracle BPEL Process Manager on Solaris and Linux before you can use them.

1. Set your PATH variable to include /home/user_home/OraBPELPM/bin:

   export PATH=/home/user_home/OraBPELPM/bin:$PATH
   
   

2. Change to the following directory:

   cd /home/user_home/OraBPELPM/samples
   
   

3. Run obant to configure the samples:

   obant.sh configure
   
   

   A message similar to the following displays at the end.

   BUILD SUCCESSFULTotal time: 23 seconds
   

Step 2: Recommended - Change Default Passwords

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

Step 3: Recommended - Configure Notification and Workflow for Oracle BPEL Process Manager

In order to use the notification service and workflow applications, you must complete the following steps.

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

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

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

Step 4: Mandatory - Download and Apply Patches

Oracle periodically releases patches that fix issues and provide enhancements. You must download and apply these patches to Oracle BPEL Process Manager. To find out if any patches have been released since you obtained your copy of Oracle BPEL Process Manager, visit the 10.1.2 patches link at the following URL for details:

http://www.oracle.com/technology/bpel

Postinstallation Tasks for Oracle Databases

Note: If you are using Oracle Database Lite, you can skip this section.

If you are using an Oracle database other than Oracle Database Lite as the dehydration store, you must complete the following steps:

• Step 1: Configure the Application Server to Use the Oracle Database as a Dehydration Store

• Step 2: (Windows only) Configure the Startup File to Use the Oracle Database

Note: Substitute the home directory name in the following sections with the one you specified on the Choose Install Folder window in Step 7 for JBoss or Step 7 for BEA WebLogic.

Step 1: Configure the Application Server to Use the Oracle Database as a Dehydration Store

See the following section based on the application server you are using:

• Configure the JBoss Application Server

• Configure the BEA WebLogic Application Server

Configure the JBoss Application Server

1. Back up the following files for the operating system you are using. Ensure that the backup file is placed in a directory other than the deploy directory listed below.

   On...	Back Up...
   Windows	C:\OraBPELPM\system\appserver\jboss\server\default\deploy\oracle-ds.xml C:\OraBPELPM\system\appserver\jboss\server\default\deploy\oracle-sample-bpel-ds.xml
   Solaris and Linux	/home/user_home/OraBPELPM/system/appserver/jboss/server/default/deploy/oracle-ds.xml /home/user_home/OraBPELPM/system/appserver/jboss/server/default/deploy/oracle-sample-bpel-ds.xml

   
   

2. Open oracle-ds.xml for the operating system you are using with a text editor. This file includes the following sections to which you must make the same changes:

   • <local-tx-datasource>

   • <no-tx-datasource>

3. Change the following two lines to use the JDBC thin driver with the Oracle database in the <local-tx-datasource> section.

   Change:

   <connection-url>jdbc:polite4@127.0.0.1:100:orabpel</connection-url>
   <driver-class>oracle.lite.poljdbc.POLJDBCDriver</driver-class>
   
   

   to:

   <connection-url>jdbc:oracle:thin:orabpel/orabpel_password@hostname:port:database_service_name  </connection-url>
   <driver-class>oracle.jdbc.OracleDriver</driver-class>
   
   

   
   

   Note: Enter the orabpel user name and password (orabpel by default, unless you changed it as recommended) that were automatically created and the hostname, port, and database service name that you manually entered when running IRCA in "Step 2: Run Integration Repository Creation Assistant".

   
   

4. Optionally add the following lines immediately below this if you want to use exception handling capabilities:

   <exception-sorter-class-name>
   org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter
   </exception-sorter-class-name>
   
   

5. Remove or comment out the following two lines. These lines apply only to Oracle Database Lite.

   <!--
   <user-name>system</user-name>
   <password>manager</password>
   -->
   
   

6. Repeat Step 3 through Step 5 to make the same changes in the <no-tx-datasource> section of oracle-ds.xml.

7. Save your changes.

8. Open oracle-sample-bpel-ds.xml and repeat Step 3 through Step 5 to make the same changes only in the <local-tx-datasource> section; this file does not include a <no-tx-datasource> section.

9. Save your changes.

10. Back up the following file for the operating system you are using:

    On...	Back Up...
    Windows	C:\OraBPELPM\system\appserver\jboss\bin\run.bat
    Solaris and Linux	/home/user_home/OraBPELPM/system/appserver/jboss/bin/run.sh

    
    

11. Open the file for the operating system you are using with a text editor.

12. Make the following changes for the JDBC thin driver.

    On...	Make The Following Changes:
    Windows	Update JBOSS_CLASSPATH as follows: set JBOSS_CLASSPATH=Oracle_Home\jdbc\lib\ojdbc14.jar;%JBOSS_CLASSPATH%;%JAVAC_JAR%;%RUNJAR%;%POST_CLASSPATH%; where Oracle_Home is the Oracle top-level directory (for example, C:\oracle\product\10.1.0\Db_1).
    Solaris and Linux	Update JBOSS_CLASSPATH as follows: JBOSS_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc14.jar:$JBOSS_CLASSPATH where $ORACLE_HOME is the Oracle top-level directory (for example, home/user_home/oracle/product/10.1.0/Db_1).

    
    
    
    

    Note: If the Oracle database is installed remotely, you must copy the JAR file locally (for example, C:\temp\ojdbc14.jar) and add it to your path.

    
    

13. Save your changes.

Configure the BEA WebLogic Application Server

1. Back up the following files for the operating system you are using:

   On...	Back Up...
   Windows	C:\OraBPELPM\domain_location\domain_name\config.xml
   Solaris and Linux	/home/user_home/OraBPELPM/domain_location/domain_name/config.xml where: domain_location is the name you specified in Step 10 domain_name is the name you specified in Step 9

   
   

2. Open the file for the operating system you are using with a text editor.

3. Make the following changes for the JDBC thin driver.

   <JDBCConnectionPool CapacityIncrement="2"
   DriverName="oracle.jdbc.OracleDriver"
   MaxCapacity="15" LoginDelaySeconds="1"
   Name="BPELServerPool"
   ShrinkPeriodMinutes="15"
   ShrinkingEnabled="true" SupportsLocalTransaction="true"
   Targets="orabpelServer"
   URL="jdbc:oracle:thin:orabpel/orabpel_password@hostname:port:database_servoce_name"/>
   

   
   

   Note: Enter the orabpel user name and password (orabpel by default, unless you changed it as recommended) that were automatically created and the hostname, port, and database service name that you manually entered when running IRCA in "Step 2: Run Integration Repository Creation Assistant".

   
   

4. Remove the following line from the JDBCConnectionPool section. This line applies only to Oracle Database Lite.

   Properties="user=system;password=manager"
   
   

5. Save your changes.

Step 2: (Windows only) Configure the Startup File to Use the Oracle Database

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.

1. Find the startorabpel.bat file located in the bin folder under the destination path that you specified during installation. For example, on Windows:

   C:\OraBPELPM\bin
   
   

2. Make a backup copy of the startorabpel.bat file.

3. Edit the startorabpel.bat file as follows:

   • Remove or comment out two lines that call Oracle Database Lite as shown.

     @rem call "C:\OraBPELPM\bin\kill_olite.bat"
     
     

     and

     @rem start /d "C:\OraBPELPM\bin" /min /realtime start_olite.bat
     
     

4. Save the startorabpel.bat file.

Postinstallation Verification Tasks for Oracle BPEL Process Manager

This section helps you verify your installation of Oracle BPEL Process Manager. Completing these steps confirms a fully functional installation of the various installed components.

Table 2-5 provides instructions for accessing the various components.

Note: Note the following conventions in Table 2-5: Substitute C:\OraBPELPM (for Windows installations) and /home/user_home/OraBPELPM (for Solaris and Linux installations) in the examples with the home directory name that you specified in the Choose Install Folder screen in Step 7 for JBoss or Step 7 for BEA WebLogic. Substitute Oracle - application_server in the Windows Start Menu with the application server in your environment (for example, Oracle - JBoss or Oracle - WebLogic).

Table 2-5 Accessing Oracle BPEL Process Manager Components

To Access The...	On Windows...	On UNIX...
Oracle BPEL Server	To start Oracle BPEL Server: Select Start > All Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 > Start BPEL PM Server To stop Oracle BPEL Server: Select Start > All Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 > Stop BPEL PM Server	To start Oracle BPEL Server: From /home/user_home/OraBPELPM/bin: startorabpel.sh To stop Oracle BPEL Server: From /home/user_home/OraBPELPM/bin: shutdownorabpel.sh
Oracle BPEL Console	You must first start Oracle BPEL Server. To start Oracle BPEL Console: Select Start > All Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 > BPEL Console You can also start Oracle BPEL Console from Internet Explorer 6.0 using the URL for your installation, which can found in bpelsetupinfo.txt.	First start Oracle BPEL Server. To start Oracle BPEL Console: From Internet Explorer 6.0, log on to the URL for your installation, which can found in bpelsetupinfo.txt.
Developer Prompt	Select Start > All Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 > Developer Prompt to open up a command prompt at the C:\OraBPELPM\samples directory. This enables you to easily access demonstrations.	Set the Developer Prompt in the Bourne shell. $ ORACLE_HOME=/home/user_home/OraBPELPM $ export ORACLE_HOME $ PATH=$ORACLE_HOME/bin:$PATH $ export PATH
Oracle BPEL Process Manager Samples and Tutorials	For details about BPEL samples and additional tutorials available for use: Select Start > All Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 > Getting Started with Samples	Log into the following URL using Internet Explorer 6.0: $ORACLE_HOME/samples/sampleshome.html
Oracle BPEL Worklist Application	To access the login window for Oracle BPEL Worklist Application: Select Start > All Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 > Sample Worklist Application You may also start Oracle BPEL Worklist Application from Internet Explorer 6.0 using the URL for your installation, which is found in bpelsetupinfo.txt.	First start Oracle BPEL Server. To start Oracle BPEL Worklist Application: From Internet Explorer 6.0, log on to the URL for your installation, which is found in bpelsetupinfo.txt.

Globalization for Oracle BPEL Process Manager

This section provides information about globalization and optional considerations.

Oracle BPEL Console and BPEL Server Locales

Oracle BPEL Console is available in the following languages: French, German, Italian, Spanish, Portuguese, Japanese, Korean, Simplified Chinese, and Traditional Chinese. Oracle BPEL Console retrieves and displays 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.

Oracle BPEL Process Manager Installation

Oracle BPEL Process Manager installation with the JBoss Application Server is only in English.

Determining the Version of Your Oracle BPEL Process Manager

You can determine the version number of Oracle BPEL Process Manager for support purposes.

To check the Oracle BPEL Server version on Windows:

1. Select Start > All Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 and select Developer Prompt.

2. Enter obversion at the command prompt.

To check the Oracle BPEL Server version on UNIX:

• Go to $ORACLE_HOME/bin and run obversion.sh.

Directory Structure for Oracle BPEL Process Manager

Table 2-6 shows the directory structure that is created after completing the installation of Oracle BPEL Process Manager.

Table 2-6 Directory Structure for Oracle BPEL Process Manager Installed Components

This Directory	Contains...
bin	BPEL server binary and script files.
docs	Javadocs and API documentation.
domains	The default domain, plus new domains you create.
install	BPEL installer-related files.
lib	Oracle BPEL Process Manager JAR files.
samples	All samples and associated files.
system	Oracle Application Server files, classes, and logs.
user_projects (BEA WebLogic only)	Default base directory name for your BEA WebLogic domain. You accepted this default name or specified a different name in Step 10 of Oracle BPEL Process Manager installation.

Deinstallation Tasks for Oracle BPEL Process Manager

Follow these instructions to deinstall Oracle BPEL Process Manager.

• On Windows Operating Systems

• On UNIX Operating Systems

Note: 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.

On Windows Operating Systems

1. Select Start > Programs > Oracle - application_server > Oracle BPEL Process Manager 10.1.2 > Uninstall BPEL Process Manager.

   The Uninstall Oracle BPEL Process Manager 10.1.2.0.0 window appears.

2. Click Uninstall.

On UNIX Operating Systems

1. Change directories to $ORACLE_HOME/install/UninstallerData.

2. Enter the following command:

   ./uninstall
   
   

   The Uninstall Oracle BPEL Process Manager 10.1.2.0.0 window appears.

3. Click Uninstall.

Troubleshooting for Oracle BPEL Process Manager

This section contains troubleshooting tips and information for issues that you can encounter.

Creating the ORABPEL Tablespace Manually

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;