Hello all -
Recently I worked on a deployment where I installed FglAM on a Windows host and configured it as a Windows Service. It then became necessary for me to deploy a second FglAM to the same host. I also wanted to run it as a Windows Service. Here's how to do it:
1. Complete the first FglAM install as you would normally (in my case I did this since I didnt know at the time that I'd need a second FglAM)
2. Install the second FglAM to a separate installation directory, which we'll assume for this discussion is C:/newfglam. Do not install it as a Windows Service, and do not start the fglam at this time.
3. Create a unique-named state directory in its installation:
C:/newfglam/bin/fglam.exe --create-state -l <state dir path>
The <state dir path> is the full pathname to a directory that will hold this fglam's setup, including configuration files, agent instances, etc. So for the above, you might say:
C:/newfglam/bin/fglam.exe --create-state -l C:/newfglam/newstatedir
4. If this fglam is going to report into the same FMS as the first fglam then you should make sure that the setup in the newstatedir does not report in from the same hostname as the first fglam. Edit the C:/newfglam/newstatedir/default/config/fglam.config.xml file and look for the <config:host-display-name> block. Near the bottom of this block, find the <config:name> and change it so that the line looks like:
Then save the file and exit the editor.
5. Now you can install this fglam instance as a service:
C:/newfglam/bin/fglam.exe -l C:/newfglam/newstatedir --install-service
This should install this fglam instance as a Windows Service with the state directory path visible in the service name so that you can distinguish it from the first fglam. Now you can start this Service if it has not already started.
6. Verify in the Foglight UI Agent Hosts page that you see entries for both fglams.
That oughta do it. Hope you're having fun with Foglight.