Cloud Search XML Upload Guide

Technical Overview

Development

• 1. Create the XML request
  2. Post the request using one of 2 methods:
     • web services
     • file based
  3. Receive (Business Gateway) BGW response
  4. Respond accordingly
• All system calls to Monster are developed by the client.
• Client is responsible for testing their own implementation.
• Monster will be available to answer questions client has about implementation.
• JobSeeker is the term used throughout this guide which maps to Employees, Candidates and Seekers
• JobSeeker posting is done against Monster's BGW.
• A user account is needed for authentication purposes. A Monster representative will provide the client with a test user account and a production user account.
• Resume uploads for each client are segmented by Channel (data container in which job seekers are stored) and Resume Board (data container in which resumes are stored). The Ids for those are provided to client by a Monster representative.

Key Points

• Email address has to be unique for each jobseeker within one private resume board. Job seekers are uniquely identified by the jobseeker's email address.
• Only one resume can currently be active for a given jobseeker on a private resume board.
• Requests done via FTP-XML Batch processing is limited to a maximum of 200 JobSeekers per file, with a maximum individual resume file size of 5 MB.
• Requests sent in real time using web services can only include one JobSeeker per request with a maximum individual resume file size of 5 MB.
• NOTE: Any data that is uploaded will be available to the client's users doing the resume searches. Therefore ONLY data that the client wishes to be exposed to those users should be provided.

Creating the XML Request

Sample XML Request

<SOAP-ENV:Envelope xmlns:SOAP-ENV="https://schemas.xmlsoap.org/soap/envelope/">
  <SOAP-ENV:Header>
    <mh:MonsterHeader xmlns:mh="https://schemas.monster.com/MonsterHeader">
      <mh:MessageData>
        <mh:MessageId>Jobseeker Private db sample</mh:MessageId>
        <mh:Timestamp>2013-04-10T14:41:44Z</mh:Timestamp>
      </mh:MessageData>
      <mh:ProcessingReceiptRequest>
        <mh:Address transportType="http">http</mh:Address>
      </mh:ProcessingReceiptRequest>
    </mh:MonsterHeader>
    <wsse:Security xmlns:wsse="https://schemas.xmlsoap.org/ws/2002/04/secext">
      <wsse:UsernameToken>
        <wsse:Username>username</wsse:Username>
        <wsse:Password>password</wsse:Password>
      </wsse:UsernameToken>
    </wsse:Security>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
   <JobSeekers xsi:schemaLocation="https://schemas.monster.com/Monster https://schemas.monster.com/current/xsd/JobSeeker.xsd" xmlns="https://schemas.monster.com/Monster" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance">
<JobSeeker status="Active" seekerAction="addOrUpdate" seekerRefCode="jobseeker1">
      <Channel monsterId="9999" />
      <PersonalData>
        <Contact>
          <StructuredName>
            <GivenName>GivenName1</GivenName>
            <FamilyName>FamilyName1</FamilyName>
          </StructuredName>
          <Address>
            <City>City</City>
            <State>ST</State>
            <CountryCode>US</CountryCode>
            <PostalCode>00000</PostalCode>
          </Address>
          <E-mail>jobseeker1@seeker.com</E-mail>
        </Contact>
      </PersonalData>
      <Resumes>
        <Resume resumeAction="addOrUpdate">
          <BoardName monsterId="8888" />
          <TextResume><![CDATA[This is the text resume for job seeker 1.
           This is just a sample resume.]]></TextResume>
        </Resume>
      </Resumes>
    </JobSeeker>
<JobSeeker status="Active" seekerAction="addOrUpdate" seekerRefCode="jobseeker2">
      <Channel monsterId="9999" />
      <PersonalData>
        <Contact>
          <StructuredName>
            <GivenName>GivenName2</GivenName>
            <FamilyName>FamilyName2</FamilyName>
          </StructuredName>
          <Address>
            <City>City</City>
            <State>ST</State>
            <CountryCode>US</CountryCode>
            <PostalCode>00000</PostalCode>
          </Address>
          <E-mail>jobseeker2@seeker.com</E-mail>
        </Contact>
      </PersonalData>
      <Resumes>
        <Resume resumeAction="addOrUpdate">
          <BoardName monsterId="8888" />
          <TextResume><![CDATA[This is the text resume for job seeker 2.
           This is just a sample resume.]]></TextResume>
        </Resume>
      </Resumes>
    </JobSeeker>
