Oracle Commerce Guided Search - Package contents and directory structure

Package contents and directory structure

The CAS directory is the root directory for the Content Acquisition System.

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

CAS
   <version>
         bin
         ...
   workspace

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

Directory	Contents
`version\bin`	Scripts to start the CAS Service (`cas-service.sh` for UNIX and `cas-service.bat` for Windows). Scripts to run the CAS Server Command-line Utility (`cas-cmd.sh` for UNIX and `cas-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 CAS Service (`cas-service-shutdown.sh` for UNIX and `cas-service-shutdown.bat` for Windows). The executable that runs the CAS Service as a Windows service (`cas-service-wrapper.exe`). Script to install CAS Console on UNIX (`configure_tools_and_frameworks_integration.sh`)
`version\console`	The `casconsole.war` file, which is the CAS Console application. The `casconsole.xml` file, which is the context file for the CAS Console. The `casconsole.properties` file, which is the configuration file for the CAS Console. These files are copied to the Oracle Commerce Workbench installation and used from that location.
`version\doc`	The reference documentation (Javadoc) for the CAS Server, the Component Instance Manager, the Record Store, the CAS Extension API, the CAS Deployment Template Component, and the Web Crawler. The Licensing Guide.
`version\doc\wsdl`	The Web Service (WSDL) files for the CAS Server, the Component Instance Manager, and the Record Store.
`version\java`	The JDK used to run the CAS components (except CAS Console, which runs in the Oracle Commerce Workbench Service).
`version\lib`	Libraries for the CAS command-line utilities including: the CAS Server utility, the Component Instance Manager utility, the Record Store utility. Libraries for the CAS APIs including: the CAS Server API, the Component Instance Manager API, the Record Store API, and the CAS Extension API.
`version\lib\cas-dt`	CAS WSDL client stub files for the Deployment Template.
`version\lib\cas-server-plugins`	Libraries for CAS plug-ins including CMS connectors and custom extensions (if applicable).
`version\lib\oit-sx`	The CAS Document Conversion Module libraries.
`version\lib\recordstore -forge-adapter`	The library for the Forge Record Store adapter.
`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 CAS Developer's Guide and also in the CAS Extension API Guide.
`version\webapps`	The `root.war` file, which is the CAS Server and Component Instance Manager applications.
`version\workspace_template`	The template for the workspace directory that contains configuration files.
`workspace`	The working directory for the CAS Server and the Web Crawler.
`workspace\conf`	The `commandline.properties` file, which contains the CAS Service settings necessary for the CAS command-line utilities to run. Three logging configuration files (`cas-service.log4j.properties` for the CAS Service, `recordstore-cmd.log4j.properties` for the Record Store, and `cas-cmd.log4j.properties` for the Command-line Utility). The Apache Tomcat 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 `cas-service.log` file, which contains the CAS Service log output, and includes log messages from all crawls managed by the CAS 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 CAS 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.

Copyright © Legal Notices