Managing Template

An environment template is a repeatable blueprint that is used to deploy PeopleSoft environments using Cloud Manager. A template defines the topology to be used when deploying the PeopleSoft application DPK, which gets downloaded to the Repository. A template also defines environment attributes to enable streamlined deployments. Access to templates can be managed by defining security attributes of the templates.

Page Name

Definition Name

Usage

Environment Template Tile

ECL_TEMPLATE_LP_FL_GBL

(This is the CREF for the tile.)

Access the Environment Template landing page.

Environment Template Page

ECL_TEMPLATE_FL

Create new templates or edit, delete or clone existing templates.

Environment Template – General Details Page

ECL_TEMPL_GEN_FL

Enter the template name, description, and selecting a database.

Environment Template – Select Topology Page for OCI

ECL_TEMPL_TOP_FL

Select the topology that you have already defined.

Environment Template – Define Security Page

ECL_TEMPL_SEC_FL

Associate zones in which the environment is created and the roles that have access to the template.

Environment Template – Summary Page

ECL_TEMPL_REV_FL

Displays the summary of the environment template that the user is about to create.

Use the Environment Template tile (ECL_TEMPLATE_LP_FL_GBL) to access Environment Template landing page.

Image: Environment Template Tile

This example illustrates the Environment Template Tile.

Environment Template Tile

Use the Environment Template page (ECL_TEMPLATE_FL) to create a new template, and edit, delete or clone an existing template.

Image: Environment Template page

This example illustrates the fields and controls on the Environment Template page. You can find definitions for the fields and controls later on this page.

Environment Template page

Note: The Lift And Shift template is the default template displayed in the Environment Template page with no database associated with it.

Field or Control

Definition

Template Name

Name of the template.

Database

Indicates the PeopleSoft application DPK that gets installed when the template is deployed.

Default Topology

Default topology associated with the template.

Description

Add a description for the template.

Edit/Delete/Clone an Existing Template

User can edit, delete or clone the existing templates using the Environment Template landing page.

Note: It is recommended to recreate the existing templates to ensure that the new custom attributes are available in the template.

  • To edit an existing template details, click a row and modify the details as per requirement.

  • To delete an existing template, select the radio button corresponding to the template which you want to delete and click the Delete button. Users cannot delete a template, if it is already used for defining an environment.

  • To clone an existing template, select the radio button corresponding to the template which you want to clone and click the Clone button available on the Environment Template landing page. The Clone Template modal window is displayed, wherein you can enter the new template name and click the Clone button. The new template is added to the template list.

Default Environment Templates

A default template is provided for Lift and Shift, which is used during environment shifting by default. This Lift and Shift template and its associated topology must be modified such that it is suitable for the environment being shifted. The Lift and shift topology is fixed in terms of number of nodes, but the shape and disk space parameters can be modified. For any environment to be provisioned in Cloud Manager, the administrator creates a template and a user uses that template to provision. In case of Lift and Shift, a default template is provided out of the box and there is no need to create any templates. When an administrator creates an environment on the Lift and Shift page, the process automatically chooses the default Lift and Shift template. This Lift and Shift template must be modified to suit the environment being shifted. For more details, see Understanding the Lift and Shift Process.

Creating a Template

Use the Environment Template wizard to create a new template using a step by step guided process.

By default, the create template guided process involves the following steps:

  1. Entering general details.

    See Environment Template – General Details Page

  2. Selecting topologies.

    See Environment Template – Select Topology Page for OCI

  3. Defining security.

    See Environment Template – Define Security Page

  4. Submitting the details.

    See Environment Template – Summary Page

Use the Environment Template – General Details page to enter the template name, description, and select a database.

Image: Environment Template – General Details page

This example illustrates the fields and controls on the Environment Template – General Details page. You can find definitions for the fields and controls later on this page.

Environment Template - General Details page

Field or Control

Definition

Name

Name of the template which you want to create.

Description

Add a description for the template.

PeopleSoft Image

Select a PeopleSoft application DPK from the list of DPKs available in the Repository.

Use the Environment Template – Select Topology page to select the topology that you have already defined. You may edit the default attributes associated with the selected topology.

Image: Select Topology page

This example illustrates the fields and controls on the Select Topology page. You can find definitions for the fields and controls later on this page.

Select Topology page

Field or Control

Definition

Default Topology

Users can mark one of the topology associated with the template as the default topology. During the environment creation process using a template, you can override this default topology and select any other topology associated with that template. If you don’t want to override, then the default topology will get used automatically.

