Deploying PeopleSoft Applications on Oracle Cloud Infrastructure Compute Classic Instances


Options



Before You Begin

Purpose

This tutorial describes the process to deploy a complete PeopleSoft 9.2 application demo database environment from Oracle Cloud Marketplace on an Oracle Cloud Infrastructure Compute Classic instance.

Time to Complete

Approximately 60 minutes, including 15 minutes active time, and an additional 30-45 minutes for the VM to start.

Background

Access a PeopleSoft image from Oracle Cloud Marketplace and use it to deploy a complete PeopleSoft application environment in an Oracle Cloud Infrastructure Compute Classic (Compute Classic) instance. The PeopleSoft application will be deployed to a single Linux Compute Classic instance using a bootable machine image that will be accessed directly from Oracle Cloud Marketplace. Use the deployed PeopleSoft application, which is a non-production, demo environment, for example to examine new features and functionality.

The deployment of PeopleSoft images that are built on PeopleSoft PeopleTools 8.56.06 and later patches include the installation and initialization of Elasticsearch, which is used for the PeopleSoft Search Framework.

For an overview of other methods available for using PeopleSoft environments with Oracle Compute Cloud Service, see Getting Started with PeopleSoft Environments in Oracle Compute Cloud Service.

Oracle Cloud Marketplace offers a platform for system integrators and software vendors to showcase services and applications that interoperate with Oracle Integrated Cloud Services.

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

What Do You Need?

  • Subscription and User Roles

    A subscription to Oracle Cloud Infrastructure Compute Classic is mandatory and you must be a user with the Compute_Operations and Storage Read Write Group roles.

    See How to Begin with Oracle Compute Classic Subscriptions in Using Oracle Cloud Infrastructure Compute Classic.

  • SSH Key Pair

    For the section Generating an SSH Key Pair, you will need either an implementation on an on-premises system (local computer) of the ssh-keygen utility (for Linux) or an application such as PuTTY (for Microsoft Windows).

  • User Credentials for Elasticsearch configuration

    If you choose to configure Elasticsearch during instance creation, you must supply your Compute Classic account credentials. See the section Preparing for the Elasticsearch Initialization.

Process Overview

To deploy a PeopleSoft application from Oracle Cloud Marketplace, execute the following steps:

  1. Prepare for the Elasticsearch initialization.

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

  3. Upload the SSH public key to Compute Classic.

  4. Configure the Compute Classic instance for HTTP access.

  5. Determine the PeopleSoft application to be deployed and initiate deployment in Oracle Cloud Marketplace.

  6. Use the Compute Classic web-based Service Console to configure the instance that will be used to host the PeopleSoft application.

  7. Sign in to the PeopleSoft application.

  8. Verify the Elasticsearch configuration in the PeopleSoft application

  9. Log in to your instance using SSH.

  10. Change the default password for the opc user (mandatory).

  11. Enable Elasticsearch manually in the deployed instance if necessary (optional).

Preparing for the Elasticsearch Initialization

Elasticsearch is used for the PeopleSoft Search Framework. When you deploy PeopleSoft application images that are built on PeopleSoft PeopleTools 8.56.06 and later, Elasticsearch is available with the PeopleSoft image.

Checking the PeopleSoft PeopleTools Release

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.

Choosing How to Enable Elasticsearch

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

Verifying the Oracle Cloud Account Information and REST Endpoint URL

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.

    Oracle Cloud My Services page
    Description of this image
  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.

    Oracle Cloud sign in page for identity domain
  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.

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

    Dashboard showing Compute Classic and Database cards
    Description of this image
  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.

    Site Selector dialog box
    Description of this image

Generating an SSH Key Pair

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

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

  1. Run the ssh-keygen command.

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

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

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

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

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

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

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

Generating an SSH Key Pair on Windows Using the PuTTY Key Generator

  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.

    PuTTY Key Generator dialog box
    Description of this image
  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.

    Generating randomness in PuTTY Key Generator dialog box
    Description of this image
  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.

    Generate SSH key pair on Windows, save private key
    Description of this image
  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.

    Generate SSH key pair on Windows, copy public key
    Description of this image
  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.

