VisiBroker properties

This section describes the VisiBroker properties.

Smart Agent properties

The following table describes the properties for Smart Agent:

Property	Default	Old property	Description
vbroker.agent.addrFile	null	ORBagent AddrFile	Specifies a file that stores the IP address or host name of a host running a Smart Agent.
vbroker.agent.localFile	null	N/A	Specifies which network interface to use on multi-home machines. This used to be the OSAGENT_LOCAL_FILE environment variable.
vbroker.agent. clientHandlerPort	null	N/A	Specifies the port that the Smart Agent uses to verify the existence of a client — in this case, a VisiBroker application. When you use the default value, null, the Smart Agent connects using a random port number.
vbroker.agent. keepAliveTimer	120 seconds	N/A	Smart agent will wake up after this timeout and based on the vbroker.agent.keepAliveThreshold value, will compute whether to do client verification. The logic is if the last received heart beat value is less than current time - (keepAliveTimer + keepAliveThreshold), then do client verification. The value of this property should be greater than 1 second and less than 120 seconds. The number of times the client verification is tried can be controlled by vbroker.agent.maxRetries property.
vbroker.agent. keepAlivethreshold	40 seconds	N/A	See vbroker.agent.keepAliveTimer. This value should be greater than 0.
vbroker.agent. verifyMaxClients	50	N/A	Specifies the maximum number of clients that the Smart Agent will try to verify on each occasion that it is woken up by keepAliveTimer. For example,   osagent -Dvbroker.agent.verifyMaxClients 23 The default is the same value that was hard-coded in previous versions.
vbroker.agent.maxRetries	4 times	N/A	The number of times the agent will do client verification on not receiving a heart beat from the client. Values can be 1 to 10.
vbroker.agent.port	14000	ORBagentPort	Specifies the port number that defines a domain within your network. VisiBroker applications and the Smart Agent work together when they have the same port number. This is the same property as the OSAGENT_PORT environment variable.
vbroker.agent.timer	300 seconds	N/A	Smart agent will wake up after this timeout and based on the vbroker.agent.threshold value, will compute whether to do other osagents verification. The logic is if the last received heart beat value is less than current time - (timer + threshold), then do osagents verification. The value of this property should be greater than 1 second and less than 300 seconds. For example, $ osagent -Dvbroker.agent.timer 60    -Dvbroker.agent.threshold 5
vbroker.agent.threshold	40 seconds	N/A	See vbroker.agent.timer. This value should be greater than 0.

Smart Agent communication properties

The properties described in the table below are used by the ORB for Smart Agent communication.

Property	Default	Old property	Description
vbroker.agent. keepAliveTimer	120	N/A	The duration in seconds during which the ORB will send keep-alive messages to the Smart Agent (applicable to both clients and servers). Valid values are integers between 1 and 120, inclusive.
vbroker.agent.retryDelay	0 (zero)	N/A	The duration in seconds that the process will pause before trying to reconnect to the Smart Agent in the event of disconnection from the Smart Agent. If the value is -1, the process will exit upon disconnection from the Smart Agent. The default value of 0 (zero) means that reconnection will be made without any pause.
vbroker.agent.addr	null	ORBagent Addr	Specifies the IP address or host name of a host running a Smart Agent. The default value, null, instructs VisiBroker applications to use the value from the OSAGENT_ADDR environment variable. If this OSAGENT_ADDR variable is not set, then it is assumed that the Smart Agent is running on a local host.
vbroker.agent.addrFile	null	ORBagent AddrFile	Specifies a file that stores the IP address or host name of a host running a Smart Agent.
vbroker.agent.debug	false	ORBdebug	When set to true, specifies that the system will display debugging information about communication of VisiBroker applications with the Smart Agent.
vbroker.agent. enableLocator	true	ORB disable Locator	When set to false, does not allow VisiBroker applications to communicate with the Smart Agent.
vbroker.agent.port	14000	ORBagent Port	Specifies the port number that defines a domain within your network. VisiBroker applications and the Smart Agent work together when they have the same port number. This is the same property as the OSAGENT_PORT environment variable.
vbroker.agent.failOver	true	ORBagent NoFail Over	When set to true, allows a VisiBroker application to fail over to another Smart Agent.
vbroker.agent.clientPort	0 (system-defined port)	N/A	Lower bound of the range of ports for the ORB to communicate with the OSAgent. Valid values are between 0 to 65535. The default 0 (zero) means a system-defined port; on most systems this will be the next available port after the last one used.
vbroker.agent. clientPortRange	0 (zero)	N/A	Range of ports within interval [clientPort, clientPort+clientPortRange] for the ORB to communicate with the OSAgent. This property is effective only when clientPort is greater than 0 (zero). Valid values are between 0 and 65535.
vbroker.orb.loadDSUser	false	N/A	By default, VisiBroker will load Osagent(DSUser ) library when property vbroker.agent.enableLocator=true or vbroker.orb.loadDSUser=true. If this is set to true but the application needs to use OAD with osagent disabled, set vbroker.orb.loadDSUser=true and vbroker.agent.enableLocator=false.

VisiBroker ORB properties

This table lists the VisiBroker ORB properties.

