4
Advanced Installation Options

After the dsinstall.sql script has been run, a package named DS_Properties is created as a result of installing the DSSYS schema. Through this package, you can call a setProperty procedure to change system properties of your current Dynamic Services instance. The advanced installation options include the following:

Enabling PL/SQL interfaces (see Section 4.1)
Enabling persistent auditing or event monitor services (see Section 4.2)
Enabling HTTP communication (see Section 4.3)
Enabling Java Messaging Services (JMS) (see Section 4.4)
Using LDAP as a central master registry (see Section 4.5)
Manually fine-tuning Dynamic Services properties (see Section 4.6)

Section 4.1 through Section 4.6 describe these advanced installation options that are provided in the installation package. These options can be invoked with the individual scripts described in each section. Most of these scripts call the DS_Properties.setProperty procedure.

Important:

In part of Section 4.3.1, directory paths often show only the UNIX path "/" specification. If you are installing on a Windows NT system, the path specification is "\" and you must make this change, as needed, for the installation to be successful.

4.1 Enabling PL/SQL Interfaces

This installation option coincides with the PL/SQL deployment view described in Section 1.3.2.

Run the provided SQL script named dssys_plsql_init.sql that is provided to grant the necessary permissions to user DSSYS.
1. Go to the directory location (ds/sql on UNIX systems or ds\sql on Windows NT systems) of the ds_plsql_init.sql file.
2. Log in to SQL*Plus as user SYS, as follows:
```
sqlplus SYS/<SYS-password>
```
3. Run the dssys_plsql_init.sql script as follows:
```
SQL> @dssys_plsql_init.sql
```
Running this script grants the necessary permissions to user DSSYS.
Next, run the SQL script named ds_plsql.sql that is provided to install the PL/SQL interface.
1. Go to the directory location on UNIX systems (ds/sql) or on Windows NT systems (ds\sql) of the ds_plsql.sql file.
2. Log in to SQL*Plus as user DSSYS as follows:
```
sqlplus DSSYS/<DSSYS-password>
```
3. Run the ds_plsql.sql script as follows:
```
SQL> @ds_plsql.sql
```
The following happens upon running this ds_plsql.sql script:
- At the beginning of the script, another script is invoked to load the Dynamic Services library into Oracle JVM, along with its dependent libraries.
- Next, a subsequent script makes declarations of a PL/SQL package called DynamicServices, mapped to the Java Stored Procedures exposed by the library.
- The ds_plsql.log file is checked to verify the installation of the package.
- Then, the script is completed.
Describe the DynamicServices package by issuing the following command at a SQL*Plus prompt.
```
SQL> desc DynamicServices
```
A sample, anonymous PL/SQL block is run to test the functions, having already registered the YahooPortfolio service as described in Section 3.2. A sample PL/SQL script demo/consumer/sample.sql on UNIX systems or demo\consumer\sample.sql on Windows NT systems, found in the Dynamic Services installation directory, tests the DynamicServices package that was just installed.

Refer to Section 5.2 for a more detailed description of how you can use the PL/SQL interface.

4.2 Enabling Persistent Auditing or Event Monitor Services

Dynamic Services offers a persistent auditing feature in which events that can be thrown during execution, can be monitored. The monitoring process involves triggering of services to be executed upon receipt of a certain event. These services that get triggered are called monitor services. A standalone monitor utility enables the process of auditing these events. Persistent auditing performs among other tasks, service execution logging and event failure notification. See Section 4.2.6 for an example of using the logger monitor service.

4.2.1 Configuring Oracle Advanced Queuing

Because Dynamic Services makes use of Oracle Advanced Queuing for delivering event messages, you must also set the dynamic init.ora parameter aq_tm_processes for your database instance to a non-zero value (for example, set it to 1) as shown in Example 4-1.

Example 4-1 Set the aq_tm_process init.ora Parameter

aq_tm_processes = 1

Refer to Oracle Advanced Queuing documentation for more information. Restart the database instance after you modify the init.ora file.

4.2.2 Installing Monitor Services

By default, monitor services (which are mostly JDBC services), insert entries into tables under the DSSYS schema. If you changed the password for DSSYS, modify the default DSSYS password in the MonitorInstall.dss file to reflect that change.

