Using CI with a Third Party Application
Connecting the Recruit Workforce Module to Recruitmax Using CI
Posted on 1/11/2007 (originally published in print on 8/1/2004)
by Joe Moglia
At some point during our illustrious careers I think almost all of us have been asked to build a file-based interface from a third party application to one of our PeopleSoft applications. The file- based interface is the work horse of the industry and an old friend for many of us. However, in this article I hope to provide a good example of how our old friend is not the only option for every interface to our PeopleSoft applications.
This article will detail how my company used PeopleSoft's Component Interface technology to build a practical and efficient real time interface between Recruitmax, a web-based third party recruiting application, and our PeopleSoft Recruit Workforce module.
In many situations, file-based interface architecture is the most appropriate, but consider the following questions:
Can you afford to wait for a batch to run before your data is available in your PeopleSoft applications?
Have you ever had a significant portion of the transactions in a batch file rejected because of data validation issues? Do you or someone on your team have to help end users straighten out the data problems?
Are you tired of adding on-line validation and then adding that same validation to your batch program?
Do you have time to monitor and check batch logs?
Component Interfaces can solve many of the issues in the questions above. This technology makes real time transactions with third party software applications possible and, most importantly, practical. PeopleSoft has come a long way with this technology since the days of Message Agents. Below is an overview of how we used Component Interfaces to get our new Recruitmax application to talk directly with PeopleSoft's Recruit Workforce module.
The Problem
To continue reading this article you must have a current VP1 Subscription.
