Test Environment

The main function of the test environment of the Adapter Engine is to test the settings of the individual adapters (JMS, File/FTP, JDBC, SOAP). It is possible to create test variants and to save these in the Adapter Engine.

You have installed the Adapter Engine and the adapter you require, started the Adapter Engine and called it using your web browser. On the configuration screen , you have chosen the menu option Test Environment and the system now displays the menu with the same name.

There are three ways of sending client-side messages using HTTP in the test environment.

• The first message type is general MIME messages.

  The test interface receives a single part MIME message in text format and sends it to a specified address on the Internet.It comprises two input areas:

  • In the first input window, enter the parameters for the HTTP header in the same way that you entered the adapter parameters. In particular, you can set the value for XI.TargetURL, for example:
    • XI.TargetURL=

      http://p35841:3333/JMS

  • In the second input window, specify the payload you want to send. The payload and the body of the HTTP request are identical.

  With this test, you can easily generate JMS text messages using the mode JMSTunneling, with the JMS adapter, for example.

• The second message type is Integration Engine messages.

  The test interface receives messages of this type with a text payload.It comprises two input areas:

  • In the first input field, enter the data that you want to put in the message header.

    You set the parameters of the header data in the same way you set the parameters of the JMS file/FTP adapter or JDBC adapter.

  • In the second input field, specify the text payload you want to send.

  With this test, you can easily either send a message to the Integration Engine, or simulate a sending Integration Engine (for example, to test the configuration of an adapter), for example.

• The third message type is simple Web Service or SOAP messages.

  The test interface receives messages of this type with a text payload.It comprises two input areas.

  • In the first input field, enter the data that you want to put in the HTTP header. In particular, you can set the values for WS.targetURL and WS.SOAPAction, for example:
    • WS.targetURL=

      http://p35841:4040/WS

    • WS.SOAPAction=

      testservice

  • In the second input field, specify the sender payload you want to send.

  Using this test it is very easy to send a Web Service message to a SOAP adapter (for example to test the configuration of the adapter), for example.

If you have set the data correctly, choose Send Message to generate and send the message for all three text variants.

The system then sends you a review of the send procedure (Send Review).The upper output field contains the generated and sent data; the lower output field contains the received data or a specific error text, in the case of an error.

To load or delete a test variant, choose Load variant. To save a test variant as a default variant, choose Save variant as.

The variant sap_default is shipped by SAP and cannot be deleted or saved under the same name. If you attempt to save sap_defaultthe system creates a new variant with the name default.

As an example of the second message type, a message for the Integration Engine is generated from the following header data and payload and sent to the following address:

http://pwdf0436:8082/sap/xi/engine?type=entry

Header Data

XI.TargetURL=http://pwdf0436:8082/sap/xi/engine?type=entry

XI.SenderParty=Sender

XI.SenderService=ExtAdapterSender

XI.SenderInterfaceNamespace=http://sap.com/xi/xidemo

XI.SenderInterface=ExtAdapterSenderIF

XI.ReceiverParty=Receiver

XI.ReceiverService=ExtAdapterReceiver

Payload

<test>Payload</test>

Message

Content type: Multipart/Related; boundary=4859e1d0-1ef1-11d6-a1c4-6fda44caeb12

Content length: 1495

--4859e1d0-1ef1-11d6-a1c4-6fda44caeb12

Content type: text/xml

Content length: 1189

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Header>

<sap:MessageHeader xmlns:sap="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1">

<sap:From>

<sap:Name>ExtAdapterSender</sap:Name>

<sap:Interface namespace="http://sap.com/xi/xidemo">ExtAdapterSenderIF</sap:Interface>

</sap:From>

<sap:To>

<sap:Name>ExtAdapterReceiver</sap:Name>

<sap:Interface namespace="http://sap.com/xi/xidemo">ExtAdapterReceiverIF</sap:Interface>

</sap:To>

<sap:MessageId>48585b30-1ef1-11d6-8726-6fda44caeb12</sap:MessageId>

<sap:QualityOfService>BestEffort</sap:QualityOfService>

<sap:TimeSent>2002-02-11T13:14:30Z</sap:TimeSent>

<sap:Direction>Request</sap:Direction>

<sap:TraceLevel file="mytrace.trc">1</sap:TraceLevel>

<sap:Logging file="mylog.log">1</sap:Logging>

<sap:Document>MainDocument</sap:Document>

</sap:MessageHeader>

</SOAP:Header>

<SOAP:Body>

<sap:Manifest xmlns:sap="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">

<sap:Payload xlink:type="simple" xlink:href="cid:payload-48585b311ef111d694636fda44caeb12@sap.com">

<sap:Document>MainDocument</sap:Document>

</sap:Payload>

</sap:Manifest>

</SOAP:Body>

</SOAP:Envelope>

--4859e1d0-1ef1-11d6-a1c4-6fda44caeb12

Content type: text/plain

Content length: 22

Content ID: payload-48585b311ef111d694636fda44caeb12@sap.com

<test>Payload</test>

--4859e1d0-1ef1-11d6-a1c4-6fda44caeb12--

The system displays the sent and the received message in the screen Send Review.