TRIM Captura to TRIM Context Upgrade Notes - TRIM User Network
TRIM Captura to TRIM Context Upgrade Notes - TRIM User Network
TRIM Captura to TRIM Context Upgrade Notes - TRIM User Network
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>TRIM</strong> <strong>Captura</strong> <strong>to</strong> <strong>TRIM</strong> <strong>Context</strong> <strong>Upgrade</strong> <strong>Notes</strong> - <strong>TRIM</strong> <strong>Context</strong> 6.1 Page 10<br />
Client Configuration<br />
This section covers the software installation on the <strong>TRIM</strong> Client computers from a<br />
technical point of view.<br />
Architecture<br />
<strong>TRIM</strong> <strong>Context</strong>’s multi-tier architecture means that all data services <strong>to</strong> the Client are<br />
provided by the <strong>TRIM</strong> Server tier:<br />
• <strong>TRIM</strong> Synchronization Server<br />
• <strong>TRIM</strong> Workgroup Server(s)<br />
• <strong>TRIM</strong> Event Server(s).<br />
For the Client installation this means that no database client, access <strong>to</strong> the Electronic<br />
Document S<strong>to</strong>re or access <strong>to</strong> the Document Content Indexes needs <strong>to</strong> be configured.<br />
The only access needed is <strong>to</strong> the <strong>TRIM</strong> Server tier.<br />
<strong>TRIM</strong> <strong>Context</strong> does not use a “<strong>TRIM</strong> Startup Direc<strong>to</strong>ry” and s<strong>to</strong>res the Offline Records<br />
structure in the user profile and most of its settings in the registry.<br />
Access rights <strong>to</strong> this part of the registry need <strong>to</strong> be granted and the impact on the<br />
local copying of roaming profiles needs <strong>to</strong> be considered.<br />
The new architecture brings with it new minimum specifications for client computers,<br />
which need <strong>to</strong> be considered before an upgrade.<br />
The new architecture allows documents <strong>to</strong> be cached on the local computer, for<br />
which disk space needs <strong>to</strong> be considered.<br />
Desk<strong>to</strong>p Integration<br />
Desk<strong>to</strong>p Integration (ODMA, Macro (for non-ODMA applications) and E-mail) has<br />
been updated.<br />
The e-mail integration in <strong>TRIM</strong> <strong>Context</strong> has been reworked and requires later<br />
versions of the e-mail clients than <strong>TRIM</strong> <strong>Captura</strong> supported.<br />
The upgrade <strong>to</strong> <strong>TRIM</strong> <strong>Context</strong> may be affected by the timing of the upgrade <strong>to</strong> the<br />
supported versions of desk<strong>to</strong>p applications and e-mail clients.<br />
TopDrawer <strong>to</strong> Offline Records <strong>Upgrade</strong><br />
TOWER Software was mindful that enforcing a manda<strong>to</strong>ry “All items must be checked<br />
in from TopDrawer” policy was unworkable in many circumstances, so instead, where<br />
users have a <strong>TRIM</strong> <strong>Captura</strong> TopDrawer with checked-out and draft items, a<br />
conversion utility is provided for migrating this environment <strong>to</strong> the <strong>TRIM</strong> <strong>Context</strong><br />
Offline Records format.<br />
As with all data conversion processes, testing is considered a manda<strong>to</strong>ry<br />
requirement. Given the potential number of TopDrawer clients that may need such