Checking the log files of components

The following table summarizes a list of log files that are generated by a specific component. For monitoring any component's tasks, check the logs that are located in their specific location.

Table 1. Log files location
Component Logs location Log files name format
IBM® AD Configuration Server <IBM ADDI Installation Folder>\IBM Application Discovery Configuration Service\log\
  • server.log
  • ibmapplicationdiscoveryconfigurationadminservice-stderr.<date>.log
  • ibmapplicationdiscoveryconfigurationadminservice-stdout.<date>.log
  • ibmapplicationdiscoveryconfigurationservice-stderr.<date>.log
  • ibmapplicationdiscoveryconfigurationservice-stdout.<date>.log
  • ezservice-daemon.<date>.log
  • ws-service-daemon.<date>.log
IBM AD Build Client <IBM AD Build Client installation folder>\Bin\Release\ IBM AD Build Client can be invoked in batch mode to create a new project in background. The log for the New project in background has the following name format NewProjInBackLog_<timestamp>.log.
<Project's Folder> IBM AD Build Client can be invoked in batch mode to run a build (full build). The log for the Build in background process has the following name format Project'sName_<timestamp>.txt.
IBM AD Build Client can be invoked in batch mode to keep the information stored in repository up-to-date. The logs for the Make process have the following format:
  • BatchMakeStatusFile_<timestamp>.txt
  • Project'sName_<timestamp>.txt
IBM AD Build Client can automatically add all files from a given physical folder to a virtual one (similar to Add all files from folder option that can be found in GUI Mode). The log for this process has the following format UpdateInBackgroundLog_<timestamp>.txt.
IBM AD Build Client can be invoked in batch mode to update API Resolutions. The log for this process has the following format UpdateApiResolutions_<timestamp>.txt.
IBM AD Build Client can be invoked in batch mode to save project properties from command line interface. The log for this process has the following format SaveProjPropInBackgroundErrFile_<time_stamp>.log.
IBM AD Build Client can be invoked in batch mode to perform a full build on the project. The status and progress information can be found in the log that is labeled BatchBuildStatusFile.txt.
<Project's Folder>\reports\ BuildErrorReport_<timestamp>.html is generated by any build performed in IBM AD Build Client.
<Project's Folder>\Synchronize\
  • ConfigFileValidation_<timestamp>.log
  • SynchronizeMembersExtendedInfo_<timestamp>
  • SynchronizeMembersProgress_<timestamp>
  • SynchronizeMembersSummary_<timestamp>
<Project's Folder>\MVS\Logs\<zOS Connection's Name>
  • MFImport_<timestamp>.log
  • MFErrors_<timestamp>.log
<IBM ADDI Installation Folder>\IBM Application Discovery Build Client\Bin\Release\CCS_Interaction_Logs\ The log for the interaction with IBM AD Configuration Server can be found under CCSErrors_<timestamp>.log.
<Path For The Retrieved Members>\Mainframe Library Members\
  • BackgroundUpdateMFMemberSources_<timestamp>.log
  • SummaryUpdateMFMemberSources_<timestamp>.log
  • SummaryGetMFMemberSources_<timestamp>.log
<Path For The Retrieved Members>\Mainframe Library Members\<zOS Connection's Name>
  • GetMFMemberSources_<timestamp>.log
  • UpdateMFMemberSources_<timestamp>.log
IBM AD Build Configuration <IBM AD Build Client installation folder>\Bin\Release\Log\ ADBuildConfiguration_<timestamp>.log
IBM Application Discovery GraphDB <IBM ADDI Installation Folder>\IBM Application Discovery Batch Server\orientdb\log\ ezservice-daemon.<date>.log
<IBM ADDI Installation Folder>\IBM Application Discovery Batch Server\orientdb-community-x.x.x_ezpatch1\log\ orient-server.log
IBM AD Validation Server <IBM AD Build Client installation path>\bin\Release\IBMApplication DiscoveryValidationServer\Logs\
  • ValidationServiceActivity_<number>.log
  • ValidationServiceStatus_<timestamp>.log
<Project's Folder>\Validation\ ValidationThroughPDS_GenerateIncludePaths_<timestamp>.log
<Project's Folder>\Synchronize\  
Authentication Server (DEX) <IBM ADDI Installation Folder>\Authentication Server (DEX)\ dex.log
IBM AD File Service <IBM ADDI Installation Folder>\IBM Application Discovery File Service\ .log
IBM AD Manual Resolution Service <IBM ADDI Installation Folder>\IBM Application Discovery Manual Resolutions Service\log\ manualres.log
IBM AD Mainframe Projects <IBM ADDI Installation Folder>\IBM Application Discovery Mainframe Projects Service\log\ mfprojs.log
IBM AD Batch Server <IBM ADDI Installation Folder>\IBM Application Discovery Batch Server\log\
  • server.log
  • ibmapplicationdiscoverybatchservice -stdout.<date>.log
  • ibmapplicationdiscoverybatchservice -stderr.<date>.log
  • ibmapplicationdiscoverywebservice -stdout.<date>.log
  • ibmapplicationdiscoverywebservice -stderr.<date>.log
  • server-daemon.<date>.log
  • webservice.log
  • webservice-daemon.<date>.log
  • status.log
  • ProjectName-projectDBVersion.log
  • gdbTool.log
  • rb.log
IBM AD Search Service <IBM ADDI Installation Folder>\IBM Application Discovery Search Service\log\ search.log
IBM AD Cross Applications Service <IBM ADDI Installation Folder>\IBM Application Discovery Cross Applications Service\log\ cross.log
IBM AD Web Services <IBM ADDI Installation Folder>\IBM Application Discovery and Delivery Intelligence\IBM AD Web Services\wlp\usr\servers\ad_server\logs .log
IBM AD Analyze Client <Eclipse Workspace folder>\.metadata\.ez\log\
  • ez.log
  • ez.<date>.log
<Eclipse Workspace folder>\.metadata\ .log