Accepted Solutions (1)
Hello Narendra,
Use the below module in your receiver HTTP adapter -
When tested, I can see the reply from HTTP server with the file name we passed-
Please also check with your target server if they were able to process the data.
Thanks
Sugata
Answers (11)
Hi Sugata,
Now message is delivered successfully without using any java mapping. Only ID Module configuration and setting up ASMA in ESR.
But filename is not reading. It is getting delivered as MainDocument and not going as AIL_INV_IDOCcreatedDate_IDOCcreatedTime
HTTP_CLIENT : 5161 REQUEST:
------=_Part_546_1040778488.1554801212614
Content-Type: multipart/form-data;
Content-ID: <payload-bf322c1c5aa711e9cdd20000001e93ee@sap.com>
Content-Description: MainDocument
Content-Disposition: form-data; name="file"; filename="MainDocument" SKUId,EANNumber,Warehouse,Quantity,UOM,Cost,Entity,TransactionType
USPOLI781,987980007333,1200,1,PC,98,ALBL,NA
------=_Part_546_1040778488.1554801212614--
Path:
ALBLMT/SOH/local/AIL_MainDocument
headers:
DynamicConfiguration conf2 = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION); DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System", "HeaderFieldOne"); conf2.put(key1,fileName); return "";
Hi Sugata,
There is no issue from a network/infra standpoints.
HTTP channel ping works fine in PI. As well the target server works completely fine with status HTTP 200 OK.
Hi Narendra,
As I have mentioned earlier you have to create only 1 operation mapping , in that 1step graphical mapping will be IDoc to XML mapping and 2nd step graphical mapping will be to create attachment using the UDF and assign some value to the target field.
could you please also let us know the details of target HTTP web page ? how the HTTP form looks like? a screenshot will do. I have tested the same way I have descried earlier and it worked.
Thanks
Sugata
Hi Sugata,
First mapping idoc to xml one to one mapping.
Coming to second mapping do we need to concatenate and send the input as below and map to 'file' ??
ARW27210,1,GT0,EA,INR,87822210012,NA,11
Hello Narendra,
As you have to send the actual data as a file, you have to convert the XML into CSV and create an attachment in the mapping itself. As your scenario is an IDoc to HTTP. I think it is a simple Async scenario, if you are expecting a response back from the target HTTP server then you have to use the request response bean and replace interface configurations in your receiver channel. As of now I am considering this as a Async scenario where you have to send the payload as a csv file and a text value as the HTTP body.
Please try the following steps-
1. Create two target data types and message types - 1st data and message type will be your actual payload structure- Records. The 2nd data type and message type will be a single field.
Something like this -
2. Create two message Mappings- 1st mapping is the actual mapping for IDoc to 1st target structure, you already have this one. the 2nd mapping is the one where you have to create the CSV from the XML output generated from the 1st mapping and assign the csv file as an attachment to the XI message.In this mapping your source structure will the 1st message type (with Record nodes) and target structure will be the 2nd message type with single field you have created.
in the 2nd step mapping you have to create an UDF to convert the XML to csv and create an attachment. please adjust the code below with your 1st structure's field names and use it - in this UDF you have to pass all the fields as source-
AbstractTrace trace = container.getTrace();
String header = "Name,Id,Email"; // field names from your first structure
String content = header + "\n";
String mimeType= "application/vnd.ms-excel;charset="+ "\"" + "uft-8" + "\"";
String filename = "Attachment.csv";// you can dynamically set this
for(int i =0; i< Name.length; i++)
{
// adjust the below line with your field names from first structure
content = content + Name[i] +"," +Id[i] + ","+ Email[i] + "\n";
}
trace.addInfo(content);
//Create attachment with CSV data
try
{
GlobalContainer globalContainer = container.getGlobalContainer();
OutputAttachments outputAttachments = globalContainer.getOutputAttachments();
Attachment attachments = outputAttachments.create(filename, mimeType, content.getBytes());
outputAttachments.setAttachment(attachments);
result.addValue("filePath"); // you can dynamically set this
} catch (Exception e)
{
result.addValue(e.toString());
}
3. create the Operation mapping with these 2 message mappings - 1st mmaping will be actual transformation and 2nd mapping will be creating the attachment and CSV file. In your operation mapping the target service interface should have the message type of single field.
4. go to integration directory and setup your receiver HTTP_AAE channel as below -
Here, note is the target HTTP form field name, you can replace as per your scenario-
5. That's all, you do not have to use message transformation bean in the receiver HTTP adapter.
6. In the UDF you can see, I have given a static filename and a constant value to the payload parameter. You can dynamically set the file name and HTTP body (payload value) in your first mapping . for this , you can add two extra field in your first structure and store the file name and payload value there- which can be passed into the second mapping UDF.
7. Once this is setup you can see the message monitoring - the payload will be the value you specify as http payload body and there will be the attachment-
Hope this will help. Please let me know if you are able to process messages succefully.
Thanks
Sugata
Message mapper 1
Message mapper 1
Message mapper 2
2 operational mappers.
1 operational mapping from idoc to soap
second operational mapping from soap to http.
code:
Message mapper 1
Idoc to xml with concatenate commas after each field.
Message mapper 2
MAPPER 1 inputs passed to UDF
2 operational mappers:
1 operational mapping from idoc to soap
second operational mapping from soap to http_AAE.
code:
HTTP Communication
config
Hi Sugata,
By the way what is file path and are your referring response payload.
This is asynchronous scenario wherein below are the body parameters. A quick example from PostMan,
Hi Ryan,
There is no issue at server side. Same is working perfectly fine in POSTMAN and there is no network/infra issues.
Hello Sugata,
Regards point no 1, this is not a simple POST method and it works only with multi form-data content-type. Please find below snapshot:
regards point no 2, it is not working with content type 'application/x-www-form-urlencoded' and please find the API correct code snippets below:
regards point no 3, the attribute namespace is corrected in ASMA UDF and resent the message but though facing same error i.e.
DynamicConfiguration conf1 = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION); DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File", "filename"); String filename=conf1.get(key1); DynamicConfiguration conf2 = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION); DynamicConfigurationKey key2 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System", "filename"); filename = "AIL_INV_" + CREDAT + "_" + CRETIM + ".csv"; conf2.put(key2,filename); return filename;
Error:
Transmitting the message to endpoint <local> using connection AFW failed, due to: com.sap.aii.adapter.http.api.HttpAdapterException: STATUS_CODE_NOT_OK- 500 Internal Server Error
There is no URL parameters and API has only body parameters.
key - file
value - AIL_INV_20190402_105412.csv
file upload in form-data content-type
| User | Count |
|---|---|
| 76 | |
| 10 | |
| 8 | |
| 8 | |
| 6 | |
| 5 | |
| 5 | |
| 5 | |
| 5 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.