Thursday, February 4, 2016
Disabling BI 4.1 CMS name on BI Launch Pad or CMC
C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\default
Open the CmcApp.properties file and make it the cms.visible=false.
Open the BIlaunchpad.properties file and make it cms.visible=false
# You can specify the default CMS machine name here
cms.default=xxxxxxxxxxxxxxxx:6400
# Choose whether to let the user change the CMS name. If it isn't shown the default System from above will be used
cms.visible=false
RESTART THE APPLICATION SERVER
Subscribe to:
Post Comments (Atom)
Sonarqube Upgrade from 9.4.4 to 9.9.4 LTS
Issue: 1) Java hasbeen upgraded from 11 to Open JDK 17. And Sonarqube is upgraded from 9.4 to 9.9.4. 2) After the upgrade sonarqube servic...
.png)
FYI, although this will work temporarily, I am fairly certain that when you take package updates this will be overwritten. You can see by opening the files noted in the original post that you are not supposed to modify them:
ReplyDelete"# DO NOT MODIFY THIS FILE!
# To customize any of the settings, create a new file in \\warfiles\webapps\BOE\WEB-INF\config\custom
# and run wdeploy. Only changes in the custom directory will be maintained over patches. The new file has to have the same file name
# as this one and shall only contain the properties that you would like to customize"
The workflow to not have packages undo this change is to create a new Cmc.App.properties or BIlaunchpad.properties file in the C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom folder (for war file deployments) or C:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF\config\custom (for tomcat deployments) and have the new file contain ONLY THE CUSTOM SETTING YOU WANT CHANGED such as:
cms.visible=false
You then want to use wdeploy to redeploy the apps and cycle your webservers. These changes will not be overwritten when packages are taken.