1. Grid Chemistry System Architecture Overview Akylbek Zhumabayev

2. Components and Connections Web Client Web Site Web Service Grid Chemistry is an Internet Application based on Multitier Architecture where Web Client supports User Interface, Web Site performs interaction between users and Web Service proposes core functionality for the project calculations. The system is originally developed on Microsoft Platform but works through open network protocols which means that each module can be independently extended or migrated to another platform. All modules can run on the same machine, interact through intranet or work in Internet. Actually our architecture suggest combination of previous types of component connection.

3. Component 1: Web Client Web Client Connection with Web Site Client OS Web Client Role is played by any industrial web browser which supports DHTML (XHTML + JavaScript): IE, Firefox, Safari, Opera etc. Web Client can run on different operating systems and interacts with Web Site through HTTP connection. Anonymous users can go to project URL and browse public content (home page, news etc.). Registered users can login to private section of web site and work with project data. In this case connection will be supported in secure mode (HTTPS).

4. Component 2: Web Site Web Site Connection with Web Service Connection with Web Client Web Server Database Server Server OS Web Site: ASP.NET 2.0 application with AJAX extensions. Web Server: Internet Information Server (IIS) version 7.0. Database Server: SQL Server 2005. Server OS: Windows Server 2008 (Domain Controller). Authentication is supported by Active Directory (Groups). Authorization permissions are stored in the database.

5. Component 3: Web Service Web Service Connection with Web Site Web Server External Application Server OS Web Service: ASP.NET 2.0 application. Web Server: Internet Information Server (IIS) version 7.0. External Application: Fortran program (command line or.NET). Server OS: Windows Server 2008. Authentication is supported by Active Directory (Groups). Authorization permissions are implemented inside program code.

6. Server OS Connections Web Client Web Site Web Service HTTP(S) SOAP Client OS Firewall Typically Web Client interacts with Web Site through Internet connection. To secure the channel VPN or SSL can be used (encrypted connection). Web Site is located in DMZ behind firewall. Web Service can run on the same OS and interacts with Web Site through SOAP protocol (over HTTP). Security can be supported with OS features, IPSec, SSL or.NET library WSE/WCF.

7. Server OS Connections (alternative) Web Client Web Site Web Service HTTP(S) SOAP Client OS Firewall In alternative connection Web Service can run on different machine behind second firewall. Thus we move Web Service from DMZ to intranet which improves its security. Server OS Firewall

8. Questions?