Deploying PeopleSoft Applications on Oracle Cloud Infrastructure Compute Classic Instances

To verify that Elasticsearch is included in the PeopleSoft application image that you obtain from Oracle Cloud Marketplace, look at the details included on the Overview tab of the image page. Images that are built on PeopleTools 8.56.06 and later patch releases include Elasticsearch.

See the section Initiating Deployment in Oracle Cloud Marketplace.

Use one of these methods to enable Elasticsearch:

• Provide the Oracle Cloud user ID, password, identity domain, and the account REST Endpoint URL in a custom attribute entry when you configure the instance.

  This sets up the search instance with the domain name constructed from the public IP address for the instance, which makes search available for users on the public Internet.

  See the section Configuring the Instance for the PeopleSoft Application.

• If you do not want to supply the user account credentials during the instance configuration, create the instance without specifying any custom attribute. After the instance is provisioned, you must input the domain name constructed from the public IP address for the instance in several places in the PeopleSoft application to enable Elasticsearch for public Internet users.

  See the section Enabling Elasticsearch Manually in the Deployed Instance (Optional).

To find the necessary information:

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

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

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

   

3. If necessary, enter your identity domain on the Oracle Cloud sign in page, which is idendomain in this example, and then click the Go button.

   Make a note of the identity domain you use, as it will be needed as part of the custom attributes used to enable Elasticsearch.

   

4. Enter a valid user name and password for your Identity Domain and then click Sign In.

   Make a note of these user credentials, as they will be needed as part of the custom attributes used to enable Elasticsearch.

   

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

   

6. On the Compute Classic service console, click the site name at the top of the page.

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

7. Record the value for the REST endpoint from the Site Selector dialog box, for example, https://api-xyz-compute.xxx.oraclecoud.com.

   

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.

1. Find puttygen.exe in the PuTTY folder on your computer and double-click it.

2. Accept the default key type, SSH-2 RSA, and set the Number of bits in a generated key to 2048, if it is not already set. Then click Generate.

   

3. Move your mouse around the blank area to generate randomness, as represented by the blue line in this example. The SSH key pair is generated.

   

4. Enter the name of the key, which is rsa-key-psft in this example, in the Key comment field. You can keep the generated key comment or create your own.

   

5. Enter a passphrase in the Key passphrase and the Confirm passphrase fields.

   Note. Remember the passphrase. You can't recover a passphrase if you forget it.

6. To save the private key in the PuTTY PPK format, click Save private key.

   Enter the same name as you used for the key comment so that you know which public key to use this private key with. The private key is saved in PuTTY's Private Key (PPK) format, which is a proprietary format that works only with the PuTTY toolset. You can use this key whenever you use PuTTY for SSH.

7. To save the public key, in the PuTTY Key Generator, select all of the characters in the Public key for pasting into OpenSSH authorized_keys file: field.

   Note. Make sure you select all the characters, not just the ones you can see in the narrow window. If there is a scroll bar next to the characters, you aren't seeing all the characters.

8. Right-click somewhere in the selected text and select Copy from the menu.

   

9. Open a text editor and paste the characters. Ensure that you paste the text at the first character in the text editor, and don't insert any line breaks.

10. Save the key using the same root name that you used for the private key. Add a .pub extension. You can give it any extension you want, but .pub is a useful convention to indicate that this is a public key.

11. Exit PuTTY Key Generator.

12. 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.

A security list is a group of Oracle Cloud instances. To open port 8000 for a specific instance, create a security list. In a subsequent step the Compute Classic instance will be added to this security list.

To create a security list:

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

2. From the drop-down list below the Network tab, select Security Lists.

   

3. Click the Create Security List button.

   

4. In the Create Security List dialog box, select or enter the following information:

   • Name: Enter a name for the new security list. For the purpose of this tutorial, enter peoplesoft_webserver_seclist. Note this name. You'll use it later in this tutorial.
   • Inbound Policy: Accept the default option, Deny (Drop packets, no reply).
   • Outbound Policy: Select Permit (Allow packets).
   • Description: Enter a description for the new security list if desired, for example, PeopleSoft FSCM9.2 web server security list.

   

5. Click Create.

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

1. Click the Network tab and select the Security Applications link from the Shared Network drop-down list below the tabs.

   

2. Click Create Security Application.

   

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

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

   

4. Click Create.

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

1. Click the Network tab and select Security Rules from the Shared Network drop-down list below the tab.

   

