Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
CLOUD MANAGER 10 HANDS-ON LAB GUIDE V10
2
Table of Contents 1 Overview 3 2 Intended Audience 3 3 Requirements before you begin 3 4 Key generation and management 3
41 Generate API Key pairs 3 42 Generate SSH key pairs 5
Part 1 ndash Prepare your tenancy 6 5 Preparing your tenancy (Prerequisites to set up Cloud Manager) 6
51 Create User 6 52 Create User groups 8 53 Create Compartment 10 54 Create Policy for authorization 11
6 Set up Cloud Manager using the Resource Manager 13 61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace 13 62 Select the region 14 63 Choose your compartment 14 64 Create the Stack 15 65 Fill the user centric details 16 66 Network settings 17 67 Verify and create 18 68 Firefox browser settings 21
Part 2 ndash Lab exercises 23 1 Activity 1 Configure Cloud Manager 23 Windows-Server-2016-Standard-Edition-VM-B1-20200114-0 23 2 Activity 2 Subscribe to Download Subscriptions 27 3 Activity 3 Review and update a Topology 27 4 Activity 4 Create a new Environment Template 29 5 Activity 5 Create Environment 34 6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients 38 Appendix A ndash OCI Account URL and Resources 39 Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private access) 41 Appendix C ndash Network layout 41 Appendix D ndash Deployed OCI Resources 43 Appendix E ndash Provisioning Windows Instances 45 Appendix F ndash Creating a new subnet 46
3
1 Overview
This document is a guide to be used in the PeopleSoft Cloud Manager 10 hands-on lab sessions The users are provided with step-by-step instructions on setting up a user group creating and adding users create compartment and respective policies in the Oracle Cloud Infrastructure Subsequently this guide instructs how to install the Cloud Manager 10 using Oracle Resource Manager The final section provides the steps to provision a PeopleSoft Environment followed by some simple hands-on exercises for you to get familiar with the system
2 Intended Audience
Users who are familiar with Oracle Cloud Infrastructure capabilities and have an OCI account (OCI account is mandatory)
Users who are familiar with PeopleSoft applications (not mandatory)
Users who are new to Cloud Manager or have already used Cloud Manager earlier
Although a good idea of the OCI network knowledge on Availability Domain VCN Subnets and ports are desirable itrsquos not mandatory
3 Requirements before you begin
User already has a tenancy with Administrator user access
My Oracle Support credentials
Minimum resources in Home region of the tenancy
a 4 x VM shapes (VMStandard22 or VMStandard21 VMStandardE22 or
VMStandardE21)
b 1 TB block storage
User brings their own Windows workstationlaptop to access OCI console
PSFT Cloud Manager and provisioned instances
User has access to a Windows workstationlaptop with the following
installed
a Git Bash for Windows - httpsgit-scmcomdownloadwin
b A web browser to connect to OCI web console and Cloud Manager PIA ndash
Firefox or Chrome recommended
4 Key generation and management
41 Generate API Key pairs
NOTE This section elaborates on the keys required for the new user accounts you will be creating as part of the tenancy creation and Cloud Manager installation The keys you generate here will be used subsequently as the section progresses Make sure you have the followed all the steps explained
4
You can use the following OpenSSL commands to generate the key pair in the required PEM format If youre using Windows youll need to install Git Bash for Windows and run the commands with that tool
Create OCI directory using the command
Generate the private key with one of the following commands It is recommended to generate the key encrypted with a passphrase when prompted
For LINUXMAC
Note For Windows you may need to insert -passout stdin to be prompted for a passphrase The prompt will just be the blinking cursor with no text
For Windows
To generate the key with no passphrase
Ensure that only you can read the private key file
Generate the public key using the private key in the same oci directory
Run the following command on your private key to encrypt it The contents of the output file will be used while setting up the Cloud Manager using the Resource Manager
base64 ~ocioci_api_keypem | tr ndashd rngt Outputfiletxt
mkdir ~oci
openssl genrsa -out ~ocioci_api_keypem -aes128 2048
openssl genrsa -out ~ocioci_api_keypem -aes128 -passout stdin 2048
openssl genrsa -out ~ocioci_api_keypem 2048
chmod go-rwx ~ocioci_api_keypem
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem
5
For Windows if you generated the private key with a passphrase you may need to insert -passin stdin to be prompted for the passphrase The prompt will just be the blinking cursor with no text
42 Generate SSH key pairs
Open a shell or terminal for entering the commands
Type a complete ssh-keygen command Example
ssh-keygen -t rsa -N -b 2048 -C ltkey_namegt -f ltpathroot_namegt
Creating an SSH Key Pair Using PuTTY Key Generator
Find puttygenexe in the PuTTY folder on your computer for example CProgram Files
(x86)PuTTY Double-click puttygenexe to open it
Specify a key type of SSH-2 RSA and a key size of 2048 bits
In the Key menu confirm that the default value of SSH-2 RSA key is selected
For the Type of key to generate accept the default key type of RSA
Set the Number of bits in a generated key to 2048 if it is not already set
Click Generate
Move your mouse around the blank area in the PuTTY window to generate random data in the key
When the key is generated it appears under Public key for pasting into OpenSSH authorized_keys file
A Key comment is generated for you including the date and time stamp You can keep the default comment or replace it with your own more descriptive comment
Leave the Key passphrase field blank
Click Save private key and then click Yes in the prompt about saving the key without a passphrase
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem -passin stdin
6
The key pair is saved in the PuTTY Private Key (PPK) format which is a proprietary format that works only with the PuTTY tool set
You can name the key anything you want but use the ppk file extension For example mykeyppk
Select all of the generated key that appears under Public key for pasting into OpenSSH authorized_keys file copy it using Ctrl + C paste it into a text file and then save the file in the same location as the private key
(Do not use Save public key because it does not save the key in the OpenSSH format)
You can name the key anything you want but for consistency use the same name as the private key and a file extension of pub For example mykeypub
Write down the names and location of your public and private key files You will need the public key when launching an instance You will need the private key to access the instance via SSH
Part 1 ndash Prepare your tenancy
5 Preparing your tenancy (Prerequisites to set up Cloud Manager)
51 Create User i From the Identity main menu choose Users
ii Enter the username and email and click Create
7
User name psftadmin_Lab (You can copy paste this name during the exercise)
iii Associate the API public key with the user a The public key that was generated as part of the prerequisite
step needs to be associated with the newly created user b Get the users OCID in the Console on the page showing the
users details To get to that page
c Open the Profile menu ( ) and click User Settings
d If youre an administrator doing this for another user Open the navigation menu Under Governance and Administration go to Identity and click Users Select the user from the list
e View the details for the user who will be calling the API with the key pair
i If youre signed in as this user click your username in the top-right corner of the Console and then click User Settings
ii If youre an administrator doing this for another user instead click Identity click Users and then select the user from the list
f Click Add Public Key
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
2
Table of Contents 1 Overview 3 2 Intended Audience 3 3 Requirements before you begin 3 4 Key generation and management 3
41 Generate API Key pairs 3 42 Generate SSH key pairs 5
Part 1 ndash Prepare your tenancy 6 5 Preparing your tenancy (Prerequisites to set up Cloud Manager) 6
51 Create User 6 52 Create User groups 8 53 Create Compartment 10 54 Create Policy for authorization 11
6 Set up Cloud Manager using the Resource Manager 13 61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace 13 62 Select the region 14 63 Choose your compartment 14 64 Create the Stack 15 65 Fill the user centric details 16 66 Network settings 17 67 Verify and create 18 68 Firefox browser settings 21
Part 2 ndash Lab exercises 23 1 Activity 1 Configure Cloud Manager 23 Windows-Server-2016-Standard-Edition-VM-B1-20200114-0 23 2 Activity 2 Subscribe to Download Subscriptions 27 3 Activity 3 Review and update a Topology 27 4 Activity 4 Create a new Environment Template 29 5 Activity 5 Create Environment 34 6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients 38 Appendix A ndash OCI Account URL and Resources 39 Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private access) 41 Appendix C ndash Network layout 41 Appendix D ndash Deployed OCI Resources 43 Appendix E ndash Provisioning Windows Instances 45 Appendix F ndash Creating a new subnet 46
3
1 Overview
This document is a guide to be used in the PeopleSoft Cloud Manager 10 hands-on lab sessions The users are provided with step-by-step instructions on setting up a user group creating and adding users create compartment and respective policies in the Oracle Cloud Infrastructure Subsequently this guide instructs how to install the Cloud Manager 10 using Oracle Resource Manager The final section provides the steps to provision a PeopleSoft Environment followed by some simple hands-on exercises for you to get familiar with the system
2 Intended Audience
Users who are familiar with Oracle Cloud Infrastructure capabilities and have an OCI account (OCI account is mandatory)
Users who are familiar with PeopleSoft applications (not mandatory)
Users who are new to Cloud Manager or have already used Cloud Manager earlier
Although a good idea of the OCI network knowledge on Availability Domain VCN Subnets and ports are desirable itrsquos not mandatory
3 Requirements before you begin
User already has a tenancy with Administrator user access
My Oracle Support credentials
Minimum resources in Home region of the tenancy
a 4 x VM shapes (VMStandard22 or VMStandard21 VMStandardE22 or
VMStandardE21)
b 1 TB block storage
User brings their own Windows workstationlaptop to access OCI console
PSFT Cloud Manager and provisioned instances
User has access to a Windows workstationlaptop with the following
installed
a Git Bash for Windows - httpsgit-scmcomdownloadwin
b A web browser to connect to OCI web console and Cloud Manager PIA ndash
Firefox or Chrome recommended
4 Key generation and management
41 Generate API Key pairs
NOTE This section elaborates on the keys required for the new user accounts you will be creating as part of the tenancy creation and Cloud Manager installation The keys you generate here will be used subsequently as the section progresses Make sure you have the followed all the steps explained
4
You can use the following OpenSSL commands to generate the key pair in the required PEM format If youre using Windows youll need to install Git Bash for Windows and run the commands with that tool
Create OCI directory using the command
Generate the private key with one of the following commands It is recommended to generate the key encrypted with a passphrase when prompted
For LINUXMAC
Note For Windows you may need to insert -passout stdin to be prompted for a passphrase The prompt will just be the blinking cursor with no text
For Windows
To generate the key with no passphrase
Ensure that only you can read the private key file
Generate the public key using the private key in the same oci directory
Run the following command on your private key to encrypt it The contents of the output file will be used while setting up the Cloud Manager using the Resource Manager
base64 ~ocioci_api_keypem | tr ndashd rngt Outputfiletxt
mkdir ~oci
openssl genrsa -out ~ocioci_api_keypem -aes128 2048
openssl genrsa -out ~ocioci_api_keypem -aes128 -passout stdin 2048
openssl genrsa -out ~ocioci_api_keypem 2048
chmod go-rwx ~ocioci_api_keypem
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem
5
For Windows if you generated the private key with a passphrase you may need to insert -passin stdin to be prompted for the passphrase The prompt will just be the blinking cursor with no text
42 Generate SSH key pairs
Open a shell or terminal for entering the commands
Type a complete ssh-keygen command Example
ssh-keygen -t rsa -N -b 2048 -C ltkey_namegt -f ltpathroot_namegt
Creating an SSH Key Pair Using PuTTY Key Generator
Find puttygenexe in the PuTTY folder on your computer for example CProgram Files
(x86)PuTTY Double-click puttygenexe to open it
Specify a key type of SSH-2 RSA and a key size of 2048 bits
In the Key menu confirm that the default value of SSH-2 RSA key is selected
For the Type of key to generate accept the default key type of RSA
Set the Number of bits in a generated key to 2048 if it is not already set
Click Generate
Move your mouse around the blank area in the PuTTY window to generate random data in the key
When the key is generated it appears under Public key for pasting into OpenSSH authorized_keys file
A Key comment is generated for you including the date and time stamp You can keep the default comment or replace it with your own more descriptive comment
Leave the Key passphrase field blank
Click Save private key and then click Yes in the prompt about saving the key without a passphrase
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem -passin stdin
6
The key pair is saved in the PuTTY Private Key (PPK) format which is a proprietary format that works only with the PuTTY tool set
You can name the key anything you want but use the ppk file extension For example mykeyppk
Select all of the generated key that appears under Public key for pasting into OpenSSH authorized_keys file copy it using Ctrl + C paste it into a text file and then save the file in the same location as the private key
(Do not use Save public key because it does not save the key in the OpenSSH format)
You can name the key anything you want but for consistency use the same name as the private key and a file extension of pub For example mykeypub
Write down the names and location of your public and private key files You will need the public key when launching an instance You will need the private key to access the instance via SSH
Part 1 ndash Prepare your tenancy
5 Preparing your tenancy (Prerequisites to set up Cloud Manager)
51 Create User i From the Identity main menu choose Users
ii Enter the username and email and click Create
7
User name psftadmin_Lab (You can copy paste this name during the exercise)
iii Associate the API public key with the user a The public key that was generated as part of the prerequisite
step needs to be associated with the newly created user b Get the users OCID in the Console on the page showing the
users details To get to that page
c Open the Profile menu ( ) and click User Settings
d If youre an administrator doing this for another user Open the navigation menu Under Governance and Administration go to Identity and click Users Select the user from the list
e View the details for the user who will be calling the API with the key pair
i If youre signed in as this user click your username in the top-right corner of the Console and then click User Settings
ii If youre an administrator doing this for another user instead click Identity click Users and then select the user from the list
f Click Add Public Key
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
3
1 Overview
This document is a guide to be used in the PeopleSoft Cloud Manager 10 hands-on lab sessions The users are provided with step-by-step instructions on setting up a user group creating and adding users create compartment and respective policies in the Oracle Cloud Infrastructure Subsequently this guide instructs how to install the Cloud Manager 10 using Oracle Resource Manager The final section provides the steps to provision a PeopleSoft Environment followed by some simple hands-on exercises for you to get familiar with the system
2 Intended Audience
Users who are familiar with Oracle Cloud Infrastructure capabilities and have an OCI account (OCI account is mandatory)
Users who are familiar with PeopleSoft applications (not mandatory)
Users who are new to Cloud Manager or have already used Cloud Manager earlier
Although a good idea of the OCI network knowledge on Availability Domain VCN Subnets and ports are desirable itrsquos not mandatory
3 Requirements before you begin
User already has a tenancy with Administrator user access
My Oracle Support credentials
Minimum resources in Home region of the tenancy
a 4 x VM shapes (VMStandard22 or VMStandard21 VMStandardE22 or
VMStandardE21)
b 1 TB block storage
User brings their own Windows workstationlaptop to access OCI console
PSFT Cloud Manager and provisioned instances
User has access to a Windows workstationlaptop with the following
installed
a Git Bash for Windows - httpsgit-scmcomdownloadwin
b A web browser to connect to OCI web console and Cloud Manager PIA ndash
Firefox or Chrome recommended
4 Key generation and management
41 Generate API Key pairs
NOTE This section elaborates on the keys required for the new user accounts you will be creating as part of the tenancy creation and Cloud Manager installation The keys you generate here will be used subsequently as the section progresses Make sure you have the followed all the steps explained
4
You can use the following OpenSSL commands to generate the key pair in the required PEM format If youre using Windows youll need to install Git Bash for Windows and run the commands with that tool
Create OCI directory using the command
Generate the private key with one of the following commands It is recommended to generate the key encrypted with a passphrase when prompted
For LINUXMAC
Note For Windows you may need to insert -passout stdin to be prompted for a passphrase The prompt will just be the blinking cursor with no text
For Windows
To generate the key with no passphrase
Ensure that only you can read the private key file
Generate the public key using the private key in the same oci directory
Run the following command on your private key to encrypt it The contents of the output file will be used while setting up the Cloud Manager using the Resource Manager
base64 ~ocioci_api_keypem | tr ndashd rngt Outputfiletxt
mkdir ~oci
openssl genrsa -out ~ocioci_api_keypem -aes128 2048
openssl genrsa -out ~ocioci_api_keypem -aes128 -passout stdin 2048
openssl genrsa -out ~ocioci_api_keypem 2048
chmod go-rwx ~ocioci_api_keypem
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem
5
For Windows if you generated the private key with a passphrase you may need to insert -passin stdin to be prompted for the passphrase The prompt will just be the blinking cursor with no text
42 Generate SSH key pairs
Open a shell or terminal for entering the commands
Type a complete ssh-keygen command Example
ssh-keygen -t rsa -N -b 2048 -C ltkey_namegt -f ltpathroot_namegt
Creating an SSH Key Pair Using PuTTY Key Generator
Find puttygenexe in the PuTTY folder on your computer for example CProgram Files
(x86)PuTTY Double-click puttygenexe to open it
Specify a key type of SSH-2 RSA and a key size of 2048 bits
In the Key menu confirm that the default value of SSH-2 RSA key is selected
For the Type of key to generate accept the default key type of RSA
Set the Number of bits in a generated key to 2048 if it is not already set
Click Generate
Move your mouse around the blank area in the PuTTY window to generate random data in the key
When the key is generated it appears under Public key for pasting into OpenSSH authorized_keys file
A Key comment is generated for you including the date and time stamp You can keep the default comment or replace it with your own more descriptive comment
Leave the Key passphrase field blank
Click Save private key and then click Yes in the prompt about saving the key without a passphrase
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem -passin stdin
6
The key pair is saved in the PuTTY Private Key (PPK) format which is a proprietary format that works only with the PuTTY tool set
You can name the key anything you want but use the ppk file extension For example mykeyppk
Select all of the generated key that appears under Public key for pasting into OpenSSH authorized_keys file copy it using Ctrl + C paste it into a text file and then save the file in the same location as the private key
(Do not use Save public key because it does not save the key in the OpenSSH format)
You can name the key anything you want but for consistency use the same name as the private key and a file extension of pub For example mykeypub
Write down the names and location of your public and private key files You will need the public key when launching an instance You will need the private key to access the instance via SSH
Part 1 ndash Prepare your tenancy
5 Preparing your tenancy (Prerequisites to set up Cloud Manager)
51 Create User i From the Identity main menu choose Users
ii Enter the username and email and click Create
7
User name psftadmin_Lab (You can copy paste this name during the exercise)
iii Associate the API public key with the user a The public key that was generated as part of the prerequisite
step needs to be associated with the newly created user b Get the users OCID in the Console on the page showing the
users details To get to that page
c Open the Profile menu ( ) and click User Settings
d If youre an administrator doing this for another user Open the navigation menu Under Governance and Administration go to Identity and click Users Select the user from the list
e View the details for the user who will be calling the API with the key pair
i If youre signed in as this user click your username in the top-right corner of the Console and then click User Settings
ii If youre an administrator doing this for another user instead click Identity click Users and then select the user from the list
f Click Add Public Key
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
4
You can use the following OpenSSL commands to generate the key pair in the required PEM format If youre using Windows youll need to install Git Bash for Windows and run the commands with that tool
Create OCI directory using the command
Generate the private key with one of the following commands It is recommended to generate the key encrypted with a passphrase when prompted
For LINUXMAC
Note For Windows you may need to insert -passout stdin to be prompted for a passphrase The prompt will just be the blinking cursor with no text
For Windows
To generate the key with no passphrase
Ensure that only you can read the private key file
Generate the public key using the private key in the same oci directory
Run the following command on your private key to encrypt it The contents of the output file will be used while setting up the Cloud Manager using the Resource Manager
base64 ~ocioci_api_keypem | tr ndashd rngt Outputfiletxt
mkdir ~oci
openssl genrsa -out ~ocioci_api_keypem -aes128 2048
openssl genrsa -out ~ocioci_api_keypem -aes128 -passout stdin 2048
openssl genrsa -out ~ocioci_api_keypem 2048
chmod go-rwx ~ocioci_api_keypem
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem
5
For Windows if you generated the private key with a passphrase you may need to insert -passin stdin to be prompted for the passphrase The prompt will just be the blinking cursor with no text
42 Generate SSH key pairs
Open a shell or terminal for entering the commands
Type a complete ssh-keygen command Example
ssh-keygen -t rsa -N -b 2048 -C ltkey_namegt -f ltpathroot_namegt
Creating an SSH Key Pair Using PuTTY Key Generator
Find puttygenexe in the PuTTY folder on your computer for example CProgram Files
(x86)PuTTY Double-click puttygenexe to open it
Specify a key type of SSH-2 RSA and a key size of 2048 bits
In the Key menu confirm that the default value of SSH-2 RSA key is selected
For the Type of key to generate accept the default key type of RSA
Set the Number of bits in a generated key to 2048 if it is not already set
Click Generate
Move your mouse around the blank area in the PuTTY window to generate random data in the key
When the key is generated it appears under Public key for pasting into OpenSSH authorized_keys file
A Key comment is generated for you including the date and time stamp You can keep the default comment or replace it with your own more descriptive comment
Leave the Key passphrase field blank
Click Save private key and then click Yes in the prompt about saving the key without a passphrase
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem -passin stdin
6
The key pair is saved in the PuTTY Private Key (PPK) format which is a proprietary format that works only with the PuTTY tool set
You can name the key anything you want but use the ppk file extension For example mykeyppk
Select all of the generated key that appears under Public key for pasting into OpenSSH authorized_keys file copy it using Ctrl + C paste it into a text file and then save the file in the same location as the private key
(Do not use Save public key because it does not save the key in the OpenSSH format)
You can name the key anything you want but for consistency use the same name as the private key and a file extension of pub For example mykeypub
Write down the names and location of your public and private key files You will need the public key when launching an instance You will need the private key to access the instance via SSH
Part 1 ndash Prepare your tenancy
5 Preparing your tenancy (Prerequisites to set up Cloud Manager)
51 Create User i From the Identity main menu choose Users
ii Enter the username and email and click Create
7
User name psftadmin_Lab (You can copy paste this name during the exercise)
iii Associate the API public key with the user a The public key that was generated as part of the prerequisite
step needs to be associated with the newly created user b Get the users OCID in the Console on the page showing the
users details To get to that page
c Open the Profile menu ( ) and click User Settings
d If youre an administrator doing this for another user Open the navigation menu Under Governance and Administration go to Identity and click Users Select the user from the list
e View the details for the user who will be calling the API with the key pair
i If youre signed in as this user click your username in the top-right corner of the Console and then click User Settings
ii If youre an administrator doing this for another user instead click Identity click Users and then select the user from the list
f Click Add Public Key
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
5
For Windows if you generated the private key with a passphrase you may need to insert -passin stdin to be prompted for the passphrase The prompt will just be the blinking cursor with no text
42 Generate SSH key pairs
Open a shell or terminal for entering the commands
Type a complete ssh-keygen command Example
ssh-keygen -t rsa -N -b 2048 -C ltkey_namegt -f ltpathroot_namegt
Creating an SSH Key Pair Using PuTTY Key Generator
Find puttygenexe in the PuTTY folder on your computer for example CProgram Files
(x86)PuTTY Double-click puttygenexe to open it
Specify a key type of SSH-2 RSA and a key size of 2048 bits
In the Key menu confirm that the default value of SSH-2 RSA key is selected
For the Type of key to generate accept the default key type of RSA
Set the Number of bits in a generated key to 2048 if it is not already set
Click Generate
Move your mouse around the blank area in the PuTTY window to generate random data in the key
When the key is generated it appears under Public key for pasting into OpenSSH authorized_keys file
A Key comment is generated for you including the date and time stamp You can keep the default comment or replace it with your own more descriptive comment
Leave the Key passphrase field blank
Click Save private key and then click Yes in the prompt about saving the key without a passphrase
openssl rsa -pubout -in ~ocioci_api_keypem -out ~ocioci_api_key_publicpem -passin stdin
6
The key pair is saved in the PuTTY Private Key (PPK) format which is a proprietary format that works only with the PuTTY tool set
You can name the key anything you want but use the ppk file extension For example mykeyppk
Select all of the generated key that appears under Public key for pasting into OpenSSH authorized_keys file copy it using Ctrl + C paste it into a text file and then save the file in the same location as the private key
(Do not use Save public key because it does not save the key in the OpenSSH format)
You can name the key anything you want but for consistency use the same name as the private key and a file extension of pub For example mykeypub
Write down the names and location of your public and private key files You will need the public key when launching an instance You will need the private key to access the instance via SSH
Part 1 ndash Prepare your tenancy
5 Preparing your tenancy (Prerequisites to set up Cloud Manager)
51 Create User i From the Identity main menu choose Users
ii Enter the username and email and click Create
7
User name psftadmin_Lab (You can copy paste this name during the exercise)
iii Associate the API public key with the user a The public key that was generated as part of the prerequisite
step needs to be associated with the newly created user b Get the users OCID in the Console on the page showing the
users details To get to that page
c Open the Profile menu ( ) and click User Settings
d If youre an administrator doing this for another user Open the navigation menu Under Governance and Administration go to Identity and click Users Select the user from the list
e View the details for the user who will be calling the API with the key pair
i If youre signed in as this user click your username in the top-right corner of the Console and then click User Settings
ii If youre an administrator doing this for another user instead click Identity click Users and then select the user from the list
f Click Add Public Key
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
6
The key pair is saved in the PuTTY Private Key (PPK) format which is a proprietary format that works only with the PuTTY tool set
You can name the key anything you want but use the ppk file extension For example mykeyppk
Select all of the generated key that appears under Public key for pasting into OpenSSH authorized_keys file copy it using Ctrl + C paste it into a text file and then save the file in the same location as the private key
(Do not use Save public key because it does not save the key in the OpenSSH format)
You can name the key anything you want but for consistency use the same name as the private key and a file extension of pub For example mykeypub
Write down the names and location of your public and private key files You will need the public key when launching an instance You will need the private key to access the instance via SSH
Part 1 ndash Prepare your tenancy
5 Preparing your tenancy (Prerequisites to set up Cloud Manager)
51 Create User i From the Identity main menu choose Users
ii Enter the username and email and click Create
7
User name psftadmin_Lab (You can copy paste this name during the exercise)
iii Associate the API public key with the user a The public key that was generated as part of the prerequisite
step needs to be associated with the newly created user b Get the users OCID in the Console on the page showing the
users details To get to that page
c Open the Profile menu ( ) and click User Settings
d If youre an administrator doing this for another user Open the navigation menu Under Governance and Administration go to Identity and click Users Select the user from the list
e View the details for the user who will be calling the API with the key pair
i If youre signed in as this user click your username in the top-right corner of the Console and then click User Settings
ii If youre an administrator doing this for another user instead click Identity click Users and then select the user from the list
f Click Add Public Key
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
7
User name psftadmin_Lab (You can copy paste this name during the exercise)
iii Associate the API public key with the user a The public key that was generated as part of the prerequisite
step needs to be associated with the newly created user b Get the users OCID in the Console on the page showing the
users details To get to that page
c Open the Profile menu ( ) and click User Settings
d If youre an administrator doing this for another user Open the navigation menu Under Governance and Administration go to Identity and click Users Select the user from the list
e View the details for the user who will be calling the API with the key pair
i If youre signed in as this user click your username in the top-right corner of the Console and then click User Settings
ii If youre an administrator doing this for another user instead click Identity click Users and then select the user from the list
f Click Add Public Key
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
8
g Paste the contents of the PEM public key (oci_api_key_publicpem in the oci folder) in the dialog box and click Add
52 Create User groups i From the OCI page click the hamburger menu on the top left select
Groups from the Identity menu
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
9
ii Click on Create Group
iii Give a new name to the group and click on Create
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
10
Group name CMadmins_Lab (You can copy paste this name during the exercise) iv Once the group is created Add the newly created user in the group
53 Create Compartment i From the Identity menu choose the Compartment
ii Create a new compartment
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
11
Compartment name PSFT_Lab (You can copy paste this name during the exercise)
54 Create Policy for authorization i From the Identity menu choose Policies and Add a new policy in the
root compartment ii Enter the policy statements as shown and click Create
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
12
Copy and paste these policy statements one by one (click the + button to add a new row)
Allow group CMadmins_Lab to manage all-resources in compartment PSFT_Lab
Allow group CMadmins_Lab to read all-resources in tenancy
Allow group CMadmins_Lab to manage App-catalog-listing in tenancy
iii Make sure that the 3 statements reflect on the policy created
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
13
6 Set up Cloud Manager using the Resource Manager Make sure the prerequisites are completed before you start with these steps
61 Get the Oracle PeopleSoft Cloud Manager 10 from Oracle Marketplace Search for Cloud Manager 10 and click the Get App button
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
14
62 Select the region From the dropdown select your OCI region where the infrastructure
account is hosted and sign in using OCI credentials
63 Choose your compartment
Choose the compartment (PSFT_Lab in this case) where you want to install the Cloud Manager and click on Launch Stack button once you have accepted the terms and restrictions
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
15
64 Create the Stack From here on the Resource Manager page will guide you to configure apply the network settings and create the Cloud Manager instance
Before you do this step please make sure you have the appropriate infrastructure resources available in your tenancy
o Fill the form and click Next o The Tag Namespace is optional You can leave it as is and click Next
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
16
65 Fill the user centric details
Note 1 You need to add the newly created User OCID in the field above
Note 2 Enter your User OCID in a single line with no line feeds or spaces
Few points to keep in mind while copying the keys
1 Enter your SSH public key in a single line with no line feeds or spaces The SSH Public
Key field does not expand
2 Enter the contents of your API Private Key in a single line with no line feeds or spaces
Note The API Private Key field does not expand
Open the Outputfile that was created in the perquisite step and copy the contents fully
and paste it in the API private key field in the above screen
3 Enter the passphrase for the API Private Key if you created one
Enter a passphrase containing alphanumeric characters and the following special
characters ~^-_=+[]
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
17
The password fields have validations in place and helps you adhere to the required specifications while creating them
66 Network settings This is where all the required network settings are taken care by the tool itself It is recommended to use the defaults in this page unless you want to
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
18
have complete control of your network Use the advanced network setting option in case you want to change ports subnets and others
67 Verify and create We are almost there in creating the instance Once you are happy with the network settings click on create This will evoke a summary page for you to verify your settings and proceed
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
19
Immediately you will see that the Resource Manager triggers the instance creation in the OCI and the logs are generated
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
20
Ideally you should not see any errors pertaining to resource availability (VMs stack space) In case you see such errors not to worry Just go back to the Create Instance page (Step 6) and edit your settings and choose the resources appropriately The Output section displays the URLs of the Cloud Manager instance with their private IP jump host details ports and the necessary tunnelsocks_proxy commands
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
21
The CM URL has the following structure http psftcm cm psftcm oraclevcncom 8000
By default the CM instance is created under a private Subnet which doesnrsquot have a public IP You will have to access your instance via a jump host The jump-host the public IP to which you can SSH and set up the tunnel to reach your CM instance If you are interested to know more about the Network architecture of the OCI please read this link After this step the actual Cloud Manager bootstrap process starts and you might probably have to wait for about an hour for your Cloud Manager instance to be accessible Step 9 Login to the Cloud Manager instance Use a browser of your choice to login to the Cloud Manager (Use the username and password you had set during the variable settings step (Step 6) Before you open up the browser make sure you have run the following commands in your terminal
ssh ndashi ltpath to your private keygt -D 8123 -f -C -q -N opcltyour cloud manager ipgt
ssh ndashi ltpath to your private keygt -f -C -q -N -L 2222ltcm private ipgt opcltyour cloud manager ipgt
68 Firefox browser settings
Select Preferences from the browser-gt Network settings
Make sure the settings are done as shown in the screen below
Protocol Application Subnet VCN Domain
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
22
Enter the Cloud Manger URL in the browser and login using the credentials (CLADMCLADM)
Congratulations you have successfully installed Cloud Manager in your tenancy now End of part 1 of the training
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
23
Part 2 ndash Lab exercises
1 Activity 1 Configure Cloud Manager Time 20 mins Overview of the activity You will configure the newly set up Cloud Manager This will include setting up repositories install Linux and Windows images set up file server mounts 1 Navigate to Cloud Manager Dashboard -gt Cloud Manager Settings -gt Cloud Manager
Settings
2 Update My Oracle Support (MOS) Credentials This is required to download DPKs and
PRPs automatically
3 Navigate to Infrastructure Settings and update Operating System Images For Linux
enable ldquoMarketplace Imagerdquo radio button
and choose the latest version from the displayed list For Windows image use the value corresponding to your region
Windows-Server-2016-Standard-Edition-VM-B1-20200114-0
Image Family Windows Server 2016 VM
Operating System Windows Release Date Jan 29 2020
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
24
Region OCID
ap-melbourne-1
ocid1imageoc1ap-melbourne-1aaaaaaaaes63dvlxxlsds4ifme4pdoji5qwvemiqib5mj4nmxl35swxp5eza
ap-mumbai-1
ocid1imageoc1ap-mumbai-1aaaaaaaaxot55f3jmsqkjqi4nenqee5kq2paw4k2xjidfanzdtyswdmzc6vq
ap-osaka-1 ocid1imageoc1ap-osaka-1aaaaaaaaqpv3jdlt7kcqj4re5us2zzmamomt4ky35r2nvhwaloxrxfkkzrrq
ap-seoul-1 ocid1imageoc1ap-seoul-1aaaaaaaaale2grvhk636igyoocp5dhsjgcz7ir2jqirhgnz7i6zsf2glucvq
ap-sydney-1
ocid1imageoc1ap-sydney-1aaaaaaaaajjh2h74ujnawnhvhrlv4x3ec6iwub3u5656bjvs3k44yts6wgwq
ap-tokyo-1 ocid1imageoc1ap-tokyo-1aaaaaaaam53ydb34n6mp2iz7heiiwiwk5xzvhdjoh7odvy54pvufszfyueqq
ca-toronto-1
ocid1imageoc1ca-toronto-1aaaaaaaahxfk3p4casmz3jbrufdfw4jinjxa3xoktdvljo6wfcnqddiv52xa
eu-amsterdam-1
ocid1imageoc1eu-amsterdam-1aaaaaaaakcq6k3acovgjzxdrbwudrhnzxor2heudc5hzqsa7cb6cdn34n5qq
eu-frankfurt-1
ocid1imageoc1eu-frankfurt-1aaaaaaaaprvx7aug42s6cskbjmtk2hw67qjbjcluv2gor5men7e3m7kxenwq
eu-zurich-1 ocid1imageoc1eu-zurich-1aaaaaaaaantcxidrgdrpk3fipkkwarqxhuksjdrzgjvstsyw4ms6pz5qiexq
me-jeddah-1
ocid1imageoc1me-jeddah-1aaaaaaaavdvizvakkeabjwbzeejmr4ze6kfz6lcxwgrc5razbdoccdulbviq
sa-saopaulo-1
ocid1imageoc1sa-saopaulo-1aaaaaaaa7u53ptyfh7z3gmljeossit65aulb7pt3jfmqi55j6nqkevfjssta
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
25
4 Click lsquoSaversquo to save the configuration
5 Click lsquoRefresh OCI Metadatarsquo button on top of the page and wait for few minutes
6 Next navigate to File Server tab Accept the defaults For Mount Target type ldquolabrdquo
uk-gov-london-1
ocid1imageoc4uk-gov-london-1aaaaaaaazifauxbneg5kp2ve46szf5l4dgohkm7ou7en55uexnlsfx7fsleq
uk-london-1 ocid1imageoc1uk-london-1aaaaaaaaddwevlcplwfa5fdwrc2n63flipwudjkarnrqkls4mzy3wldyh7qa
us-ashburn-1
ocid1imageoc1iadaaaaaaaau64jafetdp3ccdzvycvjy3owlh6evxiaheiumbnhlyw6e5knkaiq
us-langley-1 ocid1imageoc2us-langley-1aaaaaaaakxvkcelnls47jo2murg5embl7d4hezifwzaw25apabtae3glxoeq
us-luke-1 ocid1imageoc2us-luke-1aaaaaaaaaijpiovyp6qo2nwa5sbvazo4x2kho2hovzdncze54235uxxv5mta
us-phoenix-1
ocid1imageoc1phxaaaaaaaaahvlltilsjyszj4egmwc2uswey2xnm5cidhcn6uw6nrcwfzftgwq
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
26
7 Click Create This action will create a file server in a few minutes
8 Wait until the file server status shows lsquoFSS Configuredrsquo and then the system is ready for
downloads
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
27
2 Activity 2 Subscribe to Download Subscriptions
Time Approximately 60 mins depending on the network speed and number of subscriptions Overview of the activity ndash You will subscribe to download channels within the Cloud Manager This will help you automatically updateupgrade tools and other software releases from the Cloud Manager
1 Navigate to Cloud Manager Dashboard Repository Download Subscriptions
2 Go to the Unsubscribed tab
3 On a download channel of your choice click on related actions menu and choose
Subscribe For example you can subscribe to the HCM_92_Linux image as shown
4 Monitor the Logs page to check for progress
5 Once a product release is successfully subscribed you can view them in the Subscribed
tab
3 Activity 3 Review and update a Topology Time 10 mins Overview of the activity ndash Create a new Topology using the Cloud Manager The topology provides the blue print of the environment you want to provision The topology is a very convenient way to create different shapestiers for your test production or staging environment
1 Navigate to Dashboard -gt Topology -gt PUM Fulltier topology This topology will be used
to create a new environment
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
28
2 Review the nodes and update the Shapes Click Full Tier node and select a shape that is
available in your availability domain (This is where your CM is installed Refer part 1 of
the training document) Select VMStandard21 or VMStandard22 Review the available
shapes in your AD as explained in Appendix A
3 Delete the Windows node from the topology Click lsquoDeletersquo on the page shown below
and save the topology
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
29
4 When you are ready Click Save The topology should now look as shown below
4 Activity 4 Create a new Environment Template
Time 10 mins Overview of the activity ndash You will create a new environment template using the Cloud Manager The template is again a convenient way to create different instances based on your need for production test and stage scenarios
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
30
1 Navigate to Dashboard -gt Environment Template
2 Click Add New Template button Provide the below details and click Next
Name MYPUM
Description Test a PUM image
Database Click on Search icon and select a downloaded DPK For example PEOPLESOFT HCM UPDATE IMAGE 92030 - NATIVE OS
3 On Select Topology page click on search icon to search for a topology and select the
PUM Fulltier topology
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
31
4 Expand the Custom Attributes and select the PUM Fulltier topology and click Edit
Custom Attributes
5 Expand the Region and Availability Domains section Select the Region and Availability
Domain in which Cloud Manager instance is not deployed Refer Appendix A to review
tenancy service limits and find the AD which has the required shape available for
provisioning In this exercise for trial accounts AD 2 should have the required shapes
Also refer to Appendix C for network topology
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
32
Regional and Availability Domains
1 Region us-ashburn-1
2 Primary Availability Domain evQsUS-ASHBURN-AD-2 (Select an AD 2 where shapes are available for use)
3 Compartment PSFT_Lab
4 Virtual Cloud Network Labnet
Note This is just a sample The actual VCN and Region might vary based on your set up
6 Expand each of the sub-sections under Full Tier and PeopleSoft Client and provide
inputs The defaults for many parameters can be changed optionally
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
13 Post Provision Custom Script -
Full Tier | Subnet Settings 1 Subnet For Primary Instance Select a subnet Eg envs
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
33
Note ndash Since there is only one subnet the lsquoenvsrsquo subnet is automatically chosen when AD2 PSFT_Lab compartment and labnet VCN is chosen in the earlier section Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings 1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings 1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
7 Click Next to configure zone and role Select options as shown below
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
34
8 Click Next Review the page and click Submit to save the template
5 Activity 5 Create Environment
Time 50 mins Overview of the activity ndash You will create an environment using the template you have just created The environment is the actual working instance of the PeopleSoft environment you want to provision 1 Navigate to Dashboard -gt Environments and Click Create Environment button
2 Provide a unique environment name Select the Template that was created in previous
section ndash MYPUM Expand all sections under Environment Attributes and provide all
inputs Use the table given below for quick and default values Click Done to begin the
environment provisioning process
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
35
Monitor the deployment logs under Dashboard | Environments | ltEnvironmentgt | Action Menu | Details | Logs
Full Tier | Credentials
Name Value 1 Database Connect Id people
2 Database Connect Password Password1234
3 Weblogic Administrator Username system
4 Weblogic Administrator Password Password1234
5 Database Administrator Password Password1234
6 Gateway Administrator Username administrator
7 Gateway Administrator Password Password1234
8 Database Operator Id PS
9 Database Operator Password PS
10 Web Profile Password for user PTWEBSERVER Password1234
11 Database Access Id SYSADM
12 Database Access Password Password1234
Full Tier | General Settings 1 PeopleSoft Deployment Path u01apporacleproduct
2 Database Access Id SYSADM
3 Database Connect Id people
4 Enable EM agent No
5 Weblogic Administrator Username system
6 Database Name MYPUM
7 Gateway Administrator Username administrator
8 Database Operator Id PS
9 Database Server Port 1522
10 Database Type SYS
11 Enable Multi Language NO
12 Pre Provision Custom Script -
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
36
13 Post Provision Custom Script -
Full Tier | Domain Settings | Web Server Settings 1 Number of Domains 1
2 Authentication Domain default
3 HTTP PIA Port 8000
4 HTTPS PIA Port 8443
Full Tier | Domain Settings | Appserver Settings
1 Number of Domains 1
2 Number of App Server Instance (PSAPPSRV services) Per Domain 2
3 Number of Query Server Instances(PSQRYSRV services) Per Domain 1
4 Number of SQL Access App Server(PSSAMSRV services) Per Domain 1
5 Number of Jolt Listener(Jolt Handler) Per Domain 3
6 Jolt Port 9033
7 WSL Port 7000
8 Enable IB settings on first domain YES
9 Number of App Server instance(PSAPPSRV services) for IB 2
10 Number of SQL Access App Server(PSSAMSRV services) for IB 1
11 Number of PSBRKHND instances for IB 1
12 Number of PSSUBHND instances for IB 1
13 Number of PSPUBHND instances for IB 1
Full Tier | Domain Settings | Process Scheduler Settings
1 Number of Domains 1
2 Number of App Engine Server Instances(PSAESRV services) Per Domain 2
3 Number of App Engine Server Instances(PSDSTSRV services) Per Domain 2
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
37
Full Tier | Domain Settings | Process Scheduler Server Definition Parameters 1 Application Engine 1
2 XML Publisher 1
3 COBOL SQL 1
4 Optimization Engine 1
5 SQR Process 1
6 SQR Report 1
7 Max Api Aware 1
Full Tier | Domain Settings | Advanced None
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
38
6 Activity 6 Additional Exercise ndash Provision Environments with Windows Clients
As a take home exercise you can provision a PeopleSoft environment with a Windows client node Follow the high-level steps outlined below
1 Remove the PUM topology from the Environment Template that was used to
provision in the previous section ndash Refer step 2 in Create a New Environment
Template
2 Edit the PUM topology and add a new Windows Client node Select an available
shape Refer step 1in Review and Update a Topology Hint - Click + to add a node
3 Edit the Environment Template and re-add the PUM topology ndash Refer step 2 in
Create a New Environment Template Hint - Search for PUM topology
4 Configure the Custom Attributes of the topology in the template Ensure to select
the Availability Domain which has the required shapes ndash Refer Step 3 in Create a
New Environment Template
5 Create a new Environment using the newly modified template ndash Refer Create
Environment
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
39
Appendix A ndash OCI Account URL and Resources
The OCI Console URL will be as shown in the screenshot below In this example the account name provided during account creation is lsquonkpsftcloudrsquo and hence the URL will be httpsmyservices-nkpsftcloudconsoleoraclecloudcom
Review the resources available in your tenancy Navigate to Menu Administration Tenancy Details and review the service limits for Compute Determine the number of VM shapes available in your tenancy
The following table shows a typical resource availability at a given point in time Your tenancyrsquos resource could be different and can have one or more of these shapes
Shape AD-1 AD-2 AD-3
VMStandard21 1 1 1
VMStandard22 1 1 1
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
40
VMStandardE21 1 1 1
VMStandardE22 1 1 1
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
41
Appendix B ndash Accessing Cloud Manager using SSH (remove ndash we will add private
access) Steps to SSH into Cloud Manager instance 1 SSH key pair required to access Cloud Manager instance was created in step 6 in section
6
2 The SSH key pair will be under the folder named lsquokeysrsquo in the same folder where the
psftcm-setupzip was extracted
3 Launch Git Bash and navigate to the keys folder
4 Retrieve the Cloud Manager IP address It was provided as output when the stack was
applied
5 SSH into the Cloud Manager instance using below command
$ ssh -i id_rsa opc129213145213
Appendix C ndash Network layout
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
42
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
43
Appendix D ndash Deployed OCI Resources
The deployment automation (Resource Manager Stack) provisions numerous resources in the tenancy To find the list of resources that were created navigate to OCI console Resource Manager Stacks ltStackgt Apply Job details On this page click Associated Resources under Resources
In this lab example the Associated Resources show all the newly created and used resources
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
44
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
45
Appendix E ndash Provisioning Windows Instances
In this lab exercise Windows node was removed from the topology to keep the provisioning process short and simple If you want to provision Windows instances as part of an environment at a later point in time you can do so easily
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
46
Appendix F ndash Creating a new subnet
1 Navigate to Menu Networking Virtual Cloud Networks Set the Compartment to
lsquoPSFT_Labrsquo Click on the existing VCN ldquolabnetrdquo
2 Click on Create Subnet button to add a new subnet Use default route table and default
DHCP options Use 1008024 as the CIDR for subnet
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
47
Attribute Value
Name MySubnet
Subnet Type Availability Domain-specific
Availability Domain AD 3
CIDR Block 1008024 Route Table Default Route Table for labnet Subnet Access Public Subnet DNS Resolution Enable Use DNS hostnames in this SUBNET
Security List Add two security lists using the button + Additional Security List as shown in below screenshot ndash
1 cm_sec 2 Default Security List for labnet
3 Click Create Subnet The newly created subnet will be as shown
48
48