Before installing the event monitor services, you must first configure the MonitorInstall.dss file in the etc/dsadmin directory on UNIX systems or etc\dsadmin directory on Windows NT systems to point to the database where the monitor services will write information. (Most of these monitor services are database services that just load some processed information into tables.) Make this the same database as the one used for the Dynamic Services engine instance shown in Example 4-2. To make use of the of the notifier service, which is an SMTP service, you must also configure the SMTP mail related properties in the MonitorInstall.dss file.

Example 4-2 Configure the MonitorInstall.dss File

On UNIX systems:
bin/dsadmin -i etc/dsadmin/MonitorInstall.dss

On Wimdows NT systems:
bin\dsadmin -i etc\dsadmin\MonitorInstall.dss

Then, run the dsmoninstall.sql script in the ds/sql directory on UNIX systems or ds\sql directory on Windows NT systems. Running this SQL script will install the tables required by the monitor services.

Go to the directory location (ds/sql on UNIX systems or ds\sql on Windows NT systems) of the dsmoninstall.sql file.
Log in to SQL*Plus as user DSSYS as follows:
```
sqlplus DSSYS/<DSSYS-password>
```
Run the dsmoninstall.sql script as follows:
```
SQL> @dsmoninstall.sql
```

A set of default services is installed from the etc/services directory on UNIX systems or etc\services directory on Windows NT systems, using the DSAdmin command-line utility with some scripts. These services are invoked by the event monitor utility that is described in Section 4.2.3. It is important to note that none of the monitor services throws events. This prevents an infinite loop from happening where the same monitor services are invoked for the event that they throw.

4.2.3 Using the Event Monitor Utility

In addition to the DSAdmin command-line utility, there is also an event monitor command-line tool called dsmon on UNIX systems (dsmon.bat on Windows NT systems). This tool lets you start and stop the event monitor, which executes monitor services upon receipt of events published by the Dynamic Services engine. Monitor services are services that are associated with a monitor and conform to a service interface called EventHandlerTemplate. These services are located in the etc/services directory on UNIX systems or etc\services directory on Windows NT systems. The correct syntax for running this utility is shown in Example 4-3.

Note:

On Windows NT, you must customize the SET ORACLE_HOME line in dsmon.bat to point to your <ORACLE_HOME>.

Example 4-3 Usage Syntax for Running the Event Monitor Utility

dsmon -u dssys/<dssys-password>@Direct -e start

Note:

Information presented in Example 4-3 is case-sensitive.

Using the event monitor utility, you can connect to a Dynamic Services engine; start or stop the monitor; and have control over the output level of the messages during the execution of the monitor services.

4.2.4 Enabling Persistent Auditing

The next step is to enable persistent auditing. With the default installation in dsinstall.sql, event messages are disabled in the properties table. Example 4-4 shows the setProperty PL/SQL procedure calls that enable event logging for the logging and warning event types.

Example 4-4 Connect to the DSSYS Schema as DSSYS User

connect dssys/<dssys-password>;
SQL> exec DS_Properties.setProperty('DS_EV_LOGGING_enabled', 'true');
SQL> commit;

Configure persistent auditing to enable event messages only for the event types you want.

4.2.5 Starting and Stopping the Event Monitor

Start the event monitor using the command shown in Example 4-5.

Example 4-5 Start the Event Monitor

dsmon -u dssys/<dssys-password>@Direct -e start

Note:

After starting the event monitor on Windows NT systems, the DOS prompt does not display again. You must use another DOS window to issue the stop command shown in Example 4-6.

Stop the event monitor using the command shown in Example 4-6.

Example 4-6 Stop the Event Monitor

dsmon -u dssys/<dssys-password>@Direct -e stop

When you issue this stop event monitor command, you post a stop request in the queue and the event monitor stops.

4.2.6 Using the Logger Monitor Service (Case Study)

One of the monitor services that is used is called the logger monitor service. It loads a logging event message into a raw log table in the database. The log table is an object table with the object definition as shown in Example 4-7.

Example 4-7 Define the Raw Log Object Table

CREATE OR REPLACE TYPE raw_logging_typ AS OBJECT
(
  base           raw_event_typ, -- Raw event type (base)
  operation      VARCHAR2(512), -- Oper: connect, lookup,  execute, session
  status         VARCHAR2(512), -- Status of the operation: open, fail, close 
  comm_msg       VARCHAR2(4000) -- Communication Message
);
/

The dependent object raw_event_typ has a definition as shown in Example 4-8.

Example 4-8 Definition of the Raw Event Object Table

