Deploying PeopleSoft Applications on Oracle Cloud Infrastructure Instances

1. Sign in to Compute using the URL provided by your administrator, for example:

   https://console.us-ashburn-1.oraclecloud.com.

2. Enter the name of your tenancy if necessary, and enter your user name and password.

3. Click the navigation menu icon at the top left of the page, and select Compute and then Instances.

   

4. On the Compute page, select your compartment from the drop-down list on the left.

   If the Instances area does not display anything, as shown in this example, you may not have the appropriate permission to create instances. Contact your administrator.

   

Before you begin installing the PeopleSoft Update Image, it is a good idea to review the available resources and service limits for your tenancy.

1. In Oracle Cloud Infrastructure, click the navigation menu icon, and select Governance, then Limits, Quotas and Usage.

   

2. The page displays your resource limits, usage, and availability for the region. Use the drop-down lists to filter by service, scope, resource and compartments.

   For example, for the Compute service, ensure that the Availability Domain and compartment where you plan to work has enough resources to create your instances.

   

See Service Limits in the Oracle Cloud Infrastructure documentation.

1. Run the ssh-keygen command.

   ssh-keygen -b 2048 -t rsa

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

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

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

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

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

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

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

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

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

See Creating a Key Pair, Oracle Cloud Infrastructure Documentation.

The PeopleSoft Update Image contains a web server installation configured to listen for requests on port 8000 (HTTP) and 9000 (HTTPS). Your security protocols may require you to use other port values. If you use other ports, configure them when setting up the VCN, and supply the same values when creating the instance.

See the Oracle Cloud Infrastructure Networking documentation for information on VCNs.

For security, Oracle recommends that you use a private subnet to deploy the PeopleSoft Update Image. If you use a private subnet, you cannot access the instance over the internet. There are various methods of accessing an instance in a private subnet, such as with a jump host or web proxy. The Oracle Cloud Infrastructure documentation describes methods for accessing instances on private subnets.

See Oracle Cloud Infrastructure Documentation, Networking.

Note. Oracle highly recommends that you use the HTTPS protocol in all deployments. Follow the instructions found in the PeopleTools: System and Server Administration product documentation to implement the encryption keys and certificates required for Secure Sockets Layer (SSL) encryption. To review the PeopleSoft PeopleTools documentation, go to the PeopleSoft PeopleTools page on the Oracle Help Center and select your release from the drop-down list at the top. Go to the Online Help and PeopleBooks section to view the latest documentation.

This example uses the Oracle Cloud Infrastructure VCN wizard, which creates a VCN, internet gateway, NAT gateway, regional public subnet, regional private subnet, and security rules. For other options, see Networking in the Oracle Cloud Infrastructure documentation.

1. In the Oracle Cloud Infrastructure Compute Console, select Networking and then Virtual Cloud Networks.

   Note. Alternatively, you can start the VCN wizard by clicking the tile Set up a network with a wizard on the Oracle Cloud Infrastructure home page. In that case, skip the next two steps.

2. Click Start VCN Wizard.

3. Select VCN with Internet Connectivity (the default selection).

4. Click Start VCN Wizard.

   

5. On the Create a VCN with Internet Connectivity page, enter a name for the VCN.

6. Select the compartment you want to work in from the drop-down list, and then click Next.

   The name in this example is pscm_network, and the compartment is mycmprt.

   

7. Review the networking resources, and then click Create.

   

   

8. When the process is complete, click View Virtual Cloud Network to go to the Virtual Cloud Network details page.

   

9. Update the security lists to allow all necessary ports.

The subnets that you define in your VCN must allow access for the ports needed to access the PeopleSoft application in a browser, as well as SSH access for the instance. Edit the security lists in your VCN to include access for these destination ports:

• 22 (SSH)
• 8000 (default PIA HTTP port)
• 9000 (default PIA HTTPS port)
• 9033 (default Jolt port)
• 7000 (default WSL port)
• 9200 (default Elasticsearch HTTP port)
• 5601 (default Kibana HTTP port)
• 9800 (default Logstash HTTP port)

