Dashboard > Appistry EAF v3.8 > ... > Installing the Fabric > Deploy the license key
Log In   View a printable version of the current page.  
  Deploy the license key

Deploying the license key

Before deploying the License Key file, you may want to open a Log Monitor to watch the progress of the License Key deployment.

Although it is not required to have a Log Monitor running prior to deploying the license.cfg, doing so would allow you to see the progress of the file being distributed throughout your fabric to the other workers.

To start the Log Monitor run the following command with your correct fabric MCAST address:

log_monitor 239.255.0.1:4000
What about this fabric MCAST address?
Each fabric is assigned a unique MCAST address. Fabric clients and utilities (like Log Monitor and Fabric Control) use this MCAST address to communicate with the fabric. This address defaults to 239.255.0.1, but can be changed by setting the fabric-address property in the addr.cfg file that is deployed to all fabric workers. The fabric MCAST address specified by clients and utilities must match the fabric-address entry in the addr.cfg or 239.255.0.1 if using the default. As you go through command and code samples, please be sure to use the correct fabric MCAST address for your installation.
Deploying the License Key
  1. Unless you already have a valid license key deployed, the Log Monitor will be displaying errors like the following:
    Sep 27 12:14:10 00:00:00:00:00:00 FabricKeeper[E:7104] License Key Error: failed to load license file
  2. To deploy the license.cfg file, run the following command with the correct fabric administrative user, password, and fabric address.
    fabric_ctl -d 239.255.0.1:30000 -u fabric-admin/fabric-admin deploy license.cfg
  3. Fabric control sends the license key file to the worker, and the fabric services will begin to startup. The Log Monitor will display a message like the following:
    Sep 27 12:26:00 00:00:00:00:00:00 FabricKeeper[I:7108] Spreading file: license.cfg
  4. If any of the workers do not start after all of the workers have cycled, you would simply initiate a start all command using fabric_ctl. This is usually only necessary if you already had stopped the worker prior to the license key expiring.
    fabric_ctl -d 239.255.0.1:30000 -u fabric-admin/fabric-admin start all

You should now have a running licensed fabric.