Error 500 calling an ES from a BPM

[Former Member]

Hi experts,

I have a BPM in XI that calls an ES many times. The standard ESs called are the Create Project Create Network an Create Activity. The BPM calls first of all the create project, then calls the create network, once for each network realted to the main project and then calls the create activity once for each activity realated to each network.

The BPM works fine for few networks and activities, but when calling many networks and activities it returns an error 500 of conection. It will be because the project object gets blocked when its called many times in a little period of time. I think it's not due to the XML or related because if I do the same process but with a wait step between each send it works fine. Do you know how can avoid this problem?

Regards

Gonzalo

[Former Member]

ou are working with XI 3.0 or 7.0. If you have one XI installation across different network domains, host names may not be resolvable across network domains depending on your network setup. For the XI inter-component communication, URLs registered in the System Landscape Directory (SLD) are used.

XI Tools, Integration Engine and XI Adapter Engine register their URLs in the SLD in different ways:

XI Tools: Hostname and port used by the Tools (RWB, Integration Builder -Repository and -Directory) are stored in the Exchange Profile. During J2EE system restart they get self registered in the SLD using the values defined there.

XI Adapter Engine: In case of the XI Adapter Engine, these URLs are automatically entered to the SLD as part of the Adapter Framework self registration process. Host and port are taken from the J2EE server.

In most cases the host name in these URLs is not fully qualified whereas in cross-domain scenarios fully qualified host names are required.

Solution

The problem can be solved in most cases by forcing the XI self-registration to use fully qualified host names.

For XI Integration Builder, Integration Engine and Runtime Workbench, you accomplish this by entering fully qualified host names in the XI Exchange Profile, then initiating a new self-registration (restarting the J2EE engine).

For the Adapter Engine, the approach is different: Change the properties "SLD.selfregistration.httpPort", "SLD.selfregistration.httpsPort" and "SLD.selfregistration.hostName" of the J2EE service SAP XI AF CPA Cache. Enter the fully qualified host name under which the Adapter Engine can be reached from all relevant network domains. Do this in the Visual Administrator of the J2EE Engine. Then restart the applications "com.sap.aii.af.cpa.app" and "com.sap aii.af.app", or restart the complete J2EE engine. This triggers a new Adapter Engine self-registration.

Go in the Integration Server (IS) to transaction "SXI_CACHE -> Goto -> Adapter-Engine-Cache" and delete the old Adapter Engine cache entries. After that the cache is refreshed from SLD as soon as a new message in sent to the respective Adapter Engine.

Check: After restart, navigate in SLD through "Content Maintenance -> XIAdapter Framework" to your Adapter Engine. As part of the "associated instances" you find e.g. at "XI Adapter Service XIRA -> Associated Instances -> Port for XIRA of af.<SID>.<hostname>" the new URL with the fully qualified host name.

regards

chandra

[Former Member]

HI,

helpful

500 Internal Server Errors

Description: The server encountered an unexpected condition which prevented it from fulfilling the request.

Possible Tips: Have a look into SAP Notes u2013 804124, 807000

Regards

[Former Member]

I think that this notes doesn't applies to my case. The point is that my conection usually works fine for few connections, so note 804124 treats a different problem (like if the connection doesn´t work at all) and 807000, there are not time outs. We were thinking about the number of dialogue processes in our backend(we have just 7 right now) what do you think about?

Regards

Gonzalo