Detailed description
1. The Secure Gateway Client package for RHEL (better Linux with systemd) does not support to run multiple instances.
2. As the SGC is a "simple" NodeJS application it is normally easy to run multiple instances.
Request
Please get us in contact with the developers, so that the attached enhancement patch gets into the official build.
Information for the Developers
The enhancement supports multiple instances as specified by the systemd standards.
Tested and working flawlessly in our environments.
A simple instantiable systemd unit file was created, which just have to pass the instance name to the startup script.
The startup script just has to consider the instance name where necessary.
The concept used here is to have separate sgenvironment.conf files with the file pattern: /etc/ibm/sgenvironment[-<instance>].conf
Just the UI_PORT settings must be different for each instance. The instances can even use the same ACL file.
The "issue" of avoiding duplicate ports for the Web UI has to be handled by the administrator who sets up the Secure Gateway, but that is the exactly the same issue as for the client ports to the IBM cloud services. So nothing new.
The advantage of separate instances is the separate handling and configuration (e.g. log level, ACL), and using a machine not for just one instance.
Kind regards
Matthias Bücher
| Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Transferring to @Carl Swanson for review with Development as he is now responsible for the Secure Gateway offering.
Attaching of text files is blocked, although .txt listed as allowed extension, therefore converted to PDF.