cancel
Showing results for 
Search instead for 
Did you mean: 

WSRP Registration format

Former Member
0 Kudos

Hi,

while registering a SAP Portal as WSRP consumer to a WSRP producer following registration message is sent:

<?xml version="1.0" encoding="utf-8"?>
   <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
        xmlns:wn3="http://www.w3.org/1999/XMLSchema" 
        xmlns:wn2="http://www.w3.org/2000/10/XMLSchema"  
        xmlns:wn1="http://www.w3.org/2001/XMLSchema" 
        xmlns:wn0="http://schemas.xmlsoap.org/soap/encoding/" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xmlns:wn4="urn:oasis:names:tc:wsrp:v1:wsdl" 
        xmlns:tns="urn:oasis:names:tc:wsrp:v1:wsdl">
      <SOAP-ENV:Body>
         <prt0:register xmlns:prt0="urn:oasis:names:tc:wsrp:v1:types">
            <prt0:consumerName>sap</prt0:consumerName>
            <prt0:consumerAgent>SAP_EP6_SP9</prt0:consumerAgent>
            <prt0:methodGetSupported>false</prt0:methodGetSupported>
            <prt0:extensions>
               <a>sap_consumer_indication</a>
            </prt0:extensions>
            <prt0:extensions>
               <a/>
            </prt0:extensions>
         </prt0:register>
      </SOAP-ENV:Body>
   </SOAP-ENV:Envelope>

The message complies with the WSRP specification but unfortunately my WSRP producer does not support extension and doesn't ignore them either. Therefore the registration can not be performed. Is there a way (a setting in the portal) to remove the extension elements from the SOAP message which are sent from the consumer to the producer?

Regards,

Kevin

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi check the following registration steps

to start, goto

System Administration -> Federated Portal->Myself as Content Consumer => Manage My Producers

1. Choose 'New' -> 'NetWeaver Content Producer'

2. Enter producer name and producer id

3. Choose the protocol (http/https)

4. Host name and Port of the Producer

5. Click Next (View your settings in the Summary pane).and Finish

6. Open the producer object and Choose Producer Aliases in the Display drop-down menu located in the object editor toolbar

7. Choose Connection Tests in the Display drop-down menu located in the object editor toolbar

8. In the System Connection Tests table, choose the Producer Connection test

9. Click Test

10. Choose Producer Registration in the Display drop-down menu located in the object editor toolbar.

11. In the Your Consumer Name box, enter the name of your portal is sent to the producer upon registration.

12. In the Your Consumer URL box, enter the URL of the Consumer with port: (https://pwdf2846.wdf.sap.corp:50001)

13. In the Registration Parameters in registration password enter the password for NW producers (default registration password for NW producers is: password) => could be this table will be empty

14. Click Register

                • please reward points if the information helped you***************************

Answers (2)

Answers (2)

Former Member
0 Kudos

Thank you both for your help. I was able to create a remote producer und successfully performed the connection test. However, I need to find a way to prevent the portal from sending the extension part...

 <prt0:extensions>
                <a>sap_consumer_indication</a>
            </prt0:extensions>
            <prt0:extensions>
               <a/>
            </prt0:extensions>

...included in the registration SOAP message in order to get the portal working with my producer. I guess there are no explicit settings in the portal to influence the format of the WSRP messages.

Regards,

Kevin

Former Member
0 Kudos

Hi Kevin,

There is no way to avoid the sending of these Extensions but it shouldn't fail your request even if the Producer does not understand the meaning of these Extensions. The Spec states that the Producer is free to ignore the Extensions and that the Consumer should not expect the Producer to do anything with these extensions.

I suggest you contact the Producer and present them with a question of why does their SOAP framework fail the request.