After completing these steps, skip the section Obtaining the PeopleSoft Update Image from the Oracle Images List, and continue with the steps in Creating the PeopleSoft Application Instance.

1. On the Oracle Cloud Infrastructure console home page, click the navigation menu icon at the top and select Marketplace, then All Applications.

   

2. On the Marketplace page, locate the tile for the PeopleSoft Update Image.

   You can use the filters on the left, or enter "PeopleSoft" in the search box.

3. On the Launch Instance page, accept the default Version, and select your compartment from the drop-down list.

   The page includes details such as the software versions included in the image.

   Note. For PeopleSoft Update Images built on PeopleTools 8.58, select a compartment directly under the root compartment.

4. Read the Oracle terms and restrictions, and select the option agreeing to the terms.

5. Click Launch Instance.

   The Create Compute Instance page appears with the image you selected.

6. Enter a name for the instance. Ensure that the instance name is less than 30 characters.

7. Continue with the steps in the section Creating the PeopleSoft Application Instance.

If you used the steps in the previous section to obtain the image from the menu Marketplace listing, skip this section and go to Creating the PeopleSoft Application Instance.

To obtain the PeopleSoft Update Image from a list of Oracle images:

1. On the Oracle Cloud Infrastructure console home page, click Create a VM instance under Quick Actions.

   

2. Choose a compartment on Create in Compartment dialog box, if necessary. Click Confirm.

   Note. For PeopleSoft Update Images built on PeopleTools 8.58, select a compartment directly under the root compartment.

   

3. Supply a name for the PeopleSoft application instance. Ensure that the instance name is less than 30 characters.

4. Select the Availability Domain where you want to create the instance. This example shows AD 3.

   

5. Click Change Image.

   

6. On the Browse All Images page, select the Oracle Images tab.

7. Select the PeopleSoft Update Image.

   Note. To review details about the image, expand the row by clicking the down arrow.

8. Read the Oracle terms and restrictions, and select the option agreeing to the terms.

9. Click Select Image.

10. On the Create Compute Instance page, continue with the steps in the section Creating the PeopleSoft Application Instance.

You specify the passwords for the PeopleSoft application in the Initialization Script area on the create instance page. You also have the option to change the default values for ports and users in the same script. This table lists the passwords, users, and ports that you can specify.

*Mandatory — You must include all of these parameters when creating the instance.

1. Select an instance shape.

   Accept the default, or click Change Shape to choose another shape on the Browse All Shapes page. The supported shapes are VM.Standard2.1 (1 OCPU, 15 GB RAM) and VM.Standard2.2 (2 OCPU, 30 GB RAM).

2. In the Networking section, select the option Select an existing virtual cloud network.
   

3. Select the VCN that you created earlier in this tutorial from the Virtual cloud network drop-down list.

4. Select the option Select existing subnet.

5. From the Subnet drop-down list, select the public or private subnet you want to use for the PeopleSoft application instance.

6. If you want the instance to be accessible from the Internet, select the option Assign a public IPv4 address, or select the option Do not assign a public IPv4 address. 

7. In the Add SSH keys area, select the option Upload public key files (.pub), and browse to the location where you saved the public SSH key.

   

8. In the Boot Volume area, select Specify a custom boot volume size.

   Enter a minimum size of 200 GB. The total size varies depending upon the PeopleSoft product used.

   

9. Select Show Advanced Options.
   

10. On the Management tab select the option Paste cloud-init script and enter the configuration information using the JSON format in these examples.

    The instance creation requires these passwords.

    {
       "connect_pwd":  "password",
       "access_pwd":  "password",
       "admin_pwd":  "password",
       "weblogic_admin_pwd":  "password",
       "webprofile_user_pwd":  "password",
       "gw_user_pwd":  "password",
       "domain_conn_pwd":  "password",
       "opr_pwd": "password"
     }

