JDBC syn to proxy syn Scenario

Hi firnends,
JDBC (syn) to Proxy (Sys)
I need to pick the data from JDBC and status need to update back from ECC (proxy).
What are the best possible soluctions ? With or without BPM ?
Pls reply back.
Regards,
vasudeva
Edited by: vasudeva gembali on Oct 7, 2010 7:40 AM

Hi friends,
I started my scenario like
JDBC syn - proxy syn - JDBC without BPM using Using Request Response Bean Module
as in link
http://wiki.sdn.sap.com/wiki/display/XI/UsingRequestResponseBeanModuleinFILE+Adapter
. Now i am getting the issue like
JDBC is picking the data and can't update the status SET = 1 instead of 0.
It was working when it was asynch.
2. Do i need to create Receiver determination or receiver agreement two times ?

Similar Messages

JDBC- XI-BPM- Proxy synch scenario.

Hi Experts,
We already have the scenario with JDBC --> BPM > RFC which we need to convert it to the scenario JDBC> BPM -->ABAP Proxy.
Since i'm new to BPM development, i couldn't find a way to implement the requirement, because for BPM the message interface should be Abstract and these Abstract Message interfaces won't be visible in the SPROXY transaction.
Please let us know what would be the approach to achieve this requirement.
Note: XI system Version is 3.0 with SP-19.
Thanks.
Edited by: Bandana Baghel on Jun 22, 2009 1:51 PM

i couldn't find a way to implement the requirement, because for BPM the message interface
should be Abstract and these Abstract Message interfaces won't be visible in the SPROXY transaction.
What you need:
1) An Inbound Async/ Sync (as the case may be)...this MI will have the message type that you want to send-receive from the BPM...and the message(s) inlcuded in this Inbound MI should be same as in the Abstract MI from the BPM_to_Proxy communication....
Then you can develop your proxy in SPROXY...
Looking at the flow I am confused whether the flow is Sync (as you mentioned in subject) or Async (as the flow shows)...hence mentioned req/ resp messages in the resposne above.
Regards,
Abhishek.

Error while executing the SOAP-XI-JDBC(syn) scenario

Dear Forum,
We have done SOAP-XI-JDBC(synch) scenario with out BPM.
When we sent the request data from EP to Oracle database through XI, we got an error,Runtime in Message-Mapping transformation~.
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Runtime in Message-Mapping transformation: Cannot produce target element /ns:Customer/customers. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:291)
Exception message says that it is a mapping issue. But we got the responce data from database along with this message.In message monitoring we got the message processed successfully.
Now i am not able to understanding why it throughs an error Runtime in Message-Mapping transformatio~ first time ?
Pls revert me to fulfill this task successfully.
Points will be rewarded.
Regards,
Naresh

Dear Friends,
Sorry for the delay,and Thank you for your quick responce.
Yes I got that message under trace option in SXMB_MONI,
Pls find the following msg structures and if any error please let me know status...
Soap request structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="soap_reqmt" type="soap_reqdt" />
<xsd:complexType name="soap_reqdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5b474a34c8a511dc8d8e001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Request" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae20c81211dcce03001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae21c81211dcc20d001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="Operation" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
49b1ae22c81211dc858a001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Data base request structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="db_reqmt" type="db_reqdt" />
<xsd:complexType name="db_reqdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5b4e7620c8a511dcc4fe001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="STATEMENTNAME" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb0bceb11dcbb54001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="FETCHDATA">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb1bceb11dc9750001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="TABLE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb3bceb11dccc94001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="access">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb4bceb11dc9b35001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb5bceb11dca20a001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279840c81011dc8e4e001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279841c81011dcb8f4001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
d0279842c81011dc832f001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="key">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43170c81611dcc8fa001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43171c81611dcb6e3001b78afb958
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="compareOperation" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
89f43172c81611dccba5001b78afb958
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="action" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
fa204eb2bceb11dca298001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Soap Responce Structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="soap_resmt" type="soap_resdt" />
<xsd:complexType name="soap_resdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8d49d494c8a411dc81f5001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="response" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd30bd0611dcb29d001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd31bd0611dca3d7001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd32bd0611dcc7d1001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd33bd0611dca6ad001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd34bd0611dc95a8001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
491ccd35bd0611dcc034001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Database responce Structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://soap2dbns" targetNamespace="http://soap2dbns">
<xsd:element name="db_resmt" type="db_resdt" />
<xsd:complexType name="db_resdt">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
8d3b7cb1c8a411dcb1d6001a4bf038d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="STATEMENTNAME_response" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3410bcfd11dcaf4c001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="row" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3411bcfd11dc92d6001b78b0798a
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDERID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3412bcfd11dc92e8001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3413bcfd11dc9f7a001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QUANTITY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3414bcfd11dcc6c4001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
adca3415bcfd11dca54c001b78b0798a
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Regards,
Naresh

