Oracle Application Server 10 g (9.0.4) Recommended Topologies Pavana Jain

2. Oracle Application Server 10g (9.0.4)Recommended TopologiesPavana Jain

3. Agenda • Topology Considerations • Recommended Topologies • Q and A

4. Recommended Topologies • What is it? • Oracle Recommended Topologies • To address 80% use cases in the market • Why do we need it? • Too many deployment topologies • Test, document, support and recommend smaller set of topologies • What are the benefits? • Oracle • Enables better planning internally • Help guide customers on how best to deploy our product • Customers • Oracle recommended topology • Better performance

5. Recommended Topologies • General Development Configurations • Java Developer • Portal and Wireless Developer • Forms and Reports Developer • Integration Architect and Process Modeler • General Deployment Configurations • Enterprise Data Center Configuration • Departmental Configuration • Development Life Cycle Support Configuration (Test to Stage to Production rollout support)

6. Topology Considerations • Installation Considerations • How do I install Oracle Application Server 10G (9.0.4) to get to a specific topology? • Which distributed install model is best suited for this topology? • What types of machines are typically used in this topology? • What is the profile of the user who would do the installations in this topology?

7. Topology Considerations • Application Deployment and Performance Considerations • What type of performance goals are typical for this type of topology, and what heuristics can be used to estimate representative values for those goals. • What distribution of components across multiple hardware best meets those performance goals • How are applications and OracleAS components best distributed among multiple hardware nodes to meet the performance goals • What application development strategies will maximize the performance of a topology • What tunable parameters exist to improve performance, and how to determine when to alter these parameters

8. Topology Considerations • Security Considerations • What level of security does the topology require? • What isolation of components or applications is needed to increase the security of these topologies? • What 3rd party suppliers for security hardware and software requirements exist for these topologies?

9. Topology Considerations • Management Considerations • What facilities are required to manage this topology? • What distributions of components or applications across multiple hardware nodes provides for manageable topology? • What backup and recovery methods to use for these topologies? • What are the best management practices for these topologies?

10. Topology Considerations • HA Considerations • Which HA methodology is recommended for these topologies? • 3rd Party Products • What are the special 3rd party products such as gateways, adapters, and load balancer, firewall requirements in these topologies? • How do these 3rd party products impact the high availability, management, security and performance recommendations for these configurations? • Migration Objectives • How would earlier versions of Oracle9iAS need to be migrated to fit into this configuration?

11. General Development Configurations • Java Developer • Portal and Wireless Developer • Forms, Reports and Discoverer Developer • Integration Architect and Process Modeler

12. Java Developer

13. Java Developer • Consideration Highlights: • Installation and Configuration – • Quick adoption to new O/S • Installation for dummies needed • Quick uptake of IDE and container • Limited knowledge of db • Management – • GUI used sometimes. Mostly command line preferred. • File backup • Security – • Self contained environment. Might need container services.

14. Java Developer • Consideration Highlights: • HA – • File based clustering • Performance – • Good OC4J performance desired

15. Java Developer • Topology Recommendations: • Single box installations – • Jdeveloper and use of inbuilt OC4J for testing (<500M HD, 256M RAM) • OC4J standalone, Jdeveloper (< 800M HD, 516M RAM) • J2EE and Web Cache, Jdeveloper (2G HD, 516M RAM) • Consideration Recommendations: • Management – EM to startup, shutdown, OHS, OC4J management • Security – JAZN-XML, SSL • HA – File backup • Performance – OC4J tuning tips in Performance Guide

16. Portal and Wireless Developer

17. Portal and Wireless Developer • Consideration Highlights: • Installation and Configuration – • Quick adoption to new O/S, On/Off network support, DHCP • Quick uptake of Dev kits • Fair amount of knowledge of db • Management – • GUI used all the time. • Backup and Recovery • Security – • Single Sign on used to build apps.

18. Portal and Wireless Developer • Consideration Highlights: • HA – • Clustering desired • Performance – • Good performance desired

19. Portal and Wireless Developer • Topology Recommendations: • Single box installations – • OracleAS Devkits (2G HD, 516M RAM) • Infrastructure + Portal and Wireless (10G, 2G RAM) • Post installation steps to shared OHS, EM Services • Consideration Recommendations: • Management – EM to startup, shutdown, OHS, OC4J, Portal, SSO, OID, Wireless management • Security – SSO, OID, DIP, DAS • HA – Backup and Recovery tool • Performance – Portal performance tips in Portal docs

