Troubleshoot Oracle Management Cloud for PeopleSoft

Discovery Incomplete or Unsuccessful

Ensure that you have completed the prerequisite tasks before discovering PeopleSoft entities. See Perform Prerequisite Tasks.
If you have refreshed the current environment from another production environment, but the environment entity details are not refreshed for the current environment, then:
1. Run the Data Mover script perfmonpurgeall.dms and restart the domains. After the purge completes and the monitoring system is restarted, all the active agents and systems will re-register and obtain a new ID from the PPMI monitor Servlet.
2. Shut down the performance monitoring system - App, Web and PRCS servers.
3. Log in to Data Mover with a valid User ID.
4. Run the Data Mover script perfmonpurgeall.dms that is available in the location <PS_HOME>/scripts. This should be run on monitoring database. The System ID and Agent ID sequences will restart from 1.
5. Start all the servers.

Cannot detect any metric data

Retrieve latest entity information for discovery.
- Refresh the Performance Monitor Data
Check your SSL and connectivity settings.
- Setup Integration Broker
- Configure the Target Location for SSL
SSL Handshake errors: Ensure that you provided the host name or the IP address as available in your SSL certification. Check the server certificate CN to confirm this information. See Configure the Target Location for SSL and What to do if custom or demo server certificates used for PeopleSoft Servers.
WSDL Node related: missing endpoint URL.
- Make sure "Secure Target Location" is set as part of IB configuration.
WSDL Node related: Verify that the username associated with the WSDL node exists in the database and that it has access to the service operation.
To resolve error "UserName not defined in database" perform the following:
1. Open the ANONYMOUS node definition.
2. Change the default User ID from PSADMIN to a valid PS OPRID which has permission to invoke GETWSDL operation.
Ensure that you are using an Oracle Management Cloud Agent version 1.40 or later:
- Install a Cloud Agent for Discovery
Triaging issues for discovery jobs with status: failed, warning or error.
From the Discovery Job Status page, you can view the current status (failed, warning, or error) of entity addition attempts.
- For entity discovery jobs with a Failed or Warning status:
  From the Action column, click Retry to view the Add Entity page with parameters (except monitoring credentials) that were used when the entity was originally added. This allows you to quickly make any corrections and resubmit the entity discovery job without having to enter all the parameters.

Log Collection is incomplete

Go to Oracle Log Analytics Home and verify the log collection. In case of error, you can take the following corrective actions:

Ensure that host monitoring is enabled.
- See Enable Host Monitoring
Ensure that the path of the logs in the log sources is correct.
- To change the location of the logs, or to provide an additional path from where the logs of a specific log source can be collected, see Change Default Log Directories for PeopleSoft Log Sources.
Verify that the cloud agent user has access to the logs. Make the log files readable to the Oracle Management Cloud agents.
- See the section Requirement for Logs Collection on Unix in the topic Generic Prerequisites for Deploying Oracle Management Cloud Agents in Installing and Managing Oracle Management Cloud Agents.

Have some issue with the licensing

Navigate to Administration > Entity Configuration > Licensing.
Ensure that the Log Collection toggle button is ENABLED for your PeopleSoft entity.

See Enable License Editions in Getting Started with Oracle Management Cloud.

What to do if custom or demo server certificates used for PeopleSoft Servers

In case, custom or demo server certificates are used on the servers provided under Secure Target Location in Integration Broker service configuration, the cloud custom certificate must be imported to the cloud agent trust store:

Obtain the certificate:

openssl s_client -connect <machinename>:<ssl_port> </dev/null | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'> <location>/psftpia.cer

Use omcli to add the certificate to the Agent truststore:
```
omcli secure add_trust_cert_to_jks -trust_certs_loc <location>/psftpia.cer
```
Note:
You can use the keytool utility to manage the content of the truststore. By default the password is welcome.
Restart the cloud agent after adding the certificate. See omcli Command Options in Working with Oracle Management Cloud.

In releases prior to June 2019, the certificate was loaded to the JRE trust store, and each time again after the agent update. As of June 2019, you can directly upload the certificate to the agent trust store. Since the agent trust store is maintained during agent update, you will not be required to refresh the agent trust store with the certificate after the update.

Discovering Multi-Server WebLogic domain

Multi-server WebLogic domain discovery is a two step manual process performed after the PeopleSoft application has been discovered. Discovery of WebLogic domains is currently not done automatically when PeopleSoft Applications are deployed on multi-server WebLogic domain. PSFT PIA entities are the WebLogic equivalent from PeopleSoft point of view, and those will be discovered. To discover such WebLogic domain, follow the steps below.

Manually discover and create required associations:

WebLogic domain can be manually discovered as stand alone WebLogic discovery and required association can be created.

Discover WebLogic domains, for more information see: Add Oracle WebLogic Server/Domain

Create the following associations:

Source Entity	Associate Type	Destination Entity
PeopleSoft Application (Composite entity)	Contains	WebLogic Domain
Each PIA entity	Uses	Respective WebLogic Server entity

For more information see: Define Associations Between Entities.