Editing the Schema Scripts

Before running the scripts, you must edit them to contain the information for your database.

Each supported database has its own version of the create-service-all script in the <ATG2007.3dir>/Service2007.3/Service/install directory. This script runs a number of SQL files for your specific environment. You can use your own database tool to run the various SQL files outlined in the create-service-all script. Use the create-service-all script to identify the SQL files to install if you do not want to install the entire Service application.

Note: ATG provides table-drop scripts to match each table-create script; for example, drop-service-all that uninstalls tables as necessary.

SQL File

Description

Create-service_agent_all.sql

This SQL script packages all of the application and platform tables required to run ATG Knowledge. It is a combination of service_agent.sql and service_agent_platform.sql. Use this script if you do not already have all of the required platform and application tables installed in your Agent schema.

  Service_agent.sql

Versioned ATG Knowledge tables.

  Service_agent_platform.sql

This SQL script packages all of the platform tables required to run Knowledge. Use this script to install the required platform tables installed in your Agent schema but not the application tables.

Service_datawarehouse.sql

These are the ATG Knowledge and ATG Self Service data warehouse tables and should be installed where other data warehouse tables are installed, usually in a separate DB instance optimized from data warehousing.

  Service_platform_datawarehouse.sql

These are all the data warehouse platform tables. This SQL script should be used if you already have the platform data warehouse tables installed. This SQL script should be installed where other data warehouse tables will be installed, usually in a separate DB instance optimized from data warehousing.

Service_production_all.sql

This SQL script combines service_production_platform.sql, service_platform_datawarehouse.sql, service_self_service.sql, service_shared.sql and service_datawarehouse.sql. It is provided as a convenience for setting up demos and QA testing. In a production installation, the data warehouse scripts would not be installed in the production schema.

  Service_production_platform.sql

These are all the production/customer facing platform tables need for ATG Self-Service. This SQL script should be used only if you do not already have the platform tables installed in the production/customer facing schema. They are installed production/customer facing database server.

  Service_self_service.sql

These are the unversioned ATG Knowledge tables deployed to from the Agent server. They are installed on the production/customer facing database server.

  Service_shared.sql

These are the tables that are read/written to by both the ATG Knowledge and ATG Self-Service applications. They are installed production/customer facing database server.

Using MSSQL and UNIX/LINX

If you are running a UNIX/LINUX server and communicating to an MSSQL server, you cannot use the included shell scripts to install the schema. You must use a third party driver to enable these servers to function together. Microsoft does not provide ODBC libraries for UNIX/LINUX. Because UNIX and LINUX have many different variants, you must use a binary that fits your platform. There are many commercially available third party drivers available.

Using MSSQL in Multi-Language Sites

If you are configuring a multi-language site with MSSQL, to view Japanese characters correctly when the solution is authored in Japanese, ensure that the useSetCharacterStream attribute is set to true in the /atg/service/common/src/config/atg/svc/ServiceRepository component. You can set the value for all repositories in your ATG installation by editing the GLOBAL.properties file in the top-level configuration layer.

MSSQL and Performance

To significantly improve performance, set the sendStringParametersAsUnicodeparameter in the Microsoft SQL server driver. If using the com.microsoft.jdbc.sqlserver.SQLServerDriver, make sure the data source URL includes sendStringParametersAsUnicode=false.

For example:

jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=admin;sendStringParametersAsUnicode=false;SelectMethod=cursor

To Edit and Install the Service Schemas

The create-service-all script creates the database tables for all of the Service modules. Refer to Using ATG Search with ATG Service.

  1. Open the create-service-all script for your database.

  2. Modify the agent and production database account name for your environment. The script contains several markers for the following variables. Change the variable information to match your environment. Note: Variable names change between database types, and not all variables are required for all database types:

    • DYNAMO_HOME – For example: DYNAMO_HOME=C:\ATG\ATG2007.3\home

    • DB_USER_AGENT – The name of the agent (svcagent) database user

    • DB_PWD_AGENT – The password of the agent (svcagent) database user

    • DB_NAME_AGENT – The name of the agent (svcagent) database

    • (Oracle only) ORA_TNS_PRODUCTION – The TNS identifier on the production (svcadmin) machine

    • DB_USER_PRODUCTION – Identify the name of the database user on the production (svcadmin) machine

    • DB_PWD_PRODUCTION – The password of the database user on the production (svcadmin) machine

    • DB_NAME_PRODUCTION – The name of the production (svcadmin) database

  3. Save the create-service-all script.

  4. Open the drop-service-all script for your database.

  5. Make the modifications above for the drop-service-all script. Save your changes.

  6. Once you have completed the edits, run the create-service-all script on your server(s).

 
loading table of contents...