1 / 21

Revelations of a 9iAS Implementation

Session id: 36645. Revelations of a 9iAS Implementation. Michael A. Kirchenbauer P.Eng. Infrastructure Architect Sierra Systems Consultants Inc. Agenda. Overview Project goals and infrastructure goals Infrastructure Implementation Key decisions and implications. Elements and challenges

olympe
Download Presentation

Revelations of a 9iAS Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Session id: 36645 Revelations of a 9iAS Implementation Michael A. Kirchenbauer P.Eng.Infrastructure Architect Sierra Systems Consultants Inc.

  2. Agenda • Overview • Project goals and infrastructure goals • Infrastructure Implementation • Key decisions and implications. • Elements and challenges • SSO/OID • OHS/OC4J • EM • Webcache • Portal • Network • Performance • Testing • Lessons Learned and Recommendations • Q&A

  3. “Everything should be made as simple as possible, but not simpler.” - Albert Einstein

  4. Overview – The Project • Self service pension admin portal • Full pension plan based personalization • Based on customized pension package implemented in client/server configuration • Self maintenance capability (security, content) • Secure

  5. Overview – Project Goals • Project History • February 2002 to December 2002 • SUN H/W and ORACLE database shop • Initial elements included iFS and InterConnect • Integration with client/server package • Started in 9iAS v9.0.1 • 180 000 plus potential users across 9 groups • All functionality based in legacy system

  6. Overview Infrastructure Goals • Infrastructure goals • Secure data traffic externally (sensitive financial content) • Manageability (client maintainable) • Reasonably fault tolerant • Minimize cost • Scalable • Performant

  7. Infrastructure • Assumptions • Scale out less expensive than scale up • Architecture supports full suite of availability options and features • Constraining factors • Budget limited (fixed price project) • Sun hardware standard • Shared production environment (legacy) • SSL required (all external traffic)

  8. Infrastructure

  9. InfrastructureSSO/OID • Separate infrastructure machine • One DIT (Portal) • Extensions to OID schema tended to be problematic in DAS • Infrastructure server not clusterable or redundant

  10. InfrastructureOHS/OC4J • Single valued attributes (redirect, logging) • Portal clustering issues • DMS entries onerous - Log management and analysis

  11. InfrastructureEnterprise Manager • Performance issue • Apache directives limitation • Xvfb

  12. InfrastructureWebcache • Clustering easy to configure • Timeout coordination with OHS • Logging detail is limited • Portal control over caching • Issue with content invalidation

  13. InfrastructurePortal • Clustering limitation • Remote portal DB requires effort • Installation configuration differs from runtime configuration

  14. InfrastructureNetwork • Firewall issues (admin port quantity) • Capacity • LBR configuration coordination with Webcache • Hybrid SSL configuration

  15. InfrastructureApplication Performance • Configuration (connection pooling and life cycle of connections) • Database performance and configuration • Network impact (SSL overhead)

  16. Other ElementsTesting • Test tools essential • You need to deal with security (or not) • Products • IBM Rational TeamTest • Mercury Interactive LoadRunner • Open Source (JMeter,Ant,Ethereal)

  17. Some Lessons Learned • Adding servers to the pool is not trivial • Scalability cannot be based on 9iAS architecture alone • OID configuration constrained by Portal requirements and DAS • OHS limitations to standard Apache by EM • Hybrid SSL config not trivial • SSL Accelerator a MUST • Application performance related to pooling • Learn XML

  18. Recommendations • ptlasst – get friendly with it • Scale up rather than out • Prevent redirection to infrastructure • Extend base class attributes in OID rather than creation of new classes • Manage OHS logging (rotatelogs/cronolog) • Limit number of DADS and OHS processes to minimize database sessions and maximize the benefits of pooling

  19. Recommendations • If SSL is required beyond authentication, use an SSL accelerator. • If possible, wait for 9.0.4!

  20. Q & Q U E S T I O N S A N S W E R S A Additional Questions:MichaelKirchenbauer@SierraSystems.com

  21. Reminder – please complete the OracleWorld online session surveyThank you.

More Related