Install the PeopleSoft Cloud Manager Stack with Resource Manager

Before You Begin

This 45-minute tutorial shows you how to obtain the PeopleSoft Cloud Manager stack from Oracle Cloud Infrastructure Marketplace and install it using Resource Manager.

Background

Resource Manager is an Oracle Cloud Infrastructure service that helps you install, configure, and manage resources. Resource Manager uses Terraform (which is part of the service) to codify your infrastructure in declarative configuration files, which allows you to review and edit, version, persist, reuse, and share them across teams. You can then use Resource Manager to provision Oracle Cloud Infrastructure resources using your Terraform configurations.

In this tutorial, you obtain the configuration files, or stack, for Cloud Manager from the Oracle Cloud Infrastructure Marketplace, and use Resource Manager to create an instance and associated resources such as a Virtual Cloud Network (VCN), subnet, gateways, and route tables. You enter the necessary configuration variables in the Resource Manager interface, and choose the types of resources created.

See Overview of Resource Manager in the Oracle Cloud Infrastructure documentation.

This is the tenth tutorial in the Install PeopleSoft Cloud Manager series. Read the tutorials in the order listed. The optional tutorials offer alternate methods for setup.

What Do You Need?

See the prerequisites in the tutorial Prepare to Install PeopleSoft Cloud Manager.

When using Resource Manager, the recommendation is to restrict access to the stacks and stack jobs using roles and policies.

See Securing Resource Manager, IAM Policies in the Oracle Cloud Infrastructure Documentation.

Step 1: Gather Information for the Cloud Manager Stack

The Resource Manager stack setup prompts you for account and instance information. This section describes how to gather the information before you run the script. Alternatively, you may prefer to have a Compute Console window open as you enter the values, and copy the necessary OCIDs as needed.

Sign in to Oracle Cloud Infrastructure, and select Identity & Security > Users from the Menu () at the top left of the window.
Locate your user account, and select View User Details from the actions menu.
Alternatively, click the user icon at the top of the page, as shown in the next illustration, and select your user name.
On the User Details page, copy the user OCID.

Description of this illustration (oci_user_details.png)
Select Governance & Administration, then Tenancy Details from the Menu at the top left of the Oracle Cloud Infrastructure window.
On the tenancy page, make a note of the Home Region.
Select Governance & Administration, then Limits, Quotas and Usage.
Identify an Availability Domain with sufficient resources, including Compute shapes, Resource Manager stacks, Virtual Cloud Network resources, and File System service mount points.
Make a note of the shape to install Cloud Manager.
See the tutorial Verify Oracle Cloud Account Information for PeopleSoft Cloud Manager.
Create a vault, encryption key, and secrets to store and manage the passwords required for the installation.
See the tutorial Create Vault Resources for PeopleSoft Cloud Manager.
Create the API signing pair and note the passphrase.
See the tutorial Generate API Signing Pair.
Verify your My Oracle Support user ID and password.
Make a note of the credentials for a registered My Oracle Support account with a support identifier (SI). The Cloud Manager setup process ("bootstrap") will connect to My Oracle Support and download specific patches needed to update the Cloud Manager instance. The patches are applied as part of the installation process, so that the Cloud Manager instance will be up to date when installation is complete.
If you want to use an existing VCN for the Cloud Manager installation, note the name.
You can also choose to create a new VCN as part of the Resource Manager job. The fields on the Configure Variables page for the stack change depending upon your selections. To create a VCN outside Resource Manager, see the tutorial Create a Virtual Cloud Network for Cloud Manager.
If you want to use existing Network Security Groups (NSGs) with the Cloud Manager installation, see the tutorial Use Custom or Private Network Resources with PeopleSoft Cloud Manager.
Use NSGs to control the security rules associated with your instances. You can select up to three NSGs that are associated with an existing VCN when filling out the Resource Manager stack for Cloud Manager.
If you want to use a web proxy to access Cloud Manager, you must first set it up and obtain the IP address or FQDN and port.
See the tutorial Configure a Web Proxy for Cloud Manager.
If you want to apply tags to the Cloud Manager instance, create them in Oracle Cloud Infrastructure.
You can select existing defined tags, or enter free-form tags, when filling out the Resource Manager stack for Cloud Manager. See the tutorial Create Defined Tags in Oracle Cloud Infrastructure for PeopleSoft Cloud Manager (Optional).

Tip:
You can select tags in two places during the installation process — on the Stack Information page and on the Configure Variables page. The tags that you select on the Configure Variables page will be associated with the Cloud Manager instance.

