Bug 777891 (SOA-419)

Summary:	documentation - soa hardware requirements and SOA-P server configs
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Aleksandar Kostadinov <akostadinov>
Component:	Documentation	Assignee:	Joshua Wulf <jwulf>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 CR3	CC:	lcarlon
Target Milestone:	---
Target Release:	4.2 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-419
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-15 05:35:22 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 Aleksandar Kostadinov 2008-02-12 19:10:35 UTC

Date of First Response: 2008-02-15 00:33:25
project_key: SOA

What probably needs to get clear is how much minimum amount of RAM do production
and default config need.

I can't see documented which configs are actually SOA-P configs. Needs to be
written that default config in the embedded distribution is *not* SOA-P.

IMHO these should go in the getting started guide.

Comment 1 Joshua Wulf 2008-02-15 05:33:25 UTC

Getting Started Guide: 

Section 1.1

You must also have sufficient RAM in your machine for the JBoss Enterprise SOA Platform.You should have 768MB of physical RAM available for the server, in addition to the operating system and any other application requirements.

and 

Section 2.2

"Default" server profile

There are several different server profiles for the embedded EAP version of the platform, and only one for the standalone version. The default server profile is the server profile that will be used when the server is started without any command line parameters. This profile has ESB server functionality enabled.

In the case of the standalone version the default profile is named default.

In the case of the embedded EAP version there is a profile named default, but this is not the default profile used. The default profile used when the embedded EAP server is started with no parameters is the profile named production. Please refer to Section 2.1.2, "Securing jBPM for production environments" for more information about this profile. 

....

To start the server with a different profile, simply use the startup command followed by -c <profile name>.