Danté Vitulano, Sr. Solutions Architect
Jeremy Richmond, Customer Obsession Readiness Lead
The Voxeo University team discusses best practices and lessons learned from large-scale deployments: sample architectures, multi-site data centers, multi-tenancy, SIP Proxies, SBCs, and more.
6. $Install_Dir/voxeo/prophecy/config/console.propertie
s
# Automated backup restore
prophecy.console.backuprestore.interval=30000
prophecy.console.backuprestore.nrOfBackups=1
prophecy.console.backuprestore.backupFileName=
prophecy.console.backuprestore.restoreFileName=
prophecy.console.backuprestore.deleteFileAfterRestore=tru
e
6
How to Configure Backups
Backups
13. Key Points on Licensing
• Prophecy Browsers are licensed individually
• Prophecy log search indexers are licensed as a
cluster, not individually
• Prophecy Licensing is tied to, among other
things, hardware on the machine
• Windows updates have been known to break
the license
13
Licensing
15. • Software upgrades are included in the annual
Maintenance you pay on the Prophecy Ports
• Upgrades are recommended with each major
release, which generally happens once a year
• Upgrading too often is not recommended unless
there is a bug fix you are waiting on
15
Prophecy Upgrades
16. • Upgrades should be performed first in a
development environment, and tested as you would
with any software
• While upgrades can be performed with little to no
downtime, a scheduled Maintenance window is
recommended
• When Upgrading major releases, we recommend
that you remove all boxes from the
community, upgrade the controller/s and re-add
boxes as they are upgraded
• Licensing for various components can be
affected, which is why it is recommended to first
test the upgrade in a development environment
16
Prophecy Upgrades
20. All data written by CXP Server to System DB logging and
Custom DB logging goes through a message queue using the
point-to-point Java Message Service API.
The queue is persisted on disk to ensure that no data is lost if
the database temporarily becomes unavailable.
For the explicit message Brokers in between Producer and
Consumers, we
recommend using
the FuseSource
ActiveMQ
distribution,
version 5.5.1
or higher.
20
Brokers – ActiveMQ
22. 22
Virtual CXP Commander
To monitor and manage
multiple Voxeo CXP clusters
as an integrated unit, the
Virtual CXP Commander
stands in place of a regular
CXP Server. So using the
Virtual CXP Commander
consists of two steps:
1. Setting up the Virtual CXP
Commander process.
2. Configuring a CXP Commander
connection pointing to it.
23. Voxeo CXP Application Server(s):
• Generally have 2-4 instances running per server with
a JVM heap size of 1-2 GB.
• Instances can each handle roughly 500 sessions.
VCC, Metadata, Brokers and Consumers
are not as CPU intensive, so they can
be combined, but care should
be taken.
23
Sizing
24. Your database(s) must be able to handle a large
amount of records inserted per second.
• Number of inserts depends on Input States, Module
Objects, Business Tasks, etc.
The amount of data to be stored and for how also long
needs to be considered.
• For specific
information:http://help.voxeo.com/go/help/vo.cxp13.info
storeguide.overview.sizing
If you have any questions about sizing,
please call us. We are here to help!
24
Sizing