Application Programming Interface für die Inbound-Proxy-Kommunikation

Sie verwenden das folgende SAP-spezifische Interface-Pattern, um die XI-spezifischen Daten, die in der XI-Request-Message gekapselt sind, zu prüfen.

ProviderXIMessageContext

• Extension-Interface-Name

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

• Interface-Methoden

                       //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();
  
                    

Mit der folgenden Klasse rufen Sie Attachments in XI-fähigen Web-Service-Proxys ab und verarbeiten sie.

ProviderAttachmentHandlerFactory

• Name der Erweiterungsklasse

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

• Methoden

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

Weitere Informationen finden Sie im SAP-Hinweis 1885968 .