Database Reference
In-Depth Information
Post-Installation Tasks
The installation of e-Business Suite Release 12.2 on ODA has been completed. The remaining tasks are not directly
related to deploying the system on ODA, but rather to the specific requirements you have for your system, and most
of them will be covered during the e-Business Suite implementation project you are running. This chapter mentions a
few important steps and references to additional documentation besides the technical configuration of the e-Business
Suite on ODA, without which the implementation would not be complete.
Additional Configuration
The list of additional configuration tasks you'll perform in your system depends on the requirements you have for
your environment. A typical list of areas to explore include:
•
Integration with other systems
: Includes identity management products (Oracle Access
Manager, Oracle Internet Directory), reporting tools (Oracle Discoverer, OBIEE), connected
systems using incoming and outgoing database links, custom-built in-house applications,
and others.
•
Configuration of the required business functionality
: e-Business Suite is a comprehensive suite
of integrated, global business applications. Depending on your plans, you will configure few or
many modules included in Oracle e-Business Suite. The R12.2 documentation library contains
at least 85 implementation guides for different areas of functionality. You'll definitely need to
review at least some of these and you probably will have to make some changes to the existing
environment.
•
Tuning of the configuration
: Your environment will likely require some tuning after the
initial implementation. This includes sizing the connection pools between application tier
servers and the database, tuning the memory parameters of the database and application tier
services, sizing the concurrent managers and implementing parallel concurrent processing
(PCP), adjusting the session timeouts, and others.
•
Recommended patches
: The e-Business Suite modules are constantly being developed as bugs
are fixed and new features are implemented. The Release 12.2 was made generally available
in September 2013 and it is not uncommon to see critical or recommended patches to be
released soon after a product is released. You should check the “Recommended Patches”
reports in My Oracle Support to identify any known bugs and be able to fix them before your
system is transferred into production use.
Backups and Monitoring
An important preparation step for going live with ODA is the implementation of a monitoring framework for timely
notification about issues. The best way to monitor the ODA hardware is by configuring the Auto Service Request (ASR)
support feature that is included in the ODA software bundle. ASR automatically creates Service Requests, provides
diagnostic information to Oracle Support, and notifies administrators about hardware faults.
ASR does not provide any monitoring for the database, the VMs, and the e-Business Suite application. You
need to implement tools to monitor the software components of the system. ODA supports installation of third-
party agents to manage, monitor, backup, replicate, authenticate, or otherwise act on the database, the server, or
the environment,
15
thus giving the opportunity to handle the ODA the same way as any other server in your IT
infrastructure.
15
My Oracle Support note “FAQ : ODA 2.3 New Features includes Multiple Homes & 3rd Party Agent Support
(Doc ID 1415773.1).”