Uploading the SSH Key

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

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

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

  3. Enter the necessary credentials, as described in the section Verifying the Oracle Cloud Account Information and REST URL, and then click Sign In.

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

    Dashboard showing Compute Classic and Database cards
    Description of this image
  5. Select Network at the top of the page. Expand the drop-down list from Shared Network > Security Rules, and then select SSH Public Keys.

    Compute Classic Service Console Network page
    Description of this image
  6. Click Add SSH Public Key.

    SSH Public Keys page
    Description of this image
  7. In the Add SSH Public Key dialog box, enter a name and the value of the SSH public key you generated, and then click Add.

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

    Your SSH public key is added to Compute Classic.

    Add SSH Public Key dialog box
    Description of this image

Configuring Your Instance for HTTP or HTTPS Access

The PeopleSoft bootable images found in Oracle Cloud Marketplace contain a web server installation configured to listen for requests on port 8000 (HTTP) and 8443 (HTTPS).

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.

The Creating a Security List, Creating a Security Application, and Creating a Security Rule sections give an example that demonstrates how to define a security list using port 8000 for http; however, we recommend that you use this as an example only and subsequently enable port 8443 for secure connections (https/SSL) only.

Creating a Security List

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.

    Select Security Lists on Network page
    Description of this image
  3. Click the Create Security List button.

    Security Lists page
    Description of this image
  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.
    Create Security List dialog box
    Description of this image
  5. Click Create.

Creating a Security Application

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

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

    Select Security Application on Network page
    Description of this image
  2. Click Create Security Application.

    Security Application page
    Description of this image
  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).
    Create Security Application dialog box
    Description of this image
  4. Click Create.

Creating a Security Rule

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.

    Select Security Rules on the Network page
    Description of this image
  2. Click Create Security Rule.

    Security Rules page
    Description of this image
  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.
    Create Security Rule dialog box
    Description of this image
  4. Click Create.

Enabling SSH Access with the Default Security List

Enable SSH access by default for all instances that are created 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.
    Create Security Rule dialog box
    Description of this image
  4. Click Create.

Initiating Deployment in Oracle Cloud Marketplace

Determine the PeopleSoft application to be deployed, and initiate deployment as follows:

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

  2. Enter peoplesoft in the search text box, and click the Go button.

    Oracle Cloud Marketplace Applications page
  3. Choose the desired PeopleSoft application from the list of available Oracle Cloud Marketplace applications. New PeopleSoft Update Images are made available regularly on Oracle Cloud Marketplace, so your search results will vary.

  4. Click the name for the desired PeopleSoft application to begin the deployment, such as PeopleSoft FSCM 9.2 Update Image 27. Click the Get App button.

    The image page describes the components included in the image, under App by Oracle. This example shows the page for PeopleSoft FSCM 9.2 Update Image 27 DEMO with  PeopleTools 8.56.06.

    PeopleSoft FSCM 9.2 Update Image 26 DEMO page
    Description of this image
  5. On the Install Application page, select the name of the IDCS account or Oracle Cloud Identity Domain that is associated with your Oracle Compute Cloud Service subscription from the Compute Account drop-down list, which is idendomain in the following example.

  6. Select the link Oracle Standard Terms and Restriction. After reviewing the terms, select the option I have reviewed and accept the Oracle Standard Terms and Restrictions, and then click the Install button.

    Install Application page
    Description of this image
  7. The bootable image that will be used to start the instance is now available to the Compute Classic account selected in step 6.

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

    Application Successfully Installed page
    Description of this image

Configuring the Instance for the PeopleSoft Application

