on 10-31-2016 4:57 PM
Hi Experts,I have the following setup
Windows 2012 r2
BO 4.2 sp02
clustering installation with 2 nodes (BOPROD1, BOPROD2)
Everything seems ok but I would like to change the cluster name so we are not only using the default first node
I went to CCM - change the cluster name with @BOPROD
Then changed in the D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom the
BILaunch
old
# You can specify the default CMS machine name here
cms.default=BOPROD1:6400
new
# You can specify the default CMS machine name here
cms.default=@BOPROD
Also changed
PlatformServices
cms.clusters=@BOPROD
cms.clusters.production=BOPROD1:6400, BOPROD2:6400
I cannot login using the new cluster name @BOPROD but still can login with the old one
Am I missing anything?
Hi All,
Can any one Explain here Step by Step BO Server 4.2 SP4 Clustering and Tomcat load balancing .
Environment.
CMS Database: Oracle 11g R2
Windows Server 2016
SAP BI Plateform 4.2 Sp4
Regards,
Muhammad Shafiq
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Tanveer and Everybody
I found a solution as below
Finally after couple of days of working, I managed to fix the clustering issue.
Let me explain what I have done
I.I stopped Tomcat and SIA Agent under the Central Configuration Manager
I.Change the Cluster name to BOProd in both nodes
I.Then I re-create the files under tomcat and under war files in both nodes
D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom
D:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF\config\custom
I.This time I added 3 files instead of two (I have read somewhere that there was another file involved)
OpenDocument.properties
BIlaunchpad.properties
PlatformServices.properties
The difference was that I put the full qualified server address in the PlatformServices.properties
cms.clusters=BOProd
cms.clusters.production=node1, node 2
The difference I used BOProd without the @ symbol
# You can specify the default CMS machine name here
cms.default=BOProd
I.After change these in both nodes, I re-deploy the entire website files using wdeploy (really took a while)
I.Then I restart SIA Agent and Tomcat Agent
After all of these it works using during the login in the system box @BOProd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can find the clusterinfo.1400.properties file on windows under "c:/.businessobjects".
Have you restarted SIA and Tomcat for the changes to take effect.?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try
@BOPRD:6400
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
have you stopped tomcat, cleared tomcat cache, started tomcat ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You changed the properties files under warfiles - which is good because it means they won't be overwritten by an upgrade install. However, you also have to make the changes in the same place under Tomcat\webapps, then stop Tomcat and start it again in order for the changes to take effect.
-Dell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
I see you have made the following changes,
I went to CCM - change the cluster name with @BOPROD
Change the cluster name to only BOPROD and don't prefix @ sign.
Leave the other changes in the properties file as it is and then restart Tomcat and SIA.
If the issue still persists then login with CMS hostname first to web apps i.e. CMC or BI Launchpad and after that you can login using cluster name.
It can happen that the Clusterinfo.1400.properties file is not updated at times with the new cluster name that's why you are not able to login specifying the cluster name.
Regards,
Tanveer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you have a look at the SAP note for how to change the cluster name for Business Objects using Web Application:
See if you have missed anything. Also one suggestion, It seems to be odd but can you try login using IP Address or hostname of the BO server and if you can successfully login then log off. Then try to login using the cluster name.
Also are you able to login to any client tool using @Cluster Name?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also have a look at this SAP note:
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.