Managing an Enterprise Deployment Topology 5-1
5
Managing an Enterprise Deployment
Topology
This chapter provides information on managing an enterprise deployment:
■ General Management Considerations
■ Enterprise Data Center Topology: Multiple Departments Sharing the Same Data
Center
■ Departmental Topology: Departments Hosting Their Applications
■ Development Life Cycle Topology
5.1 General Management Considerations
Regardless of the type of topology you are managing, here are some general
considerations:
■ Rotating Log Files
■ Periodic Restarting of OC4J
■ Starting and Stopping Servers and Applications
■ Rolling Out Upgrades, Patches, and Configuration Changes
■ Backup and Recovery
■ Taking Advantage of NFS
■ Port Management
■ Using Static and Dynamic IP Addresses
■ Mining Log Files
■ Leaving and Joining Different Infrastructures
5.1.1 Rotating Log Files
Many services and components generate their own log files that need to be maintained
regularly. This need for maintenance varies on the size and scale of an enterprise
topology.
Log files in Oracle Application Server have a maximum limit of 2 gigabytes before
application server performance becomes adversely affected. You need to make sure
that log files are archived and reset before they near the 2 gigabyte limit. This task may
have to be performed daily or several times per week.
Comments to this Manuals