Adapting PeopleSoft Integration: Practical Solutions for Handling the Loss of Database Links inside your SQRs

  • Home
  • Adapting PeopleSoft Integration: Practical Solutions for Handling the Loss of Database Links inside your SQRs
ReviveoSoft
Blog Details Img

Problem Statement and Solutions for Integrating PeopleSoft with Upgraded Software

Problem Statement

You are running an on-premises PeopleSoft instance and using SQRs (Structured Query Reports) to connect to another on-premises software via database links. With the recent upgrade of this other software, database links are no longer offered as an integration point. This change presents a challenge, as your existing SQR programs rely on these links to exchange data between the systems. Since SQRs do not support modern integration methods like REST or SOAP APIs, you need practical solutions to ensure continued functionality of your data integration processes.

Proposed Solutions

1. Use a Staging Database with Data Import/Export

Description: Establish an intermediate staging database to handle data transfer between the upgraded software and PeopleSoft.

Implementation:

  • Export data from the upgraded software to a staging database using its available export functionalities or custom scripts.
  • Create a process to import this data from the staging database into PeopleSoft.
  • Modify your SQR program to access the data from the staging database instead of relying on direct database links.

Advantages:

  • Ensures compatibility with SQR by maintaining database interactions.
  • Allows for data validation and transformation before integration with PeopleSoft.

Considerations: You'll need to set up and manage the staging database and handle data import/export processes.

2. Develop a Middleware Application

Description: Create a middleware application to bridge the gap between the upgraded software and PeopleSoft.

Implementation:

  • Develop the middleware in a technology stack that supports modern integration methods (e.g., Java, .NET).
  • Configure the middleware to extract data from the upgraded software.
  • Transform and load the data into a format or location accessible by SQR, such as a flat file or a staging database.

Advantages:

  • Enables advanced integration capabilities while keeping SQR operations intact.
  • Offers flexibility in handling data transformation and integration.

Considerations: Developing and maintaining the middleware application requires additional resources and expertise.

3. Utilize Flat File Integration

Description: Implement a system for exporting data from the upgraded software to flat files and then use SQR to process these files.

Implementation:

  • Configure the upgraded software to export data to flat files (e.g., CSV, XML).
  • Generate these files on a scheduled basis or as needed.
  • Update the SQR program to read and process these flat files instead of relying on database links.

Advantages:

  • Simplifies the integration process by avoiding direct database connections.
  • Allows SQR to function within its existing capabilities.

Considerations: Ensure that flat file formats are consistent and reliable for integration purposes.

Conclusion

With the discontinuation of database links, integrating PeopleSoft with the upgraded software requires innovative solutions. By utilizing a staging database, developing a middleware application, employing flat file integration, or adding database-level triggers, you can maintain functionality and adapt to the new integration constraints. Each solution has its own set of benefits and considerations, so choose the approach that best fits your operational requirements and technical capabilities.