Its time for a new version of Fabric on your machine and with it comes a new Broker. Remember back to the previous page and you have A Broker Monitor, which looks after Broker Servers (each Broker Server has its own port, default 6849).
However there are some rules you need to follow
- You can only have 1 Broker Monitor per machine (pre 7.1)
- Broker Monitors can only monitor the same or lower versions than itself.
That means your 6.5 Broker monitor aint going to monitor your fancy new 7.1 Broker Server. You need to switch out the old Monitor for the Broker Monitor in 7.1, turn it on and let it happily monitor the 6.5 and 6.1 Broker Servers you may already have and THEN you can begin to add new 7.1 Broker Servers.
Switch Broker Monitor Steps
1. Install your new Broker via the webmethods installer. Dont setup any broker server instances in it yet. Choose a different broker monitor port than the old one. Doesnt matter, you wont use it anyway
2. Shut down the old Broker Monitor via the S43Broker65 script in the old Brokers directory
./S45Broker61 stop
3. In previous versions you could control which awbrokermon executable and the config directory by using environment vars.
ACTIVE_CONFIG is no longer used to point to the config dir (ie the place where awbrokermon.cfg sits and that in turn, has all the info in your Broker Servers). It seems now that your awbrokermon.cfg MUST reside in the Broker/bin directory. Not sure how to change it yet.
Remove both lines, ACTIVE_HOME is now BROKER_HOME but it is already preset inside of the new S45Broker71 file.
4. Open the _new_ awbrokermon.cfg inside of Broker/bin/awbrokermon.cfg and you will see it has only 2 lines, the IP it is bound to and the port number of the broker monitor.
Open your _old_ awbrokermon.cfg from your old config directory. There are two main components, the first two lines specifiying the user which the broker should run as and the broker server configurations. Forget the first two lines and copy paste ALL the server config lines into the _new_ awbrokermon.cfg inside of Broker/bin. This makes sure the new Broker Monitor finds all your old Broker Servers.
4. Go to your new Broker instance and run
./S45Broker71 start
Check broker monitor and broker servers are up by running
ps -efx | grep awbroker
Not only does this verify your broker monitor and servers are up it shows you which runtime executable is being used for each Broker Server.
You CAN NOT delete the old Brokers install directory. Those executables are still being run for your existing brokers. Any new brokers are run using the new executable. You can see this in action by running
Note for the EXTRA nerdy If you want to be able to flick between old and new Broker Monitors very easily, leave your ACTIVE_HOME and ACTIVE_CONFIG environment vars but point the second one at the new Broker/bin directory so it can pick up the common awbrokermon.cfg file.
