Synchronous message interface processes as Asynchronous

I have a message interface define as Outbound - Synchronous. But when it processes it shows it being an Asynchronous message. My response message mapping never executes.
Thanks,
Jim

Priyanka,
Here is the situation. This process works in XI 2.0 and I am trying to convert it to XI 3.0 The message interface is defined as outbound-synchronous. This automatically forces me to define the Output message and the input message. Because of this definition, the message mapping allows me to define the request message mapping and the response message mapping.
Basically the scenario is I receive an XML file that is mapped to an RFC that is sent to SAP R/3. This RFC creates a sales order.
When the scenario is executed, the request message mapping executes because the sales order is created in R/3. However the response message mapping never seems to executes.
The message interface is defined as Synchronous, but it shows in the message monitor as Asynchronous.
So I do not understand your question about "Do I have a corresponding inbound sync message interface".
The fact that the message interface is marked as synchronous and it has the output and input message types defined, I would have to say that this is the corresponding inbound message interface. This is how I have defined it in XI 2.0 and it works. Is there something different with XI 3.0 that maybe I am missing?
Thanks,
Jim

Similar Messages

Sync to Asyn Message interface mapping

Hi all,
I have a scenario where source message interface is a sync interface and target is async. Can any body suggest if it is possible to map the request message structure of source to target (async) and the response need to have a fixed value.
Is it required to use BPM or is it possible without BPM. Can any body please suggest? Any help will be appreciated.
Thanks
-Kulwant

Hi,
Defining Sync/Async Communication
Use
To enable the communication between a synchronously calling business system (synchronous outbound interface) and an asynchronously called business system (asynchronous inbound and outbound interface), you can define a sync/async bridge in an integration process. You can only define one sync/async bridge for each integration process.
You can also achieve sync/async communication by using the JMS adapter. If you do not have any particular demand for monitoring or for troubleshooting, SAP recommends that you use sync/async communication in the JMS adapter instead. The advantage of using the JMS adapter over synch/async communication using an integration process is a significant increase in system performance.
See: Async/Sync and Sync/Async Bridge in JMS Adapter
We use Sync/Async bridge to establish the Sync communication between the Applications.
Normally the Technical adapters like File will not support the Sync communication to send back the Response to the Sender system from the File system.
So in this case we will use Sync/Async bridge to establish the connection using BPM.
Check these
Bridging the Sync-Async bridge with Fork (XI)
Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi
Structure of a Sync/Async Bridge
The following table outlines the minimum components of a sync/async bridge:
*Step
Use*
Receive step to open the sync/async bridge
Receives the message request from the synchronously calling business system and opens the sync/async bridge
Asynchronous send step
Sends the received message asynchronously to the asynchronously called business system
Receive step
Receives the message from the asynchronously called business system
Send step to close the sync/async bridge
Sends, for example, the response from the asynchronously called business system to the synchronously calling business system
Performance Considerations
If you insert additional steps in the sync/async bridge, the synchronous time is increased correspondingly. If the time that elapses before the sync/async bridge is closed is too long, this can lead to problems.
Fault Messages
It is currently not possible to send fault messages back to the synchronously calling business system. If you want to return error statuses to the synchronously calling business system, you can define a field for an error indicator in the message that is sent to the synchronous interface.
Procedure
Define a Receive Step to Open the Sync/Async Bridge
1. Insert the receive step to open the sync/async bridge in the integration process.
*You can do this at the following points: *
Directly after the start marker
As the first step in a block if the block is the first step of the integration process and if it has the mode Standard
As the first step in a fork. If the fork already contains some starting receive steps, the Start Process indicator is automatically reset for these steps.
2. In the object area, define the container element that receives the synchronously sent message.
Specify an asynchronous, abstract interface in the container element. The message must correspond to the request message of the synchronous interface used to receive the message.
3. Select this container element in the Message field in the properties area of the receive step.
4. In the Mode field, select Open S/A Bridge.
5. Select the Start Process field.
The receive step to open the sync/async bridge must start the integration process. There must be no other receive steps to start the integration process.
6. Specify the synchronous interface for receiving the message from the synchronously calling business system. The message type of the message to be received and the request message from the synchronous interface must be identical.
Define an Asynchronous Send Step
7. Insert a send step that sends the received message asynchronously to the asynchronously called business system.
See also: Sending Messages from Integration Processes Asynchronously
Define a Receive Step
8. Insert a receive step that receives the message from the asynchronously called business system.
Define a Send Step to Close the Sync/Async Bridge
9. Insert the send step at the required position in the process definition.
Do not insert the send step in a loop, block, or fork.
10. In the Mode field, select Close S/A Bridge.
The integration process must not contain any further send steps to close a sync/async bridge.
11. In the Opened By field, specify the receive step that opened the sync/async bridge.
12. In the message field, specify the message that is sent to the synchronous interface.
This message must be of the same type as the response message from the synchronous interface that you specified in the opening receive step.
Example
You can find an example of a sync/async bridge in the Integration Repository under SAP Basis à SAP Basis 6.40, namespace http://sap.com/xi/XI/System/Patterns under BpmPatternSyncAsyncBridge.
For a description of the example, see Example: Sync/Async Communication.
BPM is an additional advantage of Netweaver XI. it provides features like Sync-Async Bridge, Async-Sync Bridge, stateful msgt processing.....so on.
Sync-Async Bridge acts as a bridge between a synchronous Business system and Asynchronous business system.
forex: if u r communicating with a synchronous RFC to a File system(always asynchronous, which is not able to send any response to synchronous RFC Interface).
In this kind of scenarios BPM Sync-Async Bridge enables communication between a Synchronous RFC to Asynchronous File system or vice versa..
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages
Plz go thru the following:
- Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] - Use of Synch - Asynch bridge in ccBPM
Asyn - Synch BPM -
http://help.sap.com/saphelp_nw70/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/43/65d4dab39b0398e10000000a1553f6/content.htm
Example on Sync/Async communication:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/65d4dab39b0398e10000000a1553f6/frameset.htm
Thanks,
Swathi

