Inbound sync. messagin

Hello -
I have created a message, service, service op to handle a inbound sync request to handle a 3rd party request/response. They used to send us a plain xml document and I think they need to change this xml document header to somthing so when it contacts the listener connector, it knows where to forward the message.. what should this header include? they used to send a plain xml.
Thanks!

The XML structure remains the same as the XSD does not change.
You can either ask them to set the HTTP headers or maybe in the Query Strings
A fully qualified endpoint URL needs to be provided by you to them on which they'll post the XML.
From PeopleBooks:
http://machine1234/PSIGW/HttpListeningConnector?&Operation=
EXAMPLE_SERVICE_OPR.VERSION_1&From=SOURCENODE
So when the third party wants to post an XML to PeopleSoft, they should use a modified version of the URL ...

Similar Messages

"sync-rule-inbound-flow-rules-invalid" error on synchronizing an Inbound Sync Rule from the FIM connector space to the Metaverse

I have created an inbound sync rule in the FIM portal to import groups from an external system (SQL Server) into the metaverse. I can import the rule from the FIM MA into the FIM connector space but when I run a full sync on the FIM MA I get the error
"sync-rule-inbound-flow-rules-invalid". The only way I have found around the error is to remove all the attributes from Inbound Attribute Flow in the sync rule. However, this defeats the purpose of having the sync rule in the first place. Searching
the Web, I have come across posts from other people with "sync-rule-inbound-flow-rules-invalid" problems but the solutions do not seem to work in my situation.
A little background about the sync rule
Metaverse Resource Type: group
External System Resource type: group
Relationship Criteria: accountName (metaverse) = "string field" (ConnectedSystemObject)
Create resource in FIM: yes
Inbound attribute flow:
- Domain
- Member
- DisplayName
- accountName
- MembershipLocked
- MembershipAddWorkFlow
- Type
- Scope
I am new to FIM so it's possible I have overlooked something in the setup of this sync rule. Any suggestions on possible causes of this issue would greatly appreciated.

There is no scope filter. In regards to the attribute flows, no functions are used. Here is further information about the attribute flows
Set up of Inbound attribute flow for the inbound Synchronization Rule.
Metaverse External System (SQL Server View)
- Domain Domain (string)
- Member Member (multi value attribute)
- DisplayName ObjectDescription (string)
- accountName ObjectID (string)
- MembershipLocked 'false' (set up as a string literal)
- MembershipAddWorkFlow 'Owner Approval' (set up as a string literal)
- Type 'Security' (set up as a string literal)
- Scope 'Universal' (set up as a string literal)
Is this the info you were asking for? If not, please clarify what details you are looking for in regards to the sync rule.

PI 7.11 sp6 - SOAP error on INBOUND SYNC (BE) interface - No handler ...

Experts,
We're running a AIX 6.1 unix based PI 7.11 system patched to Stack SP6. We've got one instance...no web dispatcher or load balancing of any kind.
Our proxy system (sender) is an ECC6.0 EHP4 system. Our 3rd party system (receiver) system is non-sap.
In about a 2 hour timespan, we processed 9700 XML messages all in the SOAP adapter. almost all our traffic is BE (sync). Of those messages, we got 11 errors. And here is what we see in XSMB_MONI and in the java default trace:
#2.0^H#2011 08 29 15:40:08:183#0-500#Error#com.sap.aii.adapter.xi.ms.XIEventHandler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#327C4279AB0F2E5C000000010019C0BE#3930552000000004#sap.com/com.sap.aii.af.ms.app#com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(Services, TransportMessage)#PIISUSER#8
546##875E5AD3D27311E0C8580000003BF9B8#875e5ad3d27311e0c8580000003bf9b8#875e5ad3d27311e0c8580000003bf9b8#0#Thread[HTTP Worker [@2008983637],5,Dedicated_Application_Thread]#Plain##
Message 4e5b07b7-8180-00ab-e100-80000ae201a4(INBOUND): was not delivered due to com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PA
RSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> No handler is registered for this service.#
#2.0^H#2011 08 29 15:40:08:081#0-500#Error#com.sap.engine.messaging.impl.spi.ServicesImpl#
#BC-XI-CON-MSG#com.sap.aii.af.ms.svc#327C4279AB0F2E98000000000019C0BE#3930552000000004##com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(Message)#J2EE_GUEST#0##875E5AD3D27311E0C8580000003BF9B8#875e
5ad3d27311e0c8580000003bf9b8#875e5ad3d27311e0c8580000003bf9b8#0#MS Queue Worker [SOAP_http://sap.com/xi/XI/SystemRqst]#Plain##
Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 4e5b07b7-8180-00ab-e100-80000ae201a4(INBOUND)#
So I've looked all over the marketplace and SDN/google. I could not find anyone else getting this type of error.
We have WILY introscope and all the diag tools. I am not seeing any bottlenecks on the threads for http or inbound/outbound queues.
I was hoping someone could point me in the right direction. I was thinking about bumping up all the default queue threads for the com.sap.aii.af.ms.svc service. It has the default "10" for all those.
We have done MAJOR tuning already on this instance. I think I've read all the notes/guides/HOW-TO...etc that there is for PI 7.11. So we are making progress.
Thanks,
NICK

