Package contents and directory structure

After installing the Integrator Acquisition System, you see this directory structure:

IAS
   3.0.0
         bin
         ...
   workspace

The contents of the IAS directory are described here in detail.

Directory	Contents
`version`\bin	Scripts to start the IAS Service (ias-service.sh for UNIX and ias-service.bat for Windows). Scripts to run the IAS Server Command-line Utility (ias-cmd.sh for UNIX and ias-cmd.bat for Windows). Scripts to run the Component Instance Manager Command-line Utility (component-manager-cmd.sh for UNIX and component-manager-cmd.bat for Windows). Scripts to run the Record Store Command-line Utility (recordstore-cmd.sh and recordstore-cmd.bat). Scripts to run the Web Crawler (web-crawler.sh for UNIX systems and web-crawler.bat for Windows). Scripts to shut down the IAS Service (ias-service-shutdown.sh for UNIX and ias-service-shutdown.bat for Windows). The executable that runs the IAS Service as a Windows service (ias-service-wrapper.exe).
`version`\cms	Server-side files for the SharePoint Object Model connector.
`version`\doc	The reference documentation (Javadoc) for the IAS Server, the Component Instance Manager, the Record Store, the IAS Extension API, and the Web Crawler. The IAS Third-Party Software Usage and Licenses.
`version`\doc\wsdl	The Web Service (WSDL) files for the IAS Server, the Component Instance Manager, and the Record Store.
`version`\java	The JDK used to run the IAS components.
`version`\lib	Libraries for the IAS command-line utilities including: the IAS Server utility, the Component Instance Manager utility, the Record Store utility. Libraries for the IAS APIs including: the IAS Server API, the Component Instance Manager API, the Record Store API, and the IAS Extension API.
`version`\lib\ias-server-plugins	Libraries for IAS plug-ins including CMS connectors and custom extensions (if applicable).
`version`\lib\oit-sx	The IAS Document Conversion Module libraries.
`version`\lib\web-crawler	The Web Crawler libraries.
`version`\sample	Directories for the sample applications and sample extensions. The sample applications are documented in the IAS Developer's Guide and also in the IAS Extension API Guide.
`version`\webapps	The root.war file, which is the IAS Server and Component Instance Manager as standalone applications.
`version`\workspace_template	The template for the workspace directory that contains configuration files.
workspace	The working directory for the IAS Server and the Web Crawler.
workspace\conf	The `commandline.properties` file, which contains the IAS Service settings necessary for the IAS command-line utilities to run. Three logging configuration files (ias-service.log4j.properties for the IAS Service, recordstore-cmd.log4j.properties for the Record Store, and ias-cmd.log4j.properties for the Command-line Utility). The Jetty configuration files.
workspace\conf\web-crawler\default	The default configuration files for the Web Crawler, including the log4j.properties logging configuration file.
workspace\conf\web-crawler\non-polite-crawl	Sample crawl configuration files for non-polite crawls. As with the polite version, the settings in these files will override the default settings.
workspace\conf\web-crawler\polite-crawl	Sample crawl configuration files for polite crawls. The settings in site.xml will override the same property settings in the default.xml file, while the crawl-urlfilter.txt file will also override the default version of the file.
workspace\logs	The ias-service.log file, which contains the IAS Service log output, and includes log messages from all crawls managed by the IAS Server.
workspace\output	Default destination directory for the crawl output from the Web Crawler. The output directory is not present upon installation. It is created when the Web Crawler writes to output records for a crawl.
workspace\state	State files for the IAS Service components. State files can include Record Store instances, state directories for data source extension information, and state directories for manipulator extension information.

Note: There is no logs directory for the Web Crawler, because by default the Web Crawler sends its standard output to the console. However, you can modify the log4j.properties file to send the output to a file.