Bug 1250144 - Installation guide is missing steps about the installation in the JBoss Web Server
Summary: Installation guide is missing steps about the installation in the JBoss Web S...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Documentation
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Petr Penicka
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-04 15:17 UTC by Spolti
Modified: 2019-07-11 09:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-14 11:17:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BXMSDOC-55 0 Major Resolved Installation guide is missing steps about the installation in the JBoss Web Server 2016-11-07 08:04:41 UTC

Description Spolti 2015-08-04 15:17:53 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BRMS/6.1/html/Installation_Guide/Installing_JBoss_BRMS_on_JBoss_EWS_2.html


Section Number and Name: 
1.8 - INSTALLING RED HAT JBOSS BRMS ON RED HAT JBOSS WEB SERVER

Describe the issue: 
The section about to activate the BTM config is missing.

Suggestions for improvement: 
Like the BPMS documentation, it should have the following steps:


Add the following valve in the server.xml file:
<Listener className="bitronix.tm.integration.tomcat54.BTMLifecycleListener" />

Create the file setenv.sh:
CATALINA_OPTS="-Xmx512M -XX:MaxPermSize=512m -Dbtm.root=$CATALINA_HOME -Dbitronix.tm.configuration=$CATALINA_HOME/conf/btm-config.properties"

BPMS doc: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html/Installation_Guide/sect-The_Generic_Deployable_Bundle_Installation.html#Downloading_deployable_package

Additional information:

Comment 2 Petr Penicka 2015-09-14 11:17:06 UTC
Issue was migrated to JBoss JIRA, see linked issue for details. Closing here.


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