VisiBroker properties

This section describes the VisiBroker properties.

JAVA RMI over IIOP properties

Property	Default	Description
vbroker.rmi.supportRTSC	false	This property enables or disables the exchange of SendingContextRuntime service contexts between clients and servers when the two are using different (evolved) versions of a class. If the client and server are on different versions of a JDK, the application should make sure that this property is set to true. This value should also be used for cases where VBJ is talking to a foreign ORB. This ensures that the codebase data is exchanged and marshaling/demarshaling of evolved classes can succeed without exceptions.
javax.rmi.CORBA.StubClass	com.inprise.vbroker.rmi.CORBA.StubImpl	Specifies the name of the implementation of the Stub base class from which all RMI-IIOP stubs must inherit.
javax.rmi.CORBA.UtilClass	com.inprise.vbroker.rmi.CORBA.UtilImpl	Specifies the name of the implementation of the Utility class that provides methods that can be used by stubs and ties to perform common operations.
javax.rmi.CORBA. PortableRemoteObjectClass	com.inprise.vbroker.rmi.CORBA.PortableRemoteObjectImpl	Specifies that the RMI-IIOP server implementation objects may inherit from javax.rmi.PortableRemoteObject or simply implement an RMI-IIOP remote interface and then use the exportObject method to register themselves as a server object.
java.rmi.server.codebase	<not set>	Specifies where a server can locate unknown classes. Acceptable value is semicolon (;)-separated URLs.
java.rmi.server. useCodebaseOnly	false	Specifies if a server is allowed to locate unknown classes. If set to true, does not allow the server to locate remote classes even if the client sends the location of the remote classes to the server.

Smart Agent properties

The properties in this table are used by the Smart Agent.

 

Property	Default	Old property	Description
vbroker.agent. addrFile	null	ORBagentAddrFile	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	Refer to documentation on 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.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. 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. timer	300 seconds	N/A	Smart agent will wake up after this 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	ORBagentAddr	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	ORBagentAddrFile	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. enableCache	true	ORBagentCache	When set to true, allows VisiBroker applications to cache IOR.
vbroker.agent. enableLocator	true	ORBdisableLocator	When set to false, does not allow VisiBroker applications to communicate with the Smart Agent.
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. failOver	true	ORBagentNoFail Over	When set to true, allows a VisiBroker application to fail over to another Smart Agent.
vbroker.agent. clientPort	0 (zero)	N/A	Lower bound of the range of ports for the ORB to communicate with the OSAgent. Valid values are between 0 to 65535. Default value of 0 (zero) means that a random port will be selected.
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.agent. backcompatBind	false	N/A	When set to false, the client ORB will use the hostname parameter passed in from the bind() method when binding to the server. When set to true, it will use the corresponding hostname's IP address when binding to the server. Set to true in order to experience pre-VBJ 8.0 binding behavior.

 

VisiBroker ORB properties

The following table describes the VisiBroker ORB properties.