Error while usinjg the JDBC to ABAP Proxy Scenario

Hello Rocks,
This is my scenario like JDBC --- Pi --- ABAP Proxy
while i am given a sender side jdbc XSD structure is like this
VWENTITYAGGREMENT
Row             1-unbound occurence
      POOL_ID   0-1 occurence
      CUST_ID
      AGREEMENT
       PRODUCT_ID
        CONTRACT_TYPE
        CONTRACT_TYPE_DESCR
        AGRMNT_STATUS
        STATUS_DESCR
          EFFDT
         TERMINATION_DT
         ADD_DT
         ADD_TM
while i am writing a select query in Sender JDBC CC is like this
SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement.
Here i am getting this Error message like this :
Error Description: Database-level error reported by JDBC driver while executing statement 'SELECT POOL_ID,CUST_ID,AGREEMENT,PRODUCT_ID,CONTRACT_TYPE,CONTRACT_TYPE_DESCR,AGRMNT_STATUS,STATUS_DESCR,EFFDT,TERMINATION_DT,ADD_DT,ADD_TM FROM vwEntityAgreement'. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
So please give me your valuable inputs !
Regards,
Ravi.

Invalid column name 'POOL_ID'.'. For details, contact your database server vendor.
Did you confirmed the name POOL_ID as suggested?
Why is the tablename different (check the case) in the query that you make and in the XSD structure that you mentioned......check if this is causing the problem.
Regards,
Abhishek.
Edited by: abhishek salvi on Jun 4, 2010 10:24 AM

File to Soap Syn Scenario

Hi Experts,
I have created File to Soap syn Scenario.
I am getting following error in RWB (CC monitoring)::
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(1), xi_input120100406-133524-40720100406-133535-09520100406-133535-32920100406-133535-57920100406-133535-82920100406-133536-07920100406-133536-32920100406-133536-56420100406-133536-78220100406-133537-032.xml, ST: ST_XMS_MSGHDR30_DYNAMIC; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: null; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(1) (or one of the attributes) has incorrect value xi_input120100406-133524-40720100406-133535-09520100406-133535-32920100406-133535-57920100406-133535-82920100406-133536-07920100406-133536-32920100406-133536-56420100406-133536-78220100406-133537-032.xml An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting xi_input120100406-133524-40720100406-133535-09520100406-133535-32920100406-133535-57920100406-133535-82920100406-133536-07920100406-133536-32920100406-133536-56420100406-133536-78220100406-133537-032.xml
Please suggest
T& R
Sushama

Hi Babu,
I am sorry if I was not clear in explaning.
Okay. I meant with the DC parameters the dynamic configuration parameters (or officially called the adapter specific message attributes or ASMA) that the file adapter added in the XI message. I assume Sushama activated this feature to transport the file adapter specific information (e.g., the file name, etc). These parameters are included in the DynamicConfiguration SOAP header. Sushama should check those entries in RWB at the adapter engine.
Some of those parameter values appeared to be too long and resulted in the quoted error:
>sap:DynamicConfiguration(3)sap:Record(1) (or one of the attributes) has incorrect value
Once which parameters are too long, Sushama can decide on how to resolve this issue using one of the options that I suggested in my previous reply.
I hope you got the idea this time.
Best regards, Yza

IS Mapping required in JDBC to PROXY asynchronous scenario?

Hi,
I am working on JDBC to PROXY asynchronous scenario. The scheduled stored procedure fetches the data from database tables and stores them in staging table in the same database. XI will fetch the records via JDBC adapter. Now these records are to be posted into SAP custom table via proxy without any transformation. Now is Message mapping and Interface mapping required in this case?

Hi
I assume that your source and traget structure will be different as you are using JDBC.
SO you will need to create message mapping and operation mapping.
-Deepak.

JDBC to ABAP PROXY ASYNCHRONOUS SENARIO

Hi Experts
JDBC to ABAP PROXY ASYNCHRONOUS SENARIO IN PI 7.4 ?
Can you tell me any one step by step procedure
BR,
Sagar

