Technical data

Departmental Topology: Departments Hosting Their Applications
Installation and Configuration Considerations for an Enterprise Topology 2-5
2.3 Departmental Topology: Departments Hosting Their Applications
Table 2–3 describes the considerations for installing and managing a departmental
topology:
Distributed Install
Topology
Web Server Tier: OHS in DMZ – 1, separate from application
server.
Application Server Tier: Application Server in DMZ – 2
Product Metadata Services: In DMZ – 2 for most cases.
Dedicated host running just Product Metadata Services used
by either dedicated or a small set of middle tier instances
Security Services: Behind the firewall. Dedicated host running
just Security Services. Shared by all middle tier instances
Management Services: Central management inside the firewall
User Profile System Administrator (Advanced User)
Table 2–3 Considerations for the Departmental Topology
Consideration User Considerations
Installation and
Management
Multiple Host installations on cluster machines, NFS machines
Multiple Middle Tier instances used
No Infrastructure used if deploying only Java or J2EE
applications
Dedicated Product Metadata Services for Portal applications
Shared Product Metadata Services for some applications
Shared Security Services to secure subset of enterprise level
users
Management Services -> Number of instances managed is less
than enterprise data center. All other management issues are
the same
Oracle Application Server should not break if there are hard
disk replacement, or CPU change or RAM upgrades or
Network Interfaces
Security Single install which would contain both Infrastructure
Software and OID/SSO data
Contains subset of users as compared to the enterprise OID
Application Deployment
and Performance
Important not to pay overhead for enterprise configuration
services
Use OHS as load balancer for multiple OC4J instances.
J2EE applications deployed on Oracle Application Server
Clusters with or without Web Cache
Portal application using Web Cache
High Availability (HA) HA requirement for departmental deployment depends on the
nature of the application
If there is a requirement, recommendation would be Local Data
Guard or Cold Failover ClusterIf there is no requirement,
complete cold backup and recovery methodology is used
Table 2–2 (Cont.) Considerations when installing and configuring Portal, BI, Wireless,
and Forms and Reports
Consideration User Consideration