1 / 31

Final Project Report On Online Registration using Web Services on a Platform

Index .

delu
Download Presentation

Final Project Report On Online Registration using Web Services on a Platform

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Final Project Report On “Online Registration using Web Services on a .NET Platform”

    2. Index  Introduction What is .NET? What are Web Services?   Web Services Vs RPC/RMI/COM Difference Between Web Service & Website Web Service Security Model Reason to choose ASP over ASP.NET ASP.NET Security Architecture ADO.NET Architecture Online Registration Web Application Implementation Detail Conclusion References

    3. Introduction This project has been implemented after a thorough study and understanding of the concepts of “Web Services” & “ ADO.NET”. In this project I have tried my best to demonstrate the concepts of Web Services as a latest technology on .NET platform and C# language by creating an “Online registration web application”. I am thankful to Prof. Abhilasha Tibrewal for her support, cooperation and highly appreciate her suggestions provided during the entire phase of project development.

    4. What is .NET ?

    5. What are Web Services? Web services are small units of code Web services are designed to handle a limited set of tasks Web services use XML based communicating protocols Web services are independent of operating systems Web services are independent of programming languages Web services connect people, systems and devices

    6. What Are Web Services? Although deceptively simple, XML is turning the way we build and use software inside out. The Web revolutionized how users talk to applications. XML is revolutionizing how applications talk to other applications—or more broadly, how computers talk to other computers—by providing a universal data format that lets data be easily adapted or transformed:

    7. Web Services Vs RPC/COM/RMI

    8. What's the difference between a Web service and a website? Unlike websites, which are pictures of data designed to be viewed in a browser by a person, a Web service is designed to be accessed directly by another service or software application. Web services are reusable pieces of software that interact programmatically over the network through industry recognized standards (XML and SOAP). Web services can be combined with each other and other applications to build intelligent interactive .NET experiences.

    9. Web Service Security Model Web service security can be applied at three levels: Platform/transport-level (point-to-point) security Application-level (custom) security Message-level (end-to-end) security

    10. Platform/Transport Level (Point-to-Point) Security The transport channel between two endpoints (Web service client and Web service) can be used to provide point-to-point security.

    11. Application Level Security With this approach, the application takes over security and uses custom security features. For example: 1. An application can use a custom SOAP header to pass user credentials to authenticate the user with each Web service request. A common approach is to pass a ticket (or user name or license) in the SOAP header. 2. The application has the flexibility to generate its own IPrincipal object that contains roles. This might be a custom class or the GenericPrincipal class provided by the .NET Framework. 3. The application can selectively encrypt what it needs to, although this requires secure key storage and developers must have knowledge of the relevant cryptography APIs. 4. An alternative technique is to use SSL to provide confidentiality and integrity and combine it with custom SOAP headers to perform authentication.

    12. Message Level (End-to-End) Security This represents the most flexible and powerful approach and is the one used by the GXA initiative, specifically within the WS-Security specification.

    13. Reason to choose ASP.NET over ASP: ASP.NET has been greatly improved over the ASP technology in .Net. Some of the important features of ASP.NET and the improvements over the classical ASP technology include:

    14. Reason to choose ASP.NET over ASP: ASP.NET further improves the performance by providing powerful server-side caching of the executed code for a faster response to the client. The associated ADO.NET technology for dealing with databases also has smart caching of records available in the form of the dataset for a very high performance data driven web application. ASP.NET is backwards compatible with the classical ASP technology. ASP.NET has a much easier deployment of web applications. Simply copy the web application directory to a target machine and set up the appropriate virtual directory to run the application. ASP.NET can use the ActiveX/COM components if needed through the RCW (Runtime Class Wrapper) feature of .Net. Although all new development in ASP.NET can be accomplished without the ActiveX/COM components. For creating scalable, tiered architectures, ASP.NET still uses the COM+ technology. However, the COM+ programming is made much simpler by the use of special attributes that can be specified for the .Net classes that will be converted to COM+ components.

    15. Reason to choose ASP.NET over ASP: ASP.NET provides excellent client-side data validation in the form of specialized validators. These validators generate the appropriate client-side Javascript code for data validation on the client side. Thus the need to program in Javascript directly on the client-side is greatly reduced. ASP.NET provides a powerful server-side event driven model for web application development where different HTML elements (server controls) on the client-side trigger events on the server-side (the associated code behind file for the aspx file contains the event handlers for these events). ASP.NET provides a very easy way to maintain the state of client-side elements once a server-side event is triggered by one of these elements and the form is submitted to the server. ASP.NET provides an AutoPostBack property for server-side controls so that if anything is changed in the control, the data is posted to the web server. For example, if a checkbox is checked or unchecked, the server-side event handler can be triggered if its AutoPostBack property is set to true. Although Visual Studio.Net is not required for developing ASP.NET applications, it makes the web application development much easier by providing an array of server-side controls, their visual placement and writing of the skeleton code for the event handlers for these.

    16. ASP.NET Security Architecture ASP.NET works in conjunction with IIS, the .NET Framework, and the underlying security services provided by the operating system, to provide a range of authentication and authorization mechanisms.

    17. ADO.NET Data Architecture Data access in ADO.NET relies on two components: the DataSet, which stores data on the local machine, and the Data Provider, which mediates interaction between the program and the database

    18. The DataSet The DataSet is a disconnected, in-memory representation of data. Data can be loaded into a DataSet from any valid data source, such as a Microsoft SQL Server database, a Microsoft Access database, or an XML file. The DataSet is persisted in memory, and the data therein can be manipulated and updated independent of the database. The DataSet object contains a collection of zero or more DataTable objects, each of which is an in-memory representation of a single table. The structure of a particular DataTable is defined by the DataColumns collection, which enumerates the columns in a particular table, and the Constraint Collection, which enumerates the constraints on the table.

    19. Steps to create a DataSet Object The basic approach for transferring data from a data source into a DataSet can be set out as follows: Create a connection object Create a command object to hold our SQL statement Create a DataSet object Create one or more DataTable objects in the DataSet Create a data adapter with the connection and command objects Use the Fill() method of the data adapter to transfer data (and it schema) from the connection object into a DataTable of the DataSet.

    20. Disconnected Database Access As applications become more complex and databases begin to serve more and more clients, a connected data access technology becomes impractical for a variety of reasons. For example: Open database connections are expensive in terms of system resources. The more open connections, the less efficient system performance becomes. Applications with connected data access are very difficult to scale up. An application that can maintain connections with two clients might do poorly with 10, and might be completely unusable with 100.   ADO.NET addresses these issues by implementing a disconnected database access model by default.

    21. Online Registration Web Application The main modules of the Application include: - Ø     Client Module (.NET Web Application): - This module comprises of the Web Forms (.aspx Files) by which, the methods of the web service (Server Methods) are invoked. Ø     Server Module (.NET Web Service): - This module (.asmx files) basically acts as a mediator between the client and the database. It has datasets for storing required information about student information, administrator information, and course information. It queries the database based on the request made by the clients.   Ø     Database Module: - It (.mdb files) comprises of the databases for storing information about student information, course information, student account information, authorized user information, and administrator information and it responds to the Server queries.

    22. Implementation Details Client Module: - This module is implemented as a .NET Web Application that includes .aspx files (Web Forms) and. aspx.cs files (C#, code behind the form). The Web Forms in this module are as follows: -

    23. Implementation Details Client Module: - This module is implemented as a .NET Web Application that includes .aspx files (Web Forms) and. aspx.cs files (C#, code behind the form). The Web Forms in this module are as follows: -

    24. Implementation Details Client Module: - This module is implemented as a .NET Web Application that includes .aspx files (Web Forms) and. aspx.cs files (C#, code behind the form). The Web Forms in this module are as follows: - Add Course WebForm: (WebForm3) - This WebForm enables the student to select and add course he wants to register for. Drop Course WebForm: (WebForm4) - This WebForm enables the student to select and drop course he/she wants to drop.

    25. Implementation Details Server Module: - This module is implemented as a .NET Web Service consisting of .asmx Files.

    26. Implementation Details The .asmx File has following Web Methods through which the client Communicates with the Server: - GetID() – Queries Student ID and Password in Student Data Table in db1.mdb(MS Access) database and stores it in a DataTable “Course” in myDS Dataset used to sign in as a student. GetPassword()- Queries Password in Student Data Table in db1.mdb(MS Access) database and stores it in a DataTable “aa” in myDS_2 Dataset used to sign in as a student. GetDrop()- Queries StudentCourse.StudentID, StudentCourse.CourseID, CourseName, course_date, course_time, Credit, Faculty, Campus, Capacity, Status, Enrollment in StudentCourse Data Table in db1.mdb(MS Access) database and stores it in a DataTable “aa” in myDS_2 Dataset used to select the course student want to drop.

    27. Implementation Details The .asmx File has following Web Methods through which the client communicates with the Server: - GetStudentID()-Queries StudentCourse.StudentID, StudentCourse.CourseID in StudentCourse Data Table in db1.mdb(MS Access) database and stores it in a DataTable “cc” in myDS_2 Dataset used to select the course registered by students and courses taken by student. GetCS_Courses() - Queries Course Information in Course Data Table in db1.mdb(MS Access) database and stores it in a DataTable “bb” in myDS_2 Dataset, used to display the course offered on a Datagrid in WebForm3.aspx. Balance()- Queries StudentID, Pass, PreviousAccountBalance, CurrentAccountBalance in StudentAccount Data Table in db1.mdb(MS Access) database and stores it in a DataTable “Account” in myDS Dataset, used to display the Account Balance on a Datagrid in WebForm1.aspx.

    28. Implementation Details The .asmx File has following Web Methods through which the client Communicates with the Server: -

    29. Implementation Details The Database Module contains following tables :

    30. Conclusion This project reflects the performance of the latest technologies - “Web Services, & .NET “ based on my best efforts and hard work.

    31. References Beginning ASP.NET by Chris Ullman, John Kauffman, Chris Hart, David Sussman, Wrox Publishers. Professional C# by Simon Robinson, Karli Watson, Burton Harvey, Jay Glynn, Christian Nagel, Wrox Publishers. CSS 555 Notes, Prof.Ausif Mahmood, www.bridgeport.edu. www.microsoft.com/net www.asp.net www.threeguysfromroilla.com

More Related