Database LocationInstructions in this chapter assume you are working with a local database for testing purposes. Adapt the instructions if you are working with a remote database. For example, in production environments, you might have to ask a database administrator to create a database user for you. You should then be able to run the other SQL scripts yourself, logged on as the user created by the administrator.Minimum User PermissionsBy default the TIBCO BusinessEvents user permissions are set to DBA privileges. At a minimum, the user must be able to create tables and views. For example for an Oracle database you could use the following:
• Install and start a supported DBMS product. See the product readme file for a list of supported products.
• Now or later, copy the appropriate JDBC drivers file to BE_HOME/lib/ext/tpcl. You must restart TIBCO BusinessEvents Studio Explorer after copying the drivers file.
The driver must be in the above location for the design-time "Test Connection" feature to work. (You can try this out after you set up the database.)
• For non-production purposes, it is convenient to use SQL Server authentication so you can create database users as needed. Select this option when you install Microsoft SQL Server. With Windows Authentication, on the other hand, you may have difficulties creating users without help from others in your enterprise.
• Microsoft SQL Server 2008 has added a new data type, datetime2, which has a date range of 0001/01/01 through 9999/12/31. Therefore, if you are using Microsoft SQL Server 2008, then you can manually change the generated SQL script (DDL) for your backing store, and replace any affected columns’ data type from datetime to datetime2.
• Use the SQL Server JDBC driver, sqljdbc4.jar. You can download this driver from:
• Use ojdbc6.jar, Oracle Thin Driver only, with Sun Java JRE 6. You can download the Oracle JDBC driver from:
Copyright © TIBCO Software Inc. All Rights Reserved.