Property	Default	Description
vbroker.orb. defaultThreadStackSize	0 (zero)	This property indicates the default size to be used by any thread created by the ORB. A default value of zero indicates a system default value. If the value is set and falls below the minimum system requirement, then the minimum system requirement value is used. Dispatchers may have their own threadStackSize property set and as such their values are used instead during thread creation.
vbroker.orb.enableFirewall	false	When set to true, the application dynamically loads the fw library to make the Gatekeeper firewall component available. By default, the property is false. When false, the fw library is not loaded, so the gatekeeper firewall component is not available.
vbroker.orb.cacheDSQuery	true	When set to true, allows VisiBroker applications to cache IOR.
vbroker.orb.rebindForward	0 (zero)	This value determines the number of times a client will try to connect to a forwarded target. You can use this property when the client cannot communicate with the forwarded target (because of network failure, for example). The default value of 0 (zero) means that the client will keep trying to connect. It determines if the ORB should rebind in the case of a failure to connect during a LOCATION_FORWARD. When the client is forwarded to a new object, an attempt is made to connect to the new (destination) object. If this attempt ends in failure, the ORB transparently connects back to the original object (the source of the forward). This rebind to the source object occurs only if two conditions are fulfilled. The first is that the total number of forwards at this point (without a normal response punctuating them) should not have exceeded the count specified in this property. The second condition is that this failure should not be the second consecutive attempt to connect to the same destination object ending in failure. This prevents the ORB from getting trapped in a loop when a load balancer object repeatedly forwards to the same non-existent object.
vbroker.orb.activationIOR	null	Allows the launched server to easily establish contact with the OAD that launched it.
vbroker.orb.oadUID	0 (zero)	Used to ensure that the OAD that launched the server still exists - a value of 1.
vbroker.orb.propStorage	null	Specifies a property file that contains property values.
vbroker.orb.backCompat	FALSE	When set to TRUE, the server is operating in backward compatibility mode.
vbroker.orb.nullstring	FALSE	When set to TRUE, passing a null string causes a BAD_PARAM exception to be thrown. Passing zero length strings is allowed if vbroker.orb.backCompat is TRUE.
vbroker.orb.admDir	null	Specifies the administration directory at which various system files are located. This property can be set using the VBROKER_ADM environment variable.
vbroker.orb.isNTService	FALSE	When set to TRUE, this property coupled with the compile flag WIN32, enables any NT service/ COM+ app to stay running when a user logs out.
vbroker.orb. enableServerManager	FALSE	When set to TRUE, this property enables Server Manager within a server so that clients can access to it.
vbroker.orb.input. maxBuffers	16	Specifies the maximum number of input buffers retained in a pool. Defaults to 16. Set the value to 0 to disable the caching of the input buffers.
vbroker.orb.input.buffSize	255	Specifies the size of the input buffer.
vbroker.orb.output. maxBuffers	16	Specifies the maximum number of output buffers retained in a pool. Defaults to 16. Set the value to 0 to disable the caching of the output buffers.
vbroker.orb.output.buffSize	255	Specifies the size of the output buffer.
vbroker.orb.initRef	null	Specifies the initial reference.
vbroker.orb.defaultInitRef	null	Specifies the default initial reference.
vbroker.orb.boa_map.TSingle	boa_s	Maps the BOA bid policy of single threaded to boa_s.
vbroker.orb.boa_map.TPool	boa_tp	Maps the BOA bid policy of thread pool to boa_tp.
vbroker.orb.boa_map. TSession	boa_ts	Maps the BOA bid policy of thread session to boa_ts.
vbroker.orb.boa_map. TPool_LIOP	boa_ltp	Maps the BOA bid policy of local thread pool to boa_ltp.
vbroker.orb.alwaysProxy	false	When set to true, specifies that clients must always connect to the server using the GateKeeper.
vbroker.orb.gatekeeper.ior	null	Forces the client application to always connect to server through the GateKeeper whose IOR is provided.
vbroker.locator.ior	null	Specifies an IOR of the GateKeeper which will be used as proxy to Smart Agent. If this property is not set, the GateKeeper specified by the vbroker.orb.gatekeeper.ior property is used for this purpose. For more information, go to the VisiBroker GateKeeper Guide.
vbroker.orb. exportFirewallPath	false	Forces the server application to include firewall information as part of any servant's IOR which this server exposes (use Firewall::FirewallPolicy in your code to force it selectively per POA).
vbroker.orb.proxyPassthru	false	If set to true, forces PASSTHROUGH firewall mode globally in the application scope (use QoSExt::ProxyModePolicy in your code to force it selectively per object or per ORB).
vbroker.orb.bids.critical	inprocess	The critical bid has highest precedence no matter where it is specified in the bid order. If there are multiple values for critical bids, then their relative importance is decided by the bidOrder property.
vbroker.orb.bidOrder	inprocess:liop:ssl:iiop: proxy: hiop: locator	You can specify the relative order of importance for the various transports. Transports are given precedence as follows: 1 inprocess 2 liop 3 ssl 4 iiop 5 proxy 6 hiop 7 locator The transports that appear first have higher precedence. For example, if an IOR contains both LIOP and IIOP profiles, the first chance goes to LIOP. Only if the LIOP fails is IIOP used. (The critical bid, specified by the vbroker.orb.bids.critical property, has highest precedence no matter where it is specified in the bid order.)
vbroker.orb.dynamicLibs	null	Specifies a list of available services used by the VisiBroker ORB. Each service is separated by a comma. You can enter the value vbsec to load the correct configured security provider, provided that the VisiBroker lib directory is present on the shared library load path. This enables you to specify the security library without needing to know the exact full VisiSecure shared library name, prefix and shared library suffix. See the chapter Creating Secure CORBA Applications Using C++ in the VisiBroker for C++ Developer’s Guide for examples of using this property.
vbroker.orb.embedCodeset	true	When an IOR is created, the VisiBroker ORB embeds the codeset components into the IOR. This may produce problems with some non-compliant ORBs. By turning off the embedCodeset property, you instruct the VisiBroker ORB not to embed codesets in IORs. When set to false, specifies that character and wide character conversions between the client and the server are not to be negotiated.
vbroker.orb. enableVB4backcompat	false	This property enables work-arounds to deal with behavior that is not GIOP 1.2-compliant in VisiBroker 4.0 and 4.1. Any VisiBroker client running on VisiBroker 4.1.1 or a release previous to 4.1.1 is affected, especially if GateKeeper is involved. To work with a Visibroker 4.0 or 4.1 client, this flag needs to be set to true. This is a server-side only flag. There is no corresponding flag on the client side.
vbroker.orb. enableNullString	false	If set to TRUE, enables marshaling of null strings.
vbroker.orb.procId	0	Specifies the process ID of the server.
vbroker.orb.usingPoll	true	On UNIX platforms, the ORB uses the system calls select() or poll() for I/O multiplexing based on the value of this property. If the value is true, poll() is used. Otherwise, select() is used.
vbroker.orb. serverSendTimeout	0	Timeout in seconds for the server-side ORB to send a message to a client. Default value 0 means no timeout. If the write operation is blocked for more then the serverSendTimeout limit, it will timeout and close the connection.
vbroker.orb. serverRecvTimeout	0	Timeout in seconds for the server-side ORB to receive a message from a client. Default value of 0 means no timeout.
vbroker.orb.interceptor. backCompat	false	By default, this property enables the interceptor (when using with servant manager) to follow the behavior described in OMG CORBA Specification, section 21.3.9.1. If you set it to true, the behavior of VisiBroker interceptors (when using with servant manager) is the same as in VisiBroker version 6.5.
vbroker.orb.firewallInit	false	If this property is set to true, and if the IOR has both IIOP and TCP type Firewall components, then if any one of the end points fail, fail-over can occur. Setting vbroker.orb.alwaysProxy=true or a programmatically configured firewall proxy takes precedence.
vbroker.orb.mtmPerCall	true	If true, any thread calling ORB::perform_work() can performs the request. If false, the thread that calls ORB::perform_work() the first time becomes the "main thread" throughout the lifetime of the ORB. The call to ORB::perform_work() from a thread other than the "main thread" does nothing.
vbroker.orb.sendLocate	false	Set this property to true to send a GIOP Locate request on binding to verify it is a GIOP server.
vbroker.orb.ncsc	none	If set to UTF8, the ORB will use UTF-8 as the native code set for IDL char instead of ISO-LATIN-1. If the property is omitted then ISO-LATIN-1 will be used as the native code set.
vbroker.orb. tagAlternateIIOPAddress	null	Sets TAG_ALTERNATE_IIOP_ADDRESS components into IIOP Profiles. These components hold alternative host and port values which are interpreted by some ORBs as fall-back addresses in the event of a client's failure to connect. VisiBroker clients do not currently interpret these properties this way. JacORB is an example of an ORB that does so. The alternate IIOP addresses must be specified as per the corbaloc IOR/URI host and port rules. The property takes a string value; comma-separated multiple values are allowed. An example of this property use might look like: vbroker.orb.tagAlternateIIOPAddress=myhost.domain.com:54321,[fe80::20c:29ff:fe58:ce28]:23232,127.0.0.1:65000
vbroker.orb. allowRelativeFileIORs	false	If set to true, this property makes the C++ ORB accept file: scheme IORs of the form file:my.ior, and interpret them as locations relative to the current working directory. Note: This behavior matches that of the Visibroker Java ORB, where relative locations are always allowed. It will become the default in a future release of the C++ ORB, so if you require the previous behavior, without relative IORs, you should modify your configuration to specify: vbroker.orb.allowRelativeFileIORs=false

The file URL conforms to the standard format of “file://<domain name>/<path>/<file>”. However, there are some constraints in the format supported by VisiBroker for C++.

•	The protocol part of the URL must be file://

•	The domain name of the URL must be empty

•	All path specifications are absolute (relative paths are not allowed)

•	The path may not contain the character “:”. The path separator must be “/”

•	For Windows, the drive letter colon (“:”) must be replaced by the “|” symbol.

The following paths show examples of valid paths:

file:///home/user/appl.ior

file:///C|/My Documents/User/root.txt

ServerManager properties

This table lists the Server Manager properties.

Property	Default	Description
vbroker.serverManager.name	null	Specifies the name of the Server Manager.
vbroker.serverManager. enableOperations	true	When set to true, enables operations exposed, by the Server Manager, to be invoked.
vbroker.serverManager. enableSetProperty	true	When set to true, enables properties, exposed by the Server Manager, to be changed.

Properties showing run-time status of server

The following properties show information on the run-time state of the Server, which can be queried from through the Server Manager’s container. These are all read-only; you cannot modify them.

Properties related to Server-side resource usage

 

Property	Default	Description
vbroker.se.<SE_name>.scm. <SCM_name>.manager. allocatedFileDescriptors	N/A	The current number of file descriptors used by the Server Connection Manager (SCM). This value is typically equal to the current number of incoming connections plus two used by the listener.
vbroker.se.<SE_name>.scm. <SCM_name>.manager. maxFileDescriptor	N/A	The maximum value of the file descriptor with the SCM.
vbroker.se.<SE_name>.scm. <SCM_name>.manager. inUseConnections	N/A	The number of incoming connections for which there are requests executing in the ORB.
vbroker.se.<SE_name>.scm. <SCM_name>.manager. idleConnections	N/A	The number of incoming connections for which there are not any requests currently being executed in the ORB.
vbroker.se.<SE_name>.scm. <SCM_name>.manager. idledTimeoutConnections	N/A	The number of idle connections which have also idled past their idle timeout setting but have yet to be closed (due to garbage collection restrictions, for example).
vbroker.se.<SE_name>.scm. <SCM_name>.dispatcher. inUseThreads	N/A	The number of threads currently executing requests within the dispatcher.
vbroker.se.<SE_name>.scm. <SCM_name>.dispatcher. idleThreads	N/A	The number of threads which are currently idle waiting for work to be assigned.

Properties related to Client-side resource usage

 

Property	Description
vbroker.ce.<CE_name>.ccm. maxFileDescriptor	The maximum number of file descriptors within the Client Connection Manager (CCM).
vbroker.ce.<CE_name>.ccm. activeConnections	The number of connections in the active pool; that is, object references are using these connections.
vbroker.ce.<CE_name>.ccm. cachedConnections	The number of connections in the cache pool; no object references are using these connections.
vbroker.ce.<CE_name>.ccm. inUseConnections	The number of outgoing connections with pending requests.
vbroker.ce.<CE_name>.ccm. idleConnections	The number of outgoing connections with no pending requests.
vbroker.ce.<CE_name>.ccm. idledTimeoutConnections	The number of idle connections which have idled past their timeout setting but have not been closed.