Use the Compute Classic service console to configure the instance that will be used to host the PeopleSoft application.

  1. As described in the section Verifying the Oracle Cloud Account Information and REST Endpoint URL, sign in to Compute Classic. The Create Instance page appears with the image.

    Create Instance, Image page
    Description of this image
  2. Click Select, and then click the right arrow (>) at the top of the page to continue.

    Create Instance page with image selected
    Description of this image
  3. Select a shape (number of OCPUs with memory allocation) for the Compute Classic instance, and then click the right arrow to continue. The shape in this example is oc1m (OCPUs: 1, Memory, 15 GB).

    Create Instance, Shape page
    Description of this image
  4. On the Instance page, select False or True from the Persistent drop-down list. This option controls the behavior of the instance and the underlying orchestration.

    For information, see Creating an Instance Using a Private Image in the Using Oracle Cloud Infrastructure Compute Classic documentation.

    Create Instance, Instance page
    Description of this image
  5. Select Auto or Specific Domain from the Placement drop-down list. Use this option to determine whether to create the instance in the same domain or a different domain as any existing instances. In this example Auto is selected.
  6. To enable Elasticsearch, enter the information required to access the Compute Classic account in the Custom Attributes field. Note that this text, including the password, is not masked. Use the following format:

    {"opc_user_id":"psft_user@example.com","opc_user_pwd":"password","opc_domain_name":"idendomain","opc_compute_rest_end_point":"https://api-xyz.compute.xxx.oraclecloud.com/"}
    
    • "opc_user_id" is the Oracle Cloud user name, for example psft_user@example.com.
    • "opc_user_pwd" is the password for the Oracle Cloud user.
    • "opc_domain_name" is the identity domain, for example idendomain.
    • "opc_compute_rest_end_point" is the REST End Point URL, for example https://api-xyz.comute.xxx.oraclecloud.com/

    Note. If you do not enter the custom attributes here, you must to enable Elasticsearch after the instance creation.  See the section Enabling Elasticsearch Manually in the Deployed Instance (Optional).

  7. Enter a Name and Label for the Compute Classic instance, or accept the defaults. Enter a description if desired.

  8. Click in the SSH Keys field, and select the SSH key you uploaded in the section Uploading SSH Keys, which is rsa-key-psft in this example.

  9. Click the right arrow to continue.
  10. On the Network page, add a hostname in the DNS Hostname Prefix field, which is PSFTFSCM92PI27 in this example.

    Create Instance, Network page
    Description of this image
  11. Accept the default Network Options, Shared Network and IP Network.

  12. Under Shared Network Options, if necessary, select Auto Generated from the Public IP Address drop-down list.

  13. Ensure that the Security Lists field includes default, and then click the right arrow to continue.

  14. Click the right arrow on the Storage page to continue.

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

    Create Instance, Review page
    Description of this image
  16. Check the status of the Compute Classic instance using the Instances tab.

    When the status has changed to Running, as in this example, make a note of the Public IP address for the instance, which is 198.51.100.67 in this example. You will use this in the next section to create the URL to access the instance.

    Instances page with status Running
    Description of this image
  17. Click the options button (Options button) for the instance and select View.

  18. Expand the Security Lists area if necessary, and then click Add to Security List.

    Instance Information page with Security Lists section
    Description of this image

    The Add to Security List dialog box appears.

  19. Select the list peoplesoft_webserver_seclist, which you created in the section Creating a Security List, from the Security List drop-down list.

    Add to Security List dialog box
    Description of this image
  20. Click Add. The instance appears in the Security Lists area as in this example:

    Instances detail page with added security list
    Description of this image

Signing in to the PeopleSoft Application

Sign in to the running PeopleSoft instance in a browser, using a URL constructed from the publicly addressable DNS name. To determine the URL, use the public IP address of the Compute Classic instance that you noted in the previous section.

  1. Click the Instances tab.

  2. From the list of instances displayed, note the Public IP address for the correct instance.

    The PeopleSoft URL will always follow this format for HTTP:

    http://oc-public-ip-address-using-hyphens.compute.oraclecloud.com:8000/ps/signon.html

    For HTTPS:

    https://oc-public-ip-address-using-hyphens.compute.oraclecloud.com:8443/ps/signon.html

    For example, the URL for the PeopleSoft FSCM 9.2 Update Image 27 application used for this tutorial is:

    http://oc-198-51-100-67.compute.oraclecloud.com:8000/ps/signon.html.

  3. Enter the PeopleSoft URL in a browser to display the sign in window:

    PeopleSoft sign in window in a browser
    Description of this image

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

Verifying the Elasticsearch Initialization

If you entered the Compute Classic account information in the custom attribute field when you created the instance, Elasticsearch was initiated as part of the instance creation.

In this case, the Host Name and URLs for the search instance are based on the URL constructed from the public IP address for the instance, described in the section Signing in to the PeopleSoft Application. If you did not enter the Compute Classic account information during the instance creation, see the section Enabling Elasticsearch Manually in the Deployed Instance (Optional) for the required steps.

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 windows, and then click Navigator.

    Navigation menu in PeopleSoft application
    Description of this image
  3. Select 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.

    Note. If the Host Name field does not display the URL constructed from the public IP address, you may have made an error in entering the custom attributes. If there is an error, the instance will be configured with the internal domain name, which will appear on this page. In that case, you must manually configure Elasticsearch as described in the section Enabling Elasticsearch Manually in the Deployed Instance (Optional).

    Search Instance Properties page
    Description of this image
  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 2.3.2 (262,613)". Click OK to close the box.

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

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

    Proxy login success message 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.

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

    Updated 8 deployed definitions message box
  9. Click the magnifying glass icon at the top of the window to display the Global Search bar.

    Search Instance Properties page with search box expanded
    Description of this image
  10. Enter a search term, such as manager, and press ENTER.

  11. Select one of the search results, such as Regional General Manager.

    Global Search results
    Description of this image

    The page for the results appears.

    Search result for Asset Manager
    Description of this image

    Note that if Elasticsearch is not configured with the URL constructed from the public IP address, you cannot access the search result over the public Internet in this manner.

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

  • Elasticsearch administrative user and password — esadmin/esadmin

  • Elasticsearch proxy user — people/peop1e

  • Callback user — PSAPPS

  • Port — 9200