Property	Default	Description
vbroker.orb.propOrdering	CMD_PROPS:SYS_PROPS:FILE_PROPS:ORB_PROPS:DEF_PROPS	This property allows the user to override the default precedence of properties set by the ORB's Property Manager. The default precedence from highest to lowest is: 1 CMD_PROPS: command-line arguments (specified through the first argument of orb.init() call. 2 SYS_PROPS: system or JVM properties, including properties specified through ‑VBJprop, -J, and so forth. 3 FILE_PROPS: properties in the file specified by ORBpropStorage property. 4 ORB_PROPS: properties set through the second argument of the orb.init() call. 5 DEF_PROPS: default ORB properties.
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.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.enableKeyId	false	When set to true, this property enables the use of key IDs in client requests.
vbroker.orb. enableServerManager	FALSE	When set to TRUE, this property enables Server Manager when the server is started, so that clients can access it.
vbroker.orb. keyIdCacheMax	16384	Specifies maximum size of the object key ID cache in a server.
vbroker.orb. keyIdCacheMin	64	Specifies minimum size of the object key ID cache in a server.
vbroker.orb.initRef	null	Specifies the initial reference.
vbroker.orb. defaultInitRef	null	Specifies the default initial reference.
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 connect to the server through the GateKeeper whose IOR is provided.
vbroker.locator.ior	null	Specifies the IOR of the GateKeeper that will be used as proxy to the 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, see 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.alwaysSecure	false	When set to true, specifies that clients must always make secure connections to the server.
vbroker.orb.alwaysTunnel	false	When set to true, specifies that clients always make http tunnel (IIOP wrapper) connections to the server.
vbroker.orb. autoLocateStubs	false	Turns on the ability to locate stubs when reading object references. This is done using read_Object, based on the object's repository id instead of either the generic object or the stubs for passed formal class argument.
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.bids.bar	n/a	This property is used to prevent specified bidders from placing bids. For example, setting it to inprocess will disable inprocess bidding. This can be useful in cases when optimized co-located invocations are not required. Only inprocess bidders can be barred.
vbroker.orb.defAddrMode	0 (Key)	The default addressing mode that client VisiBroker ORB uses. If it is set to 0, the addressing mode is Key, if set to 1, the addressing mode is Profile, if set to 2, the addressing mode is IOR.
vbroker.orb. bufferCacheTimeout	60	Specifies the time, in seconds, for which a message chunk is cached before it is discarded.
vbroker.orb.bufferDebug	false	When set to true, this property allows the internal buffer manager to display debugging information.
vbroker.orb.corbaloc. resolveHosts	false	When this property is set to true the ORB will try to resolve the hostnames specified in the corbaloc URL. When false no address resolution will take place.
vbroker.orb.debug	false	When set to true, allows the ORB to display debugging information.
vbroker.orb.dynamicLibs	null	Specifies a list of available services used by the VisiBroker ORB. Each service is separated by a comma.
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. backCompatAlign	false	Use this property when the IDL contains a longlong as a parameter or as a return value. To be backward-compatible with VisiBroker 4.1.1 or earlier versions, set this property to true.
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. For more information, see “Properties that support bi-directional communication” and also Callback with GateKeeper's bidirectional support in the VisiBroker GateKeeper Guide.
vbroker.orb. enableNullString	false	If set to TRUE, enables marshaling of null strings.
vbroker.orb.fragmentSize	0 (zero)	Specifies the GIOP message fragment size. It must be a multiple of GIOP message chunk size (vbroker.orb. streamChunkSize). Assigning a 0 (zero) to this property will eventually turn off fragmentation.
vbroker.orb. streamChunkSize	4096	Specifies the GIOP message chunk size. It must be a power of 2.
vbroker.orb.gcTimeout	30	Specifies the time in seconds that must pass before important resources that are not used are cleared.
vbroker.orb.logger. appName	VBJ-Application	Specifies the application name that appears in the log.
vbroker.orb.logger. catalog	com.inprise.vbroker.Logging.ORBMsgs	Specifies the message catalog of messages used by the ORB when logging is enabled.
vbroker.orb.logger. output	stdout	Specifies the output of the logger. It can be the standard output or a file name.
vbroker.orb.logLevel	emerg	Note: This property is deprecated. See “Debug Logging Properties” for recommended properties to use in its place. Specifies the logging level of message that will be logged. The default value, emerg, means that the system logs messages when the system is unusable, or in a panic condition. 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.orb.sendLocate	false	This property takes one of the following values: true, false, onbind, or always. When set to true, it forces the system to send a locate request before making invocations on an IIOP 1.2 target. When set to onbind, causes a locate request message to be sent when a connection is opened for the purpose of gauging if the peer is GIOP aware. The value always instructs the ORB to perform both tasks-sending the locate request before invocations and upon opening the connection.
vbroker.orb. shutdownTimeout	0 (zero)	Allows an application to set a timeout for the ORB.shudown operation in seconds. This property is useful in cases when ORB.shutdown does not finish for a long time. The process will get terminated if the shutdown does not finish and the timeout expires. The default value of 0 (zero) means that process will never get terminated.
vbroker.orb.systemLibs. applet	com.inprise.vbroker.    IIOP.Init, com.inprise.vbroker.    LIOP.Init, com.inprise.vbroker.qos    .Init, com.inprise.vbroker.    URLNaming.Init, com.inprise.vbroker.    HIOP.Init, com.inprise.vbroker.    firewall.Init, com.inprise.vbroker.    dynamic.Init, com.inprise.vbroker.    naming.Init, com.inprise.vbroker.IOP   .Init, com.inprise.vbroker.    CONV_FRAME.Init, com.inprise.vbroker.    rmi.CORBA.Init, com.inprise.vbroker.    PortableInterceptor.Init, com.borland.vbroker.    notify.Init, com.borland.vbroker.    CosTime.Init	Provides a list of system libraries loaded in applet.
vbroker.orb.systemLibs. application	com.inprise.vbroker.    IIOP.Init, com.inprise.vbroker.    LIOP.Init, com.inprise.vbroker.qos    .Init, com.inprise.vbroker.ds.    Init, com.inprise.vbroker.    URLNaming.Init, com.inprise.vbroker.    dynamic.Init, com.inprise.vbroker.ir.    Init, com.inprise.vbroker.    naming.Init, com.inprise.vbroker.    ServerManager.Init, com.inprise.vbroker.IOP    .Init, com.inprise.vbroker.    CONV_FRAME.Init, com.inprise.vbroker.rmi    .CORBA.Init, com.inprise.vbroker.    PortableInterceptor.    Init, com.borland.vbroker.    notify.Init, com.borland.vbroker.    CosTime.Init	Provides a list of system libraries loaded in application.
vbroker.orb. tcIndirection	true	Specifies that indirection be turned off when writing the typecodes. May be necessary when interoperating with ORBs from other vendors. When set to false, it is not possible to marshal recursive typecodes.
vbroker.orb.warn	0	Specifies a value of 0, 1, or 2 which indicates the level of warning messages to be printed.
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. True is the default value.
vbroker.orb.ncsc	none	If set to UTF8, the ORB will use UTF-8 as the native code set for the IDL char type, instead of ISO-LATIN-1. If the property is omitted then ISO-LATIN-1 will be used as the native code set.
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. invalidLicenseExit	true	By default, when a license check fails in an application, the application will be aborted. If set to false, a CORBA:NO_PERMISSION exception is just thrown and application will not be aborted. This property is useful when using the ORB inside a WebLogic Server process. When the license check fails, the WebLogic process will not be aborted.
vbroker.orb.tcpTimeout	0	Note: This property is deprecated due to the limitation of the design that set the value at the socket read level. It is not compliant to OMG CORBA Messaging specification. For more information, refer to the QoS relative roundtrip and request properties or policies which are well implemented and more accurate. The default zero means no timeout is enabled. This property will associate a timeout with all socket-read at the client-side ORB. The specified timeout value is in milliseconds that is passed to set SoTimeout() in java.net.Socket. Note: The setting of this property will disable the QoS relative roundtrip and request timeout policies. This property is an ORB level property, so there is no way to obtain object level or thread level granularity unlike the QoS policies. If more than one CORBA request is sent to the same connection by multiple threads concurrently, the actual time spent in reading data from socket may be greater than the timeout value set per invocation.
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. serverDelayClose	false	By default, the Server ORB closes the socket immediately after sending the CloseConnection message to the client. When this property is set to true, the Server will continue to read data from the socket after sending the CloseConnection message until the Client closes its socket. Only then will the Server close its socket. Note that all requests received after the CloseConnection message is sent will be discarded.
vbroker.orb. serverDelayCloseTimeout	30	If vbroker.orb.serverDelayClose =true is set and the Client does not respond to the CloseConnection message, the Server can set this property to limit the time the Server waits for the Client to close its socket. This can prevent the Server from hogging socket resources due to unresponsive clients. The value is in seconds and the default value is 30.
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. This property is only applicable if NIO Socket is configured at the server-side. See “vbroker.orb.serverRecv TimeoutDisconnects” for controlling whether this timeout is observed.
vbroker.orb.serverRecv TimeoutDisconnects	true	Gives users the option whether or not to disconnect a client when an NIO connection times out because it has exceeded the value of vbroker.orb.serverRecvTimeout. If this property is set to true, the client's connection will be closed if it times out. This is the default if the property is not explicitly set and matches the behavior of the SSL NIO SCM. If set to false, the connection server thread will unblock after the timeout, allowing other waiting server threads to be served from the selector pool. After some time it may then attempt to read the remainder of the message from the client's connection again, when again it may hold a selector for up to serverRecvTimeout during the attempt.
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 be: vbroker.orb.tagAlternateIIOPAddress=myhost.domain.com:54321,[fe80::20c:29ff:fe58:ce28]:23232,127.0.0.1:65000
vbroker.orb. cdrMaxInputBufferSize	0	Specifies the maximum allowed CDR input buffer size. A value greater than zero defines the upper size of the CDR input buffer on the server. If the CDR input buffer size is greater than the specified property value, the server will throw a CORBA.MARSHAL exception and discard the CDR message. If an invalid value is specified (less than zero), the server will throw a CORBA.BAD_PARAM and exit. If no value is specified, or if you specify a value of zero for the property, the previous behavior is preserved. Be cautious when choosing a value for this property. Setting it too small can result in the ORB rejecting important messages because of Out of Memory exceptions during CDR unmarshaling of arguments.
vbroker.orb. enableUTF16Surrogates	false	Manages the use of wide character sequence and wide strings that contain UTF-16 surrogate pair code points. Such code point values fall between '\uD800' and '\uDFFF'. If you set this property to true, the wstring and sequence<wchar> types may now contain characters that straddle two adjacent wchar (Java char) values. If you wish to retain the ORB’s previous behavior, in which wchar values in the affected range caused an org.omg.CORBA.DATA_CONVERSION exception, leave this property set to the default false.

