Appendix: Database ConnectionsΒΆ
The table below details the maximum number of database connections that may be used at any one time by each instance of each component. All components use connection pooling and will only explicitly keep connections open for the period they are required. This will usually be for very short periods of time, although connections will be held for longer if a component needs to select or update large amounts of data.
| Component | Base connections | Connections per dataset | Connections per request | Notes |
|---|---|---|---|---|
| Appointment Booking Engine | 8 | 1 | - | |
| Dynamic Scheduling Engine | 8 | 1 | - | |
| Resource Planning Service | 8 | 1 | - | |
| Schedule Archiving Service | 8 | 1 | - | |
| Schedule Broadcast Manager | 8 | 1 | - | |
| Schedule Dispatch Service | 8 | 1 | - | |
| Schedule Distribution Service | 8 | 1 | - | |
| Schedule Input Manager | 8 | - | 1 | By default the SIM will process up to 5 inputs concurrently. However this value can be modified via a parameter. |
| Schedule Query Manager | 8 | - | 1 | The SQM will only access the database for particular requests where it does not already have the required data cached. |
| Scheduling Administration Service | 8 | - | - | |
| Scheduling Gateway | 8 | - | 1 | |
| Scheduling Machine Manager | 8 | - | - | |
| Scheduling Restful Gateway | - | - | 1 | |
| Scheduling Service Manager | 8 | - | - | |
| Scheduling Simulation Service | 8 | - | 1 | |
| Scheduling Travel Analyser | 8 | 1 | - | |
| Scheduling Workbench | 1 | - | 1 | The number of potential connections will depend on the number of connected users. Many requests are handled by the SQM and not directly by the database. |