See also the section Reviewing the Delivered Passwords.

Logging In to Your Instance Using SSH

To set up SSL, as previously mentioned, using the instructions in the PeopleTools System and Server Administration product documentation, you must be able to access the Linux VM with SSH.

It is possible to SSH to any Linux Compute Classic instance that is started from a bootable PeopleSoft image from Oracle Cloud Marketplace using the opc user id. The opc user is configured for remote access over the SSH protocol using RSA keys. The public SSH key that you attached to the Identity Domain in a previous step is automatically added to the VM.

The opc user has sudo privileges and has a default password that must be changed upon the first attempt to SSH to the VM. Instructions to change this password are found in the section Changing the Default Password for the opc User (mandatory). First, follow the steps in this section to successfully SSH to the PeopleSoft Linux instance from either a UNIX or UNIX-like system, or from Microsoft Windows.

Logging In From a UNIX or UNIX-Like System

  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.

Logging In From a Windows System

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

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

    Note. If you don't know the public IP address of your instance, 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.

    PuTTY Configuration window
    Description of this image
  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.

    PuTTY Configuration, Data window
    Description of this image
  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.

    PuTTY Options controlling the connection page
    Description of this image
  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.

    PuTTY Configuration, SSH window
    Description of this image
  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.

Changing the Default Password for the opc User (Mandatory)

After successfully making the initial connection to the Compute Classic instance using the SSH protocol, you must immediately change the default password of the opc user.

  1. If you haven’t already done so, SSH to the VM from either a Linux or Windows system. For example, for Linux:

    $ ssh -o ServerAliveInterval=5 -o ServerAliveCountMax=1 $HOST -i/home/bob/.ssh/id_rsa opc@192.51.100.67
  2. You will see the following message telling you to change your password, upon your first connection via SSH:

    Change Password message
    Description of this image

    You cannot do anything from the Linux command line until the default password has been changed.

  3. Enter the default (current) password for the opc user, which is OracleCloud.

  4. Enter a new UNIX password two times, using the following guidelines:

    • Use an alphanumeric password.
    • The length must be a minimum of 8 characters.
    • Use at least one upper-case alphabetic character.
    • Use at least one numeric character.
    • Use at least one special character, such as @,  #, $ and so on.
    • It cannot closely resemble a dictionary word.
  5. When the password has been successfully changed, you will be immediately disconnected and you should see a message indicating success, similar to the following:

    Change password success message
    Description of this image

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

Enabling Elasticsearch Manually in the Deployed Instance (Optional)

If you do not supply the custom attribute specifying your Compute Classic account information when creating the instance, or if you supply incorrect input, Elasticsearch is configured based on the internal DNS name for the Compute Classic instance, rather than the URL constructed from the public IP address for the instance. In this case, when you use the PeopleSoft search functionality, you will not be able to access the search results over the public Internet. To enable search in the PeopleSoft application over the public Internet, you must configure Elasticsearch and Integration Broker with the details about the public-address-based URL after completing instance creation.

There are several pages in the PeopleSoft application that you update to configure Elasticsearch and Integration Broker, and the exact input varies for the URLs and host names. In general, replace the portion of the URL with the internal DNS name for the Compute Classic instance, such as http://ab1234.domainname.oraclecloud.example.com, with the URL constructed from the public IP address for the instance, such as http://oc-198-51-100-67.compute.oraclecloud.com, and do not change the remainder of the field.

Configuring the Search Instance with the Public-Address-Based URL

  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

    Search Instance Properties page with the internal DNS name
    Description of this image
  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

    Search Instance Properties page after update
    Description of this image
  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

    Gateways page after update
    Description of this image
  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

    PeopleSoft Node Configuration page
    Description of this image
  9. Select PeopleTools, Integration Broker, Configuration, Service Configuration.

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

    Service Configuration page
    Description of this image
  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
    Target Locations page
    Description of this image
  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.

    Nodes search results
    Description of this image
  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
    Node Portal tab
    Description of this image
  14. Update the remaining local nodes.

