Error Message: Envelope missing from SOAP message header (Demo Example)

[Former Member]

Hi,

I am executing the Demo Example: CheckFlightAvailability.

But, now I am getting <b>Envelope missing from SOAP message header</b> ERROR.

Regards,

Nagarjuna.

[Former Member]

Hi all,

I am getting the following trace for <b>Envelope missing from SOAP message header</b> error.

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

- <!-- Call Integration Server

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">COMMIT is expected by application !</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />

- <!-- ************************************

-->

<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>

<Trace level="3" type="T">Getting type of XMB...</Trace>

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="2" type="T">XMB kind = SND_CENTR</Trace>

<Trace level="3" type="T">Start pipeline found</Trace>

<Trace level="2" type="T">Switch to external start pipeline PID = SENDER</Trace>

- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">

<Trace level="3" type="T">No triggers found. OK.</Trace>

</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="3" type="T">system-ID = C12</Trace>

<Trace level="3" type="T">client = 105</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = XISUPER</Trace>

<Trace level="1" type="Timestamp">2006-03-31T05:37:12Z CET</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE">

<Trace level="1" type="T">Message-GUID = 4FD44C8345E6354CB65C1C46E9C56FA1</Trace>

<Trace level="1" type="T">PLNAME = SENDER</Trace>

<Trace level="1" type="T">QOS = BE</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline SENDER</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">

<Trace level="3" type="T">External PLID = SENDER</Trace>

<Trace level="3" type="T">Internal PLID = SAP_SENDER</Trace>

</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline attributes</Trace>

<Trace level="3" type="T">PID = SAP_SENDER</Trace>

<Trace level="3" type="T">ENABLE = 1</Trace>

<Trace level="3" type="T">TRACELEVEL = 0</Trace>

<Trace level="3" type="T">EXEMODE = A</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline elements</Trace>

<Trace level="3" type="T">ELEMPOS = 0001</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</Trace>

<Trace level="3" type="T">PLSRVTYPE =</Trace>

<Trace level="3" type="T">FL_DUMMY =</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T" />

- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

<Trace level="2" type="T">Persisting original message</Trace>

<Trace level="3" type="T">Message-Version = 000</Trace>

<Trace level="3" type="T">Message version 000</Trace>

<Trace level="3" type="T">Pipeline SENDER</Trace>

</Trace>

<Trace level="1" type="Timestamp">2006-03-31T05:37:13Z CET Begin of pipeline processing PLSRVID = SENDER</Trace>

<Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER" />

- <!-- ************************************

-->

<Trace level="1" type="Timestamp">2006-03-31T05:37:13Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_INTEGRATION_SERVER</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INTEGRATION_SERVER</Trace>

<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</Trace>

<Trace level="3" type="T">PLSRVTYPE =</Trace>

<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>

<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>

<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>

<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>

<Trace level="3" type="T">FL_LOG =</Trace>

<Trace level="3" type="T">FL_DUMMY = 0</Trace>

<Trace level="3" type="T" />

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">

<Trace level="1" type="T">URL for integration server read from global configuration</Trace>

<Trace level="1" type="T">URL= dest://SAP_XI_105</Trace>

- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">

<Trace level="2" type="T">Addressing mode: CallIntegrationServer</Trace>

<Trace level="3" type="T">URL = dest://SAP_XI_105</Trace>

<Trace level="3" type="T">Host =</Trace>

<Trace level="3" type="T">Port =</Trace>

<Trace level="3" type="T">Transport protocol = HTTP</Trace>

<Trace level="3" type="T">Message protocol = 003000</Trace>

<Trace level="3" type="T">Path =</Trace>

<Trace level="3" type="T">Attributes of destination: SAP_XI_105</Trace>

<Trace level="3" type="T">Type = H</Trace>

<Trace level="3" type="T">Pipeline =</Trace>

<Trace level="3" type="T">Action = EXECUTE</Trace>

<Trace level="3" type="T">Host = myhost</Trace>

<Trace level="3" type="T">Port = 8001</Trace>

<Trace level="3" type="T">Client = 100</Trace>

<Trace level="3" type="T">User = XISUPER</Trace>

<Trace level="3" type="T">Language =</Trace>

<Trace level="3" type="T">Creating HTTP-client</Trace>

<Trace level="3" type="T">HTTP-client: creation finished</Trace>

<Trace level="3" type="T">Serializing message object...</Trace>

<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

<Trace level="3" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

<Trace level="3" type="T">HTTP-client: response received</Trace>

<Trace level="3" type="T">HTTP-client: checking status code...</Trace>

<Trace level="3" type="T">HTTP-client: status code = 200</Trace>

<Trace level="3" type="T">Deserializing message object...</Trace>

<Trace level="3" type="System_Error">HTTP-client: error response= <html> <head> <title>SAP J2EE Engine Start Page</title> </head> <frameset framespacing="0" border="0" rows="90,*" frameborder="0"> <frame name="banner" scrolling="no" noresize target="contents" src="top.html" marginwidth="0" marginheight="0"> <frame name="main" src="main.html" marginwidth="10" marginheight="30" scrolling="auto"> <noframes> <body> <p>This page uses frames, but your browser doesn't support them.</p> </body> </noframes> </frameset> </html></Trace>

<Trace level="3" type="T">HTTP-client: closing...</Trace>

</Trace>

</Trace>

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">