Properties related to the Smart Agent (osagent)

 

Property	Description
vbroker.agent.currentAgentIP	The IP address of the current ORB's Smart Agent (Smart Agent).
vbroker.agent.currentAgentClientPort	The port of the Smart Agent to which the ORB is sending requests.

Miscellaneous Properties

 

Property	Description
vbroker.env.path	The value of the PATH environment variable under which the ORB is running.
vbroker.env.shlibPath	The value of the shared library path environment variable. In HP-UX, it corresponds to the SHLIB_PATH environment variable.
vbroker.env.orbVersion	This is the ORB version of the currently loaded ORB. It can also be obtained by running vbver liborb_r.sl in HP-UX.
vbroker.process. fileDescriptorLimit	The maximum number of file descriptors for the current process.
vbroker.orb.uid	The user ID of the user who started the VisiBroker server application.
vbroker.orb.commandLine	The command-line argument passed to the CORBA::ORB_init method.

Location Service properties

This table lists the Location Service properties.

Property	Default	Description
vbroker.locationservice. debug	false	When set to true, allows the Location Service to display debugging information. Note: This property is deprecated. See “Debug Logging properties” for recommended properties to use in its place.
vbroker.locationservice. verify	false	When set to true, allows the Location Service to check for the existence of an object referred by an object reference sent from the Smart Agent. Only objects registered BY_INSTANCE are verified for existence. Objects that are either registered with OAD, or those registered BY_POA policy are not verified for existence.
vbroker.locationservice. timeout	1	Specifies the connect/receive/send timeout, in seconds, when trying to interact with the Location Service.

Event Service properties

This table lists the Event Service properties.

Property	Default	Description
vbroker.events. maxQueueLength	100	Specifies the number of messages to be queued for slow consumers.
vbroker.events.factory	false	When set to true, allows the event channel factory to be instantiated, instead of an event channel.
vbroker.events.debug	false	When set to true, allows output of debugging information.
vbroker.events.interactive	false	When set to true, allows the event channel to be executed in a console-driven, interactive mode.

Naming Service (VisiNaming) properties

The following tables list the VisiNaming Service properties.

Property	Default	Description
vbroker.naming.adminPwd	inprise	Password required by administrative VisiBroker naming service operations.
vbroker.naming.enableSlave	0	If 1, enables master/slave naming services configuration. See “VisiNaming Service Clusters for Failover and Load Balancing” for information about master/slave naming services.
vbroker.naming.iorFile	ns.ior	This property specifies the full path name for storing the naming service IOR. If you do not set this property, the naming service will try to output its IOR into a file named ns.ior in the current directory. The naming service silently ignores file access permission exceptions when it tries to output its IOR.
vbroker.naming.logLevel	emerg	Note: This property is deprecated. See “Debug Logging properties” for recommended properties to use in its place. This property specifies the level of log messages to be output from naming service. Acceptable values are: • emerg (0): indicates some panic condition. • alert (1): a condition that requires user attention--for example, if security has been disabled. • crit (2): critical conditions, such as a device error. • err (3): error conditions. • warning (4): warning conditions--these may accompany some troubleshooting advice. • notice (5): conditions that are not errors but may require some attention, such as upon the opening of a connection. • info (6): informational, such as binding in progress. • debug (7): debug conditions understood by developers.
vbroker.naming.logUpdate	false	This property allows special logging for all of the update operations on the CosNaming::NamingContext, CosNamingExt::Cluster, and CosNamingExt::ClusterManager interfaces. The CosNaming::NamingContext interface operations for which this property is effective are: bind, bind_context, bind_new_context, destroy, rebind, rebind_context, unbind. The CosNamingExt::Cluster interface operations for which this property is effective are: bind, rebind, unbind, destroy. The CosNamingExt::ClusterManager interface operation for which this property is effective is: create_cluster When this property value is set to true and any of the above methods is invoked, the following log message is printed (the output shows a bind operation being executed): 00000007,5/26/04 10:11 AM,127.0.0.1,00000000, VBJ-Application,VBJ ThreadPool Worker,INFO, OPERATION NAME : bind CLIENT END POINT : Connection[socket=Socket [addr=/127.0.0.1, port=2026, localport=1993]] PARAMETER 0 : [(Tom.LoanAccount)] PARAMETER 1 : Stub[repository_id=IDL:Bank/ LoanAccount:1.0, key=TransientId[poaName=/, id={4 bytes: (0)(0)(0)(0)},sec=505,usec=990917734, key_string=%00VB%01%00%00%00%02/%00%20%20%00%00%00% 04%00%00%00%00%00%00%01%f9;%104f], codebase=null]
vbroker.se.iiop_tp.scm. iiop_tp.listener. deferAccept, vbroker.se.iiop_tp.scm.ssl. listener.deferAccept	false	Causes the Naming Service to discard incoming requests while starting up. Though the property form is generic, it should only be used with Naming Service. Use with any other service or application can cause unknown behavior. This property only works when: 1 Listener port is set. 2 Listener port range is not specified.

Properties relating to object clustering

For more information see , “Using the VisiNaming Service.”

Property	Default	Description
vbroker.naming. enableClusterFailover	true	When set to true, it specifies that an interceptor be installed to handle fail-over for objects that were retrieved from the VisiNaming Service. In case of an object failure, an attempt is made to transparently reconnect to another object from the same cluster as the original.
vbroker.naming.propBindOn	0	If 1, the implicit clustering feature is turned on.
vbroker.naming.smrr. pruneStaleRef	1	This property is relevant when the name service cluster uses the Smart Round Robin criterion. When this property is set to 1, a stale object reference that was previously bound to a cluster with the Smart Round Robin criterion will be removed from the bindings when the name service discovers it. If this property is set to 0, stale object reference bindings under the cluster are not eliminated. However, a cluster with Smart Round Robin criterion will always return an active object reference upon a resolve() or select() call if such an object binding exists, regardless of the value of the vbroker.naming.smrr.pruneStaleRef property. By default, the implicit clustering in the name service uses the Smart Round Robin criterion with the property value set to 1. If set to 2, this property disables the clearing of stale references completely, and the responsibility of cleaning up the bindings belongs to the application, rather than to VisiNaming.

VisiNaming service cluster related properties

For more information see , “Using the VisiNaming Service.”

Property	Default	Description
vbroker.naming.enableSlave	0	See “VisiNaming Service properties”.
vbroker.naming.slaveMode	None	This property is used to configure VisiNaming Service instances in the cluster mode or in the master/slave mode. The vbroker.naming.enableSlave property must be set to 1 for this property to take effect. There is no default. Possible values are cluster or slave. Set this property to cluster to configure VisiNaming Service instances in the cluster mode. VisiNaming Service clients will then be load balanced among the VisiNaming Service instances that comprise the cluster. Client failover across these instances are enabled. Set this property to slave to configure VisiNaming Service instances in the master/slave mode. VisiNaming Service clients will always be bound to the master server if the master is running but failover to the slave server when the master server is down.
vbroker.naming. serverClusterName	null	This property specifies the name of a VisiNaming Service cluster. Multiple VisiNaming Service instances belong to a particular cluster (for example, clusterXYZ) when they are configured with the cluster name using this property.
vbroker.naming.serverNames	null	This property specifies the factory names of the VisiNaming Service instances that belong to a cluster. Each VisiNaming Service instance within the cluster should be configured using this property to be aware of all the instances that constitute the cluster. Each name in the list must be unique. This property supports the format: vbroker.naming.serverNames= Server1:Server2:Server3 See the related property, vbroker.naming.serverAddresses.
vbroker.naming. serverAddresses	null	This property specifies the host and listening port for the VisiNaming Service instances that comprise a VisiNaming Service cluster. The order of VisiNaming Service instances in this list must be identical to that of the related property vbroker.naming.serverNames, which specifies the names of the VisiNaming Service instances that comprise a VisiNaming Service Cluster. This property supports the format: vbroker.naming.serverAddresses=host1: port1;host2:port2; host3:port3
vbroker.naming. anyServiceOrder (To be set on VisiNaming Service clients)	false	This property must be set to true on the VisiNaming Service client to utilize the load balancing and failover features available when VisiNaming Service instances are configured in the VisiNaming Service cluster mode. The following is an example of how to use this property: client -DVbroker.naming. anyServiceOrder=true

Pluggable Backing Store Properties

The following tables show property information for the VisiNaming service pluggable backing store types.

Default properties common to all adapters

 

