Your ATG platform installation includes a preconfigured SOLID SQL database that contains the data necessary for running the ATG demo applications. The SOLID database is intended for evaluation and development purposes only. Before deploying your application in a production environment, you should configure both your application server and ATG products to use a production-quality database management system such as Oracle or Microsoft SQL Server. Your applications can then access application server resources and ATG components simultaneously. For a list of supported databases, see the Supported Environments page on the ATG website (http://www.atg.com/en/products/requirements/).
The ATG platform includes a number of tools for creating a database, adding and removing tables, configuring data sources and connection pools, and importing and exporting data. This chapter covers the following topics:
Note: Changing ATG’s out-of-the-box database schemas is not recommended, although you can extend the schemas as necessary. If you do make any schema changes, you must migrate the changes manually when you upgrade to a new version of ATG.
Note: JBoss comes with its own demo database, Hypersonic (you may have noticed the datasource hsqldb-ds.xml in the /deploy directory). Some JBoss components need that database, so leave it in the directory unless you intend to remove the components that use it.
Note: If you are using a utf8 Oracle database, before creating any tables, in order to avoid errors you must set the system nls_length_semantics to char:
alter system set nls_length_semantics=char;
Note: If you are using an Oracle OCI client to connect your application server to the Oracle database, the bit version of Oracle OCI client must match the bit version of your JDK. For example if your JDK is 32-bit, your OCI client should be 32-bit, regardless of your operating system bit size.
