Technical Overview

References

FTP-XML Batch Job Processing

 

Technical Overview

We strongly recommend a Real Time Posting (RTP) -based solution over a batched FTP approach.  With RTP, jobs are posted in near real time, so your system stays more synchronized with Monster.

If RTP is not possible, jobs can be posted via batch files uploaded via FTP.  In this approach, the client creates an XML file containing one or more jobs for a particular user. The client drops the file off on the Monster FTP site, the Business Gateway (BGW) processes the file and returns a response file for the client to pick up that contains the results of the jobs processing. Please contact support for assistance, including FTP account creation.

Here are specific steps to follow for this process:
  1. Create an XML file with one or more jobs using the RTP guide and the toolkit.
  2. Use one SOAP envelope around all of the jobs in the file.
  3. Wrap the Job tags with a Jobs parent tag according to the job schema:
  4. <Jobs xmlns="http://schemas.monster.com/Monster">
      <Job...>
      ...
      </Job>
    </Jobs>
    
  5. Upload the XML file to the client ftp account Inbound folder.
  6. Review the results from the BGW once the response file appears in the Outbound folder and address results accordingly.
Notes:

  • The uploaded files to BGW Batch WebService are put in a queue using FIFO (First In First Out) therefore it is recommended that you upload files once per day unless there is some technical justification for more frequent uploads.
  • Jobs with add or update actions successfully processed may be viewed immediately and will be searchable in about 1.5 hours.
  • Jobs with delete action, after successfully processed will still be searchable on the site for another 1.5 hour due to the ads indexing schedule. The job will however, be locked for applying and a message will be visible to the job-seeker saying "The job has expired".
  • There is no set file naming convention for FTP-XML files, however it is recommended that you use this format: username_datetime.xml
  • The BGW authenticates only one recruiter per inbound FTP-XML file. A user is associated with a single company Xcode. In other words, the FTP-XML file needs to contain jobs belonging only to a single user.
  • No matter how many jobs are within a file, only one response file is generated and contains the results of all the jobs in the original file.
 

References

Webservices Toolkit
Common Job Errors - XML
Flat File Job Posting