CREATE OR REPLACE TYPE raw_event_typ AS OBJECT
(
  time_stamp     DATE,          -- Time stamp of the event
  service_id     VARCHAR2(512), -- Maximum length of a service ID string
  connection_id  VARCHAR2(256), -- Maximum DSConnection ID for a DSE user
  request_id     VARCHAR2(256), -- Maximum request ID for a DSE user
  consumer_id    VARCHAR2(256), -- Maximum length of a DB user
  engine_id      VARCHAR2(128)  -- Engine identifier (instance of DSE)
);
/

With an object table created based on the raw_logging_typ object, you can then make SQL queries to give a good view of the logging events that are thrown during service execution, as shown in Example 4-9.

Example 4-9 Make a SQL Query of the Logging Events

column timestamp format a14
column service   format a37
column consumer  format a8
column operation format a8
column status    format a6

select TO_CHAR(t.base.time_stamp, 'MM/DD@HH24:MI:SS') as timestamp, 
               t.base.consumer_id as consumer, 
               t.operation as operation, 
               t.base.service_id as service, 
               t.status as status
from raw_logging_table t
order by t.base.time_stamp asc;

-- The following is a sample of some logging event information that
-- might display from running the SQL query.

TIMESTAMP      CONSUMER OPERATIO SERVICE                               STATUS
-------------- -------- -------- ------------------------------------- ------
12/07@12:05:20 DSSYS    CONNECT                                        OPEN
12/07@12:05:33 DSSYS    LOOKUP                                         OPEN
12/07@12:05:33 DSSYS    LOOKUP                                         CLOSE
12/07@12:05:36 DSSYS    EXECUTE  urn:com.cnnfn:finance.portfolio03     OPEN
12/07@12:05:53 DSSYS    EXECUTE  urn:com.cnnfn:finance.portfolio03     CLOSE
12/07@12:06:23 DSSYS    CONNECT                                        CLOSE

6 rows selected.

There are certain service properties used by the logger monitor service that are set when the logger monitor service is installed. These service properties involve the database URL as well as the schema in the database that contains the raw log tables, and are therefore necessary for the logging monitor service to function properly. These service properties are described in the script files mentioned in Section 4.2.2.

4.3 Enabling HTTP Communications

This installation option coincides with the HTTP deployment view described in Section 1.3.3.

Dynamic Services can make use of the Apache servlet engine for handling remote HTTP communication between its service consumers and the Dynamic Services engine. To enable HTTP communications, first you must configure the Apache/Jserv servlet engine (see Section 4.3.1), and then configure the DSAdmin utility to use the Dynamic Services HTTP driver, DSHTTPDriver (see Section 4.3.2).

4.3.1 Configuring the Apache/Jserv Servlet Engine

The following instructions assume that you have Apache/JServ installed. Any Web server with a servlet container will work, provided that the changes are done correctly to the correct files. In this step, it is required that you configure your installation of Apache/Jserv to install a new Dynamic Services zone. The following is the list of tasks you must perform (refer to JServ documentation for more information on how to create new zones):

Edit the jserv.conf file.

This file is usually found within the Jserv/etc directory on UNIX systems or Jserv\etc directory on Windows NT systems under your Apache installation.

Note:
For an Oracle9i Release 1 (9.0.1) installation, the jserv.conf file is located in <ORACLE_HOME>/Apache/Jserv/etc directory on UNIX and ORACLE_HOME>\Apache\Jserv\etc on Windows NT.

Configure a new ds mount point by adding the new lines shown as follows:
```
# Oracle Dynamic Services Zone
ApJServMount /ds /ds
```

Edit the jserv.properties file.

This file is found in the same directory as the jserv.conf file. Make the following modifications:

Ensure Jserv is running on Java2.

Modify the wrapper.bin line to show<JAVA2_HOME> shown as follows. <JAVA2_HOME> is your Java 2 SDK installation directory.
```
wrapper.bin=<JAVA2_HOME>/bin/java
```
Create a new ds zone.

Append to the zones line, the ds zone as follows:
```
zones = <existing zones>, ds
```

Add a pointer to the ds zone properties as follows:

ds.properties=ORACLE_HOME/ds/etc/Apache_JServ/zones/ds/ds.properties

Update the Jserv classpaths.

Add all the necessary libraries needed by Dynamic Services as shown in the following list of necessary modifications.

