WebLogic Integration Solutions Best Practices FAQ

     Previous  Next    Contents  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Performance Tips

Design-Time Performance Issues

Which types of processes are faster—stateful or stateless?

Which controls are faster—process or service?

Which callback methods are faster—process control callbacks or message broker subscriptions?

How can I get better performance from parallel nodes in my business processes?

Why do my JMS queues show so many pending messages?

How can I get rid of pending JMS timer messages?

How can I increase the transaction timeout period?

Run-Time Tuning Issues

What flags should I use when I start WebLogic Server to maximize performance?

How do I tune WebLogic Integration Applications?

Can I configure the value of max-beans-in-free-pool for the JMS event generator?

When should I version a stateful business process?

Which process tracking levels should I use to optimize performance?

Do I need to run the Archiver if the process tracking levels are set to none?

How do I turn off informational Web services messages?

When should my WebLogic Integration application use the document store?

Which is the best persistence model for JMS—file-based persistence or JDBC?

What should I watch for when monitoring a WebLogic Integration application running under load?

How can I reduce the number of transactions timing out?

Why does my application seem to leak memory?

WebLogic Integration Application Recovery

Recovery Checklist

What should I check to make sure my WebLogic Integration application is configured properly for recovery?

How long should I wait to start recovery?

  Back to Top       Previous  Next