Apache tomcat registration in SLD finishes successfully, but system doesnt display in SLD

[Former Member]

  Hi,

    We are working on integrating our BOXI 3.1 SP4 FP4.1 system to solution manager version 7.1 SP06.

    We use the following:

•       Tomcat version 5.5.
•       Wily EM version:8.2.3.5
•       Java bytecode agent version: 8 SP24
•       SMD agent version: 7.3 SP02
•       SLD version: 7.1

    When we reach the stage of deploying the SLD DS web application for registering and reporting software and application component data on our Apache

    tomcat servers, we use the attached document:Apache_tomcat-SLD-DS.pdf(attachment in note 1018839)  and have followed all the steps mentioned

    there.The registration works successfully and the xml payload (WSSDL) created for the tomcat servers are successfully written into SLD(we have manually

    invoked SLD and also scheduled it to run every 12 hours using the SLDdataSupplier properties file.). The log files generated suggest that the data is being

    sent over to the SLD system.

    What we have not done yet:

•     Tomcat JMX remote conenction has not been configured yet by adding the below options:

1. com.sun.management.jmxremote
2. com.sun.management.jmxremote.port = <jmx_port>

    But since the xml payload files are being generated correctly, we can assume that the configuration is being correctly collected by the SLD data supplier.The STDOUT file for tomcat also shows that the payload data files are correctly transported to SLD(refer to the attached STDOUT file).

    Concerns:

• When we login to check the technical system in using the SLD URL, we are unable to see any technical system for Apache tomcat.Nor can we see the tomcat server in Solution Manager technical systems. What could be the possible reason for this?
• Could SAP note :1781779 be relevant here
• Is JMX connection setup not being done yet a possible reason for this ? If yes then how are xml payload files being generated?

Regards

Sagarika

stdout1.txt.zip

[satishra · Accepted solution]

sending sld data supplier XML file is failing..you can see in the error log file

INFO: (SLDDS.TRP.FINISH) [SLDTransporter] transport to SLD finished. SUCCESS = false

C:/Program Files/SAP/hostctrl/exe/sldreg -connectfile C:/Program Files/sap/hostctrl/exe/slddest.cfg -file E:/APPS/Business Objects/Tomcat55/temp\atcsld_130120_200211_946.xml

check if the xml file is correct(syntax, open in IE)..you can also test manually by sending this xml file to sld server using sldreg program..

in sld datasupplier(sldDataSupplier.properties)..check the following section (if it is set as below)..

com.sap.sup.admin.sldsupplier.SLD_TRANSPORT_DISABLED=false

If it's sent to SLD successfully,,you can check it in  SLD Server (as below)

Apache Tomcat Server

a) Display in "Technical Systems" -> "Other(...)"

                       For the display of all systems enter "Apache" in the text filter. You use the host name of the server to search for an individual system.

b) Display in "Content Maintenance / CIM Instances"

                       For the display of all systems, select the CIM class "Apache Tomcat Server". For the associations you must particularly highlight all "Installed ..." for the installed software and also "Apache Tomcat ..." for the individual components.

[Former Member · Accepted solution]

Many thanks Satish for the reply.

The places in the trace where we have received the below error message occassionally, is because the SLD server was unavailable for maintenance.(sorry should have clarified this earlier).

INFO: (SLDDS.TRP.FINISH) [SLDTransporter] transport to SLD finished. SUCCESS = false

But our problem is that even when we were encountering a successful payload data transfer as per the logs:

INFO: (SLDDS.TRP.FINISH) [SLDTransporter] transport to SLD finished. SUCCESS = true

still the registration would not complete in reality.

I did check the xml file for correct syntax through IE and it is fine.(also if it isnt correct sldreg invocation itself will fail to parse the xml file) also the variable below is correctly set to false(the default value is false)

com.sap.sup.admin.sldsupplier.SLD_TRANSPORT_DISABLED=false

We checked the SLD admin logs and found the attached error: we would require to update CIM model version and CR_Content versions, and hence going to apply SAP notes 1625376 ,669669 Reference note : 1701770

Will post the outcome here if it works .

Regards

Sagarika

SLD version error.txt.zip