Installing PeopleSoft Cloud Manager on Oracle Cloud Infrastructure Compute Classic


Options



Before You Begin

Purpose

This tutorial describes the process to obtain PeopleSoft Cloud Manager from Oracle Cloud Marketplace and install it on an Oracle Cloud Infrastructure Compute Classic instance.

Time to Complete

Approximately 2 hours.

Background

Use Cloud Manager to deploy PeopleSoft environments in Oracle Cloud Infrastructure Compute Classic (Compute Classic) for demonstration, testing, development, and production. Cloud Manager delivers a way to define your own PeopleSoft environments and save them as deployment templates.  These templates can then be used by self-service users to create their own environments either for their development or testing.

PeopleSoft Cloud Manager deploys PeopleSoft environments on Linux VMs and uses a Microsoft Windows VM to install PeopleSoft PeopleTools components.

This tutorial describes processes used by the Cloud Administrator in installing and setting up Cloud Manager. For information about using Cloud Manager to create topologies and templates, and environments, and other information on using Cloud Manager after installation, see the PeopleSoft Cloud Manager online documentation on the PeopleSoft Hosted Online Help site.

Note. You may see subtle differences in the appearance of the Oracle Cloud Infrastructure Compute Classic user interface as compared to the illustrations in this document. For example, the locations of pages, tabs, buttons, text boxes, links and so on may have changed since this document was published. Nevertheless, the concepts presented in this document are still valid and all steps are mandatory. The Oracle Cloud Infrastructure Compute Classic documentation should have current information on using images and creating instances.

Note. PeopleSoft Cloud Manager images use the PeopleSoft deployment package (DPK) format. However, be aware that the use of DPK customizations, which can be used with other types of PeopleSoft DPKs, is not supported for PeopleSoft Cloud Manager.

See the PeopleSoft Cloud Manager Home Page, My Oracle Support, Doc ID 2231255.2, for links to other Cloud Manager documentation, and information about known issues.

Context

After you complete the instructions in this tutorial to install and sign in to Cloud Manager, see the PeopleSoft Cloud Manager online documentation to use Cloud Manager. Note that with the exception of the “Lift and Shift” process, all of the following procedures are carried out in Oracle Cloud.

  • Subscribe to channels to automatically download PeopleSoft Update Images (PIs) and PeopleSoft Release Patchsets (PRPs).
  • Define environment topology based on PeopleSoft components and Oracle Cloud infrastructure elements (virtual machines).
  • Use delivered templates and create new templates based on defined topologies.
  • Create PeopleSoft environments from templates.
  • Move PeopleSoft on-premises (local) environments to Oracle Cloud ("Lift and Shift").
  • Set up PeopleSoft Update Manager (PUM) environments for Selective Adoption.
  • Update Cloud Manager using PUM functionality.
  • Upgrade PeopleSoft environments from PeopleTools 8.55 to 8.56 or 8.57.
  • Apply PeopleSoft PeopleTools patches.

What Do You Need?

The following list includes the requirements for obtaining and installing Cloud Manager on a Compute Classic instance.  For information on requirements for using Cloud Manager after installation, such as the uses listed in the Context section, see the PeopleSoft Cloud Manager online documentation.

  • Licensing Requirements and Prerequisite Products
    • The PeopleSoft Licensing Information User Manuals include details about entitled products, restricted-use licensing grants, and prerequisite requirements that may be needed to use certain Cloud Manager features. To locate the information about Cloud Manager licensing and prerequisites, see the Licensing Information User Manual for your PeopleSoft application on the PeopleSoft Documentation Portal. You can find the Cloud Manager details in the PeopleTools section.
    • PeopleSoft Cloud Manager will automate provisioning of the Microsoft Windows environments that will host the PeopleTools Application Designer and Life Cycle Management (LCM) products required for PeopleSoft Update Manager. Your Oracle Cloud IaaS subscription grants the license required for Microsoft Windows 2012 R2. Please see the Oracle Compute FAQ, https://cloud.oracle.com/en_US/opc/compute/faq, under Windows Licensing Information for details.
      Note that the Windows 2012 R2 image must be procured from Oracle Cloud Marketplace.
    • PeopleSoft Cloud Manager provides a tool for migrating on-premises PeopleSoft environments to Oracle Cloud.  This tool requires Oracle Database 12c. Customers must possess or obtain an on-premises license for Oracle Database 12c Standard or Enterprise Edition.
  • Oracle Cloud Infrastructure Classic subscriptions
  • Users and Roles
    You need full privileges to be able to create instances, create storage volumes, and create or upload contents to object storage. Here are some of the required roles:
    • You must be a user with the Compute_Monitor and Compute_Operation roles for Oracle Cloud Infrastructure Compute Classic.
      See About Compute Classic Roles in Using Oracle Cloud Infrastructure Compute Classic.
    • You must be a user with the Storage_Administrator, Storage_ReadOnlyGroup and Storage_ReadWriteGroup roles for Oracle Cloud Infrastructure Object Storage Classic.
      See About Object Storage Classic Roles and Users in Using Oracle Cloud Infrastructure Object Storage Classic.
    • If you use Oracle Database Cloud Service (DBaaS) (optional), you must be a user with the Database Administrator role.
      See About Database Cloud Service Roles and Users in Administering Oracle Database Cloud Service.
    • If you use Oracle Database Backup Cloud Service (optional), you must be a user with the DatabaseBackup_Administrator, DatabaseBackup_ReadOnlyGroup, and DatabaseBackup_ReadWriteGroup roles.
      See the Oracle Database Backup Cloud Service documentation.
    • If you use Oracle SOA Cloud Service (optional), you must be a user with the SOA_Administrator role.
      See the Oracle SOA Cloud Service documentation.
  • SSH Keys
    For the section Generating an SSH Key, you will need either an implementation of the ssh-keygen utility (for Linux) or an application such as PuTTY (for Microsoft Windows), installed on a local computer.
  • User IDs and passwords
    When you run the Cloud Manager Instance Configuration Wizard that sets up the Cloud Manager VM, you are asked for several user IDs and passwords. The Cloud Manager image is delivered with default user IDs that are reset by the setup script. The user IDs and password required by the instance configuration wizard includes the following:
    • CLADM password: The CLADM user account is delivered with Cloud Manager, and is associated with the Cloud Administrator role (PACL_CAD).
    • PeopleSoft Database Access ID and password
    • Database Administrator and password: The Cloud Manager image is delivered with a default password for SYS and SYSTEM users. This  will be reset using the value you supply to the Cloud Manager Instance Configuration script.
    • PeopleSoft connect ID and password
    • Oracle WebLogic administrator password
    • PeopleSoft Web Profile password
    • Integration Gateway password
    • Oracle Cloud user ID and password
    • My Oracle Support account ID and password
  • Port numbers
    Cloud Manager is provided with default values for the HTTP, HTTPS, Jolt, and WSL ports. For security reasons Oracle recommends that you do not use the default HTTP or HTTPS port numbers. Before beginning this procedure, decide on your port numbers. Configure the Oracle Cloud Infrastructure Compute Classic instance to allow access for the HTTP and HTTPS ports, and then supply the same HTTP and HTTPS port numbers when you run the Cloud Manager Instance Configuration script.
  • Default Internet access
    This tutorial includes instructions to allow Internet access to provisioned instances by default. This is required for Cloud Manager to install packages from a repository.

Process Overview

To install Cloud Manager, execute the following steps:

  1. Verify Oracle Cloud account information used in installing Cloud Manager.

  2. Obtain an Oracle Linux image to be used for the file server.

  3. Obtain an updated Microsoft Windows Server 2012 R2 image.

  4. Generate an SSH key pair using an on-premises Linux or Microsoft Windows system.

  5. Upload the SSH public key to Compute Classic.

  6. In Compute Classic, create a security list, security application, and security rule.

  7. Locate the Cloud Manager application and initiate deployment in Oracle Cloud Marketplace.

  8. Provision a Compute Classic instance with a Linux operating system from the Cloud Manager image.

  9. Use the instance configuration wizard to set up Cloud Manager.

  10. Sign in to the Cloud Manager instance in a browser and supply the Cloud Manager Settings details.

  11. In Cloud Manager, create a file server.
  12. Review the delivered users and permission lists.

  13. Configure Cloud Manager Linux VM for YUM updates (optional)