Hi Nick,
From error message i could feel that, there is no problem from PI side and error is at the receiver system side where PI is posting the message. Why i am telling it's not PI issue and it's receiver's issue is that, error message you got is SOAP fault message. Fault message are raised by receiver system if any error occurs. If messgae is processed successfully then receiver system would send proper SOAP response message not a SOAP fault.
soap fault: Server was unable to process request. ---> No handler is registered for this service.#
So, in my view you better check at your receiver system (in your case it's no-sap sytem) why it's giving problem as 'No handler is register for the service'.
Rgards,
RK

Unable to create Inbound Sync Server Proxy - Authorization problem

Im using PI 7.0 . When I try to create a inbound sysnchronous server proxy in SPROXY tcode , I get the following error
Authorization Check failed: S_TCODE with parameters TCD SICF
Im able to create both outbound and inbound asynchornous proxies . What could be the problem?

The JDK/Java that ODI using should be 64bit if ODI 11.1.1.6 is 64 bit. (I think JDK 1.6 is recommended for this ODI version)
Also, for which technology you are creating a data server ? and what error message you are getting while creating it ?
Thanks,
Santy.

In BPM sync/async Step , can you have different message schema?

Scenario:
File to XI to BPM to SOAP to RFC
In order to trigger the webservice , I use a dummy file which will be polled at a certain frequency- once in 30 minutes in Test mode - this will call the Webservice. The answer of webservice is sent to RFC Async.
so these are the Repository objects I created :
1. File Outbound Async Message Interface- Output Message (File_Request_MT)
2.File Abstract Message Interface-Output Message (File_Request_MT)
3.Async/ sync bridge Abstract interface to call the Webservice
4 Webservice Inbound Sync Message interface- with both input and output message
5.RFC Inbound Async message interface- input message (RFC_Request)
6 RFC Abstract Async Message interface-input message (RFC_Request)
BPM
a) Receive step which uses the the object 2.
b) Sync send which uses object 3
c) Send step which uses Object 5
I am using a BPM to Receive the file data/ "request " by using the File abstract message interface
Then use the the object 3 to call the webservice in BPM .
My question is on this step
Can I have for the abstract Interface(Object 3) the Request message as File_Request_MT and
response message as (RFC_Request) ?
I use a message mapping to map Input and Ouput message of Object 3 with Object 4.
Thanks for your insight

