Toolpack Application:tboamapp
From TBwiki
(Difference between revisions)
(clean up) |
(merge information from other tboamapp page) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | == Started By == |
| − | + | ||
| − | + | Tboamapp is started by the [[Toolpack_Application:Tbtoolpack_Service |tbtoolpack_service]]. [[Toolpack_Application:Tbtoolpack_Service |Tbtoolpack_service]] also monitors tboamapp and restarts it if required. | |
| − | * | + | |
| − | *Managing all Toolpack applications (ensuring that they are always running) | + | == Roles == |
| + | |||
| + | === Master === | ||
| + | |||
| + | The master tboamapp is responsible for these roles: | ||
| + | *Starting the election process if another tboamapp instance is detected/lost | ||
| + | *Replicating packages (files + binaries) from [[Primary/Secondary |primary]] to [[Primary/Secondary |secondary]] host | ||
| + | *Managing/monitoring all the other Toolpack applications running on its host(ensuring that they are always running) | ||
| + | *Selecting configuration database(s) ([[Primary/Secondary |primary]] or [[Primary/Secondary |secondary]]) | ||
| + | *Creating/upgrading the configuration database | ||
*Applying package upgrades throughout the system | *Applying package upgrades throughout the system | ||
| − | |||
*Installing firmware and licenses on the device hardware | *Installing firmware and licenses on the device hardware | ||
| − | * | + | *Applying configuration changes throughout the system |
| − | * | + | |
| + | === Slave === | ||
| + | |||
| + | The master tboamapp is responsible for these roles: | ||
| + | *Starting election process if another tboamapp instance is detected/lost | ||
| + | *Managing all the other Toolpack applications running on its host(ensuring that they are always running) | ||
| + | |||
| + | |||
| + | |||
| + | == High Availability == | ||
| + | |||
| + | Tboamapp is a [[Master/Slave]] type application. Every time a tboamapp instance is detected or lost, an election process is triggered. The election process will select one tboamapp instance to become [[Master/Slave |master]], and the other will be [[Master/Slave |slave]]. If it is available, the tboamapp running on the [[Primary/Secondary |primary]] host will always win the election process; therefore, the [[Master/Slave |master]] will always fall back to the [[Primary/Secondary |primary]] host when available. | ||
== Logs == | == Logs == | ||
*Logs for tboamapp can be located in one of the following three places: | *Logs for tboamapp can be located in one of the following three places: | ||
| − | + | : [InstallDir]/toolpack/setup/''SystemId''/''MajorVersion''/apps/tboamapp/ | |
| − | [InstallDir]/toolpack/setup/ | + | : /lib/tb/toolpack/setup/12358/2.3/apps/tboamapp/ |
| − | /lib/tb/toolpack/setup/12358/2.3/apps/tboamapp/ | + | : C:\TelcoBridges\toolpack\setup\12358\2.3\apps\tboamapp\ |
| − | C:\TelcoBridges\toolpack\setup\12358\2.3\apps\tboamapp\ | + | |
| − | + | ||
Latest revision as of 16:01, 15 February 2011
Contents |
Started By
Tboamapp is started by the tbtoolpack_service. Tbtoolpack_service also monitors tboamapp and restarts it if required.
Roles
Master
The master tboamapp is responsible for these roles:
- Starting the election process if another tboamapp instance is detected/lost
- Replicating packages (files + binaries) from primary to secondary host
- Managing/monitoring all the other Toolpack applications running on its host(ensuring that they are always running)
- Selecting configuration database(s) (primary or secondary)
- Creating/upgrading the configuration database
- Applying package upgrades throughout the system
- Installing firmware and licenses on the device hardware
- Applying configuration changes throughout the system
Slave
The master tboamapp is responsible for these roles:
- Starting election process if another tboamapp instance is detected/lost
- Managing all the other Toolpack applications running on its host(ensuring that they are always running)
High Availability
Tboamapp is a Master/Slave type application. Every time a tboamapp instance is detected or lost, an election process is triggered. The election process will select one tboamapp instance to become master, and the other will be slave. If it is available, the tboamapp running on the primary host will always win the election process; therefore, the master will always fall back to the primary host when available.
Logs
- Logs for tboamapp can be located in one of the following three places:
- [InstallDir]/toolpack/setup/SystemId/MajorVersion/apps/tboamapp/
- /lib/tb/toolpack/setup/12358/2.3/apps/tboamapp/
- C:\TelcoBridges\toolpack\setup\12358\2.3\apps\tboamapp\