Restarting the PeopleSoft Domains

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.

Redeploying the Search Definitions

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.

    Deploy Search Definition page, top
    Description of this image
  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.

    Deploy Search Definitions page, bottom
    Description of this image
  3. Select PeopleTools, Search Framework, Administration, Schedule Search Index. Run a full index for all Elasticsearch definitions.

    Build Search Index page
    Description of this image

Restarting the PeopleSoft Domains After Redeploying the Search Definitions.

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

Verifying the Reconfigured Elasticsearch

Follow the steps in the section Verifying the Elasticsearch Installation.

Reviewing the Delivered Passwords

The following table lists the default values for the passwords that are delivered with the PeopleSoft images on Oracle Cloud Marketplace, along with references for how to change the passwords.

# Description Default Values Reference
1
PeopleSoft Connect ID and password people/peop1e
(The password has the number one rather than the letter 'l'.)
See PeopleTools: System and Server Administration, Setting Application Server Domain Parameters, Startup Options, in  PeopleSoft Hosted Online Help.
2
Database administrator and password for the Oracle database SYS (or SYSTEM)/Passw0rd123# Oracle Database Security Guide, Managing Security for Oracle Database Users, Changing the SYS User Password inOracle Help Center
3
Access ID and password
SYSADM/SYSADM
See PeopleTools: Data Management, Administering PeopleSoft Databases on Oracle, Working with Oracle Security Features, in PeopleSoft Hosted Online Help.
4 Oracle WebLogic administrator and password system/Welcome123 See PeopleTools: System and Server Administration, Working with Oracle WebLogic, Changing WebLogic User Passwords, in PeopleSoft Hosted Online Help.
5 Web Profile user and password PTWEBSERVER/PTWEBSERVER See PeopleTools: Portal Technology, Configuring the Portal Environment, Configuring Web Profiles, in PeopleSoft Hosted Online Help.
6 Domain connection password Passw0rd123 See PeopleTools: System and Server Administration, Setting Application Server Domain Parameters, Security Options, in PeopleSoft Hosted Online Help.
7 Integration Gateway ID and password administrator/password See PeopleTools: Integration Broker Administration, Managing Integration Gateways, Accessing Gateway Setup Properties, in PeopleSoft Hosted Online Help.
8 PeopleSoft Database Operator ID The passwords are specific to the PeopleSoft product, as follows:
  • CRM: VP1/VP1
  • CS: PS/PS
  • ELM: PS/PS
  • FSCM: VP1/VP1
  • HCM: PS/PS
  • IH: VP1/VP1
See PeopleTools: Security Administration, Administering User Profiles, Working with Passwords, in PeopleSoft Hosted Online Help
9 Elasticsearch read user (Proxy) and password

Note. This is not the same as the Connect ID and password, although the values are the same. The password has the number one rather than the letter 'l'.
people/peop1e


See the steps following this table.*
10 Elasticsearch admin user and password esadmin/esadmin See the steps following this table.*
11 The PeopleSoft installation
administrator who owns PS_HOME.

Note. This user is installed as part of the image deployment.
psadm1/0radmin The password is set to expire immediately. On the first login, the system will prompt you to provide a new password.

See also PeopleSoft Deployment Packages for Update Images Installation, (PeopleSoft PeopleTools 8.56), Reviewing the Deployed Users.
Go to the PeopleSoft Update Manager (PUM) Home Page, My Oracle Support, Doc ID 1641843.2. Select the update image home pages tab, and locate the page for your PeopleSoft application (for example, HCM Update Image Home Page). Expand the Installation Documentation section to locate the guide.
12 The PeopleTools domain user who creates and configures the Application Server domain, Process Scheduler (batch server) domain, and the PIA.

Note. This user is installed as part of the image deployment.
psadm2/0radmin The password is set to expire immediately. On the first login, the system will prompt you to provide a new password.

See also PeopleSoft Deployment Packages for Update Images Installation, (PeopleSoft PeopleTools 8.56), Reviewing the Deployed Users.
Go to the PeopleSoft Update Manager (PUM) Home Page, My Oracle Support, Doc ID 1641843.2. Select the update image home pages tab, and locate the page for your PeopleSoft application (for example, HCM Update Image Home Page). Expand the Installation Documentation section to locate the guide.
13 The PeopleSoft installation
administrator who owns
PS_APP_HOME.

