Visit Platform at http://www.platform.com

ActivityService

Operation: StartActivity The StartActivity operation is used by an EGO client to request the execution of an activity on a resource. If more than one ResourceName is provided in the request, the activity is only started on the first resource in the list. Usually resources are allocated by the client prior to starting an activity, via an EGO allocation request. Thus the AllocationID within the request message is one returned from a previous RequestAllocation call. The version of JSDL supported in the request message is JSDL v1.0 (TODO: put pointer to specification). Generic link to WS-Security support.
Input Message

The StartActivityRequest contains the following elements:

  • ClientName - the registered EGO client making this request. This field is required.
  • AllocationID - the identifier of a prior allocation request that has been used to provide the resources that will be used to execute the defined activity.
  • ResourceName - one or more elements indicating where the activity is to be executed. If more than one ResourceName element is present, then the activity will only be started on the first resource listed.
  • A choice element that takes either an EGO ActivitySpecification or a JSDL JobDefinition element. One or the other is a required element. This element is used to provide the execution parameters of the activity, such as command line, the OS user id used to execute the activity, shell limits, etc.
  • Option - zero or more elements that can be used to modify the behaviour of this operation. Currently there are no options defined.
Output Message

The response message for StartActivity contains the ActivityID assigned by EGO to this activity. The ActivityID can then be used in other operations to manage and query the state of the activity.


Operation: ControlActivity The ControlActivity operation is used by an EGO client to manage the state of an activity started with a prior call to StartActivity. The operation is chosen via the ActivityControlOperation element within the request message. (TODO: describe who can perform this operation ... i.e the activity "owner" and the cluster/consumer admins?). Generic link to WS-Security support.
Input Message

The ControlActivityRequest contains the following elements:

  • ClientName - the registered EGO client making this request. This field is required.
  • AllocationID - the identifier of the activity to manage, as returned from a previous call to StartActivity. This is a required element.
  • ActivityControlOperation - an enumerated string that indicates what operation to perform on the activity. Currently the operations "signal", "terminate", "suspend", "resume", "checkpoint", and "restart" are defined, with only "signal" being supported at this time.
  • The final element is an optional choice, where the element used depends on the chosen operation. The current choice elements, based on operation are:
    • "signal" - a Signal element that indicates the POSIX signal name to be delivered to the Activity. At this time, only SIGKILL is supported.
Output Message

Currently, the response message from ControlActivity is an empty element tag (<ControlActivityResponse/>).




Date Modified: 26 Nov 2007
Platform Computing: www.platform.com

Platform Support: support@platform.com
Platform Information Development: doc@platform.com

Copyright © 1994-2007 Platform Computing Corporation. All rights reserved.