The Administration section in TIBCO EBX® is the main point of entry for all administration tasks. In this overview are listed all the topics that an administrator needs to master. Click on your topic of interest in order to access the corresponding chapter or paragraph in the documentation.
For storage optimization, it is recommended to maintain a repository (persistence RDBMS) to the necessary minimum. To this end, it is recommended to regularly perform a purge of snapshots and obsolete dataspaces and to consider using a backup file system.
See also Cleaning up dataspaces, snapshots, and history and Deleting dataspaces, snapshots, and history.
It is also possible to archive files of the file system type in order to reduce the storage costs, see EBX® monitoring.
Administration tasks can be scheduled by means of the task scheduler, using built-in tasks, see Task scheduler.
EBX® maintains an object cache in memory. The object cache size should be managed on a case by case basis according to specific needs and requirements (pre-load option and pre-validate on the reference dataspaces, points of reference, and monitoring), while continuously monitoring the repository health report.
Keeping obsolete contents in the repository can lead to a slow server startup and slow responsiveness of the interface. It is strongly recommended to delete obsolete content.
For example: datasets referring to deleted data models or undeployed add-on modules. See Deploying and registering TIBCO EBX® add-ons.
The workflow history and associated execution data have to be cleaned up on a regular basis.
The workflow history stores information on completed workflows, their respective steps and contexts. This leads to an ever-growing database containing obsolete history and can thus lead to poor performance of the database if not purged periodically. See Workflow history for more information.
It is required to configure workflow emails beforehand in order to be able to implement workflow email notifications. See Configuration for more information.
The log file size will vary according to the log level (and to the selected severity level) and disk space needs to be accordingly managed.
An automatic purge is provided with EBX®, allowing to define how many days should log files be stored. After the defined period, log files are deleted.
Any customized management of the purge of logs (backup, archiving, etc.) is the user's responsibility.
#################################################
## Directory of log files 'ebxFile:'
## This property is used by special appender prefixed
## by 'ebxFile:' (see log section below)
#################################################
ebx.logs.directory=${ebx.home}/ebxLog
################################################################
# Daily rollover threshold of log files 'ebxFile:'
# Specifies the maximum number of backup files for daily rollover of 'ebxFile:' appenders.
# When set to a negative value, backup log files are never purged.
# Default value is -1.
################################################################
ebx.log4j.appender.ebxFile.backup.Threshold=-1
EBX® is provided with an XML audit trail manager, now disabled by default. Any customized management (including purge, backups, etc.) is the user's responsibility.
See Activating the legacy XML audit trail (deprecated) and Legacy XML Audit trail (deprecated) for more information.
The management of publications of embedded data models. See Data model administration for more information on the management of these publications and the administration tasks that can be performed (delete, import and export).
It is possible to update the data models that are using XML Schema documents not managed by EBX®. See Data model refresh tool for more information.
EBX® offers extensive UI customization options. Simplified interfaces (Recommended perspectives) dedicated to each profile accessing the system can be parameterized by the administrator. According to the profile of the user logging in, the interface will offer more or less options and menus. This allows for a streamlined work environment.
See Advanced perspective for more information.
EBX® is provided with the built-in administrator profile by default. An administrator can delegate administrative rights to a non-administrator user, either for specific actions or for all activities.
The administrative delegation is defined under 'Administration' in the global permissions profile.
Access to the administration section can be granted to specific profiles via the global permissions in order to delegate access rights on corresponding administration datasets.
If all necessary administrative rights have been delegated to non-administrator users, it becomes possible to disable the built-in 'Administrator' role.