![]() |
![]() |
|
|
Setting Up the WebLogic Collaborate Environment
The following sections explain how to set up the BEA WebLogic Collaborate environment:
Before beginning the following procedures, you should complete the installation of the WebLogic Collaborate software and run the installation verification application, as described in the WebLogic Collaborate Installation Guide.
Configuring WebLogic Collaborate for BEA WebLogic Process Integrator
To configure your WebLogic Collaborate environment so that it operates with BEA WebLogic Process Integrator, you need to verify WebLogic Process Integrator Studio and Weblogic Server runtime requirements as described in this section.
Windows NT %WLC_HOME%\enabler
UNIX $WLC_HOME/enabler
The WebLogic Collaborate installation process edits the weblogic.properties file to match your environment. The proper repository pool should be uncommented and configured to the database you selected at install time. You only need to edit weblogic.properties if a problem exists in these configurations.
This step describes how to check the weblogic.ejb.deploy property and the weblogic.jdbc.connectionPool.wlpiPool property configurations.
# WLPI setup.
weblogic.ejb.deploy=\
<WLC_HOME>/lib/wlpi-ejb.jar,\
<WLC_HOME>/lib/wlpi-wlc-ejb.jar,\
<WLC_HOME>/lib/wlpi-cc-ejb.jar
The installation process replaces <WLC_HOME> with the path name to the directory where WebLogic Collaborate is installed on your system. Confirm that the this path is set correctly for your installation.
# Oracle
#
weblogic.jdbc.connectionPool.wlpiPool=\
url=jdbc:weblogic:oracle,\
driver=weblogic.jdbc.oci.Driver,\
loginDelaySecs=1,\
initialCapacity=1,\
maxCapacity=10,\
capacityIncrement=1,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshTestMinutes=10,\
props=user=<WLPIDB_USER>;password=<WLPIDB_PASSWORD>;
server=<ORACLE_SERVICENAME>
# Cloudscape
#
#weblogic.jdbc.connectionPool.wlpiPool=\
# url=jdbc:cloudscape:wlpiwlc,\
#driver=COM.cloudscape.core.JDBCDriver,\
# loginDelaySecs=1,\
# initialCapacity=1,\
# maxCapacity=10,\
# capacityIncrement=1,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshTestMinutes=10
# MSSQL
#
#weblogic.jdbc.connectionPool.wlpiPool=\
# url=jdbc:weblogic:mssqlserver4,\
# driver=weblogic.jdbc.mssqlserver4.Driver,\
# loginDelaySecs=1,\
# initialCapacity=1,\
# maxCapacity=10,\
# capacityIncrement=1,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshTestMinutes=10, \
# testTable=dual,\
# props=user=<MSSQL_WLPI_USER>;
#password=<MSSQL_WLPI_USER_PASSWORD>;
#server=<MSSQL_WLPI_DATABASE>@<MSSQL_HOSTNAME>
The extract above shows that during installation this weblogic.properties file was configured for the Oracle database (the Oracle weblogic.jdbc.connectionPool.wlpiPool property is uncommented). Confirm that the property corresponding to the database you are using is uncommented.
Within the weblogic.jdbc.connectionPool.wlpiPool property, confirm that the configuration is correct for the database you are using:
Note: The Cloudscape database is a single user database and requires no user ID and password configurations in the weblogic.jdbc.connectionPool.wlpiPool property.
prompt> sqlplus SYS/PASSWD @%WLC_HOME%\wlpi\wlpi_oracle.ddl
where:
prompt> sqlplus SYS/PASSWD $WLC_HOME/wlpi/wlpi_oracle.ddl
where:
prompt> createCloud.cmd
prompt> createcloud.sh
prompt> isql -U uid -P passwd -i wlpi_mssql.ddl
where:
Note: By default, the wlpi_database.ddl scripts do not drop tables. If you have existing tables that you wish to drop, edit the appropriate script (wlpi_oracle.ddl, wlpi_cloud.ddl or wlpi_mssql.ddl).
Windows NT %WLC_HOME%
UNIX $WLC_HOME
Windows NTD:\WLCollaborate> setEnv.cmd
UNIX
prompt> setenv.sh
Windows NT
D:\WLCollaborate> cd enabler
UNIX
prompt> cd enabler
Windows NT
D:\WLCollaborate\enabler> startweblogic.cmd
UNIX
prompt> ../startwebLogic.sh
Note: WebLogic Server must be running when you start WebLogic Process Integrator Studio (refer to "Starting WebLogic Process Integrator Studio" on page 2-7).
Troubleshooting Your WebLogic Process Integrator Configuration
If you observe binding errors on the listening port, make sure you do not have another instance of WebLogic Server 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. You use WebLogic Process Integrator Studio to create the workflows for conversations and business processes. Running the WebLogic Process Integrator Verifier Example, includes an example that shows how you can use WebLogic Process Integrator Studio.
To successfully connect to WebLogic Process Integrator, WebLogic Server must still be running after you complete the steps described in Configuring WebLogic Collaborate for BEA WebLogic Process Integrator.
Before building and running the WebLogic Process Integrator example application, verify that you can start WebLogic Process Integrator Studio and connect to WebLogic Server.
Follow these steps to start WebLogic Process Integrator Studio and connect to WebLogic Server:
Windows NT %WLC_HOME%
UNIX $WLC_HOME
Windows NT
D:\WLCollaborate> setEnv.cmd
UNIX
prompt> ../setenv.sh
Windows NT
D:\WLCollaborate> cd wlpi
UNIX
prompt> cd wlpi
Windows NT
D:\WLCollaborate> Studio.cmd
UNIX
prompt> ../studio.sh
t3://localhost:7501
where localhost represents the name of your machine.
If you are unable to log in:
![]() |
![]() |
![]() |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|