Appendix F. Troubleshooting aids 567
Table F-6 Key collection specific configuration files
Commands
Table F-7 lists some of the key commands available with a brief description of
their function and examples where appropriate. As mentioned earlier, the
cmdline_yyyymmdd.log files in the $ES_NODE_ROOT/logs directory has
information about the commands executed in the OmniFind environment.
Table F-7 Troubleshooting commands
Name Description
<collection id>.<crawler_id> Crawler configuration
<collection id>.parserdriver Parser configuration
<collection id>.runtime.nodeN Runtime/search configuration
<collection id>.indexer Main index build configuration
<collection id>.indexer.delta Delta index build configuration
<collection id>.stellent Stellent file parser configuration
<collection id>.casprocessor Optional custom analysis text annotator
configuration
ccl.properties CCL settings
collection.properties Collection settings
runtime_generic.properties Search runtime settings
sso.properties Single sign-on settings
appids.properties Search applications defined
parserTypes.cfg Defines rules for mapping file extensions or
MIME types to parser types.
Name Description
esadmin check Lists all the active processes, as shown in
Figure F-1 on page 569.
esadmin rds Reads RDS information. Use esadmin rds help for
details on this command, as shown in Figure F-2 on
page 569
568 IBM OmniFind EE V8.4: Configuration and Implementation Scenarios
esadmin report .... There are many options on this command, including
sessions, nodes, collections, and interfaces. Use
esadmin report help for details on this command,
as shown in Figure F-3 on page 570.
esadmin session discovery
discover -api <apiname>
<options>
There are many options to this command, as shown
in Example F-1 on page 570.
dumpstore Prints the contents of the RDS and Trevistore.
Figure F-4 on page 573 shows the output of
dumpstore help.
It does not print the contents of the index.
Example F-2 on page 573 shows the output of RDS
where the crawled data includes Notes Domino
(native ACLs), DB2 Content Manager (native ACLs),
and DB2 (no security). The key elements are
SecurityACLs and NativeACLs. You will note that
SecurityACLs is PUBLIC=”NO” and NativeACLs has
the appropriate access control list information for
Notes Domino and DB2 Content Manager. For DB2
however, SecurityACLs is PUBLIC=”YES” and there
is no NativeACLs information because security is
not enabled for DB2.
Example F-3 on page 576 shows the output of
trevistore for the corresponding RDS in
Example F-2 on page 573. It shows the Security
information for Notes Domino and DB2 Content
Manager, but is blank for DB2.
Example F-4 on page 577 shows the output of RDS
where the crawled data using the JDBC crawler is
DB2 with security tokens. You will note that
SecurityACLs is PUBLIC=”NO”with the token
PERSONAL.
Example F-5 on page 577 shows the output of
trevistore for the corresponding RDS in
Example F-4 on page 577. It shows the security
token (PERSONAL) in the field esfield.security_acl.
Name Description
Appendix F. Troubleshooting aids 569
Figure F-1 esadmin check output
Figure F-2 esadmin rds help output
570 IBM OmniFind EE V8.4: Configuration and Implementation Scenarios
Figure F-3 esadmin report help output
Example: F-1 esadmin session discovery discover -api command options
esadmin session discovery discover -api <apiname> <options>
-- where apiname can be any of the following, and options can be any one associated with each apiname
-- For example,
-- esadmin session discovery discover -api getJDBCDriverClasspath -driver
--
-- List of APIs and their corresponding options
--
getDB2Databases -system -database -host -port
validateDB2User -url -user -password -driver
getDB2TargetData -url -user -password -schema -table -driver
getDB2Fields -url -user -password -schema -table -driver -qRepSchema -publishingQMap
getDB2PublishingQMaps -url -user -password -driver -schemaX -tableX
getDB2PublishingCondition -url -user -password -schema -table -driver -qRepSchema -publishingQMap
validateMQConnection -queueManager -queue -host -port -channel
getSupportedDatabases
validateDatabaseUser -url -user -password -driver -driverpath
getDatabaseTargetData -url -user -password -schema -table -driver -driverpath
getJDBCDriverClasspath -driver
Appendix F. Troubleshooting aids 571
getDatabaseFields -url -user -password -schema -table -driver -driverpath
getNotesDatabases -server -protocol -id -password -database -flags @DIIOP
--
-- @DIIOP options are -iormethod -iorparam -usediiops -tcpath
--
getNotesViewsAndFolders -server -protocol -database -id -password -view -folder -flags -showhiddenviews @DIIOP
validateNotesIDFile -server -protocol <0:nrpc, 1:diiop> -id -password -filter_id -flags @DIIOP
validateNotesFields -server -database -id -password -field @DIIOP
validateNotesDatabases -server -protocol -id -password -databaseX @DIIOP
getNotesDatabaseDirectories -server -protocol -id -password -directory -flags @DIIOP
getNotesDomainName -server -protocol -id -password @DIIOP
getNotesUserInformation -server -protocol -id -password -validateuser @DIIOP
getNotesUserInformation -server -protocol -id -password -ltpatoken @DIIOP
validateNotesUser -server -protocol -id -password -validateuser -validatepassword @DIIOP
validateNotesUser -server -protocol -id -password -ltpatoken @DIIOP
getCMServers -server
getCMItemTypes -server -user -password -itemtype
getCMAttributes -server -user -password -itemtype
validateCMUserID -server -user -password
getCMUserInformation -server -user -password -validateuser
getDirectoryList -rootpath -level
getWinDirectoryList -rootpath -level -user -password
validateWinDomain -domain
getWinDomainName -rootpath
validatePublicFolder -url -user -password -trustpath -truthpassword
getPublicFolderList -url -user -password -trustpath -truthpassword -folder -level
getVBRRepositories -repository -jndi_factory -jndi_provider
getVBRRepositoriesDirect -repository
validateVBRUserID -jndi_factory -jndi_provider -repository -user -password -optional
validateVBRUserIDDirect -repository -user -password -optional
validateVBRUserID -jndi_factory -jndi_provider -repository -ltpatoken
validateVBRUserIDDirect -repository -ltpatoken
getVBRItemClasses -jndi_factory -jndi_provider -repository -user -password -optional -itemclass
getVBRItemClassesDirect -repository -itemclass
getVBRProperties -jndi_factory -jndi_provider -repository -user -password -optional -itemclass

Get IBM OmniFind Enterprise Edition Version 8.4 Configuration and Implementation Scenarios now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.