Show TOC

Application Program Interface for Inbound Proxy CommunicationLocate this document in the navigation structure

You use the following SAP-specific interface pattern to examine the XI-specific data capsulated in the request XI message.

ProviderXIMessageContext

  • Extension interface name

    com.sap.engine.services.webservices.espbase.server.additions.xi.ProviderXIMessageContext

  • Interface methods

                         //Returns an instance of ProviderXIMessageContext which is a singleton
     ProviderXIMessageContext getInstance();
     //Returns property value mapped to the specified key
     Object getProperty(String key);
     // Determines the name of a communication party of a message received at the receiver 
     String getSenderPartyName();
     //Returns request XI message application acknowledgement listener name
     String getApplicationAckRequested();
     //Returns request XI message system acknowledgement listener name
     String getSystemAckRequested();
     //Returns request XI message application error acknowledgement listener name
     String getApplicationErrorAckRequested();
     //Returns request XI message system error acknowledgement listener name
     String getSystemErrorAckRequested();
     // Determines the service of a message received at the receiver
     String getSenderService();
     //Returns request XI message queue id
     String getQueueId();
     // Determines the service of a message received at the receiver
     QName getServiceInterfaceName();
     //Identifies whether the XI request is asynchronous
     boolean isAsync();
    
                      

You use the following class to retrieve and process attachments in XI-enabled Web services proxies.

ProviderAttachmentHandlerFactory

  • Extension class name

    com.sap.engine.services.webservices.espbase.server.api.ProviderAttachmentHandlerFactory

  • Methods

    // Returns an instance of a class implementing AttachmentHandler
    AttachmentHandler getAttachmentHandler()

For more information, see SAP Note 1885968 Information published on SAP site.