Setting Up the WebLogic Process Integrator Environment

 

The following sections explain how to set up the WebLogic Process Integrator environment, so that you can run WebLogic Process Integrator Studio:

• Configuring WebLogic Collaborate for WebLogic Process Integrator

• Troubleshooting Your WebLogic Process Integrator Configuration

• Starting WebLogic Process Integrator Studio

Before beginning the procedures in this chapter, run the WebLogic Collaborate installation verification application, verifier, described in the BEA WebLogic Collaborate Installation Guide.

 

---

Configuring WebLogic Collaborate for WebLogic Process Integrator

To configure your WebLogic Collaborate environment so that it operates with WebLogic Process Integrator, you need to verify WebLogic Process Integrator Studio and Weblogic Server run-time requirements, as described in this section.

1. Open a command window, and change to the following directory:

   Windows

   %WLC_HOME%\enabler

   UNIX

   $WLC_HOME/enabler

2. Open the weblogic.properties file. This file is configured during the installation process to match your environment. This step describes how to confirm that the settings are correct for your environment.

   The proper repository pool should be uncommented and configured to the database you selected at install time. The weblogic.ejb.deploy property and the weblogic.jdbc.connectionPool.wlpiPool property configurations should match your environment. Verify the configurations as follows:

   • Find the text in the weblogic.properties file that specifies the weblogic.ejb.deploy property. The following extract from the file displays the weblogic.ejb.deploy property:

     weblogic.ejb.deploy=\
     	D:/bea/wlcollaborate1.0/lib/wlpi-ejb.jar,\
     	D:/bea/wlcollaborate1.0/lib/wlpi-wlc-ejb.jar,\
     	D:/bea/wlcollaborate1.0/lib/wlpi-cc-ejb.jar

     Ensure that the pathname is correct for the WebLogic Collaborate lib directory on your system. For this example, the WebLogic Collaborate software is installed in D:/bea/wlcollaborate1.0.

     Note: The weblogic.properties file uses forward slash format in pathnames, on UNIX and NT systems.

   • Find the text in the weblogic.preperties file that specifies the weblogic.jdbc.connectionPool.wlpiPool property.

     The following extract from the file shows the property settings for the supported databases:

     ##Oracle##
     ##Oracle##weblogic.jdbc.connectionPool.wlpiPool=\
     ##Oracle##	url=jdbc:weblogic:oracle,\
     ##Oracle##	driver=weblogic.jdbc.oci.Driver,\
     ##Oracle##	loginDelaySecs=1,\
     ##Oracle##	initialCapacity=1,\
     ##Oracle##	maxCapacity=10,\
     ##Oracle##	capacityIncrement=1,\
     ##Oracle##	allowShrinking=true,\
     ##Oracle##	shrinkPeriodMins=15,\
     ##Oracle##	refreshTestMinutes=10,\
     ##Oracle##props=user=<ORACLE_USER>;password=<ORACLE_PASSWORD>;
     server=<ORACLE_SERVICENAME>

     ### Cloudscape settings ###

     weblogic.jdbc.connectionPool.wlpiPool=\

         url=jdbc:cloudscape:wlpidb,\
         driver=COM.cloudscape.core.JDBCDriver,\
         loginDelaySecs=1,\
         initialCapacity=1,\
         maxCapacity=10,\
         capacityIncrement=1,\
         allowShrinking=true,\
         shrinkPeriodMins=15,\
         refreshTestMinutes=10

     ### SQL Server settings (MSSQL) ###

     ##MSSQL##weblogic.jdbc.connectionPool.wlpiPool=\
     ##MSSQL##	url=jdbc:weblogic:mssqlserver4,\
     ##MSSQL##	driver=weblogic.jdbc.mssqlserver4.Driver,\
     ##MSSQL##	loginDelaySecs=1,\
     ##MSSQL##	initialCapacity=1,\
     ##MSSQL##	maxCapacity=10,\
     ##MSSQL##	capacityIncrement=1,\
     ##MSSQL##	allowShrinking=true,\
     ##MSSQL##	shrinkPeriodMins=15,\
     ##MSSQL##	refreshTestMinutes=10, \
     ##MSSQL## 	testTable=dual,\
     ##MSSQL##props=user=<MSSQL_USER>;password=<MSSQL_PASSWORD>;
     server=<MSSQL_HOSTNAME>

     The preceding extract shows that during installation this weblogic.properties file was configured for the Cloudscape database (the Cloudscape weblogic.jdbc.connectionPool.wlpiPool property is uncommented). Confirm that the property corresponding to the database you are using is uncommented, and that the other database properties are commented.

     Within the weblogic.jdbc.connectionPool.wlpiPool property, confirm that the configuration is correct for the database you are using:

   • If you are using an Oracle database, confirm that <ORACLE_USER>, <ORACLE_PASSWORD>, and <ORACLE_SERVICENAME> (shown in bold in the extract above) are replaced by the user ID, password, and ORACLE_SERVICENAME values for your system. ORACLE_SERVICENAME is defined in the Oracle client tnsnames.ora file and is usually the Oracle system ID.

   • If you are using a Microsoft SQL Server database, confirm that <MSSQL_USER>, <MSSQL_PASSWORD>, and <MSSQL_HOSTNAME> (shown in bold in the extract above) are replaced by the appropriate user ID, password, and Microsoft SQL Server host name values, respectively. (MSSQL_HOSTNAME may take one of the following forms: DATABASE_NAME or DATABASE_NAME@HOST_NAME.)

     Note: The Cloudscape database is a single-user database and requires no user ID and password configurations in the weblogic.jdbc.connectionPool.wlpiPool property.