POA properties

 

Property	Default	Description
vbroker.poa.manager. threadMin	0	Controls the minimum number of threads in the auxiliary thread pool used in POA (for instance, for etherealization of objects).
vbroker.poa.manager. threadMax	0	Controls the maximum number of threads in the auxiliary thread pool used in POA.
vbroker.poa.manager. threadMaxIdle	300	Controls the idle timeout for threads in the auxiliary thread pool used in POA.
vbroker.poa.logLevel	emerg	Note: This property is deprecated. See “Debug Logging Properties” for recommended properties to use in its place. Specifies the logging level of messages to be logged. The default value, emerg, means that messages are logged when the system is unusable or during a panic condition. 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.

Server Manager 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 the run-time state of the Server which can be queried through the Server Manager's container. These are all read-only.

Properties related to Server-side resource usage

Property	Description
vbroker.se.<SE_name>.scm.<SCM_name>. manager.inUseConnections	The number of incoming connections for which there are requests executing in the ORB.
vbroker.se.<SE_name>.scm.<SCM_name>. manager.idleConnections	The number of incoming connections for which there are no requests currently being executed in the ORB.
vbroker.se.<SE_name>.scm.<SCM_name>. manager.idledTimeoutConnections	The number of connections which have been idle 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	The number of threads currently executing requests within the dispatcher.
vbroker.se.<SE_name>.scm.<SCM_name>. dispatcher.idleThreads	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.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.

