Bug 779226 (SOA-1619)

Summary: Need to document server profiles in SOA-P 5.0 distribution
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: Documentation, ConfigurationAssignee: Dana Mison <dmison>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.0.0 ER2   
Target Milestone: ---   
Target Release: 5.0.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1619
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-08 17:36:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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