PeopleSoft Integration broker Performance Tunning

14,250 views

Published on

PeopleSoft Integration Broker Performance Tunning.
Author: Victor Li
Principle Support Engineer of Oracle

Published in: Technology
1 Comment
6 Likes
Statistics
Notes
  • http://www.dbmanagement.info/Tutorials/Peoplesoft.htm
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
14,250
On SlideShare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
556
Comments
1
Likes
6
Embeds 0
No embeds

No notes for slide

PeopleSoft Integration broker Performance Tunning

  1. 1.
  2. 2. Safe Harbor Statement<br />The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.<br />
  3. 3. PeopleTools Integration Broker Performance Tuning<br />Victor Li<br />Principle Support Engineer, PeopleTools support, Oracle GSS<br />
  4. 4. Agenda<br />OverviewPeopleSoft integration broker Architecture<br />Performance tuning for asynchronous messaging<br />Performance tuning for synchronous messaging<br />
  5. 5. Some issues to think<br />Production system running fine for years and Integration Broker usage is low. Suddenly Application Server box’s CPU reaches 90%. Further troubleshooting reveals PSSUBDSP service causes it.<br />We only use PSRF* messages, ie. Reporting tools messages before. This week, we have started to implement dynamic role sync messages. Now messages stuck in working status.<br />We have a third party web interface sending sync messages to PeopleSoft web services. We have load balanced integration gateway. Web Server box and App server box are powerful. No queues in Tuxedo monitor. How can we improve the benchmark performance of message response time?<br />
  6. 6. Architecture<br />“PeopleSoft 9.1 combines all the latest features customers expect in a web-based application with the tools needed to extend it into the future.”<br />Larry Acushnet Company<br />
  7. 7. Architecture<br />Integration Engine<br />Application<br />PeopleSoft Application<br />RDBMS<br />Server<br />Outbound Operation<br />Integration Gateway<br />Third Party<br />Web Server<br />System<br />Application<br />PeopleSoft Application<br />RDBMS<br />Server<br />Inbound Operation<br />
  8. 8. ArchitectureIntegration Broker - detailed<br />
  9. 9. ArchitectureAsynchronous Operation <br />
  10. 10. ArchitectureSynchronous Operation <br />Local to local transaction<br />
  11. 11. Asynchronous & Synchronous Service Operation<br />“PeopleSoft 9.1 combines all the latest features customers expect in a web-based application with the tools needed to extend it into the future.”<br />Larry Acushnet Company<br />
  12. 12. Message segments<br />Large amounts of data(gigabytes)<br />Divide rowset-based and nonrowset-based messages into segments<br />
  13. 13. Message segments<br />Configuration and coding efforts are small and straightforward.<br />
  14. 14. Thread Pool Size--Asynchronous<br />The number of concurrent threads the handler can spawn for HTTP requests<br />Only for PSPUBHND handler<br />[PSPUBHND_dflt]<br />;===============================================<br />; Settings for publication contract handler<br />;===============================================Max Instances=1<br />Service Timeout=1200<br />Recycle Count=20000<br />Allowed Consec Service Failures=0<br />; Thread Pool Size. The Minumum value is 1 and maximum allowable is 20.<br />Thread Pool Size=1<br />
  15. 15. Thread Pool Size--Synchronous<br />The number of concurrent threads the handler can spawn for HTTP requests<br />Default is 5.<br />
  16. 16. Integration Gateway-Load Balancing<br />Load Balancer in front of Gateways.<br />JVM--MinimumHeapSize and MaximumHeapSize to the same value, eg. 512MB.<br />
  17. 17. Asynchronous Service Operation<br />“PeopleSoft 9.1 combines all the latest features customers expect in a web-based application with the tools needed to extend it into the future.”<br />Larry Acushnet Company<br />
  18. 18. Dedicated messaging server<br />Dedicated server for high message volume <br />Dedicated server domains should have PSAPPSRV configured in addition to pub/ sub servers. <br />Dedicated messaging servers are assigned a certain number of queue names <br />
  19. 19. Multiple domains<br />PUB/SUB domain separates from PIA domain<br />Scan Interval parameter to a value of 1 for each dispatcher in pub/sub server.<br />Only one active pub/sub domain is supported.<br />
  20. 20. Domain Failover<br />Configure Failover<br />Dynamic Slave Option<br />
  21. 21. Master/Slave Load Balance<br />Compensate for processing capabilities of various machines.<br />Two hyperlinks Master/Slave Load Balance and Slave Template Setup.<br />
  22. 22. Master/Slave Load Balance<br />Assign weighting based on the capability of the machine<br />
  23. 23. Master/Slave Load Balance--Deferred Master Domain Processing<br />“Enabled” –Default. Master will process its appropriate share of requests<br />“Deferred – All Queues” --One active slave<br />“Deferred – Unordered Queues” -Unordered queue +one active slave <br />
  24. 24. Slave template<br />
  25. 25. Slave template<br />
  26. 26. Multi-queue<br />Unordered queues assigned to same service operation<br />Use with master/ slave domains, dedicated messaging server.<br />
  27. 27. Multi-queue<br />
  28. 28. Application Engine Handler<br />Problem: <br />A long running message takes up all handler resources<br />Solution:<br />Offer a Service Operation Handler that is a direct initiation of an AppEngine program<br />Offload the intense processing of the message to the Process Scheduler<br />Guarantee ordering of message<br />Message must be asynchronous<br />
  29. 29. Bulk Load Handler<br />Principle of Data Mover script as notification handler<br />Asynchronous messages only<br />Great for loading data to staging table<br />
  30. 30. Guidelines<br />Partition queue <br />Notification PeopleCode <br />Component Interfaces<br />Message Compression<br />
  31. 31. Basic performance tips---server instance<br />How many messaging server: <br />At least 3 in production<br />[PSSUBHND_dflt]<br />;==============================================<br />; Settings for subscription contract handler<br />;==============================================<br />Min Instances=3<br />Max Instances=3<br />
  32. 32. Basic performance tips---messaging tables<br />For asynch messages, they are stored in PSAPMSGPUBHDR, PSAPMSGPUBCON, PSAPMGSSUBCON and etc.<br />Archive them regularly<br />
  33. 33. Batch processing or full sync EIP<br />Database Tuning--Temp table indexing<br />Archiving—N in queue definition.<br />Database Layout –tablespaces<br />Chunk messages -Around 3 MB a message.<br />Message segment<br />
  34. 34. Synchronous Service Operation<br />“PeopleSoft 9.1 combines all the latest features customers expect in a web-based application with the tools needed to extend it into the future.”<br />Larry Acushnet Company<br />
  35. 35. Multi-Threading Synchronous Requests<br />(Array of Response Messages = %IntBroker.SyncRequest(Array of Request Messages))<br />
  36. 36. Tunning Application Server<br />Provider of Synchronous Service Operations—Dedicated Application server domain<br />Jolt Handlers<br />[JOLT Listener]<br />;=========================================================================<br />; Settings for JOLT Listener<br />;=========================================================================<br />Address=%PS_MACH%<br />Port=9000<br />Encryption=0<br />Min Handlers=60<br />Max Handlers=80<br />Max Clients per Handler=20<br />
  37. 37. Basic performance tips---server instance<br />How many psappsrv instances : <br />At least 3 in production<br />[PSAPPSRV]<br />;==============================<br />; Settings for PSAPPSRV<br />;================================<br />;-------------------------------------------------------------------------<br />; UBBGEN settings<br />Min Instances=3<br />Max Instances=3<br />
  38. 38. Guideline<br />Response Time---Light transform, light onrequestpeoplecodeand light CI.<br />Number of Synchronous Requests—Minimum.<br />Small Messages—compression.<br />Exception<br />
  39. 39. Tools to determine and Reduce bottlenecks<br />“PeopleSoft 9.1 combines all the latest features customers expect in a web-based application with the tools needed to extend it into the future.”<br />Larry Acushnet Company<br />
  40. 40. Application Server layer<br />Tuxedo Commands<br />Pq--shows the current Tuxedo queuing on the domain.<br />Psr--current service request for each server on the domain and also the load (number of requests) that the server processed.<br />Tuxedo Settings<br />Message Segment Size---Increase size from the default 24 to 8K or 16K<br />Message Queue Size---Increase from 64K to 1M or 2M<br />Max Message Size---Increase from 64K to 1M or 2M<br />
  41. 41. Profile and Statistics<br />
  42. 42. Some issues to think<br />Production system running fine for years and Integration Broker usage is low. Suddenly Application Server box’s CPU reaches 90%. Further troubleshooting reveals PSSUBDSP service causes it.<br />We only use PSRF* messages, ie. Reporting tools messages before. This week, we have started to implement dynamic role sync messages. Now messages stuck in working status.<br />We have a third party web interface sending sync messages to PeopleSoft web services. We have load balanced integration gateway. Web Server box and App server box are powerful. No queues in Tuxedo monitor. How can we improve the benchmark performance of message response time?<br />
  43. 43. Q & A<br />
  44. 44. THANK YOU<br />

×