We have a WIN2016 Cluster of three BOBJ 4.1 SP10 machines.
Our users access the Launchpad through our application without the traditional login, but are currently limited to a static system name for connection.
I see all kinds of simple code snippets for accessing the application the way it currently works. I am just looking for the best method to implement the use of the @BOBJCLUSTERNAME so that if one of the servers goes down for any reason the cluster can still answer calls.
3 Answers
-
Best AnswerFeb 16, 2018 at 05:52 PM
At the very least, you must log onto an individual CMS the first time. After this, the App server (or machine the application is running on) should have the @Clustername stored along with all individual members of the cluster in a properties file.
where the file is created depends on the account that the application is running under.
on Windows, the file is: C:\Users\<username>\.businessobjects\clusterinfo.1400.properties
If this file does not exist on the machine the app is running on, the @Clustername will not work.
the file can be copied across machines if necessary.If this app runs on several user machines, rather than a web server, then the easiest and probably best practise would be to use Try..Catch to log on. Try the @clustername first, and if that fails, try a fixed servername or IP to create the properties file for the very first logon. @Clustername should work from that point on.
Dan
Add comment
-
Oct 10, 2017 at 07:00 PM
It all depends on how exactly your users are accessing BOE and why you're using static system name instead of @cluster
Add comment
-
Feb 19, 2018 at 03:15 PM
In launchpad the system name can be set in the properties file cms.default=CMSname or clustername but if you are using custom code you are probably bypassing the properties files.
Setup of the cluster.properties might help in the BI administration tag, but again if using SDK that too might be bypassed
Add comment
Add comment