help on web to IDOC scenario

[Former Member]

Hi Guys,

I hav a scenario whr i need to get the currency rate from url ( http://www.ecb.europa.eu/stats/eurofxref/eurofxref-daily.xml ) once in a day and have to post thru XI using IDOC (exchange_rate01) in R/3.

Should i go for plain HTTP adapter or wat must be approach??

if smbd can detail on aproach for XI dev plz...

Regs,

Anshul

[Former Member]

Hi Dheeraj,

completely I got ur logic and it's very usefull, i have given the points...!!

File adapter i can schedule as i trigger to run java mapping.....!!

thanks!!

Regs,

Ansh

[former_member185881]

Hi

Thanks Ansh.

Need favour from you too, well the time you complete this scenario please tell me the details about java mapping how you written code to hit url and how you created file.

Thanks

Dheeraj Kumar

[former_member185881]

Hi Ansh

Got the answer for you

Just telling you the logic according to that you can work out with your scenario because by sitting here i cant help you out in your development ok.

See you have been given a URL right

so

Step 1 : create your source structure according to that URL data.

Step 2 : create your target structure according to your requirement.

Step 3 : Do complete your IR part as usual ok

Step 4 : For this scenario you have to create java mapping in which you to write a code like this -

---

here from java mapping you have to hit that particular URL and get the current exchange rate, this hit should happen at particular time only k.--

Step 5: use this java mapping in your message maaping.

You have to create scenario FILE TO IDOC not SOAP to IDOC ok because using this java maaping you have to create a file and that file will contain a current exchange value and now the scenario is simple just pic that file from your source location and post a IDOC to R3 got it.

At runtime through Interface Determination Interface Mapping will be called and then your java mapping will be called and then filke will be created containing Current Exchange Rate.

I dont know how much i am able to clear the logic but i tried my best.

Regards

Dheeraj Kumar

Edited by: Dheeraj Kumar on Jul 9, 2009 6:26 PM

[Former Member]

Hi Dheeraj,

Thanks for ur reply.... prob here is i don't hav wsdl or xsd...the only thing provided to me is this url to get xml data..

If i go for SOAP sender or HTTP sender(ASYNC) i don't hav option to mention url...

plz hav a look at url mentioned and suggest me the possibilities..

Regs,

Ansh

[Former Member]

Hi Ansh,

Here is your xsd:

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

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:element name="Cube">

<xs:complexType>

<xs:sequence>

<xs:element ref="Cube" minOccurs="0" maxOccurs="unbounded" />

</xs:sequence>

<xs:attribute name="currency" type="xs:ID" use="optional" />

<xs:attribute name="rate" type="xs:NMTOKEN" use="optional" />

<xs:attribute name="time" type="xs:NMTOKEN" use="optional" />

</xs:complexType>

</xs:element>

<xs:element name="gesmes:Envelope">

<xs:complexType>

<xs:sequence>

<xs:element ref="gesmes:subject" />

<xs:element ref="gesmes:Sender" />

<xs:element ref="Cube" />

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="gesmes:name">

<xs:complexType mixed="true" />

</xs:element>

<xs:element name="gesmes:Sender">

<xs:complexType>

<xs:sequence>

<xs:element ref="gesmes:name" />

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="gesmes:subject">

<xs:complexType mixed="true" />

</xs:element>

</xs:schema>

Open the url you have given and it gives xml. Right click on the page and view source and save the xml file. Then go to this url:

http://www.hitsw.com/xml_utilites/

Here in the second option browse for your saved xml file. Then it gives you the xsd for the xml file.

Regards,

---Satish

[Former Member]

refer this WIKI [https://wiki.sdn.sap.com/wiki/display/XI/IDoctoSOAPSynchronouswith+BPM]

[former_member185881]

Hi

Just check it out for full details

IR

---

1)define Data type for sender and receiver system, later Message Type, later Message Interface.

2) Define you mapping and Interface mapping.

3)active your changes

ID

---

1)Define Serder Comunication channel type SOAP.

in DEFAULT XI PARAMETER you must put Message interface and Namespace of serder structure defined in IR

2) Define Receiver Communication channel.

3)define Receiver Determination

3)define Interface Determination

4)Define Sender agreement

5) Define Receiver Agreemen.

6)Active your changes.

DEFINE WEB SERVICE:

7)go to tool>enviroment>define Web services and put this string

http://<Host>:<Port>/XISOAPAdapter/MessageServlet?channel=:<Bussines_System>:<Communication Channel>.

Example: http://srv-xi01-adm:50000/XISOAPAdapter/MessageServlet?channel=:SCR_D:scr_d_soap_customer_sender

8)next step select MI of list

9)en next step you must define your sender BS and Message Interface.

10) Save Web service.

Test ur service with for example XML-Spy

Steps to make a request using the XML SPY:

1. Open the XML SPY, in the menu go to SOAP  Create new SOAP request

2.it will open a new window you will provide the path wsdl file that you have recently save .

3.Click on OK button a new window will be opened which shows the SOAP request

4.In the menu choose SOAP  Send request to server

5.Asynchronous Request: If your request is successful you will receive a SOAP response which will be empty response in an asynchronous request .

to configure file receiver adapter take in mind these blogs

/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion

/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2

Thats all!!

Thanks

Dheeraj Kumar

[former_member185881]

Hi

IR: Use your wsdl file as your Message interface

create all the things we do for all scenarios.

ID:

-> Configure Sender Soap Communication channel, Adapter Type as SOAP, Give the necessary parameters

-> all others will be same

Now for testing you have to use microsoft infopath

its simple scenario.

If others details you need You may ask again