webMethods Product Suite  | Complete Installation and Upgrade Information for Software AG Products | Installing Software AG Products | Preparing for Product Installation | Prepare Database Connection Information
 
Prepare Database Connection Information
Some products require you to supply database connection information during installation. Keep in the mind the following:
*Most products use the DataDirect Connect JDBC 5.1 driver. For information about options supported by this driver, see DataDirect Connect documentation, available on the Software AG Documentation website.
*Use the DataDirect Connect connection option MaxPooledStatements=35 on all database URLs except those for Trading Networks. This connection option improves performance by caching prepared statements. (Trading Networks caches its prepared statements using its own pooling mechanism).
*For DB2 database URLs:
*You must specify schema names using all uppercase letters. The tool you use to create database components later in this guide creates schema names in all uppercase letters, and DB2 is case sensitive for schema names.
*if your product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the database URL, where AlternateID is the name of the default schema that is used to qualify unqualified database objects in dynamically prepared SQL statements:
;AlternateId=schema;"InitializationString=(SET CURRENT
PATH=current_path,schema)";MaxPooledStatements=35
*For Integration Server and Microservices Runtime, for MySQL Community Edition 5.7, you must specify connection options for the relaxAutoCommit, useLegacyDatetimeCode , and serverTimezone parameters. For example, you can provide these connection options as follows:
jdbc:mysql://host:{3306|port}/databaseName?
relaxAutoCommit=true&useLegacyDatetimeCode=false&serverTimezone=PST
*If the database user and password do not yet exist, specify the database user and password you will create after installation. You can use one database user for multiple database components, or you can use a different database user for each database component.

Copyright © 2007-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.