AccessGrid.org

Running AG2 and AG3 Service Managers Togethe (Multi-Node Configuration Only)

This section will describe how to configure and setup both 2.x and 3.x AGServiceManagers to both be running at the same time. This will then enable the user to execute either Access Grid VenueClient without requiring to shutdown one service manager and starting the other one up.

When running a multi-node configuration for the Access Grid, each machine that doesn’t run the Venue Client, ie, any machine that isn’t the display node, requires the “AGServiceManager” to be running so that the VenueClient can externally start the required services.

With the release of the Access Grid toolkit 3, you cannot simply run both AGServiceManagers at the same time without some simple modification.

The obvious reason why you cannot run them at the same time is because they both use the same port number 11000. Therefore to be able to run both at the same time, you must specify one for AGServiceManagers to use a different port number. This can be done by issuing the --port=XXXXX command where XXXXX can be a port number selected by you.

Therefore, because AG 3.x will soon become the defacto, it is suggested that it would be best to make AG 2.x use the non-standard port address.

Start-up scripts for starting the AGServiceMangers

To help with making it easier for users, it is suggested to create a couple of simple scripts and placing them in “Start-up” directory so that every time that node in logged in, the Service Mangers will automatically start up. The following will describe how to create and 2 script files for each of the service managers.

AGServiceManager for AG 2.x

Start a terminal session and type vi AGServiceManager24.sh and hit Enter. You then need to add the following lines to the new file.:

AGServiceManager24 --port=11100

After adding them save and exit (:wq).

AGServiceManager for AG 3.x

Start a terminal session and type vi AGServiceManager.sh and hit Enter. You then need to add the following lines to the new file.:

AGServiceManager

After adding them save and exit (:wq).

Copying/Adding scripts to start-up

If you are using the KDE desktop, you can copy both the newly created files to the start-up directory by issuing the command:

cp AGServiceManager24.sh ~/.kde/Autostart/

cp AGServiceManager.sh ~/.kde/Autostart/

If you are using the Gnome desktop, select “System -> Preferences -> More Preferences -> Sessions” option from the gnome panel. Select the “Startup Programs” tab from the resulting popup window. Then using the “+Add” option, add both the AGServiceManager24.sh and AGServiceManager.sh files. This should start up both script files upon logging in.

Using a different port address

Because we are using a different port for the AGServiceManager on 2.x, when “adding” ServiceManger’s within the Node Manager configuration, you will have to change the port value. If using the suggested port and scripts above, you will change the value from 11000 to 11100. This will affect the way you configure the AG 2.x services, such as Video Producers.

Benefits

The major benefit of having the ability to run both Service Managers at the same time, is that users don’t need to change any settings, as all they have to worry about is deciding which Venue Client (Either e.x or 3.x) to start up and everything will just work.

It should be noted that unfortunately you cannot have both VenueClient’s running at the same time.

login or register to post comments