SOAP XI scenario, ambiguity in Abstract Message Interface

Hi Forum,
I have a SOAP client(synchronous)--->XI scenario,
let me describe the scenario,
Step1. SOAP client sends a SOAP request to the BPM in XI, using a synchronous receive step (Abstract synchronous MI),
Step 2. in BPM, it does some transformation
Step 3. the response of the step 2, is then sent as the response for the SOAP client request, using a Synchronous send (sync async bridge maintained),
Step 4. i use the abstract Synchronous MI (for the SOAP client to send request), to create a WSDL, and use it in ALTOVA to create SOAP request automatically,
now the problem is, In integration builder, Design,.........
when i make the abstract Synchronous MI (for the SOAP client to send request), i use 2 message types RequestMessage (output message) and ResponseMessage (input message), ******sounds bit oppsosite ..but it is like that only......but the source of ambiguity
but when i create the WSDL using the web service creation tool, in integration builder, Configuration, ....... the WSDL is bit unexpected, it shows input as ResponeMessage and output as RequestMessage....hmm.....as such i cant use that WSDL in any tool like altova to create the SOAP request automatically....
****the source of all ambiguity is....in the screen for creating the Message interface (as Synchronous abstract/outboud), we give OUTPUT MESSAGE as the input message type and vice versa...
do u agree.......
am i wrong?
in that case how can i make a correct WSDL

Let us discuss point by point.
You are doing a scenario SOAP to XI with no end point on the other side. Means you are using XI as the end point for simulating. This is my assumption.
Step1. SOAP client sends a SOAP request to the BPM in XI, using a synchronous receive step (Abstract synchronous MI),
Ok.
Step 2. in BPM, it does some transformation
Ok
Step 3. the response of the step 2, is then sent as the response for the SOAP client request, using a Synchronous send (sync async bridge maintained),
You should not use a synchronous send step here. You should be using an Async send here. The sync asyn bridge must start in the first receive step and end here.
Step 4. i use the abstract Synchronous MI (for the SOAP client to send request), to create a WSDL, and use it in ALTOVA to create SOAP request automatically,
You shuld create the WSDL for the Outbound Synchronous message interface which should have been created to supply the message to Abstract Synchronous interface. Then only you will be able to test the message.
So.. you need totally
1. OB Syn MI
2. Abstrac Syn MI (Receive in BPM)
3. Abstract Async MI (to send response to SOAP caller)
VJ

Data &message types,message interface, interface&message mapping