Property	Default	Description
vbroker.naming. backingStoreType	InMemory	Specifies the naming service adapter type to use. This property specifies which type of backing store you want the VisiNaming Service to use. The valid options are: InMemory, JDBC, Dx, JNDI. The default is InMemory.
vbroker.naming.cacheOn	0	Specifies whether to use the Naming Service cache. A value of 1 (one) enables caching.
vbroker.naming.cache. connectString	N/A	This property is required when the Naming Service cache is enabled (vbroker.naming.cacheOn=1) and the Naming Service instances are configured in Cluster or Master/Slave mode. It helps locate an Event Service instance in the format <hostname>:<port>. For example: vbroker.naming.cache.connectString=127.0.0.1:14500 See “Caching facility” for details about enabling the caching facility and setting the appropriate properties.
vbroker.naming.cache.size	2000	This property specifies the size of the Naming Service cache. Higher values will mean caching of more data at the cost of increased memory consumption.
vbroker.naming.cache. timeout	0 (no limit)	This property specifies the time, in seconds, since the last time a piece of data was accessed, after which the data in the cache will be purged in order to free memory. The cached entries are deleted in LRU (Least Recently Used) order.

JDBC Adapter properties

 

Property	Default	Description
vbroker.naming. jdbcDriver	com.borland.datastore.jdbc.DataStoreDriver	This property specifies the JDBC driver that is needed to access the database used as your backing store. The VisiNaming Service loads the appropriate JDBC driver specified. Valid values are: • com.borland.datastore.jdbc.DataStoreDriver—JDataStore driver • com.sybase.jdbc.SybDriver—Sybase driver • oracle.jdbc.driver.OracleDriver—Oracle driver • interbase.interclient.Driver—Interbase driver • weblogic.jdbc.mssqlserver4.Driver—WebLogic MS SQLServer Driver • COM.ibm.db2.jdbc.app.DB2Driver—IBM DB2 Driver
vbroker.naming. resolveAutoCommit	true	Sets Auto Commit on the JDBC connection when doing a "resolve" operation. When this property is set to "false", the resolve operation will use the same "transaction" pattern as that is used in other similar methods like bind, rebind and etc. If set it to "true", there will be better performance for the "resolve" operation. For VisiNaming using JDS HA failover configuration, set this property to "false".
vbroker.naming.loginName	VisiNaming	The login name associated with the database.
vbroker.naming.loginPwd	VisiNaming	The login password associated with the database.
vbroker.naming.poolSize	5	This property specifies the number of database connections in your connection pool when using the JDBC Adapter as your backing store.
vbroker.naming.url	jdbc:borland:dslocal:rootDB.jds	This property specifies the location of the database which you want the Naming Service to access. The setting is dependent upon the database in use. Acceptable values are: • jdbc:borland:dslocal:<db-name>—JDataStore UTL • jdbc:sybase:Tds:<host-name>:<port-number>/<db-name>—Sybase URL • jdbc:oracle:thin@<host-name>:<port-number>:<sid>—Oracle URL • jdbc:interbase://<server-name>/<full-db-path>—Interbase URL • jdbc:weblogic:mssqlserver4:<db-name>@<host-name>:<port-number>—WebLogic MS SQLSever URL • jdbc:db2:<db-name>—IBM DB2 URL • <full-path-JDataStore-db>—DataExpress URL for the native driver
vbroker.naming. minReconInterval	30	This property sets the database reconnection retry time by the Naming Service in seconds. The default value is 30. The Naming Service will ignore the request and throw a CannotProceed exception if the time interval between this request and the last reconnection time is less than the vset value. Valid values for this property are non-negative integers. If set to 0, the Naming Service will try to reconnect to the database for every request.

DataExpress Adapter properties

The following table describes the DataExpress Adapter properties:

Property	Description
vbroker.naming.backingStoreType	This property should be set to Dx.
vbroker.naming.loginName	This property is the login name associated with the database. The default is VisiNaming.
vbroker.naming.loginPwd	This property is the login password associated with the database. The default value is VisiNaming.
vbroker.naming.url	This property specifies the location of the database.

JNDI adapter properties

The following is an example of settings that can appear in the configuration file for a JNDI adapter:

Setting	Description
vbroker.naming.backingStoreType=JNDI	This setting specifies the backing store type which is JNDI for the JNDI adapter.
vbroker.naming.loginName=<user_name>	The user login name on the JNDI backing server.
vbroker.naming.loginPwd=<password>	The password for the JNDI backing server user.
vbroker.naming.jndiInitialFactory= com.sun.jndi.ldap.LdapCtxFactory	This setting specifies the JNDI initial factory.
vbroker.naming.jndiProviderURL= ldap://<hostname>:389/<initial root context>	This setting specifies the JNDI provider URL
vbroker.naming.jndiAuthentication= simple	This setting specifies the JNDI authentication type supported by the JNDI backing server.

VisiNaming Service Security-related properties

 

Property	Value	Default	Description
vbroker.naming. security.disable	boolean	true	This property indicates whether the security service is disabled.
vbroker.naming. security.authDomain	string	“”	This property indicates the authorization domain name to be used for the naming service method access authorization.
vbroker.naming. security.transport	int	3	This property indicates what transport to be used. The available values are: ServerQoPPolicy.SECURE_ONLY=1 ServerQoPPolicy.CLEAR_ONLY=0 ServerQoPPolicy.ALL=3
vbroker.naming. security. requireAuthentication	boolean	false	This property indicates whether naming client authentication is required. When vbroker.naming.security.disable is true, no client authentication will be performed regardless what value this property takes.
vbroker.naming. security. enableAuthorization	boolean	false	This property indicates whether method access authorization is enabled.
vbroker.naming. security. requiredRolesFile	string	null	This property points to the file containing the required roles that are necessary for invocation of each method in the protected object types. For more information see “Method Level Authorization”

OAD properties

This table lists the OAD properties that can be set.

Property	Default	Description
vbroker.oad.spawnTimeOut	20	After the OAD spawns an executable, specifies how long, in seconds, the system will wait to receive a callback from the desired object before throwing a NO_RESPONSE exception.
vbroker.oad.verbose	false	Allows the OAD to print detailed information about its operations.
vbroker.oad.readOnly	false	When set to true, does not allow you to register, unregister, or change the OAD implementation.
vbroker.oad.iorFile	Oadj.ior	Specifies the filename for the OAD's stringified IOR.
vbroker.oad.quoteSpaces	false	Specifies whether to quote a command.
vbroker.oad. killOnUnregister	false	Specifies whether to kill spawned servers once they are unregistered.
vbroker.oad. verifyRegistration	false	Specifies whether to verify the object registration.

This table lists the OAD properties that cannot be overridden in a property file. They can however be overridden with environment variables or from the command line.

Property	Default	Description
vbroker.oad.implName	impl_rep	Specifies the filename for the implementation repository.
vbroker.oad.implPath	null	Specifies the directory where the implementation repository is stored.
vbroker.oad.path	null	Specifies the directory for the OAD.
vbroker.oad.systemRoot	null	Specifies the root directory.
vbroker.oad.windir	null	Specifies the Windows directory.

Interface Repository properties

This table lists the Interface Repository (IR) properties.

Property	Default	Description
vbroker.ir.debug	false	When set to true, allows the IR resolver to display debugging information.
vbroker.ir.ior	null	When the vbroker.ir.name property is set to the default value, null, the VisiBroker ORB will try to use this property to locate the IR.
vbroker.ir.name	null	Specifies the name that is used by the VisiBroker ORB to locate the IR.

TypeCode properties

The table below lists the VisiBroker for C++ TypeCode properties.

Property	Default	Description
vbroker.typecode.debug	false	When set to true, this property allows the typecode code to display debugging. Note: This property is deprecated. See “Debug Logging properties” for recommended properties to use in its place.
vbroker.typecode. noIndirection	false	When set to true, this property does not allow the use of indirection when writing a recursive typecode.
vbroker.typecode. marshalName	true	Marshalling of names inside typecode data can now be suppressed by replacing these with empty strings, since the OMG spec allows. This will save network bandwidth by reducing the length of GIOP messages. However, the API functions relying on this data will not function correctly when compression is used. By default, the compression is not done. To enable this, set this property to false.
vbroker.orb. topLevelTCIndirection	0	Top-level typecode indirection optimization was introduced in VisiBroker 7.0. Details of this can be examined as OMG Issue 4796 at http://www.omg.org. You may need to turn this optimization off to guarantee successful communication with applications of an older VisiBroker version, which do not recognize the optimization and may cause a MARSHAL exception. This property allows you to turn off the top-level typecode indirection optimization. Possible values are: 0 - Disable top-level typecode indirection. 1 - Only support reading of top-level typecode indirection. 2 - Support both read and write of top-level typecode indirection. 3 - Turn optimization off when a VisiBroker 7.0 or above supplier is operating with a VisiBroker 5.x/6.x consumer, via VisiNotify Service version 7.0 or above.