# ----------------------------------------
# XML / XSD Parser from Oracle       
# ----------------------------------------
wrapper.classpath=ORACLE_HOME/lib/xmlparserv2.jar
wrapper.classpath=ORACLE_HOME/lib/xschema.jar
# ----------------------------------------------
# Oracle JDBC Driver (Compliant with JDK 1.2)
# ----------------------------------------------
wrapper.classpath=ORACLE_HOME/jdbc/lib/classes12.zip
# --------------
# JMS / AQ Stuff
# --------------
wrapper.classpath=ORACLE_HOME/rdbms/jlib/jmscommon.jar
wrapper.classpath=ORACLE_HOME/rdbms/jlib/aqapi.jar
# ----------------
# JNDI /LDAP Stuff
# ----------------
wrapper.classpath=ORACLE_HOME/jlib/providerutil.jar
wrapper.classpath=ORACLE_HOME/jlib/ldap.jar
wrapper.classpath=ORACLE_HOME/jlib/jndi.jar
# ----------------------------------------
# JSSE
# ----------------------------------------
wrapper.classpath=ORACLE_HOME/ds/lib/jsse.jar 
wrapper.classpath=ORACLE_HOME/ds/lib/jnet.jar 
wrapper.classpath=ORACLE_HOME/ds/lib/jcert.jar 
# ---------------
# XMLSQL and XSQL
# ---------------
wrapper.classpath=ORACLE_HOME/rdbms/jlib/xsu12.jar
wrapper.classpath=ORACLE_HOME/lib/oraclexsql.jar
# -------------------------------
# Oracle Dynamic Service Engine
# -------------------------------
wrapper.classpath=ORACLE_HOME/ds/lib/ds.jar

Set the environment variables.

Ensure that <ORACLE_HOME> and <LD_LIBRARY_PATH> environment variables are properly set on UNIX and that the <ORACLE_HOME> and <PATH> environment variables are properly set on Windows NT as follows:

On UNIX, set:
```
wrapper.env=ORACLE_HOME=<your_oracle_home>
wrapper.env=LD_LIBRARY_PATH=<your_oracle_home>/lib
```
On Windows NT, set:
```
wrapper.env=ORACLE_HOME=<your_oracle_home>
wrapper.env=PATH=<your_oracle_home>\bin
```

Edit the file <ORACLE_HOME>/ds/etc/Apache_JServ/zones/ds/ds.properties on UNIX systems or <ORACLE_HOME>\ds\etc\Apache_JServ\zones\ds\ds.properties on Windows NT systems and make the following modifications:
1. Update the repository location for the Dynamic Services zone.
  
  Change the location of the Dynamic Services jar file as follows:
```
repositories=ORACLE_HOME/ds/lib/ds.jar
```
2. Update Oracle Driver information for DSServlet.
  
  Change the driver to be used by the DSServlet as a servlet property by using the appropriate connection string for your database instance as follows:
```
servlets.default.initArgs=DS_ORCL_URL=jdbc:oracle:thin:@<your-host>:<your-port:<your-SID>
```
Restart Apache.

To restart Apache on UNIX, execute the following commands:
```
cd <Apache installation directory>
On UNIX systems:
bin/apachectl restart

On Windows NT systems:
bin\apachectl restart
```
On Windows NT, restart the Apache server from the Start bar. For Oracle9i Release 1 (9.0.1), start from your Oracle home, select Oracle HTTP Server, then Start HTTP Server powered by Apache.

4.3.2 Configuring the DSAdmin Utility to Use the HTTP Driver

After the Apache/JServ installation is completed, you can use the DSHTTPDriver with the DSAdmin utility after you perform the following tasks:

Navigate to the etc/dsadmin/DSAdminConfig.xml file on UNIX systems or etc\dsadmin\DSAdminConfig.xml file on Windows NT systems.

Enable the HTTP driver by following the comments for the DS_DRIVERS property. Update the URL used by the DSHTTPDriver by finding the DS_CONNECTION_DESCRIPTOR name = HTTP element and within this element, the element that begins with DS_URL. Change the value to point to the servlet that you just installed.

Note:

The URL used by the HTTP driver is an HTTP URL, while the URL used by the Direct driver is a JDBC URL. The rationale is that when the HTTP driver is used, requests are sent using HTTP to the previously described installed Java servlet. This Java servlet directly interacts with a Dynamic Services engine in the same way that the Direct driver does. This means that the two drivers may not necessarily share the same engine.

4.4 Enabling Java Messaging Services (JMS) Communications

