[#MULE-3836] Expand documentation on deployment scenarios around app servers and using JCA vs embedded method

Mule

Expand documentation on deployment scenarios around app servers and using JCA vs embedded method

Created: 15/Oct/08 12:54 PM Updated: 12/Nov/08 08:23 PM

Component/s:

Documentation / Website

Affects Version/s:

2.1.1

Fix Version/s:

2.x Product Backlog

Time Tracking:

Original Estimate:

6 hours

Remaining Estimate:

6 hours

Time Spent:

Not Specified

Issue Links:

Related

This issue relates to:

~~MULE-3861~~ Document deployment to WebLogic

Labels:
User impact:	Low
Effort points:	0.5
Affects Docs:	Yes

Description

« Hide

What are the advantages/disadvantages of deploying Mule as a webapp using the embedded version versus the JCA Resource Adapter when deploying in an application server. When should you choose one option versus the other and in what scenarios does this make better sense to do than deploying mule standalone?

http://www.mulesource.org/display/MULE2USER/Deployment+Scenarios

All

Comments

Work Log

Change History

Transitions

FishEye

Sort Order:

[ Permlink | « Hide ]

Ken Yagen added a comment - 11/Nov/08 12:46 PM

Also document what features/mule capabilities are lost when running as embedded or JCA. (for example, patch management support)

[ Permlink | « Hide ]

Daniel Zapata added a comment - 11/Nov/08 01:20 PM

I did some research on JCA and the following may be useful:
Why choose JCA (non Mule-specific):

tight coupling
performance
lifcycle management
work management: the resource adapter can submit work requests to the app server
app server can control thread management and pooling
scalability with asynchronous integration

Some resources (some are a little dated):

[ Permlink | « Hide ]

Daniel Feist added a comment - 11/Nov/08 04:33 PM - edited

>performance
Mule JCA adaptor doesn't increase mule's performance

>lifcycle management
Other than stop/start of JCA adaptor no other appServer lifecycle is used

>work management: the resource adapter can submit work requests to the app server
The Mule resource adaptor only does this with if Mule->MDB "Message Inflow" is being used and only for incoming message using "Message inflow"

>app server can control thread management and pooling
The Mule resource adaptor does not use any appServer threading or pooling.