Client-side LIOP connection properties

The table below lists the VisiBroker for C++ Client-side LIOP Connection properties.

Property	Default	Description
vbroker.ce.liop.ccm. connectionCacheMax	5	Specifies the maximum number of cached connections on a client. The connection is cached when a client releases it. Therefore, the next time a client needs a new connection, it can retrieve one from the cache instead of creating a new one.
vbroker.ce.liop.ccm. disableConnectionCache	false	When set to true, this property disables connection caching on the client side.
connectionMax	0	Specifies the maximum number of total connections for a client. This includes the active connections, plus the ones that are cached. The default value of 0 (zero) specifies that the client will not try to close any of the old active or cached connections.
connectionMaxIdle	360	Specifies the time, in seconds, that the client uses to determine if a cached connection should be closed. If a cached connection has been idle longer than this time, then the client will close the connection.
vbroker.ce.liop.ccm.type	Pool	Specifies the type of client connection management used by a client. The default value Pool means connection pool. This is currently the only valid value for this property.
vbroker.ce.liop. connection.rcvBufSize	0	Specifies the size of the receive socket buffer. The default value 0 (zero) implies a system dependent value.
vbroker.ce.liop.connection. sendBufSize	0	Specifies the size of the send socket buffer. The default value 0 (zero) implies a system dependent value.
vbroker.ce.liop.connection. shmSize	4096	Specifies the size, in bytes, of shared memory. If your client program and object implementation communicate via shared memory, you may use this option to enhance performance.
vbroker.se.default.local. listener.doorMaxMsgSize	1,000,000	Specifies the maximum message size which will be sent through the fast IPC (door) mechanism in Solaris (when the client and server are running on the same machine). If the message size is greater than the default value (1,000,000), it will not be sent using the IPC, and will default to the next available mechanism (UNIX domain socket or TCP/IP socket).

Client-side IIOP connection properties

The table below lists the VisiBroker for C++ Client-side IIOP Connection properties.

Property	Default	Description
vbroker.ce.iiop.ccm. connectionCacheMax	5	Specifies the maximum number of cached connections on a client. The connection is cached when a client releases it. Therefore, the next time a client needs a new connection, it can retrieve one from the cache instead of creating a new one.
vbroker.ce.iiop.ccm. disableConnectionCache	false	When set to true, this property disables connection caching on the client side.
vbroker.ce.iiop.ccm. connectionMax	0	Specifies the maximum number of the total connections within a client. This is equal to active connections plus the ones that are cached. The default value of zero means that the client does not try to close any of the old active or cached connections.
vbroker.ce.iiop.ccm. connectionMaxIdle	0	Specifies the time in seconds that the client uses to determine if a cached connection should be closed. If a cached connection has been idle longer than this time, then the client closes it.
vbroker.ce.iiop.ccm.type	Pool	Specifies the type of client connection management used by a client. The value Pool means connection pool. This is currently the only valid value for this property.
vbroker.ce.iiop.clientPort	0 (system-defined port)	Specifies the client port to be used when a connection is opened by the ORB. Allowed values range from 0 to 65535.The default 0 (zero) means a system-defined port; on most systems this will be the next available port after the last one used. A range should be specified using the vbroker.ce.iiop.clientPortRange property when this property is used.
vbroker.ce.iiop. clientPortRange	0	Specifies the range of client ports to be used when a connection is opened by the ORB, starting with the port specified by the vbroker.ce.iiop.clientPort property. Allowed values range from 0 to 65535.
vbroker.ce.iiop. connection.forceLinger	false	A TCP/IP setting.
vbroker.ce.iiop.connection. rcvBufSize	0	Specifies the size of the receive socket buffer. The default value 0 (zero) implies system dependent value.
vbroker.ce.iiop.connection. sendBufSize	0	Specifies the size of the send socket buffer. The default value 0 (zero) implies system dependent value.
vbroker.ce.iiop.connection. tcpNoDelay	false	When set to TRUE, the server's sockets are configured to send any data written to them immediately instead of batching the data as the buffer fills.
vbroker.ce.iiop.host	none	Binds the client side sockets to a specified local address (or addresses), which can be useful when interacting with firewalls or routing tables. You can use this property to specify an address in IPv4 or IPv6 format, or to specify two addresses, one in each format, separated by a comma. For example: vbroker.ce.iiop.host=192.168.0.1,fdb0::1234:1 If you specify more than one address in the same format, the first valid address is used and an error message is generated. If you only specify one address it is used for both address types, enabling an IPv4-mapped IPv6 address to be used for both types. If no address is specified the value is left for the underlying system to determine.
vbroker.ce.iiop.connection. noCallback	false	When set to TRUE, this property allows the server to call back to the client.
vbroker.ce.iiop.connection. socketLinger	0	A TCP/IP setting.
vbroker.ce.iiop.connection. keepAlive	true	A TCP/IP setting.
vbroker.ce.iiop.connection. ipv6ScopeId	null	Provides a value that identifies the scope identifier or interface number. It is used in conjunction with the IPv6 scoped addresses such as link-local or site-local. The default value is null. This value will be used to formulate into the form “<ipv6 address="">%<ipv6scopeid>” for the getaddrinfo() network function to translate the scope identifier string into a sin6_scope_id integer value of the sockaddr_in6 structure. The IPv6 scoped address is from the IOR host address.

QoS-related Properties

 

Property	Default	Description
vbroker.qos.cache	True	Specifies if QoS policies should be cached per delegate instead of being checked prior to every request made by the client.
vbroker.qos. defaultRRTTimeout	0	Sets the default value in milliseconds of relative round trip request timeout. Default 0 means no timeout.
vbroker.qos. defaultRRQTimeout	0	Sets the default value in milliseconds of relative request timeout. Default 0 means no timeout
vbroker.orb.qos. defaultConnectTimeout	0	Sets the default value in milliseconds of connection timeout. Default 0 means no timeout.

Server-side server engine properties

This table lists the server-side server engine properties.

Property	Default	Description
vbroker.se.default	iiop_tp	Specifies the default server engine.
vbroker.se.default.local. manager.enabled	true	When set to false, disables LIOP connection.

Server-side thread session IIOP_TS/IIOP_TS connection properties

This table lists the server-side thread session IIOP_TS/IIOP_TS connection properties.