2. Click Create Security Rule.

   

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

   • Name: Enter an appropriate name for the rule. For the purpose of this tutorial, enter allow_http_to_8000.
   • Status: Select Enabled.
   • Security Application: Select open_tcp_8000, which is the security application that you created earlier.
   • Source: Select the Security IP List radio button and from the Security IP List drop-down list, select public-internet.
   • Destination: Select the peoplesoft_webserver_seclist security list that you created earlier.
   • Description: Enter a description for the rule if desired.

   

4. Click Create.

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

1. On the Oracle Compute Classic Service Console, click the Network tab.

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

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

   Enter or select the following information:

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

   

4. Click Create.

1. Enter the following command:

   ssh -o ServerAliveInterval=5 -o ServerAliveCountMax=1 $HOST -i/path/to/<private_key_name> opc@<public_ip_address_of_instance>

   Note. If you don't know the public IP address of your instance, you can find it by going to the Instances tab on the Compute Classic Service Console. From the list of instances displayed, identify the correct instance and note the Public IP Address.

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

3. 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 Instances tab on the Compute Classic Service Console. From the list of instances displayed, identify the correct instance and note the Public IP Address.

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

   

4. In the Category pane, expand Connection, and then click Data. The Data panel is displayed.

5. In the Auto-login username field, enter opc. Confirm that the When username is not specified option is set to Prompt.

   

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

   Ensure that the Enable TCP keepalives (SO_KEEPALIVE option) check box is selected.

   

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

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

   

9. In the Category tree, click Session.

   The Session panel is displayed.

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

11. Click Open to open the connection.

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

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

13. 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.

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

2. Select PeopleTools, Search Framework, Administration, Search Instance, and find the default Search Instance, PTSF_DEFAULT.

   On the Search Instance Properties page, the Host Name field is populated with the internal DNS name for the Compute Classic instance, which is psftfscm92pi272.compute-idendomain.oraclecloud.example.com in this example.

   The URL field under Call Back Properties is populated with this URL (PS_OOVHOKIUYY2X is the default local node):

   http://psftfscm92pi272.compute-idendomain.oraclecloud.example.com:8000/PSIGW/RESTListeningConnector/PS_OOVHOKIUYY2X

   

3. For the Host Name in the Search Instance Properties area, enter the URL generated from the public IP address for the instance in this format:

   oc-198-51-100-67.compute.oraclecloud.com

4. For the URL in the Call Back Properties area, change the internal DNS name to the public-address-based URL, leave the last portion of the URL unchanged, and save the page. For example, change the entry to:

   http://oc-198-51-100-67.compute.oraclecloud.com:8000/PSIGW/RESTListeningConnector/PS_OOVHOKIUYY2X

   

5. Select PeopleTools, Integration Broker, Configuration, Gateway.

6. On the Gateways page, in the URL field, change the internal DNS name to the public-address-based URL, and leave the last portion of the URL unchanged. For example, change the URL to:

   http://oc-198-51-100-67.compute.oraclecloud.com:8000/PSIGW/PeopleSoftListeningConnector

   

7. Select the Gateway Setup Properties link.

8. On the PeopleSoft Node Configuration page, change the values for App Server URL in the Gateway Default App. Server and PeopleSoft Nodes areas, and then click OK. For example, change the App Server URL to:

   //oc-198-51-100-67.compute.oraclecloud.com:9033

   

9. Select PeopleTools, Integration Broker, Configuration, Service Configuration.

10. On the Service Configuration tab, select the link Setup Target Locations.

    

11. In the Web Services Target Location and REST Target Locations areas, change the values for the Target Locations to the public PeopleSoft application URL, and then click OK. For example, change the target locations to:

    • Web Services Target Location:
      http://oc-198-51-100-67.compute.oraclecloud.com:8000/PSIGW/PeopleSoftServiceListeningConnector/PS_OOVHOKIUYY2X
    • REST Target Location:
      http://oc-198-51-100-67.compute.oraclecloud.com:8000/PSIGW/RESTServiceListeningConnector/PS_OOVHOKIUYY2X
      

    

12. Select PeopleTools, Integration Broker, Integration Setup, Nodes, and search for all nodes. Click the top of the Local Nodes column twice to sort the local nodes. In this example there are three local nodes; the default local node for this installation, PS_OOVHOKIUYY2X, PSFT_RTBL and ERP.

    

13. Select one of the local nodes from the list, such as PS_OOVHOKUIYY2X, and then select the Portal tab. In the Content URI Text and Portal URI Text fields, change the internal DNS name to the public-address-based URL, and leave the last portion of the URL unchanged. For example, change the URIs to:

    • Content URI Text: http://oc-198-51-100-67.compute.oraclecloud.com:8000/psc/ps
    • Portal URI Text: http://oc-198-51-100-67.compute.oraclecloud.com:8000/psp/ps

    