hi
I am very new to XI, i want to know about
1) Data Types
2)Message Types
3)message interface
4) interface mapping
5)message mapping
i am totally confused with eachother, can you please give me the clear definitions for these things
regards
pradeep

Hi Pradeep,
A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged
->A data type is a basic unit for defining the structure of the data for a message type and, as a result, for the message to be exchanged.
A data type is an XML Schema Definition (XSD). This definition determines how the valid payload of a message will look. Data types in XML schema are only an abstract description of a structure that you can assign to elements in an XML schema definition. A message type or a fault message type that references a data type determines the name of the root element of a message.
Ref link
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
2)Message Types
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.
· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.
3)message interface
You use a message interface to describe a platform-independent or programming-language-independent interface, which you want to use to exchange messages between application components using SAP Exchange Infrastructure.
4) interface mapping
Interface mappings register your mapping program for an interface pair in the Integration Repository.
5)message mapping
A message mapping refers to a mapping of messages and is supported by a graphical mapping editor. The editor enables you to design a structure mapping between any two XML structures and connect to a value mapping.
Follow these Ref Link for all answers...
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Regards,
Ramesh.

Message interface in synchronous mode but run in asynchronous

I try to use SAP-XI in synchronous mode with JDBC to JDBC connection.
A 'Outbound' message Interface under synchronous mode is defined for
sender while an 'Inbound' message interface under synchronous mode is for
receiver.
In the sender communication channel, a "select" SQL statement is
placed for getting data via JDBC.
For inbound interface, a stored procedure is triggered and it will
return 2 paramaters.
From transaction SXMB_MONI, I found that the message was in 'asynchronous'
mode and I don't know how to collect the 2 output paramters.

Dear all,
Upon all your suggestions, my testing have a big jump with below results but still have some problem
In the sender communication channel, a "select" SQL statement is placed for getting data via JDBC. It works.
For inbound interface (receiver), below stored procedure was actually triggered and it DOES return 2 paramaters.
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:MT_t1 xmlns:ns0="http://xxx.xxx.hk/zxxxx/jdbc">
<update>
<storedProcedurename action="EXECUTE">
<table>LIBRARY.PANSYTEST</table>
<TRNX_TYPE IsInput="TRUE" TYPE="CHAR">001</TRNX_TYPE>
<TRNX_NO IsInput="TRUE" TYPE="CHAR">101048</TRNX_NO>
<OUT_TRNX_TYPE IsOutput="TRUE" TYPE="CHAR">001</OUT_TRNX_TYPE>
<OUT_TRNX_NO IsOutput="TRUE" TYPE="CHAR">101048</OUT_TRNX_NO>
</storedProcedurename>
</update>
</ns0:MT_t1>
Then I got the response message from the inbound interface
<?xml version="1.0" encoding="utf-8" ?>
<ns0:MT_t1_response xmlns:ns0="http://xxx.xxx.hk/zxxxx/jdbc">
<update_response>
<response_1>
    <update_count>0</update_count>
    </response_1>
    <OUT_TRNX_TYPE>001</OUT_TRNX_TYPE>
    <OUT_TRNX_NO>101048</OUT_TRNX_NO>
    </update_response>
</ns0:MT_t1_response>
This response message was mapped to below message type. I suppose this will be passed
to outbound system (sender) and run a SQL "Update ps_cu_pg1iawd set cu_retrieved_by = "ZCU_CUSIS"
cu_action_cd = 'P' where cu_trx_type = 001 and cu_trx_num = 101048"
BUT the table ps_cu_pg1iawd is NOT updated and NO error was found in SXMB_MONI.
    <?xml version="1.0" encoding="UTF-8" ?>
<ns0:MT_Response xmlns:ns0="http://xxx.xxx.hk/zxxxxx/jdbc">
<statement>
<PS_CU_PG1IAWD action="UPDATE">
    <table>ps_cu_pg1iawd</table>
<access>
    <cu_retrieved_by>ZCU_CUSIS</cu_retrieved_by>
    <cu_action_cd>P</cu_action_cd>
    </access>
<key_1>
    <cu_trx_type>001</cu_trx_type>
    </key_1>
<key_2>
    <cu_trx_num>101048</cu_trx_num>
    </key_2>
    </PS_CU_PG1IAWD>
    </statement>
</ns0:MT_Response>

Abstract asynchronous message interface for fault (exception) messages

