Additional Configuration Requirements if Already Using Log Analytics for PeopleSoft

Topics:

Perform Additional Requirements for Discovering PeopleSoft Applications
Perform Additional Requirements for Discovering PeopleSoft Applications and Continued Use of Log Analytics

The benefits of upgrading the PeopleSoft configuration are as follows:

Availability and performance metrics for the application and its components right out of the box.
Oracle Management Cloud provides a PeopleSoft Monitoring Dashboard set with several predefined dashboards that provide overview of the PeopleSoft application and the health of its components.

The entity type PeopleSoft Application is deprecated, and is not supported for upgrade.

Perform Additional Requirements for Discovering PeopleSoft Applications

If you have been using Log Analytics for PeopleSoft using cloud agents released in 1.39 or earlier, review the new requirements in order for PeopleSoft entity discovery and metric collection.

PeopleTools version supported and typical workflow for setting up: Set Up the Environment
Perform discovery of the entire PeopleSoft application including its components and underlying infrastructure: Install a Cloud Agent for Discovery
The Oracle Management Cloud Agent must be installed on either a host with a PeopleSoft Application Server domain or a host with a Process Scheduler domain.
Discover PeopleSoft applications and collect PeopleSoft log data from discovered entities: Perform PeopleSoft Specific Tasks
After you've set up the environment for monitoring PeopleSoft with Oracle Management Cloud, verify the setup by conducting a few simple tests: Verify the Setup

Perform Additional Requirements for Discovering PeopleSoft Applications and Continued Use of Log Analytics

In order to leverage Oracle Management Cloud Log Analytics for PeopleSoft, Cloud Agents are required on all PeopleSoft-related hosts as the Cloud Agent is responsible for collecting log data from each host. Since you've been using Log Analytics for PeopleSoft, then you already have an earlier version of Cloud Agent (pre release 1.40) installed on all PeopleSoft related hosts.

While Oracle highly recommends upgrading Cloud Agents to the latest Cloud Agent version (1.40 or higher) to gain the latest features available it is not required in order to continue using OMC LA for PeopleSoft. See What's New in Oracle Management Cloud for PeopleSoft.

Install Cloud Agent release 1.40 on one of the hosts where the PeopleSoft Server Domain is installed. See Install a Cloud Agent for Discovery.
Perform discovery of the PeopleSoft Application. Be sure to select the version 1.40 cloud agent you installed in step one. See Add PeopleSoft Entities.
From each host where a prerelease 1.40 Cloud Agent is collecting PeopleSoft log data, delete the corresponding PeopleSoft entities identified with that local pre-release 1.40 Cloud Agent by issuing this OMCLI command:
```
omcli delete_entity agent <input_json_file>
```
Note that if you do not delete the entity on the pre-release 1.40 Cloud Agent, metric collection errors would appear in the cloud agent log files.

Do not execute this command on the host where the 1.40 (or later) Cloud Agent was installed in step one.
```
{
    "entities": [    
       {
        "name": "PSAPPSRV_host1",
        "type": "omc_oracle_psft_appserv"
       },
       {
        "name": "peoplesoft_host1",
        "type": "omc_oracle_psft_pia"
       },
       {
        "name": "PRCSDOM_host1",
        "type": "omc_oracle_psft_prcs"
       }
    ]
}
```
Create a uses association from each newly discovered PeopleSoft entity to its respective host.

Note: You do not need to create a uses association for any PSFT entities that reside on the host from where Cloud Agent 1.40 performed PSFT discovery. The association between the PSFT entities and its underlying host is automatically done during discovery.

Navigate to Administration > Discovery > Entity Associations.

See Work With Entity Associations in Using Oracle Log Analytics.
Verify all uses associations between PeopleSoft components and underlying hosts have been configured properly. Navigate to the newly discovered PSFT Application > Related Members page.

If any PSFT Component rows appear in the table on the Related Members page doesn’t display a host name as a clickable link, then the uses association configuration was not done properly (it could also mean that host monitoring is not enabled for that host entity). If this is the case, then ensure that host monitoring is enabled for that host entity as well as ensure that the uses association was done properly.