...
A redundant jtel Cluster within your VM-Hosts may look like the example architecture from Shutdown/Startup Procedure - Large V3 - Redundant Databases + Load Balancing + Storage
Your VM-Hosts should be configured so that none of the jtel vms turn on automatically after the Host ist started. If any startup-automation is in place, it should be deactivated beforehand or configured to fit within the parameters of this procedure.
Example
Explanation
To begin shutdown procedures, the active side is chosen. In the table below the active side is VM-Host 1. We will move it to VM-Host 2 to illustrate a controlled fail-over.
...
At least a backup of database on acd-dbm1 is required. If the capacity on your VM-Hosts is enough, snapshots of critical machines are also good, but not essential. The critical machines are all
- acd-dbm1
- acd-dbm2
- acd-lb1
- acd-
...
- lb2
- acd-
...
- store1
- acd-
...
- store2
Step 2 - Deactivate Monitoring
If monitoring is installed on your system, schedule a downtime for 2 hours for the machines on VM-Host 2. This is the approximate time this procedure will take to conclude. Extend if needed. The downtime for the machines on VM-Host 1 should be set to however long they will be inactive.
If your monitoring server is currently running on VM-Host 1, it has to be moved to a different VM-Host.
Step 3 - Shutting down all software
...
| Machine(s) | Start what | It is installed if you are using | How to stop |
|---|---|---|---|
| acd-tel2 | 8-Server | ACD / IVR | Explorer to shell:startup - start the link to startup_launcher.cmd For service installations, start the robot5 service. |
| Platform UDP Listener | ACD / IVR | Explorer to shell:startup - start the link to startListener.bat For service installations, start the jtel Platform UDP Listener service. | |
| Presence Aggregator | A PBX or presence connector which uses the presence aggregator:
| Explorer to shell:startup - start the link to start-presence-aggregator.cmd For service installations, start the jtel Presence Aggregator service. | |
| Telephony Connector | A PBX which uses a custom connector:
| Explorer to shell:startup - start the link to JTELInnovaphonePBXService.exe or jtelTAPIMonitorService.exe For service installations, start the service, for example the jtel TAPI service or jtel Innovaphone Service. | |
| Exchange Connector | E-Mail with an Exchange or Office 365 Server | Start the jtelEWSMailService service. | |
| IMAP Connector | E-Mail with an IMAP(S) Server | Start the jtelIMAPMailService service. | |
| acd-jb4-6 | Wildfly | Anything | sudo systemctl start wildfly For installations not using systemctl: sudo service wildfly start |
| acd-chat2 | Chat Server | CHAT | sudo systemctl start jtel-clientmessenger For installations not using systemctl: sudo service jtel-clientmessenger start |
| acd-api2 | REST API | REST | sudo systemctl start jtelrest For installations not using systemctl: sudo service jtelrest start |
| acd-dbm2 | Platform UDP Listener | SOAP | sudo systemctl start jtel-listener For installations not using systemctl: sudo service jtel-listener start |
Step 11 - Reactivate monitoring
The monitoring is now reactivated on all machines on VM-Host 2
Step 12 - Ensure system functionality
...
If all tests are successful, the system is now running only on VM Host 2 and fully operational.
Startup
...
The following steps assume that VM Host 1 has been booted, and all jtel VMs on the server are turned off. If the jtel vms were mistakenly turned on, problems in the cluster might have occured as a result.
| Info |
|---|
This part of the procedure is not designed to be standalone and directly correlates to the previous shutdown steps above, as it is part of the example. |
Step 1 - Backups
Another backup of the database is created. This time acd-dbm2 is the active database.
Step 2 - Deactivate Monitoring
Schedule a downtime for the monitoring on all machines for approximately 2 hours. Extend if needed.
If your monitoring server is currently running on VM-Host 1, it has to be moved to a different VM-Host.
Step 3 - Shutting down all software
| Machine(s) | Stop what | It is installed if you are using | How to stop |
|---|---|---|---|
| acd-telN | 8-Server | ACD / IVR | X the cmd file starter window. For service installations, stop the robot5 service. |
| Platform UDP Listener | ACD / IVR | X the cmd file starter window. For service installations, stop the jtel Platform UDP Listener service. | |
| Presence Aggregator | A PBX or presence connector which uses the presence aggregator:
| X the cmd file starter window. For service installations, stop the jtel Presence Aggregator service. | |
| Telephony Connector | A PBX which uses a custom connector:
| X the cmd file starter window. For service installations, stop the service, for example the jtel TAPI service or jtel Innovaphone Service. | |
| Exchange Connector | E-Mail with an Exchange or Office 365 Server | Stop the jtelEWSMailService service. | |
| IMAP Connector | E-Mail with an IMAP(S) Server | Stop the jtelIMAPMailService service. | |
| acd-jbN | Wildfly | Anything | sudo systemctl stop wildfly For installations not using systemctl: sudo service wildfly stop |
| acd-chatN | Chat Server | CHAT | sudo systemctl stop jtel-clientmessenger For installations not using systemctl: sudo service jtel-clientmessenger stop |
| acd-apiN | REST API | REST | sudo systemctl stop jtelrest For installations not using systemctl: sudo service jtelrest stop |
| acd-dbmN | Platform UDP Listener | SOAP | sudo systemctl stop jtel-listener For installations not using systemctl: sudo service jtel-listener stop |
...