Click + to add more topologies. A new row of empty fields appears below the existing record. You can configure the fields based on the requirements.

Note: Be sure to select the topology under the Override Topology section and then continue with the template creation.

Topology Name

Select the required topology that you want to include in the template.

Note: While selecting a topology, the custom attributes associated with the selected topology is displayed. It is possible to override the default attributes based on the requirements.

  1. Expand the Custom Attributes section.

  2. Select the required topology.

  3. Enter the required attributes and click Next.

    Note: Cloud Manager allows users to add customization during template creation under Edit Custom Attributes section. This customization can be added only to middle tier and database tier. The customization will be available to users when they select this template. This facilitates the user to define custom attribute values for the environment being deployed.

  4. After entering the required attributes, click the Validate Network button to ensure your infrastructure settings are correct and the network is valid.

    This validates whether the port is open for an incoming/outgoing connection across different subnets and VCN. The connection can be:

    1. From Cloud Manager to VM

    2. From VM to Cloud Manager

    3. From VM to VM

    Some of the validations are based on user input (Jolt Port, WSL Port, Database Server Port, HTTP PIA Port, HTTPS PIA Port).

    The following implicit validations are performed:

    From

    To

    Every subnet

    Cloud Manager subnet: NFS ports TCP - 2049, 111, 892, 32803

    Cloud Manager subnet

    Every subnet (including itself) except Windows VM subnet: ssh port 22

    Cloud Manager subnet

    Windows VM’s subnet : WinRM TCP Ports 5985, 5986

    Cloud Manager subnet

    Windows VM’s subnet: CIFS ports TCP 445, 139, 138, 137

The following sections must be configured in every template.

The General Setting and Domain Settings depend on the type of node.

Image: Region and Availability Domains section

This example illustrates the fields and controls on the Region and Availability Domains section. You can find definitions for the fields and controls later on this page.

Region and Availability Domains section

Field or Control

Definition

Region

A region is a localized geographic area, and an availability domain is one or more data centers located within a region. A region is composed of several availability domains.

Note: Cloud Manager will provision and manage environments only in the region where it is deployed. See Infrastructure Settings Page.

Primary Availability Domain

Availability domain in OCI.

Compartment

Compartments allow you to organize and control access to your cloud resources. A compartment is a collection of related resources (such as instances, virtual cloud networks, block volumes) that can be accessed only by certain groups that have been given permission by an administrator.

Note: You must use a compartment that is directly under the root compartment. Nested compartments, that is, lower-level subcompartments, are not supported for Cloud Manager, or for environments that you provision with Cloud Manager.

Virtual Cloud Network

Virtual Cloud Network within OCI. A virtual cloud network is a virtual version of a traditional network—including subnets, route tables, and gateways—on which your instances run.

For details on setting up the OCI environment, refer to the OBE Installing PeopleSoft Cloud Manager in Oracle Cloud Infrastructure.

Note: In OCI, the templates will not have any default values for Region and Availability Domains section. All templates must be updated with these settings before using it for deployment using the Create Environment Page.

Each node in the template must be configured for the subnet where it will run.

Image: Subnet Settings section

This example illustrates the fields and controls on the Subnet Settings section.

Subnet Settings

Each availability domain in OCI contains three fault domains for high availability. OCI randomizes the availability domains by tenancy to help balance capacity in data centers.

Use the Fault Domain Settings section to select which fault domain to use for a specific node. Select the fault domain from the drop down list, only fault domains in the availability domain for the node are listed and available.

If OCI Default is selected , OCI randomly selects the fault domain to use and customer is not aware of which fault domain is being used.

Note: DB Systems node does not have fault domain settings.

For more information on faults domains see Regions and Availability Domains.

Image: Fault Domain section

This example illustrates the fields and controls on the Fault Domain section.

Fault Domain section

The Advanced section contains kernel parameters and Ulimit values. Expert administrators have the option to change these values.

Important! No validation is performed on these fields. Only Operating system experts should change these values.

Note: Add Node operation and ELK nodes do no include an Advanced section.

Image: Advanced section

This example illustrates the fields and controls on the Advanced section.

Advanced section

Ulimits

This input field allows you to set ulimit values for the Linux node.  Each line of the input represents one ulimit entry. The format to be used for each line is as follows:

[user|group].[soft|hard].<limit name> = <value>

The left-hand side of the expression represents a ulimit, and the right hand expression is a value of that ulimit. They are separated by a = sign.

Field or Control

Definition

user or group

