NLB multiple Web site access shared files solution

When the company portal project is formally deployed, the BPM site has multiple Web front-end servers because the BPM site uses the NLB cluster deployment approach. The process has the upload attachment function, initially because the server formal environment NLB deployment method, simply save all the attachments in the BPM Web site upload folder. When deployed to a formal environment, it is found that upload attachments are randomly uploaded to a web front end server.

Initially, in order to resolve file synchronization on multiple Web front-end services, simply consider the file Synchronization tool. The Sync tool selects the Googlesyn bidirectional file Sync tool, which is very useful and easy to configure, which solves the problem of deploying a formal environment.

Bug in file Sync tool:

1, can not be real-time synchronization, at least a second level of delay.

2, multiple Web front-end disk space wasted serious.

3, there is a risk of synchronization failure, not very good monitoring files

In order to completely solve this problem, then consider building a file server. This allows us to save all attachment class files on the file server, and then multiple Web front-end servers to fetch the corresponding files. However, consider the existing project code architecture, preferably without changing the code in the case of a smooth transition. Later on the web, IIS 7.5 has the ability to add virtual directories that can be mapped to a shared folder on a file server. This allows for a smooth transition of our project without the need to change the code (the only mention is when I have modified the asynchronous transform file to pass in HttpContext.Current, the asynchronous execution context is different).

Virtual directory specific resolution steps:

1. Right-click on the IIS site to add the virtual directory.

2. Enter an alias (preferably the same as the pre-migration folder name, which avoids modifying the code) Upload.

3. Enter the physical path to share the directory address with the file server.

4. Click "Connect as" to enter the user name account and password with full control of the shared file. The best thing is that the shared folder server has a common account with the BPM Web site server, and this account has permissions to control the shared folder.

5. Click "Test Settings" to verify that it is OK.

After testing, we can completely solve our problems.

The solution for setting up an FTP server has not been verified at this time.

NLB multiple Web site access shared files solution