|
|
IntroductionThis article describes the differences between the two types of domain data storage that can be used:
FileDatabaseNote that there are two types of transports available to a domain:
RVEMS. If this option is chosen for domain transport then a database must be used for domain storage.Setting the Domain Storage TypeThe decision to set the storage type is made when the domain is created.
Using the Domain Utility GUIThe checkbox highlighted below determines whether database or file storage is used.
After this checkbox is selected, a later screen will gather the database connection details and provide the opportunity to test the database connection.
Using the Domain Utility command line executable (domainutilitycmd)To create a database based domain, the following section of the CreateDomain.xml file should be uncommented (the “<–” and “–>” markers removed) and filled in as appropriate. If a file based domain is to be used, then this section should be left commented.
<!– uncomment the following for DB configuration –><!– <DatabaseConfiguration>
<DatabaseUrl>jdbc:tibcosoftwareinc:sqlserver://localhost:1433;databaseName=eaidb </DatabaseUrl>
<DatabaseUsername>sa</DatabaseUsername>
<DatabasePassword>sa</DatabasePassword>
<JdbcDriver>tibcosoftwareinc.jdbc.sqlserver.SQLServerDriver</JdbcDriver>
<DatabaseMinConnections>0</DatabaseMinConnections>
<DatabaseMaxConnections>5</DatabaseMaxConnections>
</DatabaseConfiguration>
–>
File Based DomainAs the name implies, the domain data is stored in the files on a system drive.
Warning: Although these files are written in XML, they should not be manually edited as that can cause corruption of the domain rendering it inoperable.
Location of FilesBy default these files are stored in the directory:
<TIBCO HOME>/administrator/domain/<domainName>/data
However this can be altered when the domain is created.
Using the Domain Utility GUIOn the “Create New Domain” task, check the “Show Advanced” box
Then scroll down and set the Domain Home values as required.
Using the Domain Utility command line executable (domainutilitycmd)The CreateDomain.xml file can be altered to set the domain home files as needed by setting the following XML parameters.
<TRADomainHome/> <AdminDomainHome/>
The following table provides some details regarding the different files that may be found in this directory:
File NameDescriptionSYS_<domain name>.datThis file contains details of the applications deployed,deployment history and plugins used.AUTH_<domain name>.datThis file contains the domain access control data: users, roles, and the permissions associated with them.SYS_PJBtemp.dat.filesThis directory contains binary data for the domain. Note that this directory contains subdirectories with names like:plicationConfiguration ationConfiguration
This is by design. There is an FAQ regarding this – FAQ1-9DCF6M
Other files may also be found in this directory some example are belowAPP_<domain name>_HawkConfig.datData linked to domain plugins.APP_<domain name>_MonitoringManagement.datAPP_<domain name>_Uddi_App_Domain.dat<domain name>-<Application name>.datData associated with a application deployed on the server (where the application transport is either HTTP or RV)<domain name>-<Application name>.dat.filesBenefitsIt is not database dependentLimitationsWhen Administrator starts up, the entire SYS and AUTH dat files are read into memory. If there are a large number of deployments or a large deployment history then this can slow down the Administrator upon start-up. This can be worked around by ensuring the application deployment histories are kept to a minimum. However it does limit the number of applications that can effectively be deployed.During deployment, the entire SYS dat file is rewritten a few times which could potentially slow down deployment.A domain update (including deployments) means that the whole dat file (SYS, AUTH or both) has to be rewritten to disk. This means there is the possibility of corruption if there is a write or disk failure.Database Based DomainThe domain data is stored in a database.
The exact database schema depends upon factors such as the plugins that have been installed and the type of password policy used. Hence the schema is not publicly available and the database user must have permission to create new database objects.
Categories: None
The words you entered did not match the given text. Please try again.
Oops!
Oops, you forgot something.