The key word “user” represents a limit for a  Linux user, and the key word “group” represents a limit for a user group. Exactly which users and groups are added to the Linux configuration files is internally determined by the environment deployment process. You cannot set those actual user/group names here.

soft or hard

The keyword “soft” denotes the limit a process can use. It can later be increased by the corresponding user/group.

The keyword “hard” denotes the maximum limit to which the soft limit can be raised to.

limit name

This is the name of the limit. Please refer to table below for the list of names

value

This is either a numeric value or the string “unlimited”. Please refer to table below for a list of values and the units in which they have to be expressed

This table lists the ulimit names.

Name

unit

cpu

Seconds

fsize

Blocks

data

Kilobytes

stack

Kilobytes

core

Blocks

rss

Kilobytes

nofile

Number of file descriptors

as

Kilobytes

nproc

Number of processes

memlock

Kilobytes

lock

Number of locks

sigpending

Number of queued signals

nice

Nice level (an integer)

rtprio

Realtime priority (an integer)

rttime

Number

Kernel Parameters

The kernel parameters input field can be used for setting Linux kernel parameters. Each line represents one Linux parameter. The format of each line should be as follows:

<kernel parameter name> = <value>

The list of all kernel parameters can be found from the main page of the Linux sysctl command.

Example Full Tier Node with ELK Stack and COBOL

Based on the topology selected, the full tier contains the appropriate settings for the node. The examples in this section display full tier topology that includes ELK Stack and COBOL.

Image: Full Tier - General Settings (1 of 2)

This example illustrates the fields and controls on the Full Tier - General Settings (1 of 2). You can find definitions for the fields and controls later on this page.

Full Tier - General Settings (1 of 2)

Image: Full Tier - General Settings (2 of 2)

This example illustrates the fields and controls on the Full Tier - General Settings (2 of 2). You can find definitions for the fields and controls later on this page.

Full Tier - General Settings (2 of 2)

Field or Control

Definition

Elasticsearch Port

Elasticsearch port.

Weblogic Administrator Username

User name of the Weblogic administrator. This is used for accessing WebLogic console.

PeopleSoft Deployment Path

Location where the PeopleSoft application is deployed.

Database Access ID

Access Id for the database.

Database Connect ID

Connect Id for the database.

Enable EM Agent

Select either Yes or No to enable or disable EM agent.

Elasticsearch Port

Elasticsearch port.

Database Type

Select the required database type. Available database types are DEMO or SYS.

Enable Multi Language

Select either Yes or No to enable multi language support.

Database Name

Name of the database.

Gateway Administrator Username

User Id of gateway administrator.

Database Operator ID

Database Operator ID.

Database Server Port

Listener port number.

COBOL Compiler Type

If COBOL is enabled in the selected topology, you must select the Cobol compiler type, Server Express or Visual COBOL.

Note: Server Express is not supported for PeopleTools 8.58 and onward.

Note: The COBOL license must be configured on the Cloud Manager Settings page. See Cloud Manager Settings Page

ELK Discovery Host Name

Host names for any nodes that are already members of a cluster. Host names (or IP/DNS) are required for letting each Elasticsearch server know where it can ping and find other Elasticsearch servers during booting up.

ELK Installation Directory

ELK Installation Directory

Pre Provision Custom Script

Select an uploaded script to execute prior to provisioning the environment.

See Upload Custom Scripts Page

Post Provision Custom Script

Select an uploaded script to run post provisioning.

See Upload Custom Scripts Page

Kibana Port

Kibana port.

ELK Cluster Name

ELK cluster name.

Domain Settings Section

Full tier includes Web Server, Appserver and Process Scheduler.

Field or Control

Definition

Web Server Settings

For Web Server setting see Configuring Web Server Tier Settings.

Appserver Setting

For App Server Setting see Configuring AppServer Tier Domain Settings.

Process Scheduler Settings

For Process Scheduler Setting see Configuring Process Scheduler Domain Settings.

Process Scheduler Server Definition Parameters

For Process Scheduler Setting see Configuring Process Scheduler General Setting.

DB Systems settings includes:

  • General settings

  • Subnet settings

  • DB System options

    The DB System options differ depending on whether the database system is on a VM, bare metal, or Exadata.

DB Systems General Settings

Image: DB Systems – General Settings

This example illustrates the fields and controls on the DB Systems – General Settings. You can find definitions for the fields and controls later on this page.

DB Systems - General Settings

Field or Control

Definition

Database Server Port

Listener port number.

Character Set

The character set for the database.

Database Connect ID