Raj,
Thanks for the feedback , but I have a question regarding your reply
Interface Objects
Object 1: File_Request_Abs
Object 2: Soap_Response_Abs
Object 3:Soap_Abs_Synch
Output Message:File_Request_Abs
Input Message:Soap_Response_Abs
Object 4:Rfc_Request_Abs
The question is about
a)SOAP_RESPONSE_ABS : could you please tell me why do we need an abstract interface -SOAP_RESPONSE_ABS?
I created a message type MT_SOAP_RESPONSE and used that in the BPM sync Send step as the Input message.
b)Soap_Abs_Synch- I am using message types
MT_File_request and MT_SOAP_Response From your reponse, it looks like you are suggesting to use
Abstract Interfaces as Output message and Input Message, am I correct? Could you please tell me whether this has advantages over using message types MT_file_request and MT_soap_reponse? I haven't used Abstract interfaces before as Input message and output message; infact, I wasn't even aware that it can be. Please confirm that it is possible. Thank you for increasing my knowledge !!!
These are the Objects I created
Message Type :
a) MT_Filerequest
b) MT_SOAPresponse
Message Interface
a)MI_Filerequest_out_async -
Output message
Mess. type MT_filerequst
b)MI_filerequest_async_abs-
Mess. type MT_filerequst
Used
i) used for BPM receiver step- container definition
ii) receiver determination
c)MI_webservice_sync_in - This is created from External definition
d)MI_webservice_sync_abs-
Input message - MT_soapresponse
Output message- MT_fierequest
Used:
i) used for BPM sync send step ,
ii)Interface mapping between MI_Webservice_sync_in and MI_webservice_sync_abs
iii)Container element-SOAP_response
e) MI_RFC_async_out
Input message
RFC_Request(This is imported from RFC definition)
g) MI_RFC_async_abs
Input message
RFC_Request(This is imported from RFC definition)
Mapping
Message mapping
i)Filerequest_TO_SOAPrequest
Source: MT_Filerequest
Target: SOAPrequest(Got from External definition)
ii)SOAPresponse_TO_BPM_response
Source : SOAPresponse(got from External definition)
Target : MT_SOAPresponse
Interface Mapping
i)IM_BPM_TO_SOAP
Source Interface : MI_webservice_sync_abs
Target :MI_webservice_sync_in
uses following message mapping
Request : filerequest_TO_SOAPrequest
Response:SOAPresponse_TO_BPM_response
BPM container element
i)Receiver_container TYPE MI_Filerequest_out_async
ii)SOAP Responsecontainer TYPE MI_webservice_sync_abs
iii)RFC_Request_container TYPE MI_RFC_async_abs
BPM flow
Receive---->Send Synch-->Transformation----->Send Asynch
Receive -
> receiver_container
Send Synch -
> receiver_container(Request Message), Soap_response_container(Response Message)
Transformation -
> Source(Soap_response_container), Target(RFC_request_container)
Send Asynch -
> RFC_request_container
Thanks for your help!!!

Unable to view Abstract Message Interface(Sync) in Container Step of BPM

Dear Friends,
This is IDOC---SOAP Sync Communication Interface
I have created the External Def by exporting & importing the Standard Idoc
and Imported the WSDL File which has the Request & response Structure
I have created the Outbound Sync message Interface for Idoc side
and Abstract Sync message Interface for the same to use in BPM
and also created Inbound Sync Message Interface for Webservice side
and Abstract Sync Message Interface for the same to use in BPM
Problem is::::
While creating the Container varible inside the Integration Process, i have to select the Abstract Message Interface which i created for Idoc.
But it is not at all visible in the list.
What might be the problem
REgards
Seshagiri

Hi,
I have created
For Idoc side
1) Create O/b Sync by having request of Idoc and response structure of Idoc
2) Create ABS Sync by having the request of Idoc and response structure of Idoc
3) Create ABS Async by having the Request of Idoc Only
For Webservice side
1) Create I/b Sync by having the request of webservice and response of that
2) Create ABS Sync by having the request of webservice and response of that
3) Create ABS Async by having the Response of Webservice only
I created the Steps inside the Integration Process as showed in the screens.
1)Integration Process graph
http://img145.imageshack.us/img145/4848/ipviewwv1.jpg
2)Receive Step
http://img293.imageshack.us/img293/1756/receivepropng8.jpg
3)Send step1
http://img179.imageshack.us/img179/2200/send1bd0.jpg
4)Send Step2
http://img182.imageshack.us/img182/8468/send2wl1.jpg
When i check the F7, it is throwing the error like
http://img247.imageshack.us/img247/4356/errortx3.jpg
Regards
Seshagiri

Triggering a BPM(NW) using sync interface and get the sync response

Hi Folks,
I have a scenario where in I have to trigger a BPM (NW) using a sync interface from a SOAP client by making request to get the response from SAP webservice . If the response from SAP is successful then its a happy path but if it fails or times out then there is an failure mapping to ECC using an IDOC. My question is to achieve the sync process how many synchronous interfaces do I need to use? Please let me know if my design works with 4 sync interface. One outbound sync interface at the source (i.e the request ing system), the other inbound sync interface to the BPM to trigger the BPM, another outbound sync interface within BPM for the request to SAP. the fourth inbound sync interface at the ECC for the response from ECC. Or please let me know if there is a better design option than this.
Regards
Kalyan.

Hi,
Control Step
Use
You use a control step () to do the following:
·        Terminate the current process
·        Trigger an exception
·        Trigger an alert for Alert Management (see also: Triggering an Alert)
Activities
Terminate the Current Process
Choose Terminate Process.
At runtime, the system terminates the current process instance, including all active steps, and sets the status for the process to logically deleted.
Trigger an Exception
Choose Trigger Exception and specify the triggering exception (see also: Exception Handling). The relevant exception handler must be defined in the same block or a superordinate block.
The system triggers the specified exception at runtime.
For more information about using exceptions, see Example: Collecting and Bundling Messages - One Interface.
Proxy..
How to create proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
How to Activate Proxy.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
ABAP Server Proxies (Inbound Proxy)
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
OutBound Proxy (Client Proxy)
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
File to R/3 via ABAP Proxy with good example
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
Debug your inbound ABAP Proxy implementation
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
Thanks,
Satya Kumar

How to implement Sync-Sync scenario in BPM? Please help!

Hi Experts,
I have a Sync-Sync scenario (SOAP - RFC) where both sender as well as receiver are synchronous.
I have created outbound sender sync interface, abstract sender sync interface, Receiver abstract sync interface and Receiver inbound sync interface.
In BPM I have started with Receive step.
But in receive step I can give either Async Abstract interface or Open Sync-Async bridge. I am confused!
How to implement my scenario in BPM?
It will be really great if somebody can send me the step by step info or doc.
Thanks & Regards,
Gopal

Hi,
Refer this link
use synchronous send step in your BPM - http://help.sap.com/saphelp_nw04/helpdata/en/43/6211331c895f6ce10000000a1553f6/content.htm
RFC Scenario using BPM --Starter Kit
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
regards
Aashish Sinha
PS : reward points if helpful

File BPM Webservice IDOC .........Error in BPM workflow(Sync send step)

Hi all,
I have the same type scenario that is file initiates the bpm that invokes the Webservice.the file data goes into bpm as the input data of the webservice and webservice gives the response and then the web-service response is mapped to
idoc and finally posted to R/3.
The interface sI created:
1.outbound Async -
>for file
2. Abstract async----
>bpm reciever step.
3.Abstract sync----
>bpm sync send step.
4.inbound sync -
>for the webservice to recieve the reqst and to send the response to Abstract sync
5.Abstract async----
>to send the data out of BPM
6.inbound async----
for idoc
created 3 communication channel.
1.file adapter: sender
2.SOAP adapter: Recv
3.IDOC adapter: Recv
created 3 reciever determination
Business process instance in ID
reciever agreement(2)
interface determaination
But getting a problem in BPM.
I think the scenario is logically correct as I have seen previous
SDN suggestions.
But getting the problem in BPM's sync step.and the SOAP rec channel is also inactive.in BPM workflow I can see the recv step is getting file req data but after that in the sync send step
its stuck up.getting error.
Please sir suggest me.

Remove the interface you created for Idoc that is inbound async one. use the imported Idoc itself as the interface and also as the message type. Everything else looks good though i did not really evaluate ur ID configuration..
VJ

How to realize a Sync-Asyn Bridge

Hey Folks,
I was trying to 'decode' whatever is written in the How to guide (Realize a sync - async and async - sync bridge in the adapter framework). Thanks to Bhavesh he posted the thread on the Async - Sync part and so i thought i would figure out the Sync - Async part.
Ok so here is what i have done till now (with no success);
its a HTTP <-> XI <-> File
So;
2 DT/MT for HTTP, 2 DT/MT for file
1 MI outbound sync -> http
1 MI inbound sync -> File
the 2 mappings and the 1 IM
In configuration;
1 rec. file adapter and 1 sender file adapter
the configuration is as usual for a sync scenario; except for the sender agreement for the sender file adapter, i configure a dummy sender agreement with dummy interface and dummy namespace but the original CC created.
In the Recv. file channel module part;
1     AF_Modules/RequestOnewayBean     Local Enterprise Bean     2
2     CallSapAdapter     Local Enterprise Bean     0
3     AF_Modules/WaitResponseBean     Local Enterprise Bean     1
2     passThrough     true
in the sender file channel;
1     AF_Modules/NotifyResponseBean     Local Enterprise Bean     1
So any of you guys who did something on that document, i hope can throw some light
Cos i am sure i am missing something here !!!
~~ShaBZ

HI,
Are you using BPM or not??
Can you plz tell me the SP number/version.
I hope Sync - Asyn without BPM is possible with latest SP.
Please see the below links
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
Searching for a BPM scenario
With BPM
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards
Chilla..

Async to Sync Scenario

Hi Experts,
I am doing async JDBC to sync webservice scenario.
I did create async interface for JDBC and sync interface for webservice.
my scenario is i just want to see the response from webservice in XI for trouble shoot, i dont need to send the response message to database.
can anyone tell me how can we do it without using BPM (async to sync bridge).
Kind Regards,
kiran

Hi
Please go through below steps now
I have added the comments with same in bold font
Data Types: JDBC_DT,File_DT
Message Types: JDBC_MT,File_MT
Message Interfaces:
JDBC_OUT_MI(outbound,async),This should be Sync given MT_File as respo
File_MI(inbound,async), Dont use this
WS_IN_MI(inbound,sync,input=WS_req,output=WS_resp)
WS_resp_MI(outbound,async,WS_resp), -----No need of this
Message Mappings:
JDBC_WS_req_MM
(JDBC_OUT(JDBC_MT)------->WS_IN_MI(WS_req) ).
*Here WS_IN_MM msg. mapping should be used insted of*
*WS_IN_MI i.e message interface*
*WS_File_Res_MM*
(WS_Res(Source -- Ws_res) ---> File_MT)
Interface Mapping: JDBC_WS_req_IM(source=JDBC_OUT_MI,target=WS_IN_MI)
In IM you need to use the above one only
Here you have two tabs as Request & Response, Request will be normal as
it is JDBC_MT to WS_Req with proper mapping
*In Response use File_MT <--- Ws_RES with appropriate mapping *
For ID configuration refer below sample scenario,
It is File1 to RFC to File2- Just in your scenario it is JDBC>WS--->File2
So refer and do necessary changes
From SP 19 on XI 3.0 and SP 10 on PI 7.0, a File - RFC - File ( Asynch - Synch ) scenario can be done without a BPM.
Steps:
Integration Repository
The Integration Repository will be similar to any Synchronous Scenario ( say HTTP - RFC ) . 1 Outbound Synch message Interface and 1 Inbound Synch Message Interface.
Integration Directory
This is where a few differences lie, so let me take some time.
1. The Receiver Determination , Interface Determination will be the same as in HTTP - RFC synch scenario. Create the Sender File Adapter, Receiver RFC Adapter and Receiver File Adapter.
2. Sender Agreement will be for the Sender File Adapter. Sender Agreement uses the Synch Outbound Message Interface.
3. Receiver Agreement will be for the Receiver RFC adapter. Receievr Agreement will use the RFC as thge Inbound Message Interface.
4. We need to add a few modules in the Sender File Adapter.
Go to the Modules Tab of the Sender File Adater, and add the following modules in the same sequence,
Number - ModuleName - Type - ModuleKey
code1- AF_Modules/RequestResponseBean - Local Enterprise Bean - 1
2- CallSapAdapter-Local Enterprise Bean - 2
3-AF_Modules/ResponseOnewayBean-3[/code]
Parameters
ModuleKey - ParameterName - ParameterValue
code1 - passThrough - true
3-receiverChannel - Receiver File Adapter Name
3-receiverService - Receiver Business Service/ System[/code]
With this configuration, you can now handle the requirement without a BPM
This feature been already blogged for JMS Adapters in these blogs ,
Sync/Async communication in JMS adapter without BPM (SP19)
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
Async/Sync Communication using JMS adapter without BPM (SP 19)
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
Dynamic Configuration is also possible,and this as well as many other options are discussed in the How To guide - "How To Realize a sync-async and async-sync
bridge within the Adapter Framework" available on the Service Market Place.
For info on the Modules used here, look into these links,
Request Response Bean
http://help.sap.com/saphelp_nw04/helpdata/en/45/20c210c20a0732e10000000a155369/content.htm
Response Oneway Bean
http://help.sap.com/saphelp_nw04/helpdata/en/45/20cc5dc2180733e10000000a155369/content.htm
Hope this info helps,
Thanks
Swarup

ABAP - INTERFACE_REGISTRATION_ERROR for outboud sync ABAP proxy

Hi,
I have created ABAP sync client proxy in R/3 and trying to test using abap report. I am facing following error in XI sxmb_moni.
I have created client proxy for outbound sync interface, however the error is pointing inbound sync interface (ie QAChkR3_Sync_Mimicking).
Even I tried creating proxy for given inbound interface but same error exists.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
<SAP:P1>ifmmessif</SAP:P1>
<SAP:P2>QAChkR3_Sync_Mimicking</SAP:P2>
<SAP:P3>http://ls.att.com/Exacta/QACheck_Mimicking</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No implementing class registered for the interface (type ifmmessif, name <u>QAChkR3_Sync_Mimicking</u>, namespace http://ls.att.com/Exacta/QACheck_Mimicking )</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.
Pratibha.