Note. This user is installed as part of the image deployment.
psadm3/0radmin The password is set to expire immediately. On the first login, the system will prompt you to provide a new password.

See also PeopleSoft Deployment Packages for Update Images Installation, (PeopleSoft PeopleTools 8.56), Reviewing the Deployed Users.
Go to the PeopleSoft Update Manager (PUM) Home Page, My Oracle Support, Doc ID 1641843.2. Select the update image home pages tab, and locate the page for your PeopleSoft application (for example, HCM Update Image Home Page). Expand the Installation Documentation section to locate the guide.
14 The Oracle Database Server user name.

Note
. This user is installed as part of the image deployment.
oracle2/oracle The password is set to expire immediately. On the first login, the system will prompt you to provide a new password.

See also PeopleSoft Deployment Packages for Update Images Installation, (PeopleSoft PeopleTools 8.56), Reviewing the Deployed Users.
Go to the PeopleSoft Update Manager (PUM) Home Page, My Oracle Support, Doc ID 1641843.2. Select the update image home pages tab, and locate the page for your PeopleSoft application (for example, HCM Update Image Home Page). Expand the Installation Documentation section to locate the guide.
15 Elasticsearch DPK user

Note
. This is not the same as the esadmin administrator. This user is installed as part of the image deployment.
esadm1/0radmin The password is set to expire immediately. On the first login, the system will prompt you to provide a new password.

See also PeopleSoft Deployment Packages for Update Images Installation, (PeopleSoft PeopleTools 8.56), Reviewing the Deployed Users.
Go to the PeopleSoft Update Manager (PUM) Home Page, My Oracle Support, Doc ID 1641843.2. Select the update image home pages tab, and locate the page for your PeopleSoft application (for example, HCM Update Image Home Page). Expand the Installation Documentation section to locate the guide.

*Use the following guidelines to change the Elasticsearch passwords.

See PeopleSoft Deployment Packages for Elasticsearch Installation (PeopleTools 8.56), on the Elasticsearch Home Page, My Oracle Support Doc ID 2205540.2. Select the tab Elasticsearch on PeopleTools 8.56, and look in the table under Installation and Implementation.

  1. Log in to the instance for the PeopleSoft application using SSH or PuTTY.

    See the section Logging In to Your Instance Using SSH in this tutorial.

  2. Change to user esadm1, and supply the default password 0radmin. You must change the password the first time you log in.

    sudo su - esadm1
  3. Change directory to /opt/oracle/psft/pt/ES/bin.

  4. Use the elasticsearchuser script to change the password for a user. For example, to change the password for the user people, enter:

    ./elasticsearchuser adduser people

    See PeopleSoft Deployment Packages for Elasticsearch Installation (PeopleTools 8.56), Using the Elasticsearchuser Script.

  5. At the script prompt, answer yes, and then enter the default password, peop1e.

    User Exists. Do you wish to change the password?(Y/N) Y
    Enter your old password:
  6. At the prompt, enter the new password twice.

    Enter new password:
    Confirm new password:
    Password for people changed.
  7. Enter this command, and locate the Elasticsearch process ID in the list of results:

    ps –ef | grep elas
  8. Stop the process with this command, substituting the Elasticsearch process ID from the previous step for <pid>:

    kill <pid>
  9. Start Elasticsearch with the command: nohup ./elasticsearch &

  10. Sign into the PeopleSoft application in a browser, and select PeopleTools, Automated Configuration Management, ACM Template, Template Definition.

  11. Search for and open SEARCH_TEMPLATE.

    See PeopleSoft Deployment Packages for Elasticsearch Installation (PeopleTools 8.56), Using the Automated Configuration Management SEARCH_TEMPLATE.

  12. Select the Configure Search Instance plugin and click the Properties icon.

  13. Change the value for env.node1_search_read_password to the new password.

  14. Save the template and click Execute to begin the program run.

  15. On the Configuration Template Definition page for the SEARCH_TEMPLATE, select the Deploy Search Definition plug-in and click Execute to begin the deployment.

  16. Select PeopleTools, Search Framework Administration, Search Instance.

  17. On the Search Instance Properties page, use the test buttons to verify that the password change was successful.

    If you changed the read (Proxy) user, test by clicking Proxy Login. If you changed the admin user password, test by clicking Test Login.

Want to Learn More?