How to Set up OCI Tenancy for PeopleSoft Cloud Manager – Part I

In our previous blog we announced the release of the latest PeopleSoft Cloud Manager Image 6, which includes support for Oracle Cloud Infrastructure (OCI).  Cloud Manager for OCI is designed to work in a simple way.  Let’s try to understand those design aspects that must be considered for your planning.

  • Deploy all instances of a PeopleSoft environment in a single OCI Region
    Cloud Manager can deploy PeopleSoft environments in only one region, the one in which it is running.  When you sign in to Cloud Manager in a browser and access the Cloud Manager Infrastructure Settings page, you see this region listed as “Deployment Region.” When you create or configure an environment template in Cloud Manger, you will see all regions listed, but you must always specify the region chosen as Deployment Region on the Cloud Manager Infrastructure Settings page.
  • Deploy all instances of a PeopleSoft environment in a single Availability Domain (AD) in the chosen Deployment Region
    In environment templates, you can set the AD in which you want to deploy an environment.  All instances are deployed in the chosen AD.  Cloud Manager doesn’t provide the ability to choose different ADs for each instance of the same environment. For example, you will not be able to deploy a Database instance in one AD and middle tier components (Application Server, Process Scheduler, and PIA) or a PeopleSoft Client instance in another AD.
  • Deploy all instances of a PeopleSoft environment in a single compartment
    While defining environment templates you get an option to choose the compartment in which an environment will be deployed.  All instances of an environment will always be deployed in the selected compartment.  You will not be allowed to deploy instances of the same environment across two or more compartments.  For example, you cannot deploy a Database instance in one compartment and middle tier instances or a PeopleSoft Client instance on another compartment. 
  • Deploy the Cloud Manager instance, and all instances of a PeopleSoft environment, on a single VCN that is dedicated for PeopleSoft environments. 
    The Cloud Manager instance must be deployed in the same VCN as all instances of a PeopleSoft environment.  Under the dedicated VCN, you can create multiple subnets that can be used to isolate individual instances or production and non-production environments.

Let’s go through those requirements that satisfy the above mentioned design considerations.  To provision PeopleSoft environments in OCI using Cloud Manager, you’ll need to prepare your tenancy with a few pre-requisite configurations. 

Create a compartment

When you get access to your OCI tenancy, you’ll have an administrator user only.  You can find an overview about how to set up your tenancy here

Note. To locate the commands mentioned here, click the Navigation Menu at the top left of the OCI console home page.

Let’s start by creating a compartment in which all PeopleSoft environments will be provisioned.  If you want to deploy your development, test or production environments on separate compartments, then create enough compartments for the various environments.  For this blog, let’s assume we have created a compartment and named it nkpsft.

Create a cloud user for PeopleSoft

Sign in as the administrator user for OCI, and create a user for Cloud Manager with sufficient privileges to create and manage instances, the Virtual Cloud Network and subnets.  This involves multiple steps as outlined below.   

First, create a Group for Cloud Manager users; for example, CM-Admin.

Next, create a policy, for example CM-Admin-Policy, to grant access to compartment nkpsft to Cloud Manager group.

After that, create a user cloudmgr that will be used in Cloud Manager Settings.

Finally, add cloudmgr user to CM-Admin group.  With this, we have set up a compartment and a user with admin privileges to create and manage instances on OCI.

In our next blog, we’ll talk about the next important pre-requisite – Networking.  Cloud Manager Image 6 on OCI does not enforce a flat networking architecture, as it does in OCI-Classic.  Your network admin can design and lay out the required networking architecture.  You can create your own networking layout and Cloud Manager automation will use it to deploy PeopleSoft environments.  Remember, you’ll be creating networking components in the same compartment that you had created earlier, so that Cloud Manager gets access to it. 

 

How to Set up OCI Tenancy for PeopleSoft Cloud Manager – Part I

In our previous blog we announced the release of the latest PeopleSoft Cloud Manager Image 6, which includes support for Oracle Cloud Infrastructure (OCI).  Cloud Manager for OCI is designed to work in a simple way.  Let’s try to understand those design aspects that must be considered for your planning.

  • Deploy all instances of a PeopleSoft environment in a single OCI Region
    Cloud Manager can deploy PeopleSoft environments in only one region, the one in which it is running.  When you sign in to Cloud Manager in a browser and access the Cloud Manager Infrastructure Settings page, you see this region listed as “Deployment Region.” When you create or configure an environment template in Cloud Manger, you will see all regions listed, but you must always specify the region chosen as Deployment Region on the Cloud Manager Infrastructure Settings page.
  • Deploy all instances of a PeopleSoft environment in a single Availability Domain (AD) in the chosen Deployment Region
    In environment templates, you can set the AD in which you want to deploy an environment.  All instances are deployed in the chosen AD.  Cloud Manager doesn’t provide the ability to choose different ADs for each instance of the same environment. For example, you will not be able to deploy a Database instance in one AD and middle tier components (Application Server, Process Scheduler, and PIA) or a PeopleSoft Client instance in another AD.
  • Deploy all instances of a PeopleSoft environment in a single compartment
    While defining environment templates you get an option to choose the compartment in which an environment will be deployed.  All instances of an environment will always be deployed in the selected compartment.  You will not be allowed to deploy instances of the same environment across two or more compartments.  For example, you cannot deploy a Database instance in one compartment and middle tier instances or a PeopleSoft Client instance on another compartment. 
  • Deploy the Cloud Manager instance, and all instances of a PeopleSoft environment, on a single VCN that is dedicated for PeopleSoft environments. 
    The Cloud Manager instance must be deployed in the same VCN as all instances of a PeopleSoft environment.  Under the dedicated VCN, you can create multiple subnets that can be used to isolate individual instances or production and non-production environments.

Let’s go through those requirements that satisfy the above mentioned design considerations.  To provision PeopleSoft environments in OCI using Cloud Manager, you’ll need to prepare your tenancy with a few pre-requisite configurations. 

Create a compartment

When you get access to your OCI tenancy, you’ll have an administrator user only.  You can find an overview about how to set up your tenancy here

Note. To locate the commands mentioned here, click the Navigation Menu at the top left of the OCI console home page.

Let’s start by creating a compartment in which all PeopleSoft environments will be provisioned.  If you want to deploy your development, test or production environments on separate compartments, then create enough compartments for the various environments.  For this blog, let’s assume we have created a compartment and named it nkpsft.

Create a cloud user for PeopleSoft

Sign in as the administrator user for OCI, and create a user for Cloud Manager with sufficient privileges to create and manage instances, the Virtual Cloud Network and subnets.  This involves multiple steps as outlined below.   

First, create a Group for Cloud Manager users; for example, CM-Admin.

Next, create a policy, for example CM-Admin-Policy, to grant access to compartment nkpsft to Cloud Manager group.

After that, create a user cloudmgr that will be used in Cloud Manager Settings.

Finally, add cloudmgr user to CM-Admin group.  With this, we have set up a compartment and a user with admin privileges to create and manage instances on OCI.

In our next blog, we’ll talk about the next important pre-requisite – Networking.  Cloud Manager Image 6 on OCI does not enforce a flat networking architecture, as it does in OCI-Classic.  Your network admin can design and lay out the required networking architecture.  You can create your own networking layout and Cloud Manager automation will use it to deploy PeopleSoft environments.  Remember, you’ll be creating networking components in the same compartment that you had created earlier, so that Cloud Manager gets access to it.