Perform PeopleSoft Specific Tasks

Discover PeopleSoft applications and collect PeopleSoft log data from discovered entities.

To perform these tasks, you must have the Oracle Management Cloud Administrator role.

Add PeopleSoft Entities

Discover PeopleSoft entities using the Oracle Management Cloud console or with the command-line interface omcli.

Topics:

Discover a PeopleSoft Application with the Console

From the Oracle Management Cloud main menu, navigate to Administration > Discovery > Add Entity.
From the Entity Type drop-down, select PeopleSoft Application.
From the Discovery Type drop-down, select Oracle Database or JSON File.
Select Oracle Database if the PeopleSoft entity uses Oracle Database as the back-end database and you want to provide the database details in the console. When you select this option, the details about all the dependent entities are automatically extracted from the database.

Select JSON File if you are using any other database or if you want to provide the details of all the PeopleSoft entities manually. You can select this mode of discovery even for Oracle Database.
Note:
- For discovery using the JSON file, you must install cloud agent version 1.54 or later.
- The database is not discovered when you use the JSON file to specify the details of the entities. You must discover the database separately.
Enter the Entity Name for the composite entity that you're creating, using up to 256 characters.
Provide the database or entity information:
- For Oracle Database discovery type:
  
  From the Database Host list, select the host where the PeopleSoft Database is installed and running, and enter the Database Service Name containing the PeopleSoft schema. The default database port is automatically available in the Database Port field. You can change it, if required.
  
  If your database entity is already discovered, then to skip the discovery of the database, under Discover Database, select false. The discovery job will however obtain the database entity information, validate the entity, and ensure that the database is included in the PeopleSoft Application composite. Note that if you choose to associate the logs automatically in step 9, then the log data from the database is automatically associated with PeopleSoft entity.
- For JSON File discovery type:
  
  Create the JSON file with the details of all the PeopleSoft entities and save it on the host where the Cloud Agent is installed. Make a note of the file name and its path, for example, /oracle/ptusers/psadm2/psft/manual_discovery.json. See Create JSON File for Manual Discovery.
  
  In the Discovery JSON File Name field, enter the name of the JSON file that you created earlier with a fully qualified path. Make sure that the agent user has READ permission to the JSON file.
Select a Cloud Agent from a host with a PeopleSoft Application Server domain. This cloud agent must be version 1.40 or later.
Under Monitoring Credentials, provide the login credentials and select the Database Role from the drop-down.
Select the radio button for Discover Process Monitor and provide the required user credentials.
By choosing to discover Process Monitor, you gain access to performance data on submitted PeopleSoft processes, like the rate of completed processes over time and the status of active processes.
If you choose not to discover Process Monitor with the PeopleSoft Application composite discovery for reasons like the process monitor is not configured yet, then you can refresh the composite entity at a later point when you add the Process Monitor.
Select the radio button for Discover Elasticsearch and provide the required user credentials. Ensure that you're using the cloud agent from version 1.42 or later.
Similar to Process Monitor, if you choose not to discover Elasticsearch with the PeopleSoft Application composite discovery for reasons like Elasticsearch is not configured yet, then you can refresh the composite entity at a later point when you add Elasticsearch.
Under Entity Attributes, select the Tag only this entity radio button and select the license edition from the drop-down list, either Standard or Enterprise.
For details about Oracle Management Cloud offerings in Standard and Enterprise editions and the price implications, see Oracle Management Cloud Offerings in Getting Started with Oracle Management Cloud.
To associate the relevant log sources automatically with PeopleSoft entities for log collection, toggle the Associate Logs button. Once enabled, Oracle Management Cloud collects log data from the hosts on which the cloud agent is installed. If you're already using Oracle Log Analytics for PeopleSoft, then see Additional Configuration Requirements if Already Using Log Analytics for PeopleSoft.
Optionally, you can create tags that define additional relationships between the Oracle PeopleSoft entities. A tag is a key-value pair that can be assigned to an entity. Tags offer enhanced categorizing, searching, and grouping capabilities of the entities with which they are associated. Setting tags for entities allows you to logically organize the entities according to the properties that you’ve defined. For example, you may want to use the same tag for all entities that are physically in the same location, or entities that are part of the same custom logical group. The Tag all members option applies to composite entities and allows you to specify the same tag to all members discovered under this entity. See Create and Set Tags for Entities in Working with Oracle Management Cloud.
Click Add Entity. You are returned to the Entity Addition Job Status page. The entity addition job name will appear in the table of entities on the page.
From the summary, you can also note the details of the discovery operation, and verify that you've completed the required prerequisite tasks.
Refresh the status and wait for the discovery job to complete. If the discovery job failed, then update the parameters that caused the failure and re-run the discovery.
Verify that the following entities are discovered:
- PeopleSoft Application
- PeopleSoft Application Server Domain
- PeopleSoft Process Scheduler Domain
- PeopleSoft Pure Internet Architecture (PIA)
  - Oracle WebLogic Domain
  - Oracle WebLogic Server
- Process Monitor (if chosen to be added at PeopleSoft discovery time)
- Elasticsearch (if chosen to be added at PeopleSoft discovery time)
- Oracle Database Instances (If chosen to be discovered with the current discovery configuration)
From Infrastructure Monitoring Home, click the OMC Navigation icon > click Monitoring > click Entities > click the link on the PeopleSoft Application composite entity > click Members tab. Verify that the above entities are listed under the members.

Create JSON File for Manual Discovery

To manually provide PeopleSoft entity details, log in to the host where the cloud agent is installed, create a JSON file as in the example below:

{
    "version": "1.0",
    "databaseType": "Oracle",
    "databaseHostName": "psftdb.example.com",
    "databaseServiceName": "PSFTSVC007",
    "psStatusToolsRel": "8.56",
    "psStatusPtPatchRel": "4",
    "psReleaseAppType": "Financials/SCM",
    "psReleaseLabel": "Financials/SCM 9.20.00.420",
    "psftAppservDom": [
        {
            "PM_DOMAIN_NAME": "APPDOM",
            "PM_DOMAIN_DIR": "/oracle/ptusers/psadm2/psft/pt/8.56/appserv/APPDOM",
            "PM_HOST_PORT": "psftapp1.example.com:9033",
            "PM_JMX_RMI_PORT": "10100",
            "PTPMJMXUSER": "admin",
            "PTPMJMXPSWD": "{V1.1}XXXXXXXXXXXXXX=="
        },
        {
            "PM_DOMAIN_NAME": "APPDOM2",
            "PM_DOMAIN_DIR": "/oracle/ptusers/psadm2/psft/pt/8.56/appserv/APPDOM2",
            "PM_HOST_PORT": "psftapp2.example.com:9066",
            "PM_JMX_RMI_PORT": "20100",
            "PTPMJMXUSER": "admin",
            "PTPMJMXPSWD": "{V1.1}XXXXXXXXXXXXXX=="
        }
    ],
    "psftPrcsDom": [
        {
            "PM_DOMAIN_NAME": "PRCSDOM",
            "PM_DOMAIN_DIR": "/oracle/ptusers/psadm2/psft/pt/8.56/appserv/prcs/PRCSDOM",
            "PM_HOST_PORT": "psftprcs1.example.com:9067",
            "PM_JMX_RMI_PORT": "10200",
            "PTPMJMXUSER": "admin",
            "PTPMJMXPSWD": "{V1.1}XXXXXXXXXXXXXX=="
        }
    ],
    "psftPIA": [
        {
            "PM_DOMAIN_NAME": "peoplesoft",
            "PM_DOMAIN_DIR": "/oracle/ptusers/psadm2/psft/pt/8.56/webserv/peoplesoft",
            "PM_HOST_PORT": "psftpia1:8000:8443",
            "PTPMJMXUSER": "system",
            "PTPMJMXPSWD": "{V1.1}XXXXXXXXXXXXXX=="
        }
    ],
    "psIbWsdlName": "PROCESSREQUEST.1",
    "psIbSvcSetupTgtLocation": "http://psftpia1.example.com:8000/PSIGW/PeopleSoftServiceListeningConnector/PSFT_LOCAL",
    "psIbSvcSetupSecTgtLocation": "https://psftpia1.example.com:8443/PSIGW/PeopleSoftServiceListeningConnector/PSFT_LOCAL",
    "psPtsfSrchEngnAdminSrvUrl": "http://psftes.example.com:9200/"
}

Note:

The database is not discovered when you use the JSON file to specify the details of the entities. You must discover the database separately.

The properties and their values specified in the JSON file are as described below:

