Last updated: September 29, 2008
This document contains updates to the VisiBroker 8.0 documentation issues.
For the latest version of this document, go to the Borland Documentation Web site at http://techpubs.borland.com/am/visibroker/v80/.
Starting from VisiBroker 8.0, Borland no longer supports network type licenses. Therefore, in Section "Using the License Manager" of vb_Overview.pdf (Overview), all reference to "network license" should be ignored.
Ignore the following paragraph in Chapter 2, Using the License Manager on page 7.
There are two types of Borland VisiBroker licenses:–
In VisiBroker for Java Guide, the following argument option has been missed out under "VBJ" section in "Programmer Tools for Java"
Passes the property name and value pair into the Java Virtual Machine as a System Property by adding it as a
In VisiBroker for Java Developer guides, reference to Corba 2.6 is incorrect.
All CORBA 2.6 reference needs to be changed to CORBA 3.0 with exception clause "excluding CCM and GIOP 1.3" under section Understanding the CORBA model and VisiBroker CORBA compliance in VisiBroker for Java Developer guide.
Some of these properties listed below in the table have been missed out in the VisiBroker Guides and the Release Notes. Yet some have not been updated in VisiBroker 8.0 documentation.
||300 secs||Smart agent will wake up after this timeout and based on the vbroker.agent.threshold value, will compute whether to do other osagents verification. The logic is if the last received heart beat value is less than current time - (timer + threshold), then do osagents verification. The value of this property should be greater than 1 second and less than 300 seconds.
||40 secs||Please see documentation for vbroker.agent.timer. This value should be greater than 0.|
||0|| 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 |
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 requests are 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.
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. This property only applies to VisiBroker for Java product.
||false||If this property is set to true, and if the IOR has both IIOP and TCP type Firewall components, then if any one of the end points fail, fail-over can occur.
||true||If true, any thread calling
This property is applicable in both VisiBroker for C++ and Java developer's guide. 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
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.
||false||In VisiBroker for C++, setting this property to true will allow the thread pool dispatcher to create an unlimited number of threads when the property
||false|| Causes the Naming Service to discard incoming requests while its 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 behaviour.
This property only works when:
||true||Sets Auto Commit on the JDBC connection when doing a "resolve" operation.
When this property is set to "false", the resolve operation will use the same "transaction" pattern as that is used in other similar methods like bind, rebind and etc. If set it to "true", there will be better performance for the "resolve" operation.
For VisiNaming using JDS HA failover configuration, set this property to "false".
This property is found in VisiBroker 6.5 release notes but has not been updated in VisiBroker 8.0 Security Guide:
||n/a||This is used to specify the location of Certificate Rovocation List (CRL).|
In the VisiSecure Guide, under the chapter 'VisSecure for C++ APIs', under the section 'General API', 'class vbsec::Current' the sentence "Some calls are relevant only in an request execution context." is incorrect. The sentence should read as ""All the calls are relevant only in the context of a method invocation." See the updated API document on com.borland.security, Interface 'Current'.
In the VisiBroker for .Net Developer's Guide, under chapter ' Building and deploying VisiBroker for .NET applications', under section 'Deploying VisiBroker for .NET applications' under VisiBroker for .NET deployment license key, it states that the VisiBroker for .NET license key is on the VisiBroker deployment CD-ROM in the License Directory. But, for VisiBroker for .NET 8.0, it is not possible to get the client.slip file directly from the CD. Instead the client.slip file is written as part of the installation, therefore, go to <visi-install-dir>\VisiNet\client.slip to copy the license file.
In the VisiBroker for .Net Developer's Guide, under chapter ' Building and deploying VisiBroker for .NET applications', under section ' Deploying VisiBroker for .NET applications' under VisiBroker for .NET runtime libraries, it states that:
| For deployment, VisiBroker for .NET supports client applications on the front end or ASP.NET server applications. You must install the following VisiBroker for .NET runtime libraries on each machine that runs the VisiBroker for .NET-powered applications:
Borland.Janeva.NTD.dll is no longer in use and therefore has to be ignored.
This issue has not been documented previously. Therefore we recommend you to note that prior to VisiBroker for .Net 7.0, J# reflection was used to instantiate the class type. In version 7.0 onwards, VisiBroker for .NET runtime is now independent from either Microsoft J# or the SUN JDK. It is now completely in .NET MSIL. Therefore, the default access control for class default constructor may not work as before. If class SampleServerLoader is not explicitly declared using the keyword "public" in order for .NET runtime to access, then an exception is raised and you cannot possibly access the default constructor.
Currently, the VisiBroker for .Net Developer's Guide and ReadMe for VisiNet still uses the Janeva 6.5. Janeva has been renamed as "VisiNet". As VisiNet doesn't depend on Visual J #.net, all the related part must be ignored.
VisiBroker for .NET is a .NET product. As such, it requires the .NET Framework for execution, which is available as a free download from Microsoft. For the .net framework support, VisiNet supports Microsoft .NET Framework 3.0
There is a documentation error with regard to osagent max log size.
In the VisiBroker C++ and VBJ Developer's Guide, under the Chapter ' Using the Smart Agent' under the section 'Starting a Smart Agent (osagent)', The max value for Osagent is documented as 300M. However, the actual value is 512 MB.
C++ API Reference Guide needs the following below to be added in the ORB methods under the section 'ORB' under ' Core interfaces and Classes'.
void register_initial_references (const char * identifier, CORBA::Object_ptr obj);
|Identifier||The name of the service by which the initial reference will be known.|
|obj||Non-null object reference|
For technical support, contact the Borland Support Center at http://support.borland.com/. Before contacting support, you may want to consult the Borland Support Center Borland Answers at http://support.borland.com/kb.php