Solman 7.1 SP11 HTTP Code 503 : Service Unavailable

[Former Member]

Dear Gurus,

I need your help as I have problems with my Solman 7.1 SP11.

I have just upgraded my Solman 7.1 SP11 and I already applied sap notes 1933506 latest version 9.

My ST is SAPKITL711 and LM-SERVICE is 7.10 SP11 (1000.7.10.11.0.20140213055500).

The problems that I have:

1. My solman_setup - system preparation - "Set Authentication Policy for Agents" is on red status:
Error Message: Error while calling Diagnostics setup web service. Check note 1822831.
CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 503 : Service Unavailable")
CX_SOAP_FAILURE : Error when processing Web service call
CX_SOAP_CORE : Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 503 : Service

Unavailable")
I tried to troubleshoot using these below sap notes but still not able to solve the issue:
- snote 1752309 - Web service invocation problem caused by Unsupported xstream found
- snote 2018474 - Unsupported xstream found (HTTP Code 503  Service Unavailable)
- snote 1822831

2. Then in my Solman JAVA - NWA, I found error message in SSO - "SSO Certificate not found". The next day when I

tried to open Solman JAVA - NWA, I am not able to login anymore.
when I tried to open JAVA NWA & JAVA SLD, it always prompts for password.
However I am still able to open http://fqdn:8000or50000/index.html and Web Service Navigator.

I appreaciate if you can advise me.

Thank you.

Regards,
Stephan

[Former Member · Accepted solution]

Hi Stephan,

Regarding your error on smd certificates, the hint is below.

