Forum members - I am looking for anyone who has any experience in integrating PeopleSoft Enterprise HRMS 9.1 with the OPA 10.4 batch processor using PeopleSoft dbase tables that can be easily accessed by AE/SQR programs. Due to very high throughput requirements with a large corporate client...using IB/WSDL/web service integration is out of the question.
Also, this integration has to be very reliable (IB has a tendency to intermittently error out).
Has anyone on this forum done this ? This client will be presenting high daily OPA determination processing...so batching it up on a recurrence of an AE program and writing input to a table...waiting for OPA 10.4 batch processing to trigger/complete...and then read the results back into the PSoft HRMS 9.1 app pages from an output table seems the way to go....
I would appreciate talking to anyone who has gone this route. Thanks
If you really want performance I'd suggest using the Oracle Determinations Engine (ODE) direct API. This is available in both Java and .NET and is blisteringly fast compared to the web service. This way you maintain control over your own data handling. The batch processor in 10.4 is good but for out and out performance use the ODE API..
There have been quite a few performance improvements in the batch processor between 10.4 and 10.4.1 and OBP is basically a high performance database wrapper around the engine API's. There is a lot you can do with views and / or staging table and OBP configuration to make batch processing both performant and reliable without resorting to low(ish) level API programming.
Thanks for the replies. The client I am working for wants blisteringly fast real-time answers from the OPA Determinations-API back to the PSoft 9.1 application pages (without using IB).
We are looking at very high user populations (10,000+ per day). As much as I may want to use fast batch-processing solutions...it probably is not going to be suitable.
Thanks for your kind replies. -Robert A. Ward
IB = Integration Broker.
If you can resolve or improve the separate issue of IB erroring out then the web service call (determination server) should give you the performance you need based on the volumes you have mentioned.
Otherwise you could look into the applicability of your page PeopleCode using Java to make a direct call into the determination engine (and bypassing IB).
I have worked with the Batch Processor and PeopleSoft and the performance is excellent. The trick is the key for the record is expected to be a unique number, so the composite keys typically used in PeopleSoft are not ideal. I created views to be able to use the batch processor to meet this requirement. Also, currently you can not use inferred entity instances to create a new row of data with the batch processor, so if this is a requirement you will need to work around this.
Please let me know what additional information you need.