Bug 779226 (SOA-1619) - Need to document server profiles in SOA-P 5.0 distribution
Summary: Need to document server profiles in SOA-P 5.0 distribution
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1619
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, Configuration
Version: 5.0.0 ER2
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.0.0 GA
Assignee: Dana Mison
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-20 02:33 UTC by Len DiMaggio
Modified: 2010-02-08 17:36 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-08 17:36:54 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1619 0 None None None Never

Description Len DiMaggio 2009-11-20 02:33:37 UTC
Date of First Response: 2009-12-03 23:16:37
project_key: SOA

Of the (6) server profiles in ER2 and ER3:

* production
* default
* all
* minimal
* standard
* web
 
The 'standard' and 'web' profiles do not support ESB applications/archives to be deployed. 

We should remove the 'web' and 'standard' server profiles/configs from the SOA-P 5.0 distribution to avoid user confusion as:

a) Users wishing to deploy web apps, can deploy them to any of the profiles that also support ESB apps.

b) Apart from the difference in support for ESB apps, the standard and default profiles are functionally equivalent.

c) In the 4.2 GA release, the embedded server's 'default' profile did not support ESB deployment - this caused user confusion as the standalone server's default profile did support ESB deployment. We resolved this in 4.3 when all the embedded server's profiles that we shipped (apart from the minimal profile) supported ESB deployment.

Comment 2 Dana Mison 2009-12-04 04:16:37 UTC
this information is now included in the Getting Started Guide, Section 1.1.1 - Server Profiles 


Note You need to log in before you can comment on or make changes to this bug.