Location Service properties

The following 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.
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

The following 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 the “VisiNaming Service Clusters for Failover and Load Balancing” section for information about configuring master/slave naming services.
vbroker.naming. factoryIorFile	N/A	When this property is specified with a value specifying a file name, the Naming Service will store the IOR of context factory in that file. The IOR file can then be used by the nsutil utility to shutdown the Naming Service remotely.
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.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 the Object Clusters section.

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 “VisiNaming Service Clusters for Failover and Load Balancing”.

Property	Default	Description
vbroker.naming.enableSlave	0	See “VisiNaming Service properties”.
vbroker.naming.slaveMode	No default. Can be set to: cluster or slave.	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. 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: vbj -Dvbroker.naming.anyServiceOrder=true Client

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 used in other similar methods such as bind, rebind and so on. If it is set 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 Naming Service's database reconnection interval time, in seconds. The default value is 30. The Naming Service will ignore the reconnection 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 the Naming Service will use. 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. However, when the vbroker.naming.security.disable property is set to true, no client authentication will be performed regardless of the value of this requireAuthentication property.
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 following table lists the configurable Object Activation Daemon (OAD) properties. See “Using the Object Activation Daemon (OAD)” for details about using the OAD.

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 server processes, once they are unregistered.
vbroker.oad. verifyRegistration	false	Specifies whether to verify the object registration.
vbroker.oad.locateAlways	false	This property is used as an environment setting when registering a Visibroker Java server with the oadutil command. Set this property to true, so that the client can locate the VisiBroker server that is started by OAD. See “Registering objects with oadutil” for details.