Step 2: Obtain the PeopleSoft Cloud Manager Stack from the Marketplace

To obtain the PeopleSoft Cloud Manager stack:

On the Oracle Cloud Infrastructure console home page, click the menu icon () and select Marketplace, then All Applications.
Under Filters on the left, select Stack from the Type drop-down list, and Oracle from the Publisher drop-down list.
On the Marketplace page locate and click the PeopleSoft Cloud Manager tile.
On the Overview page for the PeopleSoft Cloud Manager stack, select the compartment to install the instance.
Review the Oracle terms, and then select the option indicating that you have reviewed and understand the conditions.
Click Launch Stack.

Description of this illustration (obtain_stack_launchstack.png)
On the Create stack, Stack Information page, enter a stack name and description if desired, or accept the defaults.

Description of this illustration (create_stack_page_stack_information.png)
(Optional) Select tags to apply to the stack.
Click Next.
Continue with the steps in Enter Cloud Manager Instance Values.

Step 3: Enter Cloud Manager Instance Values

The Create Stack, Configure Variables page includes a list of the parameters needed to create and configure the Cloud Manager instance.

In the Cloud Manager Instance section, select the Availability Domain where you want to create the Cloud Manager instance from the drop-down list.
Select a shape with at least 1 OCPU and 14 GB or more of memory for the Cloud Manager instance from the Shape drop-down list.
The following example shows VM.Standard2.4 (4 OCPU, 60 GB RAM).

Note:
Remember to confirm that the required resources are available in your tenancy and Availability Domain.

Description of this illustration (create_stack_page_config_vars_top.png)
If you select a flexible shape, you must also specify the number of OCPUs and memory in GBs.

Select an AMD (VM.Standard.E3.Flex or VM.Standard.E4.Flex) or Intel flexible shape (VM.Optimized3.Flex). See the information on flexible shapes in Compute Shapes in the Oracle Cloud Infrastructure documentation.

Description of this illustration (create_stack_page_config_top_flex_shape.png)
Select the storage volume size in GBs for the secondary block volume for the Cloud Manager instance.
In the previous examples, the storage volume size is 200 GBs.
Select iscsi or paravirtualized from the volume attachment type drop-down list.
The iSCSI and Paravirtualized attachment types are options for attaching a block volume to a VM instance, and affect usage and performance. For information, see Volume Attachment Types in the Oracle Cloud Infrastructure documentation.
Select the option Choose SSH Key File, and browse to locate the file.
Alternatively, select the option Paste SSH Key, and paste the text in the field.

See the section Generate SSH Keys in the tutorial Prepare to Install Cloud Manager.
Enter the contents of your API Private Key.

