《票务易购系统之火车票板块毕业设计（论文）.doc》由会员分享，可在线阅读，更多相关《票务易购系统之火车票板块毕业设计（论文）.doc（74页珍藏版）》请在三一办公上搜索。
1、大连交通大学信息工程学院毕业设计(论文)任务书题 目票务易购系统之火车票板块任务及要求：1.设计（研究）内容和要求任务：1、 调查票务系统当前技术的发展近况，完成实习报告，字数不少于3000，第三周交给指导老师。2、 结合自己实习情况安排进度，填写进度计划表，第二周完成后交给指导老师签字，并严格执行。3、 按照软件工程思想，独立完成系统的设计和程序开发，完成代码估计2000行左右。4、 用JSP技术实现票务系统基本功能。5、 程序简洁，算法可行，运行情况良好。要求：1、 每周和指导老师至少见面沟通一次，回报课题进展情况，接受老师询问。2、 接到任务书后，查阅与题目及专业相关的外文资料进行翻译，
2、要求不少于10000个外文字符，译出汉字不得少于3000，于第四周交给指导老师审阅。3、 毕业设计第13周完成毕业论文的装订，并由指导老师评阅。论文要求12000字以上，包括综述、系统总体设计、系统实现、性能分析、结论等。4、 教学第13周通过中软及教研室组织进行软件验收，验收时要提供软件使用说明书。5、 于第13周提出毕业答辩申请并签字。6、 第14 周答辩，要求制作PPT2.原始依据通过大学几年的学习，已经学习了诸如软件工程、数据库原理及应用、数据结构、C+、Visual Basic、JAVA等多门程序设计语言和网络等基础知识和专业知识，学生有能力而且可以独立完成小中型项目的设计与开发。学
3、校现有设备和环境可以提供给学生实习和上机，而且具有专业老师可以指导学生。3.参考文献1 孙鑫.Servlet/JSP深入详解-基于Tomcat的Web开发.电子工业出版社.2008-8-12 Bergsten，HOReilly JavaAmerican:Sernni Yey3 张孝祥，徐明华JSP基础与案例开发详解清华大学出版社2009-8-14 李丹丹SQL Server 2000数据库实训教程清华大学出版社2007-8-15 王毅SQL应用开发范例宝典：软件工程师典藏人民邮电出版社2008-7-16 杨林软件工程实践教程（第2版）电子工业出版社2011-4-17 朱少民软件测试方法和技术（
4、第二版）清华大学出版社2010-7-18 伊乐斯架构实战软件架构设计的过程机械工业出版社2010-4-19 Paaton,R软件测试（英文版第二版）机械工业出版社2006-1-110 多布斯软件测试与持续质量改进人民邮电出版社2011-7-111 张华祥,刘弘.Java语言基础教程M.北京:清华大学出版社,200712 耿祥义,张跃平.Java课程设计M.北京:清华大学出版社,200813 耿祥义,张跃平.JSP使用教程M.北京:清华大学出版社,2007指导教师签字：教研室主任签字： 年 月 日大连交通大学信息工程学院毕业设计(论文)进度计划与考核表学生姓名付婷婷专业班级软件工程08-3班指导
5、教师阎树昕 刘瑞杰本课题其他人员无题目票务易购系统之火车票板块日期计划完成内容完成情况指导老师检查签字第1周实习调研，查阅课题相关外文资料第2周了解行业状况、查阅文献资料，阅读资料，撰写调研报告第3周完成后台数据库的设计并编码，完成部分论文第4周进行需求分析第5周进行概要设计第6周进行概要设计, 基本框架完成，提交毕业论文提纲第7周完成后台数据库的设计并编码，完成部分论文第8周完成后台数据库的设计并编码，完成部分论文第9周继续编码并进行测试，继续编写毕业设计论文第10周继续进行程序测试，继续编写毕业设计论文第11周整理资料、文档、图表等，修改毕业设计论文第12周完成毕业设计论文，打印，按要求装
6、订第13周软件验收和准备毕业设计答辩第14周毕业设计答辩及成绩评定指导教师签字： 年月日注：“计划完成内容”由学生本人认真填写，其它由指导教师考核时填写。大连交通大学信息工程学院毕业设计(论文)外文翻译学生姓名 付婷婷 专业班级 软件工程08-3班指导教师 阎树昕刘瑞杰 职 称 高工讲师 所在单位 信息科学系软件工程教研室 教研室主任 刘瑞杰 完成日期 2012年4月13日How to troubleshoot connectivity issues in SQL Server 2000This article can help you to resolve connectivity prob
7、lems with Microsoft SQL Server 2000. This article contains descriptions of common connectivity problems and the steps that you can take to help resolve your connectivity problems. SQL Server 2000 supports several methods of communication between the instance of SQL Server and the client applications
8、. If your client application and the instance of SQL Server reside on the same computer, Microsoft Windows interprocess communication (IPC) components, such as local named pipes or the Shared Memory protocol, are used to communicate. However, when the client application and the instance of SQL Serve
9、r reside on different computers, a network IPC, such as TCP/IP or named pipes, is used to communicate.SQL Server 2000 uses Net-Library, a DLL, to communicate with a particular network protocol. A matching pair of Net-Libraries must be active on the client computer and the server computer to support
10、the network protocol that you want to use. For example, if you want to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net-Library (Dbnetlib.dll) must be configured to connect to the server on the client computer. Likewise, t
11、he server TCP/IP Sockets Net-Library (Ssnetlib.dll) must listen on the server computer. In this scenario, the TCP/IP protocol stack must be installed on both the client computer and the server computer.After you install SQL Server 2000, you can configure the properties of the client Net-Libraries by
12、 using Client Network Utility. You can configure the properties of the server Net-Libraries by using Server Network Utility (Svrnetcn.exe). The server Net-Libraries are installed during the installation of the server tools in SQL Server Setup. However, some of the server Net-Libraries may not be act
13、ive. By default, SQL Server 2000 enables and listens on TCP/IP, named pipes, and Shared Memory. Therefore, for a client to connect to a server computer, the client must connect by using a client Net-Library that matches one of the server Net-Libraries that is currently being used by the instance of
14、SQL Server.For additional information about SQL Server communication components and Net-Libraries, see the following topics in SQL Server Books Online: Communication ComponentsClient and Server Net-LibrariesManaging ClientsMost of the connectivity issues that you may notice in SQL Server 2000 occur
15、because of problems with TCP/IP, Windows authentication, or a combination of TCP/IP and Windows authentication. Important Before you start to troubleshoot connectivity issues in SQL Server 2000, make sure that the MSSQLServer service is started on the computer that is running SQL Server.Verify your
16、DNS settingsThe name resolution process in Domain Name System (DNS) is used to resolve the IP address to the name of the instance of SQL Server. If the name resolution process does not work correctly, the instance of SQL Server is not reachable, and you may receive one or more of the following error
17、 messages: SQL Server does not exist or access deniedGeneral Network ErrorCannot Generate SSPI ContextTo verify that the name resolution process is resolving the correct server, you can ping the server by using the server name and the IP address of the server. To do so, follow these steps: 1.Click S
18、tart, and then click Run.2.In the Run dialog box, type cmd in the Open box, and then click OK.3.At the command prompt, run the following command:ping Note the IP address that is returned.4.At the command prompt, run the following command (where IP address is the IP address that you noted in step 3)p
19、ing a Verify that the command resolves to the correct server name. If either of the specified commands are not successful, time out, or do not return the correct values, the DNS lookup is not working correctly or the problem occurs because of other networking or routing issues. To see your current D
20、NS settings, run the following command at a command prompt:To %systemroot%system32driversetchosts file on the client computer. You can also work around the problem by connecting to the server by using the Named Pipes Net-library.Verify the enabled protocols and aliasesConnectivity problems may occur
21、 if the alias on the client computer is set incorrectly. You can view the aliases by using Client Network Utility. To do so, follow these steps: 1.Start Client Network Utility. If the SQL Server client tools are installed on the computer that is running the client application, follow these steps to
22、start Client Network Utility: a. Click Start, and then point to Programs.b. Point to Microsoft SQL Server, and then click Client Network Utility.If the SQL Server client tools are not installed on the client computer, follow these steps to start Client Network Utility: a. Click Start, and then click
23、 Run.b. In the Run dialog box, type cliconfg in the Open box, and then click OK.2.In the SQL Server Client Network Utility window, click the General tab, and then enable all the protocols that you want to use.Note You must at least enable the TCP/IP protocol and the named pipes protocol.3.Click the
24、Alias tab, and then verify the aliases that are configured for the instance of SQL Server. 4.Verify the properties of the aliases to make sure that the server name or IP address and the protocol are configured correctly.You can create a new alias to test the connectivity by using the server name, th
25、e IP address, or even by using a different protocol.Note Earlier versions of Microsoft Data Access Components (MDAC) have a different user interface for Client Network Utility. Therefore, if you do not see the options that are listed in this article, install a later version of MDAC on the computer t
26、hat is running the client application.Verify that the instance of SQL Server is listening correctlyTo verify that the instance of SQL Server is listening on named pipes, TCP/IP, or another protocol that you are using at the client application, open the current SQL Server error log file. The SQL Serv
27、er error log file may contain entries that are similar to the following:2003-11-06 09:49:36.17 server SQL server listening on TCP, Shared Memory, Named Pipes. 2003-11-06 09:49:36.17 server SQL server listening on 192.168.1.5:1433, 127.0.0.1:1433.If you analyze the entries in the SQL Server error log
28、 file, you can verify that the instance of SQL Server is listening on the correct IP address and on the correct port. By default, a default instance of SQL Server listens on the port 1433. You can also use Server Network Utility to verify the protocol settings for SQL Server and to change the proper
29、ties in SQL Server, including the protocols that can connect to SQL Server and the ports that can be used. For more information about using Server Network Utility, see the SQL Server Network Utility topic in SQL Server Books Online. Sometimes, SQL Server 2000 may not bind to port 1433 or any other s
30、pecified port. This problem may occur if the port is being used by another application or if you are trying to connect by using an IP address that is not correct. Therefore, the TCP/IP connections to SQL Server may not be successful and you may receive the following error message in the SQL Server e
31、rror log file: 2001-11-14 15:49:14.12 server SuperSocket Info: Bind failed on TCP If you cannot connect to the instance of SQL Server by using a TCP/IP connection, try to use the named pipes protocol or the Shared Memory protocol. Run the following command at a command prompt to obtain information a
32、bout the ports that are in use:You can also use the Portqry command-line utility to obtain more information about the ports that are in use.Note For named instances of SQL Server, SQL Server dynamically determines the port and listens on the determined port. Therefore, when you start the named insta
33、nce of SQL Server, SQL Server tries to listen on the port that was previously being used. If SQL Server cannot bind to that port, the named instance may dynamically bind to a different port. In that situation, make sure that the client application is also set to determine the port dynamically. Alter
34、natively, you can also specify a static port for the named instance to bind to and to listen on by using Client Network Utility.Connectivity problems may also occur because of problems with MDAC. For example, a software installation may overwrite some of the MDAC files or change the permissions that
35、 you must have to access the MDAC files. You can run the MDAC Component Checker to verify the MDAC installation on your computer.Note If you are connecting to a named instance of SQL Server, make sure that you are running MDAC 2.6 or later on your computer. Earlier versions of MDAC do not recognize
36、named instances of SQL Server. Therefore, connections to named instances may not be successful.You can use the Odbcping.exe utility to verify connections through the SQL Server ODBC driver.You can also test connectivity to the instance of SQL Server by using a .udl file.Troubleshoot firewall issuesI
37、f firewall exists between the client computer and the computer that is running SQL Server, make sure that the ports that are required to communicate through the firewall are open.If you use the TCP/IP protocol to connect to the instance of SQL Server, make sure that you can use the Telnet program to
38、 connect to the port where SQL Server is listening. To use the Telnet program, run the following command at a command prompt: Telnet If the Telnet program is not successful and you receive an error message, resolve the error and then try to connect again.Note Because of issues that were caused by th
39、e Slammer virus, the User Datagram Protocol (UDP) port 1434 may be blocked on your firewall.Troubleshoot authentication and security issuesConnections to SQL Server may not be successful because of authentication failures. If the authentication fails, you may receive one of the following error messa
40、ges:Login failed for user Login failed for user NTAUTHORITYANONYMOUS LOGONLogin failed for user nullIf you receive an error message because of an authentication failure and the error message does not mention a specific SQL Server login name, troubleshoot the problem with Windows authentication. You
41、may receive the following error message because of problems with Windows authentication: Cannot generate SSPI ContextThe following problems may cause authentication and security issues: Problems occur with NTLM authentication or with Kerberos authentication.The domain controller cannot be contacted
42、because of connectivity issues.Problems occur with trust relationships across domains.For more information about possible causes, see the event logs on the computer. To work around connectivity problems with Windows authentication, you can use SQL Server Authentication to connect to the instance of
43、SQL Server. If the connection is not successful when you use SQL Server Authentication, you receive the following error message: Login failed for user . Not associated with a trusted connectionTo troubleshoot this problem, follow these steps. Warning If you use Registry Editor incorrectly, you may c
44、ause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. 1.Make sure that the instance of SQL Server is configured to use Windows aut
45、hentication and SQL Server Authentication. To do so, make sure that the following registry keys are on the computer that is running SQL Server. For the d Server:HKEY_LOCAL_MACHINESoftwareMicrosoftMSSQLServerMSSQLServerLoginModeFor the named instance of SQL Server: HKEY_LOCAL_MACHINESoftwareMicrosoft
46、MicrosoftSQLServerMSSQLServerLoginModeMake sure that the following registry key values are set:Authentication typeValueWindows authentication only1Mixed mode (SQL Server Authentication and Windows authentication)2Note If you make any changes to the registry, you must stop and then restart the instan
47、ce of SQL Server for the changes to take effect.2.Try to connect to the instance of SQL Server by using different Windows accounts or SQL Server login accounts. This can help determine if the connection is not successful because of problems with a particular login account. For example, the password of the login account may have been changed.3.Try to connect to the instance of SQL Server by using different protocols. For example, the connections that use the TCP/IP proto
