Test 1
(A) EDS Batch Load Profile
- Total employee records processed: 51905190 (estimated to be an acceptable high-end employee record change due to student employee changes).
- Employee records identified before EDS Batch run (& time range to specify in request) via WorkDataChange web service component - invoke invoked either by soapUI or SOA console.
...
- SOA Console initiates EDS Batch (simulates Tidal invoke) - "Project “Project Explorer, Employee, PeopleSoft, Proxy, InvokeBatchSync"InvokeBatchSync”
- Oracle SOA
- Workday
- Oracle SOA
- PeopleSoft
- PS_CU_EMPSYNCSTG_J
- PS_CU_EMPSYNCSTG_P
- PS_CU_GRAD_PAY_STG
...
- There were initially 5 running BPEL processes for first 5-15 mins of the test, then only 2 running for the remaining of the test run. This did not affect the overall processing time as compared to the last run; though we expected to see 5 running processes.
- This run was performed on the new threading model, with previous run executed on the old threading model.
- This test involved PeopleSoft psutst DB for the 1st time.
- These results were similar to Craig Reicke's original baseline results.