|
|
|
|
|
|
WebLogic Collaborate Sample Configuration Files
This topic provides system administrators with sample configuration files for BEA WebLogic Collaborate. During installation, these files are automatically customized, so they will work on any supported computer system and network. They are provided here, along with descriptions of the information required in each.
The sample configuration files are provided in teh following sections:
Each file includes sample values for parameters that are updated by the installation program. These sample values are highlighted in bold.
config.xml
By default, the BEA WebLogic Collaborate installation sets up the collaborate/config/samples and collaborate/config/mydomain domains. The configuration for each domain is defined in eXtensible Markup Language (XML). Persistent storage for a domain configuration is provided by the config.xml file located in install_dir/collaborate/config/domain_name, where install_dir is the directory under which WebLogic Integration has been installed (typically <BEA_Home>/wlintegration2.0).
This section presents and describes the contents of the collaborate/config/mydomain/config.xml file
This sample is provided for informational purposes only. The config.xml file should not be edited directly. Any changes made to the file while the domain is active will not have any effect on the domain configuration and will be overwritten by the boot version of the file.
You can view and modify the settings that are captured in the config.xml through the WebLogic Server Administration Console. When you start the WebLogic Server Administration Console as described in Starting the WebLogic Server Administration Console, the server home page is displayed. Items in the navigation tree in the left-pane correspond to the elements and attributes defined in the config.xml file.
The root element of the config.xml file is Domain. The first entry in the domain is the server configuration, as shown in the following figure.
Figure A-1 The config.xml File: Part 1
The Domain and Server elements and attributes define the basic configuration. The settings here are reflected in the WebLogic Server Administration Console. For example, if you select myserver from the navigation tree, the server page is displayed as shown in the following figure. Figure A-2 WebLogic Server Administration Console Server Page
By clicking the appropriate tab on this page, you can update the listen port, log file name, log level and output, and other server configuration parameters. For help with any settings, click the question mark in the upper right to view the online help, or see the WebLogic Server documentation set at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs60
As shown in the following figure, the server element is followed by the specification of the log file, and settings for the JMS JDBC Store, Java Transaction API (JTA), Java Messaging Server (JMS) server, and security.
Figure A-3 The config.xml File: Part 2
To optimize performance, the setting for the JMS JDBC store prefix name should be customized for your database. The syntax for prefix name is [[catalog.]schema.]prefix]. To update the JMS store prefix name, select Services Figure A-4 JMS JDBC Store Page
As shown in the following figure, the next section of the config.xml file deploys the web applications required for the WebLogic Collaborate Administration Console, and the WebLogic Collaborate startup and shut down classes. Figure A-5 The config.xml File: Part 3
As shown in the following figure, the next section of the config.xml file includes JMS connection information for WebLogic Process Integration, and the JDBC connection pool information. The bold text indicates settings that are updated based on the information you provide during installation. The arrow indicates the continuation of text that appears on a single line in the file. For information about updating the JDBC configuration, see Updating the JDBC Connection Pool. Figure A-6 The config.xml File: Part 4
The next section deploys the EJBs required for WebLogic Process Integrator. The deployment order is controlled by the DeploymentOrder setting. You can use this setting as required to control deployment order for custom applications and EJBs. Figure A-7 The config.xml File: Part 5
You can view and update parameters for the applications, Web applications, and EJBs deployed by selecting Deployments from the WebLogic Server Administration Console navigation tree, then selecting the appropriate deployment type. The EJB deployments are shown in the following figure. Figure A-8 Deployments
As shown in the following figure, the next section of the config.xml file sets up the JMS Topics required by WebLogic Process Integrator. Figure A-9 The config.xml File: Part 6
As shown in the following figure, the next section includes the startup class for the WebLogic Process Integrator time processor, and settings for the WebLogic Process Integrator RDBMS Realm security configuration. The values in bold are updated during installation based on the information you provide. The arrows indicate the continuation of text that appears on a single line in the file. Figure A-10 The config.xml File: Part 7
The last section of the file deploys the WebLogic internal management Web applications, and sets up the WebLogic Logic Process Integrator caching realm for the RDBMS security realm. Figure A-11 The config.xml File: Part 8
setEnv.cmd/setEnv.sh
This executable file is used to set the environment variables for WebLogic Collaborate. A version of this file resides in the bin directory under the WebLogic Collaborate installation directory, and in each domain directory. This file is called by the startWeblogic command file and other command files provided with the WebLogic Collaborate distribution.
The setEnv.cmd (Windows) or setEnv.sh (UNIX) file for the collaborate/config/mydomain domain is shown in the following figure. The values in bold are set during installation based on your installation location.
Figure A-12 The setEnv Command
startWebLogic.cmd/startWeblogic.sh
This executable command file starts WebLogic Server. Using the content of the config.xml file, it deploys WebLogic Collaborate, WebLogic Process Integrator, and the WebLogic Collaborate plug-in for WebLogic Process Integrator. It is installed in both the collaborate/config/samples and collaborate/config/mydomain directories.
The startWeblogic.cmd (Windows) or startWeblogic.sh (UNIX) file for the collaborate/config/mydomain domain is shown in the following figure. The arrows indicate the continuation of a line that appears as a single line in the file.
Figure A-13 The startWeblogic Command
fileRealm.properties
This properties file controls the User, Group, and ACL objects that are created when WebLogic Server is started.
The fileRealm.properties file for the collaborate/config/mydomain domain is shown in the following figure.
Figure A-14 The fileRealm.propertis File: Part 1
Figure A-15 The fileRealm.propertis File: Part 2
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|
