Java Data Bean Connect String Archived (Doc ID 511828.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

SBL-JCA-00204, SBL-JCA-00403

We have moved our Java Data Bean code from Systest (where single Object manager was being used) to UAT (where Multiple object Managers are being used) and are facing problems wrt connection to the object manager (ie connect string formation is probably not correct)

This is the error message that we get
Unable to connect to host "server" at port "2321". (SBL-JCA-403)

This is the connect string being generated
siebel.tcpip.none.zlib://Bserver:2321/ent_ate/FINSObjMgr_enu

Pls find enclosed below the detailed error message:

I checked many SRs in supportweb and it seems that the connect string format in case of multiple servers is :siebel:// virtualserver/ EnterpriseName/ XXXObjMgr_ lang
Could it be the reason as to why the code is not working in the As-is form.

Also, I could not find an exact description of the changes that need to be done overall so that the actual value of the virtualserver is being retrieved in the code.

Can you pls let us know as to what would be the actual value for the connect string in this scenario and what changes have to be done in different files so that the code works based on the new connect string, if at all it needs to be used.

1.Is it necessary to add a new property siebel.conmgr.virtualhosts in the siebel.properties file .So far we were not using the siebel.properties file.
Can u pls specify the value to be associated with this property if it is to be used

2.I checked the lbconfig .txt file and found that the value of the VirtualServer is :-
VirtualServer=1:server03003:2321;2:server03004:2321;3:server03005:2321;4:server03006:2321;

Changes

 n/a

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.