|
Why No Automated Updates This Help File Page was last Modified on 12/22/2012 |
|
|
|
|
Why No Automated Updates This Help File Page was last Modified on 12/22/2012 |
|
|
Why No Automated Updates
This Help File Page was last Modified on 12/22/2012
|
Why No Automated Updates This Help File Page was last Modified on 12/22/2012 |
|
|
|
|
Why No Automated Updates This Help File Page was last Modified on 12/22/2012 |
|
|
| □ | Why is there no Automated Update Procedure? |
| • | Automated Updates require that ALL connections to the Sybase® Adaptive Server Anywhere database engine be disconnected. |
| • | First and foremost, most Central Stations can’t afford to just shut down their operations for an undetermined amount of time. |
| • | As an example, imagine a Central Station that is receiving 50 Signals per minute with ten Operators processing those Signals. |
| • | Each operator would have to manually look up the CSID, Signal ID and/or Physical Zone, and the Municipalities who will accept the Dispatch for those accounts. |
| • | This would almost certainly create a life safety issue especially in the case of Fire, Panic and/or Burglary Alarm Conditions. |
| • | The Millennium Series is a multi-service platform. |
| • | In addition to the standard Millennium Central Station Monitoring application many Central Stations also use the Communications Module, Cluster, Dealer Module, Web Tech, Virtual Operator Module, etc. and interrupting any of these Service Processes can have serious consequences for the database. |
| • | In addition to being a multi-service platform, there are many “process driven” features in the Millennium Series such as Auto-Billing, Auto-Draft, Auto Purchases, and Auto-Service, all of which - if interrupted in mid-process - can also have serious consequences for the database. |
| • | You could just kill all the processes prior to the automated upgrade, but it may interrupt any of the above processes and procedures causing major issues. |
| • | But more importantly, you can’t prevent Dealer Module, Web Tech, Virtual Operator Module, etc., Users located outside of the Central Station from logging in and creating a problem, or creating an interruption affecting the upgrade process. |
| □ | What is Micro Key Solutions doing to make this process easier for Technical Support personnel and end Users? |
| • | The MKMS Development Department has adopted a new mini-release upgrade format. |
| • | This means they will be doing mini releases every three to four weeks with enhancements and fixes that do not require system shutdown, as there will be no database modifications. |
| • | They will also investigate the possibility of creating a semi-automated way for end Users to upgrade their individual network Workstations. |
| • | The Basic concept being: when a Workstation tries to connect to the Sybase® Adaptive Server Anywhere database engine, it will recognize that the Workstation needs an upgrade and will push that upgrade to the Workstation automatically. |
| • | The MKMS Development Department is also investigating virtualized work station environments for future deployment by “High Volume/High Number of Accounts” end Users. |