Where to Locate the Logs for PeopleSoft Search Framework and SES

by Apurva T. on April 27, 2014

in PeopleSoft Administration

You will need access to the PeopleSoft Search Framework and SES logs to troubleshoot issues related to SES or search. The logs will help you troubleshoot issues related to installation or maintenance of the same.

Here are some of the logs, you will need to look at in case an issue arises:

PEOPLESOFT INTEGRATION BROKER 

  1. errorLog.html (in <PS_CFG>/webserv/<DOMAIN_NAME>/applications/peoplesoft/PSIGW.war) – It shows any errors encountered in communications between PeopleSoft and SES msgLog.html (in <PS_CFG>/webserv]/<DOMAIN_NAME>/applications/peoplesoft/PSIGW.war) -(need to go into integrationGateway.properties and set ig.log.level=5 for this to work). Then you will see all communications between PeopleSoft and SES

PIA
PIA_stdout.log (or NTService log on Windows) (in <PS_CFG>/webserv/<DOMAIN_NAME>/servers/PIA/logs) – This log may show errors in gateway communication (note that you want to look at the logs used by the Gateway)

Appserver
APPSRV_MM_DD.log (in <PS_CFG>/appserv/<DOMAIN_NAME>/LOGS – This log may show integration-related errors

 

SES 11.2.2.2 (Mid-Tier Logs (Weblogic))

  1. search_server1_yyyy_MM_dd_hh_mm.log  and search_server1-diagnostic.log (in  <SES_MIDDLETIER_HOME>/ user_projects/domains/search_domain/servers/search_server1/logs) -These are the WebLogic logs for the search server used by SES. It shows the machine name and port# that the SES Web server is using and you can tell whether it started successfully, and whether any errors are logged.
  2. access.log (in <SES_MIDDLETIER_HOME>/ user_projects/domains/search_domain/servers/search_server1/logs) – It shows all the http requests coming in to the mid-tier WebLogic server

Crawler/Index Build Logs
search.crawler.i*.MMDDHHMM.log  (in <SES MIDDLETIER_HOME>/logs/crawler/crawler) – Shows crawling results and how many indexes were built.  Search “Crawling Results” for a summary.

 

SES 11.1.2.2 (Mid-Tier Logs (WebLogic))

  1. AdminServer_yyyy_MM_dd_hh_mm.log (in <SES_HOME>/search/base_domain/servers/AdminServer/logs) – This is the WebLogic log for the web server used by SES.It shows the machine name and port# that the SES Web server is using and you can tell whether it started successfully, and whether any errors are logged.
  2. base_domain.log (in <SES_HOME>/search/base_domain/servers/AdminServer/logs) – Shows additional WebLogic logging info (in conjunction with AdminServer_yyyy_MM_dd_hh_mm.log_
  3. access.log (in <SES_HOME>/server/search/base_domain/servers/AdminServer/logs) – Shows all the http requests coming in to the mid-tier WebLogic server
Also Read:  Cannot Undeploy Search Definitions. Receive Error "Service Exception: ns2:CreatableAdminObjectFault : EQA-11000: The object with key .... was not found"

 

Crawler/Index Build Logs

  1. i1ds*.MMDDHHMM.log (in <SES>/oradata/ses/log) – It shows crawling results and how many indexes were built. Search “Crawling Results” for a summary.
  2. search_i1ds*.log (in <SES_HOME>/ctx/log) – Doesn’t seem as useful as above log, but it does show how many indexes were built.
  3. opt*.log (in <SES_HOME>/ctx/log) – This is the “index optimization” log

Oracle Database Logs
1. listener.log (in <SES_HOME>/log/diag/tnslsnr/<MACHINE-NAME>/listener/trace)
This shows the last time the SES DB started and what machine name/port# it is listening on

{ 0 comments… add one now }

Leave a Comment

Previous post:

Next post: