Talemetry Apply/RMX Enterprise
1. Resumes are Posted to Talemetry
a. Resume is posted to hosted service at https://rmx.resumemirror.com. Resume can post here from using one of the following methods:
i. Submission from Apply Workflow
ii. Office Add-in (Outlook, Word or IE)
iii. Email forwarding (sent to a @resumemirror.net address)
iv. FTP site post (at Talemetry)
v. Back End Import (sent to Talemetry staff to import system migration data)
2. Data is never deleted until pickup
a. All data posted to the Talemetry hosted service at https://rmx.resumemirror.com will wait on the hosted service at Talemetry and will not be deleted unless the data is picked up
3. Data is retrieved using the Talemetry Java Integrator at regular intervals
a. Data is picked up from the Talemetry hosted service using the Java Integrator. You can configure the Java Integrator to poll at regular intervals. This is configurable on the Java Integrator web site configuration screen.
b. If no data is being retrieved on the Java integrator then this is likely due to one of the following reasons
i. Network access to rmx.resumemirror.com at port 443 is either being blocked or needs to be configured to use a proxy. Proxy configuration settings are in the Java Integrator interface under Configuration/Network. If it is blocked entirely and it is not due to proxy server configuration – please contact your network team.
ii. Your credentials are not correct – please check your credentials in the Java Integrator to confirm that the values are correct for the account. To see if there is a credentials error, you can review the daily log at C:\TalemetryIntegratorStorage\logs
iii. You don’t have any data to pick up on that account – you need to send through a resume through one of the Posting methods listed in step 1 for any data to be picked up.
c. You can tell if data is being retrieved by the Java integrator if XML files (one per resume) are posting into either one of the following directories below:
i. C:\TalemetryIntegratorStorage\APPLY_EBS11I\Archive – for transactions that successfully post to the iRecruitment database
ii. C:\TalemetryIntegratorStorage\APPLY_EBS11I\Error - for transactions that fail to post to the iRecruitment database
4. You can set a maximum number of resumes to retrieve per batch run of the Java integrator
a. For additional control on data pick up – you can set a maximum retrieve amount per poll directly in the C:\TalemetryIntegratorStorage\TalemetryIntegratorSettings.xml file on the Java integrator server. If you set this maximum amount then if there is a larger amount of resumes to pick up then is shown in the MaxRetrieve tag, the oldest resumes will be picked up, until the maximum value has been reached. When the next poll happens, it will pick up the next batch of oldest data to the maximum value shown here. No data is lost or deleted.
5. A stylesheet is applied to the resume data that is being picked up
a. As the resume is being picked up from the Talemetry hosted service, a stylesheet is applied to transform the data. This stylesheet is located in the directory at C:\TalemetryIntegratorStorage\settings\XSL\Apply
b. The stylesheet is set based on the Java Integrator interface value shown under Configuration/Apply for Oracle EBS and the value XSL file name. The XSL file name is a relative path that starts assumes a directory of C:\TalemetryIntegratorStorage and the path after this must be specified (i.e. a valid value would be: settings\XSL\Apply\XSLSample_For_Apply_iRecruitment11i.xsl)
c. After the stylesheet is applied, the XML data is posted in the Error or Archive folder. If the data has problems based on a stylesheet transformation then you can see the data in these folders following the transformation.
6. The XML data for the resume is posted to the Oracle database
a. The Java Integrator’s final step is to post the entire XML after the transformation into the rmx_interface table. If the data has posted to this table then the Java Integrator is working successfully.
b. The data posts to the rmx_interface table using the database credentials configured in the Java Talemetry Integrator. Please ensure that the database connection information is accurate and that the username/password being used have access to post to the rmx_interface table. You will also need to ensure that there is no network blockage from the windows server hosting the talemetry integrator to your database.
c. Database communication requires the ojdbc6.jar file to be downloaded from Oracle and copied to the folder at C:\TalemetryIntegratorStorage\settings\JDBC. If this file is missing you will not be able to post data to Oracle.
d. When data is posted to the rmx_interface table initially, it will have a status of NEW
e. If the connection fails and you need to repost resume files after the communication issue has been resolved, copy the XML files for the failed resumes from the C:\TalemetryIntegratorStorage\APPLY_EBS11I\ Error folder to the C:\TalemetryIntegratorStorage\APPLY_EBS11I\Repost folder. These will get picked up on the next run of the Java Integrator for Apply.
f. The entry in the rmx_interface table will provide an ID value that is used throughout the processing of that resume. You can use this ID value as a filter when looking at the staging tables or looking at the rmx_diagnostics table (it is the reference_id value in the rmx_diagnostics table)
7. The overseer job runs as a concurrent batch job on your Oracle database
a. All configuration settings for the running of the overseer job are set in the rmx_configuration table.
b. The rmx_configuration table setting for Overseer Interval determines how many seconds between run intervals. The default setting is 300 seconds (5 minutes)
c. If you need to repost a resume to Oracle – do not change the status of the failed transaction to NEW. Instead you will need to get the XML file from the Windows server with the Java Integrator and copy it from the C:\TalemetryIntegratorStorage\APPLY_EBS11I\ Archive folder to the C:\TalemetryIntegratorStorage\APPLY_EBS11I\Repost folder.
8. The overseer job extracts the data from the XML and places it into staging tables
a. If you query any of the rmx staging tables and filter them by ID (the ID from the rmx_interface table) then you can view the data extracted from the XML
9. The overseer job then uses the data from the staging tables to create or update an application using the delivered Oracle API
a. If the applicant is a duplicate of an existing applicant as identified by the email address then an update will be made to the existing applicant rather than creating a duplicate
b. The settings used to determine whether to update an existing applicant are in the rmx_configuration table and are Replace Existing Work History, Replace Existing Education.
10. The overseer job writes log data to the rmx_diagnostics table
a. To look at the details of a transaction and if there were any issues, query the rmx_diagnostics table where reference_id = (the value from the rmx_interface table)
b. Any lines with a status of WARNING will indicate a problem with a specific piece of data posting that does not prevent the applicant data from being created
c. Any lines with a status of ERROR indicate a problem that stopped the entire application from posting
11. If email Autoreplies are turned on then an email will be sent to the applicant with their login credentials
a. The setting to send email are in the rmx_configuration table
i. Postman Enabled must be set to Yes
ii. Applicant Email Desired must be set to Yes
b. The SMTP server must be setup within your Oracle environment
c. The subject line for the email is pulled from the rmx_configuration table - Autoreply Subject Text
d. The text of the email is pulled from the rmx_documents table – CANDIDATE_NOTIFICATION.html. This field is an HTML blob and can be updated with any standard HTML tags.
12. The applicant appears in the Oracle iRecruitment interface