This installation option coincides with the JMS deployment view described in Section 1.3.3.

A SQL script named dsjms_aqinit.sql is provided to install the JMS option.

Go to the directory location (ds/sql) on UNIX systems or (ds\sql) on Windows NT systems of the dsjms_aqinit.sql file.
Log in to SQL*Plus as user DSSYS as follows:
```
sqlplus DSSYS/<DSSYS-password>
```
Run the dsjms_aqinit.sql script as follows:
```
SQL> @dsjms_aqinit.sql
```
Running the dsjms_aqinit.sql script in a SQL*Plus session as the DSSYS user, creates all the tables and queues necessary for JMS communications.

4.4.1 Configuring and Running the JMS Daemon

To configure and run the JMS daemon, perform the following tasks:

Edit the etc/dsadmin/DSAdminConfig.xml configuration file on UNIX systems or the etc\dsadmin\DSAdminConfig.xml configuration file on Windows NT systems that is used to run the daemon. The following code example shows the specific parameters that you must configure in this configuration file.

.
.
.
<DS_CONNECTION_DESCRIPTOR name="JMSDAEMON">
   <annotation>
     -| For Nickname "JMSDAEMON":  
      | These are specifications of the JMS driver class 
     +| that will be used as well as the URL to be used with it 
   </annotation>
   <DS_DRIVER>oracle.ds.driver.DSDirectDriver</DS_DRIVER>
   <DS_URL>jdbc:oracle:thin:@your-host:your-port:your-sid</DS_URL>
   <JMSD_LOG_FILE>logs/jmsd.log</JMSD_LOG_FILE>
   <JMSD_NUM_THREADS>10</JMSD_NUM_THREADS>
</DS_CONNECTION_DESCRIPTOR>
.
.
.

Note:

There is only a single URL for the database. This is the database that is used to host the request/response queues, as well as the database for the Dynamic Services engine. It must be the same database where the DSSYS schema was installed.

Run the following program to start the daemon that listens to all asynchronous requests.

On UNIX systems:
bin/dsjmsd -u dssys/dssys@JMSDAEMON -c etc/dsadmin/DSAdminConfig.xml -e start

On Windows NT systems: bin\dsjmsd -u dssys/dssys@JMSDAEMON -c etc\dsadmin\DSAdminConfig.xml -e start

Note:

Before running the dsjmsd.bat file on Windows NT, check and change the SET ORACLE_HOME line to point to your Oracle home.

Also, in your DSAdminConfig.xml file, uncomment the DS_CONNECTION_DESCRIPTOR element for the JMSDAEMON nickname.

For future reference, the following code example shows how to stop the JMS daemon.

On UNIX systems:
bin/dsjmsd -u dssys/dssys@JMSDAEMON -c etc/dsadmin/DSAdminConfig.xml -e stop

On Windows NT systems:
bin\dsjmsd -u dssys/dssys@JMSDAEMON -c etc\dsadmin\DSAdminConfig.xml -e stop

4.4.2 Configuring the DSAdmin Utility to Enable JMS Communications

Before configuring the DSAdmin utility to enable JMS communications, you must note that for all service consumer applications that want to use the JMS communication path, the database users that represent them must be granted the AQ_Administrator_Role privilege. The client library needs to register itself as an asynchronous subscriber to the response queue for asynchronous executions. Note that DSSYS is already granted that role. To configure the DSAdmin utility to enable JMS communications, perform the following tasks:

Navigate to the etc/dsadmin/DSAdminConfig.xml configuration file on UNIX systems or the etc\dsadmin\DSAdminConfig.xml configuration file on Windows NT systems.
Edit the etc/dsadmin/DSAdminConfig.xml file on UNIX systems or the etc\dsadmin\DSAdminConfig.xml file on Windows systems and update the URL used by the DSJMSDriver by finding the DS_CONNECTION_DESCRIPTOR name = JMS element, and within this element, the element that begins with DS_URL. Change the value to point to the URL of the database that is hosting the queues. Also, uncomment this JMS nickname DS_CONNECTION_ DESCRIPTOR element.

During runtime, requests are sent to the request queue in this database. The requests are picked up by the daemon that is communicating with this same database, and used in a service execution that returns a response. That response is submitted to a response queue in the same database, to be picked up asynchronously by the initial request submitter.

4.5 Using Lightweight Directory Access Protocol (LDAP) as a Central Master Registry