Hi,
Has anyone yet discovered how to create an abstract asynchronous message interface for a fault message so that said message can be referenced in an Integration Process? I am currently at a loss as to how to reference the exception message returned by a synchronous RFC call, and how to return the fault message of a synchronous MI from a BPM.
Thanks for any help you can provide on this issue - please do not refer me to existing blogs or forum messages if they do not specifically answer this question in a positive manner. I have just been through the SAP Notes and the SDN forum and Google and while I have seen many questions about this topic I have not seen any answers.
Stephen

hi stephen,
never worked on this but out ofcuriosity after seeing ur question i tried to create one:
but i found these:
fault message types will only be used in case of synchronous messages.....if it is asynchronous the fault message type radio button it self will not seen while creating message interface..just check.
you need to create a Fault message type to use it in an interface...u can add your own fields also if u want.
in your present case you mentioned you are using synchronous RFC...try creating a synchronous abstract interface there you can give fault message type also...just check by creating one...
correct me if i am wrong...
regards.

Error: Message interface is not used by this process Netweaver PI 7.0

Hi All,
I am receiving this error in file to idoc scenario. The file is being picked up by communication channel. Then through an interface mapping IM_MET_ROUTE is being forwarded to a BPM MET_FILE_ROUTE. The MET_FILE_ROUTE forwards it to different BPM depending on file type. whenever I am posting a file it is not reaching IM_MET_ROUTE and giving an error as shown below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please suggest any solution to remove the error.

Hi All,
Thanks a lot Vikrant for your suggestion. The error is resolved. This was not a configuration problem. This was a design problem. Initially I also looked for configuration changes but that was correct hence I came to conclusion that this might be a design isuue.
These are the steps that we should follow to resolve the errors
1. First Check your configuration again and again with test tool and payload to find where exactly your configuration is failing.
2. The above step will not be successful since we are already receiving the error.
3. The above test will fail in interface determination step.
4. Please go through the interface determination in Integration repository(PI 7.0).
5. Check whether all interface mapping,source and target message interface are proper or not.
6. if receiver or sender of message is an BPM please look into their receiver and sender element message type.This must match with the one specified in Interface mapping defined within Integration directory( in the interface deterination step).
In my case the sixth step above was the solution.

BPM : Message interface is not used by this process

Hi,
In BPM : to pass the message facing error as below.
Messages not reflecting in BPM monitor.
I have configured Recveiver - transformation - sender in BPM.
In recvier in BPM is configured with Abstract Type as same in the message mapping.
Is there any thing i am missing?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have refered links but not able to get the clue for this error as its from the Call adapter.
error: Message interface is not used by this process Netweaver PI 7.0
BPE_ADAPTER: MESSAGE_NOT_USED
Regards,

Hi,
I just saw your IP design and from this I can see that you have message mapping between Sender(as in Outbound interface MIOASY) and abstract interface (as in MIAASY) and then in that you have used transformation step to utilise Interface mapping which is between same abstract interface which is not required at all as message type for both the interfaces is same. For me, what your configuration would be is
1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used
2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)
3. Interface determination between
    a. Sender and Outbound interface and Abstract interface with interface mapping IM_Sender
    b. IP as sender with abstract interface MIAASY and receiver interface MIIASY with no interface mapping being used as it must be of same type as receiver interface is
4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.
If I am assuming it correct then if you see then inside BPM we are not using receiver interface MIIASY which is why I feel this error is coming.
However, if you design it something like this then I feel the error would get resolved
Design
1. Make one abstract interface (MIAASY_Sen) of same type as sender, and create another abstract interface (MIAASY_Rec) of same type as your receiver message type
2. Create message mapping between sender message type and receiver message type, Interface mapping IM_ABS - (MM_ABS_ABS) between sender abstract interface (MIAASY_Sen) and receiver abstract interface (MIAASY_Rec)
3. BPM should be something like this
   Container:*
rec Abstract Interface MIAASY_Sen
send Abstract Interface MIAASY_Rec
Receiver (rec) - Transformation (IM_ABS) - sender (send)
Configuration
1. Sender agreement to fetch the message from outbound interface(MIOASY) utilising communication channel with whatever adapter you have used
2. Receiver Determination with Sender and sender interface as MIOASY while receiver as IP(Integration process)
3. Interface determination between
    a. Sender,Outbound interface MIOASY and Abstract interface MIAASY_Sen with no interface mapping
   b. IP as sender with abstract interface MIAASY_Rec and receiver interface MIIASY with no interface mapping being used as it is of same type as receiver interface is
