tRestClient correlation value in request not same as response

synfield — Sat, 16 Nov 2024 06:33:44 GMT

I'm not sure that I have the correct understanding, but I'm trying to match up multiple tRestClient user record posts with their responses, in order to match up the statusCode's and response's returned, for each record, from the Rest API server, in order to update their corresponding records in the DB.

I thought I could use business correlation option in tRESTClient put the correlation_id in the request header doesn't match the correlation_id in the response header.

---------------------------
ID: 1
Address: https://api10preview.sap.com/odata/vf22/cust_upload
Http-Method: POST
Content-Type: application/json
Headers: {Content-Type=[application/json], Accept=[application/json], Authorization=[Basic XXXXX], CorrelationID=[85f893a02967475080eb6b262921d6c4]}
Payload: {"effectiveStartDate":"\\/Date(1544076000000)\\/","externalCode":"MIT4444444","cust_jobInfo":{"__metadata":{"uri":"https://api10preview.sap.com/odata/vf22/cust_upload","type":"SFOData.cust_CEJobInfo"},"cust_CEEffectiveDate_effectiveStartDate":"\\/Date(1544076000000)\\/","cust_CEEffectiveDate_externalCode":"MIT4444444","cust_Position":"No","externalCode":"396ab44ab75c4ebcbd13266871b2f2ab","cust_payscaleType":"Payscale type","cust_payscaleLevel":"Payscale level","cust_unit":"SAP Unit - Academic","cust_employeePayType":"Salaried","cust_location":null,"cust_division":"CE Directorate (other)","cust_activityCode":"Projects","cust_businessGroup":"Academic","cust_payscaleArea":"Payscale area","cust_payscaleGroup":"Payscale group","cust_team":"SAP Team - Service Desk","cust_department":"Business Development"}}
--------------------------------------
[DEBUG]: org.apache.cxf.transport.http.Headers - Content-Type: application/json
[DEBUG]: org.apache.cxf.transport.http.Headers - Accept: application/json
[DEBUG]: org.apache.cxf.transport.http.Headers - Authorization: Basic XXXXXX
[DEBUG]: org.apache.cxf.transport.http.Headers - CorrelationID: 85f893a02967475080eb6b262921d6c4

ID: 1
Response-Code: 400
Encoding: UTF-8
Content-Type: application/json;charset=utf-8
Headers: {API-ELAPSED-TIME=[29], Company-Id=[xxxx], connection=[keep-alive], Content-Length=[145], content-type=[application/json;charset=utf-8], CorrelationId=[e932eaf1-2da6-49f5-847b-ac04224af167], DataServiceVersion=[1.0], Date=[Tue, 19 Feb 2019 02:26:51 GMT], Error-Code=[], Event_ID=[EVENT-UNKNOWN-UNKNOWN-rb01areboh11s-20190219132651-931514], OPTR_CXT=[0100010000d0ab1721-33ed-11e9-9166-29d33ae9b95b00000000-0000-0000-0000-000000000001-1 HTTP ;], RequestNo=[[663800]], sap-server=[true], Server=[BizX], Set-Cookie=[JSESSIONID=98DD22ED98CF71A646BE5245F844F913.sc10bsfapi02t; Secure; Path=/], SFODataServerTimeZone=[Australia/Sydney], Strict-Transport-Security=[max-age=16070400; includeSubDomains], X-CSRF-Token=[5IPRxxxyBmGP7EL10TqW5bebQxx3d], X-SF-Record-Count-Recursive=[0]}
Payload: {
"error" : {
"code" : "BadRequestException", "message"

Is there another way to do this if I can't use the "business correlation" property, i.e. is it possible to use the "ID: 1" etc.. that's provided in the stack trace, if so, how do I access this?

Cheers.

Re: tRestClient correlation value in request not same as response

Anonymous — Thu, 07 Mar 2019 01:42:20 GMT

Hello,

Did add the correlation ID feature to the endpoint features list for your rest services? Are you able to configure your tRestClient to do a POST?

Which talend ESB product used?

Best regards

Sabrina

Re: tRestClient correlation value in request not same as response

synfield — Thu, 07 Mar 2019 20:46:13 GMT

Hi Sabrina, So are you saying I need to configure this on the REST server end and that this service has to be implemented in Talend to do so?

Unfortunately, I'm using a third-party REST service and can't make changes.

Thanks for your help.

Kind regards

topic Re: tRestClient correlation value in request not same as response in Talend Studio

tRestClient correlation value in request not same as response

Re: tRestClient correlation value in request not same as response

Re: tRestClient correlation value in request not same as response