Determinations for a szenario without BPM

[Former Member]

Hi,

if I would like to create a WebService -> XI -> DB szenario

without BPM, how often I have to use the wizard (for agreements

and determinations)?

Normally with BPM, I needed three:

1) Webserivce BS to XI

2) XI to DB

3) XI to WebSerivice

But without BPM I thought I need just one wizard walkthrough:

1) sync. Webservice to sync. DB call

But I received the following error:

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

- <!-- Receiver Identification

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>No receiver could be determined</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

So it seems something missing...

Any ideas?

Thanks

regards

chris

[Former Member · Accepted solution]

Hi Christian,

Check in your sxmb_moni trace and see if all your business services, receiving interfaces and other configs same in your directory and during runtime.Also do an SXI_CACHE refresh, and activate all your objects again.

cheers,

Prashanth

P.S Please mark helpful answers

[Former Member · Accepted solution]

Hi,

I reactivated themand clear cache, but still same problem.

My trace:

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

- <!-- Receiver Identification

-->

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <SOAP:Header>

- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>SystemError</SAP:MessageClass>

<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>

<SAP:MessageId>456AF5D9-AB80-5A2C-E100-00000AFBCF14</SAP:MessageId>

<SAP:RefToMessageId>C8628B40-7E26-11DB-A03C-0003BACE8C09</SAP:RefToMessageId>

<SAP:TimeSent>2006-11-27T14:51:37Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service />

<SAP:Interface namespace="" />

</SAP:Sender>

- <SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service>BS_EP7_SOAP</SAP:Service>

<SAP:Interface namespace="http://test.ri/CMDBWithoutBPM">MI_CMDB_request</SAP:Interface>

</SAP:Receiver>

<SAP:Interface namespace="http://test.ri/CMDBWithoutBPM">MI_CMDB_request</SAP:Interface>

</SAP:Main>

- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:QualityOfService>BestEffort</SAP:QualityOfService>

</SAP:ReliableMessaging>

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="RCVR_DETERMINATION"><b>NO_RECEIVER_CASE_BE</b></SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>No receiver could be determined</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

- <SAP:Hop timeStamp="2006-11-27T14:51:37Z" wasRead="false">

<SAP:Engine type="AE">af.xit.xidscbi</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>

<SAP:MessageId>C8628B40-7E26-11DB-A03C-0003BACE8C09</SAP:MessageId>

<SAP:Info />

</SAP:Hop>

- <SAP:Hop timeStamp="2006-11-27T14:51:37Z" wasRead="false">

<SAP:Engine type="IS">is.01.xidscbi</SAP:Engine>

<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>

<SAP:MessageId>C8628B40-7E26-11DB-A03C-0003BACE8C09</SAP:MessageId>

<SAP:Info>3.0</SAP:Info>

</SAP:Hop>

</SAP:HopList>

- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Date>20061127</SAP:Date>

<SAP:Time>155137</SAP:Time>

<SAP:Host>xidscbi</SAP:Host>

<SAP:SystemId>XIT</SAP:SystemId>

<SAP:SystemNr>01</SAP:SystemNr>

<SAP:OS>SunOS</SAP:OS>

<SAP:DB>ORACLE</SAP:DB>

<SAP:Language />

<SAP:ProcStatus>023</SAP:ProcStatus>

<SAP:AdapterStatus>000</SAP:AdapterStatus>

<SAP:User>PIAFUSER</SAP:User>

<SAP:TraceLevel>1</SAP:TraceLevel>

<SAP:LogSeqNbr>000</SAP:LogSeqNbr>

<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>

<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>

<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>

<SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>

<SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService>

<SAP:QIdInternal />

<SAP:CommitActor>X</SAP:CommitActor>

<SAP:SplitNumber>0</SAP:SplitNumber>

<SAP:NumberOfRetries>0</SAP:NumberOfRetries>

<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>

<SAP:TypeOfEngine client="001">CENTRAL</SAP:TypeOfEngine>

<SAP:PlsrvExceptionCode />

<SAP:EOReferenceRuntime type="TID" />

<SAP:EOReferenceInbound type="TID" />

<SAP:EOReferenceOutbound type="TID" />

<SAP:MessageSizePayload>771</SAP:MessageSizePayload>

<SAP:MessageSizeTotal>3360</SAP:MessageSizeTotal>

<SAP:PayloadSizeRequest>771</SAP:PayloadSizeRequest>

<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>

<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>

<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>

<SAP:Reorganization>INI</SAP:Reorganization>

<SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>

<SAP:InterfaceAction>INIT</SAP:InterfaceAction>

<SAP:RandomNumber>62</SAP:RandomNumber>

<SAP:AckStatus>000</SAP:AckStatus>

<SAP:SkipReceiverDetermination />

</SAP:RunTime>

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

- <SAP:RunTimeItem>

<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="begin" host="xidscbi">20061127145137.380731</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>

<SAP:Timestamp type="end" host="xidscbi">20061127145137.461964</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="begin" host="xidscbi">20061127145137.463046</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="end" host="xidscbi">20061127145137.47029</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>

<SAP:Timestamp type="begin" host="xidscbi">20061127145137.474297</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>

<SAP:Timestamp type="end" host="xidscbi">20061127145137.829578</SAP:Timestamp>

</SAP:RunTimeItem>

</SAP:PerformanceHeader>

- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:TraceLevel>Information</SAP:TraceLevel>

<SAP:Logging>Off</SAP:Logging>

</SAP:Diagnostic>

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

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

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

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</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="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

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

<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="1" type="T">system-ID = XIT</Trace>

<Trace level="1" type="T">client = 001</Trace>

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

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="Timestamp">2006-11-27T14:51:37Z 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 = C8628B407E2611DBA03C0003BACE8C09</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</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 CENTRAL</Trace>

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

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

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

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

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

-->

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

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

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

-->

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

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>

</Trace>

</Trace>

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

</Trace>

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

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

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

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

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

-->

</SAP:Trace>

</SOAP:Header>

- <SOAP:Body>

<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />

</SOAP:Body>

</SOAP:Envelope>

I'm not able to see where the error comes from

regards

chris

[Former Member · Accepted solution]

The error is right here:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>

As Suraj mentioned above, check your reciever determination. But also, what are you using parties for? Is it something that you must use a party for? Have you defined your business systems in the SLD such that you can create a business service without party? This may help solve your reciever determination issue, as I have made that mistake before.

Message was edited by:

Harrison Holland

[Former Member · Accepted solution]

I have defined a BS in SLD and use it as Service without party.

So he didn't use a partner.

The wizard created :

- one rec. determination

- one interface determination

- one sender agreement

- one receiver agreement

I have just created one oubound interface for webservice and one inbound

interface for database call (both sync), 2 mappings (request and response)

and one interface mapping.

so, everything looks fine. but where is the problem??

thanks

[former_member187339 · Accepted solution]

Hi,

Check these:

1) Sender Adapter : Are you seeing any messages here?

2) Receiver Adpter : Are you seeing any messages here?

3) What is QOS for the adapter? It should be BE.

4) In moni what you can see? how many rows?

Regards

Suraj

[Former Member · Accepted solution]

hi,

1) at the soap communication channel I can see two entries:

-call failed

-request received for a channel

where do I see the sender adapter? In RWB when I click on

component-monitoring -> adapter monitoring

he only says : SOAP Adapter Monitoring is now part of Channel Monitoring

in message-monitoring he only shows messages for the soap service

not for the database service.

2) like number one. where can I see this?

3) for sync I use BE

4) in MONI it shows two entries for every try.

first: receiver service : BS_SOAP

receiver interface: database interface

second: sender service : BS_SOAP

sender interface: database interface

[Former Member · Accepted solution]

Chech both your outbound and inbound interfaces in IR. They should both have mode "Synchronous".

Regards,

Jai Shankar

[bhavesh_kantilal · Accepted solution]

Hi,

1. While creating the WSDL , are the details entered like Sender Service, Sender Interafce , etc correct ? Please try to recreate the WSDL and also see in MONI when you message hits XI what is the sender service , sender interface? Is this for what you have created the Receiver Determination?

2. Are you using the same outbound synch message interface for both the BPM and non BPM solutions? If yes, please create a new Message Interafce for your new non BPM soltuion.

Regards,

Bhavesh

[Former Member · Accepted solution]

@Jai

Both, inbound and outbound are synchronous

@Krishna Moorthy P

Creating all caches changes nothing. I sended a message and in sxmb_moni

appeared 2 entries with red lamps.Interessting is, that nowhere stands the

SOAP-interfaces. I would expect that the sender interface is the SOAP

outbound interface

@Bhavesh Kantilal

Because I'm not working with partner, I only entered here dummy entries and it

worked til now. Could it be, that these informations are only necessary for

processes without BPM?

But know I tried the following :

Service: Business system that include soap channel