11. If you want to specify additional parameters, include them in the same cloud-init script.

    For example, this script specifies non-default values for the HTTP and HTTPS ports in addition to the mandatory parameters:

    {
       "connect_pwd":  "password",
       "access_pwd":  "password",
       "admin_pwd":  "password",
       "weblogic_admin_pwd":  "password",
       "webprofile_user_pwd":  "password",
       "gw_user_pwd":  "password",
       "domain_conn_pwd":  "password",
       "opr_pwd": "password",
       "pia_http_port":  "9100",
       "pia_https_port":  "9150"
     }

12. Click Create.

    

13. Monitor the instance creation on the Instances page.

    If necessary, select the instance to see the details. When the instance creation is complete, as indicated by status Running, you can sign in to follow the progress.

    If you specified a public subnet, make a note of the Public IP address for the instance in the section Instance Access.

    

    

1. Enter the following command:

   ssh -i <path_to_private_key_file>/<private_key_name> -o ServerAliveInterval=5 -o ServerAliveCountMax=1 opc@<public_ip_address_of_instance>

2. If you don't know the public IP address of your instance, you can find it by going to the Compute console and selecting the Instances tab. Select your compartment, and view the instance details page. The Primary VNIC information section includes the Public IP Address.

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

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

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

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

   Note. If you don't know the public IP address of your instance, you can find it by going to the Compute console and selecting the Instances tab. Select your compartment, and view the instance details page. The Primary VNIC information section includes the Public IP Address.

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

   

4. In the Category pane, click Connection. Enter 5 in the Seconds between keepalives (0 to turn off) text box.

   

5. In the Category pane, expand SSH, and then click Auth. The Auth panel is displayed.

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

   

7. In the Category tree, click Session.

   The Session panel is displayed.

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

9. Click Open to open the connection.

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

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

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

Monitor the configuration process status by reviewing the log file /home/opc/bootstrap/oci_status.log.

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

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

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

Note. The term bootstrap is sometimes used to refer to the setup script used to deploy the image.

The PeopleSoft application instance configuration log files are found in these locations:

• /home/opc/bootstrap/oci_status.log — Configuration process log
• /home/opc/bootstrap/psft_oci_setup.log — Image provisioning log
• /opt/oracle/psft/dpks/setup/psft_dpk_setup.log — Detailed Puppet log for the image installation

If you want to copy the log files to a Microsoft Windows computer, use a secure copy or secure FTP utility such as those associated with Putty.

For example, to transfer the files using the PSCP utility in PuTTY:

1. Create a saved session in PuTTY to connect to the PeopleSoft application instance VM.

2. Make a note of the path to your Putty installation on your laptop (for example, C:\Program Files (x86)\PuTTY).

3. Make a note of the path on the instance VM with the files you want to copy, and the path on your laptop where you want to save them.

4. Open a command prompt and make a note of your PATH environment variable.

   To list the environment variables, enter the command set. Copy the contents of PATH to Notepad or elsewhere as a backup.

5. In the command prompt, append the path to the PuTTY installation to the beginning of your PATH. For example:

   set PATH=C:\Program Files (x86)\PuTTY;%PATH%

   Note. This environment variable setting only lasts until the command window closes.

6. Use this command to connect to the session with user opc, and copy files from the source instance VM to the target Microsoft Windows computer:

   pscp –l <user> <session name>:<source> <target>

7. Enter the passphrase for the SSH key at the prompt.

   >pscp -l opc psft-infodev:/home/opc/bootstrap/psft_oci_setup.log C:\user\PeopleSoftImage\target

   Passphrase for key "mykey":

   psft_oci_setup.log        | 1142 kB | 1142.5 kB/s | ETA: 00:00:00 | 100%

Elasticsearch was initiated as part of the instance creation. The Host Name for the search instance is based on the instance name.

To verify that Elasticsearch is installed and running, use these steps:

1. Sign in to the deployed PeopleSoft environment in a browser.

2. Click the NavBar icon at the top of the window, and then click Navigator.

   

3. Select in sequence PeopleTools, Search Framework, Administration, Search Instance, and find the default Search Instance.

   The Search Instance Properties page for the default search instance, PTSF_DEFAULT, appears, as shown in this example.

   

