Fabric Worker
The worker installation installs the application fabric and administrative utilities on a single worker.
The installation steps described here are appropriate for manually installing:
- single worker fabrics (such as on a developer's workstation)
- small multi-worker fabrics being used for evaluation, development, testing, or small production environments
- a single worker as a preparation step for setting up for using the fabric assimilation features.
The Appistry EAF installation and basic configuration consists of the following procedures.
What about installing larger fabrics, and the fabric assimilation feature?
For information on automating the installation and configuration of fabric workers using the fabric assimilation feature, please refer to Worker Assimilation.
Prepare for installation
If installing fabric workers for production, test, or development fabrics
We assume the following:
- The fabric is segmented from the network by a firewall that restricts MCAST communication.
- The fabric is on a single network switch.
- The client and workers are on the same network segment.
- The operating system is already installed.
If installing fabric workers on developer workstations, or for an evaluation fabric
We assume the following:
- The client and workers are on the same network segment.
- The operating system is already installed.
 | Personal firewalls
Personal firewalls, such as Norton Internet Security and Zone Alarm, are known to interfere with fabric communication. Please disable all personal firewalls. |
If correct .NET runtime libraries are not installed on your system, and you intend to use .NET fabric tasks
 | Java SE 6 bug on Win32 affects fabric workers and fabric_pkg
Due to a bug in Java SE 6, the msvcr71.dll is required to be in the system path on Win32. This Java SE 6 bug affects fabric workers running Java SE 6, as well as users running fabric_pkg to package fabric applications that use Java SE 6.
The following two links document the bug:
Java 6's Release Notes: http://java.sun.com/javase/6/webnotes/ states "SE 6 applications that use custom launchers must be installed with msvcr71.dll in the same directory as the launcher executable"
Java Bug #6509291:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6509291 "Launching java using the jvm.dll no longer works without msvcr71.dll in the system path"
The following is a list of known workarounds. Again, this only occurs on Win32. Unix/Linux has no issues with Java SE 6.
- Add "Program File\Java\...\bin" to the system path on all Fabric Workers and Administrators (recommended by Appistry as the best solution).
- Copy msvcr71.dll from Program File\Java\...\bin to the system32 directory on all Fabric Workers and Administrators (this is discouraged by Microsoft).
- Copy msvcr71.dll from Program File\Java\...\bin to the Fabric\system directory on all Fabric Workers and Administrators (Appistry discourages this).
|
| None of the Appistry EAF components may be run from the CD itself.
You must install the worker components onto the worker hard drive. |
Install Appistry EAF on a worker
- Go to the directory storing Appistry EAF setup executable.
- Double-click setup.exe.
- If the .NET runtime library is not installed or you are not running the required .NET runtime library version, a dialog box appears stating the .NET components will not be registered. Your options at this point are:
- Click No to exit the installation process and install the .NET runtime library.
OR
- Click Yes to continue the installation process. You may install the .NET runtime library at a later time and register the Appistry EAF .NET components using the Appistry-provided utility.
- Click I agree to the license agreement and continue with installation.
- In the Install list, select the desired installation. You may select more than one installation type.
- Enter the fabric's MCAST address, then click Next.
| 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. |
- Click Next to accept the default installation directory or enter a different directory, then click Install.
| FABRIC_HOME
The installation directory that you select becomes the top of FABRIC_HOME, which is C:\Program Files\Fabric\system by default. |
- Click Yes to enable the fabric worker manager to automatically start when the worker reboots.
- The worker installation is now complete. Click Finish.
- Click Yes to reboot your system.
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
- 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
- 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
- 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
- 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.