Hi Sagar
Check the documents below and you will be able to create the whole scenario.
JDBC sender part:
SAP PI Adapter Series: JDBC Adapter Configuration
ABAP proxy receiver part:
Step-by-step FTP to ABAP Proxy - Process Integration - SCN Wiki

File---- XI----- JDBC(synchronus)---- transformation-------- Proxy ??

can u tell me,
if i have scenario with multiple receivers,
file-->XI->JDBC(synchronus)>transformation--
>Proxy
i want to make it without BPM,
how can i do that,
coz, without BPM, how will the sequence of those two receivers(JDBC and Proxy) be specified, coz in my ID, when i do receiver determionation for the two receivers, how will the sequence be maintained....

Your scenario isn't simply multiple receivers, as you have also multiple senders (JDBC here plays as receiver and sender).
You can't do it properly without BPM.
And by properly I mean maintaing all the correct logical routing steps (receiver/interface determination etc).
What you could do is a File2Proxy async scenario and in mapping you could perform Lookup in DB. That is only way of achieving it without BPM.
Regards,
Henrique.

Acknowledgement for AsynThird-party-- SOAP-- PI-- ABAP proxy-- ECC scenario

Can someone please provide me a step-by-step for Third-party>SOAP>PI>ABAP proxy>ECC scenario.
Third-part system is sending an Asynchronous HTTPS message to PI which is then routed to the ECC system to do some processing. I have read many blong and all SAP Docu available on this subject, but i am still confused.
I understand that ABAP Proxies supports acknowledgement, but what needs to be done in the third-party system to be able to receive acknowledgements. Is there any special config. that needs to be done in Sender SOAP adapter?
What diff. needs to be done in ABAP proxy to be able to send acknowledgement messages, any config. in XI receiver adapter?
I will appreciate any guidance.
Thanks,
Saurabh

HI
Third party application need to have the synchronus communication enabled. If not then you need to get a wrapper develop for this kind of communication
For proxy development
Just go through these links:
How to create proxy.
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
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
Outbound Proxy (Client Proxy)
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
How to Activate Proxy.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
File to R/3 via ABAP Proxy with good example
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
http://help.sap.com/saphelp_nw2004s/helpdata/en/48/d5a1fe5f317a4e8e35801ed2c88246/frameset.htm
Synchronous Proxies:
Outbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2boutbound%2bprogram%2b-%2bpurchase%2border%2bsend
Inbound Synchronous Proxy
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation

File to Proxy synchronous scenario

Experts,
I am working on a File to proxy synchronous scenario.
I am doing the content conversion at the sendre side by using java program as input structure is very complex so have to go fr java code. Its a txt file at sender side.
Once I read the file in XI, am doing a graphical mapping ( just one to one mapping) then using the server proxy , a service entry is getting created then response am sending to the receiver.
My question is , can I use graphical mapping as I am using a java class for content conversion? both in one scenario is possible?
I have developed a java code for content conversion and it is working fine. How to use this .jar file in XI?
Can Any one help me wz thsi one?
Thanks in Advance
Virendra

My question is , can I use graphical mapping as I am using a java class for content conversion?
You can use as long as the structure generatde by the JAVA program is same as the source-message structure of the message mapping.
I have developed a java code for content conversion and it is working fine. How to use this .jar file in XI?
In my opinion this should be the adapter module....as the conversion needs to be done in the channel and inclucing it as a mapping wont help.
Regards,
Abhishek.

SOAP to Proxy synchronous scenario

Hi,
Hope you are all doing well.
I have a SOAP to Proxy synchronous scenario. As part of this scenario, the data structure of the response sent by SAP is different from the response sent back to the SOAP requester. Hence I have used request message mapping between the SOAP request sent by requester and the one passed on to SAP and response message mapping between the response sent by SAP and the one passed on to the requester. Both the message mappings are incorporated in a single Interface mapping.
The problem is that the interface is behaving like a asynchronous one, i.e., request is passing over to SAP but though the proxy is giving a response back, the same is not coming over to XI.
It would be really helpful if you can let me know what might have gone wrong.
regards
Debansu