4. On the Search Instance Properties page, in the Search Instance Properties area, click Ping beside the Host Name field. You see the message "Ping Test Result: Success. Elasticsearch version 6.1.2 (262,613)". Click OK to close the box.

   

5. Click Test Login beside the User Name field. You see the message "Login Success (262,615)". Click OK to close the box.

   

6. Click Proxy Login. You see the message "Proxy login success (262,1319)". Click OK to close the box.

   

7. Click Validate in the Call Back Properties area, beside Confirm Password. You see a page saying "All validations are successful." Select the Show All option for more details.

   Click Return.

   

8. Select the link Update Deployed Definitions. You see the message "Updated 6 deployed definitions. Failed to update 0 definitions. Refer to event log for more details (262,623)". Click OK to close the box.

   Note. The number of deployed definitions that you see may vary.

   

9. Click the magnifying glass icon at the top of the window to display the Global Search bar, and click the arrow to select the search area.

   

10. Enter a search term, such as manager, and press ENTER.

11. The page for the results appears.

    

The Elasticsearch parameters configured by the image deployment include the following default values:

• Elasticsearch administrative user and password — esadmin/Esadmin1

• Elasticsearch proxy user — people/peop1e

• Callback user — PSAPPS

• Port — 9200

There are several pages in the PeopleSoft application that you update to configure Elasticsearch and Integration Broker. If the verification tests for Elasticsearch fail, or if you cannot access the search results over the public Internet, verify that these pages have the correct information. For more information, see the PeopleTools: Search Technology product documentation on the PeopleSoft PeopleTools page on the Oracle Help Center.

See also the resources on the Elasticsearch Home Page, My Oracle Support, Doc ID 2205540.2.

For PeopleSoft Update Images built on PeopleTools 8.58, Kibana is initiated as part of the instance creation. To determine whether Kibana is included with your image, as well as the PeopleTools patch release, see the PeopleSoft Update Image details on the Marketplace image page.

See the section Obtaining the PeopleSoft Update Image.

Note. If you are deploying a PeopleSoft Update Image that was built on PeopleTools 8.58.04 and later, you can use Kibana without performing the steps described here to open the firewall to port 5601. Skip steps 1 through 6.

For information on using Kibana, see PeopleTools: Search Technology on PeopleTools on the Oracle Help Center, Online Help and PeopleBooks.

Before you can sign in to Kibana, you must perform these steps to enable access to the necessary port.

1. Access the PeopleSoft application instance as described in the section Logging in to the PeopleSoft Application Instance.

2. Log on as the root user.

   $ sudo su -

3. Enter the following commands to open the firewall to port 5601.

   # firewall-cmd --permanent --zone=public --add-port=5601/tcp 

   # firewall-cmd --reload

4. Change directory to /opt/oracle/psft/pt/tools_client.

   $ cd /opt/oracle/psft/pt/tools_client

5. View the contents of tnsnames.ora and make a note of the database name, which is HCMEGF in this example:

   $ more tnsnames.ora

   HCMEGF =
      (DESCRIPTION =
          (ADDRESS_LIST =
              (ADDRESS = (PROTOCOL = TCP)(HOST = 10.0.2.14)(PORT = 1521))
          )
          (CONNECT_DATA =
              (SERVER = DEDICATED)
              (SERVICE_NAME = HCMEGF)
          )
       )

6. Add access to port 5601 in the subnet for the instance.

7. To access Kibana, use the fully-qualified domain name from the PIA URL. Replace the port number with port 5601. For example:

   http://psft-instance-infodev.subnet1.pscmnetwork.oraclevcn.com:5601

8. On the sign in page, enter the Elasticsearch user name and password from the previous section, and the database name, and click Sign In.

   

Elasticsearch was initiated as part of the instance creation. The Host Name for the search instance is based on the instance name.

To verify that Elasticsearch is installed and running, use these steps:

1. Sign in to the deployed PeopleSoft environment in a browser.

2. Click the NavBar icon at the top of the window, and then click Menu.

   