Access ID for the database.

Enable EM Agent

Select Yes to enable enterprise manager agent for creating the infrastructure that is required to deploy an EM agent.

National Character Set

The national character set for the database.

Database Operator ID

Default database operator ID.

Database AccessID

Access ID for the database.

Database Type

Select the required database type. Available database types are DEMO or SYS.

Enable Multi Language

Select either Yes or No to enable multi language support.

Database Name

Name of the database.

PDB Name

Name of the Pluggable Database.

Pre Provision Custom Script

Select an uploaded script to execute prior to provisioning the environment.

See Upload Custom Scripts Page

Post Provision Custom Script

Select an uploaded script to run post provisioning.

See Upload Custom Scripts Page

Image: DB Systems Section for VM

This example illustrates the fields and controls on the DB Systems section when the database system is on a virtual machine. You can find definitions for the fields and controls later on this page.

DB Systems Section for VM

Field or Control

Definition

Subnet for Primary Settings

A subnet is a subdivision of Oracle Cloud network. Subnets can be either public or private. You choose this during subnet creation, and you can't change it later. For details, refer OBE Installation Guide for Cloud Manager.

Software Release

Oracle database release version. Select the software release from the drop down list.

Staring in Image 10, the following software releases are supported in DBS.

  • 12.1

  • 12.2

  • 18c

  • 19c

The database release version must be chosen based on the database version in PeopleSoft Image or customer's lifted database version.

Display Name

Display name for the DB system. The name doesn't need to be unique. An Oracle Cloud Identifier (OCID) will uniquely identify the DB system.

Auto Backup

Displays whether automatic incremental backups for this database is enabled or disabled.

License Type

The type of license you want to use for the DB system. Your choice affects metering for billing. License included means the cost of the cloud service includes a license for the Database service. Bring Your Own License (BYOL) means you are an Oracle Database customer with an Unlimited License Agreement or Non-Unlimited License Agreement and want to use your license with Oracle Cloud Infrastructure. This removes the need for separate on-premise licenses and cloud licenses.

Node Count

The number of nodes in the DB system. The number depends on the shape you select. You can specify 1 or 2 nodes for virtual machine DB systems, except for VM.Standard2.1 and VM.Standard1.1, which are single-node DB systems.

Note: Some shapes may not be available in new tenancies.

Note: Except 1.1 and 2.1, all other shapes seem to be supported for RAC (2-node DB system).

Software Edition

The database edition supported by the DB system.

Cluster Name

A unique cluster name for a multi-node DB system. The name must begin with a letter and contain only letters (a-z and A-Z), numbers (0-9) and hyphens (-). The cluster name can be no longer than 11 characters and is not case sensitive.

Fault domain

Select the fault domain for the database node, if the DB System contains 2 nodes, you will be able to configure the fault domain for each node.

Example Database Systems on Bare Metal

Image: DB System Options for Bare Metal

This example illustrates the fields and controls for DB System Options for Bare Metal . You can find definitions for the fields and controls later on this page.

DB System Options for Bare Metal

Field or Control

Definition

Total Node Count

The number of nodes in the DB system. Only single node DB systems are supported for BM shapes.

CPU Core Count

Number of CPU cores enabled on the database system. Cloud Manager does not validate the core count, therefore you must use the correct core count for the BM shape selected in the topology configuration or the deployment may fail.

Data Storage Percentage

Percentage assigned to DATA storage including user data and database files. The remaining percentage is assigned to RECO storage including database redo logs, archive logs, and recovery manager backups. Accepted values are 40% and 80%.

Disk Redundancy

Type of redundancy configured for the database system. Normal is 2-way redundancy. High is 3-way redundancy. Allowed values are High and Normal

Software Release

Oracle database release version. The database release version must be chosen based on the database version in PeopleSoft Image or customer's lifted database version.

Display Name

Display name for the DB system. The name doesn't need to be unique. An Oracle Cloud Identifier (OCID) will uniquely identify the DB system.

Auto Backup

Displays whether automatic incremental backups for this database is enabled or disabled.

License Type

The type of license you want to use for the DB system. Your choice affects metering for billing. License included means the cost of the cloud service includes a license for the Database service. Bring Your Own License (BYOL) means you are an Oracle Database customer with an Unlimited License Agreement or Non-Unlimited License Agreement and want to use your license with Oracle Cloud Infrastructure. This removes the need for separate on-premise licenses and cloud licenses.

Software Edition

The database edition supported by the DB system.

Fault Domain

