• Products
• Web Content Management
• Web Asset Management
• Taxonomy and Categorisation
• Deployment Server
• SharePoint Connector
• Features
• Design
• Create
• Describe
• Manage
• Library Services
• Reporting and Analysis
• Workflow
• Web Asset Manager
• File Management
• Document Lifecycle
• WAM architecture
• server configuration
• technical requirements
• integration
• WAM features
• Choice of Interfaces
• Extensibility
• Web Based Admin
• Accessibility Compliance
• Deliver
• Extend
• Integrate
• Develop
• What's New?
• Customers
• News
• Resources
• Services
• Find a Partner
• About Us
• Careers with us
• Sitemap

Server configuration

There are a variety of architectural configurations for an Immediacy system.

Where a live server exists externally with a staging server internally Immediacy provides an XML upload to synchronise data from the staging server to the live server. This works using HTTP via port 80 and will therefore work through a firewall.

Immediacy has been designed to support a large number of users and has been both tested and deployed in relatively high volume situations. Internal testing has included automated stress testing which indicates that a single standard server machine running Immediacy can support in excess of 1 million hits per day.

System performance is dependant on a number of variables, including the complexity of the processes being run, the operating system, the database engine used and the performance of the underlying hardware.

Higher performance can usually be achieved by scaling 'up' i.e. using progressively more powerful machines. Alternatively organisations can scale 'out' by running the system on load-balanced clusters. Correctly configured this gives high performance coupled with additional resilience as there is no single point of failure. Immediacy has been used in, and is compatible with, both approaches. Configurations in use range from a single server, to clustered web servers with attached clustered database servers.