Summary: Deploys a Processing Unit onto the Service Grid.

Syntax

gs> pudeploy [processing unit name, jar file, or directory location]

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 structure. The Processing Unit should also be copied to the machine the GSM is running in under the <GigaSpaces Root>\deploy directory.

Another option to deploy a processing unit is to jar the processing unit directory structure into a jar file (that can exists anywhere within the file system) and then specify that jar file as the parameter to the pudeploy. The pudeploy 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.

For more details, refer to the Open Spaces SLA Container section.

Options

Option Description Value Format
Processing Unit name – mandatory Name of the Processing Unit directory that exists under the GSM deploy directory (see Open Spaces SLA Container).

If you are using a few options in the pudeploy command, pass this option as the last parameter. For example: gs> pudeploy -groups group1 group2 hello-world (hello-world is the Processing Unit name).
 
-cluster Allows you to control the ClusterInfo injected into the container (see ClusterInfo). The cluster option is a simplified option that overrides the cluster part of the SLA deployment descriptor. 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 bean-level 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]
-groups Allows you to specify a list of lookup groups that are used to look up the GSM to deploy to. -groups [groupName1 groupName2 ...]
-locators Allows you to specify a list of lookup locators that are used to look up the GSM to deploy to. -locators [host:port host:port ...]
-timeout Allows you to specify a timeout value (in milliseconds) when looking up the GSM to deploy to. Defaults is 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  
h / help Prints help  
-user User name for login to secured space – optional parameter  
-password Password for login to secured space – optional parameter  

Example

The following deploys a Processing Unit called data-processor using the sync_replicated cluster schema with 2 instances (total_members), a timeout value of 7 seconds (7000 milliseconds), and the lookup groups group1 and group2.

gs> pudeploy -cluster schema=sync_replicated total_members=2 -timeout 7000 -groups group1 group2 data-processor

The following deploys a Processing Unit called data-processor using context-level properties called context.properties, and bean-level properties called space1.properties applied to bean named space1.

gs> pudeploy -properties file://config/context.properties -properties space1 file://config/space1.properties data-processor

The following deploys a Processing Unit called data-processor using an SLA element read from sla.xml.

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

The following example deploys a partitionedsync2backup cluster with the name mySpace for both the Processing Unit and the Space.

 
pudeploy -cluster schema=partitioned-sync2backup total_members=2,1 -override-name mySpace -properties embed://dataGridName=mySpace /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