Select the fault domain for the database node, if the DB System contains 2 nodes, you will be able to configure the fault domain for each node.

Example Database System on Exadata

Image: Database System Options on Exadata

This example illustrates the fields and controls on the database system options on Exadata. You can find definitions for the fields and controls later on this page.

Database System Options on Exadata

Field or Control

Definition

Exadata DB System

Displays a list of Exadata DB systems that are available in your availability domain. If there is only one Exadata DB System, the value is auto-populated.

Software Release

Oracle database release version. The database release version must be chosen based on the database version in PeopleSoft Image or customer's lifted database version.

Auto Backup

Displays whether automatic incremental backups for this database is enabled or disabled.

Database is RAC

Displays whether database is RAC.

For templates using a topology with multiple middle tiers, you will configure the custom attributes for each middle tier.

Image: Custom Attributes section

This example illustrates the fields and controls on the Custom Attributes section showing multiple middle tiers.

Custom Attributes section

Image: Middle Tier - General Settings and Domain Settings for Web Server

This example illustrates the fields and controls on the Middle Tier - General Settings and Domain Settings for Web Server. You can find definitions for the fields and controls later on this page.

Middle Tier - General Settings and Domain Settings for Web Server

Field or Control

Definition

Enable EM Agent

Select either Yes or No to enable or disable EM agent.

Weblogic Administrator Username

User name of the Weblogic administrator. This is used for accessing the Weblogic console.

PeopleSoft Deployment Path

Location where the PeopleSoft application is deployed.

Gateway Administrator Username

User Id of gateway administrator.

Pre Provision Custom Script

Select an uploaded script to execute prior to provisioning the environment.

See Upload Custom Scripts Page

Post Provision Custom Script

Select an uploaded script to run post provisioning.

See Upload Custom Scripts Page

Domain Settings

Field or Control

Definition

Number of Domains

Enter the number of web server domains. Number of domains can be 1 to 5.

Authentication Domain

The domain in which the portal is running and across which the single sign-on authentication token is valid.

HTTP PIA Port

There will be as many ports, equal to the given number of domains, separated by comma.

HTTPS PIA Port

There will be as many ports, equal to the given number of domains, separated by comma.

Image: Domain Settings for Appserver

This example illustrates the fields and controls on the Domain Settings for Appserver. You can find definitions for the fields and controls later on this page.

Domain Settings for Appserver

Field or Control

Definition

Number of Domains

Number of application server domains. Number of domains can be 1 to 5.

Number of App Server Instance Per Domain

Number of PSAPPSRV instances required. This configuration is applied to all App Server domains.

Number of Query Server Instances Per Domain

Number of PSQRYSRV instances required. This configuration is applied to all App Server domains.

Number of SQL Access App Server(PSSAMSRV) Per Domain

Number of PSSAMSRV instances required. This configuration is applied to all App Server domains.

Number of Jolt Listener per Domain

Number of Jolt Listener per Domain.

Jolt Port

There will be as many ports, equal to the given number of domains, separated by comma.

WSL Port

There will be as many ports, equal to the given number of domains, separated by comma.

Enable IB Domain on first Domain

If Yes is selected IB will be enabled in the first App Domain.

Number of App Server Instance (PSAPPSRV services) for IB

Number of App Server Instance (PSAPPSRV services) for IB.

Number of SQL Access App Server (PSSAMRSRV services) for IB

Number of SQL Access App Server (PSSAMRSRV services) for IB

Number of PSBRKHND instances for IB

Number of PSBRKHND instances for IB

Number of PSSUBHND instances for IB

Number of PSSUBHND instances for IB

Number of PSPUBHND instances for IB

Number of PSPUBHND instances for IB

If the middle tier is Process Scheduler and COBOL is enabled in the topology, the General Setting will include COBOL Complier Type.

Image: Process Scheduler Middle Tier - General Settings

This example illustrates a Process Scheduler middle tier node, where COBOL is enabled in the topology.

Process Scheduler Middle Tier - General Settings

Field or Control

Definition

COBOL Compiler Type

If COBOL is enabled in the selected topology, you must select the COBOL compiler type, Server Express or Visual COBOL.

Note: Server Express is not supported for PeopleTools 8.58 onwards.

Note: The COBOL license must be configured on the Cloud Manager Settings page. See Cloud Manager Settings Page

Image: Domain Settings for Process Scheduler Settings and Process Scheduler Server Definition Parameters

This example illustrates the fields and controls on the Domain Settings for Process Scheduler Settings and Process Scheduler Server Definition Parameters. You can find definitions for the fields and controls later on this page.

