problem of ESS with Portal

[Former Member]

Hello experts!

I would appreciate a little help from you.

We have configured recently ESS in our portal. The problem arised since that.

We detected that all the connections between our portal and the gateway of the backend is all concentrated in the central instance.

Let me explain you. Imagine a user logs in to the application server 1 (app1) of the portal. He makes something in ESS and we detect that the connection to the backend (erp) is not made through the application server. In fact, we appreciate that this connection goes through the central instance.

JCo connection are load balanced. The problem seems to be in another configuration.

As you can understand, as ESS gives a lot of workload to the system, and since it is being processed centrally in central instance, we're having a lot of performance issues (regarding cpu bottleneck) in central instance. The other 4 applications servers are just with a 10% CPU load.

Could you help us please so that the requests from the application servers to the backend don't have to be processed in the central instance?

regards,

Filipe Vasconcelos

[Former Member]

ok

[Former Member]

Yes. in JCo definition of Webdynpro we have defined with load balanced. And in fact, it is balancing in the destination (ERP system). The problem is in source system that all requests of application servers are processed centrally in central system.

[achim_hauck2]

Filipe,

have you chosen the "Load Balanced" -option as you created teh application JCO-connections in WebDynpro Content Administrator? (The MetaData-connections are "load balanced" by default)

kr, achim