on 11-04-2010 2:39 AM
We recently upgraded our Solman to v7.01 EHP1 sp06 , Wily v8.2 and Diagnostics to v7.11
While testing, we have the following errors and questions:
1) When clicking on system analysis -> Log Viewer
Error "Application Log Viewer is not available for your selection" - this does not happen to all systems, only some
2) Is the Log viewer applicable for both ABAP and Java systems?
3) Is the Expert Analysis for Java systems only?
4) How do we remove the old entries in Agent Administration-> Agent Candidate Mgt->SLD View ? Is there a table that stores the entries which we can clean up? We've uninstalled the diagnostic agent v7.0 and installed with 7.1 and the SMDSIDs have changed
5) We are encountering intermittent connection timeout issues when opeing WA , TA or CA in solman. Do we have to increase the timeout parameter icm/server_port_x ?
Appreciate all your help
Implement note 1458488 - Logs not added in Logviewer
Set these parameters below according with page 10 of Configuration guide of solman EHP1
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
icm/host_name_full = fully qualified server name
This parameter must be attributed to the fully qualified server name (for example, wdfd002568.wdf.sap). The name must contain at least two periods, see also SAP Note 434918.
icm/server_port_1 = PROT=SMTP,PORT= <> 0; for example: 25000
login/no_automatic_user_sapstar = 0
icm/conn_timeout; for example: 20000
icm/keep_alive_timeout; for example: 240
SAPLOCALHOSTFULL = fully qualified server name
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, that was helpful and we already had those settings set. We opened sap case and in our particular case, this fixed the issue on
====
#1) missing http log
-In managed system log configuration, the severity of trace location com.sap.engine.services.httpserver.server.Smd is set to NONE, it should be set to INFO so that you could have the HTTP header entries written
to that httpresponse.trc.
In addition, these are the recommendations from sap:
The managed ABAP system should have the latest ST-PI/ST-A/PI
installed and correctly configure the icm/HTTP/logging_0 parameter.
(icm/HTTP/logging_1 is optional in case your HTTP logs will be
overwritten shortly due to the heavy workload)
The managed JAVA system should follow the above trace location
settings to write the verbose header information into the trace file.
Of course, the wily agent Java bytecode instrumentation is a must.
===
I am still waiting for suggestions / answers for my other issues
4) did you find a way to remove the agent candidates? I remember this was directly in the SLD content, but don't remember exaclty where...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
96 | |
11 | |
11 | |
10 | |
9 | |
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.