Active-Passive
- Go to http://localhost:8181
- Log in as admin/admin.
- Click on the Containers tab.
- Select both lab9container1 and lab9container2 and click on the Stop button.
- Once stopped, open gedit.
- Click Open and browse to ~/FuseWorkshop/Fuse6.2.1/instances/lab9container1/etc
- Select system.properties.
- Go to the end of the file, and add a new line.
- Copy and paste the following lines:
- Save the file and close it.
- It should look like this:
- Repeat the procedure for lab9container2
|
Red Hat JBoss Fuse provides failover capability using either a simple lock file system or a JDBC locking mechanism. In both cases, a container-level lock system allows bundles to be preloaded into the slave kernel instance in order to provide faster failover performance. |
|
- Open a terminal and create the sharedLock dir by executing mkdir ~/FuseWorkshop/Fuse6.2.1/sharedLock
- Go back to the web browser.
- Click on the Containers tab.
- Select lab9container1 and click on the Start button.
- Select lab9container2 and click on the Start button (since this is the passive container, it won’t appear as started).
- Select lab9container1 and click on the Stop button.
- Fabric should have detected that the active container has stopped and started the passive container.
- Check that lab9container2 is now running.
- Select lab9container2 and click on the Stop button.
- Open gedit and remove the previously added lines to both system.properties files (one for lab9container1 and one for lab9container2).
- Select both lab9container1 and lab9container2 and click on the Start button.