Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1153506

Summary: "6.1. Setting up a cluster" doesn't specify its contents is for business-central
Product: [Retired] JBoss BPMS Platform 6 Reporter: Hisao Furuichi <hfuruich>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED CURRENTRELEASE QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.3CC: bpms-support, brms-docs
Target Milestone: CR2Keywords: Reopened
Target Release: One-off release   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-18 05:10:29 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:
Embargoed:

Description Hisao Furuichi 2014-10-16 06:14:37 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/Installation_Guide/index.html#Setting_up_a_cluster

Section Number and Name:
6.1. Setting up a cluster

Describe the issue:
This section doesn't use the word, "business-central". So it's hard for some user to understand that this section is required to cluster business-central.

Suggestions for improvement: 
Please add notes like "This section is for clustering business-central. If you are not using business-central, please skip this section".

Additional information:

Comment 1 Vikram Goyal 2014-10-17 01:20:04 UTC
Hi Hisao - thanks for filing this.

I am not really sure why anyone using BPMS would not be using Business Central though? This section talks about the GIT VFS repo, which I believe is essential for anyone who is going to cluster BPMS.

Comment 2 Hisao Furuichi 2014-10-17 01:38:43 UTC
Hi Vikram. Thx for your comments.

For example, one of Red Hat' customer is planning to use JBDS to develop their assets(bpmn2,drls,etc) using their own repository. So they don't need to use business-central.
Also if business-central is running only at development environment, user will not set up business-central at production environment.

Does it make sense for you?

Comment 3 Vikram Goyal 2014-10-17 01:40:34 UTC
Yes thanks Hisao. If I were to just add "To cluster your GIT (VFS) repository in Business Central, do the following:", would that be enough?

Comment 4 Hisao Furuichi 2014-10-17 01:42:03 UTC
Sounds great Vikram.
Thank you

Comment 5 Vikram Goyal 2014-10-27 06:05:30 UTC
The note about Business Central has been added in this section [1].

Moving this to ON_QA.

Once this has been verified, I will release it in an async update.

[1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/Installation_Guide/index.html#Setting_up_a_cluster

Comment 7 Hisao Furuichi 2014-11-28 05:13:40 UTC
Hello. Our customer requests us to modify the content again. Could you take a look at their request please?

[current contents]
To cluster your GIT (VFS) repository in Business Central, do the following:

[requests to upgrade]
To cluster your GIT (VFS) repository in Business Central, do the following(If you don't use Business Central, you may skip this section):

With this fix, administrator who does not know about GIT still be able to decide whether they can skip this section or not.

Thx

Comment 8 Vikram Goyal 2014-12-01 00:08:49 UTC
Thanks Hisao - I have updated the content on the staging environment to reflect the new wording [1].

Moving this to ON_QA. Once it has been verified I will push it live.

For changes to a bug that is closed and live, could I request that a new bug is opened?

[1] https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.0/html-single/Installation_Guide/index.html#Setting_up_a_cluster

Comment 9 Hisao Furuichi 2014-12-01 00:13:49 UTC
Hello, Vikram.

Thx for your quick response. From next time, I'll open a new ticket instead of reopening existing one. Sorry for that.

Thx