Deployment Architecture

There are no one size fits all when it comes to how the solution is deployed. The EngageIP platform is designed for scalability. As LogiSense customers grow their business, they expect their back office system to handle the workloads and usage that come with a larger volume of customers, data and transactions.

There are 3 components to any EngageIP deployment. Hosted customers typically don’t have to concern themselves with these details but they are useful nonetheless for informational purposes.

AWS
ComponentDescription
EngageIP Web ServerThe EngageIP Web Server is Windows IIS based and hosts the EngageIP web portal. This is the administrator portal through which an administrator configures the EngageIP system
EngageIP App ServerThe EngageIP App Server hosts the application services such as subscription billing and real time rating that power the EngageIP system. The App Server runs multiple services; each service executes processing for a key EngageIP processing block.
EngageIP Database ServerThis server powers the Microsoft SQL database. The database contains configuration data, tables and business data that needs to be persisted.

There are various deployment topologies that can be supported based on the scalability, performance and redundancy needs of the end customer. EngageIP can be deployed on premise or on a private cloud. Private cloud hosting is available on Amazon Web Services (AWS).