("HTTP Code 503 : Service
Unavailable")

this is very clear issue meaning from the given sap note

http 503 (Service Unavailable)
- Make sure your Solution Manager java stack is operational. This error is thrown when the java stack has not completed its startup procedure, or when a deployment is pending. For troubleshooting, check if the Java Web Services endpoints are reachable (http 404 case - troubleshooting).

for your case, make sure your SMD agent is up and running fine and registered to the solution manager and you are using SOLMAN_setup user or the user with admin access.

Regarding your java user login issue, make sure your JAVA UME connected to ABAP. You can set via VA or login to identity management UME -> configuration ->datasources , Please connect your basis team, detail steps refer the solution manager security guide https://websmp202.sap-ag.de/~sapidb/011000358700000482312011E.PDF step page 55.

Please check.

Thanks

Jansi

[Former Member · Accepted solution]

Hi Jansi,

Page 55 is an overview of capabilities/functions? I cannot go to Identity Management as I cannot go to NWA as well. However I am able to go to VA. I am currently in VA - Server0 - Services - Configuration Adapter - Runtime - Display Configuration - Configuration - cluster data - server - persistent - com.sap.security.core.ume.service - dataSourceConfiguration_abap.xml.

<?xml version="1.0" encoding="UTF-8"?>

<!-- $Id: //shared_tc/com.sapall.security/630_SP_COR/src/_deploy/dist/configuration/shared/dataSourceConfiguration_r3_roles_db.xml#8 $ from $DateTime: 2004/08/03 08:42:39 $ ($Change: 16964 $) -->

<!DOCTYPE dataSources SYSTEM "dataSourceConfiguration.dtd">

<dataSources>

  <dataSource id="PRIVATE_DATASOURCE" className="com.sap.security.core.persistence.datasource.imp.DataBasePersistence" isReadonly="false" isPrimary="true">

    <homeFor>

      <principals>

        <principal type="account">

          <nameSpace name="$serviceUser$">

            <attribute name="SERVICEUSER_ATTRIBUTE">

              <values>

                <value>IS_SERVICEUSER</value>

              </values>

            </attribute>

          </nameSpace>

        </principal>

        <principal type="user">

          <nameSpace name="$serviceUser$">

            <attribute name="SERVICEUSER_ATTRIBUTE">

              <values>

                <value>IS_SERVICEUSER</value>

              </values>

            </attribute>

          </nameSpace>

        </principal>

        <principal type="group"/>

        <principal type="team"/>

        <principal type="ROOT"/>

        <principal type="OOOO"/>

      </principals>

    </homeFor>

    <notHomeFor/>

    <responsibleFor>

      <principals>

        <principal type="account"/>

        <principal type="user"/>

        <principal type="group"/>

        <principal type="team"/>

        <principal type="ROOT"/>

        <principal type="OOOO"/>

      </principals>

    </responsibleFor>

    <notResponsibleFor/>

    <privateSection/>

  </dataSource>

  <dataSource id="R3_DATASOURCE" className="com.sap.security.core.persistence.datasource.imp.R3Persistence" isReadonly="false" isPrimary="true" policyEnforced="true">

    <homeFor>

      <principals>

        <principal type="user"/>

        <principal type="account"/>

      </principals>

    </homeFor>

    <notHomeFor>

      <principal type="user">

        <nameSpace name="$serviceUser$">

          <attribute name="SERVICEUSER_ATTRIBUTE">

            <values>

              <value>IS_SERVICEUSER</value>

            </values>

          </attribute>

        </nameSpace>

      </principal>

      <principal type="account">

        <nameSpace name="$serviceUser$">

          <attribute name="SERVICEUSER_ATTRIBUTE">

            <values>

              <value>IS_SERVICEUSER</value>

            </values>

          </attribute>

        </nameSpace>

      </principal>

    </notHomeFor>

    <responsibleFor>

      <principals>

        <principal type="user">

          <nameSpaces>

            <nameSpace name="com.sap.security.core.usermanagement">

              <attributes>

                <attribute name="uniquename"/>

                <attribute name="firstname"/>

                <attribute name="lastname"/>

                <attribute name="salutation"/>

                <attribute name="title"/>

                <attribute name="jobtitle"/>

                <attribute name="department"/>

                <attribute name="email"/>

                <attribute name="telephone"/>

                <attribute name="mobile"/>

                <attribute name="fax"/>

                <attribute name="locale"/>

                <attribute name="timezone"/>

                <attribute name="referenceuser"/>

              </attributes>

            </nameSpace>

          </nameSpaces>

        </principal>

        <principal type="account">

          <nameSpaces>

            <nameSpace name="com.sap.security.core.usermanagement">

              <attributes>

                <attribute name="j_user"/>

                <attribute name="j_password"/>

                <attribute name="validfrom"/>

                <attribute name="validto"/>

                <attribute name="islocked"/>

                <attribute name="lockreason"/>

                <attribute name="passwordchangerequired"/>

                <attribute name="userid"/>

                <attribute name="ispassworddisabled"/>

                <attribute name="logonalias"/>

                <attribute name="SecurityPolicy"/>

              </attributes>

            </nameSpace>

          </nameSpaces>

        </principal>

      </principals>

    </responsibleFor>

    <notResponsibleFor/>

    <attributeMapping/>

    <privateSection/>

  </dataSource>

  <dataSource id="R3_ROLE_DS" className="com.sap.security.core.persistence.datasource.imp.R3RoleDataSource" isReadonly="true" isPrimary="true">

    <homeFor/>

    <notHomeFor/>

    <responsibleFor>

      <principals>

        <principal type="group">

          <nameSpaces>

            <nameSpace name="com.sap.security.core.usermanagement">

              <attributes>

                <attribute name="description"/>

                <attribute name="displayname"/>

                <attribute name="uniquename"/>

              </attributes>

            </nameSpace>

            <nameSpace name="com.sap.security.core.usermanagement.relation">

              <attributes>

                <attribute name="PRINCIPAL_RELATION_MEMBER_ATTRIBUTE"/>

              </attributes>

            </nameSpace>

          </nameSpaces>

        </principal>

      </principals>

    </responsibleFor>

    <notResponsibleFor/>

    <attributeMapping/>

    <privateSection>

      <ume.r3.roles.user_datasource_id>R3_DATASOURCE</ume.r3.roles.user_datasource_id>

    </privateSection>

  </dataSource>

</dataSources>

[Former Member · Accepted solution]

Hi Stephan,

The security guide, only gives the information that UME configuration is one of the task you need to perform, but it wont give How to

Seems you are stuck.

Please contact your BASIS team on steps for UME configuration to ABAP source.

Thanks

Jansi

[Former Member · Accepted solution]

Hi Jansi,

I am the basis and solman person as well. Should I channel this message to the basis discussion group instead?

Thanks.

Regards,

Stephan Fong

[Former Member · Accepted solution]

Hi Jansi,

Regarding your comment:

"for your case, make sure your SMD agent is up and running fine and registered to the solution manager and you are using SOLMAN_setup user or the user with admin access."

I only have problem when accessing solman_setup from my abap client 001 (working client). If I access solman_setup through abap client 000, it is working fine. How can I register it back to client 001?

Thanks.

Regards,

Stephan

[Former Member · Accepted solution]

Hi,

Actually we some steps to change this ume client, check out here

Changing the ABAP Client for the UME After a Client Copy - Identity Management - SAP Library

Changing the AS ABAP Back-End System for the UME - Identity Management - SAP Library

Unfortunately I didn't get wiki page, except here

Thanks

Jansi

[Former Member · Accepted solution]

Hi Jansi,

I managed to make my NWA working. What I did was to put back the *.P12 certificate in the VA.

However I am still facing problem on

http 503 (Service Unavailable)

- Make sure your Solution Manager java stack is operational. This error is thrown when the java stack has not completed its startup procedure, or when a deployment is pending. For troubleshooting, check if the Java Web Services endpoints are reachable (http 404 case - troubleshooting).

My SMD agents are running fine. Any other advices that I can check?

Thank you.

Regards,

Stephan

[Former Member · Accepted solution]

Hi All,

When I accessed solman_setup, I found the same error messages in these two steps:

1. solman_setup - configure connectivity - configure web dispatcher - via system settings (icm/httpurlloc) - test connectivity

2. solman_setup - configure connectivity - set authentication policy for agents - use basic authentication (user/password)

Error message is:

CX_AI_SYSTEM_FAULT : SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 503 : Service Unavailable")

CX_SOAP_FAILURE : Error when processing Web service call

CX_SOAP_CORE : Error when calling SOAP Runtime functions: SRT: Unsupported xstream found: ("HTTP Code 503 : Service Unavailable")

This error message is encountered in my productive client (001). However if I access the solman_setup from client 000, it has no problem and working fine.

My solman has: (as recommended by sap note 1483508)

- ST 710 SP11 (SAPKITL711)

- LM-SERVICE 7.10 SP11 (1000.7.10.11.1.20140505095300)

Please help me with your ideas.

Thank you.

Regards,

Stephan

[Former Member · Accepted solution]

Hi All,

Similar problem happens here.

http://scn.sap.com/thread/3430781

Thanks.

Regards,

Stephan