Summary: Deploys a Processing Unit onto the Service Grid.

Syntax

gs> deploy [processing unit jar file / directory location / name]
The older pudeploy command
The deploy command replaces the pudeploy command and is identical to it in terms of supported arguments and options.
pudeploy is still supported but is considered a deprecated command and will be removed in future versions

Description

A Processing Unit can be easily deployed onto the Service Grid. In order to deploy a Processing Unit, the Processing Unit must follow the processing unit directory structure.
Before deploying the processing unit you will need to jar it and then specify that jar file as the parameter to the deploy}] command. The deployment process will upload the jar file to all the GSMs it finds and unpack it under the {{deploy directory. It will then issue the deploy command.

Options

Option Description Value Format
Processing Unit Location/Name – mandatory The location of the processing unit directory or jar file on your file system (see this page).

If you are using a few options in the deploy command, pass this option as the last parameter.
For example: gs> deploy hello-world.jar
(hello-world.jar is the processing jar file).
 
-cluster Allows you to control the clustering characteristics of the processing unit.
The cluster option is a simplified option that overrides the cluster part of the processing unit's built in SLA (if such exists).
The following options are available (used automatically by any embedded space included in the Processing Unit):
  • schema – the cluster schema used by the Processing Unit.
  • total_members – the number of instances, optionally followed by the number of backups
    (number of backups is required only if the partitioned-sync2backup schema is used).
-cluster schema=[schema name] total_members=numberOfInstances[,numberOfBackups]
-properties Allows you to control deployment properties. -properties [bean name] location
-sla Allows you to specify a link (default to file-system) to a Spring XML configuration, holding the SLA definition. -sla [slaLocation]
-zones Allows you to specify a list of deployment zones that are to restrict that the deployment to specific GSCs. -zones [zoneName1, zoneName2 ... ]
-timeout Allows you to specify a timeout value (in milliseconds) when looking up the GSM to deploy to.
Defaults to 5000 milliseconds (5 seconds).
-timeout [timeoutValue]
-override-name Allows you to specify an override name for the deployed Processing Unit
(a different name than the directory name under deploy).
Mainly used when using a Processing Unit as a template.
-override-name [processing unit name]
-max-instances-per-vm Allows you to set the SLA number of instances per VM  
-max-instances-per-machine Allows you to set the SLA number of instances per machine  
-max-instances-per-zone Allows you to set the SLA number of instances per zone in the format of zoneX/number,zoneY/number  
h / help Prints help  
-secured Deploys a secured processing unit (implicit when using -user/-password) - (CLI) Security -secured [true/false]
-user -password Deploys a secured processing unit propagated with the supplied user and password - (CLI) Security -user xxx -password yyyy
You may use the Primary-Backup Zone Controller to deploy primary and backup on specific different zones.

Example

The following deploys a processing unit jar file named data-processor.jar using the sync_replicated cluster schema with 2 instances (total_members).

gs> deploy -cluster schema=sync_replicated total_members=2 data-processor.jar 

The following deploys a processing unit archive called data-processor.jar using deployment properties file called pu.properties.

gs> deploy -properties file://config/pu.properties data-processor.jar 

The following deploys a processing unit archive called data-processor.jar using an SLA element read from an external sla.xml file.

gs> deploy -sla file://config/sla.xml data-processor.jar

The following example deploys a partitioned-sync2backup space cluster with the name mySpace for both the processing unit and the Space it contains.

 
deploy -cluster schema=partitioned-sync2backup total_members=2,1 -override-name mySpace -properties embed://dataGridName=mySpace /templates/datagrid
Multiple deployment properties can be injected by having ; between each property - see below example:
>gs deploy -cluster schema=partitioned-sync2backup total_members=10,1 -properties 
"embed://dataGridName=myIMDG;space-config.proxy-settings.connection-monitor=none;space-config.engine.extended-match.regular-expressions-cache-size=600" 
-override-name myIMDG /templates/datagrid
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence