How to stop searching of SOA Instance in weblogic server 10.3.6 when click on Instances tab

2632212

Hello All,

When I click on any SOA composites then by default it goes to Dashboard tab but when I click on Instances tab then after clicking that SOA go and search for recent instances processed by that composite.Due to very heavy database , Sometimes it takes too much long time to bring the instances and sometimes it gets timed out. I do not want weblogic to go and search recent instances when I click on Instances tab.

I have tried with keeping as 0 minutes to Restrict display of instances and faults to the last in SOA Infrastructure Common Properties.

i have checked on Disable fetching of instance and fault count metrics. Each metric can still be retrieved on demand.

Audit level as Production.

Keeping 0 minute is helping me in case Dashboard tab but when I click on Instances tab even after keeping 0 minutes to  Restrict display of instances and faults to the last in SOA Infrastructure Common Properties ,still weblogic goes for searching instances due to which we have to wait till it finds the instances or gets timed out.

Could you guys please help on this ?

Martien van den Akker

Hi,

I don't think you can stop EM to start querying. In 12c this changed. There you first get a search dialog.

But in your case: take a look at purging: https://blogs.oracle.com/soaproactive/entry/soa_suite_11g_purging_guide or partitioning http://www.ateam-oracle.com/purging-and-partitioned-schemas/ .

Also you can remove unused composite versions: https://technology.amis.nl/2016/01/14/dramatically-reduce-soa-suite-11g-startup-time-by-cleaning-the-mds/ .

So bottom line: try to clean up your database on a regular basis.

Why do you click on the instances tab? By mistake or because you do want to see instances?

Another thing: sometimes a redesign of your composites could help. I did a migration of a Oracle Workflows to BPEL once. There was a construct where every few minutes a check is done to the database to see if a status has changed for a particular process instance. This was done in a reusable process. This generated loads and loads of instances. Oh, how I wished I'd took the time to redesign this to a construct where at status change a message on a queue was put. And instead of regularly checking the table, the queue was polled based on a  correlation set. This could dramatically reduce the growth of the database. So maybe in your case there can be some optimization done as well.

Regards,

Martien

Martien van den Akker

Hi,

I don't think you can stop EM to start querying. In 12c this changed. There you first get a search dialog.

But in your case: take a look at purging: https://blogs.oracle.com/soaproactive/entry/soa_suite_11g_purging_guide or partitioning http://www.ateam-oracle.com/purging-and-partitioned-schemas/ .

Also you can remove unused composite versions: https://technology.amis.nl/2016/01/14/dramatically-reduce-soa-suite-11g-startup-time-by-cleaning-the-mds/ .

So bottom line: try to clean up your database on a regular basis.

Why do you click on the instances tab? By mistake or because you do want to see instances?

Another thing: sometimes a redesign of your composites could help. I did a migration of a Oracle Workflows to BPEL once. There was a construct where every few minutes a check is done to the database to see if a status has changed for a particular process instance. This was done in a reusable process. This generated loads and loads of instances. Oh, how I wished I'd took the time to redesign this to a construct where at status change a message on a queue was put. And instead of regularly checking the table, the queue was polled based on a  correlation set. This could dramatically reduce the growth of the database. So maybe in your case there can be some optimization done as well.

Regards,

Martien

2632212

Hello ,

Thank you for your reply.

We are working on purging and undeploying unnecessary composite from Server.

But I just thought we can do meanwhile to avoid this condition.

We need to use instance tab when we want to search any particular instance at particular time for debugging any issue.

I will loo into your links.

Thanks..

Martien van den Akker

Maybe this helps as well: Composite Sensors in Oracle SOA Suite 12c ...