Property	Default	Description
vbroker.se.iiop_ts.host	null	Specifies the host name used by this server engine. The default value, null, means use the host name from the system.
vbroker.se.iiop_ts. proxyHost	null	Specifies the proxy host name used by this server engine. The default value, null, means use the host name from the system.
vbroker.se.iiop_ts.scms	iiop_ts	Specifies the list of Server Connection Manager name(s). One possible value for security would be ssl. See the VisiBroker Security Guide for details.
vbroker.se.iiop_ts.scm. iiop_ts.manager.type	Socket	Specifies the type of Server Connection Manager.
vbroker.se.iiop_ts.scm. iiop_ts.manager. connectionMax	0	Specifies the maximum number of connections the server will accept. The default value, 0 (zero), implies no restriction.
vbroker.se.iiop_ts.scm. iiop_ts.manager. connectionMaxIdle	0	Specifies the time in seconds the server uses to determine if an inactive connection should be closed or not.
vbroker.se.iiop_ts.scm. iiop_ts.manager. garbageCollectTimer	30	The number of seconds between garbage-collection for connection objects.
vbroker.se.iiop_ts.scm. iiop_ts.listener.type	IIOP	Specifies the type of protocol the listener is using.
vbroker.se.iiop_ts.scm. iiop_ts.listener. preferIPv4Stack	false	A boolean value indicating whether the listener has to use IPv4 or IPv6. The default value is false, which will enforce usage of IPv6. If the property vbroker.se.iiop_ts.host is given an IPv4 or IPv6 address value, then you can ignore the property setting. Note: On Windows XP platforms, the IPv6 stack does not accept IPv4 traffic. This is a Microsoft implementation limitation. However, Windows Vista and above do not have such a limitation. Enabling the IPv6 stack on Windows XP requires the associated “…preferIPv6Address…” properties to be set accordingly. This property also supersedes the old-style property name vbroker.connection.onlyListenIPv4=<false|true>.
vbroker.se.iiop_ts.scm. iiop_ts.listener. preferIPv6Addresses	false	A boolean value indicating whether the listener would generate IPv4 or IPv6 address. The default value is false, which put IPv4 address into the IOR. If the property vbroker.se.iiop_tp.host is given an IPv4 or IPv6 address value, then you can ignore this property setting.
vbroker.se.iiop_ts.scm. iiop_ts.listener. preferIPv6AddressType	none	Specifies the preferred IPv6 address scope type to be returned if multiple scope addresses are configured for a given host. The default value is none. Valid values are none, linklocal, and others. • none provides the first address returned by the getaddrinfo() network function. • linklocal provides the address type of Link-Local. • others returned the first other address except if it is the Link-Local type.
vbroker.se.iiop_ts.scm. iiop_ts.listener. ipv6ScopeId	null	Provides a value that identified the scope identifier or interface number. It is used in conjunction with the IPv6 scoped addresses such as link-local or site-local. The default value is null. This value will be used to formulate into the form “<ipv6 address>%<ipv6ScopeId>” for the getaddrinfo() network function to translate the scope identifier string into a sin6_scope_id integer value of the sockaddr_in6 structure. For example: vbroker.se.iiop_ts.scm.iiop_ts.listener. preferIPv6Addresses=true vbroker.se.iiop_ts.scm.iiop_ts.listener.ipv6ScopeId=eth0   If a link-local address is returned with the value “fe80::1”, then internally the scoped address “fe80::1%eth0” is formulated and passed to getaddrinfo(). Alternatively, you could also set it via "vbroker.se.iiop_ts.host" with the value “fe80::1%eth0”.
vbroker.se.iiop_ts.scm. iiop_ts.listener.port	0	Specifies the port number that is used with the host name property. The default value, 0 (zero), means the system will pick a random port number.
vbroker.se.iiop_ts.scm. iiop_ts.listener.proxyPort	0	Specifies the proxy port number used with the proxy host name property. The default value, 0 (zero), means the system will pick a random port number.
vbroker.se.iiop_ts.scm. iiop_ts.listener.rcvBufSize	0	Specifies the size of the receive socket buffer. The default value 0 implies system dependent value.
vbroker.se.iiop_ts.scm. iiop_ts.listener. sendBufSize	0	Specifies the size of the send buffer. The default value 0 implies a system dependent value.
vbroker.se.iiop_ts.scm. iiop_ts.listener. socketLinger	0	A TCP/IP Setting.
vbroker.se.iiop_ts.scm. iiop_ts.listener. keepAlive	0	A TCP/IP Setting.
vbroker.se.iiop_ts.scm. iiop_ts.listener. giopVersion	1.2	This property can be used to resolve interoperability problems with older VisiBroker ORBs that cannot handle unknown minor GIOP versions correctly. Legal values for this property are 1.0, 1.1 and 1.2. For example, to make the nameservice produce a GIOP 1.1 ior, start it like this: nameserv -VBJprop vbroker.se.iiop_tp.scm.iiop_tp.listener.giopVersion=1.1
vbroker.se.iiop_ts.scm. iiop_ts.dispatcher.type	Thread Session	Specifies the type of thread dispatcher used in the Server Connection Manager.
vbroker.se.iiop_ts.scm. iiop_ts.dispatcher. threadStackSize	0	The size of the thread stack. The default value, 0, indicates system default. However, on the HP-UX platform, the default value is 128 KB.
vbroker.se.iiop_ts.scm. iiop_ts.dispatcher. coolingTime	3	Time duration in seconds when a connection is considered hot (expecting more requests). After the time is elapsed, the connection is returned back from the dispatcher.
vbroker.se.iiop_ts.scm. iiop_ts.connection. rcvBufSize	0	Specifies the size of the receive socket buffer. The default value 0 implies a system-dependent value.
vbroker.se.iiop_ts.scm. iiop_ts.connection. sendBufSize	0	Specifies the size of the send buffer. The default value 0 implies a system dependent value.
vbroker.se.iiop_ts.scm. iiop_ts.connection. socketLinger	0	A TCP/IP setting
vbroker.se.iiop_ts.scm. iiop_ts.connection. keepAlive	true	A TCP/IP setting
vbroker.se.iiop_ts.scm. iiop_ts.connection. tcpNoDelay	true	When this property is set to false, this turns on buffering for the socket. The default value, true, turns off buffering, so that all packets are sent as soon as they are ready.

Server-side thread session BOA_TS/BOA_TS connection properties

This protocol has the same set of properties as the “Server-side thread session IIOP_TS/IIOP_TS connection properties”, by replacing alliiop_ts with boa_ts in all the properties. For example, the vbroker.se.iiop_ts.scm.iiop_ts.manager.connectionMax will become vbroker.se.boa_ts.scm.boa_ts.manager.connectionMax. Also, the default value for vbroker.se.boa_ts.scms is boa_ts.

Server-side thread pool IIOP_TP/IIOP_TP connection properties

This table lists the server-side thread pool IIOP_TP/IIOP_TP connection properties.

Property	Default	Description
vbroker.se.iiop_tp.host	null	Specifies the host name that can be used by this server engine. The default value, null, means use the host name from the system. Host names or IP addresses are acceptable values.
vbroker.se.iiop_tp. proxyHost	null	Specifies the proxy host name that can be used by this server engine. The default value, null, means use the host name from the system. Host names or IP addresses are acceptable values.
vbroker.se.iiop_tp.scms	iiop_tp	Specifies the list of Server Connection Manager name(s). One possible value for security would be ssl. See the VisiBroker Security Guide for details.
vbroker.se.iiop_tp.scm. iiop_tp.manager.type	Socket	Specifies the type of Server Connection Manager.
vbroker.se.iiop_tp.scm. iiop_tp.manager. connectionMax	0	Specifies the maximum number of cache connection on the server. The default value, 0 (zero), implies no restriction.
vbroker.se.iiop_tp.scm. iiop_tp.manager. connectionMaxIdle	0	Specifies the time in seconds that the server uses to determine if an inactive connection should be closed or not.
vbroker.se.iiop_tp.scm. iiop_tp.listener.type	IIOP	Specifies the type of protocol the listener is using.
vbroker.se.iiop_tp.scm. iiop_tp.listener. preferIPv4Stack	false	A boolean value indicating whether the listener has to use IPv4 or IPv6. The default value is false, which will enforce usage of IPv6. If the property "vbroker.se.iiop_tp.host" is given an IPv4 or IPv6 address value, then you can ignore the property setting. Note: On Windows XP platforms, the IPv6 stack does not accept IPv4 traffic. This is a Microsoft implementation limitation. However, Windows Vista and above do not have such a limitation. Enabling the IPv6 stack on Windows XP requires the associated “…preferIPv6Address…” properties to be set accordingly. This property also supersedes the old-style property name vbroker.connection.onlyListenIPv4=<false|true>.
vbroker.se.iiop_tp.scm. iiop_tp.listener. preferIPv6Addresses	false	A boolean value indicating whether the listener would generate IPv4 or IPv6 address. The default value is false, which put IPv4 address into the IOR. If the property vbroker.se.iiop_tp.host is given an IPv4 or IPv6 address value, then you can ignore this property setting.
vbroker.se.iiop_tp.scm. iiop_tp.listener. preferIPv6AddressType	none	Specifies the preferred IPv6 address scope type to be returned if multiple scope addresses are configured for a given host. The default value is none. Valid values are none, linklocal, and others. • none provides the first address returned by the getaddrinfo() network function. • linklocal provides the address type of Link-Local. • others returned the first other address except if it is the Link-Local type.
vbroker.se.iiop_tp.scm. iiop_tp.listener. ipv6ScopeId	null	Provides value that identified the scope identifier or interface number. It is used in conjunction with the IPv6 scoped addresses such as link-local or site-local. The default value is null. This value will be used to formulate into the form “<ipv6 address>%<ipv6ScopeId>” for the getaddrinfo() network function to translate the scope identifier string into a sin6_scope_id integer value of the sockaddr_in6 structure. For example: vbroker.se.iiop_tp.scm.iiop_tp.listener. preferIPv6Addresses=true vbroker.se.iiop_tp.scm.iiop_tp.listener.ipv6ScopeId=eth0   If a link-local address is returned with the value “fe80::1”, then internally the scoped address “fe80::1%eth0” is formulated and passed to getaddrinfo(). Alternatively, you could also set it via "vbroker.se.iiop_tp.host" with the value “fe80::1%eth0”.
vbroker.se.iiop_tp.scm. iiop_tp.listener.port	0	Specifies the port number used with the host name property. The default value, 0 (zero), means that the system will pick a random port number.
vbroker.se.iiop_tp.scm. iiop_tp.listener.portRange	0 (zero)	This property is effective only when listener.port is greater than 0 (zero). If the listener cannot bind to that port because the port may be in use then the listener will try to bind to the ports in the range [port, port+portRange]. If no ports in the range are available then a COMM_FAILURE exception will be thrown.
vbroker.se.iiop_tp.scm. iiop_tp.listener.proxyPort	0	Specifies the proxy port number used with the proxy host name property. The default value, 0 (zero), means that the system will pick a random port number.
vbroker.se.iiop_tp.scm. iiop_tp.listener.rcvBufSize	0	Specifies the size of the receive socket buffer. The default value 0 implies a system-dependent value.
vbroker.se.iiop_tp.scm. iiop_tp.listener. sendBufSize	0	Specifies the size of the send socket buffer. The default value 0 implies a system-dependent value.
vbroker.se.iiop_tp.scm. iiop_tp.listener. socketLinger	0	A TCP/IP setting.
vbroker.se.iiop_tp.scm. iiop_tp.listener.keepAlive	true	A TCP/IP setting.
vbroker.se.iiop_tp.scm. iiop_tp.listener. giopVersion	1.2	This property can be used to resolve interoperability problems with older VisiBroker ORBs, that cannot handle unknown minor GIOP versions correctly. Acceptable values for this property are 1.0, 1.1 and 1.2.
vbroker.se.iiop_tp.scm. iiop_tp.dispatcher.type	ThreadPool	Specifies the type of thread dispatcher used in the Server Connection Manager.
vbroker.se.iiop_tp.scm. iiop_tp.dispatcher. threadMin	0	Specifies the minimum number of threads that the Server Connection Manager can create.
vbroker.se.iiop_tp.scm. iiop_tp.dispatcher. threadMax	0	Specifies the maximum number of threads that the Server Connection Manager can create. The default value 0 (zero) implies the ORB will control the thread generation using an internal algorithm based on heuristics. Setting the property vbroker.se.iiop_tp.scm.iiop_tp.dispatcher.unlimitedConcurrency=true implies that setting this property to 0 enables and unlimited number of threads in the thread pool to be created.
vbroker.se.iiop_tp.scm. iiop_tp.dispatcher. threadMaxIdle	300	Specifies the time in seconds before an idle thread will be destroyed.
vbroker.se.iiop_tp.scm. iiop_tp.dispatcher. threadStackSize	0	The size of the thread stack. The default value 0 indicates the system default. However, on the HP-UX platform, the default value is 128 KB.
vbroker.se.iiop_tp.scm. iiop_tp.dispatcher. coolingTime	3	Time duration, in seconds, when a connection is considered hot (expecting more requests). After the time is elapsed, the connection is returned back from the dispatcher.
vbroker.se.iiop_tp.scm. iiop_tp.connection. rcvBufSize	0	Specifies the size of the receive socket buffer. The default value 0 implies a system dependent value.
vbroker.se.iiop_tp.scm. iiop_tp.connection. sendBufSize	0	Specifies the size of the send buffer. The default value 0 implies a system dependent value.
vbroker.se.iiop_tp.scm. iiop_tp.connection. socketLinger		A TCP/IP setting.
vbroker.se.iiop_tp.scm. iiop_tp.connection. keepAlive		A TCP/IP setting.
vbroker.se.iiop_tp.scm. iiop_tp.connection. tcpNoDelay	true	When this property is set to false, this turns on buffering for the socket. The default value, true, turns off buffering, so that all packets are sent as soon as they are ready.
vbroker.iiop_tp.scm. iiop_tp.dispatcher. unlimitedConcurrency	false	Setting this property to true allows the thread pool dispatcher to create an unlimited number of threads when the property vbroker.se.xxx.scm.yyy.dispatcher.threadMax is set to 0. By default, the ORB will utilize internal heuristics calculation to determine the need of creating new threads.

