[Stefano]

Hello guys
in your knowledge/experience it's possibile in OTM 5.5CU4 dedicate a connection pool to INTEGRATION ACTIVITY by servlet (xml import and export), dedicate means

• have a DB sessions connection pool dedicate for integration
• have a DB sessions connection pool dedicate for UI activity ....and more
• have a DB sessions connection pool dedicate to process recurring process task

Thanks in advance for your commets or help

Bye

[chrisplough]

Stefano,

Honestly, I haven't configured OTM in this way in the past, so I don't know that it's possible. Several of the components exist (being able to create your own DB pool, etc), but I haven't seen them brought together in this way.

I guess my first question is, why? I'm not sure that I see the benefit (performance or otherwise) to breaking out these db connection pools, unless your primary DB connection pool is oversubscribed. In which case, it may be easier to simply increase the capacity, rather than trying to create and maintain various connection pools.

Can you provide more details?

--Chris

[Stefano]

First of all Thank for you answer

I give you more information---
we have migrated to 5.5 last weeked from 5.0 on a teorichally more powerfull architecture, but we are registering a performance problem during import XML from external system, via glog.integration.servlet.WMServlet.
We are investigating on this issue, looking at DB tuning (we had still tuned it with new statistics and so on during our integration test..but seem that some specific query on 5.5 db are worst respect 5.0 db), but in the meantime I want to isolate and separate INTEGRATION activity from USER activity and if possible also from RECURRING PROCESS Activity, because this extra time consumed in integration seems affect also normal UI activity.

Perhaps it's not only a DB problem, could be also a performance problem on App Server ..condiring that we moving out from a BEA old and stable to a new (And not so tested...) OAS

Thanks in advance for any kind of suggestions

Ciao

[chrisplough]

Stefano,

Unfortunately, I don't know how you'd separate off to different db pools, but now I understand why you want to. I guess I'd point to 2 primary issues:

1. The use of OAS immediately introduces a performance degradation. It may only be 10-20% on most platforms, but can be as high as 200% on Linux, because you have to move away from the JRockit JDK to the Sun JDK.
2. Many times slowdowns in integration aren't a DB-related issue (though, it's definitely worth checking), but rather caused by either backups in the Event Queues (check via the EventDiagServlet - glog.webserver.event.EventDiagServlet) or with object contention (check via the MediatorDiagServlet - glog.webserver.mediator.MediatorDiagServlet).--

May I ask what is necessitating the swap from WebLogic to OAS?

--Chris

[Stefano]

Chris
We move to BEA to OAS for licences issue......Oracle drive it

We move from BEA WINDOWS servers to LINUX OAS one...

I hope that performance degradation don't reach 200%....someone coud be killed...and ...I'm too young for die

At the moment I perform some fine-fine-fine tuning (interface was in production from 2006 without big problem afeter initial phase) on import procedure related agents that reduce time of importing and situation now is better, however there is any document on the forum or around the world that explains or give suggestions what are most important things to check on "EventDiagServlet"

Thanks

Ciao

[chrisplough]

Haha - I hope you don't die either. Unfortunately, you will see a very significant performance degradation, since you were running on JRockit (it's used with WebLogic on Win32 also) and now you're running with the Sun JDK. If you wanted to verify, I'd recommend installing a temporary WebLogic OTM instance on the Linux server and comparing performance (assuming this isn't PROD).

There isn't a much information on the EventDiagServlet or MediatorDiagServlet (or other OTM utility servlets, for that matter) since they are pretty advanced. Mostly, those of us who have been doing development or performance tuning for years have just built up a knowledge around them. Here is some high-level info, though: http://www.otmfaq.com/forums/f27/doc...vlet-page-639/ (Documentation on using EventDiagServlet page)

I do plan to write up more detailed information about several of them -- I just need to find the time... You know how that work

--Chris

[Stefano]

Thanks Chris
Finnaly using mediator servlet I discover that occassionaly performance problems depends from something blocked, some "object contention"...
We solve this pushing "release" on mediator servlet....but why this happens??
no lock in db session...??
Do you have in your experience any idea??
I did'nt find anything in log, I have to see some special logs item?

BIG Problem seems that during this BLOCKING period OTM become slower...as is JAVA process absorb 100% resource....

(CU4-linux...)

Thanks in advance

[chrisplough]

Stefano,

This contention is a common performance problem for OTM customers and we've been doing a lot of projects around it lately. Usually, these issues are the result of Agent contention and require a detailed look at all of your OTM Agents in order to resolve. You want to ensure that you're not kicking off too many Agents at the same time that work upon the same business objects (orders, shipments, etc). The way the Agents are structured also has a lot to do with the overall performance and contention.

I know this is vague, but getting into OTM Agent optimization is a BIG topic. I hope that this at least points you in the right direction, though.

--Chris