|
|
|
|
|
|
BEA WebLogic Process Integrator Sample Configuration Files
This section provides system administrators with sample configuration files for the BEA WebLogic Process Integrator. During installation, these files are automatically customized, so they will work on your computer system/network. They are provided here with an explanation of what they should contain. The specific settings that are changed by the installer are marked bold, and an explanation of those changes is made after the code block. The following sample configuration files are provided:
This section should also be used as reference for any manual configurations that are required after the initial installation of BEA WebLogic Process Integrator. Examples:
A section entitled "Configuring BEA WebLogic Server Security Realm for BEA WebLogic Process Integrator" has been included after the "rdbmsrealm.properties" section. This section provides instructions to those BEA WebLogic Process Integrator users who want to configure a particular BEA WebLogic Server security realm to work with BEA WebLogic Process Integrator.
weblogic.properties
This is the WLPI Specific Settings section of the specialized BEA WebLogic Process Integrator version of the BEA WebLogic Server weblogic.properties file. It is located near the end of the file. It is installed into the root directory of BEA WebLogic Process Integrator (the default root directory is c:\bea\wlprocessintegrator1.2).
Listing A-1 Sample WLPI Specific Settings Section of weblogic.properties
# ***************************************************************
# WLPI Specific Settings *
# ***************************************************************
# Security realm
weblogic.security.realmClass=com.bea.wlpi.rdbmsrealm.RDBMSRealm
#weblogic.security.realm.debug=true
# ***************************************************************
# Information stored in the RDBMS realm
# If you want to use WebLogic Process Integrator with the Weblogic
# Properties Realm simply comment out the line
# "weblogic.security.realmClass=..." and
# un-comment the following lines.
# NOTE: any information added to the RDBMS realm after the initial
# installation will not be reflected here automatically - you must
# add it manually. ****************************************************************
# WLPI users
#weblogic.password.admin=security
#weblogic.password.system=security
#weblogic.password.wlpisystem=wlpisystem
#weblogic.password.joe=password
#weblogic.password.mary=password
# WLPI groups
#weblogic.security.group.wlpiUsers=system,joe,mary,admin
#weblogic.security.group.wlpiAdministrators=wlpisystem,system,admin,joe,mary
# WLPI orgs
#weblogic.security.group.WLPIOrg@ORG1=joe,mary,admin
#weblogic.security.group.WLPIOrg@ORG2=joe,mary,admin
# WLPI roles
#weblogic.security.group.WLPIRole@Role1+ORG1=joe,mary,admin
#weblogic.security.group.WLPIRole@Role1+ORG2=joe,mary,admin
#weblogic.security.group.WLPIRole@Role2+ORG1=joe,mary,admin
#weblogic.security.group.WLPIRole@Role2+ORG2=joe,mary,admin
# ACLs and permissions.
weblogic.allow.list.weblogic.jndi.weblogic=everyone
weblogic.allow.list.weblogic.jndi.weblogic.ejb=everyone
weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
weblogic.allow.execute.weblogic.servlet.containerManaged=everyone
weblogic.allow.reserve.weblogic.jdbc.connectionPool.wlpiPool=everyone
weblogic.allow.reset.weblogic.jdbc.connectionPool.wlpiPool=guest,admin
weblogic.allow.shrink.weblogic.jdbc.connectionPool.wlpiPool=guest,admin
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# WEBLOGIC EJB PROPERTIES
# -------------------------------------------------
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# *per-cluster* properties file ONLY.
# Workaround for WebLogic session bean timeout 'feature'.
weblogic.rmi.dgc.idlePeriodsUntilTimeout=1000
# Deploy enterprise JavaBeans.
weblogic.ejb.deploy=./lib/wlpi-ejb.jar,./lib/pobean.jar
# Connection pool for MS SQL Server 7.0 using Type 4 jDriver.
##MSSQL##weblogic.jdbc.connectionPool.wlpiPool=\
##MSSQL## url=jdbc:weblogic:mssqlserver4:<MSSQL_DBNAME>@<MSSQL_HOSTNAME>:<MSSQL_PORT>?sql7=true,\
##MSSQL## driver=weblogic.jdbc.mssqlserver4.Driver,\
##MSSQL## loginDelaySecs=1,\
##MSSQL## initialCapacity=1,\
##MSSQL## maxCapacity=2,\
##MSSQL## capacityIncrement=1,\
##MSSQL## allowShrinking=true,\
##MSSQL## shrinkPeriodMins=15,\
##MSSQL## refreshTestMinutes=10,\
##MSSQL## props=user=<MSSQL_USER>;password=<MSSQL_PASSWORD>
# Connection pool to Oracle using Type 4 (thin) JDBC driver. (1)
weblogic.jdbc.connectionPool.wlpiPool=\
url=jdbc:oracle:thin:@mydbhost:1521:mydb,\ #(2)
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=1,\
maxCapacity=3,\
capacityIncrement=1,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshTestMinutes=10,\
props=user=wlpidbadm;password=password;\ #(3)
# Connection pool to Sybase using jConnect JDBC driver.
##SYBASE##weblogic.jdbc.connectionPool.wlpiPool=\
##SYBASE## url=jdbc:sybase:Tds:<SYBASE_HOSTNAME# Connection pool to CLOUDSCAPE
##CLOUDSCAPE## weblogic.jdbc.connectionPool.wlpiPool=\
##CLOUDSCAPE## url=jdbc:cloudscape:<CLOUDSCAPE_DBNAME>,\
##CLOUDSCAPE## driver=COM.cloudscape.core.JDBCDriver,\
##CLOUDSCAPE## initialCapacity=1,\
##CLOUDSCAPE## maxCapacity=2,\
##CLOUDSCAPE## capacityIncrement=1,\
##CLOUDSCAPE## props=user=none;password=none;server=none# DataSource setup
weblogic.jdbc.TXDataSource.com.bea.wlpi.TXDataSource=wlpiPool
# JMS topic connection factory. For persistent JMS, set DeliveryMode=persistent
weblogic.jms.connectionPool=wlpiPool
weblogic.jms.connectionFactoryName.wlpiFactory=com.bea.wlpi.TopicConnectionFactory
weblogic.jms.connectionFactoryArgs.wlpiFactory=DeliveryMode=non_persistent
# JMS topics
weblogic.jms.topic.wlpiAudit=com.bea.wlpi.AuditTopic
weblogic.jms.topic.wlpiError=com.bea.wlpi.ErrorTopic
weblogic.jms.topic.wlpiEvent=com.bea.wlpi.EventTopic
weblogic.jms.topic.wlpiTimer=com.bea.wlpi.TimerTopic
weblogic.jms.topic.wlpiNotify=com.bea.wlpi.NotifyTopic
# Mail session
weblogic.resource.MailSession.com.bea.wlpi.MailSession=\
mail.from=user@host,\
mail.host=xyz.bea.com #(4)
.
.
.
- The JDBC driver section for your database was uncommented by removing the pound (#) characters. In this sample, the Oracle JDBC driver section was uncommented.
- Your database name, host server, and port were specified in the line beginning with url=. In this sample, the host server is mydbhost (by @ sign), the port is 1521 (which is the default), and the database name is mydb. The installation program retrieves these values from the database configuration dialog box that is displayed during installation. The Oracle version of this dialog box showing these same sample settings is shown in Figure 2-10.
- The settings user= and password= are set to an account with create/update/delete privileges on the database server. In this sample, the user is wlpidbadm, and the password is password. The installation program retrieves these values from the database configuration dialog box that is displayed during installation. The Oracle version of this dialog box showing these same sample settings is shown in Figure 2-10.
- This is an optional setting and the only setting that is made manually with a text editor. mail.host must be set to your outgoing mail or SMTP server. For more detailed instructions, see Step 1. Editing the weblogic.properties File in Configuring and Starting BEA WebLogic Process Integrator.
rdbmsrealm.properties
This is the command (or sh) file that sets the environment variables for the database connections to BEA WebLogic Process Integrator. It is installed into the root directory of BEA WebLogic Process Integrator (the default directory is the root directory, c:\bea\wlprocessintegrator1.2).
Listing A-2 Sample rdbmsrealm.properties File
#####################################
# - - - - - - MS SQL Server 7.0 - - - - - - -
##MSSQL##driver=weblogic.jdbc.mssqlserver4.Driver
##MSSQL##dbURL=jdbc:weblogic:mssqlserver4:<MSSQL_DBNAME>@<MSSQL_HOSTNAME>:<MSSQL_PORT>?sql7=true
##MSSQL##dbUser=<MSSQL_USER>
##MSSQL##dbPassword=<MSSQL_PASSWORD>
# - - - - - - ORACLE Thin - - - - - - - # (1)
driver=oracle.jdbc.driver.OracleDriver
dbURL=jdbc:oracle:thin:@mydbhost:1521:mydb # (2)
dbUser=wlpidbadm
dbPassword=password # (3)
getGroupNewStatement=false
# - - - - - - SYBASE using jConnect - - - - -
##SYBASE##dbURL=jdbc:sybase:Tds:<SYBASE_HOSTNAME>:<SYBASE_PORT>/<SYBASE_DBNAME>
##SYBASE##driver=com.sybase.jdbc.SybDriver
##SYBASE##useMultipleConnections=true
##SYBASE##dbUser=<SYBASE_USER>
##SYBASE##dbPassword=<SYBASE_PASSWORD>
# - - - - - - CLOUDSCAPE - - - - - -
##CLOUDSCAPE##dbURL=jdbc:cloudscape:<CLOUDSCAPE_DBNAME>;create=true;autocommit=false
##CLOUDSCAPE##driver=COM.cloudscape.core.JDBCDriver
##CLOUDSCAPE##getGroupNewStatement=true
##CLOUDSCAPE##dbUser=
##CLOUDSCAPE##dbPassword=
##CLOUDSCAPE##getGroupNewStatement=true# Prepared statements for querying
getUser=SELECT U_NAME, U_PASSWORD FROM users WHERE U_NAME = ?
getGroupMembers=SELECT GM_GROUP, GM_MEMBER from groupmembers WHERE GM_GROUP = ?
getAclEntries=SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries WHERE A_NAME = ? ORDER BY A_PRINCIPAL
getUsers=SELECT U_NAME, U_PASSWORD FROM users
getGroups=SELECT GM_GROUP, GM_MEMBER FROM groupmembers ORDER BY GM_GROUP
getAcls=SELECT A_NAME, A_PRINCIPAL, A_PERMISSION FROM aclentries ORDER BY A_NAME, A_PRINCIPAL
getPermissions=SELECT DISTINCT A_PERMISSION FROM aclentries
getPermission=SELECT DISTINCT A_PERMISSION FROM aclentries WHERE A_PERMISSION = ?
# Prepared statements for insertions
newUser=INSERT INTO users VALUES ( ? , ? )
addGroupMember=INSERT INTO groupmembers VALUES ( ? , ? )
# Prepared statements for deletions
removeGroupMember=DELETE FROM groupmembers WHERE GM_GROUP = ? AND GM_MEMBER = ?
removeLastGroupMember=UPDATE groupmembers SET GM_MEMBER = '' WHERE GM_GROUP = ? AND GM_MEMBER = ?
deleteUser1=DELETE FROM users WHERE U_NAME = ?
deleteUser2=DELETE FROM groupmembers WHERE GM_MEMBER = ?
deleteUser3=DELETE FROM aclentries WHERE A_PRINCIPAL = ?
deleteGroup1=DELETE FROM groupmembers WHERE GM_GROUP = ?
deleteGroup2=DELETE FROM aclentries WHERE A_PRINCIPAL = ?
- The JDBC driver section for your database was uncommented by removing the pound (#) characters. In this sample, the Oracle JDBC driver section was uncommented.
- Your database name, host server, and port were specified in the line beginning with dbURL=. In this sample, the host server is mydbhost (by @ sign), the port is 1521 (which is the default), and the database name is mydb. The installation program retrieves these values from the database configuration dialog box that is displayed during installation. The Oracle version of this dialog box showing these same sample settings is shown in Figure 2-10.
- The settings dbUser= and dbPassword= are set to an account with create/update/delete privileges on the database server. The installation program retrieves these values from the database configuration dialog box that is displayed during installation. In this sample, dbUser is set to wlpidbadm, and dbPassword is set to password. The Oracle version of this dialog box showing these same sample settings is shown in Figure 2-10.
Configuring BEA WebLogic Server Security Realm for BEA WebLogic Process Integrator
This section provides instructions to those BEA WebLogic Process Integrator users who want to configure a particular BEA WebLogic Server security realm to work with BEA WebLogic Process Integrator.
User, role, and organization information within BEA WebLogic Process Integrator is maintained in BEA WebLogic Server security realms. Creating a new user, role, or organization within BEA WebLogic Process Integrator means adding those entities to the BEA WebLogic Server security realm. Therefore, the functions of creating and deleting users, roles, and organizations are accessible only if a manageable realm is used and detected by BEA WebLogic Process Integrator.
An example of configuring a BEA WebLogic Server security realm for BEA WebLogic Process Integrator can be found in the weblogic.properties file and is repeated at the beginning of Listing A-1. The file weblogic.properties uses the realmClass com.bea.wlpi.rdbmsrealm.RDBMSRealm to configure BEA WebLogic Process Integrator security.
Your security realm needs to be implemented within BEA WebLogic Server and must follow certain guidelines:
- The realm's group names need to accept the "@" symbol as well as the "+" symbol.
- BEA WebLogic Process Integrator users are BEA WebLogic Server users.
- You must create the following three users:
- wlpisystem
- admin
- system
- You must create the following two groups:
- wlpiUsers
- wlpiAdministrators
- The users system and admin need to belong to the wlpiUsers group.
- The users wlpisystem, system, and admin need to belong to the wlpiAdministrators group.
- WLPI organizations are BEA WebLogic Server groups.
- The organization name should be WLPIOrg@OrgName.
- For example, to create an organization called ORG1, you must create the BEA WebLogic Server group WLPIOrg@ORG1.
- To make the users belong to the ORG1 organization, you need to add them to the WLPIOrg@ORG1 group.
- BEA WebLogic Process Integrator Roles are BEA WebLogic Server groups.
- The group name should be WLPIRole@RoleName+OrgName.
- For example, to create a Role called Role1 within the ORG1 organization, you must create the BEA WebLogic Server group WLPIRole@Role1+ORG1.
- To make the users belong to the Role1 role, you need to add them to the WLPIRole@Role1+ORG1 group.
Once your realm is populated (using the above guidelines), you can use the BEA WebLogic Process Integrator Studio to create users, roles, and organizations without having to use the above syntax.
setwlpiserverenv.cmd (setwlpiserverenv.sh)
This is the command (or sh) file that sets the environment variables for the BEA WebLogic Process Integrator server. It is installed into the bin directory under the root directory of BEA WebLogic Process Integrator (the default directory is c:\bea\wlprocessintegrator1.2\bin).
Listing A-3 Sample setwlpiserverenv.cmd (setwlpiserverenv.sh) file
@rem Copyright (c) 2000 BEA Systems, Inc. All rights reserved.
@rem setWLPIServerEnv.cmd - establish WebLogic Process Integrator Server runtime environment.
@echo off
rem Set JAVA_HOME to the directory containing your Java 2 runtime environment.
set JAVA_HOME=c:\jdk1.2.2 (1)
rem Set WL_HOME to the directory containing WebLogic Server 5.1.
set WL_HOME=c:\weblogic (2)
rem Set JDBC_DRIVER to a classpath entry for the JDBC driver you are using.
rem Classpath entries can be directories, zip files, or jar files. Multiple entries
rem must be semicolon separated. You must install the JDBC driver yourself.
rem Supported databases include:
rem Microsoft SQL Server
rem ##MSSQL## set JDBC_DRIVER=%WL_HOME%\mssqlserver4\classes
rem Oracle 8.1.5
set JDBC_DRIVER=%WL_HOME%\lib\classes12_01.zip;%WL_HOME%\lib\
nls_charset12_01.zip (3)
rem Sybase System 11
rem ##SYBASE## set JDBC_DRIVER=%WL_HOME%\jConnect-4_2\classes
rem Cloudscape
rem ##CLOUDSCAPE## set JDBC_DRIVER=%WL_HOME%\eval\cloudscape\lib\cloudscape.jarrem Set WLPI_HOME to the directory containing WebLogic Process Integrator.
set WLPI_HOME=c:\bea\wlprocessintegrator1.2 (4)
rem Set BEA_HOME to the directory containing WebLogic Process Integrator license.
set BEA_HOME=c:\bea (5)
- JAVA_HOME: This variable represents the root of the Java run-time environment (for example, c:\jdk1.2.2). BEA WebLogic Process Integrator expects to find a Java archive called jre\lib\rt.jar in the subdirectory of this path.
- WL_HOME: This variable represents the root of the BEA WebLogic Server installation directory (for example, c:\weblogic).
- JDBC_DRIVER: This variable represents the directory path containing the JDBC driver classes, .jar, or .zip. This variable is set similar to the following values based on your database.
- WLPI_HOME: This variable represents the root of the BEA WebLogic Process Integrator installation directory (default is c:\bea\wlprocessintegrator1.2).
- BEA_HOME: This variable represents the BEA Home directory (default is c:\bea). Starting with the 1.2 release of BEA WebLogic Process Integrator, all BEA products will be installed under this directory, and there will be one license.bea file for all BEA products installed under the BEA Home directory.
setwlpiclientenv.cmd (setwlpiclientenv.sh)
This is the command (or sh) file that sets the environment variables for the BEA WebLogic Process Integrator client. The BEA WebLogic Process Integrator clients are the Studio and the Worklist. The setwlpiclientenv file is installed into the bin directory under the root directory of BEA WebLogic Process Integrator (the default directory is c:\bea\wlprocessintegrator1.2\bin).
Listing A-4 Sample setwlpiclientenv.cmd (setwlpiclientenv.sh) File
@rem Copyright (c) 2000 BEA Systems, Inc. All rights reserved.@rem SetWLPIClientEnv.cmd - establish WebLogic Process Integrator client runtime environment.@echo offrem Set JAVA_HOME to the location of your Java 2 runtime environment.set JAVA_HOME=c:\jdk1.2.2 # (1)rem Set WLPI_HOME to the directory containing WebLogic Process Integrator.set WLPI_HOME=c:\bea\wlprocessintegrator1.2 # (2)
- JAVA_HOME: This variable represents the root of the Java run-time environment (for example, c:\jdk1.2.2). BEA WebLogic Process Integrator expects to find a Java archive called jre\lib\rt.jar in the subdirectory of this path.
- WLPI_HOME: This variable represents the root of the BEA WebLogic Process Integrator installation directory (for example, c:\bea\wlprocessintegrator1.2).
Copyright © 2000 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.