Domain Settings for Process Scheduler Settings and Process Scheduler Server Definition Parameters

Process Scheduler Settings

Field or Control

Definition

Number of Domains

Number of process scheduler domains.

Number of App Engine Server Instances(PSAESRV services) Per Domain

Number of application engines required.

Number of App Engine Server Instances(PSDSTSRV services) Per Domain

Number of application servers required.

Process Scheduler Server Definition Parameters

Field or Control

Definition

Application Engine

Number of application engine processes.

XML Publisher

Number of XML publishers.

COBOL SQL

Number of COBOL SQL processes.

Optimization Engine

Number of optimization engines.

SQR Process

Number of SQR processes.

SQR Report

Number of SQR reports.

Max Api Aware

Number of Max Api Aware.

Image: General Settings for Windows Middle Tier

This example illustrates the fields and controls on the General Settings for Windows Middle Tier. You can find definitions for the fields and controls later on this page.

General Settings for Windows Middle Tier

Field or Control

Definition

Enable EM Agent

Select either Yes or No to enable or disable EM agent.

WebLogic Administrator Username

User name of the WebLogic administrator. This is used for accessing WebLogic console.

Gateway Administrator Username

User ID of Gateway.

Pre Provision Custom Script

Select an uploaded script to execute prior to provisioning the environment.

See Upload Custom Scripts Page

Post Provision Custom Script

Select an uploaded script to run post provisioning.

See Upload Custom Scripts Page

NVision Mode

Select either OpenXML or Excel.

PeopleSoft Deployment Path

Location where the PeopleSoft application is deployed.

The database tier includes general settings and subnet settings.

Image: Database Tier – General Settings

This example illustrates the fields and controls on the Database Tier – General Settings. You can find definitions for the fields and controls later on this page.

Database Tier - General Settings

Field or Control

Definition

Database Server Port

Listener port number.

Database Connect ID

Connect Id for the database.

PeopleSoft Deployment Path

Location where the PeopleSoft application is deployed.

Enable EM agent

Select Yes to enable enterprise manager agent for creating the infrastructure that is required to deploy an EM agent.

Database Operator ID

Default database operator ID.

Database Access ID

Access ID for the database.

Database Type

Select the required database type. Available database types are DEMO or SYS.

Enable Multi Language

Select either Yes or No to enable multi language support.

Database Name

Name of the database.

Pre Provision Custom Script

Select an uploaded script to execute prior to provisioning the environment.

See Upload Custom Scripts Page

Post Provision Custom Script

Select an uploaded script to run post provisioning.

See Upload Custom Scripts Page

Is Database Unicode

Select either Yes or No.

Image: General Settings for ELK Stack Tier

This example illustrates the fields and controls on the General Settings for ELK Stack Tier. You can find definitions for the fields and controls later on this page.

General Settings for ELK Stack Tier

Field or Control

Definition

Cluster Name

The name of the Elasticsearch cluster.

PeopleSoft Deployment Path

Location where the PeopleSoft application is deployed.

Discovery Host Name

The host name for any nodes that are already members of a cluster.

Port

Elasticsearch port.

Installation Directory

The path to install Elasticsearch and/or Kibana.

Pre Provision Custom Script

Select an uploaded script to execute prior to provisioning the environment.

See Upload Custom Scripts Page

Post Provision Custom Script

Select an uploaded script to run post provisioning.

See Upload Custom Scripts Page

Kibana Port

Kibana port

Use the Environment Template – Define Security page to associate the zone in which the environment is created and the role that will have access to the template.

Image: Environment Template – Define Security Page

This example illustrates the fields and controls on the Environment Template – Define Security Page.

Environment Template - Define Security Page

Field or Control

Definition

Zone Name

Indicates the zone in which the environment is created.

Role Name

Indicates the roles that have access to the template for creating environments. Only the users belonging to the role specified will be able to access the template while creating environment.

The delivered Cloud Manager roles are:

  • Cloud Administrator (PACL_CAD)

  • Cloud PeopleSoft Administrator (PACL_PAD)

  • Self-Service User (PACL_SSC)

Use the Environment Template – Summary page (ECL_TEMPL_REV_FL) to review and submit the template details.

Image: Environment Template – Summary Page

This example illustrates the fields and controls on the Environment Template – Summary page.

Environment Template - Summary Page

The details provided in all the pages in the Environment Template wizard is displayed here.

Field or Control

Definition

Submit

Click this button to submit the details for template creation.