Bug 996123 - EAP have to be started with configuration "standalone-full"
Summary: EAP have to be started with configuration "standalone-full"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Documentation
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: CR2
: ---
Assignee: lcarlon
QA Contact: Petr Široký
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-12 13:02 UTC by Petr Široký
Modified: 2014-02-21 13:33 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Build: CSProcessor Builder Version 1.11 Build Name: 13464, Getting Started Guide-6-Beta-1 Build Date: 29-07-2013 16:57:59 Topic ID: 13673-457380 [Latest]
Last Closed: 2013-08-19 12:29:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Petr Široký 2013-08-12 13:02:18 UTC
Title: Starting the server

Describe the issue:
EAP 6.1 have to be started with configuration "standalone-full" since JMS modules are needed for successful deployment of business central. 


Suggestions for improvement:
Instead of "./standalone.sh" use "./standalone.sh -c standalone-full.xml" (or "./standalone.sh --server-config=standalone-full.xml" - not sure if the "-c" is deprecated or not)


Additional information:
This is only necessary for BPMS, BRMS does _not_ need the "standalone-full" profile.

Comment 3 Petr Široký 2013-08-15 12:52:31 UTC
Hello Lee,

I am sorry I probably misunderstood the productization intent to update the standalone.xml with all needed stuff, so with ER1 there is no need to use the standalone-full.xml configuration, the update standalone.xml is enough. Could you please revert the changes you made? Thanks and again I am sorry for the confusion.

Comment 4 lcarlon 2013-08-15 23:26:44 UTC
Hi Petr,

No problem. I've removed the changes. Setting back to ON-QA, though realistically I could probably just close the bug.

Thanks
Lee

Comment 5 Petr Široký 2013-08-19 12:29:40 UTC
Stage server contains docs without the "full" config - so everything is as it was before this bugzilla was created - which is correct. Closing this one.


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