This table list 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.
vbroker.oad.vbj	vbj	Specifies the VisiBroker for Java directory.

Interface Repository properties

The following 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.

Client-side IIOP connection properties

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

Property	Default	Description
vbroker.ce.iiop.ccm. connectionMax	0	Specifies the maximum number of total connections for a client. This is equal to the number of active connections plus cached connections. The default value of zero specifies that the client will 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 the connection.
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.ccm. waitForCompletion	false	This property can be set to true to specify that the application wants to wait for all replies to be received and only after then should the ORB should close the connection. The default value of false indicates that ORB will not wait for any replies.
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.clientPort	0 (random port)	Specifies the client port to be used when a connection is opened by the ORB. Allowed values range from 0 to 65535. 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.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.

URL Naming properties

This table lists the URL Naming properties.

Property	Default	Description
vbroker.URLNaming. allowUserInteraction	true	When set to true, allows the URL Naming Service to initiate the graphical user interface (GUI) for user interaction.
vbroker.URLNaming.debug	false	When set to true, specifies that the URLNaming Service display debugging information.

QoS-related Properties

 

Property	Default	Description
vbroker.orb.qos.relativeRTT	0	This property can be used to set the RelativeRoundtripTimeoutPolicy in milliseconds. It takes effect at the ORB level and can be overridden programatically at other levels. The default value of 0 means no timeout.
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.orb.qos. connectionTimeout	0 (no limit)	This property allows the convenience of setting the RelativeConnectionTimeoutPolicy QoS policy at the ORB level, without requiring explicit code to be written. The connection timeout value should be specified in milliseconds.
vbroker.qos.backcompat	False	The default value of false exhibits the current VB_NOTIFY_REBIND behavior described in “Using Quality of Service (QoS)”. A value of true reverts to the behavior of VB_NOTIFY_REBIND in VisiBroker version 6.5.
vbroker.orb. socketTimeoutMonitorPeriod	0	Set this property to start a thread which periodically monitors the socket write and connect timeout. The property value (in milliseconds) controls the period. The default value of 0 means that the monitoring thread is not started. Note that this feature is effective only when vbroker.orb.tcpTimeout is set. This timeout mechanism does not need a thread per connection to enforce invocation timeout, but the actual timeout may occur after tcpTimeout + SocketTimeoutMonitorPeriod.

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.

Server-side thread session IIOP_TS/IIOP_TS connection properties

The following 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.
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.port	0	Specifies the port number that is used with the host name property. The default value, 0 (zero), specifies that 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), specifies that the system will pick a random port number.
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. connection.keepAlive	false	Set this property to true to enable TCP KeepAlive option.

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

