VISULOX Integration Examples

VISULOX can be integrated based on varied requirements:

• Maximization on access security

• Maximization data security

• Scaling

• Redundancy and geo redundancy
  
  

This article describes possible setups and evaluate its usecases.

Also this article has suggestions for node sizing depending on user and application usage. (Application to user factor is 2). There will be no difference between physical and virtual servers as long the specifications in CPU and memory are equivalent.

With scaling it is understood, that more and more users and applications can be used, With redundancy is understood, that a failure of a server (or a module) has no impact. Setup with multiple nodes always include scaling and redundancy. System recovery is a different approach and can be guaranteed with the virtualization infrastructure.

Each node hosting VISULOX can be used as a recorder and application server. A VISULOX Revision Server has to be independent.

A VISULOX setup is based on nodes, Redhat or Oracle 8/9. Each node hosts one or more modules: VISULOX GATEWAY, VISULOX PORTAL Service, VISULOX Service.