See the tutorial Generate API Signing Keys for PeopleSoft Cloud Manager.
Enter the passphrase for the API Private Key, if you created one.
Enter a passphrase containing alphanumeric characters and the following special characters: tilde (~), AT sign (@), pound sign (#), percent sign (%), caret (^), asterisk (*), hyphen (-), underscore (_), equal sign (=), plus sign (+), left square bracket ([), left curly bracket ({), right square bracket (]), right curly bracket (}), colon (:), period (.), comma (,), question mark (?), slash (/).
Select the home region for your tenancy from the drop-down list. In this example, the tenancy home region is us-phoenix-1.

Description of this illustration (create_stack_page_config_vars_middle.png)
Enter a database name or accept the default name, CMPSDB.
Ensure that the name begins with an uppercase letter followed by 7 or fewer uppercase letters or numbers.
Select a compartment where the Oracle Cloud Infrastructure vault that contains your password secrets is located.
See the tutorial Create Vault Resources for Password Management for PeopleSoft Cloud Manager.
Select the vault.

Description of this illustration (create_stack_config_vars_dbname_vault.png)
Select the compartment where the vault secrets are stored.
Enter the Access ID, or accept the default.
Select the vault secret that you created for each password.
- Db Connect Password
- Access Password
- Db Admin Password
- Cloud Manager Administrator Password
- Integration Gateway User Password
- WebLogic Administrator User Password
- Web Profile User Password
- Domain Connect Password
Description of this illustration (create_stack_config_vars_secrets1.png)

Description of this illustration (create_stack_config_vars_secrets2.png)
(Optional) Enter the user ID and password for a registered My Oracle Support account.
If you do not supply the information here you can enter it after you complete the installation, on the Cloud Manager Settings page.
(Optional) Select the following information from the drop-down lists under Tags to apply a defined tag to the Cloud Manager instance:
- Tag Namespace
- Tag Key
- Value
The lists display the Tag Namespaces, Tag Keys, and Values that are available in your tenancy.
To apply a free-form tag, enter a name in the Tag Key field, and a value.
Click Add tag to add more tags, or click the X to remove a tag.

Description of this illustration (create_stack_config_vars_secrets3.png)
If you want to set up a new VCN, continue with the next section, Enter Values for a New Virtual Cloud Network.
If you want to use an existing VCN, skip the next section and continue with the section Enter Values for an Existing Virtual Cloud Network.

Step 4: Enter Values for a New Virtual Cloud Network

Use these instructions if you want to set up a new VCN for Cloud Manager. If you want to select an existing VCN, skip this section and go to the next section, Enter Values for an Existing Virtual Cloud Network.

To set up the Cloud Manager stack to create a new VCN:

In the Networking section, enter a host name for the Cloud Manager instance.
This name will be used as part of the URL you use to access Cloud Manager in a browser. The name must start with an alphanumeric character, following by alphanumeric characters or hyphens.
Select Create Network Resources.
The VCN will include gateways, subnets, and security rules, in the same compartment as the Cloud Manager instance. The exact items included depend upon the other selections that you make in the Networking section.

Description of this illustration (create_stack_new_vcn.png)
Enter a name for the new VCN.
The name must start with a letter. It can have a maximum of 15 letters and numbers.
Select Create Private Subnets if you want the Cloud Manager instance, and the components for provisioned environments, to reside in private subnets.
If you want to use public subnets, clear this option. This does not apply to the subnet for the bastion, if you create one, which is always public.

Note:
For security reasons, the public subnets do not allow access to the Internet by default. Review the subnets after installation and add any necessary security rules.

Select Create Subnets for PeopleSoft Components if you want to create subnets that you can use when you provision environments in Cloud Manager.

This includes the PeopleSoft components such as application server, Process Scheduler, web server, the PeopleTools client, and so on. The subnets are set up with the correct rules to allow the various components to communicate. The following table lists the subnets that are created by default:

Subnet Name	Usage
app	PeopleSoft application server and Process Scheduler nodes
cm	Cloud Manager instance and File Storage Service file server
db	Database instances
ft	PUM fulltier instances
bastion	Bastion host that provides external connectivity for SSH, HTTP, and so on, when external Internet connection is blocked.
mt	Generic subnet for mid-tier instances including application server, Process Scheduler, PIA and Search stack. This is an alternative to using the piaes and app subnets.
piaes	PIA and Search stack (OpenSearch and OpenSearch Dashboards, or Elasticsearch and Kibana) instances
win	Windows clients

If you only want to create a subnet for the Cloud Manager instance, clear the Create Subnets for PeopleSoft Components option.

Note:

If you do not select this option, the network will include a single subnet called cm. The cm subnet security rule will allow access to all ports within the subnet.

Select Create a Bastion to create a bastion instance to use for connecting to the Cloud Manager instance.
Select this option if the Cloud Manager instance resides in a private subnet. The IP for a private subnet cannot be accessed directly from the Internet. In this case, you can set up a bastion to enable SSH access to the Cloud Manager instance and SSH port forwarding to connect to the Cloud Manager web server (PIA). The bastion will be created inside the new VCN.

See the Oracle Cloud Infrastructure documentation for the Bastion service.

Note:
If you create a VCN with public subnets, and you do not create a bastion, the public subnets will include Internet access for the PIA HTTP and HTTPS ports by default.

Note:
Do not create a bastion if you are using a Government Cloud account. The Bastion service is not available.

Description of this illustration (create_stack_create_bastion.png)
If you select Create a Bastion, enter a name, or accept the default, cmbastion.
The bastion name must start with an alphanumeric character, followed by alphanumeric characters or hyphens
(Optional) For Custom PIA FQDN, enter a custom fully-qualified domain name (FQDN) for the URL used to access Cloud Manager PIA in a browser. Use the format hostname.example.com.
If you do not enter a custom PIA FQDN, the default domain name is based on the subnet and VCN names in this format: <hostname>.<subnet label>.<vcn label>.oraclevcn.com

For example, you may want to assign a custom PIA FQDN if you have purchased or otherwise obtained a Domain Name System (DNS) name, and want to map the Cloud Manager IP to that DNS name. If you assign a custom PIA FQDN, it also sets up a corresponding authentication domain for the Cloud Manager PIA.

Note:
If you assign a custom PIA FQDN when installing a Cloud Manager instance, you must carry out an additional step if you choose to perform a backup and restore of that Cloud Manager instance. Access the Cloud Manager instance with SSH as user opc as described in the tutorial Log in to the Cloud Manager Instance. Open the file /etc/oci-hostname.conf for editing, and change PRESERVE_HOSTINFO=3 to PRESERVE_HOSTINFO=0. This will allow the Cloud Manager backup and restore process to assign a new private IP and hostname during the backup process. See Understanding Cloud Manager Backup and Restore in the PeopleSoft Cloud Manager documentation, on the PeopleSoft Cloud Manager page on the Oracle Help Center.
(Optional) Select Show Advanced Networking Details to review and modify networking items such as the subnets, CIDR, and ports associated with the network.

Description of this illustration (create_stack_network_advanced_one.png)

Description of this illustration (create_stack_network_advanced_two.png)

Description of this illustration (create_stack_network_advanced_three.png)

Description of this illustration (create_stack_network_advanced_four.png)

Descrption of this illustration (create_stack_network_advanced_five.png)

Step 5: Enter Values for an Existing Virtual Cloud Network

Use these instructions if you want to use an existing VCN for Cloud Manager. If you want to create a new VCN, skip this section, and use the instructions in the previous section, Enter Values for a New Virtual Cloud Network.

To set up the Cloud Manager stack to use an existing VCN:

In the Networking section, enter a host name for the Cloud Manager instance.
This name will be used as part of the URL you use to access Cloud Manager in a browser.
Clear the option Create Network Resources.

Description of this illustration (create_stack_existing_vcn.png)
From the Network Compartment drop-down list, select the compartment containing the VCN and subnet you want to use.
From the Existing Network drop-down list, select the VCN that you want to use.
From the Existing Subnet for Cloud Manager drop-down list, select an existing subnet for the Cloud Manager instance. The subnet must be present in the VCN you selected.
(Optional) Enter the information for an existing Web Proxy for Cloud Manager.
If your network does not have an Internet Gateway or a NAT Gateway, you need a web proxy. Enter an IP address or fully-qualified domain name (FQDN) for an existing web proxy, followed by a colon and port number.
<proxy host>:<proxy port>
For example: 198.51.100.10:80 or webproxy.example.com:80

After you complete the Cloud Manager installation, follow the instructions in the tutorial Configure a Web Proxy for Cloud Manager.
If you select Create a Bastion, enter a name and select an existing subnet in the VCN you selected for the Cloud Manager instance.
(Optional) For Custom PIA FQDN, enter a custom fully-qualified domain name (FQDN) for the URL used to access Cloud Manager PIA in a browser. Use the format hostname.example.com.
If you do not enter a custom FQDN, the default domain name is based on the subnet and VCN names in this format: <hostname>.<subnet label>.<vcn label>.oraclevcn.com

For example, you may want to assign a custom URL if you have purchased or otherwise obtained a Domain Name System (DNS) name, and want to map the Cloud Manager IP to that DNS name. If you assign a custom PIA, it also sets up a corresponding authentication domain for the Cloud Manager PIA.

Note:
If you assign a custom PIA FQDN when installing a Cloud Manager instance, you must carry out an additional step if you choose to perform a backup and restore of that Cloud Manager instance. Access the Cloud Manager instance with SSH as user opc as described in the tutorial Log in to the Cloud Manager Instance. Open the file /etc/oci-hostname.conf for editing, and change PRESERVE_HOSTINFO=3 to PRESERVE_HOSTINFO=0. This will allow the Cloud Manager backup and restore process to assign a new private IP and hostname during the backup process. See Understanding Cloud Manager Backup and Restore in the PeopleSoft Cloud Manager documentation, on the PeopleSoft Cloud Manager page on the Oracle Help Center.
(Optional) Select the option Add Network Security Groups for Cloud Manager instance, and select up to three existing Network Security Groups (NSGs).
The drop-down lists display NSGs that are available in the existing VCN you selected. See the tutorial Use Custom and Private Network Resources for Cloud Manager.

Description of this illustration (create_stack_page_nsgs.png)

Step 6: Run the Cloud Manager Stack Job

After supplying the required information on the Create Stack pages, click Next, or click Back to make changes.
Review the configuration variables.
Select Run Apply to begin the Resource Manager job immediately. If you do not select this option, run the Plan and Apply jobs from the Stack Details page.

Description of this illustration (create_stack_run_apply.png)
Click Create.
If you selected the Run Apply option, Resource Manager executes the Terraform Apply job to create the specified resources. Follow the progress on the Stack Details page for the job.
When the Apply job status changes to Succeeded, select Outputs from the Resources list on the left.

Description of this illustration (stack_details_apply_job_outputs.png)

The outputs of the stack setup include the following:
- bastion_name — The name supplied when creating the bastion.
- cm_http_url — Use this URL to access Cloud Manager in a browser.
- cm_https_url — Use as the secure URL to access Cloud Manager in a browser.
- cm_private_ip — The private IP address for the Cloud Manager instance.
- cm_public_ip — The public IP address for the Cloud Manager instance.
- deployment_status — Select Show to view the message "Please check the files CloudManagerStatus.log and CloudManagerStatusError.log under /home/opc/bootstrap folder of the new VM."
Select Job Resources from the Resources list on the left to see the links to the Cloud Manager instance, oci_core_instance, and other resources you configured.
This example shows the bottom portion of the Job Details page, with the Job Resources list. What you see in this list depends upon your choices on the Create Stack pages.

Note:
Cloud Manager is not ready to use when the Apply job is complete. The Cloud Manager instance configuration ("bootstrap") script must run to complete the installation setup. The instance configuration script is launched automatically after the Apply job succeeds.

To monitor the script status, log in to the Cloud Manager instance as described in the tutorial Log in to the Cloud Manager Instance, and review the log file /home/opc/bootstrap/CloudManagerStatus.log.

For example, to view the end of the log file, enter this command:

$ tail /home/opc/bootstrap/CloudManagerStatus.log

Description of this illustration (stack_details_apply_job_assoc_resources.png)

Working with Resource Manager Jobs (Optional)

In some cases you may want to install Cloud Manager without starting from the beginning with a newly downloaded Marketplace stack. For example, if there is a problem with the stack execution, you can run the Terraform plan and apply jobs for the stack from Resource Manager without needing to download the stack again.

If you are rerunning the stack setup due to a problem, it is a good idea to remove the associated resources from the unsuccessful run first.

See Managing Stacks and Jobs in the Oracle Cloud Infrastructure documentation for more information.

If necessary, from the Oracle Cloud Infrastructure menu, select Resource Manager > Stacks.
Select your compartment if necessary, and locate the Cloud Manager stack you downloaded from the Marketplace.
If you want to remove resources from a previous run, click Destroy, and supply a name for the Destroy job.
Wait until the Destroy job is complete.
You can view the current input by selecting Variables from the Resources list on the left.
Click Edit Variables if you want to make any changes.

Description of this illustration (resmgr_stack_details_variables.png)
Click Plan at the top of the Stack Details page.

It is a good idea to run a Terraform plan job, so that you can validate the configuration, correct any errors, and preview the resources that will be created.

Description of this illustration (resmgr_stack_plan.png)
On the Plan frame, enter a name or accept the default, then click Plan.
When the plan execution is complete, on the Job Details page for the plan select Logs on the left, and review the Terraform plan details.
Scroll through to check for errors.
If you want to save the configuration files, click Download Terraform Configuration on the Job Details page for the plan.
Select Stack Details at the top of the page.
To execute the plan and complete the Cloud Manager installation, click Apply.
On the Apply frame enter a name for the apply job, or accept the default.
Select the job plan to use from the Apply Job Plan Resolution drop-down list.
Select Automatically approve, or select the latest successful job plan to run.

Description of this illustration (resmgr_stack_apply.png)
Click Apply.

Note:
Cloud Manager is not ready to use when the Apply job is complete. The Cloud Manager instance configuration ("bootstrap") script must run to complete the installation setup. The instance configuration script is launched automatically after the Apply job succeeds.

To monitor the script status, log in to the Cloud Manager instance as described in the tutorial Log in to the Cloud Manager Instance, and review the log file /home/opc/bootstrap/CloudManagerStatus.log.

For example, to view the end of the log file, enter this command:

$ tail /home/opc/bootstrap/CloudManagerStatus.log

Next Steps

Learn More

PeopleSoft Cloud Manager Home Page, My Oracle Support, Doc ID 2231255.2
Cumulative Feature Overview Tool (Click Generate a CFO report and select PeopleSoft Cloud Manager at the top.)
Oracle Cloud Documentation in Oracle Help Center

Title and Copyright Information

Install the PeopleSoft Cloud Manager Stack with Resource Manager

F26267-11

August 2025

Obtain the PeopleSoft Cloud Manager stack from Oracle Cloud Infrastructure Marketplace and install it using Resource Manager.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.