Previous Naming Service Configuration Next

NameSingleton Configuration

CORBA Properties

IOR Name Service Entry

The Naming Service entry for the Singleton.

Property Name

Object.Name

Property Type

FIXED

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

NO

IOR URL

The IOR URL property specifies the location of an Interoperable Object Reference (IOR) for the Service, using the Universal Resource Locator (URL) format. This information is used when a client attempts to resolve a reference to the Service. Currently only http and file URLs are supported, for example:

file:/usr/users/openfusion/servers/NameService.ior
http://www.prismtech.com/openfusion/servers/NameService.ior

Property Name

IOR.URL

Property Type

FIXED

Data Type

URL

Accessibility

READ/WRITE

Mandatory

NO

IOR File Name

The IOR File Name option specifies the name and location of the IOR file for the Singleton. If this property is not set, the IOR file name will be:

<INSTALL>/domains/<domain>/<node>/<service>/<singleton>/<singleton>.ior

where <INSTALL> is the OpenFusion installation path. See The Object Hierarchy for details of the domains directory structure.

Property Name

IOR.File

Property Type

FIXED

Data Type

FILE

Accessibility

READ/WRITE

Mandatory

NO

Resolve Name

The ORB Service resolution name used to resolve calls to the Singleton

Property Name

ResolveName

Property Type

FIXED

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

YES

IOR Name Service

The name of the Naming Service which will be used to resolve the Singleton object.

Property Name

IOR.Server

Property Type

FIXED

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

NO

Lightweight Directory Access Protocol (LDAP)

The Naming Service uses Sun Microsystems' JNDI (Java Naming and Directory Interface) LDAP provider. This allows the Naming Service to be stored in a standard LDAP server. Caching is not supported under the LDAP persistence option.

LDAP User

The administrator of the LDAP server may want each user to have their own login name and password. This property specifies the user name. The user name should be in the fully qualified LDAP format, for example:

uid=RNCross,ou=People,o=prismtechnologies.com

Property Name

DB.LDAP.User

Property Type

STATIC

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

YES

LDAP Password

The administrator of the LDAP server may want each user to have their own login name and password. This property specifies the password.

Property Name

DB.LDAP.Password

Property Type

STATIC

Data Type

PASSWORD

Accessibility

READ/WRITE

Mandatory

YES

LDAP URL

The URL specifies the location within the LDAP server where the Naming Service should store its persistent data. The data will not appear in the traditional hierarchical format due to limitations of the LDAP storage mechanism.

An example URL is:

ldap://excalibur.prismtechnologies.com:2809/ou=OpenFusion Naming Service,o=prismtechnologies.com

Property Name

DB.LDAP.URL

Property Type

STATIC

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

YES

LDAP Trace

Output hexadecimal dump of the incoming and outgoing LDAP ASN.1 BER packets from the LDAP server.

Property Name

DB.LDAP.Trace

Property Type

FIXED

Data Type

BOOLEAN

Accessibility

READ/WRITE

Mandatory

YES

LDAP Security

LDAP Authentication Mechanism. The security method may be:

The administrator must enable all privileges upon the target location in the LDAP hierarchy when anonymous bind is selected. The LDAP v3 protocol uses the SASL to support pluggable authentication. This means that the LDAP client and server can be configured to negotiate and use possibly non-standard and/or customized mechanisms for authentication, depending on the level of protection desired by the client and the server. The LDAP v2 protocol does not support the SASL.

Property Name

DB.LDAP.Security

Property Type

STATIC

Data Type

ENUM

Accessibility

READ/WRITE

Mandatory

YES

LDAP SASL Mechanism Names

A list of mechanisms should be entered in the configuration tool when the SASL option is chosen, for example:

DIGEST-MD5 CRAM-MD5

This specifies that DIGEST-MD5 authentication is to be used, or that CRAM-MD5 authentication is to be used when the SASL mechanism is unavailable. An AuthenticationNotSupportedException will be thrown when neither is available.

Property Name

DB.LDAP.SASL

Property Type

STATIC

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

YES

Persistence Options

The Naming Service provides two extra persistence options and a read cache for the caching of naming contexts.

The different kinds of caching available to the Naming Service are:

Read Cache Flush Interval

The interval, in seconds, between read cache flush operations. A least-recently-used algorithm is employed to reduce the size of the cache to the level of the Read Cache Minimum Size.

The default value is 0 (zero), which indicates no timed cache flush will be performed.

