The shutdown command for the application server ensures that the tag on this technical table is removed. These checks are performed by repeatedly tagging a technical table in the relational database. After starting the repository, the JVM periodically checks that it still holds ownership of the repository. Before the repository becomes available, the repository must first acquire exclusive ownership of the relational database. If such a situation was to occur, it would lead to unpredictable behavior and potentially even corruption of data in the repository.ĮBX® performs checks to enforce this restriction. It is then required that they specify distinct table prefixes using the property .Ī repository cannot be shared by multiple JVMs. Furthermore, to achieve horizontal scalability, an alternative is to deploy a distributed data delivery (D3) environment.Ī single relational database instance can support multiple EBX® repositories (used by distinct JVMs). These aspects are detailed in the sections Single JVM per repository and Failover with hot-standby. However, a failover architecture may be used. This repository is physically persisted in a supported relational database instance, accessed through a configured data source.Ī repository cannot be shared by multiple JVMs at any given time. The main principles of the TIBCO EBX® technical architecture are the following:Ī Java process (JVM) that runs EBX® is limited to a single EBX® repository.
Monitoring and cleanup of the relational database.
Rules for the database access and user privileges.
0 kommentar(er)