Server-side thread pool BOA_TP/BOA_TP connection properties

This protocol has the same set of properties as the “Server-side thread pool IIOP_TP/IIOP_TP connection properties”, but replacing all iiop_tp with boa_tp in all the properties. For example, vbroker.se.iiop_tp.scm.iiop_tp.manager.connectionMax becomes vbroker.se.boa_tp.scm.boa_tp.manager.connectionMax. Also, the default value for vbroker.se.boa_tp.scms is boa_tp.

Server-side thread pool LIOP_TP/LIOP_TP connection properties

This table lists the server-side thread pool LIOP_TP/LIOP_TP connection properties.

Property	Default	Description
vbroker.se.liop_tp.host	null	Specifies the host name that can be used by this server engine. The default value, null, means use the host name from the system. Host names or IP addresses are acceptable values.
vbroker.se.liop_tp. proxyHost	null	Specifies the proxy host name that can be used by this server engine. The default value, null, means use the host name from the system. Host names or IP addresses are acceptable values.
vbroker.se.liop_tp.scms	liop_tp	Specifies the list of Server Connection Manager name(s).
vbroker.se.liop_tp.scm. liop_tp.manager.type	Local	Specifies the type of Server Connection Manager.
vbroker.se.liop_tp.scm. liop_tp.manager. connectionMax	0	Specifies the maximum number of cache connection on the server. The default value, 0 (zero), implies no restriction.
vbroker.se.liop_tp.scm. liop_tp.manager. connectionMaxIdle	0	Specifies the time in seconds that the server uses to determine if an inactive connection should be closed or not.
vbroker.se.liop_tp.scm. liop_tp.manager. garbageCollectTimer	0	The garbage-collection timer (in seconds) for connections.
vbroker.se.liop_tp.scm. liop_tp.listener.type	LIOP	Specifies the type of protocol the listener is using.
vbroker.se.liop_tp.scm. liop_tp.listener.port	0	Specifies the port number used with the host name property. The default value, 0 (zero), means that the system will pick a random port number.
vbroker.se.liop_tp.scm. liop_tp.listener.proxyPort	0	Specifies the proxy port number used with the proxy host name property. The default value, 0 (zero), means that the system will pick a random port number.
vbroker.se.default.local. listener.door	true	Specifies whether the Door API has to be used for the Client and Server to communicate when running on the same machine. When set to true, the Door API is used for the LIOP. When set to false, the LIOP uses a UNIX Domain Socket for IPC. This property is only for Solaris operating systems.
vbroker.se.default.local. listener.shm	true	Specifies whether shared memory will be used for the Client and Server to communicate when running on the same machine. When set to true, shared memory is used for the LIOP. When set to false, the LIOP uses a UNIX Domain Socket for IPC. This property is for HP-UX, AIX and Linux operating systems.
vbroker.se.liop_tp.scm. liop_tp.listener.shmSize	4096	The size, in bytes, of the shared memory allocation. If your client program and object implementation communicate via shared memory, you may use this option to enhance performance.
vbroker.se.liop_tp.scm. liop_tp.listener. userConstrained	0	When set to true, the file is hidden in a directory accessible only by the owner.
vbroker.se.liop_tp.scm. liop_tp.listener. giopVersion	1.2	This property can be used to resolve interoperability problems with older VisiBroker ORBs, that cannot handle unknown minor GIOP versions correctly. Acceptable values for this property are 1.0, 1.1 and 1.2.
vbroker.se.liop_tp.scm. liop_tp.listener. allowedGroups	null	Allows server applications to control the trustees to the securable synchronization objects, used for Local IPC communication on Windows. Allows semicolon-separated Windows User groups to access servers using LIOP. Users not belonging to the groups specified will not be allowed to connect and will failover to IIOP
vbroker.se.liop_tp.scm. liop_tp.dispatcher.type	ThreadPool	Specifies the type of thread dispatcher used in the Server Connection Manager.
vbroker.se.liop_tp.scm. liop_tp.dispatcher. threadMin	0	Specifies the minimum number of threads that the Server Connection Manager can create.
vbroker.se.liop_tp.scm. liop_tp.dispatcher. threadMax	0	Specifies the maximum number of threads that the Server Connection Manager can create. The default value 0 (zero) implies the ORB will control the thread generation using an internal algorithm based on heuristics.
vbroker.se.liop_tp.scm. liop_tp.dispatcher. threadMaxIdle	300	Specifies the time in seconds before an idle thread will be destroyed.
vbroker.se.liop_tp.scm. liop_tp.dispatcher. threadStackSize	0	The size of the thread stack. The default value 0 indicates the system default. However, on the HP-UX platform, the default value is 128 KB.
vbroker.se.liop_tp.scm. liop_tp.dispatcher. coolingTime	3	Time duration, in seconds, when a connection is considered hot (expecting more requests). After the time is elapsed, the connection is returned back from the dispatcher.
vbroker.se.liop_tm.scm. liop_tm.manager.enabled	true	Set this to false if you are using a Main Thread model with LIOP on a Windows system, to ensure that a request is serviced in that environment.

Server-side thread pool BOA_LTP/BOA_LTP connection properties

This protocol has the same set of properties as the thread pool liop_tp/liop_tp connection properties, but replacing all liop_tp with boa_ltp in all the properties. For example, vbroker.se.liop_tp.scm.liop_tp.manager.connectionMax becomes vbroker.se.boa_ltp.scm.boa_ltp.manager.connectionMax. Also, the default value for vbroker.se.boa_ltp.scms is boa_ltp.

Properties that support bi-directional communication

This table lists the properties that support bidirectional communication. These properties are evaluated only once—when the SCMs are created. In all cases, the exportBiDir and importBiDir properties on the SCMs are given priority over the enableBiDir property. In other words, if both properties are set to conflicting values, the SCM-specific properties will take effect. This allows you to set the enableBiDir property globally and specifically turn off bidirectionality in individual SCMs.

Property	Default	Description
vbroker.orb.enableBiDir	none	You can selectively make bidirectional connections. If the client defines vbroker.orb.enableBiDir=client and the server defines vbroker.orb.enableBiDir=server the value of vbroker.orb.enableBiDir at the GateKeeper determines the state of the connection. Values of this property are: server, client, both or none.
vbroker.se.<se>.scm.<scm>. manager.exportBiDir	By default, not set by the ORB.	A client-side property. Setting it to true enables creation of a bidirectional callback POA on the specified server engine. Setting it to false disables creation of a bidirectional POA on the specified server engine.
vbroker.se.<se>.scm.<scm>. manager.importBiDir	By default, not set by the ORB.	A server-side property. Setting it to true allows the server-side to reuse the connection already established by the client for sending requests to the client. Setting it to false prevents reuse of connections in this fashion.

Debug Logging properties

This section details the properties that can be used to control and configure the output of debug log statements.

The debug log statements are categorized according to the areas of the ORB from where they are logged. These categories are called source names. Currently the following source names are logged:

•	connection – logs from the connection related source areas such as client side connection, server side connection, connection pool etc.

•	client – logs from client side invocation path

•	agent – logs for Osagent communication

•	cdr – logs for GIOP areas

•	se – logs from the server engine, such as dispatcher, listener etc.

•	server – logs from server side invocation path.

•	orb – log outputs from the ORB.

For VisiNotify, the following source names are logged:

•	v_vntfy - logs from the process.

•	v_vnchnl - logs from the channel object.

•	v_vn_pxsup - logs from proxy supplier objects.

•	v_vnper - logs from persistency module.

•	v_vndb - logs from low level circular file based db layer

•	v_vnlogdiscard - Details of any events that are discarded

For VisiTelcoLog, the following source names are logged:

•	v_vtlog - logs from the process.

•	v_vtlper - logs from the log persistence layer.

•	v_vndb - logs from low level circular file based db layer.

For VisiTransact, the following source names are logged:

•	v_ots_txncontext - logs from transaction factory, control and coordinator.

•	v_ots_interceptor - logs from client and server interceptors and transaction current related operations.

•	v_ots_completion - logs related to transaction completion.

•	v_ots_pc - logs related to resource and synchronization objects registered.

For VisiSecure C++, the following source names are logged:

•	v_secauthn - logs from authentication related code (login module, callback handler, identity services and alike).

•	v_secauthz - logs from authorization related code (Authorization provider, Authorization domain, role map and alike).

•	v_secssl - logs from SSL transport related code (SecureSocketProvider, CertificateFactory and alike).

•	v_seccsiv2 - logs from CSIV2 service context protocol related code (Security context management code and alike).

•	v_secmisc - logs from the rest of code.

Enabling and Filtering

The following table describes the properties used to enable logging and filtering.

Property	Default	Description
vbroker.log.enable	false	When set to true, all logging statements will be produced unless it is being filtered. Values are true or false.
vbroker.log.logLevel	debug	Specifies the logging level of the log message. When set at a level, the logs with log levels equal to the specified level or above are forwarded. This property is applied at the global level. Values are emerg, alert, crit, err, warning, notice, info and debug ranking from the highest to the lowest. The meaning of the log levels are: • emerg - indicates some panic condition. • alert - a condition that requires user attention--for example, if security has been disabled. • crit - critical conditions, such as a device error. • err - error conditions. • warning - warning conditions--these may accompany some troubleshooting advice. on the opening of a connection. • info - informational, such as binding in progress. • debug - debug conditions understood by developers.
vbroker.log.default.filter. register	null	Register source name for controlling (filtering) the logs from that source. Values are client, server, connection, cdr, se, agent and orb. Multiple values can be provided as a comma separated string. Note: The source names have to be registered using this property before they can be explicitly controlled using the vbroker.log.filter.default.<source-name>.enable and vbroker.log.filter.default.<source-name>.logLevel properties.
vbroker.log.default.filter. <source-name>.enable	true	Once a source name is registered, logs output from the source can be explicitly controlled using this property. Values are true or false.
vbroker.log.default.filter. all.enable	true	This is a special case of the previous property where an inbuilt source name “all” is being used. “all” here denotes all the source names that have not been registered.
vbroker.log.default.filter. <source-name>.logLevel	debug	This property provides finer-grained control over the global log level property. The log level specified using this property explicitly applies to the given source name. The possible values are similar to the global logLevel values.
vbroker.log. enableSigHandler	false	When set to true, installs a signal handler based on SIGUSR2 to allow toggling of logging at runtime. Values are true or false. Note: This applies only to UNIX platforms.

Appending and Logging

The output of the logs can be appended (forwarded) to either the Console or a rolling local file system file (or both), either in a simple layout or in a more complicated Log4J XML event layout (format). By default the logs are appended to the Console in a simple layout. The names of the various appenders and layouts supported are:

•	stdout – Name of the Console appender.

•	rolling – Name of the rolling file appender.

•	simple – Name of a simple predefined output layout.

•	xml – Name of Log4J XML event layout.

•	full – Name of a full record fields printout layout.

The following table describes the properties used to configure the destination of the log output and its format.

Property	Default	Description
vbroker.log.default. appenders		List of comma-separated appenders for specifying log output destination.
vbroker.log.default. appender. <appender-inst-name>. appenderType	stdout	Type of the appender instance that needs to be configured with the logger. Values can be stdout or rolling or a custom appender type.
vbroker.log.default. appender. <appender-inst-name>. layoutType	simple	Type of layout (format) to be associated with the registered appender destination. Values are simple or xml or a custom layout type.
vbroker.log.default. appender. <appender-inst-name>.async	false	When set to true, the appender will log events asynchronously. This feature is mainly designed to improve logging performance of FileAppender.

Configurations

For the built-in rolling appender type, you can create the following configurations. The properties are described below, assuming that for each appender instance, the appender type is specified as “rolling”.

Property	Default	Description
vbroker.log.default. appender. <appender-inst-name>.logDir	<current_ directory>	Directory for the rolling log file to reside in.
vbroker.log.default. appender. <appender-inst-name>. fileName	vbrolling. log	Name of the rolling log file
vbroker.log.default. appender. <appender-inst-name>. maxFileSize	10	Size in MB for each backup before rolling over. Values >= 1
vbroker.log.default. appender. <appender-inst-name>. maxBackupIndex	1	Number of backups needed. When set to 0 (zero), no backup is created and logging will keep on appending to the file. Values >= 0
vbroker.log.default. appender. <appender-inst-name>.async	true	Asynchronous logging mechanism, When set to false, the appender outputs the message with synchronous manner.

The following properties can be used to define custom appender and layout types.

Property	Default	Description
vbroker.log.appender. register		Comma-separated new appender type names being introduced to the logger framework
vbroker.log.appender. <appender-type-name>. sharedLib		Complete path including file name of the shared library or the DLL containing the custom appender
vbroker.log.layout.register		Comma-separated new layout type names being introduced to the logger framework
vbroker.log.appender. <layout-type-name>. sharedLib		Complete path including file name of the shared library or the DLL containing the custom layout

Examples

The following examples explain some of the debug logging properties' usage scenarios. In the example commands, vbapp is a VisiBroker for C++ application.

1	To turn on logging with default log level.

prompt> vbapp –Dvbroker.log.enable=true

2	To trace only info level and above.

prompt> vbapp –Dvbroker.log.enable=true –Dvbroker.log.logLevel=info

3	To turn off agent related component statements.

prompt> vbapp –Dvbroker.log.enable=true \
–Dvbroker.log.default.filter.register=agent \
–Dvbroker.log.default.filter.agent.enable=false

4	To trace the client and connection related area only.

prompt> vbapp –Dvbroker.log.enable=true \
-Dvbroker.log.default.filter.enable=false \
–Dvbroker.log.default.filter.register=client,connection

5	To trace emerg on se and err on the cdr areas and the rest info level.

prompt> vbapp –Dvbroker.log.enable=true \
-Dvbroker.log.logLevel=info \
–Dvbroker.log.default.filter.register=se,cdr \
–Dvbroker.log.default.filter.se.logLevel=emerg \
–Dvbroker.log.default.filter.cdr.logLevel=err

6	To set up output to local file systems with three backups.

prompt> vbapp –Dvbroker.log.default.appenders=rolling \
-Dvbroker.log.default.appender.rolling.logDir=/opt/vbc \
-Dvbroker.log.default.appender.rolling.fileName=vbc.log \
-Dvbroker.log.default.appender.rolling.maxBackupIndex=3