Bug 882522 - Incorrect war file name for security setting in step #4. Should be business-central-server.war instead of business-central.war.
Summary: Incorrect war file name for security setting in step #4. Should be business-c...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Documentation
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: lcarlon
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-01 16:44 UTC by Bill Kemp
Modified: 2012-12-02 23:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Instance Name: Not Defined Build: CSProcessor Builder Version 1.5 Build Filter: null Build Name: Build Date: 31-07-2012 13:50:38
Last Closed: 2012-12-02 23:11:16 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bill Kemp 2012-12-01 16:44:36 UTC 
Description of problem:


Version-Release number of selected component (if applicable):

BRMS 5.3.0 Getting Started Guide 

in Section:

Section 2.2 Installing the Standalone Package

at:

https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html-single/BRMS_Getting_Started_Guide/index.html#Installing_the_Standalone_Package

How reproducible:

Incorrect war file name for security setting in step #4. Should be business-central-server.war instead of business-central.war. (see below)

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Add the security domain property to jboss-web.xml which is located in server/default/deploy/business-central/WEB-INF/, for instance: 

Expected results:

Add the security domain property to jboss-web.xml which is located in server/default/deploy/business-central-server/WEB-INF/, for instance: 

Additional info:
Comment 1 lcarlon 2012-12-02 23:11:16 UTC 
Thanks for reporting, Bill.

The new documentation for BRMS 5.3.1 will go live late this week or next and that particular step is no longer required.

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