Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
6 replies
Subscribers
7 subscribers
Views
2195 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
there's a server A and server B which are configured as HA and their gateway
lilyc
over 11 years ago
there's a server A and server B which are configured as HA and their gateways (kdb files) are stored in a mounted device. now we want to move server B to a better server (performancewise). is it ok if I shut down the server B's Appian suit and Jboss and copy the contents and configuration to the new server then change new server's ip address to server B's ip address and start the suite and jboss on the new server B? any suggestions? advice? a simple walk through will be so much appreciated. ...
OriginalPostID-84406
OriginalPostID-84406
Discussion posts and replies are publicly visible
Parents
0
Alok Mohare
Appian Employee
over 11 years ago
After step #7 from my previous note, you can follow these steps:
8) Ensure the kdb's were copied over correctly, after the stop-suite.bat|sh so that both /gw1 and /gw2 directories have the same kdb.
9) Start engines on SERVER B and JBoss so that SERVER B can work in STANDALONE while you perform maintenance (server+configuration changes) on server A.
9) Once that is complete, stop Jboss and run a stop-suite.bat|sh on SERVER B, so that kdb's are synced between SERVER A and SERVER B
10) Verify that the kdb was copied over to both /gw1 and /gw2 directories
11) Start SERVER A and wait for all engines to come up
12) Start SERVER B and wait for all engines to come up
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Alok Mohare
Appian Employee
over 11 years ago
After step #7 from my previous note, you can follow these steps:
8) Ensure the kdb's were copied over correctly, after the stop-suite.bat|sh so that both /gw1 and /gw2 directories have the same kdb.
9) Start engines on SERVER B and JBoss so that SERVER B can work in STANDALONE while you perform maintenance (server+configuration changes) on server A.
9) Once that is complete, stop Jboss and run a stop-suite.bat|sh on SERVER B, so that kdb's are synced between SERVER A and SERVER B
10) Verify that the kdb was copied over to both /gw1 and /gw2 directories
11) Start SERVER A and wait for all engines to come up
12) Start SERVER B and wait for all engines to come up
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data