Interface-Name: outbound interface

interface namespace: outbound interface namespace

but even this didn't work.

<a href="http://www.christian-riekenberg.de/upSkript/up/szenario.JPG">Here ist my szenario.</a> Data and message types are in another namespace.

any ideas?

thanks

chris

[bhavesh_kantilal · Accepted solution]

Chris,

The only strange thing I noticed in the image is that there was no Datatype and message Type. Have you created the same?

just ensure that the SOAP Url is valid. Can you post the SOAP Url you are using?

Like I mentioned , did you check the sender service, sendr interface etc in your MONI? Are they for what the Receiver determination is created?

Regards,

Bhavesh

[Former Member · Accepted solution]

hi,

like I wrote, data and message types are defined in another

namespace. The URL is:

http://<xiserver>:<port>/XISOAPAdapter/MessageServlet?channel=:BS_EP7_SOAP:EP7_UserWithOutBPM_SOAP

(server and port normally are replaced)

If this URL would be wrong, nothing should appear in MONI, or?

The message should go like this:

web service -> MI_EP_request -> MI_CMDB_request -> database

and back. So is it correct, that MONI gives as sender interface MI_CMDB_request?

Do I only need those determination and agreements I did (see picture)?

Or do I need a second wizard walkthrough for returning from database

to web service??

regards

chris

Message was edited by:

Christian Riekenberg

[former_member187339 · Accepted solution]

Hi,

>>http://<xiserver>:<port>/XISOAPAdapter/MessageServlet?channel=:BS_EP7_SOAP:EP7_UserWithOutBPM_SOAP

This is right...

>>The message should go like this:

web service -> MI_EP_request -> MI_CMDB_request -> database

and back. So is it correct, that MONI gives as sender interface MI_CMDB_request?

No it should be MI_EP_request...

>>Do I only need those determination and agreements I did (see picture)?

Or do I need a second wizard walkthrough for returning from database

to web service??

Second wizard walkthrough not required....

Check these...

1) Sender Agreement ( Sender Service: BS_EP7_SOAP Channel:EP7_UserWithOutBPM_SOAP)

2) Receiver Determination( Sender Service: BS_EP7_SOAP Receiver Service: BS_CMDB)

3) Interface Determination (Sender Service: BS_EP7_SOAP Receiver Service: BS_CMDB)

4) Receiver Agreement (Sender Service: BS_EP7_SOAP Receiver Service: BS_CMDB Channel:BS_CMDB)

Before doing this:

1) Add MI_EP_Request in the <b>sender</b> tab of BS_EP7_SOAP

2) Add MI_CMDB_request in the<b> receiver</b> tab of BS_CMDB

Regards

Suraj

Regards

Suraj

[bhavesh_kantilal · Accepted solution]

Hi,

><i>Or do I need a second wizard walkthrough for returning from database

to web service??</i>

No, as both your Message Interfaces are Synch just 1 receievr determination , interface determination and interface mapping.

The URL as well looks good to me.

What you can do is as an alternative, use the SOAP Url given in this blog by Stefan and check if it works.

/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi,

@Bhavesh Kantilal

Your advice to check the MONI for correct receiver determination

let me check the soap channel again and there was a mistake.

I used the inbound interface MI_CMDB_request there damm

I changed it to the correct one and.......no, it don't works, but the

I received another error messeage No I got this one:

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'table_user'(structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ')'.</SAP:AdditionalText>

But I think I've got this error before and will search this forum for this.

Thank you all very much for helping. Points will be given.

regards

chris

[bhavesh_kantilal · Accepted solution]

Hi,

This new error is because of the fact that the JDBC receievr adapter's data format is not valid.

post your Request Message with and the response message you have created for the JDBC call and this can be debugged as well

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi,

thanks, but you all helped enough. I think I will need your energy for

other problems

The last error was because in a key field of my JDBC-Structure

I tried to check a integer field with a LIKE-compareOperation.

Thanks a lot.

reagards

chris

[moorthy]

Hi,

Go to SXMB_MONI and check the Sender Service/Interface and Receiver Service + Reciever Interface. So cross check this with whatever you have configured in the integration directory...

Probably during runtime it is taking osme other interfaces.

Also refresh the cache - go to Integration Builder->Administration->Cache Overview and refresh all the caches..

REgards,

moorthy

[former_member187339]

Hi,

Check you Receiver Determination.

You should have done these:

1) Sender agreement

2) Receiver Determination and Interface Determination

3) Receiver Agreement.

Regards

Suraj