As installed in the dsinstall.sql script, the instance of the Dynamic Services engine is a standalone instance with its own storage for the registry. To increase scalability, you may want to install multiple Dynamic Services engines communicating with a central master Lightweight Directory Access Protocol (LDAP) registry (see Figure 1-8). First, you must successfully install the Oracle Internet Directory (OID) LDAP server with all the appropriate schemas.

4.5.1 Setting Up LDAP with Oracle Internet Directory

To set up LDAP with OID, you must install OID (see Section 4.5.1.1), and then install the Dynamic Services LDAP schema (see Section 4.5.1.2).

4.5.1.1 Oracle Internet Directory

To install Oracle Internet Directory, run the Oracle Installer of your Oracle9i Release 1 (9.0.1) distribution and choose the Oracle9i Management and Integration option. Then, select Oracle Internet Directory from the list of displayed products. For more information, refer to Oracle installation instructions.

4.5.1.2 Dynamic Services LDAP Schema

Before proceeding in the installation, verify the following:

Ensure the oidmon instance is running. If not, run the following command to start it.
```
oidmon connect=OIDDB1 sleep=10 start
```
OIDDB1 is the system identifier (SID) of the database instance created by the OID installer.
Ensure the oidldapd server is running. If not, run the following command to start an instance of the OID LDAP server.
```
oidctl connect=OIDDB1 server=oidldapd instance=1 start
```

Then, proceed with the installation of the Dynamic Services LDAP schema and issue the following command from a command-line shell:

On UNIX systems:
ldapmodify -h oracledev1-sun.us.oracle.com -p 389 -D "cn=orcladmin" -w "welcome"  
-v -c -f $<ORACLE_HOME>/ds/ldif/oiddsschema.ldif

On Windows systems:
ldapmodify -h oracledev1-sun.us.oracle.com -p 389 -D "cn=orcladmin" -w "welcome"  
-v -c -f $<ORACLE_HOME>\ds\ldif\oiddsschema.ldif

Table 4-1 describes the ldapmodify command-line options that can be used for installing the Dynamic Services LDAP schema.

Table 4-1 ldapmodify Command-Line Options for Installing Dynamic Services LDAP Schema

Options	Description
h	Specifies the host machine where OID is running.
p	Specifies the port number to which OID is listening. By default, the port number is 389.
D	Specifies the user name (in Distinguished Name (DN) format defined by LDAP). By default, the admin for OID is "cn=orcladmin".
w	Specifies the password for the user claimed in option "-D". By default, the password for admin is "welcome".
v	Specifies verbose mode.
c	Specifies that all warning or error messages during the installation are delayed from being viewed until the end.
f	Specifies the location of the schema file to be uploaded to OID. In this example, <ORACLE_HOME> refers to your Oracle9i installation.

The oiddsschema.ldif file includes all the necessary steps for the installation of the Dynamic Services schema into OID. These steps are:

Create unique attributes used by Oracle Dynamic Services.
Create an index on those attributes.
Create the object classes.

After successfully installing the Dynamic Services LDAP schema, the next step is to create default entries for Dynamic Services, such as the release number of the product and the root of the User Profile Subtree. Issue the command shown in Example 4-10 to do this.

Example 4-10 Run the ldapmodify Command to Create Default Entries for Dynamic Services

On UNIX systems:
ldapmodify -h oracledev1-sun.us.oracle.com -p 389 -D "cn=orcladmin" -w "welcome"  
-v -c -f <ORACLE_HOME>/ds/ldif/oiddsdit.ldif

On Windows NT systems:
ldapmodify -h oracledev1-sun.us.oracle.com -p 389 -D "cn=orcladmin" -w "welcome"  
-v -c -f <ORACLE_HOME>\ds\ldif\oiddsdit.ldif

Note:

In this release, the oiddsdit.ldif file assumes the DN of OracleContext to be "cn=OracleContext, C=US". Change the DN to one of your choice, if needed.

4.5.2 Configuring Dynamic Services Registry to Use LDAP

In order to change this instance of the Dynamic Services engine into one that communicates with the master LDAP server, you must change some properties in the properties table. This is done by executing the two setProperty PL/SQL procedure calls shown in Example 4-11.

Example 4-11 Configure the Dynamic Services Registry to Use the Master LDAP Server

exec DS_Properties.setProperty('oracle.ds.registry.defaultRegistry',
                               'oracle.ds.registry.DSMasterMirrorRegistry');
