Resolution:
HOWTO: Upload Gridlibs via FabricServer CLI:

FabricServer CLI allows uploading any kind of Gridlibs to the Broker. This includes:

    * Distribution Gridlib
    * JDK Gridlib
    * Container Gridlib
    * Domain Gridlib
    * Any arbitrary Gridlib needed as a base for your Container/Domain to run.

The uploadGridlib CLI command allows Gridlib upload.

If the uploaded Gridlib is a Domain or Container Gridlib, then it is added to staged resources on the Broker. As a result, they must be deployed, so that the resource gets sync'ed to all the Engines on the grid, and also to the Failover Broker, if any.

    * Use deployDomain command to deploy a Domain.
    * Use deployContainer command to deploy a Container.

All other Gridlibs (i.e. if it's not a Domain or Container) are directly added to the deployed resources on the Broker, and hence they are immediately available to be sync'ed on to the grid. Once uploaded to deployed resources, these Gridlibs are also expanded on the Broker, as one or more Domains or Containers might be depending on them.

The following order is required to successfully upload, expand, load, or deploy Gridlibs:

   1. Upload any Distribution Gridlib, JDK Gridlib, or any arbitrary base Gridlib that your Domain or Container Gridlib will depend on.

          o Wait for them to finish expanding. CLI returns after dropping the zip in the dir, it doesn't wait for them to finish expanding. (One way to verify if the Broker finished expanding is via FabricServer Dashboard's *Grid Info* panel, which should display *'Grid Libraries All unpacked'*)

   1. Upload your Container Gridlib, if any.

          o Wait for the Broker to load the Container (can be verified using *listContainers* command)

   1. Upload Domain Gridlib

          o Wait for the Broker to load the domain (can be verified using *listDomains* command)

   1. Deploy the Container.
   2. Deploy the Domain.

Uploading grid libraries via the FabricServer CLI