Resolution:
Description:
============
Overriding the Schema name for the Database concept using the Global variable in TIBCO BusinessEvents .

Environment:
============
All Operating Systems
TIBCO BusinessEvents 4.0.x and 5.x

Resolution:
============
Schema name values can be specified using global variables in database concept-&gtextended properties-&gtSCHEMA_NAME and it will be taken into account at runtime. Refer to the attachment DatabaseConceptandSchemaName.png to see the location of the SCHEMA_NAME property in TIBCO BusinessEvents studio .

Example Scenario :

Client has two environments with two different user names and passwords in the database. There are two identical tables under these two schemas (Ex: SCHEMA names used are wmdev and wmqa). Using database concept import facility with one schema name(Ex: wmdev) to import the concepts from Database and then using the other schema name (Ex: wmqa) in the schema name attribute of the imported concepts to run the be engine is permitted in TIBCO BusinessEvents 4.x.

Environment :  DEV
User name   :  wmdev
Schema name :  wmdev

Environment :  QA
User name   :  wmqa
Schema name :  wmqa

Note that in case global variables are not used in the username and password section in TIBCO Shared Resources JDBC connection , it would require rebuilding the ear file with different schema names . It is recommended to use global variables for the username and password in TIBCO Shared Resources JDBC connection to take advantage of the above use case.

Attachments:
============
DatabaseConceptandSchemaName.png