This article applies to FusionReactor On-Premise customers only. These customers are identified by their license keys which do not begin with CLOUD-. Some users run FusionReactor behind restricted firewalls which do not allow all outbound connections. In this case, these users may need to add specific firewall rules to allow FusionReactor to communicate with our licensing infrastructure.
FusionReactor licensed with on-premise (non-Cloud) licenses requires access to the following DNS address in order to communicate with our licensing service
This address resolves to one or more IP addresses which are attached to a load-balanced cluster. These IP addresses are dynamic and can change without warning.
If you are unable or unwilling to use the dynamic DNS rules above, we have provided a static IP address which can be used for this service.
N.b. this is not the address of our dynamic licensing service (see above) but for the static endpoint at api-intergraldata-static.fusionreactor.io.
After enabling this firewall rule, the following -D option needs to applied to your JVM environment, to instruct FusionReactor use this address for licensing:
If you are using a non-standard Java security policy, you may have to add rules to it to allow FusionReactor to connect to these services. The form of these rules is:
Should FusionReactor be completely unable to communicate with our licensing service, you should note the following:
Customers upgrading from FusionReactor On-Premise to FusionReactor Cloud should also read technote FRS-418, which is linked below in the Related Issues section. This has further information for required firewall transits.
|Components:||License + Activation|
|Last Updated:||Today 3:59 PM|
FRS-384: Proxying FusionReactor
FRS-418: FusionReactor Cloud Firewall DNS and Static IP address rules
Comments are closed.