Property Name	Description	Source of the Value	Example Value
`version`	JSON data version. Current supported version is 1.0.	Fixed value 1.0 for current	`1.0`
`databaseType`	PeopleSoft back end database type	-	`Oracle` for Oracle Database
`databaseHostName`	Host name where the database is installed	-	`dbhost.example.com`
`databaseServiceName`	Database Service name, if applicable	-	`PSFTSVC007`
`psStatusToolsRel` `psStatusPtPatchRel`	PeopleTools version (major and minor)	`SELECT TOOLSREL, PTPATCHREL from PSSTATUS;`	`8.56` `4`
`psReleaseAppType`	PeopleSoft Application type	`SELECT SUBSTR(RELEASELABEL, 1, INSTR(RELEASELABEL, ' ')) AS APP_TYPE FROM PSRELEASE WHERE ROWNUM = 1 ORDER BY RELEASEDTTM DESC;`	`Financials/SCM`
`psReleaseLabel`	PeopleSoft Application type with version	`SELECT RELEASELABEL FROM PSRELEASE WHERE ROWNUM = 1 ORDER BY RELEASEDTTM DESC;`	`Financials/SCM 9.20.00.420`
`psftAppservDom` Domain properties: `PM_DOMAIN_NAME` `PM_DOMAIN_DIR` `PM_HOST_PORT` `PM_JMX_RMI_PORT` `PTPMJMXUSER` `PTPMJMXPSWD`	Array of application server domains Description of domain properties: Domain name as listed in psadmin Domain directory Domain host:port JMX RMI port JMX user name Encrypted JMX user password	`SELECT DISTINCT PM_DOMAIN_NAME, PM_DOMAIN_DIR, PM_HOST_PORT, PM_JMX_RMI_PORT, PTPMJMXUSER, PTPMJMXPSWD FROM PSPMAGENT PA, PS_PTPMJMXUSER PU WHERE PA.PM_AGENT_TYPE = 'PSMONITORSRV' AND PA.PM_DOMAIN_TYPE = '01' AND PU.PM_AGENTID = PA.PM_AGENTID;`	-
`psftPrcsDom` Domain properties: `PM_DOMAIN_NAME` `PM_DOMAIN_DIR` `PM_HOST_PORT` `PM_JMX_RMI_PORT` `PTPMJMXUSER` `PTPMJMXPSWD`	Array of process scheduler domains Description of domain properties: Domain name as listed in psadmin Domain directory Domain host:port JMX RMI port JMX user name Encrypted JMX user password	`SELECT DISTINCT PM_DOMAIN_NAME, PM_DOMAIN_DIR, PM_HOST_PORT, PM_JMX_RMI_PORT, PTPMJMXUSER, PTPMJMXPSWD FROM PSPMAGENT PA, PS_PTPMJMXUSER PU WHERE PA.PM_AGENT_TYPE = 'PSMONITORSRV' AND PA.PM_DOMAIN_TYPE = '04' AND PU.PM_AGENTID = PA.PM_AGENTID;`	-
`psftPIA` Domain properties: `PM_DOMAIN_NAME` `PM_DOMAIN_DIR` `PM_HOST_PORT` `PTPMJMXUSER` `PTPMJMXPSWD`	Array of PIAs Description of domain properties: Domain name as listed in psadmin Domain directory Domain host:port JMX user name Encrypted JMX user password	`SELECT DISTINCT PM_DOMAIN_NAME, PM_DOMAIN_DIR, PM_HOST_PORT, PTPMJMXUSER, PTPMJMXPSWD FROM PSPMAGENT PA, PS_PTPMJMXUSER PU WHERE PA.PM_AGENT_TYPE = 'WEBRESOURCE' AND PA.PM_DOMAIN_TYPE = '02' AND PA.PM_AGENTID = PU.PM_AGENTID;`	-
`psIbWsdlName`	WSDL name for process monitor	`SELECT IB_WSDLNAME FROM PSIBWSDLDFN WHERE IB_SERVICENAME = 'PROCESSREQUEST';`	`PROCESSREQUEST.1`
`psIbSvcSetupTgtLocation` `psIbSvcSetupSecTgtLocation`	Integration broker target locations (Secure target location is used)	`SELECT IB_TGTLOCATION, IB_SECTGTLOCATION FROM PSIBSVCSETUP;`	`http://psftpia1.example.com:8000/PSIGW/PeopleSoftServiceListeningConnector/PSFT_LOCAL` `https://psftpia1.example.com:8443/PSIGW/PeopleSoftServiceListeningConnector/PSFT_LOCAL`
`psPtsfSrchEngnAdminSrvUrl`	Elasticsearch admin server URL	-	`http://psftes.example.com:9200/`