Hi,
you should have that:
1. Two Message Mapping:
1.1. a Message Mapping for request    (called MM_request)    , from MT_SOAP_request     to   MT_Proxy_request.
1.2. a Message Mapping for response (called MM_response) , from MT_Proxy_response   to   MT_SOAP_response.
2. One Operation Mapping (in PI 7.1) or Interface Mapping (in PI 7.0) from SI_SOAP to SI_ Proxy with:
2.1 in the tab "request", so from MT_SOAP_request     to   MT_Proxy_request    , give your Message Mapping "MM_request".
2.2 in tab "response"   , so from MT_Proxy_response   to   MT_SOAP_response, give your Message Mapping "MM_response".
3. In you Directory, you define a flow like that:
from SI_SOAP to SI_ Proxy by using your Operation Mapping.
If I missed nothing, that's all.
MT = Message Type
MM = Message Mapping
SI =Service Interface in PI 7.1 or Message Interface in PI 7.0.
regards.
Mickael
Edited by: Mickael Huchet on Oct 19, 2011 4:07 PM

SOAP - XI- PROXY synchronous scenario

Hi Experts,
I have a
SOAP -
XI -
PROXY Synchronous Scenario
I have done the following things ESR and ID
ESR:
1. Created DT and respective MT for Request and Response.
2. Created Service Interfaces with Synchronous mode with respective MT's.
3. Created Two separate MM with respective Request and Response MT's.
4. Created Operation Mapping and call both Request and Response Mappings in it.
Integration Directory (ID):
1. Configured considering Sender SOAP and Receiver ECC Services.
2. Configured CC with required parameters in Sender SOAP CC and Receiver XI CC.
3. Generate wsdl from Sender agreement and save it as a local file.
I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
Please hep me out.
Thanks

Hi Ram,
I am getting error in receiver agreement. Do I need to specify any Module parameters in Module TAB for Sender CC or Receiver CC to synchronous scenario.
It looks like you did not create a receiver agreement, or if you did, it did not match the interface that is given or configured in Interface Determination. Can you recheck your configuration?
Regards,
Mark

No receiver could be determined in Proxy----File Scenario

Hi All,
Iam doing Proxy---File scenario
Every thing i got success in SAP R/3 side MONI
I got this Error in XI side MONI as No receiver could be determined
I check the Sender Service in MONI--- SOAP Header ---Main( Both R/3 side & XI side also)
Here it is showing like sapdev as my sender service, but actually my sender Business system is Sub_Dev_ssd.
How to get it rectify
Regards
Vamsi

Hi Chirag & Santosh,
As i said the problem is when i check in XI side MONI
The sender service is showing sapdev BUT it shld be Sub_Dev_SSD which i have selected in the Receiver Determination Step also.
The same is showing in the SAP R/3 side MONI also
According to my understanding , The Correct Business system which is there in the SLD & which i want to use is not Picking in the SAP R/3 side and so thats why iam getting the Service as sapdev & the same sapdev Service is passing to XI also
I think the Business system from the SLD is Not comming into picture.
What to do for this??
Regards
Vamsi

Synchronous Proxy - SOAP Scenario (Error 500 in Response).

Hi
I've built a few Synchronous Proxy -> SOAP Scenarios,
with 'Do Not Use SOAP Envelope' option.
For two of them, I'm facing a common error.
The error is: ADAPTER.HTTP_EXCEPTION (HTTP 500 Internal Server Error).
When I paste the EXACTLY SAME payload picked up from XI, into the SOAP client, it works giving valid response.
Trying to figure out the issue.
R/3 System:
WAS 620 (Level 0041)
XI System:
PI 7.0 (Level 0007)
SOAP System:
BizRights (Approva) 3.0
Any help is appreciated.
Rajendra.

Hi,
Following SAP notes may help you- 804124, 807000
Regards,
Moorthy

Soap to proxy : sync scenario

Hi
Have a new PI 7.1 system , wanted to do a soap to proxy sync scenario
Do i need to create business system for proxies or if I just create 2 business services: one for sender and other for reciever ,it would suffice?
Is there any advantage / dsiadvantage if I use Business service instead of Business systems?
In SLD if I just create a product /swcv : it should be good if I want to use Business service mechanism instead of Business syste, ? or is creating Technical system and Business system mandatory even if I have to configure scnearios using Business service
Thnx

Business Systems require technical systems/software components and products, from an organisational perspective in PI it might be a good idea to define these things for an external entity (Business System). As far as Im aware business Services do not have that same requirment.
I tend to limit business service usage to one off or simple interaction B2B, as soon as you have more than one adapter interacting with the same external entity a business system with all of "their" adapters will help keep things clear to other people configuring integration scenario's. Whilst smart naming standard will get you around this most of the time, it makes more sense to put them together under the one system.
Hope this helps.

JDBC syn to proxy syn Scenario

Similar Messages

Maybe you are looking for