<Trace level="3" type="T">Persisting message Status = 023</Trace>

<Trace level="3" type="T">Message version 001</Trace>

<Trace level="3" type="T">Pipeline SENDER</Trace>

</Trace>

</Trace>

<Trace level="1" type="T">SystemError message generated. Guid: 21F0AE2C2FC02A43A60784FB49F42781</Trace>

<Trace level="1" type="T">Error during execution of message : 4FD44C8345E6354CB65C1C46E9C56FA1</Trace>

<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 4FD44C8345E6354CB65C1C46E9C56FA1</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="3" type="T">Persisting message Status = 023</Trace>

<Trace level="3" type="T">Message version 000</Trace>

<Trace level="3" type="T">Pipeline SENDER</Trace>

</SAP:Trace></b>

Can any one help me to slove this problem.

Thanks,

Nagarjuna.

[Former Member]

Hi,

In the Integration Builder(Desin)->Objects->SAP BASIS->SAP BASIS 6.40->http://sap.com/XI/Demo/Agency->Adapter Objects->CommunucationChannelTemplate. Open the XIDemoChannel_WebServiceSOAP.

In the Connection Parameters the "Target URL" is showing <b>http://host:port/sap/bc/srtxip/sapi/SXIDAL_FLIGHTSEATAVAIL_CHECK?sap-client=107</b>.

Is this correct?

I configured the Demo:CheckFlightAvailability only and the clients are 105 & 106. I don't know how 107 came here.

Please help me.

Thanks,

Nagarjuna.

[stefan_grube]

Hi Nagarjuna,

The XI demo examples assume that you you different clients for communication with proxy and RFC. So usually you have:

105: Sender

106: Proxy Receiver

107: IDOC/RFC/WebService Receiver

If the client 107 does not exist, change the URL to an existing client: http://host:port/sap/bc/srtxip/sapi/SXIDAL_FLIGHTSEATAVAIL_CHECK?sap-client=106

Regards

Stefan

[Former Member]

Hi,

I only configured the clients 105 and 106 Proxy-Proxy.

And I used the communication channel "GeneratedReceiverChannel_XI".

I am getting the Error Message: Envelope missing from SOAP message header.

Do i need to edit the http://host:port/sap/bc/srtxip/sapi/SXIDAL_FLIGHTSEATAVAIL_CHECK?sap-client=107 to 106???

Thanks,

Nagarjuna.

[stefan_grube]

Is this URL in your receiver channel GeneratedReceiverChannel_XI?

In this case change the URL to http://host:port/sap/xi/engine?type=receiver

Regards

Stefan

[Former Member]

Hi Stefan,

In the GeneratedReceiverChannel_XI, I provided the following info:

<b>Addressing Type: URL Address

Target Host: <myhost name>

Service Number: 8001

Path: /sap/xi/engine?type=receiver</b> After this I saved and activated GeneratedReceiverChannel_XI .

Now, started executing the Demo example from Client 105.

The Demo examples BSP opens and I selected the first Scenario : Check Flight Seat Availability and "Start".

<b>Airline: Lufthansa

Flight Number: 0400

and "CheckAvailability".</b>

But still I am getting the same error.

Thanks,

Nagarjuna.

[stefan_grube]

Hi Nagarjuna,

The question is, if this communication channel is taken for your outbound call. Check in SXMB_MONI which channel is taken (as you have a sync call, you might to have to increase the logging level.)

The next idea is: When you have taken the adapter template for the SOAP channel, check out that your adapter type is XI (not SOAP).

Regards

Stefan

[Former Member]

Hi Stefan,

I removed the body { font-family:tahoma,helvetica,sans-serif;color:#333333;background-color:#FFFFFF; }td { font-family:tahoma,helvetica,sans-serif;font-size:70%;color:#333333; }h1 { font-family:tahoma,helvetica,sans-serif;font-size:160%;font-weight:bold;margin-top:15px;margin-bottom:3px;color:#003366; }h2 { font-family:verdana,helvetica,sans-serif;font-size:120%;font-style:italic;font-weight:bold;margin-top:6px;margin-bottom:6px;color:#999900; }p { font-family:tahoma,helvetica,sans-serif;color:#333333;margin-top:4px;margin-bottom:4px; }ul { font-family:tahoma,helvetica,sans-serif;color:#333333;list-style-type:square;margin-top:8px;margin-bottom:8px; }li { font-family:tahoma,helvetica,sans-serif;color:#33333;margin-top:4px; }.emphasize .note a { font-family:tahoma,helvetica,sans-serif;text-decoration:underline;color:#336699; }a:visited a:hover { text-decoration:none; } also.

Thanks,

Nagarjuna.

[stefan_grube]

Hi Nagarjuna,

Could you describe more exactly, what steps you have done and when does the message occur?

Regards

Stefan

[Former Member]

Hi Stefan,

I followed the steps in DemoConfGuide.pdf and provided HTTP Destination for 105 client and 106 client.

And from 105 I started executing the Demo: CheckFlightAvailability . I selected LH 0400 and submit.

Then it gaves me the Error message: Envelope missing from SOAP message header.

Thanks,

Nagarjuna.

[Former Member]

Hey,

just chk out this link which defines in detail about soap message and how it has to be declared

/people/padmankumar.sahoo/blog/2005/02/15/an-overview-of-soap

regards

jithesh