If a FusionReactor client is unable to contact its license service, it will revert to a manual license activation procedure. During this process, the user must copy an encrypted request into our licensing portal, and past an encrypted reply back into the client.
For large volumes of servers, this process must be repeated and requires significant time and effort.
FusionReactor’s internal license service can use standard HTTPS proxies, however, such as Squid.
Add the following options to your JEE container’s Java properties or startup options file:
… setting them appropriately for your organization.
FusionReactor will then contact its licensing services via this proxy.
If your corporate networking administration requires you to request specific targets, these should be data.intergraldata.com and license.fusionreactor.io, port 443 (HTTPS).
For JEE server environments which have been ‘locked down’ and made as secure as possible, the default Java Security Manager policy may have been tightened up somewhat.
By default, this is permission java.security.AllPermission;, but this may have been altered to provide a greater degree of security.
In order to allow connections to our license service, the Java process in which FR runs must be granted the following Permissions:
permission java.net.SocketPermission “license.fusionreactor.io:443”, "connect, accept, resolve”;
permission java.net.SocketPermission “data.intergraldata.com:443”, "connect, accept, resolve”;
permission java.net.SocketPermission “corp-proxy.acme.com:3128”, "connect, accept, resolve”;
The final permission in the list should be replaced with your own corporate proxy server, if you are using one. This rule allows FR and the JVM to connect using it.
|Components:||License + Activation|
|Last Updated:||Today 1:16 PM|
FRS-418: FusionReactor Cloud Firewall DNS and Static IP address rules