Amaxus Installation Scenarios

Distributed environment installation

Many organisations have a geographically diverse structure, with sites and offices in multiple locations.  Amaxus is flexible enough to integrate with most distributed environments.  For example, an organisation may have a head office in one location and one or more remote sites with requirements to access data.

The example below illustrated how Amaxus could be implemented across two sites connected with a low bandwidth or unreliable network connection.

^{Figure 4 – A master-slave distributed implementation of Amaxus}

In this scenario, data is managed and published at the primary site and replicated to the remote site as appropriate (out-of-hours, for example).  This allows remote users to have full and high-speed access to corporate data without relying on the wide area network (WAN) links.  This solution would be ideal for organisations with a centrally managed data or knowledge infrastructure and diverse or remote sites which require reliable access to this information.

In the second scenario below, three sites manage their own content locally.  Read-only copies would be replicated via the primary site to the remaining two sites allowing the full content to be available at all three sites, whilst retaining the ability for local sites to manage their own content.

^{Figure 5 - A read/read-write distributed implementation of Amaxus}