Frequently Asked Questions.
Look in the logs directory of your webserver (e.g. for tomcat, in $CATALINA_HOME/logs) a file named <warname>toolkit.log (where <warname> is the name of the war file containing the toolkit, e.g. millennium.war). If there is no such file, then look for a file named toolkit.log in the same directory.
You can override the log4j.properties file used by the Toolkit by setting the CoreConfiguration.LoggingConfigFile parameter. This approach ensures the setting will continue to be used even if you replace the war file with a newer version. Alternatively you could edit the log4j.properties file in the exploded webapp (typically $CATALINA_HOME/webapp/<warname>/WEB-INF/classes/log4j.properties), but that change will be lost if you deploy a new copy of the war file.
Simply edit the values (or add properties and set their values) in the context descriptor you created when you installed the connector.
Put the following in your toolkit.properties file:NCIPServiceValidatorConfiguration.SchemaURLs=Note that there’s nothing after the equals sign; the effect is to suppress the default behavior where the Toolkit loads the ILS DI schema (which incorporates the NCIP 2.01 schema). With that set you should see a DEBUG-level message in the log file like this:SchemaURLs is empty; no XML validation will be performed.
Set the NCIPServiceValidatorConfiguration.AddDefaultNamespaceURI property to true.
Set the LookupUserService.Class property in the context descriptor (changing 'LookupUser' to the name of the service you want to disable) to org.extensiblecatalog.ncip.v2.common.DefaultService.
Your initial deployment consisted of two files in your tomcat directories: the war file and the context descriptor. Here are the steps to create another instance of the same web application, but with different properties:
Average response time, measured from entry to exit of the HttpServlet::!doPost method, was well under 10 milliseconds for 4,000 service invocations. The test was conducted on a Dell Latitude laptop running Windows 7 Enterprise with a Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz. It used the LookupItemSet service, which returned some minimal bibliographic data for one bib with 1-3 items. The test used the Dummy connector, so it does not include time spent interacting with the ILS, which is obviously going to be the greatest portion of processing for any NCIP responder.
► Sign in to add a comment