Initial Checks:
Path of BO installation
E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0
SAP BO Version Check
Go to Add or Remove Programs dialog. The update indicates the current level.
Tomcat Information
http://<<Full Host Name>>:8080/manager/html
Like:
Tomcat Version - Apache Tomcat/6.0.35
JVM Version - 1.6.0_37-b06
JVM Vendor - Sun Microsystems Inc.
OS Name - Windows Server 2008 R2
OS Version – 6.1
OS Architecture – amd64
DAA Status on BO Host
Host Agent Status:
Host Agent Version Check
saphostctrl -function ExecuteOperation -name versioninfo
Update host agent to very latest.
(DAA and Host Agent are not very compulsory to taken care but this will help in Managed system registration with SOLMAN system)
SLD Registration
http://<<Hostname>>:5<Instance No.>00/sld
user: admin user
Pass: *****
Just to check, there is no entry for BO system.
Transferring Tomcat and BOE data to SLD
Step 1 -Transfer Tomcat Web App details to SLD
Download the TomcatSLDDataSupplierWEB.zip application from OSS Note 1508421 and extract it to local directory
Step 2.1. Enable Manager Role in TomCat Application if not enabled already
- Open tomcat-users.xml from tomcat installation directory
(i.e. E:\Program Files (x86)\SAP BusinessObjects\Tomcat6\conf)
- Add roles “manager” and “admin”
Note : Take Backup of file “tomcat-users”
Before
After
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
<!--
<role rolename="tomcat"/>
<role rolename="role1"/>
<user username="tomcat" password="tomcat" roles="tomcat"/>
<user username="both" password="tomcat" roles="tomcat,role1"/>
<user username="role1" password="tomcat" roles="role1"/>
-->
<role rolename="manager"/>
<role rolename="admin"/>
<user username="admin" password="admin" roles="admin,manager"/>
</tomcat-users>
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Step 2.2. Deploy the SLDDS Application using Tomcat Manager Page
Open Tomcat Manager Page by calling http://<hostname>:<portusedbytomcat>/manager/html
Go to down side of page and get below screen of the above page
Use the “WAR file to deploy” option to deploy the downloaded war file from Snote 1508421
Select the file and press Deploy button.
Once deployed, you will see an additional application called TomcatSLDDataSupplierWEB in the manager page (refer the below screenshot).
Step 2.3 - Send Data to SLD
Next step is to transfer the data using the SLDDataSupplier application which was deployed in the previous step, in order to perform the data transfer, create the connect.key file to generate a file with SLD related information such as (user, host, port, pwd, etc.,)
C:\Program Files\SAP\hostctrl\exe>sldreg -configure connect.key
Enter the following details:
Option | Description |
UserName | User name for the SLD server. |
Password | The user account password used to authenticate the user name entered. Password and Confirm Password must match for the password to be accepted. |
ServerHost | The host name or the IP address of the SLD server. |
Port | The HTTP(S) port on which the SLD server is running. Enter a valid port number in the range of 0-65535. |
Use https | Indicate if you want a secure connection or not. |
Write this information to secure file | If you want to store the encrypted HTTP connection information, enter y/n n |
Step 2.4. Adjust the Tomcat SLDDS control file to send the data to SLD
Open sldDataSupplier.properties (if the file is not found in the below mentioned directory, then copy sldDataSupplier.properties.template to sldDataSupplier.properties)
E:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\sap.com~TomcatSLDDataSupplierWEB
Update the file as below (E:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\sap.com~TomcatSLDDataSupplierWEB)
Below entry should be there :
com.sap.sup.admin.sldsupplier.WORKING_DIR=C:/WSSLDProvider/work
com.sap.sup.admin.sldsupplier.SLD_FILE_NAME_PREFIX= sldds
com.sap.sup.admin.sldsupplier.SLD_FILE_NAME_USE_TIMESTAMP = true
com.sap.sup.admin.sldsupplier.SLDREG_PATH=C:/Program Files/SAP/hostctrl/exe/sldreg.exe
com.sap.sup.admin.sldsupplier.SLDREG_CONFIG_FILE_PATH= C:/Program Files/SAP/hostctrl/exe/connect.key
com.sap.sup.admin.sldsupplier.SLD_SCHEDULER_DISABLED = false
com.sap.sup.admin.sldsupplier.SLD_SCHEDULER_INITIAL_INTEVAL=300000
com.sap.sup.admin.sldsupplier.SLD_SCHEDULER_INTERVAL= 43200000
Once the connect.key and sldds properties files are created start the SLDDS application from Tomcat manager page as mentioned below.
During the application start, the information about the Tomcat server will be sent to SLD (using the connect.key and the XML file generated by the application),
Some More Information with regard to BO configuration to SLD. Also to send data to SLD forcefully.
http://<<Full Host Name>>:8080/sap.com~TomcatSLDDataSupplierWEB/TomcatSLDDataSupplier?action=help
http://<<Full Host Name>>:8080/sap.com~TomcatSLDDataSupplierWEB/sldsupplier?action=displayConfig
http:<<Full Host Name>>:8080/sap.com~TomcatSLDDataSupplierWEB/sldsupplier?action=displaySchedulers
http:<<Full Host Name>>:8080/sap.com~TomcatSLDDataSupplierWEB/sldsupplier
http://<<Full Host Name>>:8080/sap.com~TomcatSLDDataSupplierWEB/sldsupplier?action=sldSupplier
Once you get data with action=sldSupplier Option, it means data has been send to SLD forcefully.
SLD Registration Finished.
- SAP Managed Tags:
1 Comment
