Diagnostics Agent Configuration of ABAP based systems

[Former Member]

Hi Experts,

we have solution manager 7.01 SPS27 , and we are trying to run Diagnostics Agent Configuration for our ABAP based system.

First try - we ran, everything worked fine except one Warning message

SSO] The ABAP profile of instance tt1p003a/T1P/20 (tt1p003a) contains the parameter : login/accept_sso2_ticket=0 . This parameter should be set to value 1 for enabling SSO

So we have defined defined this parameter in the INSTANCE PROFILE of our ABAP system and restart SAP.

Rerun the setup again, but still it gives the same warning message -- here is the detailed log

Found SID for SSO ACL entry : SGP

Found login.ticket_client for SSO ACL entry : 000

The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc_{webadministrator}solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar

The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (620 bytes)

ABAP Certificate was successfully retrieved (595 bytes)

ABAP SSO ticket certificate of SGP was imported in ABAP PSE of tt1p003a (client 100)

The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SGP LoginTicketClient=010)

Java SSO ticket certificate of SGP was imported in ABAP PSE of tt1p003a (client 100)

The Java SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SGP LoginTicketClient=000)

The ABAP profile of instance tt1p003a/T1P/20 (tt1p003a) contains the parameter : login/accept_sso2_ticket=0 . This parameter should be set to value 1 for enabling SSO

Can't understand why it's still giving this Warning - we have tried stopping SMD agent on ABAP based system - Re-run the setup again - but no luck.

In E2E - Workload Analysis, we can see that data is being reported for this ABAP based system.

Please provide your thoughts on this -

1. whether this is just cosmetic warning message and we can ignore this ? If not what do we need to do to get rid of this warning message?

2. how can we verify if SSO from Solution Manager to this ABAP based system is working?

Appreciate your time.

Thanks & Best Regards

Davinder

[Former Member]

Hi,

On the ABAP system, goto tcode RZ10.

From menu -> goto -> profile values of active servers -> select the active application server -> check the 'active' value of parameter login/accept_sso2_ticket.

Regards,

Srikishan

[Former Member]

Hi,

login/accept_sso2_ticket=1 is already active, we have re-checked this after system restart. Even in RZ11 it shows current value and Profile value as 1.

But still we are getting the same warning in Diagnostics Setup of this ABAP system.

How can we actually test if SSO between Solution Manager and ABAP based satellite system is working?

Regards

Davinder

[Former Member]

Hi,

This is a strange situation.

To check if the ABAP satellite system accepts logon tickets:

- Run sso2 tcode with no parameters

To check SSO between SolMan and ABAP:

- Run sso2 on SolMan, provide RFC to the ABAP system and execute

- Another simple test: Create two user-ids (with same name but different passwords) on the two systems. Test a simple service say 'ping' via SICF on the SolMan system. It should open a browser prompting for user/password on SolMan. Once opened, without closing the window - change the address to point to the 'ping' service of the ABAP system. It should not ask for user/password again. This shows SSO is working.

Regards,

Srikishan

[guilherme_balbinot]

Hello Davinder,

Even though the parameter is there, it must be accessible for checking.

In order to get the profile value of the managed system we use a webservice handled by sapstartsrv on port 56013. It seems that this port is not listening: sapstartsrv is probably stopped.

You can see it here:

"!! Exception : Service call exception; nested exception is:

java.net.ConnectException: Connection

refused(cause=java.net.ConnectException Connection refused)"

Would you please check that sapstartsrv is up and running, then check that port 56013 is listening and then please restart the setup.

Note that your port number might be different.

Additional information:

-

---

As mentioned in the Note 936273,

"The start service is integrated into the Unix operating system using the

"sapinit" script as well as entries for each instance in

"/usr/sap/sapservices" (see Note 823941 (UNIX) or Note 893215(IBM i)).

"

So please check the Note 823941 and 936273 to set up the autostart of the sapstartsrv. Then restart your system and then you can check whether sapstartsrv is started by

- 'ps -ef grep sapstartsrv' command.

- '/sbin/init.d/sapinit status' command.

-

---

Best regards,

Guilherme