Clients must have a dedicated NIC of at least 100 Mbps.
Moderate thick client access with 500 active connections is supported.
The data transfer (synchronization of user data) rate must be 10 MB per hour per client.
The synchronization interval must be 10 minutes for thick clients.
Both SSL and non-SSL communication is supported.
Heavy Web access is supported with a data transfer rate of 60 MB per hour per client.
5.4 Deployment Scenarios
The following sections discuss deployment scenarios in a master-slave deployment with a high Web
Access load:
Section 5.4.1, "Web Access," on page 29
Section 5.4.2, "Online Application Submission," on page 29
5.4.1 Web Access
Consider an example of a consulting firm that provides various services to its clients by presenting
products or solutions, performing customer product analysis in spreadsheets, or recording customer
scenarios. In addition, a majority of the workforce of this firm is always on the move.
In such a situation, you can deploy a master-slave deployment to effectively meet the needs of the
employees. The employees can use iFolder over the Internet to securely access the organization's
presentations about various solutions and products that the customer is interested in. The sales or
marketing representatives of the firm can download the presentations and spreadsheets through
iFolder Web Access and do online presentations.
The sales or marketing representatives can also modify presentations and upload them to the iFolder,
then share the iFolder with offsite representatives for evaluation, or they can distribute the modified
presentations to other sales or marketing representatives across the globe. Novell
effectively synchronizes these information units among company representatives so that everyone
has access to the latest information.
5.4.2 Online Application Submission
Consider the case of a banking organization that is planning to provide online banking services to its
customers. The online banking features could include all types of application submission
procedures, so that the customer can visit the online bank instead of going to the actual bank
location.
One such application submission procedure is the loan application. For every customer, the bank can
allocate an iFolder and the customer can receive documents, update them, and upload them again to
the iFolder for the bank's verification.
The document exchange procedure can be fully automated so the data between the bank and the
customer is always in sync and the customers get a real-time experience wherever they are. This
effectively replaces the form-based submission procedure. Using iFolder, the customer can
download the document, fill in the form at leisure, and upload it to his or her own iFolder, which
synchronizes with the bank's iFolder, and the bank representative gets the updated document that
can be printed or processed further.
Master-Slave Deployment for a High Web Access Load
®
®
iFolder
29
Need help?
Do you have a question about the IFOLDER 3.8 - DEPLOYMENT and is the answer not in the manual?
Questions and answers