cancel
Showing results for 
Search instead for 
Did you mean: 

Cost Center Replication from SAP PI Axis Error

0 Kudos

Hi Experts,

We are doing the Cost Center replication from SAP to EC using PI as pass-through.

We followed the guide "Integrating Employee Central with SAP ERP Using a Pass-Through Scenario for SAP Process Integration Adding an SAP PI system between SAP ERP and the middleware system".

It is mentioned to use http (Axis). Without the Module Configuration properties we get the error that connection is close. With the properties http.proxyHost and http.proxyPort we are getting and error in the property proxy. I assume that this value needs to be client's proxy, but they are saying that for outbound they are not using any proxy for other interfaces and it is not needed as it is a direct connection. (They were not using Axis Framework before).

Is there any hint if what they need to put in the parameter value for proxy?

Many thanks,

Kind regards,

Helder Rodrigues

Accepted Solutions (0)

Answers (1)

Answers (1)

bhavesh_kantilal
Active Contributor
0 Kudos

Hello Helder,

The proxy host and port are optional properties. You can remove only these 2 properties and retain the remaining properties.

Regards,

Bhavesh

0 Kudos

Hi Bhavesh,

If we do so, we get the following error:

I found note 2232490 - Error in PI while waiting for a response from Boomi but client told me that from Runtime Workbench and it was a asynchronous call which means PI is not waiting for any response.

So not sure if something else is missing. Any clue would be appreciated!

Many thanks,

Kind regards,

Helder Rodrigues

bhavesh_kantilal
Active Contributor
0 Kudos

Hello Helder,

Even though it is a Asynchronous call -> PI expects a HTTP 200 OK. If Boomi is not returning the same the moment it receives the data from PI,then that could be the cause for the connection closed.

2 things you can ask your Boomi counterparts to check :

  • Is Boomi receiving the data?
  • Are they sending a HTTP 200 OK back to PI

SOAP asynchronous calls are eventually HTTP calls and in HTTP world, even if no response payload is expected a HTTP 200 OK is expected ( with no Body ) for the message to exit gracefully.

Regards,

Bhavesh

0 Kudos

Hi Bhabesh,

No I'm corrently in Boomi and in "Process reporting" nothing is there.

"Are they sending a HTTP 200 OK back to PI" interesting need to research a bit in this one, any hint?

Thanks and regards,

Helder Rodrigues

Muniyappan
Active Contributor
0 Kudos

can you check if PI server is able to connect to target? you can do the telnet command.

regarding the adapter module parameter, keep blank. you dont have to provide anything if target is not using.

former_member182412
Active Contributor
0 Kudos

Hi Helder,

Get the HTTP traces as per below.

  • If your PI version support set the parameter TraceHTTP as per this blog
  • Configure TCPGateway as per this blog

Regards,

Praveen.

0 Kudos

Hi Muni M,

Thanks for your reply!

Yes, client did and confirmed that they are able to reach out to Boomi.

Thanks and regards,

Helder Rodrigues

0 Kudos

Hi,

We are using standard package, so in Boomi anything special to send back the HTTP 200 code.

Thanks and regards,

Helder Rodrigues

0 Kudos

Hi Preveen,

Asked for it, let see it this will show the issue!

Thanks and regards,

Helder Rodrigues

former_member182412
Active Contributor
0 Kudos

Hi Helder,

Try with smaller payload and see the call will success?

Regards,

Praveen.

bhavesh_kantilal
Active Contributor
0 Kudos

Well if its the standard package on Boomi, then this should be the norm.

In that case it could the case as described in the OSS note of a timeout due to the higher payload size.

As you do not have a Proxy Server in the middle, the timeout needs to be set in the SOAP Adapter using Axis and the SAP note for this that describes how to perform the same -

http://service.sap.com/sap/support/notes/1289145

Regards,

Bhavesh