20. Forms, Reports and Discoverer Developer

21. Forms, Reports and Discoverer Developer • Consideration Highlights: • Installation and Configuration – • Good amount of knowledge of db • Management – • GUI used all the time. • Backup and Recovery • Security – • Single Sign on used to build apps.

22. Forms, Reports and Discoverer Developer • Consideration Highlights: • HA – • Clustering desired • Performance – • Good performance desired

23. Forms, Reports and Discoverer Developer • Topology Recommendations: • Single box installations – • OracleAS Devkits (2G HD, 516M RAM) • Infrastructure + BI and Forms (10G, 4G RAM) • Post installation steps to shared OHS, EM Services • Consideration Recommendations: • Management – EM to startup, shutdown, OHS, OC4J,Forms, Reports, Discoverer, SSO, OID, • Security – SSO, OID, DIP, DAS • HA – Backup and Recovery tool • Performance – OC4J tips

24. Integration Architect and Process Modeler

25. General Deployment Configurations • Enterprise Data Center Configuration • Departmental Configuration • Development Life Cycle Support Configuration (Test to Stage to Production rollout support)

26. Enterprise Data Center TopologyJ2EE Applications

27. Enterprise Data Center TopologyPortal and other Applications

28. Enterprise Data Center • Consideration Highlights: • Installation and Configuration – • Ability to install OracleAS in tiered environment • Management – • GUI used all the time • Backup and Recovery • Cluster management • System provisioning • Cloning, Change Host name, Change IP address • Patching

29. Enterprise Data Center • Consideration Highlights: • Security – • Single Signon and integration with windows native authentication and other 3rd party products • Central user provisioning system with the ability to handle outside as well as inside organization authentication and authorization capabilities • HA – • Clustering needed • Active Clusters needed • Disaster Recovery needed • Performance – • Caching capabilities needed • Application performance monitoring

30. Enterprise Data Center • Topology Recommendations: • Tiered installations (testing ongoing)– • Web Tier: OHS, Web Cache (2G, 2G RAM), Identity Management (10G, 4G RAM) • J2EE Tier: OC4J (2G, 2G RAM) • Business Tier: Customer database (10G, 4G RAM) • Consideration Recommendations: • Management – Central Console, Standalone Console, lot of scripts for batch processing • Security – SSO, OID, DIP, DAS, fanout, AD connector, Netgrity integration • HA –Web Cache cluster, OracleAS Cluster, Cold Failover Cluster or Replication (local protection), Disaster Recovery (remote protection) • Performance – Sizing tips to be made available

31. Departmental Configurations

32. Departmental Topology • Consideration Highlights: • Installation and Configuration – • Ability to install OracleAS on multiple machines as different users • Management – • GUI used all the time • Backup and Recovery • Cluster management • System provisioning • Change Host name, Change IP address • Patching

33. Departmental Topology • Consideration Highlights: • Security – • Single Signon • Central user provisioning system for the department • HA – • Clustering needed • Active Clusters needed • Performance – • Caching capabilities needed • Application performance monitoring

34. Departmental Topology • Topology Recommendations: • Tiered installations (testing ongoing)– • Middle Tier (depends on the middle tier) • Infrastructure (10G, 4G RAM) • Consideration Recommendations: • Management – Standalone Console, Central Console • Security – SSO, OID, DIP, DAS • HA –Web Cache cluster, OracleAS Cluster, Cold Failover Cluster • Performance – Sizing tips to be made available

35. Development Life Cycle Support Configurations

36. Development Life Cycle Support Configurations Tests ongoing. Recommendations not yet defined for how applications get moved from Test to Stage to Production Environment. . The instances do not move.. Just applications moves . Test environment recommendation would be similar to Developer topologies . Staging environment recommendation would be similar to Departmental topology . Production environment recommendation would be similar to Enterprise Data Center topology

37. Recommended Topology Project • Where are we with this project as of 8/7/2003: • Testing for deployment topologies are ongoing. Results with recommendation will be documented in official documentation before production. • Sizing tools are planned and we hope to have it delivered close to production. • The following sales tools are planned: • Cheat sheet with consideration decisions to help decide which topology a customer would get most benefit from . • Comparison study on how we compare with BEA/IBM wrt these topologies. • Document of the type of licenses recommended to deploy these topologies