PeopleSoft Cloud Manager Image 10-HandOnLabGuide-v1.0
PeopleSoft Cloud Manager Image 10-HandOnLabGuide-v1.0
PeopleSoft Cloud Manager Image 10-HandOnLabGuide-v1.0
Image 10
Hands-On Lab Guide V1.0
March 2020
Copyright © 2020, Oracle and/or its affiliates
Confidential: Public
PURPOSE STATEMENT
This document provides an overview of features and enhancements included in
PeopleSoft Cloud Manager Image 10. It is intended solely to help you assess the
business benefits of upgrading to PeopleSoft Cloud Manager Image 10 and to plan
your I.T. projects.
DISCLAIMER
This document in any form, software or printed matter, contains proprietary
information that is the exclusive property of Oracle. Your access to and use of this
confidential material is subject to the terms and conditions of your Oracle software
license and service agreement, which has been executed and with which you agree to
comply. This document and information contained herein may not be disclosed,
copied, reproduced or distributed to anyone outside Oracle without prior written
consent of Oracle. This document is not part of your license agreement nor can it be
incorporated into any contractual agreement with Oracle or its subsidiaries or
affiliates.
This document is for informational purposes only and is intended solely to assist you
in planning for the implementation and upgrade of the product features described. It
is not a commitment to deliver any material, code, or functionality, and should not be
relied upon in making purchasing decisions. The development, release, and timing of
any features or functionality described in this document remains at the sole
discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include
all features described in this document without risking significant destabilization of
the code.
Intended Audience
Users who are familiar with Oracle Cloud Infrastructure capabilities and have an Oracle Cloud Infrastructure account.
Users who are familiar with PeopleSoft applications (not mandatory).
Users who are new to Cloud Manager or have already used Cloud Manager earlier.
It is a good idea for user to have knowledge of the Oracle Cloud Infrastructure concepts such as Availability Domain,
VCN, subnets, and ports, but it is not mandatory.
Prerequisites
The user performing the lab should have:
Oracle Cloud Infrastructure account (mandatory).
My Oracle Support credentials.
A tenancy with Administrator user access.
Tenancy home region with these resources (these are the minimum requirements):
– 4 VM shapes (VM.Standard2.2 or VM.Standard2.1, VM.StandardE2.2 or VM.StandardE2.1)
– 1 TB block storage
Microsoft Windows workstation or laptop with:
– Access to the Oracle Cloud Infrastructure Console, Cloud Manager and provisioned instances
– A web browser to connect to OCI console and Cloud Manager PIA. Firefox and Chrome are recommended.
– Git Bash for Windows installed from https://git-scm.com/download/win
2. Click the menu icon ( ) at the top left. Under Governance and Administration, select Identity, Users.
Users page
4. Enter a user name, which is psftadmin_Lab in this example, a description, and an email address (optional), and then
click Create.
5. After you create the user, select the user name from the list of users to go to the User Details page. Alternatively, select
View Details from the Related Action menu.
6. On the User Details page, copy the OCID for the user. You will use this in installing Cloud Manager.
7. In the API Keys section, click Add Public Key.
8. On the Add Public Key dialog box, select Paste Public Keys.
9. Paste the contents of the PEM public key (oci_api_key_public.pem in the .oci folder) in the field and click Add.
5. Enter the name for the newly created user, psftadmin_Lab in this document, and click Add.
7. Click Create.
8. On the details page for the policy, make sure the four policies are listed.
5.1 - Get Oracle PeopleSoft Cloud Manager 10 from Oracle Cloud Marketplace
1. Search for Oracle PeopleSoft Cloud Manager 10 in Oracle Cloud Marketplace.
3. From the drop-down list, select the OCI region that hosts your Oracle Cloud Infrastructure account, and sign in using
your Oracle Cloud Infrastructure account credentials.
4. Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager, accept the terms and
restrictions, and click Launch Stack.
– In the User OCID field, add the newly created User OCID in a single line, with no line feeds or spaces.
– Enter your SSH public key in a single line, with no line feeds or spaces. The SSH Public Key field does not expand.
– Enter the contents of your API Private Key.
Open the Outputfile.txt that you created in the section on generating keys, copy the contents fully and paste them
in the API Private Key field. Enter the contents in a single line, with no line feeds or spaces. The API Private Key field
does not expand.
– Enter the passphrase for the API Private Key, if you created one.
5. When you are happy with the network settings, click Create. This brings up a summary page for you to verify your
settings and proceed.
By default, the CM instance is created under a private subnet, which doesn’t have a public IP address. You will have to access
your instance through a jump host. The jump-host has the public IP that you can access with SSH and set up the tunnel to
reach your Cloud Manager instance. If you are interested in knowing more about the Network architecture in Oracle Cloud
Infrastructure, see Overview of Networking in the Oracle Cloud Infrastructure online help.
After this step, the actual Cloud Manager bootstrap process starts and you may have to wait for about an hour for your
Cloud Manager instance to be accessible.
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 begins running
automatically after the Apply job succeeds. To monitor the script status, see the tutorial Install the Cloud Manager Stack with
Resource Manager.
5.4 - Log in to the Cloud Manager Instance Through the Jump Host
This section uses the commands in the Output section to set up access to the private subnet.
1. In the git bash shell on your Microsoft Windows computer, run this command to set up the SSH tunnel through the
jump host to the private subnet. Substitute the values from the Outputs page
ssh –i <path to your SSH private key> -f -C -q -N -L 2222:<cm_private_ip> opc@<jumphost_public_ip>
2. In the git bash shell, run this command with the values from the Outputs page to set up the SOCKS proxy for browser
access:
ssh –i <path to your SSH private key> -D 8123 -f -C -q -N opc@<jumphost_public_ip>
3. In the Firefox browser on the same Microsoft Windows computer, select Network Settings > Preferences.
4. Select Manual proxy configuration, and enter 8123 as the port for the SOCKS host.
Make sure the settings are as shown in the example below.
5. In the same browser, enter the Cloud Manager URL from the Outputs section and sign in with the user ID CLADM and
the password for the Cloud Manager administrator that you entered when filling out the stack.
You see the Cloud Manager home page (dashboard).
Congratulations, you have successfully installed Cloud Manager in your tenancy. This concludes Part 1 of the training.
3. Select Infrastructure Settings from the menu on the left to update the Operating System Images.
4. For the Linux image, select the Marketplace Image option and choose the latest version from the displayed list.
5. For the Windows image, go to this Oracle Cloud Infrastructure web site and locate the latest image: Windows Server
2016 VM.
6. Copy the OCID for your region and paste it on the Infrastructure Settings page.
11. Click Create. This action will create a file server in a few minutes.
4. Delete the Windows node from the topology. Click Delete on the page shown below and save the topology.
Topology page
3. On the Select Topology page, click the search icon to search for a topology and select the PUM Fulltier topology.
4. Expand the Custom Attributes section, select the PUM Fulltier topology, and click Edit Custom Attributes.
Note. This is just a sample. The actual VCN and Region might vary based on your setup.
Refer to Appendix A to review tenancy service limits and find the availability domain that has the required shape
available for provisioning. In this exercise, for trial accounts, evQs:US-ASHBURN-AD-2 should have the required shapes.
Also, refer to Appendix B for network topology.
6. Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide inputs.
You have the option to change the default values for many of the parameters.
Full Tier | General Settings
4 Enable EM agent No
8 Database Operator Id PS
Note. Since there is only one subnet, the ‘envs’ subnet is automatically chosen when AD-2, PSFT_Lab compartment and
labnet VCN are chosen in the earlier section.
1 Number of Domains 1
1 Number of Domains 1
1 Number of Domains 1
1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
8. Click Next. Review the page and click Submit to save the template.
Summary page
4. Expand all the sections under Environment Attributes and provide all inputs.
Use the tables given below for quick and default values. Click Done to begin the environment provisioning process.
Full Tier | Credentials
8 Database Operator Id PS
4 Enable EM agent No
8 Database Operator Id PS
1 Number of Domains 1
1 Number of Domains 1
1 Number of Domains 1
1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
5 SQR Process 1
6 SQR Report 1
The following table shows a typical resource availability at a given point in time. Your tenancy’s resources could be different
and can have one or more of these shapes.
VM.Standard2.1 1 1 1
VM.Standard2.2 1 1 1
VM.Standard.E2.1 1 1 1
VM.Standard.E2.2 1 1 1
In this lab example, the Associated Resources show all the newly created and used resources, including the jump host, Cloud
Manager instance, and the network components.
Use the following values in filling out the Create Subnet page:
– Name — MySubnet
– Subnet Type — Availability Domain-specific
– Availability Domain — AD 3
– CIDR Block — 10.0.8.0/24
– Route Table — Default Route Table for labnet
– Subnet Access — Public Subnet
– DNS Resolution — Enable Use DNS hostnames in this SUBNET
– Security Lists — Add two security lists, the default and the cm_sec security lists. Click +Additional Security List to
add a new list.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon 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, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group. 0120