</JobSeekers>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

SOAP Envelope

<SOAP-ENV:Envelope xmlns:SOAP-ENV=
"https://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <!-- see Header section below -->
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
        <!-- see Body - JobSeeker section below -->
    </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Header

    <mh:MonsterHeader xmlns:mh="https://schemas.monster.com/MonsterHeader">
      <mh:MessageData>
        <mh:MessageId>Jobseeker Private db sample</mh:MessageId>
        <mh:Timestamp>2013-04-10T14:41:44Z</mh:Timestamp>
      </mh:MessageData>
      <mh:ProcessingReceiptRequest>
        <mh:Address transportType="http">http</mh:Address>
      </mh:ProcessingReceiptRequest>
    </mh:MonsterHeader>
    <wsse:Security xmlns:wsse="https://schemas.xmlsoap.org/ws/2002/04/secext">
      <wsse:UsernameToken>
        <wsse:Username>username</wsse:Username>
        <wsse:Password>password</wsse:Password>
      </wsse:UsernameToken>
    </wsse:Security>

Body - JobSeeker

1. Processing Information
   This section contains information about the way the JobSeeker message will be processed, under which account, the channel to be used and the seekerRefCode, if client chooses to provide this piece of data.
   
   The attributes seekerScope and status are required in order for the seeker to be searchable.
   
   The seekerRefCode is a unique piece of data that the client provides for the seeker and can use for identifying and tying the seeker back to the client system.

   <JobSeeker status="active" seekerAction="addOrUpdate" seekerRefCode="Id_in_ATS">
       <Channel monsterId="9999"/>
       

2. JobSeeker Information
   This contains the main information that will be defined in the JobSeeker's account. Example: name, address, availability, education, etc.
   
   For location information, refer to http://integrations.monster.com/Toolkit/LocationEnumeration.
   
   Data for some fields has to be selected from a set list of values, referred to as enumeration values, found at https://schemas.monster.com/Current/XSD/Enumerations.xsd. If in the schema the element type contains "EnumStr" in it, such as this element definition, then that element needs an enumerated value populated. Here is an example from the schema:
   
   

   <xsd:element name="CareerLevel" type="CareerLevelEnumStr">
   

   
   
   Here is an example of jobseeker data:
   
   

   <PersonalData>
       <Contact>
           <StructuredName>
              <GivenName>GivenName</GivenName>
   	    <FamilyName>FamilyName</FamilyName>
   	</StructuredName>
           <Address>
   	    <StreetAddress>StreetAddress</StreetAddress>
   	    <City>City</City>
   	    <State>ST</State>
   	    <CountryCode>US</CountryCode>
   	    <PostalCode>00000</PostalCode>
           </Address>
               <Phones>
   	    <Phone phoneType="home" priority="primary">(999) 999-9999</Phone>
              <Phone phoneType="mobile" priority="secondary">(999) 999-9988</Phone>
   	</Phones>
   	<E-mail>jobseeker1@seeker.com</E-mail>
       </Contact>
   </PersonalData>
   <Profile>
       <CareerLevel monsterId="13"></CareerLevel>
       <TotalYearsWorkExperience monsterId="7"></TotalYearsWorkExperience>
   </Profile>
   

