Environments Overview
Cloud Manager provisions PeopleSoft environments on-demand with just a few clicks. The entire provisioning process is automated. At the end of provisioning, a ready-to-use environment is available within a short time. The environments can be created by a three step process:
Create Topology
Create Template
Create Environment
Note: Prior to creating an environment, ensure that the required DPKs are already downloaded in the Repository.
An administrator defines a template for creating an environment. The topology is encapsulated inside the template. Users can select a template, override topologies, change any attributes, if needed and provision PeopleSoft environments on demand.
Users are allowed to perform actions on a running environment, such as stop, view details, create new template from it, and so on. For details, see the Actions on the Environment section under the Environments Page.
Note: Also, you must ensure to tune the servers, database, and PeopleSoft system for optimum performance once the deployment is completed.
Page Name |
Definition Name |
Usage |
---|---|---|
ECL_ENVPROV_FL_GBL (Content reference for the tile.) |
Access the Environments landing page. |
|
ECL_ENVPRO_FL |
Access the Environments landing page. |
|
Create Environment |
ECL_ENV_ADD_SCF |
Create a new environment. |
Environment Details |
ECL_ENV_DET_FL |
Access more details of the environment from one location. |
Manage Attributes |
ECL_ENV_ATTR_FL |
Centrally administer the configuration of all the managed instances using Cloud Manager. |
Manage Tags |
ECL_ENV_TAGS_FL |
Add, delete or update tags for each node in the environment. |
Manage Passwords |
ECL_ENV_RESET_FL |
Update Cloud Manager with environment attributes, if a user modifies it outside Cloud Manager. |
Manage PUM Connections |
ECL_SA_MANAGEPM_FL |
Manage PUM connections. |
Infrastructure CPU Patches |
ECL_ENV_INFRUPD_FL |
Display currently applied third party component details. |
Apply PeopleTools Patch |
ECL_ENV_PTCHUPD_FL |
Apply latest patches. |
Upgrade PeopleTools |
ECL_ENV_UPGD_FL |
Update PeopleTools version (major version changes). |
Provision Task Status |
ECL_PTS_PROV_TASK |
Use to check provisioning status and retry or resume. |
Policies |
ECL_POLICY_ENVS |
Associate policies with the environment name. |
Logs |
ECL_ESEARCH_FL |
View logs of all operations such as create, delete, actions performed on the environment, and the like. |
Monitoring |
ECL_ML_ALERTS_FL |
Enable or disable monitoring for the environment. |
Load Balancing |
ECL_LB_BACKENDS_FL |
Set up load balancing. |
Advisory Settings |
ECL_ENVRECM_SET_FL |
Configure or update advisory settings for the environment. |
Sparse Hierarchy Details |
ECL_EXA_SPARSE_FL |
Create test masters and manage their sparse clones. This page is available only for environments with databases running on Exadata. |
Use the Environments tile (ECL_ENVPROV_FL_GBL) to access the Environments landing page.
Navigation:
The Environments tile is delivered as part of the Cloud Manager home page.
This example illustrates the Environments tile.

Use the Environments page (ECL_ENVPRO_FL) to manage, create, and import provisioned environments. You can view the environments in card or grid (list) format. This documentation typically refers to the card format.
Navigation:
Click the Environment tile on the delivered Cloud Manager Fluid home page. The Environments page is displayed.
This example illustrates the fields and controls on the Environments page. You can find definitions for the fields and controls later on this page.

Field or Control |
Description |
---|---|
Name |
Name of the environment. Note: Length of Environment name and identity domain name should not exceed 20 characters in OCI. |
Status |
Status of the environment provisioned through Cloud Manager. The different statuses associated with the environment are:
|
Description |
Description of the environment. |
Zone |
Zone in which the environment is deployed. |
PIA URL |
Indicates the URL used to connect to the provisioned environment. |
Create Environment button |
Click this button to access the Create Environment page, where you can create new environments. |
Related Actions button |
Click this button to perform different actions for managing the environment as a whole. |
Import Environment button |
Click this button to import a database system environment. See Importing Environment |
Actions on the Environment
You can perform a variety of actions on the environment by using the Related Actions button corresponding to each environment. The actions can be:
Details: Select this option to view environment details and to perform additional actions on the environment such as performing a health check, applying a PeopleTools patch, viewing logs, and managing PUM connections.
Start: Select this option to start all the instances and then all the domains within them.
Stop: Select this option to stop all domains and shutdown all the instances. In case of database, only compute database instances are shutdown. You cannot stop the DB system if it is used as a database tier and has multiple PDBs.
Delete: Select this option to remove the environment.
Note: If DB system is used as a database tier and has multiple PDBs, only the PDB is deleted and the DB system is not terminated.
Manage Node: Select this option to scale an environment up or down, add nodes, remove nodes, restart, stop, start, and work with search clusters.
Clone Environment: Select this option to clone an existing environment.
Refresh: Select this option to refresh the database or the database, Application Home (PS_APP_HOME) and Custom Home (PS_CUST_HOME).
This option is only available for DBaaS environments. This option is disabled for environments that use DB system as database tier and have multiple PDBs.
Backup and Restore: Select this option to backup or restore an environment.
This option is disabled for environments that use DB system as database tier and have multiple PDBs.
Deploy: Select this option to continue deploying an environment that has paused after infrastructure creation.
Delegate Access: This functionality is no longer supported. See Role Based Security Page for the currently supported action.
Disaster Recovery: Select this option to set up an environment as a standby in case of failure.