VisiBroker for Java Developer’s Guide : VisiBroker properties

VisiBroker properties
This section describes the VisiBroker properties.
JAVA RMI over IIOP properties
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.
Specifies the name of the implementation of the Stub base class from which all RMI-IIOP stubs must inherit.
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.
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.
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.
 
vbroker.agent.
clientHandlerPort
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
vbroker.agent.
maxRetries
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.
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.
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.
When set to true, specifies that the system will display debugging information about communication of VisiBroker applications with the Smart Agent.
When set to true, allows VisiBroker applications to cache IOR.
When set to false, does not allow VisiBroker applications to communicate with the Smart Agent.
When set to true, allows a VisiBroker application to fail over to another Smart Agent.
Set to true in order to experience pre-VBJ 8.0 binding behavior.
 
VisiBroker ORB properties
The following table describes the VisiBroker ORB properties.
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)
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.
vbroker.orb.
activationIOR
When set to true, this property enables the use of key IDs in client requests.
vbroker.orb.
enableServerManager
When set to TRUE, this property enables Server Manager when the server is started, so that clients can access it.
vbroker.orb.
keyIdCacheMax
vbroker.orb.
keyIdCacheMin
vbroker.orb.
defaultInitRef
When set to true, specifies that clients must always connect to the server using the GateKeeper.
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
vbroker.orb.
proxyPassthru
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).
When set to true, specifies that clients must always make secure connections to the server.
When set to true, specifies that clients always make http tunnel (IIOP wrapper) connections to the server.
vbroker.orb.
autoLocateStubs
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.
2
3
4
5
6
(The critical bid, specified by the vbroker.orb.bids.critical property, has highest precedence no matter where it is specified in the bid order.)
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.
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
When set to true, this property allows the internal buffer manager to display debugging information.
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.
When set to true, allows the ORB to display debugging information.
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
vbroker.orb.
backCompatAlign
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.
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
If set to TRUE, enables marshaling of null strings.
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
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:
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
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.
tcIndirection
Specifies a value of 0, 1, or 2 which indicates the level of warning messages to be printed.
vbroker.orb.
serverSendTimeout
If the write operation is blocked for more then the serverSendTimeout limit, it will timeout and close the connection.
vbroker.orb.
invalidLicenseExit
If set to false, a CORBA:NO_PERMISSION exception is just thrown and application will not be aborted.
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.
Note: The setting of this property will disable the QoS relative roundtrip and request timeout policies.
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
vbroker.orb.
serverDelayCloseTimeout
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
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
 
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.
Server Manager properties
This table lists the Server Manager properties.
vbroker.serverManager.
enableOperations
When set to true, enables operations, exposed by the Server Manager, to be invoked.
vbroker.serverManager.
enableSetProperty
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
vbroker.se.<SE_name>.scm.<SCM_name>.
manager.inUseConnections
vbroker.se.<SE_name>.scm.<SCM_name>.
manager.idledTimeoutConnections
Properties related to Client-side resource usage
vbroker.ce.<CE_name>.ccm.
idledTimeoutConnections
Properties related to the Smart Agent (osagent)
Location Service properties
The following table lists the Location Service properties.
When set to true, allows the Location Service to display debugging information.
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.
Event Service properties
The following table lists the Event Service properties.
vbroker.events.
maxQueueLength
When set to true, allows the event channel factory to be instantiated, instead of an event channel.
When set to true, allows output of debugging information.
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.
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
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.
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:
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:
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):
vbroker.se.iiop_tp.scm.
iiop_tp.listener.deferAccept
vbroker.se.iiop_tp.scm.ssl.
listener.deferAccept
Properties relating to object clustering
For more information see the Object Clusters section.
vbroker.naming.
enableClusterFailover
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.
If 1, the implicit clustering feature is turned on.
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”.
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
See the related property, vbroker.naming.serverAddresses.
vbroker.naming.
serverAddresses
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.
anyServiceOrder
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:
Pluggable Backing Store Properties
The following tables show property information for the VisiNaming service pluggable backing store types.
Default properties common to all adapters
vbroker.naming.
backingStoreType
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:
See “Caching facility” for details about enabling the caching facility and setting the appropriate properties.
0 (no limit)
JDBC Adapter properties
vbroker.naming.
jdbcDriver
interbase.interclient.Driver—Interbase driver
weblogic.jdbc.mssqlserver4.Driver—WebLogic MS SQLServer Driver
vbroker.naming.
resolveAutoCommit
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.
jdbc:db2:<db-name>—IBM DB2 URL
<full-path-JDataStore-db>—DataExpress URL for the native driver
vbroker.naming.
minReconInterval
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:
JNDI adapter properties
The following is an example of settings that can appear in the configuration file for a JNDI adapter:
VisiNaming Service Security-related properties
ServerQoPPolicy.SECURE_ONLY=1
ServerQoPPolicy.CLEAR_ONLY=0
ServerQoPPolicy.ALL=3
vbroker.naming.security.
requireAuthentication
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
vbroker.naming.security.
requiredRolesFile
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.
vbroker.oad.
spawnTimeOut
vbroker.oad.
killOnUnregister
vbroker.oad.
verifyRegistration
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.
Interface Repository properties
The following table lists the Interface Repository (IR) properties.
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.
Client-side IIOP connection properties
The table below lists the VisiBroker for Java Client-side IIOP Connection properties.
vbroker.ce.iiop.ccm.
connectionMaxIdle
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
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.
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.
0 (random port)
vbroker.ce.iiop.
clientPortRange
URL Naming properties
This table lists the URL Naming properties.
vbroker.URLNaming.
allowUserInteraction
When set to true, allows the URL Naming Service to initiate the graphical user interface (GUI) for user interaction.
When set to true, specifies that the URLNaming Service display debugging information.
QoS-related Properties
 
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.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.
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
Server-side server engine properties
This table lists the server-side server engine properties.
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.
One possible value for security would be ssl. See the VisiBroker Security Guide for details.
vbroker.se.iiop_ts.scm.iiop_ts.
manager.connectionMax
vbroker.se.iiop_ts.scm.iiop_ts.
manager.connectionMaxIdle
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.
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.
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.
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.
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.
One possible value for security would be ssl. See the VisiBroker Security Guide for details.
vbroker.se.iiop_tp.scm.
iiop_tp.manager.type
vbroker.se.iiop_tp.scm.
iiop_tp.manager.connectionMax
vbroker.se.iiop_tp.scm.
iiop_tp.manager.
connectionMaxIdle
vbroker.se.iiop_tp.scm.
iiop_tp.listener.type
vbroker.se.iiop_tp.scm.
iiop_tp.listener.port
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
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
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
vbroker.se.iiop_tp.scm.
iiop_tp.dispatcher.threadMin
vbroker.se.iiop_tp.scm.
iiop_tp.dispatcher.threadMax
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
vbroker.se.iiop_tp.scm.
iiop_tp.connection.
tcpNoDelay
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
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.
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.
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:
Enabling and filtering
The following table describes the properties used to enable logging and filtering.
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
vbroker.log.default.filter.
<source-name>.logLevel
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.
vbroker.log.default.appender.
appender-inst-name>.layoutType
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.
vbroker.log.default.appender.
rolling.maxBackupIndex
Deprecated properties
The following properties are deprecated at version 8.5.
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.
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.
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.
vbroker.se.ws.scm.ws_ts.
manager.connectionMax
vbroker.se.ws.scm.ws_ts.
manager.connectionMaxIdle
vbroker.se.ws.scm.ws_ts.
connection.keepAlive
SOAP Request Dispatcher properties
This table lists the SOAP Request Dispatcher properties.
vbroker.se.ws.scm.ws_ts.
dispatcher.threadMax
vbroker.se.ws.scm.ws_ts.
dispatcher.threadMin
vbroker.se.ws.scm.ws_ts.
dispatcher.threadMaxIdle
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.