14. Update the remaining local nodes.

Sign into the PeopleSoft application as described in the section Logging In to Your Instance Using SSH to reboot the PeopleSoft domains. Here is a summary of the steps. For more information see the PeopleTools product documentation.

1. Change to the psadm2 user and run PSADMIN.

   [opc@psftfscm92pi272 pt]$ sudo su - psadm2

   [psadm2@psftfscm92pi272 ~]$ psadmin

2. On the PSADMIN menu, select 1) Application Server.

   PSADMIN -- PeopleTools Release: 8.56.06
   Copyright (c) 1996, 2017, Oracle and/or its affiliates. All rights reserved.
   --------------------------------
   PeopleSoft Server Administration
   --------------------------------
     PS_CFG_HOME            /home/psadm2/psft/pt/8.56
     PS_HOME                /opt/oracle/psft/pt/ps_home8.56.06
     PS_APP_HOME            /opt/oracle/psft/pt/fscm_app_home
     1) Application Server
     2) Process Scheduler
     3) Web (PIA) Server
     4) Switch Config Home
     5) Replicate Config Home
     6) Refresh Config Home
     q) Quit
   Command to execute (1-6, q): 1
   

3. Specify 1) Administer a domain, and select 1) APPDOM.

   --------------------------------------------
   PeopleSoft Application Server Administration
   --------------------------------------------
     1) Administer a domain
     2) Create a domain
     3) Delete a domain
     4) Import domain configuration
     q) Quit
   Command to execute (1-4, q) : 1 

   Domain list:
      1) APPDOM
   Select domain: 1 

   --------------------------------
   PeopleSoft Domain Administration
   --------------------------------
        Domain Name: APPDOM
   
     1) Boot this domain
     2) Domain shutdown menu
     3) Domain status menu
     4) Configure this domain
     5) TUXEDO command line (tmadmin)
     6) Edit configuration/log files menu
     7) Messaging Server Administration menu
     8) Purge Cache
     9) Preload Cache
    10) Clean IPC resources of this domain
     q) Quit
   

4. Specify 2), Domain shutdown menu, and then 1) Normal shutdown.

   -------------------------------
   PeopleSoft Domain Shutdown Menu
   -------------------------------
        Domain Name: APPDOM
     1) Normal shutdown
     2) Forced shutdown
     q) Quit
   
   Command to execute (1-2, q) [q]: 1
   
   Shutting down Application Server domain APPDOM...

5. When the shutdown process is complete, quit and specify 1) Boot this domain, followed by 1) Boot (Serial Boot) and wait for the APPDOM to boot.

   --------------------------------
   PeopleSoft Domain Administration
   --------------------------------
        Domain Name: APPDOM
   
     1) Boot this domain
     2) Domain shutdown menu
     3) Domain status menu
     4) Configure this domain
     5) TUXEDO command line (tmadmin)
     6) Edit configuration/log files menu
     7) Messaging Server Administration menu
     8) Purge Cache
     9) Preload Cache
    10) Clean IPC resources of this domain
     q) Quit
   
   Command to execute (1-10, q) : 1
   
   
   -------------------------------
   PeopleSoft Domain Boot Menu
   -------------------------------
        Domain Name: APPDOM
   
     1) Boot (Serial Boot)
     2) Parallel Boot
     q) Quit
   
   Command to execute (1-2, q) [q]: 1
   

6. Repeat steps 2-5 with the Process Scheduler and Web (PIA) Server domains.

Undeploy and redeploy all of the search definitions, and then perform a full crawl.

1. Sign in to the PeopleSoft application in a browser and select PeopleTools, Search Framework, Administration, Deploy/Delete Object, and search for all definitions.

   The Deploy Search Definition page appears. This example shows the top of the page.

   

2. Select all of the Elasticsearch definitions, and click Undeploy and then Deploy. This example shows the bottom of the Deploy Search Definition page after redeploying several definitions. The PTPORTALREGISTRY definition has Deploy Status Deployed and Crawl Status Not Crawled.

   

3. Select PeopleTools, Search Framework, Administration, Schedule Search Index. Run a full index for all Elasticsearch definitions.

   

Follow the instructions in the section Restarting the PeopleSoft Domains to restart the PeopleSoft application server, Process Scheduler, and web server (PIA) domains.