Test 1  


(A) EDS Batch  Load Profile  

- Total employee records processed: 5190  (estimated to be an acceptable high-end employee record change due to student employee changes).
- Employee records identified (& time range to specify in request) via WorkDataChange web service component - invoked either by soapUI or SOA console.


(B) End-to-End Test

  1. SOA Console initiates EDS Batch (simulates Tidal invoke) - “Project Explorer, Employee, PeopleSoft, Proxy, InvokeBatchSync”
  2. Oracle SOA
  3. Workday
  4. Oracle SOA
  5. PeopleSoft
    - PS_CU_EMPSYNCSTG_J
    - PS_CU_EMPSYNCSTG_P
    - PS_CU_GRAD_PAY_STG



(C) Comparison Criteria Results

Criteria

Sub Detail

Value

Comments

Total processing time:

 

1 hr & 10 mins

 


(D) Comments:

- 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.




  • No labels