Caching and the need for OTAG to direct Tempo Box users to local OTCS (cache) instances

Danai Sae-Han

Hi

Tempo Box allows users to store a great deal of their most cherished documents offline.
However, for MNCs with a lot of roaming users this could be a problem, as users need to synchronise their documents.
Not everyone is willing to host OTAG / Tempo Box on the DMZ and prefer a controlled intranet environment.

Here is the catch: for OTCS you can set up cache servers across the globe. But is OTAG aware of this as well?
If I have synchronised documents from my corporate HQ and visit a local branch with an OTCS cache server and its own OTAG server. Using the OTCS web UI I get automatically redirected to the closest cache server.

Just load-balancing OTAG will probably not help, because it still needs to fetch the content from OTCS/OTAS. Is OTAG / Tempo Box making use of OpenText Content Web Services? And can it therefore make use of the caching that OTCWS provdes?

We are dealing with technical drawings and media files of 200~300 MB each on average. Hence the need for caching.

Thanks.

--
Danai Sae-Han