Deploying Space Using CLI

To deploy a single space through the Service Grid CLI:

1. Under the gs interactive shell, change directory to the deployment repository directory, by typing cd ../config/deployment
2. Type deploy gigaspace.xml

gs> list
total services 11
[1]   GigaSpace                gigaspaces-1400-045      <?>
[2]   Grid Service Container   gs-grid                  test@11.0.0.6
[3]   Grid Service Manager     gs-grid                  test@11.0.0.6
[4]   GigaSpace_container      gigaspaces-1400-045      <?>
[5]   Grid Service Container   gs-grid                  test@11.0.0.6
[6]   Grid Service Container   gs-grid                  test@11.0.0.6
[7]   Grid Service Manager     gs-grid                  test@11.0.0.6
[8]   Lookup                   gs-grid, gigaspaces-14   11.0.0.6
[9]   Lookup                   gs-grid, gigaspaces-14   11.0.0.6
[10]  Grid Service Manager     gs-grid                  test@11.0.0.6
[11]  Lookup                   gs-grid, gigaspaces-14   11.0.0.6

To configure Space URL parameters using the gs.space.url.arg. prefix, refer to the Configuring Space URL Parameters section.

Testing and Monitoring the Deployment

Test the deployment using the list command. If the deployment was successful, you should see a new GigaSpaces instance as part of the list.

gs> list
total services 5
[1]   Grid Service Container     gs-grid                    pc-nati@11.0.0.3
[2]   Lookup                     gs-grid, gigaspaces-1333   11.0.0.3
[3]   GigaSpace                  gigaspaces-1333            pc-nati:GigaSpace_c
[4]   Grid Service Manager       gs-grid                    pc-nati@11.0.0.3
[5]   GigaSpace_container        gigaspaces-1333            <unknown>

You can also run the list space command to see specific statistics on the space:

gs> list space
total 1
Space name          count       secure clustered cache-size state
-------------------------------------------------------------------
GigaSpace           0           false  false     50000      STARTED

Deploying Space Using Admin UI

To deploy a space using the Service Grid Admin UI:

1. Start the Service Grid Admin UI, using the gs-ui utility.
2. Start the Deployment Wizard by clicking the Deploy button (see screenshot below), and select A Proactive Space as the deployment type. Click Next.

   

   • A – Deployment button.

     Selecting Application as the deployment type defines a Generic Application Service (see Compute Grid).

3. Set the deployment parameters:
   • In the Deployment Name field, enter a name to identify the deployed cache service.
   • In the Space Name field, enter a name to identify the deployed space in the Admin UI
   • In the Initial Instance Count and Maximum Instance Count fields, type 1 to deploy a single space.
   • From the Space Schema drop-down menu, select cache.
   • Leave the Cluster Schema field blank to deploy a non-clustered space.

     

     Click here to view more details about the deployment parameters.

     Parameter	Description
     Deployment Name	The cache service name.
     Space Name	The space name. Also used to define the cache cluster name.
     Initial Instance Count	The minimum number of instances that need to be running at any given point of time. The actual number of instances depends on the availability of the GSC instances. This number is used to handle failover – if the actual number of instances is less than the minimum number, the Service Grid proactively tries to re-deploy a failed service to another available machine.
     Maximum Instance Count	The maximum number of instances that need to be running. Relevant for scaling policy – if a scaling event happens (e.g. CPU utilization exceeds a certain level), a new instance is deployed and relieves some of the load from the existing cluster members. These instances are auto-deployed and un-deployed up to the maximum number of instances specified.
     Space Schema	Determines the configuration type for the space. Default selects the default schema that comes with GigaSpaces. It can be overwritten by the gs.space.url.arg.schema property. See Schema Basics for more details.
     Cluster Schema	Determines the cluster topology. The options in the drop-down menu are based on the basic topologies supported by GigaSpaces. These value can be overwritten by the gs.space.url.arg.cluster_schema property. See Cluster Schemas for more details.

     To create a Deployment Descriptor based on the default settings, click the Advanced button. This opens the Deployment Descriptor Generator, allowing you to modify the default settings.

     When you are done, press Next.

4. In this step you determine the location of the code of the GigaSpaces service, by selecting a codebase server. This enables the Service Grid to dynamically deploy GigaSpaces instances on machines that do not have GigaSpaces installed. The server location is provided as a URL.
   Select one of the GSM instances from the list.

   

5. Click Verify. This verifies that the location provided by the deployment descriptor is available. If not, another GSM instance, which maintains a reference to the service, is suggested.

   The verification step is required only if the codebase server provided in the deployment descriptor is unavailable.

   If you clicked Verify and the server is not verified successfully, this indicates that your HTTP port is not set correctly in the Service Deployment Descriptor. Open the descriptor file, and edit the tag <Parameter Name="httpPort" Value="9010" />, under <Component Name="com.gigaspaces.start">. Set the Value attribute to the current port set on your codebase server.

   Once the verification finishes successfully, the Deploy button becomes enabled.

6. Click the Deploy button to start the deployment process. Current deployment status is shown; wait for deployment to finish or press Close to abort the process.

   

Testing and Monitoring the Deployment

Viewing the Deployment

• A – the newly deployed space is added to the Service Deployments tree.
• B – the green box represents the service for the selected deployment. Double-clicking it leads you to a window called Space Administration UI, which provides the options to start the space browser and to terminate the service.
• C – this button represents the container or containers that are currently running. When pressed, details of the space or spaces running in that container are shown. If you have several containers running, you will have a button for each container.
• D – a list showing the details of the space or spaces running in the specified container.

Viewing the Service Attributes

• A – selecting a service instance displays its service deployment attributes.

Refer to the UI Undeploy, Redeploy, and Update Options section to learn how to use these options.

GigaSpaces supports space monitoring and management using JMX – the Java Management Extensions. For more details, refer to the JMX Management section.

RELATED TOPICS

Declaring Elements Globally in Deployment Descriptor

Declaring Service UI in Deployment Descriptor

Deployment Descriptor Codebase Element

Deployment Descriptor DeploymentSchedule Element

Deployment Descriptor Parameters and Configuration Elements

Deployment Descriptor SharedComponent Element

Deployment Descriptor SLA Element

deploy - Service Grid CLI

Fixed and Dynamic ServiceBean ProvisionType

Injecting Deployment Descriptor Properties into POJOs

POJO Lifecycle in Service Grid

Proactive Cache

redeploy - Service Grid CLI

Rio OperationalString

Service Associations

Service Deployment Descriptor

Service Grid ClassLoader Hierarchy

undeploy - Service Grid CLI

Using Service Grid to Deploy Partitioned Space

Using Service Grid to Deploy Partitioned Space with Backup

Using Service Grid to Deploy Replicated Space

Using Service Grid to Deploy Space

Using Service Grid to Deploy Spring Applications

Using System Properties for Deployment Descriptor Element Values