exec DS_Properties.setProperty('oracle.ds.registry.ldap.providerUrl',
                               'ldap://your.ldap.server:389');

The first call instructs the instance to go to a master LDAP server for the central master registry rather than to itself (the default value that was set during installation is 'oracle.ds.registry.DSSimpleRegistry'). The second call points your instance to the correct LDAP server for its registry communications.

You must change your.ldap.server to the host name of the machine that is running Oracle Internet Directory.

After you complete the preceding step, perform the following tasks:

Run the DSAdmin utility again and go to the DSAdminShell.Registry.Engine subshell to register your engine with the central master registry; however, this step is optional and needed only for management purposes.
Browse the DSAdminShell.Registry.Engine subshell to see the directives available to manage the list of engines that communicate with the central master registry.

4.6 Manual Fine-Tuning of Dynamic Services Properties

Table 4-2 describes the Dynamic Services properties that you can change after installing Dynamic Services.

Table 4-2 Dynamic Services Properties

Property	Description
proxySet	Controls usage of proxy server for HTTP access; (true \| false)
proxyHost	Proxy server host name
proxyPort	Proxy server port number
oracle.ds.registry.ldap.providerUrl	URL of the LDAP server to be used as central master registry
oracle.ds.registry.ldap.principal	User name to be used to connect to LDAP server
oracle.ds.registry.ldap.credential	Password to be used to connect to LDAP server
oracle.ds.registry.ldap.rootdn	DN of the root of the Dynamic Services tree in LDAP(cn=OracleDynamicService, cn=Products, <DN of OracleContext>)
cacheSet	Enables or disables service response caching; (true \| false)
debugLevel	Controls debug output level; (TERSE \| VERBOSE \| TRACE)

Note:

Both property name and property values are case-sensitive.

The properties are stored in the installed DSSYS schema. To set a property:

Connect to the Oracle database as DSSYS using SQL*Plus as follows:
```
sqlplus DSSYS/<DSSYS-password>
```

Run the setProperty PL/SQL procedure by issuing the following SQL statement:

SQL> EXECUTE DS_PROPERTIES.setProperty('<property name>', '<property 
value>');

Display a list of current properties by issuing the following SQL statements:
```
SQL> SET SERVEROUTPUT ON;
SQL> EXECUTE DS_Properties.show;
```

4 Advanced Installation Options

4.1 Enabling PL/SQL Interfaces

4.2 Enabling Persistent Auditing or Event Monitor Services

4.2.1 Configuring Oracle Advanced Queuing

Example 4-1 Set the aq_tm_process init.ora Parameter

4.2.2 Installing Monitor Services

Example 4-2 Configure the MonitorInstall.dss File

4.2.3 Using the Event Monitor Utility

Example 4-3 Usage Syntax for Running the Event Monitor Utility

4.2.4 Enabling Persistent Auditing

Example 4-4 Connect to the DSSYS Schema as DSSYS User

4.2.5 Starting and Stopping the Event Monitor

Example 4-5 Start the Event Monitor

Example 4-6 Stop the Event Monitor

4.2.6 Using the Logger Monitor Service (Case Study)

Example 4-7 Define the Raw Log Object Table

Example 4-8 Definition of the Raw Event Object Table

Example 4-9 Make a SQL Query of the Logging Events

4.3 Enabling HTTP Communications

4.3.1 Configuring the Apache/Jserv Servlet Engine

4.3.2 Configuring the DSAdmin Utility to Use the HTTP Driver

4.4 Enabling Java Messaging Services (JMS) Communications

4.4.1 Configuring and Running the JMS Daemon

4.4.2 Configuring the DSAdmin Utility to Enable JMS Communications

4.5 Using Lightweight Directory Access Protocol (LDAP) as a Central Master Registry

4.5.1 Setting Up LDAP with Oracle Internet Directory

4.5.1.1 Oracle Internet Directory

4.5.1.2 Dynamic Services LDAP Schema

Table 4-1 ldapmodify Command-Line Options for Installing Dynamic Services LDAP Schema

Example 4-10 Run the ldapmodify Command to Create Default Entries for Dynamic Services

4.5.2 Configuring Dynamic Services Registry to Use LDAP

Example 4-11 Configure the Dynamic Services Registry to Use the Master LDAP Server

4.6 Manual Fine-Tuning of Dynamic Services Properties

Table 4-2 Dynamic Services Properties

4
Advanced Installation Options