Property Name

DB.ReadCache.Int

Property Type

DYNAMIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

Read Cache Maximum Size

The maximum number of objects that the read cache will be allowed to hold. A value of zero means that there is no read cache. When the cache reaches the read limit size, a least-recently-used algorithm is employed to reduce the size of the cache to the level of the Read Cache Minimum Size.

The default value is 500.

The Read Cache Maximum Size must be set greater than zero if a write cache is required, as it is not possible to have a write cache without a read cache.

Property Name

DB.ReadCache.Max

Property Type

DYNAMIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

Read Cache Minimum Size

The minumum number of objects which will be left in the cache when it is cleared. The default value is 0 (zero).

Property Name

DB.ReadCache.Min

Property Type

DYNAMIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

Write Cache Write Interval

The write interval option refers to the delay (in seconds) between saving object state changes within a server, and writing this information to persistent store. This option is a performance optimization feature as it can be used to prevent the service making a lot of small updates to the persistent store.

A value of zero indicates no delay. Changes are written immediately to the persistent store if both the Write Cache Write Interval and Write Cache Batch Size are set to zero.

The default value for this property is zero. Increasing the write interval value may improve performance when the data held by a service is changing rapidly.

Property Name

DB.WriteInterval

Property Type

DYNAMIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

Write Cache Batch Size

The Write Batch Size option specifies the maximum number of updates that will be buffered before the data is written to persistent storage. Just as for the write interval option, the write batch size option is also a performance optimization feature.

A value of zero indicates that the updates are not buffered but are written immediately to the datastore. Increasing this property value may improve performance when the data held by a service is changing rapidly.

The Read Cache Maximum Size must be set greater than zero if a write cache is required, as it is not possible to have a write cache without a read cache.

The effect of setting both the Write Interval and Write Batch Size to values greater than zero is that of batched timed writes.

Property Name

DB.WriteBatch

Property Type

DYNAMIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

Naming Data Storage Type

This property sets the persistent storage type. The type can be:

If Default is selected, the data store will default to the location of the service data (using JDBC). See Storage Type for details.

Property Name

DB.NameDataPersistence

Property Type

STATIC

Data Type

ENUM

Accessibility

READ/WRITE

Mandatory

YES

Instrumentation Properties

The interfaces for setting the instrumentation properties are given below. For information on managing instrumentation, see Instrumentation.

Count of resolve operations

The number of resolve operations since the Service started or was last reset.

Property Name

ResolveCount

Property Type

DYNAMIC

Data Type

COUNTER

Accessibility

READ/WRITE

Mandatory

NO

Count of rebind context in service

The number of rebind contexts in service since the Service started or was last reset.

Property Name

ReBindContextCount

Property Type

DYNAMIC

Data Type

COUNTER

Accessibility

READ/WRITE

Mandatory

NO

Count of context bind operations

The number of context binds in service since the Service started or was last reset.

Property Name

BindContextCount

Property Type

DYNAMIC

Data Type

COUNTER

Accessibility

READ/WRITE

Mandatory

NO

Count of unbind operations

The number of unbinds in service since the Service started or was last reset.

Property Name

UnBindCount

Property Type

DYNAMIC

Data Type

COUNTER

Accessibility

READ/WRITE

Mandatory

NO

Count of rebind operations

The number of rebinds in service since the Service started or was last reset.

Property Name

ReBindCount

Property Type

DYNAMIC

Data Type

COUNTER

Accessibility

READ/WRITE

Mandatory

NO

Count of bind operations

The number of binds in service since the Service started or was last reset.

Property Name

BindCount

Property Type

DYNAMIC

Data Type

COUNTER

Accessibility

READ/WRITE

Mandatory

NO

General Properties

JNDI ContextFactory Cache Flush Interval

The internal ContextFactory cache can be purged to prevent the possibility of memory leaks. This property specifies the interval, in seconds, between ContextFactory cache flush operations. A value of zero indicates that no timed cache flush will take place.

JNDI ContextFactory Cache Flush Interval is used in conjunction with the JNDI ContextFactory Cache Maximum Size and JNDI ContextFactory Cache Minimum Size properties to determine the purging behaviour.

Property Name

jndiCtxCacheInt

Property Type

STATIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

JNDI ContextFactory Cache Maximum Size

The maximum number of contexts allowed in the ContextFactory cache. When the cache exceeds this size, contexts are purged according to a least-recently-used algorithm