3. JobSeeker Resumes
   This section supplies the JobSeeker's resume. There are a couple of examples below.
   
   Text Resume example:

   <Resumes>
       <Resume resumeAction="addOrUpdate" >            
           <BoardName monsterId="9999"/>
           <ResumeTitle>Resume of jobseeker 12345</ResumeTitle>
           <ResumeModDate>2010-12-30T17:13:38Z</ResumeModDate>
                 <TextResume>
                     <![CDATA[ This is the text resume for job seeker 1. This is just a sample resume.]]> 
           </TextResume>
           <ResumeOrigin>
   <Origin monsterId="4"/>
                           <OriginDescription>corporatewebsite.com</OriginDescription>
    </ResumeOrigin>  
       </Resume>
   </Resumes>
   
    
    
   Docx resume example:
   
    
    
   <Resumes>
     <Resume resumeAction="addOrUpdate" >
       <BoardName monsterId="8888"/>
       <ResumeTitle>Resume 2 of jobseeker 12346</ResumeTitle>
       <ResumeModDate>2010-12-22T15:19:58Z</ResumeModDate>
       <ResumeDocument documentAction="add">
           <File>
            base64binary encoded resume document goes here
           </File>
           <FileName>jobseeker1.docx</FileName>
       </ResumeDocument>
     </Resume>
   <Resumes>
   
   

FTP-XML Batch Processing

Supported Document Types and Encoding

Common tasks

Adding a new JobSeeker and Resume

Modifying a JobSeeker and Resume

Deleting a Jobseeker (Only for non-OFCCP company)

  <SOAP-ENV:Body>    
    <JobSeekerDeleteBySeekerRefCode>
	<SeekerRefCode>jobseeker12345</SeekerRefCode>
	<ChannelID>9999</ChannelID>
        <ChannelAlias>PRS99849912</ChannelAlias>
        <ResumeBoardID>8888</ResumeBoardID>
    </JobSeekerDeleteBySeekerRefCode>
  </SOAP-ENV:Body>

Delete by Email address:

  <SOAP-ENV:Body>
    <JobSeekerDeleteByEmailAddress xmlns="https://schemas.monster.com/Monster" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="https://schemas.monster.com/Monster https://schemas.monster.com/Current/xsd/Monster.xsd">				    
       <EmailAddress>jobseeker12345@seeker.com</EmailAddress>
       <ChannelID>9999</ChannelID>
       <ChannelAlias>PRS99849912</ChannelAlias>
       <ResumeBoardID>8888</ResumeBoardID>
    </JobSeekerDeleteByEmailAddress>
  </SOAP-ENV:Body>

     

Deactivating a Jobseeker (Only for OFCCP)

<SOAP-ENV:Body>
    <DeactivateResume xmlns="https://schemas.monster.com/Monster" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="https://schemas.monster.com/Monster https://schemas.monster.com/Current/xsd/Monster.xsd">
        <EmailAddress>jobseeker12345@seeker.com</EmailAddress >
	<ChannelID>9999</ChannelID>
        <ChannelAlias>PRS99849912</ChannelAlias>
        <ResumeBoardID>8888</ResumeBoardID>
    </DeactivateResume>
</SOAP-ENV:Body>
     

Testing

1. Use the webservices toolkit (http://integrations.monster.com/Toolkit) to start your testing. There are samples on the main page of the toolkit in the Samples section. In this tool, use the Validate button to confirm that you have your jobseeker XML in compliance with the Monster schemas including all data fields that are in scope for the project.
2. Then from your own web services application to do an HTTP POST of a single jobseeker to BGW URL: https://gateway.monster.com:443/bgwPower 
   (NOTE: Monster's BGW uses port 443; this is not an industry standard port so in some cases it needs to be configured in client's firewall. It is not necessary for client to use port 443 to exit their system.)
3. Receive and review BGW response
4. Respond accordingly
   • If successful, then no action needed
   • If errors, then fix and repost

1. Use the webservices toolkit (http://integrations.monster.com/Toolkit) to start your testing. There are samples on the main page of the toolkit in the Samples section. In this tool, use the Validate button to confirm that you have your jobseeker XML in compliance with the Monster schemas including all data fields that are in scope for the project.
2. Make sure to always check the "Use BGWPower" checkbox when testing any requests in this tool.
3. Using XML that worked within a single record from step 1, create an FTP-XML batch file with 5-10 records and wrap it inside of a JobSeekers tag. Note the "s" in that field name which signifies that it will contain multiple records, i.e. a batch file.
4. Upload test file to testing FTP folder (structure shown below) and let MPS team know so the test file will be processed and feedback will be provided.
5. Respond accordingly
   • If successful then no action needed
   • If errors, then fix and re-upload