4. Receiver agreement with MIIASY being used as receiver interface and communication channel utlililsed to convert it into receiver format.
Let me know if it works.
Regards,
Amit

Message interface is not used by this process

Hi,
I´ve created a process to get a txt file in the O.S., verify this file and create another file. This verify I´m using BPM but there is an error message:
"SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message interface is not used by this process</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>"
Could you help me,
thanks,
Renato

Hi Renato,
Can you please elaborate what you did you do to eliminate the problem. I am facing the same one now.
A file is received followed by FCC and then a interface mapping is to be called. somehow the system is unable to find the necessary mapping and giving this error.

Integration Process Referencing Message Interfaces In A Different SWCV

Hello Experts!
I am creating an Integration Process IP within SWCV A, using an Interface Mapping Object within SWCV A, Abstract Message Interface MI_A1 from SWCV B and Abstract Message Interface MI_A2 from SWCV B.
Because we have the dependencies set up in the SLD wherein SWCV A is a dependent SWCV of SWCV B, these basis objects can be referenced by the IP during the create process.
However, when I try to execute a "check" or activate the IP, I get the following error:
Expression must return the interface type MI_A1
Expression must return the interface type MI_A2
If I copy the MI objects into SWCV A, the IP is activated successfully.
The question is:
Why is it that while I'm creating the IP I am able to reference these basis objects, but the "check" or "activate" does not allow it? What is this error telling me?
Want more points? Appreciate any insight.

Thanks for pointing me to the right direction, Aamir.
It turned out that the problem was caused by one of the Message Interfaces used by the Interface Mapping. It had errors to where it was pointing to an inactive IDoc object. The bad MI caused the IM to be bad, that eventually caused the problem while creating the Integration Process.
Thanks again!
H.

Avoid processing of Duplicate Synchronous Messages

Hi,
I have two synchronous messages coming with almost zero delay in it. Both the messages contains the same data which is causing a major problem in the backend.
I want to avoid the processing of duplicate message. My scenario is HTTP to SOAP (sync)...
The option that I thought of are:
- Using BPM so that messages can be sent sequentially to backend and there it can be checked for duplicate entries (client is not ready to use BPM)
- Providing Delay in Message Mapping...(I will end up with same issue as same amount of delay will be provided to both the messages may or may not but dont want to take risk)
- I cant make a look up to see if entry already exists as the difference between incoming duplicate messages are so small that it will not give the desired result.
Also thought of creating message ID in URL only but it is not possible with QOS BE.
Is there any way through which I can process the sync messages in sequential way... or something that will avoid processing
of duplicate messages?
Any thought?
Thanks,
Sunil Singh

Hi Sunil,
Checking the data weather is duplicate or not (ie, its already resides in Rev application) would sure require to use of lookup or BPM.
>
SUNIL SINGH wrote:
> I want to avoid the processing of duplicate message. My scenario is HTTP to SOAP (sync)...
even if the data is comming with some delay between them. how will you check that is duplicate message or not unless you use lookup or BPM in it to compare two independent messages at runtime.
My idea would be! instead of trying to put a validation at PI.
check in the source system whats causing their application to generate duplicate messages in first place and send it to PI.
check whats the issue over there and ask them to rectify it or rather not to trigger duplicate data. (it would be easier to control this from source application).
PS: even if we find a way to stop duplicate messages to be processed inside PI. its unnecessary load for PI.
-->Senthilprakash.

Failed Asynchronous Messages still processing

Hi,
Scenario: Asynchronous
QoS: EO
SAP > PI > 3rd Party
I have an almost 1500 failed messages in my SXI_MONITOR SAP PI with an error of 'No Receiver Determination'. I have already solved the issue and the future messages were successful. However, the 1500 failed messages are still being pushed/processed, which is taking up too much memory.
How do you stop these failed messages in processing?
Is there a way that when a failed message already fails, it would stop pushing/processing in SAP PI?
thank you.

Hi,
I think your team mates or BASIS team might have already set a background job for re triggering failed messages in ABAP stack .
If you don't want those messages then you can cancel those in SMQ2/SXMB_MONI.
Regards
Venkat