3. Close the weblogic.properties file.

4. Change to the directory where the WebLogic Process Integrator scripts are installed:

   Windows

   %WLC_HOME%\wlpi

   UNIX

   $WLC_HOME/wlpi

5. Create the WebLogic Process Integrator repository database tables by executing one of the following commands:

   • Oracle

     Windows

     prompt> createOracle.cmd

     UNIX

     prompt> . ./createOracle.sh

   • Cloudscape

     Windows

     prompt> createCloud.cmd

     UNIX

     prompt> . ./createcloud.sh

   • Microsoft SQL Server (Windows)

     prompt> createMSSQL.cmd

     Note: These scripts use DDL files (wlpi_oracle.ddl, wlpi_cloud.ddl, or wlpi_mssql.ddl). By default, the createdatabase.xx scripts do not drop tables. If you have existing tables that you wish to drop, edit the appropriate DDL file.

     After you execute these scripts, you may see the SQL prompt. Exit from SQL before proceeding to the next step.

6. Change to the directory where you installed WebLogic Collaborate:

   Windows

   %WLC_HOME%

   UNIX

   $WLC_HOME

7. Ensure that the setenv.sh script defines the following environment variables.

   Variable	Definition
   JAVA_HOME	The directory path where you installed the JDK software. For example: JAVA_HOME=/usr/local/JDK1.2.2
   WL_HOME	The directory path where you installed the WebLogic Server software. For example: WL_HOME=/usr/local/weblogic
   WLC_HOME	The directory path where you installed the WebLogic Collaborate software. For example: WLC_HOME=/usr/local/WLCollaborate

8. Execute the setenv script to set the WebLogic Collaborate environment variables:

   Windows

   prompt> setEnv.cmd

   UNIX

   prompt> . ./setenv.sh

9. Change directory to the enabler subdirectory and start WebLogic Server:

   Windows

   prompt> cd enabler

   prompt> startweblogic.cmd

   UNIX

   prompt> cd enabler

   prompt> ./startwebLogic.sh

Note: WebLogic Server must be running when you start WebLogic Process Integrator Studio (refer to Starting WebLogic Process Integrator Studio).

 

---

Troubleshooting Your WebLogic Process Integrator Configuration

If you observe binding errors on the listening port, make sure another instance of WebLogic Server is not running using the same port (that is, another command window with the startwebLogic script running).

If WebLogic Server is unable to create a connection pool, as indicated by exceptions displayed in the command window, check that the connection pool property, weblogic.jdbc.connectionPool.wlpiPool, is specified correctly.

If you continue to have a problem, make sure that the database server is running and accessible, and that you have the appropriate permissions.

 

---

Starting WebLogic Process Integrator Studio

WebLogic Process Integrator Studio is the workflow editing component of the WebLogic Process Integrator software, and can be used to create the workflows for conversations and business processes in the WebLogic Collaborate environment.

Before using WebLogic Process Integrator in your WebLogic Collaborate environment, complete the following procedure to verify that you can start WebLogic Process Integrator Studio and connect to WebLogic Server.

1. Complete the procedure described in Configuring WebLogic Collaborate for WebLogic Process Integrator, and ensure that WebLogic Server is still running before you proceed to step 2.

2. Open a new command window, change to the directory where WebLogic Collaborate is installed, and execute the script to set the WebLogic Collaborate environment variables:

   Windows

   prompt> cd %WLC_HOME%

   prompt> setEnv.cmd

   UNIX

   prompt> cd $WLC_HOME

   prompt> . ./setenv.sh

3. Change to the directory where the WebLogic Process Integrator scripts are installed:

   Windows

   %WLC_HOME%\wlpi

   UNIX

   $WLC_HOME/wlpi

4. Execute the following script, which starts WebLogic Process Integrator Studio and displays the WebLogic Process Integrator Studio login dialog box:

   Windows

   prompt> Studio.cmd

   UNIX

   prompt> . ./studio.sh

   The WebLogic Process Integrator Studio login dialog box is displayed.

   

5. Enter the BEA user name (bea) and password (12345678) in the dialog box.

6. In the Server text field, enter the following:

   t3://localhost:7501

   where localhost represents the name of your machine.

7. Click OK.

If you are unable to log in:

• Check for errors in the command window in which you started WebLogic Process Integrator Studio.

• See the section Troubleshooting Your WebLogic Process Integrator Configuration.

• Make sure that the WebLogic Server instance is still running.

• Make sure you ran the script (createOracle, createCloud, or createMSSQL) to create the WebLogic Process Integrator database tables. Refer to Configuring WebLogic Collaborate for WebLogic Process Integrator. (See step 5.)