Bug 777891 (SOA-419) - documentation - soa hardware requirements and SOA-P server configs
Summary: documentation - soa hardware requirements and SOA-P server configs
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-419
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation
Version: 4.2 CR3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 GA
Assignee: Joshua Wulf
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-12 19:10 UTC by Aleksandar Kostadinov
Modified: 2014-10-19 23:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-15 05:35:22 UTC
Type: Bug


Attachments (Terms of Use)


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

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>.


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