Property Name

jndiCtxCacheMax

Property Type

STATIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

JNDI ContextFactory Cache Minimum Size

The size that the ContextFactory cache will be reduced to following a cache flush. For example, if this property is set to 10 then all but 10 contexts will be purged during a flush operation.

Property Name

jndiCtxCacheMin

Property Type

STATIC

Data Type

INTEGER

Accessibility

READ/WRITE

Mandatory

YES

JNDI Properties File

The location of the jndi.properties file. If this is left blank, the jndi.properties file will not be created.

The jndi.properties file is useful for JNDI client applications that need to connect to the Naming Service hierarchy.

The OpenFusion JMS Manager requires a valid jndi.properties file. See JMS Manager for details.


When more than one Naming Service is used, each one must be configured to use a different jndi.properties file.

Property Name

jndiPropertiesFile

Property Type

STATIC

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

NO

JNDI OF Properties File

The location that the of.jndi.properties file will be written to. If this is left blank, the file will not be created.

The of.jndi.properties file can be used by JBoss (and other application servers) to access the OpenFusion JNDI properties. As an alternative to using this file, properties could be hard coded or passed to an application as command-line parameters.

Property Name

jndiOFPropertiesFile

Property Type

STATIC

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

NO

JNDI Root ID

This option allows the root ID used by the JNDI hierarchy to be manually configured. This is useful when used in conjunction with the Server Persistent ID (SID) property (see Server Persistent ID) as these are then known values that may be passed to JNDI client programs. These clients can then access the Naming Service persistent data.

See the OpenFusion Naming Service Guide for more details of using JNDI

Property Name

JNDIID

Property Type

STATIC

Data Type

UUID

Accessibility

READ/WRITE

Mandatory

NO

Enable Load Balancing

This allows load balancing to be performed by the Naming Service.

Property Name

LoadBalancing

Property Type

DYNAMIC

Data Type

BOOLEAN

Accessibility

READ/WRITE

Mandatory

YES

View Non-Corba Objects

This allows the Naming Service to browse a JNDI hierarchy even when non-CORBA objects (e.g. java.lang.String) have been stored. The Naming Service will log and ignore any non-CORBA objects it encounters when this option is disabled.

Property Name

ViewNonCorba

Property Type

DYNAMIC

Data Type

BOOLEAN

Accessibility

READ/WRITE

Mandatory

YES

Purge on List

Invalid object references (that is, those object references which are not active and not persistent) are removed from a naming context when the list operation is performed on the context and Purge on List is selected.

Object purging is discussed in detail in the OpenFusion Naming Service Guide.

Property Name

Clean.List

Property Type

DYNAMIC

Data Type

BOOLEAN

Accessibility

READ/WRITE

Mandatory

YES

Purge on Load

Invalid object references (that is, those object references which are not active and not persistent) are removed when contexts are first accessed after a server has been restarted and Purge on Load is selected.

Object purging is discussed in detail in the OpenFusion Naming Service Guide.

Property Name

Clean.Load

Property Type

DYNAMIC

Data Type

BOOLEAN

Accessibility

READ/WRITE

Mandatory

YES

Purge Class Plugin

This should be a publicly instantiable Java class that implements the com.prismt.openfusion.plugin.Purgable interface. This interface has one operation:

public boolean isPurgable (org.omg.CORBA.Object obj)

This class is used to determine whether or not to purge objects from the Naming Service. Typically, a client will code this operation to determine whether their object is persistent or transient and hence may be purged. This service will also check the active/inactive state. The ObjectAdapter.isTransient method is the default used when a class is not specified. This will successfully determine the persistent state for objects created using the OpenFusion framework, but it will not work for foreign objects.

Purging is the deletion of invalid object references and purgable objects from a service. Object references are regarded as invalid when they are not active and not persistent. The OpenFusion Naming Service can most easily determine whether an object is purgable if the com.prismt.openfusion.plugin.Purgable interface is implemented. See the OpenFusion Naming Service Guide for further details.

Property Name

Clean.PurgeClass

Property Type

DYNAMIC

Data Type

STRING

Accessibility

READ/WRITE

Mandatory

NO

System Master

This property should be set to true (checked) if this is the master naming service for a system. There can be only one master naming service.

Property Name

Resolver

Property Type

STATIC

Data Type

BOOLEAN

Accessibility

READ/WRITE

Mandatory

YES



Previous Naming Service Configuration Next