3. Select in sequence PeopleTools, Search Framework, Administration, Search Instance, and find the default Search Instance.

   The Search Instance Properties page for the default search instance, PTSF_DEFAULT, appears. These examples show the top and bottom portions of the page.

   

   

4. On the Search Instance Properties page, in the Search Instance Properties area, click Ping beside the Host Name field. You see the message "Ping Test Result: Success. Elasticsearch version 7.10.0 (262,613)". Click OK to close the box.

   

5. Click Test Login beside the User Name field. You see the message "Login Success (262,615)". Click OK to close the box.

   

6. Click Proxy Login. You see the message "Proxy login success (262,1319)". Click OK to close the box.

   

7. Click Ping beside the Host Name field in the Logstash area. You see the message "Ping Test Result: Success. ok (262, 613)".

   

8. Click Validate in the Call Back Properties area, beside Confirm Password. You see a page saying "All validations are successful." Select the Show All option for more details.

   Click Return.

   

9. Select the link Update Deployed Definitions. You see the message "Updated 79 deployed definitions. Failed to update 0 definitions. Refer to event log for more details (262,623)". Click OK to close the box.

   Note. The number of deployed definitions that you see may vary.

   

10. The Global Search bar is available at the top of any of the PeopleSoft demo environment pages. Select a search category and enter a search term.

    

The Elasticsearch parameters configured by the image deployment include the following default values:

• Installation directory — /opt/oracle/psft/pt/ES/pt/elasticsearch7.10.0

• Elasticsearch administrative user and password — esadmin/Esadmin1

• Elasticsearch proxy user — people/Esadmin2

• Callback user — PSAPPS

• Port — 9200

There are several pages in the PeopleSoft application that you update to configure Elasticsearch and Integration Broker. If the verification tests for Elasticsearch fail, or if you cannot access the search results over the public Internet, verify that these pages have the correct information. For more information, see the PeopleTools: Search Technology product documentation on the PeopleSoft PeopleTools page on the Oracle Help Center.

See also the resources on the Elasticsearch Home Page, My Oracle Support, Doc ID 2205540.2.

For PeopleSoft Update Images built on PeopleTools 8.59, Kibana is installed and initiated as part of the instance creation. Use Kibana to visualize data for Elasticsearch server monitoring and application index monitoring, and to create dashboards to visualize application search indexes. To determine whether Kibana is included with your image, as well as the PeopleTools patch release, see the PeopleSoft Update Image details on the Cloud Marketplace image page.

The Kibana installation directory is /opt/oracle/psft/pt/ES/pt/Kibana7.10.0.

See the section Obtaining the PeopleSoft Update Image.

To verify that Kibana is installed and running:

1. Sign in to the PeopleSoft application in a browser.

2. Select in sequence PeopleTools, Security, and User Profile. Search for your user ID, and then select the Roles tab.

   Verify that the Kibana Administrator role is included in the list of roles, and add it if necessary. This role is required to access the Kibana home page.

3. Select Reporting Tools and then Kibana.

4. On the Welcome to Elastic page, select Explore on my own.

   

   This displays the Kibana home page.

   

For information on using Kibana, see PeopleTools: Search Technology on PeopleTools on the Oracle Help Center, Online Help and PeopleBooks.

Beginning with PeopleSoft Update Images that are built on PeopleSoft PeopleTools 8.59, Logstash is installed and initiated as part of the instance creation. Logstash is used for the PeopleSoft Health Center, which displays charts and data using Kibana. It is also used with external data integration.

The Logstash installation directory is /opt/oracle/psft/pt/ES/pt/Logstash7.10.0.

For information on working with the Logstash installation, see PeopleSoft Deployment Packages for Elasticsearch Installation, PeopleSoft PeopleTools 8.59, PeopleTools on the Oracle Help Center.

To use Logstash for PeopleSoft Health Center, see PeopleTools: Performance Monitor, "Configuring PeopleSoft Health Center," PeopleTools on the Oracle Help Center.

To use Elasticsearch, Kibana, and Logstash for external data integration, see PeopleTools: Search Technology, "Integrating External Data with PeopleSoft," PeopleTools on the Oracle Help Center.