![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Copy the appropriate JDBC drivers file to BE_HOME/lib/ext/tpcl. You must restart BusinessEvents Studio Explorer after copying the drivers file. This step is required before you can use the design-time Test Connection feature. It is also required for runtime.
•
To allow faster TCP connection retries, use the property multiSubnetFailover=true even if your cluster is on the same subnet as recommended by Microsoft,To support Windows authentication, use property integratedSecurity=trueSee SQL Server authentication vs. Windows authentication for details.
5. Replace the script in <tibco_be_home>/bin/initialize_database_sqlserver.sql with the following script that creates a user associated to Windows login:To overcome this behavior, give the SQL Server login a higher permission at the server level such as sysadmin on all the SQL Server replicas, or use Windows login. For Windows login refer to SQL Server AlwaysOn Availability Groups.
• 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: http://msdn.microsoft.com/en-us/data/aa937724.aspx
2. Admin/Custom installation will create the file tnsnames.ora.Configuration while creating the file tnsnames.ora should match the database server configuration (database server is running on a remote machine).
3. Install TIBCO BusinessEvents and add the file ojdbc6.jar from the client installation to the folder BE_Home/lib/ext/tpcl.
4. The connect URL used in the TIBCO BusinessEvents is jdbc:oracle:oci:@DBServerHostName:1521:DBInstance.This URL can be found in the file tnsnames.ora.
• Use ojdbc6.jar drivers file.You can download this file from the following location: http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-111060-084321.html
• When OCI client is configured with 32-bit client, Oracle might display "No data found" error. To resolve the error, reduce the recovery batch size using the be.engine.cluster.recovery.batchsize property.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |