Problem: Product Name: VisiBroker for C++ Product Version: 5.2.1 & 6.5 Product Component: ORB Platform: All In situations like when the Client needs to access multiple Servers running in local network and behind firewall, it is found that VBC Client strictly bid for Firewall profile and never attempt to bid for IIOP profile. This will result in the client not able to access local Server. The behavior is consistent with whether the Client started with vbroker.orb.alwaysProxy=true or using firewall policies. However, VBJ Client can bid for both Firewall and IIOP profiles by setting the following property. vbroker.orb.dynamicLibs=com.inprise.vbroker.firewall.Init Resolution: A new property called "vbroker.orb.firewallInit" introduced in latest service pack of VBE 5.2 1 and VBE 6.5 versions, when set it to true, VBC Client now bid for both Firewall and IIOP profiles. The settings for the firewall policies (in code) or vbroker.orb.alwaysProxy property will continue to function as per normal, which is, bidding strictly for firewall only. VBJ support three types of bidding behavior 1) IIOP only 2) Firewall only (using either vbroker.orb.alwaysProxy or firewall polices, together with vbroker.orb.dynamicLibs) 3) IIOP and Firewall (using vbroker.orb.dynamicLibs only) Now VBC support bidding behavior similar to VBJ (with introduction of new property). 1) IIOP only (Don"t set any firewall policies nor include vbroker.orb.alwaysProxy property) 2) Firewall only (Set firewall polices or vbroker.orb.alwaysProxy) 3) IIOP and Firewall (Set vbroker.orb.firewallInit only) For VBE 6.5, the fix incorporated into Service Pack 9. For VBE 5.2.1, please obtain fix from Borland Support.
↧