Oracle® Web Services Manager Deployment Guide 10g (10.1.3.3.0) Part Number E10298-01 |
|
|
View PDF |
This chapter provides general information for modifying the configuration files for the Oracle Web Services Manager (Oracle WSM) components: Oracle Enterprise Manager 10g Web Services Manager Control (Web Services Manager Control), Oracle WSM Monitor, Oracle WSM Agents, Oracle WSM Gateways, and Oracle WSM Policy Manager.
See Chapter 5, "Deploying Oracle WSM Gateways", for specific information about configuring Oracle Web Services Manager Gateways.
See Chapter 6, "Installing Oracle WSM Agents", for specific information about configuring Oracle Web Services Manager Agents.
This chapter includes the following sections:
Use the wsmadmin
command with the appropriate operation, that is, configApps
, deployApps
or deploy
, to configure and deploy the customized components. See "Deploying Applications" for more information about the wsmadmin
commands to use. See Appendix C, "Oracle Web Services Manager WSMADMIN Commands" for information on the individual commands.
Component Context Root Strings
The portion of the URL address that immediately follows the server name and port specification is called the context root.
http://
server_name:port/context_root/....
The context_root
is mapped to the J2EE application. The HTTP Server uses this mapping to locate the application. Table 3-1 lists the valid context root strings for Oracle WSM components.
Table 3-1 Oracle WSM Context Root Strings
Component Name | Context Root String |
---|---|
Oracle WSM Policy Manager |
|
Web Services Manager Control |
|
Oracle WSM Monitor |
|
Oracle WSM Gateway |
|
An example URL for the Web Services Manager Control is: http://jdoe.us.oracle.com:8888/ccore
.
If you use wsmadmin
commands to deploy your applications, the correct context root strings are used, by default. However, if you use Oracle Enterprise Manager 10g Application Server Control Console to deploy your components, there are no defaults. You must specify the context root strings yourself, and you must use the context root strings in Table 3-1 to ensure that Oracle WSM works properly.
The following is a list of properties that can and cannot be changed:
Properties that can be changed:
Oracle WSM Database instance associated with the Oracle WSM component
Oracle WSM Database connections for multiple components in the ORACLE_HOME
/owsm/config/bin/coresv.properties
file
Properties that cannot be changed:
Host operating system
Host application server
The following sections list the configuration files and identify the properties in each file used to configure each Oracle WSM component.
Related properties in each configuration file are grouped together. For example, in the monitorui-config-installer.properties
file, the properties used to configure the database drivers and URLs are grouped together. In the sections that follow, these groupings are loosely referred to as property groups.
To configure the Web Services Manager Control, you need to modify certain properties files. The default location for the configuration files for the Web Services Manager Control is ORACLE_HOME
/owsm/config/ccore
. The three configuration files that contain properties relevant to the Web Services Manager Control are as follows:
The default location for the monitorui-config-installer.properties
file for the Web Services Manager Control is ORACLE_HOME
/owsm/config/ccore
. This section describes properties in the monitorui-config-installer.properties
file. The properties in this file are grouped together as follows:
This section also contains information about how to enable Java Single Sign-On (JSSO) for the Oracle WSM Monitor. See "Enabling JSSO for the Oracle WSM Monitor", for more information.
The database drivers and URLs properties are used to configure the database URLs and drivers. Table 3-2 lists the properties and provides an example value for each property.
Table 3-2 monitorui-config-installer.properties Database Drivers and URLs Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The UI authentication properties are used to configure the authentication provider used by Web Services Manager Control. You can use a database or an LDAP server to authenticate users. Table 3-3 lists the properties and provides an example value for each property in the Database Authentication Settings property group.
Table 3-3 monitorui-config-installer.properties Database-based Authentication Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 3-4 lists the properties and provides an example value for the LDAP authentication settings properties.
Table 3-4 monitorui-config-installer.properties LDAP-based Authentication Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can specify an e-mail address for your support contact. Use the following property to specify the fully qualified e-mail address of your support contact:
ui.supportContact.email=
support_contact_email_address
The Oracle WSM Monitor Repository properties are used to configure the Web Services Manager Control Repository. Table 3-5 lists the properties and provides examples values.
Table 3-5 monitorui-config-installer.properties Oracle WSM Monitor Repository Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
This is the property that contains the encoded password for the repository. |
|
|
|
|
|
|
|
|
|
|
|
|
|
This property contains the encoded password for the component repository. |
|
|
|
|
|
|
The Oracle WSM Monitor communicates with and exchanges information with the Web Services Manager Control. The two properties you can use to set up the pairing between these two components are ui.om.server.rmiHost
and ui.om.server.rmiPort
.
Table 3-6 lists properties and description of the Corda settings.
Table 3-6 monitorui-config-installer.properties Corda Settings
Property | Description |
---|---|
|
The valid values for this property are |
|
If you have set |
|
If you have set |
The Notification Engine properties are used to collect information used for business analysis. Table 3-7 lists the properties and description of each property.
Table 3-7 monitorui-config-installer.properties Notification Engine Settings
Property | Description |
---|---|
|
The value for this property defaults to the e-mail address in |
|
Leave this property blank if you want to use the default toolkit. |
|
The value for this property is the DNS name for the management software. |
|
This property contains the port number where traps will be sent. The default value is 162. |
|
The value for this property is the authentication protocol for the management software. |
|
The value for this property is the user name to authenticate on traps. |
|
The value for this property is the password to authenticate on traps. |
The Oracle Web Services Manager Installation Guide describes how to enable JSSO for the Oracle WSM Monitor, by editing the install.properties
file. Follow this procedure to enable JSSO for the Oracle WSM Monitor.
To enable JSSO for the Oracle WSM Monitor
Open the ORACLE_HOME
/owsm/bin/install.properties
file, and verify that the following parameter is set:
install.sso.support=true
Go to ORACLE_HOME
/owsm/bin
and run the wsmadmin deploy
command:
wsmadmin deploy
control
The default location for the policyui-config-installer.properties
file for the Web Services Manager Control is ORACLE_HOME
/owsm/config/ccore
. This section describes properties in the policyui-config-installer.properties
file. The properties in this file are grouped together as follows:
Use these settings to configure the database URLs and drivers. Table 3-8 lists properties and examples of values in the Database Drivers property group of the policyui-config-installer.properties
file:
Table 3-8 policyui-config-installer.properties Database Drivers and URLs Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use these settings to configure the authentication provider used by the Web Services Manager Control. Currently you can select database-based authentication or LDAP-based authentication. Table 3-9 lists properties and examples of values in database-based authentication property group of the policyui-config-installer.properties
file.
Table 3-9 policyui-config-installer.properties Database-based Authentication Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 3-10 lists properties and examples of values in LDAP-based authentication property group of the policyui-config-installer.properties
file.
Table 3-10 policyui-config-installer.properties LDAP-based Authentication Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can specify an e-mail address for your support contact. Use the following property to specify the fully qualified e-mail address of your support contact:
ui.supportContact.email=support_contact_email_address
Use these property settings to configure the Web Services Manager Control Repository. Table 3-11 lists properties and examples of values in Web Services Manager Control Repository property group of the policyui-config-installer.properties
file:
Table 3-11 policyui-config-installer.properties Web Services Manager Control Repository Settings
Property | Example |
---|---|
|
jdbc:polite4@localhost:1531:orawsm |
|
oracle.lite.poljdbc.POLJDBCDriver |
|
|
|
The value for this property contains the encoded password for the component repository. |
|
5 |
|
|
|
|
The default location for the ui-config-installer.properties
file for the Web Services Manager Control is ORACLE_HOME
/owsm/config/ccore
. This section describes properties in the ui-config-installer.properties
file. The properties in this file are grouped together as follows:
Use these settings to configure the database URLs and drivers. Table 3-12 lists properties and examples of values in the Database Drivers and URLs property group of the ui-config-installer.properties
file:
Table 3-12 ui-config-installer.properties Database Drivers and URLs Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use these settings to configure the authentication provider used by the Web Services Manager Control. Currently you can select database-based authentication or LDAP-based authentication. Table 3-13 lists parameters and examples of values in the database-based authentication provider property group of the ui-config-installer.properties
.
Table 3-13 ui-config-installer.properties Database-based Authentication Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ignore this parameter. It is obsolete. |
|
Ignore this parameter. It is obsolete. |
Table 3-14 lists parameters and examples of values in the LDAP-based authentication provider property group of the ui-config-installer.properties
.
Table 3-14 ui-config-installer.properties LDAP-based Authentication Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can specify an e-mail address for your support contact. Use the following property, and specify the fully qualified e-mail address of your support contact:
ui.supportContact.email=support_contact_email_address
Use these property settings to configure the Web Services Manager Control Repository. Table 3-15 lists parameters and examples of values in the Administrative Repository property group of the ui-config-installer.properties
.
Table 3-15 ui-config-installer.properties Administrative Repository Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
The value for this property contains the encoded password for the repository. |
|
|
|
|
|
|
|
|
|
|
|
|
|
The value for this property contains the encoded password for the component repository. |
|
|
|
|
|
|
The ui-config-installer.properties
file lists parameters and values in the Oracle WSM Monitor property group. The two properties you can use to set up Oracle WSM Monitor are ui.om.server.rmiHost
and ui.om.server.rmiPort
.
These values can be set in the Corda property group of the ui-config-installer.properties
file.
The Notification Engine properties are used to collect information used for business analysis. Use these property settings to configure the notification engine. Table 3-16 lists properties and examples of values in the Notification property group of the ui-config-installer.properties
file.
Table 3-16 ui-config-installer.properties Notification Engine Settings
Property | Description |
---|---|
|
The value for this property defaults to address in |
|
Leave the value for this property blank if you want to use the default toolkit. |
|
The value for this property contains the DNS name for the management software |
|
This property contains the port number where traps will be sent. The default value is 162. |
|
This is the authentication protocol for the management software. |
|
The value for this property is the user name to authenticate on traps. |
|
The value for this property is the password used to authenticate traps. |
To configure the Oracle WSM Monitor, you need to modify certain properties files. The default location for the configuration files for the Oracle WSM Monitor is ORACLE_HOME
/owsm/config/coreman
. The two configuration files that contain properties relevant to the Oracle WSM Monitor are as follows:
The default location for the collector-config-installer.properties
file for the Oracle WSM Monitor is ORACLE_HOME
/owsm/config/coreman
. Table 3-17 lists properties and examples of values in the collector-config-installer.properties
file.
Table 3-17 collector-config-installer.properties Database Drivers and URLs Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The default location for the monitor-config-installer.properties file
for the Oracle WSM Monitor is ORACLE_HOME
/owsm/config/coreman
. The properties in this file are grouped together as follows:
Database Driver
Oracle WSM Monitor Repository
Oracle WSM Monitor and Web Services Manager Control Pairing
Notification Engine
Use these settings to configure the database URLs and drivers. Table 3-18 lists properties and examples of values in the Database Driver property group of the monitor-config-installer.properties
file:
Table 3-18 monitor-config-installer.properties Database Drivers and URLs Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use these property settings to configure the Web Services Manager Control Repository. Table 3-19 lists properties and examples of values in the Oracle WSM Monitor Repository property group of the monitor-config-installer.properties
file.
Table 3-19 monitor-config-installer.properties Oracle WSM Monitor Repository Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
The value for this property contains the encoded password for the repository. |
The Web Services Manager Control communicates with the Oracle WSM Monitor. The monitor-config-installer.properties
file lists properties and values in the Oracle WSM Monitor and Web Services Manager Control Pairing property group.
Table 3-20 lists properties and examples of values in Oracle WSM Monitor and Web Services Manager Control Pairing group of the monitor-config-installer.properties
file:
The Notification Engine properties are used to collect information used for business analysis. Use these property settings to configure the notification engine. Table 3-21 lists properties and examples of values in the Notification property group of the monitor-config-installer.properties
file.
Table 3-21 monitor-config-installer.properties Notification Engine Settings
Property | Description |
---|---|
|
The value defaults to the e-mail address in the |
|
Leave this blank if you want to use the default toolkit. |
|
This property contains the DNS name for the management software. |
|
This property is the Port number where traps will be sent. The default value is 162. |
|
This property contains the authentication protocol for the management software. |
|
This property contains the user name to authenticate on traps. |
|
This property contains the password to authenticate on traps. |
To configure the Oracle WSM Policy Manager, you modify properties in a single configuration file, ORACLE_HOME
/owsm/config/policymanager/policymanager-config-installer.properties
. This section contains a brief description of this property file.
The default location for the policymanager-config-installer.properties
file for the Oracle WSM Policy Manager is ORACLE_HOME
/owsm/config/policymanager
. The properties in this file are grouped together as follows:
Use these property settings to configure the Oracle WSM Policy Manager Repository. Table 3-22 lists properties and examples of values in the Oracle WSM Policy Manager Repository property group of the policymanager-config-installer.properties
file.
Table 3-22 policymanager-config-installer.properties Policy Repository Settings
Property | Example |
---|---|
|
|
|
|
|
system |
|
This property contains the encoded password for the component repository. |
|
5 |
|
|
|
|
Use these property settings to configure the Oracle WSM Policy Manager Repository. Table 3-23 lists properties and examples of values in the Oracle WSM Policy Manager Component Repository property group of the policymanager-config-installer.properties
file.
Table 3-23 policymanager-config-installer.properties Component Repository Settings
Property | Example |
---|---|
|
|
|
|
|
|
|
This property contains the password for the component repository. |
The default location for the Oracle Web Services Manager Gateway configuration file is ORACLE_HOME/
owsm/config/gateway/gateway-config-installer.properties
. The properties in this file are grouped together as follows:
Component ID
Administrative Repository
Transport Protocol
The default location for the Oracle WSM server agent configuration file is ORACLE_HOME
/owsm/config/serveragent/serveragent-config-installer. properties
. The properties in this file are grouped together as follows:
Component ID
Container Type
Policy Manager
Policy Settings
The default location for the Oracle WSM client agent configuration file is ORACLE_HOME
/owsm/config/clientagent/clientagent-config-installer. properties
. The properties in this file are grouped together as follows:
Component ID
Container Type
Policy Manager
Policy Settings
You can modify the ORACLE_HOME
/owsm/config/bin/coresv.properties
files to specify database connections for multiple components. Table 3-24 lists properties, property descriptions, and sometimes provides examples of values to configure database connections:
Table 3-24 Database Connection Parameters in the coresv.properties File
Property | Values and Descriptions |
---|---|
|
Indicates the type of database: oracle, sqlserver, or olite. |
|
Indicates the type of database driver: thin or thick. |
|
The machine name where the database is installed, or the IP address. |
|
This is the jdbc port. |
|
The name of the Oracle WSM Database (default is CCORE, when it is an Oracle Database). |
|
The user name to log in to the Oracle WSM Database. |
|
The password to log in to the Oracle WSM Database. |
|
The same value as |
|
The URL for the JDBC driver associated with the database. For example, |
|
If using OLite, the only valid value is thin. For Oracle Database 10g, specify thick or thin. |
|
The administrator account to log in to the database. The default is |
|
The password associated with the account specified by |
|
The name of the database instance where the Oracle WSM Repository is stored. (The default is CCORE). |
Oracle WSM Monitor captures and stores service details, status, and performance metrics from each service request or response handled by Oracle WSM gateways or agents. You can configure Oracle WSM so that specific conditions trigger an alarm. A processing rule, which is a response to the alarm, is then executed. One possible response is to send an e-mail to the appropriate individuals. In order for the e-mail to be sent, you must configure Oracle WSM with the e-mail server and account information. See Chapter 6, "Monitoring Oracle Web Services Manager, in Oracle Web Services Manager Administrator's Guide for more information about sending an e-mail notification when an alarm is triggered.
To configure Oracle WSM for e-mail notification
Edit the properties in the ORACLE_HOME
/owsm/config/ccore/ui-config-installer.properties
file (Table 3-25).
Table 3-25 ui-config-installer.properties File
Property Name | Description |
---|---|
|
Name of the E-mail server that sends the e-mail notifications. |
|
SMTP port on which the E-mail server sends the e-mail notifications. |
|
User name of the account used to send e-mail notifications. |
|
Password of the account used to send e-mail notifications. This password must be obfuscated. Use the |
|
E-mail account from which the e-mail notifications are sent. |
Edit the properties in the ORACLE_HOME
/owsm/config/coreman/monitor-config-installer.properties
file (Table 3-26).
Table 3-26 monitor-config-installer.properties File
Property Name | Description |
---|---|
|
Name of the E-mail server that sends the e-mail notifications. |
|
SMTP port on which the E-mail server sends the e-mail notifications. |
|
User name of the account used to send e-mail notifications. |
|
Password of the account used to send e-mail notifications. This password must be obfuscated. Use the |
|
E-mail account from which the e-mail notifications are sent. |
Edit the properties in the ORACLE_HOME
/owsm/config/ccore/monitorui-installer.properties
file (Table 3-27).
Table 3-27 monitor-ui-config-installer.properties File
Property Name | Description |
---|---|
|
Name of the E-mail server that sends the e-mail notifications. |
|
SMTP port on which the E-mail server sends the e-mail notifications. |
|
User name of the account used to send e-mail notifications. |
|
Password of the account used to send e-mail notifications. This password must be obfuscated. Use the |
|
E-mail account from which the e-mail notifications are sent. |
Redeploy the Web Services Manager Control and the Oracle WSM Monitor components using the wsmadmin deploy
command.
Note:
See Appendix C, "Oracle Web Services Manager WSMADMIN Commands" for more information on thewsmadmin deploy
and wsmadmin encodePasswords
commands.