The following 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 connections 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.
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.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.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.
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.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.se.iiop_tp.scm. iiop_tp.connection.keepAlive	false	Set this property to true to enable TCP KeepAlive option.
vbroker.se.iiop_tp.scm. iiop_tp.listener. useSelectorPool	false	This property modifies the behavior of Java servers configured with the property vbroker.se. iiop_tp.scm.iiop_tp.manager.type=Socket_nio. (See “High scalability configuration for VisiBroker for Java (using Java NIO)” for details of that property.) If this property is set to true, each IIOP (non-SSL) NIO Listener in the server will be constrained to consume a maximum of vbroker.se.iiop_tp .scm.iiop_tp.listener.selectorMax instances of java.nio.channels.Selector at any given time. Note that setting this new property may cause threads to wait for a pooled Selector, so potential impact on performance should be carefully considered and profiled before setting the property. If this new property is not set, or is set to false, the number of Selectors in use continues to be as described in “High scalability configuration for VisiBroker for Java (using Java NIO)”.
vbroker.se.iiop_tp.scm. iiop_tp.listener.selectorMax	20	Maximum number of NIO Selectors that can be created in the NIO Selector Pool. Increasing this value may improve the throughput in cases of very high concurrent invocations. This property is only applicable if vbroker.se. iiop_tp.scm.iiop_tp.listener.useSelectorPool is set to true.

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”, by replacing all iiop_tp with boa_tp in all the properties. For example, the vbroker.se.iiop_tp.scm.iiop_tp.manager.connectionMax will become vbroker.se.boa_tp.scm.boa_tp.manager.connectionMax. Also, the default value for vbroker.se.boa_tp.scms is boa_tp.

Properties that support bi-directional communication

The following table lists the properties that support bi-directional 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 bi-directional communication in individual SCMs.

Property	Default	Description
vbroker.orb.enableBiDir	none	You can selectively make bi-directional 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, this property is not set by the ORB. This is a client-side property. Setting it to true enables creation of a bi-directional 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, this property is not set by the ORB. This is 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.

VisiBroker for Java internally uses Log4J infrastructure for logging.

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 the 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 the server side invocation path

•	orb: logs from the ORB

•	naming: logs from Naming Service

•	gatekeeper: logs from Gatekeeper

•	time: logs from Time Service

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 the log is being filtered. Values are true or false.
vbroker.log.async	false	When set to true, the logger switches to asynchronous mode. This feature is mainly designed to improve logging performance of FileAppender. After the logger retrieves an event from the pool, it will construct a message with logging information created with predefined layout, pushed to message queues, and return immediately to avoid IO blocking which will increase the performance of main thread. Another pool of threads consistently listens to these queues and writes to a configured file destination.
vbroker.log.logLevel	debug	Specifies the logging level of the log message. 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 a 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. • notice - conditions that are not errors but may require some attention. • info - informational, such as binding in progress. • debug - debug conditions used 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 must be registered using this property before they can be explicitly controlled using vbroker.log.default.filter.<source-name>.enable and vbroker.log.default.filter.<source-name>.logLevel properties.
vbroker.log.default.filter. <source-name>.enable	true	Once a source name is registered, log output from the source can be explicitly controlled using this property. Values are true or false.
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.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.

Appending and logging

The output of the logs can be appended to specific destinations and formatted using specific layouts. VisiBroker for Java uses the appenders and layouts provided by Log4J for these purposes. Two inbuilt appenders “stdout” and “rolling” implement console and rolling file implementation. Apart from the various layouts available with Log4J, two inbuilt layouts “simple” and “xml” provide good layout capabilities.

stdout – Name of the Console appender type.

rolling – Name of the rolling file appender type.

simple – Name of a simple predefined output layout type.

xml – Name of Log4J XML event layout type.

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	stdout	List of comma-separated appenders for specifying log output destination.Values are stdout, rolling and/or any user-specified appender name. User can further specify the appenders using: log4j.appender.<name>=<full class name in log4j>
vbroker.log.default.appender. appender-inst-name>.layoutType	PatternLayout	Type of layout (format) to be associated with the registered appender destination. Values are PatternLayout, simple, xml and/or the full class name of all the Log4J supported layouts.

For the built-in rolling appender type, you can create the following configurations.

