Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 Introduction : Database and File-based Storage

Database and File-based Storage
An administration domain stores domain information in a database repository or file repository, depending on the transport type. If TIBCO Rendezvous is set as the transport, you can store domain data in a database repository or file repository. If TIBCO Enterprise Message Service is set as the transport, you can only store domain data in a database repository.
In most cases, it is recommended to use a database for the domain repository and files for client application repositories.
In the case of a file-based domain, domain data is stored in the SYS_domain.dat and AUTH_domain.dat files. Data stored in the SYS_domain.dat file is referred to as the administration domain while data stored in the AUTH_domain.dat file is referred to as the authorization domain.
The authorization domain contains the users, roles and data access ACLs. Everything else is stored in the administration domain: installed software, machines, applications, plug-ins, TIBCO Administrator ACLs, and so on. As such, the administration domain file is usually much larger than the authorization domain file.
Editing these files is not recommended. It can potentially lead to loss of all domain data and to unpredictable behavior of TIBCO Administrator.
In a file-based domain, the Hawk agent accesses the domain repository through the administration server.
If a database is used, the administration domain is stored in tables beginning with Ad, while authorization domain data is stored in tables beginning with Au.
In a database-based domain, the Hawk agent accesses the domain repository directly and does not go through the administration server.
Performance can improve if domain data is saved into a database. During deployment, there are a number of steps during which domain data is committed. If domain data is stored in files, the files are loaded at startup and each time a change to the domain is saved, the contents of the corresponding file must be regenerated and the file saved. Each commit for a file-based domain requires writing the entire file, which is expensive both because of I/O and calculating the large number of individual strings.
When using a file-based repository with a primary and secondary administration server, performance will be slower than when using a database to store administration domain data.
When using a database, only the changed data is written. In addition to faster performance when saving domain data, there also is significant memory savings. Domain data will not be loaded and cached by TIBCO Administrator in the way that application data is. Note that moving application data to a database has no such savings and will slightly increase the server startup and deployment times.
To migrate from a file-based domain to a database-based domain, simply create a new domain with database settings, then use the AppManage utility to export your applications from the old domain and import them into the new domain.
Restrictions on Database Storage
Database storage has the following restrictions:
In a database-based domain, the TIBCO Hawk agents on all client machines must have database connectivity because they access the domain repository directly instead of accessing it through the administration server.
Client Application Data Storage
TIBCO Administrator creates application repositories when you deploy an application. For information about the deployment process, see the TIBCO Administrator User’s Guide.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved