Installing Multiple LAPs on a Windows Machine

Version 3
    Share This:

    Note: In current versions of AO (from 7.7) the service name can be specified during installation, rendering this process unnecessary.

     

    Installing multiple LAPs onto a Windows machine is a little involved due to the way the installer works. It will always use the same service name during installation, so the second LAP installed will effectively disable the first.

     

    With a little preparation and some tweaks after peer installation, multiple LAPs can co-exist on a Windows box. Note that this procedure is not officially endorsed by BMC and you use it at your own risk. Also note that much of this process has been put together based on some scribbled notes, so please be aware that errors might have crept in.

     

    Preparation

    Before installation, choose values for the following items (I have included examples).

    LAP1

    Web Listen Port: 8083

    Shutdown Port: 8009

    Peer Comms: 8503

    Installation Folder: C:\Program Files\BMC Software\AO\LAP1

    LAP2

    Web Listen Port: 8085

    Shutdown Port: 8010

    Peer Comms: 8505

    Installation Folder: C:\Program Files\BMC Software\AO\LAP2

     

    Installation

    LAP1

    1. Run the installer for LAP1 as normal, using the values noted above where asked. Do not select the option to start the service after installation.
    2. When installation has completed, run regedit.exe as an administrator.
    3. Open HKLM\SYSTEM\CurrentControlSet\services and find AO-LAP.
    4. Right-click the entry and change the name to AO-LAP1.
    5. Click on this entry and double-click DisplayName.
    6. Modify the display name to be unique (e.g. add a number to the end, or an environment name such as 'Dev').
    7. Edit the ImagePath and after -zglaxservice change AO-LAP to AO-LAP1.
    8. Open the LAP's install folder, then the subfolders server and .jms (i.e. $LAPHOME$\server\.jms).
    9. Edit the file broker-config.xml.
    10. Ensure the port number specified in the uri element is as you noted above. Close the file, saving if required.

    LAP2

    1. Run the installer for LAP2 as normal, using the values noted above where asked. Do not select the option to start the service after installation.
    2. When installation has completed, run regedit.exe as an administrator.
    3. Open HKLM\SYSTEM\CurrentControlSet\services and find AO-LAP.
    4. Right-click the entry and change the name to AO-LAP2.
    5. Click on this entry and double-click DisplayName.
    6. Modify the display name to be unique (e.g. add a number to the end, or an environment name such as 'Prod').
    7. Edit the ImagePath and after -zglaxservice change AO-LAP to AO-LAP2.
    8. Open the LAP's install folder, then the subfolders server and .jms (i.e. $LAPHOME$\server\.jms).
    9. Edit the file broker-config.xml.
    10. Ensure the port number specified in the uri element is as you noted above. Close the file, saving if required.

     

    Post-Installation

    You should now reboot the server. When the server has restarted, check that both services are running.

     

    Some additional diagnostic steps that might help if things aren't working:

    • Check the LAP logs for messages that indicate a failure to bind ports.
    • At a command prompt, use the following commands (assuming the ports shown above):
    netstat -noa | findstr "8503"
    netstat -noa | findstr "8505"
    
    • Assuming that you get a result, the last column on the screen will show the process ID that is bound to each of those ports. No result means nothing is listening on the specified port.
    • Now open Task Manager and select the Processes tab. Then, from the View menu, choose "Select Columns...", tick the "PID (Process ID)" item and click OK.
    • Sort by PID and you should be able to locate the processes bound to those ports. In newer versions of Windows you can view the properties of the process and check the path; you can use this to check that the LAPs are on the right ports.

     

    Additional Notes

    It is probably possible to replace the registry edits with use of a command such as "sc". I may revisit this in the future.