Property	Default	Description
vbroker.log.default.appender. rolling.logDir	<current_directory>	Directory for the rolling log file to reside in.
vbroker.log.default.appender. rolling.fileName	vbrolling.log	Name of rolling log file.
vbroker.log.default.appender. rolling.maxFileSize	10	Size in MB for each backup before rolling over. Values >= 1.
vbroker.log.default.appender. rolling.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.

Deprecated properties

The following properties are deprecated at version 8.5.

Deprecated Property	Recommended Property
vbroker.orb.debug	vbroker.log.enable
vbroker.orb.logLevel	vbroker.log.logLevel
vbroker.agent.debug	vbroker.log.default.filter.agent.enable
vbroker.locationservice.debug	vbroker.log.default.filter.agent.enable
vbroker.poa.logLevel	vbroker.log.default.filter.server.logLevel
vbroker.gatekeeper.passthru.logLevel	vbroker.log.default.filter.gatekeeper.logLevel
vbroker.orb.logger.output	vbroker.log.default.appenders

Setting properties in an applet

Setting properties for applets can only be done in the applet parameters. For example:

<APPLET archive="vbjorb.jar, vbsec.jar" CODE="ClientApplet.class">

<PARAM NAME="org.omg.CORBA.ORBClass" VALUE="com.inprise.vbroker.orb.ORB">

<PARAM NAME="vbroker.orb.alwaysTunnel" VALUE="true">

</APPLET>

Note:

VisiBroker 3.x-style command-line options cannot be used as applet parameters.

Web services run-time properties

Using the properties listed, you can enable the run time.

Property	Default	Description
vbroker.ws.enable	false	Takes in a Boolean true or false parameter. Setting this value to true will enable the VisiBroker Web Services Runtime.

Web services HTTP Listener properties

To configure the HTTP Listener, use the properties listed in the following table.

Property	Default	Description
vbroker.se.ws.Host	null	Specifies the host name to be used by the listener.
vbroker.se.ws.proxyHost	null	Specifies the proxy host name used by the web services engine. Default value null means use the host name from the system.
vbroker.se.ws.scm.ws_ts.listener.port	80	Specifies the port number to be used by the listener socket.
vbroker.se.ws.scm.ws_ts.listener.type	WS	Specifies the protocol the listener is using. A value of WS-HIOPS will start a secure (https-based) listener.

Web services Connection Manager properties

Using the properties listed below, you can configure the Web services Connection Manager.

Property	Default	Description
vbroker.se.ws.scm.ws_ts. manager.connectionMax	0	If keepAliveConnection is true, this property specifies the maximum number of connections the server will accept. Default 0 indicates no restriction.
vbroker.se.ws.scm.ws_ts. manager.connectionMaxIdle	0	This property determines the maximum time an unused connection will remain alive
vbroker.se.ws.scm.ws_ts. manager.type	Socket	Specifies the type of Server Connection Manager
vbroker.se.ws.scm.ws_ts. connection.keepAlive	false	Set this property to true to enable TCP KeepAlive option.

SOAP Request Dispatcher properties

This table lists the SOAP Request Dispatcher properties.

Property	Default	Description
vbroker.se.ws.scm.ws_ts. dispatcher.threadMax	0	Maximum number of threads to be present in the thread pool dispatcher. Default value 0 indicates unlimited number of threads.
vbroker.se.ws.scm.ws_ts. dispatcher.threadMin	0	Minimum number of threads to be present in the thread pool dispatcher.
vbroker.se.ws.scm.ws_ts. dispatcher.threadMaxIdle	300	Time in seconds before an idle thread in the thread pool is destroyed.
vbroker.se.ws.scm.ws_ts. dispatcher.type	Thread Session	Specifies the type of thread dispatcher used in the Server Connection Manager.

Getting the ORB version programmatically

When using VisiBroker for Java, you can obtain the ORB version string by calling the getVersion method on the com.inprise.vbroker.orb.ORB class, as shown in the following example:

String orbVersion = com.inprise.vbroker.orb.ORB.getVersion();

The version string appears in the format shown the following example:

....VisiBroker for Java [08.05.xx.xx]

Note:

This method is static, so calling it does not require initializing the ORB.