Now that you have created the BIZUI tables, you must create the SearchAdmin tables.
Set the following environment variables prior to running
create-search-admin.bat:SEARCH_VERSION=2007.3(Required for Unix Only)SEARCH_DB_TYPE=db2|mssql|oracleSEARCH_DB_USER=the svcadmin database userSEARCH_DB_PWD=the svcadmin database userpasswordFor configuration on an SQL Server:
SEARCH_MSSQL_DB_NAME=svcadmindatabase user
SEARCH_MSSQL_DB_HOST=localhostFor configuration on an Oracle Server:
SEARCH_ORACLE_TNS=oracle database tnsFor configuration on a DB2 Server:
SEARCH_DB2_DB_NAME=svcadmindatabase user
Run the
<ATG2007.3dir>/Search2007.3/SearchAdmin/install/file to create the
create-search-admin.batDAF.SearchandSearchAdmintables in the production (svcadmin) schema and import the starting data needed forSearchAdmin.Run the
<ATG2007.3dir>/Search2007.3/SearchAdmin/install/to create the initial
create-atgservice-searchproject.batATGServicesearch project.The script creates two separate content sets - one for Knowledge solutions and one for Self Service solutions and it names the logical partition associated with those content set to “Knowledge Solutions” and “Self Service Solutions”
When ATG Knowledge does a search, it excludes the logical partition called “Self Service Solutions”. When ATG Self Service does a search, it excludes the logical partition called “Knowledge Solutions”. This prevents the knowledge solution and the self service solution from being returned in a single search.
Note: If you set up your search solutions manually, then you must ensure that the Knowledge Solutions and Self Service Solutions are placed in different content sets. These content sets must be renamed to “Knowledge Solutions” and “Self Service Solutions”.