Verifying Oracle Cloud Account Information

Fulfilling Password Requirements

Ensure that the password for your Oracle Cloud account does not include these characters: single quote ('), double quote ("), slash (\), or pound (#).

This requirement is in addition to those for the Oracle Cloud password policy. The Cloud Manager Instance Configuration Wizard does not support passwords with these characters. If necessary, reset your password before running the configuration script.

Verifying Access to Oracle Cloud Infrastructure Compute Classic and Oracle Cloud Infrastructure Object Storage Classic

  1. Sign in to the Oracle Cloud My Services application at https://cloud.oracle.com/sign_in.

  2. Select the account type from the drop-down list, and enter the necessary credentials.

    If you want to use your Identity Cloud Service (IDCS) account, select Cloud Account with Identity Cloud Service from the drop-down list, and enter your Cloud Account Name. Alternatively, select Traditional Cloud Account, as shown in this example, and then select the Data Center/Region that hosts your Oracle Cloud identity domain. Click the My Services button.

    Oracle Cloud sign in window
    Description of this image
  3. If necessary, enter your identity domain on the Oracle Cloud sign in page and then click the Go button:

    Oracle Cloud My Services page
  4. Enter a valid user name and password for your Identity Domain and then click Sign In:

    Oracle Cloud Sign in page with user name and password
  5. On the Dashboard, click the options icon (Options button) on the Compute card and select Open Service Console to verify your access.

    Oracle Cloud My Services Dashboard
    Description of this image
  6. Verify access to Oracle Cloud Infrastructure Object Storage Classic by repeating step 5 with the Storage card.

    Note. If you do not see the Compute and Storage cards on the Dashboard, click Customize Dashboard and change the selection to Show.

Determining REST End Point URLs

The Cloud Manager Instance Configuration Wizard includes prompts for Oracle Cloud Compute REST end point, Oracle Cloud DBAAS REST end point, and Oracle Storage REST end points. A REST end point is the URL needed to access the service using the REST (REpresentational State Transfer) application programming interface (API). Oracle provides the REST endpoint URLs for every Oracle Cloud service subscription. Contact your administrator to obtain the following prerequisite information to sign in to the identity domain:

  • User name and password to sign in to Oracle Cloud
  • Data center
  • Oracle Cloud identity domain

If you have an account for Oracle Database Cloud Service (DBaaS), you can use it to host PeopleSoft environment databases for Cloud Manager. Use the same identity domain (and zone if applicable) for the DBaaS account as that for the Oracle Cloud Infrastructure Compute Classic account. If you later configure additional file servers or Cloud Manager instances, use the same identity domain, zone, and Oracle Cloud Infrastructure Compute Classic REST end point.

To find the REST end points for Oracle Cloud Infrastructure Compute Classic, DBaaS, and Storage Classic for your Identity Domain:

  1. From the Oracle Cloud Dashboard, click the options icon (Options button) on the Compute card and select Open Service Console.

    Select Open Service Console on Compute Card
    Description of this image
  2. On the Compute service console, click the site name at the top of the page.

    Note. Be sure to select the site in which you will provision the Cloud Manager instance.

    Click Site on the Compute Console
    Description of this image
  3. Record the value for the REST endpoint from the Site Selector dialog box.

    Site Selector box
    Description of this image
  4. To determine the REST end point for Oracle Database Cloud Service, click Dashboard.

  5. On the Dashboard, click the options icon on the Database card, and then select View Details.

  6. Record the value from the REST Endpoint field on the Overview page.

    Service Details: Oracle Database Cloud Service page
    Description of this image
  7. To determine the REST end point for Oracle Database Cloud Service, click Dashboard.

  8. On the Dashboard, click the options icon on the Storage Classic card, and then select View Details. Alternatively, click the Navigation icon and select Services, Oracle Cloud Infrastructure Object Storage Classic.

  9. Select Accounts. Under Account Information, record the Rest Endpoint and Auth V1 Endpoint.

  10. You can also build the URLs for the end points manually by substituting the Cloud account name for <cloud_account_name> in the following URL syntax:

    • Oracle Cloud Storage REST end point: https://<cloud_account_name>.storage.oraclecloud.com/v1/Storage-<cloud_account_name>
    • Oracle Cloud Storage Auth end point: https://<cloud_account_name>.storage.oraclecloud.com/auth/v1.0

Determining REST and AUTH End Points for IDCS Accounts

If you use an IDCS account, in addition to the REST End Point URLs for Compute Classic and DBaaS described in the previous section, the Cloud Manager Instance Configuration Wizard includes prompts for Oracle Cloud Storage account name, Oracle Cloud Storage REST end point, and Oracle Cloud Storage Auth end point.

To find the account name and end point URLs for Oracle Cloud Infrastructure Object Storage Classic:

  1. Sign in to the Oracle Cloud My Services application at https://cloud.oracle.com/sign_in.

  2. Select Cloud Account with Identity Cloud Service from the drop-down list, enter your Cloud Account Name, and then click My Services.

  3. On the Oracle Cloud Dashboard, the Cloud Account name, idcsaccount in this example, is displayed at the top right. You can also view account details by clicking Account Management.

    Oracle Cloud My Services Dashboard
    Description of this image
  4. Click the options menu on the Storage Classic tile, and select View Details. On the Overview page for Service: Oracle Cloud Infrastructure Object Storage Classic, you can find the REST end point and Auth end point URLs in the Additional Information section.

    Storage Classic card with View Details
    Description of this image
  5. You can also build the URLs for the end points manually by substituting the IDCS account name for <cloud_account_name> in the following URL syntax:

    • Oracle Cloud Storage REST end point: https://<cloud_account_name>.storage.oraclecloud.com/v1/Storage-<cloud_account_name>
    • Oracle Cloud Storage Auth end point: https://<cloud_account_name>.storage.oraclecloud.com/auth/v1.0

Determining the Service Instance ID for IDCS Accounts

For IDCS accounts, you must supply the Service Instance ID for Compute Classic when you run the Cloud Manager Instance Configuration Wizard. To find the Service Instance ID:

  1. From the Oracle Cloud Dashboard, click the options icon (Options button) on the Compute Classic card and select View Details.

    Alternatively, you can select the Compute Classic link on the card.

  2. On the Overview page for Service: Oracle Cloud Infrastructure - Compute Classic, in the Additional Information section, make a note of the Service Instance ID.

Obtaining an Oracle Linux Image for the File Server

Choosing an Oracle Linux Image for the File Server

Cloud Manager requires an Oracle Linux 6 image for the file server. Obtain an image using one of the methods outlined here. After completing the Cloud Manager setup, you will configure the file server in the Cloud Manager Settings area.

You can install an Oracle Linux image for the file server using one of these methods:

  • You can download an Oracle Linux image, called PeopleSoft Linux Image for Cloud Manager, that is configured for use with Cloud Manager from Oracle Cloud Marketplace.
    This is a reference image that you can use for a quick start to evaluate Cloud Manager. If the image suits your organizational requirements, you can continue to use the same image for production.
  • If your organization has requirements for custom packages and security settings, you can create a custom image based on the PeopleSoft Linux Image for Cloud Manager  reference image. Use the information in the tutorial Creating a Custom Linux Image for PeopleSoft Cloud Manager to customize the reference image.
  • You also have the option to create a custom image using a base Oracle Linux image. In this case, you must carry out additional steps to configure the image to work with Cloud Manager. In addition, you are responsible for determining and obtaining any operating system requirements.
    For information, see the tutorial Creating a Custom Linux Image for PeopleSoft Cloud Manager on Oracle Cloud Infrastructure Compute Classic, in the Oracle Learning Library.

Obtaining the PeopleSoft Linux Image for Cloud Manager from Oracle Cloud Marketplace

Make a note of the fully qualified name. You will need this when running the script to set up Cloud Manager.

Locate the Cloud Manager image and initiate deployment as follows:

  1. Sign in to the Oracle Cloud Marketplace at http://cloud.oracle.com/marketplace.

  2. In the Applications area, enter peoplesoft in the search text box, and click the Go button.

    Oracle Cloud Marketplace home page
  3. In the search results, locate PeopleSoft Linux Image for Cloud Manager and click the name to begin the deployment. The next page lists the operating system and kernel versions included in the image. Click the Get App button.

    Get App button
  4. Review and accept the Oracle terms and conditions and click the Next button.

  5. If necessary, select the name of the Oracle Cloud Identity Domain that is associated with your Compute Classic subscription from the Compute Account drop-down list, and then click the Install button.

    Install Application page in Oracle Cloud Marketplace
    Description of this image
  6. You see a message saying the application was successfully installed. The image that will be used for the file server is now available to the Compute Classic account you selected in step 5. Click Start Compute Console.

    Application Successfully Installed window
    Description of this image
  7. On the Oracle Cloud sign in window, enter your identity domain, then your user name and password to sign in.

  8. On the Oracle Cloud Dashboard, click the options icon (Options button) on the Compute card and select Open Service Console.

  9. Select Images.

  10. On the Images page, select Personal from the Category drop-down list to see the PeopleSoft Linux Image for Cloud Manager that you obtained from Oracle Cloud Marketplace.

  11. To obtain the fully qualified name for the image, hold the cursor over the image name.

    Make a note of the name, as you must supply this name when configuring Cloud Manager. The name in this example is /Compute-idendomain/psft_user@example.com/PSFTCM_OL_6.6_01. The fully qualified name has the format /Compute-<identity_domain_name>/<user_name>/<image_name>

    Qualified image name for Linux reference image
    Description of this image

Obtaining an Updated Microsoft Windows Image for Cloud Manager

Cloud Manager requires a Microsoft Windows image to host PeopleSoft client tools such as Change Assistant and Application Designer. Follow the instructions in the tutorial Creating a Windows Private Image for PeopleSoft Cloud Manager on Oracle Cloud Infrastructure Compute Classic to obtain a Microsoft Windows Server 2012 R2 image, apply the latest Microsoft updates, and create a private image. You will enter the fully qualified name for the private image when completing the section Specifying the Cloud Manager Settings in this tutorial.

Generating an SSH Key Pair

When you create your Compute Classic instance, you must provide a secure shell (SSH) public key that will be used for authentication when you log in to the instance. Generate your SSH key pair and upload the SSH public key to Compute Classic before you start to create your instance.

Generating an SSH Key Pair on UNIX or UNIX-Like Systems Using ssh-keygen

  1. Run the ssh-keygen command.

    ssh-keygen -b 2048 -t rsa
  2. The command prompts you to enter the path to the file in which you want to save the key. A default path and file name are suggested in parentheses. For example: /home/user_name/.ssh/id_rsa. To accept the default path and file name, press Enter. Otherwise, enter the required path and file name, and then press Enter.

  3. The command prompts you for a passphrase. Enter a passphrase.

    Note that the passphrase isn't displayed when you type it in. Remember the passphrase. If you forget the passphrase, you can't recover it.

  4. When prompted, enter the passphrase again to confirm it.

    The command generates an SSH key pair consisting of a public key and a private key, and saves them in the specified path. The file name of the public key is created automatically by appending .pub to the name of the private key file. For example, if the file name of the SSH private key is id_rsa, then the file name of the public key would be id_rsa.pub.

  5. Make a note of the path where you've saved the SSH key pair.

    When you create instances, you must provide the SSH public key. When you log in to an instance, you must specify the corresponding SSH private key and enter the passphrase when prompted.

Generating an SSH Key Pair on Microsoft Windows

Generate a secure SSH key pair using an application such as PuTTY. 

Make a note of the public and private key names and where they are saved. When you create instances, you must specify the SSH public key. When you log in to an instance, you must provide the path to the corresponding SSH private key and enter the passphrase when prompted.

Uploading the SSH Key

  1. Sign in to the Oracle Cloud My Services as described in the section Determining REST End Point URLs.

  2. On the Dashboard, click the options icon (Options icon) on the Compute card, and select Open Service Console:

    Oracle Cloud My Services Dashboard page with Cloud Services menu
    Description of this image
  3. Select the Network tab and then select the SSH Public Keys link on the left side of the Network configuration page.

    The SSH Public Keys page is displayed.

    Oracle Compute Cloud Service Network page, SSH Public Keys
    Description of this image
  4. Click Add SSH Public Key.

  5. In the Add SSH Public Key dialog box, enter a name, for example cminfodev-key, and the value of the SSH public key you generated, and then click Add.

    Note. Paste the key value exactly as it was generated. Don't append or insert any extra characters, line breaks, or spaces.

    Your SSH public key is added to Compute Classic.

    Add SSH Public Key dialog box
    Description of this image

Creating a Security List, Security Application and Security Rule for Cloud Manager

The PeopleSoft Cloud Manager image found in Oracle Cloud Marketplace contains a web server installation configured to listen for requests on port 8000 (HTTP) and 8443 (HTTPS). Your security protocols may require you to use other port values. If you use other ports, configure them here and supply the same values in the section Running the Cloud Manager Instance Configuration Wizard.

The steps included in the Creating a Security List, Creating a Security Application, and Creating a Security Rule sections demonstrate how to define a security list using port 8000 for HTTP; however, we recommend that you use this as an example only and subsequently enable port 8443 or another port for secure connections (HTTPS/SSL) only.

Note. Oracle highly recommends that you use the HTTPS protocol in all deployments. Follow the instructions found in the PeopleTools System and Server Administration product documentation to implement the encryption keys and certificates required for Secure Sockets Layer (SSL) encryption.

Creating a Security List

A security list is a group of Compute Classic instances that you can specify as the source or destination in one or more security rules. The instances in a security list can communicate fully, on all ports, with other instances in the same security list. In a subsequent step the Compute Classic instance will be added to this security list.

To create a security list:

  1. On the Compute Classic service console, click the Network tab.

  2. Select the Security Lists link, and then click Create Security List.

    Security Lists page
    Description of this image
  3. In the Create Security List dialog box, select or enter the following information:

    • Name: Enter a name for the new security list. For the purpose of this tutorial, enter cm_infodev_seclist. Note this name. You'll use it later in this tutorial.
    • Inbound Policy: Accept the default option, Deny (Drop packets, no reply).
    • Outbound Policy: Select Permit (Allow packets).
    • Description: Enter a description for the new security list if desired; for example, PeopleSoft Cloud Manager security list.
      Create Security List dialog box
      Description of this image
  4. Click Create.

  5. You may create additional security lists for access to other HTTP and HTTPS ports.

Creating a Security Application

A security application is a mapping between a port number and port type (TCP, UDP, or ICMP). To open port 8000, you must create a security application for that port.

  1. Click the Network tab and then the Security Applications link.

    Security Applications page
    Description of this image
  2. Click Create Security Application.

  3. In the Create Security Application dialog box, select or enter the following information:

    • Name: Enter a name for the new security application. For the purpose of this tutorial, enter cm_infodev_tcp8000. Note this name. You'll use it later in this tutorial.
    • Port Type: Select TCP.
    • Port Range Start: In both of these fields, enter the port that you want to open, port 8000.
    • Description: Enter a description for the new security application (for example, Allow TCP traffic on port 8000).
      Create Secuity Application dialog box
      Description of this image

  4. Click Create.

  5. You may create additional security applications for TCP access to other ports.

Creating a Security Rule

Create a security rule to allow TCP traffic from the Internet on port 8000.

  1. Click the Network tab and then the Security Rules link.

    Security Rules page
    Description of this image
  2. Click Create Security Rule.

  3. In the Create Security Rule dialog box, select or enter the following information:

    • Name: Enter an appropriate name for the rule. For the purpose of this tutorial, enter cm_infodev_secrule8000.
    • Status: Select Enabled.
    • Security Application: Select the cm_infodev_tcp8000 security application that you created earlier.
    • Source: Select the Security IP List radio button
    • From the Security IP List drop-down list, select public-internet for the purposes of this tutorial.
      Note that public-internet is a default security IP list that permits traffic from any host on the Internet. If you want to restrict access to a certain set of IPs, you must create a new Security IP List and use it here.
    • Destination: Select the cm_infodev_seclist security list that you created earlier.
    • Description: Enter a description for the rule (for example, PeopleSoft Cloud Manager security rule).
      Create Security Rule dialog box
      Description of this image
  4. Click Create.

Enabling SSH Access with the Default Security List

Enable SSH access by default for all instances that are created in Compute Classic. This procedure assumes the presence of the default security list. If you do not see the security list named default associated with your identity domain, contact Oracle support. The default security list must be present in the path /Compute-<domain>/default/default.

  1. On the Compute Classic service console, click the Network tab.

  2. On the Network page, select Security Rules, and then click Create Security Rule.

  3. In the Create Security Rule dialog box, define a security rule to allow SSH connections from public-internet to the default security list you created in the previous steps.

    Enter or select the following information:
    • Name: Enter a descriptive name, for example DefaultPublicSSHAccess.
    • Security Application: Select ssh from the drop-down list.
    • Source: Select the Security IP Address option, and select public-internet from the drop-down list.
    • Destination: Select the Security List option, and select the default security list from the drop-down list.
    • Description: Enter a description such as Default security rule for public SSH access.

    Create Security Rule dialog box
    Description of this image
  4. Click Create.

Initiating Deployment in Oracle Cloud Marketplace

Locate the Cloud Manager image and initiate deployment as follows:

  1. Sign in to the Oracle Cloud Marketplace at http://cloud.oracle.com/marketplace.

  2. In the Applications area, enter PeopleSoft in the search text box, and click the Go button.


    Oracle Cloud Marketplace sign in windows
  3. In the search results, click the Cloud Manager name to begin the deployment. The next page describes the components included in the image, such as the version of the Linux operating system and PeopleSoft PeopleTools. Click the Get App button.

    Get App button
  4. Review and accept the Oracle terms and conditions and click the Next button.

  5. If necessary, select the name of the Oracle Cloud Identity Domain that is associated with your Compute Classic subscription from the Compute Account drop-down list, and then click the Install button.

  6. You see a message saying the application was successfully installed. The image that will be used to start the instance is now available to the Compute Classic account you selected in step 5.

    Click the Start Compute Console button, which will present the sign-in page for Compute Classic.

Provisioning the Cloud Manager VM

Use the Compute Classic service console to configure the VM instance from the Cloud Manager image that you obtained from Oracle Cloud Marketplace. This section assumes that you signed in to Compute Classic directly from the Oracle Cloud Marketplace installation.

Note. You can also choose to sign in to Compute Classic later to create the Cloud Manager VM instance.

See Creating an Instance from the Instances Page in the Oracle Cloud Infrastructure Compute Classic (IaaS) documentation.

  1. If you signed in to Compute Classic directly from the Oracle Cloud Marketplace installation, the Create Instance page appears, with the Cloud Manager image.

    Click Select, and then click the right arrow (>), shown here above Review and Create on the top right.

    Image page, Selected image
    Description of this image
  2. If you do not go directly to the console after installing from Oracle Cloud Marketplace, sign in to the Compute Classic service console later and select the Images tab. The Cloud Manager image is included in the list on the Images page.

  3. Click the option button (Option button) for the Cloud Manager image and select Create Instance.

    Images page, Create Instance
    Description of this image
  4. On the Shape page, select the shape that you want to use, and then click the right arrow (>) beside Review and Create on the top right.

    The shape specifies the OCPU and memory allocated. The minimum recommended is oc1m (1 OCPU, 15 GB), as shown in this example.

    Create Instance, Shape page
    Description of this image
  5. On the Instance page, specify the following information and then click the right arrow (>), shown here above Review and Create, on the top right.

    • Enter a name and label for the instance, or accept the default name and label. In this example the name and label are CloudManager_Infodev.
      The Name used here must be unique in the domain. No other instance in the domain where Cloud Manager is running should have the same name.
    • Click in the SSH Keys field and select your public SSH key, cminfodev-key in this example.
    • Verify that this text appears in the Custom Attributes field: {"cloud_manager_image":"true"}
      Create Instance, Instance page
      Description of this image
  6. On the Network page, click in the Security Lists area, and select the default security list (required).

    Create Instance, Network page
    Description of this image
  7. Enter a DNS hostname prefix, such as cminfodev.

  8. Click in the Public IP Address drop-down list.

    Create Instance, Network page with Public IP Adress drop-down list
    Description of this image
  9. Select Persistent Public IP Reservation from the drop-down list.

    Create Instance, Network page, with Persistent IP address
    Description of this image
  10. Click Create IP Reservation.

    Create Instance, Network page, with Create IP Reservation button
    Description of this image
  11. In the Create Public IP Reservation dialog box, enter a name to identify the public IP reservation, such as cminfodev_publicip, and click Create.

    Create IP Reservation dialog box
    Description of this image
  12. Click the right arrow (>) beside Review and Create on the top right of the Network to continue.

    Continue on Network page
    Description of this image
  13. On the Storage page, accept the defaults and then click the right arrow.

    Create Instance, Storage page
    Description of this image
  14. Review the instance configuration and click the Create button to create the Oracle Cloud Infrastructure Compute Classic instance.

    Review page
    Description of this image
  15. Check the status of the Cloud Manager instance using the Instances tab. When the instance is ready to use, the status is set to Running.

  16. To view detailed information about the instance, click the options button and select View. The instance page describes the storage volumes, security lists, SSH public keys, and instance snapshots for the instance.

    Running instance
    Description of this image

Setting Up Cloud Manager on the Linux VM

The Cloud Manager image includes a setup script that will start automatically when you access the instance created in the previous section. The instance, which is a Linux VM, can be accessed from a Microsoft Windows machine using an SSH client such as PuTTY, or directly from a Linux machine. The setup script prompts you for several user IDs and passwords, as mentioned in the section What Do You Need. Make a note of your input for later reference.

Logging in to the Linux VM from a Linux or UNIX System

  1. Enter the following command:

    ssh -i <path_to_private_key_file>/<private_key_name> -o ServerAliveInterval=5 -o ServerAliveCountMax=1 opc@<public_ip_address_of_instance>
  2. If you don't know the public IP address of your instance, you can find it by going to the Instances tab on the Compute Classic service console. From the list of instances displayed, identify the correct instance and use the menu on the right to view the running instance. The Overview information section includes the Public IP Address.

  3. If you entered a passphrase when creating your SSH key pair, enter the passphrase when prompted.

  4. The first time you connect to your instance, the SSH utility prompts you to confirm the public key. In response to the prompt, enter yes.

Logging in to the Linux VM from a Microsoft Windows System

  1. Start PuTTY. The PuTTY Configuration window is displayed, showing the Session panel.

  2. In the Host Name (or IP address) field, enter the public IP address of your instance.

    Note. If you don't know the public IP address of your instance, go to the Instances tab on the Compute Classic service console, click the Options menu for the instance and select View to see the details page.

  3. In the Connection type field, select SSH if it is not already selected.

    PuTTY Configuration dialog box, Basic options for your PuTTY session
    Description of this image
  4. In the Category pane, click Connection. Enter 5 in the Seconds between keepalives (0 to turn off) text box.

    PuTTY Configuation dialog box, Options controlling the connection
    Description of this image
  5. In the Category pane, expand SSH, and then click Auth. The Auth panel is displayed.

  6. In the Private key file for authentication field, click Browse and select the private key file that you saved earlier, cminfodev-key.ppk in this example.

    PuTTY Configuration dialog box, Options controlling SSH authentication
    Description of this image
  7. In the Category tree, click Session.

    The Session panel is displayed.

  8. In the Saved Sessions field, enter a name for this connection configuration, and then click Save.

  9. Click Open to open the connection.

    The PuTTY Configuration window is closed and the PuTTY window is displayed.

  10. When prompted for a user name, enter opc.

  11. Enter the passphrase you had provided for your SSH key pair.

  12. The first time you connect to your instance, the PuTTY Security Alert window is displayed, prompting you to confirm the public key. Click Yes to continue.

Changing the Default Password for the opc User (Mandatory)

After successfully making the initial connection to the Compute Classic instance using the SSH protocol, you must immediately change the default password of the opc user. Note that you cannot do anything from the Linux command line until the default password has been changed. Use these guidelines to change the password:

Change the default password using the following guidelines:

  • Use an alphanumeric password.
  • The length must be a minimum of 8 characters.
  • Use at least one upper-case alphabetic character.
  • Use at least one numeric character.
  • Use at least one special character, such as @,  #, $ and so on.
  • It cannot closely resemble a dictionary word.
  1. If you haven’t already done so, SSH to the VM from either a Linux or Microsoft Windows system:

    $ ssh -o ServerAliveInterval=5 -o ServerAliveCountMax=1 $HOST -i <path_to_private_key>/<private_key_name> opc@<public_ip_address_of_instance>
  2. You will see the following message telling you to change your password, upon your first connection via SSH:

    login as: opc
    Using username "opc".
    Authenticating with public key "cminfodev-key"
    Passphrase for key "cminfodev-key":
    You are required to change your password immediately (root enforced)
    Authorized uses only. All activity may be monitored and reported.
    WARNING: Your password has expired.
    You must change your password now and login again!
    
  3. Enter the default (current) password, which is OracleCloud.

    Changing password for user opc.
    Changing password for opc
    (current) UNIX password:
    
  4. When the password has been successfully changed, you will be immediately disconnected and you should see a message indicating success, similar to the following:

    New UNIX password: 
    Retype new UNIX password:
    passwd: 
    all authentication tokens updated successfully. 

You can now SSH to the instance using the opc user as previously directed. The password for the opc user must be changed at least every 90 days.

Running the Cloud Manager Instance Configuration Wizard

Before beginning this procedure, ensure that you have the URLs, user IDs, and passwords mentioned in the What Do You Need? section at the beginning of this tutorial.

  1. Connect to the Cloud Manager instance with SSH if necessary.

    If you are using PuTTY to connect on Microsoft Windows, select Session, enter the IP address for the Cloud Manager instance in the Host Name field, and then click Open.

    The Cloud Manager Instance Configuration Wizard script starts automatically when you sign in.

  2. Enter the user ID that you use to sign in to Oracle Cloud; for example, psft_user@example.com, and then enter the user ID password twice.

    The password that you enter here must fulfill the requirements in the section Verifying Oracle Cloud Account Information.
    *********************************************************
    *Welcome to Cloud Manager Instance Configuration Wizard *
    *********************************************************
                                  
    Enter the Oracle Cloud user id: psft_user@example.com
    Enter the Oracle Cloud user password : Re-Enter the Oracle Cloud user password :
  3. Enter the required credentials.

    • If you are using a Traditional Cloud Account, enter your Oracle Cloud Identity Domain name, for example idendomain.
    • If you are using an IDCS account, enter the Service Instance ID for Compute Classic that you determined at the beginning of this tutorial.  
    Enter the Oracle Cloud domain name or Service ID (IDCS): idendomain 
  4. Enter the REST end point URL for the Compute Classic domain that you determined at the beginning of this tutorial.

    See Verifying Oracle Cloud Account Information.

    Enter the Oracle Cloud Compute REST end point: https://api-xyz.compute.xxx.oraclecloud.com/   
  5. Enter your user ID and then enter the password twice, for My Oracle Support.

    The My Oracle Support credentials are used to set up the repository for downloading images from My Oracle Support.

    Enter the My Oracle Support user id: psft_user@example.com
    Enter the My Oracle Support user password :
    Re-Enter the My Oracle Support user password :
  6. Enter the Domain Boot password twice for the Cloud Administrator, CLADM.

    Do not follow the requirements in the prompt for the maximum length. The password must be 8 characters or less in length and contain only alphanumeric characters.

    Enter the new Domain Boot user password for user CLADM:
    Ensure that the password contains only alphanumeric characters
    and is no more than 32 characters in length: Re-Enter the new Domain Boot user password for user CLADM:
  7. Enter the password twice for the PeopleSoft connect ID, people, following the requirements in the prompt.

    Enter the new PeopleSoft Connect ID password for user people. Ensure that
    the password does not contain any spaces ( ), dashes (-) percentage (%), slash (/) and
    quote characters (",') and is at least 6 and no more than 30 characters in length: Re-Enter the new PeopleSoft Connect ID password for user people:
  8. Enter the PeopleSoft access ID, SYSADM, and enter the password twice, following the requirements in the prompt.

    SYSADM is the only valid access ID for Cloud Manager.

    Enter the PeopleSoft Access ID [SYSADM]: SYSADM 
    Enter the new PeopleSoft Access password for user SYSADM:
    Ensure that the password contains only alphanumeric characters and
    is no more than 8 characters in length: Re-Enter the new PeopleSoft Access password for user SYSADM:
  9. Enter the password twice for the SYS or SYSTEM database users, following the requirements in the prompt.

    Enter a new PeopleSoft database admin users [SYS/SYSTEM] password.
    Ensure that the password is between 8 and 30 characters in length
    with at least one lowercase letter, one uppercase letter, one number
    and one special character (_,-,#):
    Re-Enter the new Database Admin Password:
  10. Enter the password twice for the Oracle WebLogic administrator user, system, following the requirements in the prompt.

    Enter a new WebLogic Server Admin user [system] password. Ensure that
    the password is between 8 and 30 characters in length with at least
    one lowercase letter, one uppercase letter, one number or one
    one special character (!@#$%^&):
    Re-Enter a new WebLogic Server Admin user [system] password:
  11. Enter the password twice for the PeopleSoft Web Profile user, PTWEBSERVER:

    Enter the new password for Web Profile user PTWEBSERVER.
    Ensure he password contains only alphanumeric characters and
    is between 8 and 30 characters in length:
    Re-Enter the password for Web Profile user PTWEBSERVER:
  12. Enter the password twice for the Integration Gateway user, administrator, following the requirements in the prompt:

    Enter the new password for Integration Gateway user administrator.
    Ensure the password contains only alphanumeric characters and
    is between 8 and 30 characters in length:
    Re-Enter the new password for Integration Gateway user administrator:
  13. Choose whether to configure advanced options.

    • If you want to configure advanced options answer y (yes). Use these prompts to change the default database name and port numbers.
    • If you have an IDCS account, answer y (yes), to supply required information.
    • If you want to accept the default options, and you don't have an IDCS account, answer n (no) and continue with step 18.
    Do you want to configure advanced Cloud Manager options or configure Cloud Account with Identity Cloud Service options [y|N]?: y

    Enter the name of the database. Please ensure that the database name starts with a letter and includes only uppercase alphabets and numbers and is no more than 8 characters in length [CMPSDB]: MYCMDB Enter the HTTP port. Please ensure that port value is between 1024 and 65535 [8000]: 8000 Enter the HTTPS port. Please ensure that port value is between 1024 and 65535 [8443]: 8843 Enter the JOLT port. Please ensure that port value is between 1024 and 65535 [9033]: 9033 Enter the WSL port. Please ensure that port value is between 1024 and 65535 [7000]: 7000

    The responses to the following prompts differ depending upon the type of account. If you are using an IDCS account, the values in the next four steps are required. If you are using a Traditional Cloud Account, the information is optional, and you can press ENTER to continue at each prompt. The methods to determine these values were described at the beginning of this tutorial.

    See Verifying Oracle Cloud Account Information.

  14. Enter the account name for Oracle Cloud Infrastructure Object Storage Classic. This is required for both Traditional Cloud Accounts and IDCS accounts.

    If you have a cloud account with Identity Cloud Service enter the following options. If you have a 
    Traditional Cloud Account, press Enter to skip.

    Enter the Oracle Cloud Storage account name:
  15. Enter the REST end point for Oracle Cloud Infrastructure Object Storage Classic. This is required for both Traditional Cloud Accounts and IDCS accounts.

    Enter the Oracle Cloud Storage REST end point [https://idendomain.storage.oraclecloud.com/v1/Storage-idendomain]:
  16. Enter the authentication end point for Oracle Cloud Infrastructure Object Storage Classic. This is required for both Traditional Cloud Accounts and IDCS accounts.

    Enter the Oracle Cloud Storage Auth end point [https://idendomain.storage.oraclecloud.com/auth/v1.0]:
  17. If you have an account for Oracle Database Cloud, enter the REST end point URL.

    Enter the Oracle Cloud DBAAS REST end point: https://dbaas.oraclecloud.com/
  18. Review the summary information. Answer y to continue, or n to change your responses.

    If you did not configure the advanced options, the summary shows the default values for the database name and port numbers. Be sure to verify these values before continuing.

    Note: Cloud Manager public ip refers to the IP address of the Cloud Manager VM. If there is an IP address displayed for this item, it means that the Oracle Cloud credentials you provided are valid and there is no issue in accessing Oracle Cloud services.

    Validating the Cloud Manager Bootstrap input values ....
    ************************************************************************************************** Cloud Manager Instance Configuration Summary ************************************************************************************************** Oracle Cloud user id                            : psft_user@example.com Oracle Cloud user password                      : ******** Oracle Cloud domain name                        : idendomain Oracle Cloud Compute REST end point             : https://api-xyz.compute.xxx.oraclecloud.com/
    Oracle Cloud Storage REST end point : https://idendomain.storage.oraclecloud.com/v1/Storage-idendomain Oracle Cloud Storage Auth end point : https://idendomain.storage.oraclecloud.com/auth/v1.0 Oracle Cloud DBAAS REST end point               : https://dbaas.oraclecloud.com/ My Oracle Support user id                       : psft_user@example.com My Oracle Support user password                 : ******** Domain Boot user password for user CLADM        : ******** PeopleSoft Connect ID password for user people  : ******** PeopleSoft Access password for user SYSADM     : ******** Database Admin password                         : ******** WebLogic Server Admin password                  : ******** Web Profile user PTWEBSERVER password          : ********
    Integration Gateway user administrator password : ******** Name of the database                            : MYCMDB HTTP port                              : 8000 HTTPS port                              : 8843 JOLT port                              : 9033 WSL port                              : 7000 Cloud Manager public ip : 198.51.100.67
    **************************************************************************************************
                          Cloud Manager Bootstrap Input Validation Summary
    **************************************************************************************************

    Oracle Cloud Authentication                       : SUCCESS
    Cloud Manager IP validation                       : SUCCESS
    Default sec-list validation                       : SUCCESS
    [Sec-list name: /Compute-idendomain/default/default]
    Oracle Storage Cloud Access : SUCCESS
    **************************************************************************************************
    Are you happy with your answers? [y|n]: y

    *********************************************************************** * Cloud Manager provisioning started. Please check the * * /opt/oracle/psft/dpk/scripts/CloudManagerStatus.log file for status * ***********************************************************************
  19. Monitor the configuration process status by reviewing the log file /opt/oracle/psft/dpk/scripts/CloudManagerStatus.log.

    The configuration process takes several minutes. When the process completes successfully, the same log file includes the Cloud Manager URL to sign in to the PeopleSoft Pure Internet Architecture (PIA) in a browser.

    Note. The term bootstrap is sometimes used to refer to the Cloud Manager Instance Configuration wizard.

The Cloud Manager instance configuration log files are found in these locations:

  • /opt/oracle/psft/dpk/scripts/CloudManagerStatus.log — Input logs for the Cloud Manager Instance Configuration wizard
  • /opt/oracle/psft/dpk/scripts/psft_opc_setup.log — Cloud Manager provisioning log
  • /home/psadm2/psft/data/cloud/cmlogs/BOOTSTRAP_LOGS/*  — PeopleSoft Cloud Administrator logs related to processes such as file server creation
  • /home/psadm2/psft/data/cloud/cmlogs/envs/CLOUD_MANAGER_INSTANCE/*  — PeopleSoft Cloud Administrator logs related to Cloud Manager instance creation for updating Cloud Manager

Reviewing the Cloud Manager Input Validation Details

The tables in this section list input validation messages you may see and their meaning.

Table 1. Oracle Cloud Authentication

#
Message Value Reason Comment
1
SUCCESS Oracle Cloud user id, Oracle Cloud user password, Cloud domain name are correct values. Oracle Cloud Infrastructure Compute Classic REST end point may or may not be valid, because the user can provide a REST end point for different sites in the same domain. To confirm, check the Cloud Manager IP validation (Table 3).
2
FAILURE

One or more of the following inputs is wrong:

  • Oracle Cloud user id

  • Oracle Cloud user password

  • Cloud domain name

  • Oracle Cloud Compute REST end point

  • This failure may or may not be the reason for other validation failure.

  • This failure can also occur due to OPC Auth Token error.


Table 2. Cloud Manager IP validation

#
Message Value Reason Comment
1
SUCCESS
  • Able to get the Cloud Manager IP successfully, and the value will be updated in the Cloud Manager public ip field.

  • User has entered the correct REST end point

NA
2
FAILURE
  • Wrong Oracle Cloud Infrastructure Compute Classic REST end point

  • Oracle Cloud Authentication is failed (see Table 1)

NA

Table 3. Default sec-list Validation

#
Message Value Reason Comment
1
SUCCESS The Cloud Manager VM is already associated with the /Compute-<domain_name>/default/default sec-list The OPC domain has /Compute-<domain_name>/default/default sec list and it is associated with the Cloud Manager VM.
2
FAILURE

The Cloud Manager VM is not associated with the /Compute-<domain_name>/default/default sec-list

  • The OPC domain may or may not have the sec-list.

  • The user did not provide the default sec-list along with the custom sec-lists.


Table 4. Oracle Storage Cloud Access

#
Message Value Reason Comment
1
SUCCESS User is able to access the Oracle Storage Cloud for this OPC domain. NA
2
FAILURE User is not able to access the Oracle Storage Cloud for this OPC domain.
  • The user has not initialized the Cloud storage service.

  • User has never been into Cloud Storage console, hence had never specified the geographic data jurisdiction.

Adding the Security Lists to the Cloud Manager Instance

Add the Cloud Manager instance to the Security List that you defined in the earlier section Creating a Security List. You must complete this step to enable access to Cloud Manager PIA from the public-internet security IP list mentioned earlier.

Adding an instance to a security list allows it to communicate freely with all other instances in that same security list.

  1. Select the Instances tab on the Compute Classic service console.

  2. Click the options icon (Options icon) for the Cloud Manager instance and select View.

  3. Click Add to Security List in the section Security Lists.

    Security Lists section on instance overview page
    Description of this image
  4. In the Add to Security List dialog box, select the security list you created.

    Add to Security List dialog box
    Description of this image
  5. If you created other security lists, for example for the 8443 port, add them.

Accessing the Cloud Manager Instance in a Browser

Sign in to the running Cloud Manager instance in a browser, using a URL constructed from the publicly addressable DNS name. As mentioned, you can find the Cloud Manager URL in the log file created after the successful completion of the Cloud Manager Instance Configuration Wizard.

Alternatively, to determine the URL, locate the public IP address of the Compute Classic instance.

  1. Select the Instances tab.

  2. Click the options icon (Options icon) for the Cloud Manager instance and select View to review the instance details.

  3. Note the Public IP address.

    The URL also requires the HTTP or HTTPS port, as listed in the summary information for the Cloud Manager Instance Configuration Wizard in the previous section.

    The URL will always follow this format for HTTP:
    http://oc-<public-ip-address-using-hyphens>.compute.oraclecloud.com:<http_port>/ps/signon.html

    For HTTPS:
    https://oc-<public-ip-address-using-hyphens>.compute.oraclecloud.com:<https_port>/ps/signon.html

    For example, for Cloud Manager that was configured with HTTP port 8002 on a Compute Classic instance with the public IP address 198.51.100.67, the URL  is:
    http://oc-198-51-100-67.compute.oraclecloud.com:8002/ps/signon.html.

  4. Enter the Cloud Manager URL in a browser. You see a window for Weblogic Application Server 12.2.1.0.0.

    Welcome to Weblogic Application Server window
  5. Click the link Please click here to PeopleSoft logon page to display the Cloud Manger sign in window.

Note. Oracle strongly recommends that you change the default PeopleSoft Pure Internet Architecture (PIA) user passwords, because the Compute Classic instances are on the public Internet.

Specifying the Cloud Manager Settings

Using the Cloud Manager Settings Page

Use the Cloud Manager Setting page to specify user IDs and other information before using Cloud Manager to create topologies and templates.

  1. Sign in to Cloud Manager in a browser using the Cloud Administrator user ID and password.

  2. On the home page, select the Cloud Manager Settings tile.

    Note that the Cloud Manager Settings tile appears only for users who sign in with the Cloud Administrator user ID.

    Cloud Manager home page with Setting tile
    Description of this image
  3. Select Settings from the left-hand panel.

  4. In the Oracle Cloud Service section, verify that the information for your Compute Classic account is correct. This information is based on the input to the Cloud Manager Instance Configuration wizard.

    • Domain Name: This field displays the Compute Classic Identity Domain. Do not change this value.
    • User Name: This field displays the Compute Classic account ID. Do not change this value.
    • Password: Enter the password for your Compute Classic account.
    • Storage Account name: Enter the name for your Storage Classic account.
    • Compute REST Endpoint: This field displays the URL to access Compute Classic. You can find the REST endpoint on the Service Details page for your Identity Domain, or on the instance details page.
    • DBaaS REST Endpoint: This field displays the URL to access Oracle Database Cloud Service, if you have an account. You can find the REST endpoint on the Service Details page for your Identity Domain, or on the instance details page.
    • IDCS Storage REST Endpoint: Enter the Storage Classic REST URL that you determined earlier.
    • IDCS Storage Auth REST Endpoint: Enter the Storage Classic Auth URL that you determined earlier.
    Oracle Cloud Service section of Cloud Manager Settings page
    Description of this image
  5. In the My Oracle Support (MOS) Credentials section, verify that the user ID and password for your My Oracle Support account are correct. This information is based on the input to the Cloud Manager Instance Configuration wizard.

    Enter the URL https://updates.oracle.com.
    Read the MOS License information and click the links to read about the My Oracle Support terms of use and privacy policy.

    Note. Be sure to read the My Oracle Support license information before you subscribe to download channels.

    My Oracle Support (MOS) Credentials section of Cloud Manger Settings page
    Description of this image
  6. In the PeopleSoft Credentials for REST Services, verify the delivered Cloud Manager Administrator user name, CLADM, and password. This information is based on the input to the Cloud Manager Instance Configuration wizard.

    This refers to the standard Integration Broker REST services that are available in the Cloud Manager instance. These REST services are used internally by Cloud Manager modules to send and receive the results of long-running, asynchronous activities.

    PeopleSoft Credentials for REST Services section of Cloud Manager Settings page
    Description of this image
  7. In the Lift & Shift Container section, the container name is included for information.

    Lift & Shift Container section of Cloud Manager Settings page
    Description of this image
  8. If you have a license for a COBOL compiler, enter your COBOL serial number and license key in the Cobol License section (optional).

    Note. Oracle is the exclusive reseller of the Micro Focus COBOL compiler for use with PeopleSoft applications. Contact your Oracle sales representative for a license.

    Cobol License section of Cloud Manager Settings page
    Description of this image
  9. Enter information about operating system images that Cloud Manager will access, if available.

    The following example shows the Operating System Image section after specifying two images, for Oracle Linux 6.6 and Microsoft Windows Server 2012, which may be needed, for example, with PUM environments.

    The OS Image field contains the fully-qualified name for the image. You can obtain image information using one of these methods:

    • To obtain image information from the Images page: On the Oracle Cloud dashboard, access the Compute Classic service console. Select the Images tab, and hold the cursor over the image name to see the image URL.
    • Alternatively, after creating an instance from an image, select the Instances tab. Click the menu icon Menu icon for the instance, and select View.
      On the Instances Overview page, the Image URL is included in the Information section.

    For the Bootable Volume Size, specify a value in GB that is at least 5% larger than the size of the machine image that you are associating with the storage volume. Note that the size of the machine image refers to the uncompressed size, not the compressed size.
    Operating System Image section of Cloud Manager Settings page
    Description of this image
  10. The File Server Details field is not editable. After you create a file server using the instructions in the section Creating and Maintaining a File Server in this tutorial, the name will be displayed.

    File Server Details section of Cloud Manager Settings page
    Description of this image
  11. Click Save Settings at the top of the page if you make any changes.

Using the My Settings Page

End users can enter or edit their public SSH key on the My Settings page. After adding this SSH key, Cloud Manager will inject the key into the Linux VM of any PeopleSoft environment that you provision. You can see the SSH keys associated with the PeopleSoft environment by viewing the details for the instance in the Compute Classic service console.

  1. From the Cloud Manager home page, click the My Settings tile.

  2. To enter a new SSH Public key, enter the text in the My SSH Publish Key field and click Save.

    My Settings page
    Description of this image
  3. To edit or replace an existing key, enter the text for the key, and then click Save.

  4. Click Edit, and change or replace the text.

  5. Click Save again.

Creating a File Server

Creating a New File Server

Use the Cloud Manager Settings tile to create a file server, which is used with the Cloud Manager Repository feature to automatically download updates. This section describes how to create a new file server for a Cloud Manager instance. This section assumes that an Oracle Linux image is available and specified under Operating System Image in the Settings page described previously.

See the information on Cloud Manager Settings - File Server page in the PeopleSoft Cloud Manager product documentation, PeopleSoft Hosted Online Help.

If you are creating a new Cloud Manager instance and want to reuse the file server storage volume that you created for a previous Cloud Manager instance, see the later section, Reusing an Existing File Server Storage Volume.

  1. Sign in to Cloud Manager in a browser using the Cloud Administrator user ID and password.

  2. On the home page, select the Cloud Manager Settings tile.

    Note that the Cloud Manager Settings tile appears only for users who sign in with the Cloud Administrator user ID.

  3. Select File Server from the panel on the left.

    File Server Configuration page
    Description of this image
  4. On the File Server Configuration page, enter a name, such as cmInfodevFileserver. Enter a name with alphanumeric characters, and no special characters.

    File Server Configuration page
    Description of this image
  5. Select Small, Medium or Large from the VM Size drop-down list.

  6. The Boot Volume Size is specified when setting up the image.

  7. Enter a value in GB for the Data Volume Size. Enter a value large enough to accommodate images you plan to download, such as 500 GB.

  8. The Oracle Linux Image name is specified when setting up the image.

  9. In the Advanced section, select NO for Use existing fileserver volume.

    See the next section for information on reusing an existing file server volume

  10. Click Create.

    File Server Configuration page with information supplied
    Description of this image
  11. Click Yes on the dialog box with Are you sure you want to continue?

    Verify creation dialog box
  12. When the file server is deployed, the status changes to Configured.

    File Server Configuration page with status complete
    Description of this image

Ensuring File Server Access

You can access the Cloud Manager VM in an SSH session using your personal public and private SSH key pair, as previously mentioned. To log in to the file server VM, you access the Cloud Manager VM with SSH, then initiate another session using the Cloud Manager private SSH key, which is added by the Cloud Manager deployment process. Use the following steps to access the file server VM from the Cloud Manager VM:

  1. Log in to the Cloud Manager instance as the opc user, and supply the passphrase for your SSH public key.

  2. Change to root user:

    sudo su - psadm2
  3. Change directory to /home/psadm2/psft/data/cloud/opchome/<identity_domain_name>/<opc_user_id>/.ssh.

    For example, /home/psadm2/psft/data/cloud/opchome/idendomain/psft_user@example.com/.ssh.

  4. Locate the file id_key_rsa.pub, which contains the SSH public key of the Cloud Manager instance.

    Note that id_key_rsa.pub is the SSH key that Cloud Manager uses to connect to instances that it provisions, and is not the same as your personal public SSH key. The corresponding private SSH key is id_key_rsa.

  5. To access the existing file server VM, start an SSH session with this command:

    ssh -i id_key_rsa opc@<file_server_name>

If you wish to retain and access all downloaded packages on the file server VM independently, you must manually add your personal public SSH key to the file server after you create it in Cloud Manager. This applies to both new file servers and file servers you create from existing file server storage volumes. Add the personal public SSH key text to a new line in the /home/opc/.ssh/authorized_keys file on the file server VM. After adding the personal public SSH key, use the matching private SSH key to access the file server VM.

For more information on working with file servers, see the PeopleSoft Cloud Manager online documentation on PeopleSoft Hosted Online Help.

Reusing an Existing File Server Storage Volume

You can create a snapshot of a file server volume to reuse it for a new Cloud Manager instance.

Note. It is not necessary to stop the existing Cloud Manager instance before creating the snapshot for a new Cloud Manager instance.

  1. Sign in to the Compute Classic service console, and select the Instances tab.

  2. Click the options icon for the existing file server instance, and select View.

    Instances page, select existing file server instance
    Description of this image
  3. On the instance details page, go to the Storage Volumes section.

  4. Click the options icon for the secondary storage volume, and select View Details.

    Instance details page, View details for file server
    Description of this image
  5. On the storage volume details page, go to the Storage Snapshots section, and click Create Storage Snapshot.

    Storage volume details page, Create Storage Snapshot
    Description of this image
  6. Specify the following information in the Create Storage Snapshot dialog box, and then click Create.

    Create Storage Snapshot dialog box
    Description of this image
  7. When the snapshot has been created, go to the Storage tab and select Storage Snapshots.

  8. Click the options icon for the snapshot, and select Restore Volume.

    Storage Snapshots page, Restore Volume
    Description of this image
  9. Specify the following information on the Restore Storage Volume dialog box, and click Restore.

    Restore Storage Volume dialog box
    Description of this image
  10. To view the volume created from the snapshot, go to the Storage tab, and select Storage Volumes.

  11. Hold the cursor over the volume name, and note the fully-qualified name.

    Storage page, view restored volume
    Description of this image
  12. Sign in to Cloud Manager in a browser using the Cloud Administrator user ID and password, and select the Cloud Manager Settings tile.

  13. Select File Server from the panel on the left. On the File Server Configuration page, the Boot Volume Size and Oracle Linux Image information fields are populated with information from the Settings page.

    File Server Configuration page
    Description of this image
  14. Enter a name for the new file server. Do not use the same name as that of the original file server instance.

  15. Expand the Advanced section and select Yes for the switch Use existing file server volume.

  16. Enter the fully-qualified path and name of the storage volume.

  17. Click Create.

    File Server Configuration page with user input
    Description of this image
  18. Wait until the status changes from In progress to Configured. The file server is ready for use.

    File Server Configuration page with status Configured
    Description of this image

Removing the File Server in Case of Failure

If the file server creation fails due to any issues, perform the following steps to clean up and recreate the file server. This section assumes that the Cloud Manager VM is up and running.

  1. Sign in to Cloud Manager in a browser using the Administrator user ID and password, and select the Cloud Manager Settings tile.

  2. Select File Server from the panel on the left. If the file server creation has failed, a Delete button will be enabled at the top right of the File Server Configuration page, and the Status will be Failed.

    File Server Configuration page with failed file server
    Description of this image
  3. For information about the failure, select the link beside Status Click here for more info to see the error description.

    Error description for file server failure
    Description of this image

    Alternatively, select Logs from the panel on the left, and search for the term "fileserver" for example:

    File server logs page
    Description of this image
  4. Click Delete to clean up the failed file server instance, and click Yes on the message box with "Are you sure you want to continue?"

    Verify that the file server was deleted from the instances on the Instances tab of the Compute Classic service console.

    Do you want to continue message
  5. If the delete action failed, as indicated by status Deletion Failed, click the Delete button again.

    File Server Configuration page with Status Deletion Failed
    Description of this image
  6. You see a message explaining that subsequent attempts to delete the file server will only delete the file server configuration details that are saved in Cloud Manager. You must also delete the file server instance and storage volumes manually before continuing. Click Yes to continue.

    To delete the instance manually, sign in to the Compute Classic service console, and locate the file server instance on the Instances tab. Select Delete from the options menu.

    Explanation of subsequent deletion
    Description of this image
  7. When you have deleted the file server, you can crate a new file server. Enter and save the correct information for the Linux OS image on the Settings page in the Operating System image section, and then return to the File Server Configuration page, which will have the Create button enabled.  Enter the required input and try to create the file server again.

    File Server Configuration page
    Description of this image

Reviewing Cloud Manager User, Roles, and Permission Lists

Understanding Cloud Manager Roles, Permission Lists, and User

Cloud Manager is delivered with these roles, permission lists, and user account:

  • Delivered roles
    • Cloud Administrator (PACL_CAD)
    • Cloud PeopleSoft Administrator (PACL_PAD)
    • Self-Service User (PACL_SSC)
  • Delivered permission lists
    • Cloud Administrator Permissions (PACL_001)
    • PeopleSoft Admin for Cloud (PACL_002)
    • Cloud Self Service (PACL_003)
  • Delivered user account
    The CLADM user account is associated with the Cloud Administrator role and other PeopleSoft administrative roles.

Here is a brief summary of the tasks associated with each delivered role. 

The Cloud Administrator:

  • Downloads and initiates the Cloud Manager image from Oracle Cloud Marketplace.
  • Provisions the Cloud Manager instance in Compute Classic.
  • Configures the Cloud Manager Repository to auto-download required PeopleSoft Update Images (PIs) from My Oracle Support.
  • Has access to all Cloud Manager tiles.
  • Has the ability to add Cloud PeopleSoft Administrator and Self-Service Users.
  • Can manage all environments.

The Cloud PeopleSoft Administrator:

  • Creates deployment templates based on downloaded PIs or customer environments that have been cloned to template in Compute Classic.
  • Has access to the Topology, Environment Template, Environments, and My Settings tiles.
  • Can manage all environments.

The Self-Service User:

  • Creates Compute Classic instances from available templates.
  • Starts, stops, and deletes instances.
  • Has access to the Environments and My Settings tiles.
  • Can manage only his own environments.

Viewing Cloud Manager Permission Lists and Roles

To view the delivered Cloud Manager Permission Lists:

  1. On the Cloud Manager home page, click the NavBar button at the top right, click the Navigator button, and select PeopleTools, Security, Permissions & Roles, Permission Lists from the menu.

    Accessing Navigator button and PeopleTools menu
    Description of this image
  2. Enter PACL in the Search By field, and click Search on the Permission Lists page to see the three delivered Cloud Manager Permission Lists, PACL_001, PACL_002, PACL_003.

    Cloud Manager Permission Lists page
    Description of this image

  3. Navigate to PeopleTools, Security, Permissions & Roles, Roles, enter PACL and click Search to view the delivered Cloud Manager Roles, PACL_CAD, PACL_PAD and PACL_SSC.

    Cloud Mananger Roles list
    Description of this image
  4. Select PACL_CAD from the Search Results and select the Permission Lists tab.

    The permission lists that are associated with Cloud Administrator include PACL_001, PACL_002, and PACL_003.

    Cloud Administrator Permission Lists
    Description of this image
  5. Click Next in List to view the three permission lists associated with PACL_PAD, the Cloud PeopleSoft Administrator.

    The associated permission lists include the Cloud Manager permission lists PACL_002 and PACL_003.

    Cloud PeopleSoft Administrator permission lists
    Description of this image
  6. Click Next in List to view the two permission lists associated with PACL_SSC, the Cloud Self Service User.

    The associated permission list is the Cloud Manager permission list PACL_003.

    Cloud Self Service User permission lists
    Description of this image

Adding Cloud Manager Roles to an Existing User Profile

To set up a user profile for a Cloud Manager user, the Cloud Administrator can create a new user, or begin with an existing user and add the requisite roles, as shown in this section. For details on working with PeopleSoft user profiles, see PeopleTools: Security Administration, "Working with User Profiles" in PeopleSoft Hosted Online Help.

  1. Sign in to Cloud Manager in a browser using the Cloud Administrator user ID, CLADM, and password.

  2. On the home page, select PeopleTools, Security, User Profiles, Copy User Profiles to access the User Profiles search page.

    PeopleTools, Security, User Profiles, Copy User Profiles
    Description of this image
  3. Select the User ID that you want to copy, for example PRODMGR.

  4. On the Copy User Profiles page, enter a new user ID, CLDPRODMGR in this example, a description, and the password that the new user ID should use to sign in to Cloud Manager.

    Note. This example show the Copy ID Type Information option selected. If this option is not selected, the system does not save the EMPLID in the PSOPRDEFN table.
    Click Save.

    Copy User Profiles, New User Information page
    Description of this image
  5. On the General page, supply any necessary information.

    Copy User Profile General page
    Description of this image
  6. Select the Roles tab, and click the plus sign in the User Roles table to add a new row.

    Copy User Profile Roles page
    Description of this image
  7. On the Look Up Role Name page, enter PACL in the search field, and select PACL_PAD, for the Cloud PeopleSoft Administrator.

    Look Up Role Name page
    Description of this image

    The new role appears in the User Roles table.
    Copy user Profile Roles page after addition
    Description of this image
  8. Repeat steps 6 and 7 to add other Cloud Manager roles.

Configuring the Cloud Manager Linux VM for YUM Updates

The Cloud Manager image for Oracle Cloud Infrastructure Classic is not pre-configured to use the Oracle YUM repository. If you want to install OS updates from the YUM repository on the Cloud Manager Linux VM, use these instructions to configure it.

  1. Sign in to the Linux VM as the root user.

  2. Run the following commands:

    cd /etc/yum.repos.d
    wget http://yum.oracle.com/public-yum-ol6.repo

For more information, see the Oracle Linux yum server website, http://yum.oracle.com.

Want to Learn More?