Environment
In a product implementation and post-implementation there will be a number of copies of the product installed. Each copy of the product is known as an environment. Each environment will be created for a specific purpose, according to your site plans, and accessible to a group of users deemed necessary for that purpose. For example, there will be at least one testing environment where designated personnel will perform their testing tasks.
For planning purposes an environment is an instance of:
• The web applications deployed in an Oracle WebLogic domain. This may be in a single server or across a cluster of servers.
• The business applications deployed in an Oracle WebLogic domain. This can be the same physical Oracle WebLogic Server or another instance (such as a separate server). This may be in a single server or across a cluster of servers.
• A database containing the application’s schema. Physically, a schema can exist in an individual database instance or be shared within a database instance (that is, you can install multiple schemas of the product in the same database). This may be in a single server or across a cluster of servers.
While there is no restriction on the number of environments, it is recommended that the minimal number of copies of the product is installed using the guidelines outlined in the Environment Management document in the
Software Configuration Management Series (Doc Id:
560401.1) on
My Oracle Support.
Environment Identifier
An environment identifier is generated as part of the installation. This identifier is used by the technical utilities to manage the components and servers across the architecture. The environment identifier is used in the following ways:
• The Oracle Application Management Pack for Oracle Utilities uses the environment identifier to link child targets to a Utilities Environment target. This is used for monitoring and managing disparate targets (within a single host or across multiple hosts).
• It is used for tracking purposes only outside of the Oracle Application Management Pack for Oracle Utilities.
This feature is used in conjunction with the
Server Roles facility.
Server Roles
One of the features of the installation and configuration is the ability to design architecture roles to a single installation (a product home). This allows the product to support specific roles per installation or a combination of roles for a single installation for flexibility. There are three roles available:
Selection of each of the roles will enable or disable certain parameters that are available in the configureEnv.sh (see configureEnv – Set up Environment Settings) utility.
Note: Even though the role can be set for individual sets of functionality, all the code and facilities are installed and patched to support post installation role change.
Note: If the role is changed post installation, additional parameters may need to be provided.
Once the role is set, several additional configuration parameters are set in the ENVIRON.INI:
• SERVER_ROLE_BATCH (see SERVER_ROLE_BATCH - Whether the Batch Server Is Enabled in This Installation)
• SERVER_ROLE_INTEGRATION (see SERVER_ROLE_INTEGRATION - Whether the IWS Server Is Enabled in This Installation)
• SERVER_ROLE_ONLINE (see SERVER_ROLE_ONLINE - Whether the Online Server Is Enabled in This Installation)