The content repository is a part of the core data model of ACS 4.0 -and greater, and is loaded automatically as part of the ACS -installation process.
- -If you wish to install the content repository in a database schema -outside the context of ACS, the following instructions apply.
- -First install the data model and PL/SQL API:
- -In additional to SQL and PL/SQL, the content repository implements -a limited set of key methods in Java. The XML import and export -methods are dependent on Oracle's XML Parser for Java v2, available -from the Oracle Technology Network:
- - -http://technet.us.oracle.com/tech/xml/parser_java2/index.htm - -To load the XML parser, download and untar the distribution. Load -the class package lib/xmlparserv2.jar into Oracle from a shell -prompt:
- -$ loadjava -user user/password xmlparserv2.jar- -
Finally, load the SQLJ files in -packages/acs-content-repository/java:
- -$ loadjava -user user/password -resolve *.sqlj- -
Installation of the data model and API should now be complete.
- -The content repository relies on an Intermedia with the INSO -filtering option to search text within a wide variety of file formats, -including PDF and Microsoft Word. When the index on the -content column of cr_revisions is built, the INSO -filter automatically detects the file type of each entry and extracts -all available text for indexing.
- -If your searches are not returning any results even after rebuilding -the index, INSO filtering may be silently failing. You can verifying this -by checking for entries in the ctx_user_index_errors view -following an alter index statement.
- -If you experience errors on a UNIX system, check the following:
- -- (SID_DESC = - (SID_NAME = PLSExtProc) - (ORACLE_HOME = /ora8/m01/app/oracle/product/8.1.6) - (ENVS = LD_LIBRARY_PATH=/ora8/m01/app/oracle/product/8.1.6/lib:/usr/lib:/lib:/usr/openwin/lib:/ora8/m01/app/oracle/product/8.1.6/ctx/lib) - (PROGRAM = extproc) - ) -- -
If your searches are still failing even after following these -instructions, try a simple test case to -determine whether the problem has something to do with the content -repository data model itself.
- -The content repository is a part of the core data model of ACS 4.0 +and greater, and is loaded automatically as part of the ACS +installation process.
+ +If you wish to install the content repository in a database schema +outside the context of ACS, the following instructions apply.
+ +First install the data model and PL/SQL API:
+ +In additional to SQL and PL/SQL, the content repository implements +a limited set of key methods in Java. The XML import and export +methods are dependent on Oracle's XML Parser for Java v2, available +from the Oracle Technology Network:
+ + +http://www.oracle.com/technetwork/database-features/xmldb/xdk-java-082884.html + +To load the XML parser, download and untar the distribution. Load +the class package lib/xmlparserv2.jar into Oracle from a shell +prompt:
+ +$ loadjava -user user/password xmlparserv2.jar+ +
Finally, load the SQLJ files in +packages/acs-content-repository/java:
+ +$ loadjava -user user/password -resolve *.sqlj+ +
Installation of the data model and API should now be complete.
+ +The content repository relies on an Intermedia with the INSO +filtering option to search text within a wide variety of file formats, +including PDF and Microsoft Word. When the index on the +content column of cr_revisions is built, the INSO +filter automatically detects the file type of each entry and extracts +all available text for indexing.
+ +If your searches are not returning any results even after rebuilding +the index, INSO filtering may be silently failing. You can verifying this +by checking for entries in the ctx_user_index_errors view +following an alter index statement.
+ +If you experience errors on a UNIX system, check the following:
+ ++ (SID_DESC = + (SID_NAME = PLSExtProc) + (ORACLE_HOME = /ora8/m01/app/oracle/product/8.1.6) + (ENVS = LD_LIBRARY_PATH=/ora8/m01/app/oracle/product/8.1.6/lib:/usr/lib:/lib:/usr/openwin/lib:/ora8/m01/app/oracle/product/8.1.6/ctx/lib) + (PROGRAM = extproc) + ) ++ +
If your searches are still failing even after following these +instructions, try a simple test case to +determine whether the problem has something to do with the content +repository data model itself.
+ +