Bug 1324501 - [Doc] Missing backup DC "unpromoting" procedure
Summary: [Doc] Missing backup DC "unpromoting" procedure
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Andrea Hoffer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-06 13:38 UTC by oarribas
Modified: 2019-03-01 12:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Build Name: 23087, Administration and Configuration Guide-6.4 Build Date: 08-10-2015 16:59:36 Topic ID: 13661-743899 [Latest]
Last Closed: 2019-03-01 12:29:11 UTC
Type: Bug


Attachments (Terms of Use)

Description oarribas 2016-04-06 13:38:32 UTC
Title: About Domain Controller Discovery and Failover

Describe the issue: There is no information about the "unpromoting" procedure.


Suggestions for improvement:
A new procedure with the information to "unpromote" the backup DC could be added.
As https://access.redhat.com/support/cases/#/case/01279577?commentId=a0aA000000Cy5dDIAR, write-remote-domain-controller pointing it back to the original DC is needed. For example:

/host=HOST_NAME:write-remote-domain-controller(host="${jboss.domain.master.address}",port="${jboss.domain.master.port:9999}",security-realm="ManagementRealm",username="${username}")


Additional information:
As this comment: https://access.redhat.com/support/cases/#/case/01279577?commentId=a0aA000000CxTPQIA3 several backup host can be configured, but this information is also missing in the documentation.

<domain-controller>
    ...
    <static-discovery name="primary" host="<DC-IPAddress>" port="9999"/>
    <static-discovery name="backup1" host="<Host1-Address>" port="9999"/>
    <static-discovery name="backup2" host="<Host2-Address>" port="9999"/>
    <static-discovery name="backup3" host="<Host3-Address>" port="9999"/>
    ...
</domain-controller>


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