Java TM 2 SDK, Enterprise Edition Configuration Guide Version 1.2.1

Contents

• Introduction
  
  
• JDBC ^TM Drivers
  
  
• Transactions
  
  
• Port Numbers
  
  
• Log Files
  
  
• Security
  
  
• Memory Threshold for Passivation
  
  
• HTTP Document Root

Introduction

In most cases, you won't have to make any changes to the properties files. However, if you wish to use a database driver other than Cloudscape, you'll need to follow the instructions in the next section.

JDBC ^TM Drivers

If your enterprise beans use the JDBC API to access a database other than Cloudscape, then you must configure the JDBC drivers according to the instructions in the sections that follow. (If you aren't sure if this release supports your JDBC driver, see the Supported Databases and JDBC Drivers section of the Release Notes.)

Driver Location

The J2EE_CLASSPATH Environment Variable

Note: You should remove the driver .jar files from the CLASSPATH environment variable.

About XA Datasource Support

If your driver does not support XA datasources, you must follow the instructions in the section, Drivers Without XA Datasource Support.

If your driver supports XA datasources, to take advantage of XA's features you must follow the instructions in the section, Drivers with XA Datasource Support.

If your driver supports XA datasources and you follow the instructions in the section, Drivers Without XA Datasource Support, the driver will work but cannot take advantage of XA's features.

Drivers Without XA Datasource Support

The jdbc.drivers Property

         
jdbc.drivers=<classname>:<classname>: . . .
      

         
jdbc.drivers=oracle.jdbc.driver.OracleDriver:testutil.MyDriver
      

The jdbc.datasources Property

The syntax of jdbc.datasources follows:

         
jdbc.datasources=<jndi_datasource>|<url>|<jndi_datasource>|<url>. . .
      

The pipe character (|) serves two purposes. First, it separates the <jndi_datasource> and <url> elements that form a pair. Second, it delimits each pair of <jndi_datasource> and <url> elements.

The <jndi_datasource> element has the following syntax:

         
jdbc/<jndi_name>
      

Here is an example:

         
jdbc.datasources=jdbc/Oracle|jdbc:oracle:thin@rtc:1521:acct|jdbc/MyDB|jdbc:test
      

Drivers with XA Datasource Support

         
jdbc20.datasources
         
xadatasource.<n>.jndiname
         
xadatasource.<n>.classname
         
xadatasource.<n>.dbuser
         
xadatasource.<n>.dbpassword
         
xadatasource.<n>.prop.<property-name>
      

The jdbc20.datasources Property

The syntax of jdbc20.datasources follows:

         
jdbc20.datasources=<jndi_datasource>|<jndi_XA_datasource>|<jndi_datasource>|<jndi_XA_datasource>. . .
      

.

The pipe character (|) serves two purposes. First, it separates the <jndi_datasource> and <jndi_XA_datasource> elements that form a pair. Second, it delimits each pair of <jndi_datasource> and <jndi_XA_datasource> elements.

The <jndi_datasource> and <jndi_XA_datasource> elements have the same syntax:

         
jdbc/<jndi_name>
      

Here is an example:

         
jdbc20.datasources=jdbc/Merant|jdbc/XAMerant|jdbc/Finch|jdbc/XAFinch
      

The xadatasource Properties

         
xadatasource.<n>.jndiname=jdbc/<jndi_XA_datasource>
      

The xadatasource.<n>.classname property specifies the class name of the XA DataSource.

The xadatasource.<n>.dbuser and xadatasource.<n>.dbpassword properties specify the database user and password used to sign on to the database to perform recovery. Usually, this database user will have the database administrator privilege. (For more information on recoveries, see the section, The distributed.transaction.recovery Property.)

The xadatasource.<n>.prop.<property_name> specifies the value associated with a particular property name. The actual property names may vary with the JDBC driver.

An example follows:

         
xadatasource.0.jndiname=jdbc/XAMerant
         
xadatasource.0.classname=com.merant.sequelink.jdbcx.datasource.SequeLinkDataSource
         
xadatasource.0.prop.url=jdbc:sequelink://mypc:5000/[Oracle]
      

Transactions

The distributed.transaction.recovery Property

The value of this property may be either true or false. When J2EE is first installed, the value is false:

         
distributed.transaction.recovery=false
      

The transaction.timeout Property

         
transaction.timeout=5
      

When J2EE is first installed, the timeout value is set to 0:

         
transaction.timeout=0
      

Only enterprise beans with container-managed transactions are affected by the transaction.timeout property. For enterprise beans with bean-managed, JTA transactions, you invoke the setTransactionTimeout method of the UserTransaction interface. You also invoke the setTransactionTimeout method for other components, such as servlets and JSP pages, that demarcate transaction with the UserTransaction interface.

Port Numbers

Log Files

         
log.directory=logs
      

The log files generated depend on whether you launch j2ee in the single or multiple VM (virtual machine) mode.

Single VM Log Files

         
$J2EE_HOME/<logs>/<host>/ejb
      

The following log files are generated:

         
system.out
         
system.err
         
event.log
         
output.log
         
error.log
         
audit.log
      

Multiple VM Log Files

Web Service Log Files

         
access.log=access.log
         
error.log=error.log
      

Security

Unauthenticated User Name

         
default.principal.name=guest
         
default.principal.password=guest123
      

Keystore Password

The .keystore file is typically protected by a password. By default, this password is changeit. You can modify the password by editing the keystore.password entry in the web.properties file.

ANYONE Role

Memory Threshold for Passivation

         
passivation.threshold.memory=128000000
      

HTTP Document Root

         
documentroot=public_html/
      

Copyright © 2000 Sun Microsystems, Inc. All rights reserved.