Discover a PeopleSoft Application with omcli

Using the command-line interface omcli and PeopleSoft specific JSON files, you can discover the PeopleSoft composite entity.

See Add Entities Using JSON Files in Using Oracle Infrastructure Monitoring.

Download the PeopleSoft specific sample JSON files omc_oracle_psft_sample.json and omc_oracle_psft_sample_creds.json from Sample JSON Files (zip file). See Download and Customize Oracle Infrastructure Monitoring JSONs in Using Oracle Infrastructure Monitoring.

PeopleSoft JSON Files and Properties

Customize the sample JSON files with the properties suitable for your PeopleSoft setup.

Definition File: omc_oracle_psft_sample.json

name: PeopleSoft Entity Name
displayName: This is PeopleSoft Entity Display Name shown in the Infrastructure Monitoring UI.
timezoneRegion: Time Zone Example: PDT, GMT, etc
omc_psft_db_host: Fully-qualified Host Name where the Oracle Database is installed.
omc_psft_db_port: Oracle Database port
omc_psft_db_service_name: Oracle Database Service Name

Credential File: omc_oracle_psft_sample_creds.json

For DBCreds:
- DBUserName: Your Database User Name. Specify the user who is granted the access in the pre-requisite step Grant Privileges for Monitoring.
- DBPassword: Your Database Password
- DBRole: Your Database User Role. By default, this is NORMAL.
For MonitorCreds:
- user_name: PeopleSoft Administrator role user
- password: PeopleSoft Administrator role user password
For AliasCredential:
- Alias: Elasticsearch monitoring user name
- Password: Elasticsearch monitoring user password

Review Job Status for Discovery Results

After you add the PeopleSoft Application entity, you are automatically re-directed to the Discovery Job Status page.

Alternatively, navigate to Administration > Discovery > Discovery Job Status.
The entity addition job name will appear in the table of entities on the page.
From the summary, note the details of the discovery operation, and verify that you've completed the required prerequisite tasks.
Refresh the status and wait for the discovery job to complete.
Note the status (failed, warning, or error) of the entity discovery attempts. Click the status to view the summary of the discovery job.
If the discovery job failed, then update the parameters that caused the failure and re-run the discovery. For the status Failed or Warning, Retry link appears in the Action column.
Click Retry. The Add Entity page opens with the parameters that were used when the entity was originally added. Add the monitoring credentials, update the entity parameters, and re-submit the request for discovery.

Collect Log Data from PeopleSoft Entities

Collect log data from PeopleSoft entities for which you have enabled log association during discovery. Note that the logs are collected only from those hosts on which the cloud agent is installed.

Oracle PeopleSoft Entity Type	Logs Collected
PeopleSoft Application Server Domain	PeopleSoft Application Tuxedo Access Logs PeopleSoft Application Tuxedo User Logs PeopleSoft Application server domain Application Server (APPSRV) Process Logs PeopleSoft Application server domain Monitor Server (MONITORSRV) Process Logs PeopleSoft Application server domain Watch Server (WATCHSRV) Process Logs
PeopleSoft Pure Internet Architecture	PeopleSoft Integration Gateway Error Logs PeopleSoft Integration Gateway Message Logs PeopleSoft WLS Server Access Logs PeopleSoft WLS Server Logs PeopleSoft WLS Server STDOUT Logs PeopleSoft WLS Servlet Logs
PeopleSoft Process Scheduler Domain	PeopleSoft Analytics Engine Server Logs PeopleSoft Application Analytics Engine Server Logs PeopleSoft Master Scheduler Server Logs PeopleSoft Process Scheduler App Engine Server Logs PeopleSoft Process Scheduler Distribution Agent Logs PeopleSoft Process Scheduler Master Scheduler Logs
Oracle Database	Database Alert Logs Database Trace Logs Database Incident Dump Files

However, you can change the association of log sources with entities, add more log sources as suitable for your application, or remove some from the list of log sources that are automatically enabled for collection. See Work With Entity Associations in Using Oracle Log Analytics.

For troubleshooting solutions for log collection in your PeopleSoft environment, see Troubleshoot Oracle Management Cloud for PeopleSoft.