Message Interface not running as synchronous

Hi,
We have an synchronous interface which was running fine. We then applied SP18. This inerface now only runs in asynch mode.
Has anybode experienced this before.
Thanks
Martin

Hi Ram,
There can be two possibilities....
1. Either you might not have added your Message Interface to the Business service . If added..
2. you need to check whether the Interface direction is set to inbound in the IR.
Regards
Gopi

Statistics (overview) for Synchronous messages processed via AAE

Hello,
We are on PI 7.11
Is there any way to get synchronous messages processed via AAE displayed on RWB Message Monitor Overview view?
Maybe there is some parameter available similar to messaging.syncMessageRemover.removeBody for persisting payloads for sync messages.
Thanks!
Best Regards,
Artsiom Anichenka

Mark,
But I think there is already (PI 7.11) a possibility to persist payloads for java-only sync messages. I was mentioning this parameter in my original post:
messaging.syncMessageRemover.removeBody
this parameter is true by default and if you set it to false payloads will not be deleted, but this is not our aim. We want payloads to be deleted from sync messages, but we also want to see those messages on RWB MessageMonitor for overview.
For me this is somekind of frustrating that the overview page doesn't really give you overview of what is happening on your system, like what and how many messages where processed...
So can you please specify what is really planned for 7.31. Did you meant that parameter I am mentioning above or we will really get sync java-only messages to overview?
Best Regards,
Artsiom Anichenka

Message Interface for HTTP to JDBC synchronous scenario

Hi Experts,
Could you please explain the Message Interface from the below blog. Actually, I am confused with the Outbound Interface. Is it correct?
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response
1. LoginData_Sync_OUT_MI
Input Message : Role_MT
Output Message : LoginData_MT
2. LoginData_DB_Sync_IN_MI
Input Message : LoginData_DB_DT
Output Message : Dummy_DT
Regards
Sara

Hi All,
Here is my Interface mapping's problem details.
Scenario : I have to pass EmpId as a request from webservice to JDBC, If we have the EmpId address in the JDBC then we have to return the address of the employee as a response to Webservice.
Please find the below datatype, message type and etc., which I have used it for the scenario.
1. Data Types:
a) DT_REQUEST ( Webservice to XI request)
     1. EmpId
b) DT_JDBC_REQUEST ( XI to JDBC request)
     1. EmpId ,2. EmpName, 3. Company,4. AddressLine1
     5. AddressLine2,6. City,7. State
c) DT_JDBC_RESPONSE (JDBC to XI response)
     1. EmpId ,2. EmpName, 3. Company,4. AddressLine1
     5. AddressLine2,6. City,7. State
d) DT_RESPONSE (XI to Webservice response)
     1. EmpId ,2. EmpName, 3. Company,4. AddressLine1
     5. AddressLine2,6. City,7. State
2. Message Type created according to the Data Type.
3. Message Interface:
a) MI_Outbound
<b>Output Message :</b> MT_REQUEST
<b>Input Message :</b> MT_JDBC_RESPONSE
b) MI_Inbound
Input Message : MT_JDBC_REQUEST
Output Message : MT_RESPONSE
4. Message Mapping:
a) MM_REQUEST[EmpId mapping]
Source Message : MT_ REQUEST
Target Message : MT_JDBC_REQUEST
b) MM_RESPONSE [Mapping for all the fields]
<b>Source Message : MT_JDBC_RESPONSE
Target Message : MT_RESPONSE</b>
5. Interface Mapping
IM_WEB_DB
Source Interface : MI_Outbound
Target Interface : MI_Inbound
Request :
Source Message : MT_REQUEST
Target Message : MT_JDBC_REQUEST
Response :
<b>Source Message : MT_RESPONSE
Target Message : MT_JDBC_RESPONSE</b>
Here the source Message should be MT_JDBC_RESPONSE and the Target Message should be MT_RESPONSE. But when I tried to create the Interface Mapping I am getting the above bolded Response Messages automatically populated by XI.
Actually, I have followed Siva's blog to do this scenario. Finally confused with the Interface Mapping's response messages. So, please help me out with this scenario steps.
Regards
Sara

Synchronous message interface processes as Asynchronous

Similar Messages

Maybe you are looking for