Re: Administration Service
Blackberry/com/btsc KB19436
I've run into this problem before, but it was with 2 BES. This is what got both of them logging in with no conflicts.
Task 1 - Backup existing configuration files to a different location
Stop all BlackBerry Administration Service services on all BlackBerry Administration Service nodes in the cluster.
Copy the file bas-object-versioning-cache-service.xml from C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\server\default\deploy\ to a different directory (e.g. Desktop).
Copy the file cluster-service.xml from C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\jboss\ejb\server\default\deploy\ to a different directory (e.g., Desktop).
Note: If you simply rename the files and leave in their original location, the modifications below will not work.
Task 2 - Edit the configuration files
Modify both attached files below, so that the TCPPING initial_hosts match the environment:
Replace BAShost2, BASHost3 etc. with the name of the other BlackBerry Administration Service nodes within the cluster.
The node order must be the same on every BlackBerry Administration Service node in the cluster.
Note: The simplest way to achieve this is to ensure after the BlackBerry Administration Service hostnames are customized, copy and replace the two customized xml files across all BlackBerry Administration Service nodes. This will ensure the order of the hosts is maintained.
Place the modified bas-object-versioning-cache-service.xml file into the following location on all BlackBerry Administration Service nodes:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\server\default\deploy\bas-object-versioning-cache-service.xml
Place the modified cluster-service.xml file in the following location on all BlackBerry Administration Service nodes:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\jboss\ejb\server\default\deploy\cluster-service.xml
Task 3 - Start all BlackBerry Administration Service nodes
Start the BlackBerry Administration Service services on only one BlackBerry Administration Service node (the first BlackBerry Administration Service node to come online will be considered the singleton and responsible for IT policy reconciliation and other critical singleton specific tasks).
Wait 7 to 10 minutes before starting the BlackBerry Administration Service services on the second BlackBerry Administration Service node.
Continue waiting 7 to 10 minutes before starting each successive BlackBerry Administration Service node.
Task 4 - Verify BlackBerry Administration Service Node Functionality
Attempt to login to each BlackBerry Administration Service node in the cluster using the hostname of the BlackBerry Administration Service node.
Verify that the login page is displayed.
Verify that the Microsoft® Active Directory® or BlackBerry Administration Service login completes successfully.
Attempt to login to the BlackBerry Administration Service console by accessing the BlackBerry Administration Service pool name (if round robin Domain Name System (DNS) is set up).
Verify that the login page is displayed.
Verify that the Microsoft Active Directory or BlackBerry Administration Service login completes successfully.
|