You replied:
Even in a shared installation, try to configure OBJECTS.LSI, PDAC.LSI and SDAC.lsi to be local to the machine, to avoid corrupting this file and speeding up login process.
You suggested making those 3 files local. Why wouldn’t we just go with a local installation?
We perceive the benefit of a shared installation is that future software releases would only need to be installed on the server. The local machines running BO would not need to be updated since they are running BO off of the server. Are our assumptions correct? We are strongly considering switching back to a local installation due to the problems we’ve encountered with a shared installation.
When you have problems connecting, you may also want to post what database you are trying to connect and use as your security domain. I have had a large success using Business Objects with Oracle as our database. I have seen issues with Business Objects on other types of databases, but it is usually in part to the databases inability to handle row-level locking.
I understand that Sybase (11.9?) will be releasing a version that allows for rowlevel locking. Until that happens it is quite possible that the root of your issue may not be directly related to BO, but to the database the information is stored on. I have asked numerous questions of Business Objects Technical Support and here is essentially what it boils down to.
Business Objects is dependent on being able to access multiple tables at one time (security domain, document and universe domain). When someone is exporting to a user, it is possible that that user has access problems to maintain database integrity. If you are not on an Oracle database, then it is possible that setting ‘virtual’ row level locking (pages set to one row), and dirty reads turned on, would get you some improved interaction.
You replied:
Even in a shared installation, try to configure OBJECTS.LSI, PDAC.LSI and SDAC.lsi to be local to the machine, to avoid corrupting this file and speeding up login process.
Correct. This is what we suggest to our customers even in shared client installations. The configuration of these 3 files to be local has nothing to do with the installation mode of the client (i.e where the software, etc. is located). This configuration can be altered after the Server-installation, before leaving the install program there is a ‘change’ button somewhere (right bottom of the dialog box) which lets you re-define the localisation of these 4 (incl. BOMAIN.key) files. It also can be changed individually for a specific client and is used ONLY for defining the location of these files.This does NOT mean, you have to install stand-alone clients!
You suggested making those 3 files local. Why wouldn’t we just go with a local installation?
see above
Hope this helps…
Walter
DI Walter Muellner
Delphi Software GmbH, Vivenotgasse 48, A-1120 Vienna / Austria Tel: +43-1-8151456-12, Fax: +43-1-8151456-21 e-mail: w.muellner@delphi.at, WEB: http://www.delphi.at