Submit a job (Deprecated)

Purpose

Deprecated since version 9.1.5. Use this API instead: Submit a job (POST).

Submits a job to IBM Spectrum LSF Application Center.

  • Precondition: the administrator has prepared and published the application.

  • For any parameter, the value specified by the web service request overrides the default value specified by the application form.

  • The job is submitted as the logged in user.

  • Just like through the web graphical interface, when you submit a job, a temporary directory is created for the job and the file you attached is copied to the directory. The owner for the directory is the user that is logged on. The directory inherits the logged on user’s umask permission on the Platform Application Center host.

Request


HTTP Request Field Field format/value Notes
HTTP Method POST  
URL http://<hostname>:<port>/platform/webservice/pacclient/submitapp  
Content-Type (header) multipart/mixed;boundary=YYYYY  
Accept text/xml  
Cookie platform_token=<token> <token>:returned from logon
Body --boundary<Application Name Area (table 1)>--boundary<Parameters Area (table 2)>--boundary<File Attachment (table 3)> boundary can be any random unique string. For details, see additional tables.

Application Name Area


Field Name Field format/value Notes
Content-Disposition Form-data;name="AppName"  
Content-ID AppName  
Content <App_Type[:App_Instance]> Specify App_Type only if there is no App_Instance

Example
-----------------------------------
Content-Disposition: form-data; name=AppName
Content-ID: <AppName>
"\r\n"
FLUENT:FLUENT_WEB
-----------------------------------

Parameters Area


Field Name Field format/value Notes
Content-Disposition Form-data;name="data"  
Content-Type multipart/mixed;boundary=XXXX  
Content-ID <Data>  
Content --boundaryContent-Disposition: form-data; name=”c1”Content-Type: application/xml; charset=US-ASCIIContent-Transfer-Encoding: 8bit“\r\n”
<AppParam>  
   <id>%s</id>    <value>%s</value>
   <type>%s</type> 
</AppParam>
--boundary
Content-Disposition: form-data; name=”c1”Content-Type: application/xml; charset=US-ASCIIContent-Transfer-Encoding: 8bit“\r\n”<AppParam>    <id>%s</id>    <value>%s</value>   <type>%s</type> </AppParam>--boundary…--boundary--
<id>%s</id> defines the parameter name on the application form<value>%s</value> defines the value of the parameter. The value format for a file: <Filename>,upload|copy|linkUpload: upload file from local. File must be attached in attached area of this request.Copy: copy file to job directoryLink: link file to job directory. <type>%s</type> defines the parameter type. The possible values are: “file” or empty. “file” indicates the current parameter is a file .

Example
-----------------------------------
Content-Disposition: form-data; name='data'
Content-Type: multipart/mixed; boundary=_Part_1_701508.1145579811786
Content-ID: <data>
“\r\n”
--_Part_1_701508.1145579811786
Content-Disposition: form-data; name='c1'
Content-Type: application/xml; charset=US-ASCII
Content-Transfer-Encoding: 8bit
“\r\n”
<AppParam>  <id>JOB_NAME</id> <value>From_webS</value><type></type> </AppParam>
--_Part_1_701508.1145579811786
Content-Disposition: form-data; name='c3'
Content-Type: application/xml; charset=US-ASCII
Content-Transfer-Encoding: 8bit
“\r\n”
<AppParam>  <id>FLUENT_JOURNAL</id> <value> fluent-test.jou,upload </value> <type> file</type> </AppParam>
--_Part_1_701508.1145579811786--
----------------------------------

File Attachment


Field Name Field format/value Notes
Content-Disposition Form-data;name="f1"  
Content-Type application/octet-stream  
Content-ID <Filename>  
Content-Transfer-Encoding UTF-8  
Content <File content in bytes>  

Example
-----------------------------------
Content-Disposition: form-data; name='f1'
Content-Type: application/octet-stream
Content-Transfer-Encoding: UTF-8
Content-ID: <fluent-test.jou>
“\r\n”
PGh0bWw+CiAgPGhlYWQ+CiAgPC9oZWFkPgogIDxib2R5PgogICAgPHA+VGhpcyBpcyB0aGUg
-----------------------------------

Response


HTTP Response Field format/value Notes
Response code "200" - connection ok; otherwise connection failed  
Success Message
<Job>
  <name>%s</name>
  <id>%s</id>
  <status>%s</status>
  <cmd>%s</cmd>
</Job>
Failure Message
<Job>
  <errMsg>%s</errMsg>
</Job>
%s=return error message