Hi Krishna,
Proxy in R/3 is reactivated still the error persists.
There are few more o/b proxies which are running fine.
Even LPCONFIG txn is done properly.
I wonder why the error is for inbound proxy when I am trying to test outbound sync proxy.
I dont have sap marketplace id to check the given notes. Will you pls brief about it.
Pratibha.

CcBpm Sync - Proxy

Hi Guys,
I've been trying to get this working since last week monday but I get the same error everytime I try some other approach.
Its a simple Soap -> ECC (sync) -> Proxy interface. If this works I'll add a 2nd interface to the bpm.. Error I get: "The process does not support the given synchronous interface or does not support synchronous messages"
in my bpm I've got 2 container parameters (outbound req & resp). I've got 3 steps in my process,
receive (async) -> send (sync) -> send (async)     - gave me this error so I tried
receiver S/A bridge open -> send (sync) -> send S/A bridge close       - still gave me this error.
My opperation mapping has my outbound sync SI & my inbound sync SI.
Config: soap sender to proxy receiver.
Receiver Detr from soap -> bpm
Receiver Detr from bpm -> ECC
Receiver Detr from bpm -> soap
Any idea where I the issue could be?
Thanks,
Jan

https://service.sap.com/sap/support/notes/856597
Q: To which URL can I send my SOAP message?
           A: The URL for your SOAP sender channel is
           http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c
           where host is the host name, port is the port number, p is the optional party name, s the service name, and c is the channel name, respectively.The URL given above is valid for 3.0/7.0/7.1.
           A new URL syntax is also valid and is recommended to be used. The URL for the SOAP sender channel is
           http://host:port /XISOAPAdapter/MessageServlet?senderParty=FP& senderService=FS& interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace

Developing AIF Inbound Synchronous Proxy interface

Hello! I'm trying to develop simple AIF Inbound Synchronous Proxy interface, but there is absolutely no information about it. Cookbook just covers async interfaces.
So, I just have Inbound sync ABAP-Proxy. I developed inbound AIF interface, entered the inbound proxy class. My interface is working, FM in Action is calling and works correctly.
But, I have two problems:
1) I don't understand, how should I get back a response to the Proxy?
2) I can't see a payload of my interface in AIF Monitoring.
SP level of AIF is 04.
Thank you in advance.

1) I don't understand, how should I get back a response to the Proxy?
I really want to know how did you implement in you proxy class. In general, if you call /aif/cl_enabler_proxy=>process_message, this doesn't support your synchronous interface.
My idea is, in proxy class, you could call CALL FUNCTION '/AIF/FILE_PROCESS_DATA' to process your input request and add you own coding to get back a response or another function module /AIF/FILE_TRANSFORM_DATA to transform your own SAP data to your response data structure(This need you to define another outbound interface and mapping).
Brecht is right, this is similar to his outbound synchronous interface.
You could refer to function module /AIF/SEND_WITH_PROXY. This function module is designed to support synchronous outbound interface
2) I can't see a payload of my interface in AIF Monitoring.
If you want to see input and output structure in Error Handling, I think you need to use XML persistency engine to save your own payload and save this payload via class /aif/cl_persist_engine_xml method /aif/if_persistency_engine~update.
This also could be found in function module /AIF/SEND_WITH_PROXY for example.
Best Regards,
Eric.

Filtering objects in Inbound Synchronization Rule

Hi
i want, under certain conditions, to stop an inbound sync on a user object that is in FIM metaverse based on a condition that exists in metaverse and not in the CS of the managemnet agent.
that is, I want when a metaverse attribute is updated on a user, this user should not be part of the inbound sync any more. i i want all attribute flow to stop for this user.
is it possible to do that?
thank you.
MM

Once you have corrected your import flow in sync rule, you have to do the following:
- Import on FIM MA (Delta would be enough)
- Full Synch on FIM MA (as Sync rules were changed)
- Full Synch on AD MA - to import objectSID of every object from AD.
- Export to FIM MA (to update objectSID - make sure you have suitable flow in synch engine)
If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

Inbound sync. messagin

Similar Messages

Maybe you are looking for