Výsledky vyhledávání - "SQL *Loader"
-
1
Autoři:
Resource Type: eBook.
Témata: Relational databases, SQL (Computer program language), Programming languages (Electronic computers)
Categories: COMPUTERS / Database Administration & Management
-
2
Autoři: Moore, Dave.
Zdroj: Indeks.
Témata: ORACLE (system informatyczny)
Přístupová URL adresa: http://katalog.nukat.edu.pl/lib/item?id=chamo:346393&theme=nukat
-
3
Autoři:
Zdroj: Oracle Internals ISBN: 9780849311390
-
4
Autoři:
Přispěvatelé:
Témata: Tutor de aprendizaje - Diseño, Herramienta SQL, Ingeniería de sistemas, TESIS - FACULTAD INGENIERÍA, TECNOLOGÍA, APRENDIZAJE, Sistema Operativo, Unix, Software libre, Tutor de aprendizaje, Oracle, Sql * Loader
Geografické téma: Bogotá
Popis souboru: PDF; application/pdf
Relation: Barba Martin, L. (2002). Pedagogia y relacion educativa. Ciudad de Mexico: Centro de Estudios Sobre la Universidad : Plaza y Valdes.; Bernárdez, M. L. (2007). Diseño, producción e implementación de E-learning. Global Bussines Press.; Libre, S. d. (2011). Colombia; Nazareno, I. G., Olarte, D. F., & Informáticos., 2. C. (3 de Febrero de 2010). CARGAS MASIVAS CON SQL * LOADER.; Olarte, D. F. (2010). Cargas Masivas con SQL * Loader.; Oracle. (2005). Oracle® Database Utilities. Obtenido de http://docs.oracle.com/cd/B19306_01/server.102/b14215/ldr_concepts.htm #i1007844; Pérez, K. C. (Agosto de 2011). TUTORES EN AMBIENTES VIRTUALES DE APRENDIZAJE. Bogotá, Colombia.; Rivera, F. L. (2008). Bases de datos Relaciones Teoria y practica. Medellin, Antioquia, Colombia: Fondo editorial ITM.; Urman, S. (2002). Oracle9i Programación PL/SQL. Madrid, España: McGraw Hill.; Valparaíso, P. U. (2011). Biblioteca ágora. Obtenido de http://agora.ucv.cl/manual/2parte_recetas/curro%202part/tutoria/tutoria.ht ml; https://hdl.handle.net/10901/8429; instname:Universidad Libre; reponame:Repositorio Institucional Universidad Libre
Dostupnost: https://hdl.handle.net/10901/8429
-
5
Autoři:
Přispěvatelé:
Témata: Datorzinātne, Oracle SQL Developer, Sqlplus, SQL Loader, Slodze, Docētāji
Relation: 64990; https://dspace.lu.lv/dspace/handle/7/38662
Dostupnost: https://dspace.lu.lv/dspace/handle/7/38662
-
6
Autoři:
Přispěvatelé:
Témata: Docētāji, Oracle SQL Developer, SQL Loader, 4. Education, Datorzinātne, Slodze, Sqlplus
Přístupová URL adresa: https://dspace.lu.lv/dspace/handle/7/38662
-
7
Autoři:
Přispěvatelé:
Relation: 68647; https://dspace.lu.lv/dspace/handle/7/46381
Dostupnost: https://dspace.lu.lv/dspace/handle/7/46381
-
8
Autoři:
Zdroj: Jurnal Pendidikan dan Teknologi Indonesia. 5:955-967
-
9
-
10
Autoři:
Témata: Computing and Computers
Relation: http://cds.cern.ch/record/1511111; oai:cds.cern.ch:1511111
Dostupnost: http://cds.cern.ch/record/1511111
-
11
Autoři:
Přispěvatelé:
Zdroj: DTIC AND NTIS
Témata: Computer Programming and Software, OPTIMIZATION, RELATIONAL DATA BASES, DATA STORAGE SYSTEMS, INTERROGATION, AUSTRALIA, BATCH PROCESSING, C PROGRAMMING LANGUAGE, JAVA PROGRAMMING LANGUAGE, SOFTWARE METRICS, INSERTION TECHNIQUES, DATA INSERTION, PL/SQL PROGRAMMING LANGUAGE, PRO*C PROGRAMMING LANGUAGE, OCI PROGRAMMING LANGUAGE, SQL*LOADER PROGRAMMING LANGUAGE, JDBC PROGRAMMING LANGUAGE, SQLJ PROGRAMMING LANGUAGE, ORACLE COMPUTER PROGRAM, QUERY RETRIEVAL, AQ F03-09-2220, FOREIGN REPORTS
Popis souboru: text/html
-
12
Autoři:
Přispěvatelé:
Témata: SQL*Loader
Popis souboru: application/pdf
-
13
Autoři:
Přispěvatelé:
Popis souboru: application/pdf
Relation: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.258.8624; http://research.ijcaonline.org/volume54/number13/pxc3882538.pdf
-
14
Autoři:
Přispěvatelé:
Zdroj: urn:tid:202550265
Popis souboru: application/pdf
Dostupnost: http://hdl.handle.net/10400.22/16896
-
15
Autoři:
Zdroj: DTIC AND NTIS
Témata: Computer Programming and Software, OPTIMIZATION, RELATIONAL DATA BASES, DATA STORAGE SYSTEMS, INTERROGATION, AUSTRALIA, BATCH PROCESSING, C PROGRAMMING LANGUAGE, JAVA PROGRAMMING LANGUAGE, SOFTWARE METRICS., INSERTION TECHNIQUES, DATA INSERTION, PL/SQL PROGRAMMING LANGUAGE, PRO*C PROGRAMMING LANGUAGE, OCI PROGRAMMING LANGUAGE, SQL*LOADER PROGRAMMING LANGUAGE, JDBC PROGRAMMING LANGUAGE, SQLJ PROGRAMMING LANGUAGE, ORACLE COMPUTER PROGRAM, QUERY RETRIEVAL, AQ F03-09-2220, FOREIGN REPORTS, Text
-
16
Autoři: a další
Zdroj: CISTI (Iberian Conference on Information Systems & Technologies / Conferência Ibérica de Sistemas e Tecnologias de Informação) Proceedings; 2019, p1-6, 6p
-
17
Autoři:
Popis souboru: application/pdf
Relation: Technical report (University of Alabama at Birmingham. Department of Electrical and Computer Engineering); 2018-08-ECE-128; Technical report (Southern Methodist University. Department of Computer Science and Engineering); 2001-10-ECE-011; Technical Report 2018-08-ECE-128 Technical Report 2001-10-ECE-0 11 TheN-Queens Test Bed Sachin Chincholikar Ozgur Aktunc Murat M. Tanik This technical report is a reissue of a technical report issued September 2001 Department of Electrical and Computer Engineering University of Alabama at Birmingham August 2018 Technical Report 2001-10-ECE-011 The N-Queeus Test Bed Sachin Chincholika:r Ozgur Aktunc Murat M. Tanik TECHNICAL REPORT Department of Electrical and Computer Engineering Uruversity of Alabama at Birmingham September 2001 ABSTRACT This technica1 report provides detailed infonnation about theN-Queens test bed. This enterprise test-bed has been created with several enabling technologies such as Java, XML, and DBMS software. The components of the application have been explained in detail and the results gathered are listed in this report. 2 TABLE OF CONTENTS INTRODUCTION OF N-QUEENS TEST BED APPLICATION N-Queens Problem The Project JAVA WEB SERVER FEATURES AND INSTALLATION Features of Java Web Server Installation SERVLETS What are Servlets. Features ofServlets ORACLE DATABASE Why Oracle? Use of Oracle for N-Queens Features of Oracle Installation and Configuration of the Oracle Database 5 5 7 14 14 17 25 25 26 29 29 30 32 33 3 L.MX PROCESSOR What is L.MX? L.MX in N-Quee.n.c;; Application RESULTS FUTURE IlVfPROVE.MEl\TTS OF N-QUEENS APPLICATION APPENDIX REFERENCES 35 35 36 37 38 39 47 4 INTRODUCTION OF N-QUEENS TEST BED APPLICATION N-QUEENS PROBLEM TheN-Queens problem, is a generation of the 8-Queens problem, which has been studied for more than a century. The N-Queens problem, as the more general form of the 8-Queens problem was first proposed in 1867 (Campbell1977). TheN-Queens problem can be defined as follows: place N queens on an NxN chessboard, one queen on each square, so that no queen captures any of the others, that is, a configuration in which there exists at most one queen on the same row, column or diagonals. A representation ofN-Queens problem is given on a chessboard in Figure 1.1. During the last three decades, the problem has been discussed in the context of computer science and used as an example of backtrack algorithms, pe1mutation generation divide and conquer paradigm, program development methodology constraint satisfaction problems, integer programming, specification, and neural networks. Some practical applications of theN-Queens problem such as, VLSI 5 testing, traffic control, and deadlock prevention, are also mentioned in the website. Figure 1.1 -Representation ofN- Queens problem on chessboard 6 THE PROJECT A three-tier architecture based enterprise development test-bed, comprising of Java Server-side technologies like servlets and JDBC, eXtensible Markup Language (XML) and Oracle 8i database ·was developed to provide solutions of the N-Queens problem. This project was being developed as a test-bed on top of various strategies and technologies that are implemented to develop enterprise software applications. It demonstrates the use of three-tier architecture, one of the most efficient approaches to build enterprise software applications. It also shows the use of Java and XML technologies, the two distinctive technologies for enterprise development, along with Oracle 8i as a database. The enterprise development test-bed can be accessed over the Internet. The project data is stored in a backend database in Oracle 8i sofuvare. By using Java servlets and JDBC technology in the middle tier, the data is made available to the users. In addition, the enterprise development test-bed allows creating, viewing, and listing of documents in XML format. The information entered by the user at the front end is converted to the XML format in the middle layer, and stored in the XML format at the back-end. When the user wants to view the stored information, it is converted back from XML to HTML using a XML parser. 7 Project Description. The architecture of the project is as shown in the Figure 1.2. It primarily consists of three building blocks: User Interface which acts as a front end of the enterprise development test-bed, Server part which acts as a middle layer and a Data Storage which acts as a backend of the enterprise development test-bed. User Interface part is ptimarily consisted of HTML pages linked to each other. It acts as a front end of the application and serves the user with the information about the app1ication and accepts the user's request. t i~t~)"; I;,i~:d'n~·~! I ~-lLI .\{(\1~ ·-l ";1. . .:{ '"";'- ,,)1-1',' • ~·~. .- ·L- --- ·- ., ,~--__:: . 1 ~>; l I i I ~ I ,.J I 11 g~ . ,. \'l~wl\54• S(ErrorMessages.j ava :33) at com.sun.server.ServerProcess. (ServerProcess.java:51) at java.lang.Ciass.forNameO(Native Method) at ja va.lang. Class. forN arne( Compiled Code) at sun.secmity.Logiu.getClass(Login.java:78) at sun.secmity.Login.main(Compiled Code) To avoid this problem, disable the ITT. (Note that disabling the TIT will have a negative impact on performance.) To disable the JIT, start the server using the jserv startup script and specify ";-vmargs -Djava.compiler=NONE". For example: 17 jserv -javahome d:\idk1.2 -vmargs -Djava.compiler=NONE When running Java Web Server with Java 2, resource locations relative to the parti tion root(\), the dtive containing the Java Web Server, are not resolved properly. (Bug 4256359) This means that you must specify the drive letter when setting protection or aliases for resources not contained in the server _root. For example, rather than specifying the file pathname as: \home\$user\public _ html\text. txt You would specify it as: c: \home\$user\public _ html\text. txt 18 INSTALLING JAVA WEB SERVER ON WINDOWS PLATFORM A. Supported Platforms B. Prerequisites C. Defaults Installation Directory Java Runtime Environment Ports D. Installation SUPPORTED PLATFORMS The Java Web Server(tm) is officially supported only under the Solaris(tro) SPARC(tm) and Windows NT environments. ·windows 95 is supported for development but not for deployment. \Vhile Java Web Server 2.0 can run on any platform that supports the JDK 1.1. 7, platforms other than Solaris and Windows are untested and therefore unsupported. To use the Java Web Server, you need a server environment as well as a client environment. 19 For the server environment: You require a Java Development Kit (JDK) 1.1.7 or a JDK 1.1.7-compliant Java Runtime Environment (IRE). Note: Java Web Server 2. 0 bundles a JDK 1.1. 7 -compliant JRE which it will use by default. This is the recommended way to run the Java Web Server. For the client environment: You require a JDK 1.1-compatible browser to run the Java Web Server administrative tools. Note: Most recent browsers are JDK 1.1-compatible. Cunent versions ofNetscape Navigator ( 4.5) and Microsoft Internet Explorer ( 4. 0) are known to be compatible. 20 PREREQUISITES Hardware and Operating System Prerequisites Minimwn Intel 486-based PC 32MB RAM Windows 95 (with Winsock 2*) OR Windows NT 4.0 * Windows Sockets 2 (WinSock 2) may be downloaded from Microsoft's website at: http://www.microsoft.com/windows95/downloads/contents/ wuadmintools/s_ wunetworkingtools/w95sockets2/default.asp Recommended Intel Pentium 166 (or higher)-based PC 64MB RAM Windows NT 4.0 with Service Pack 4 The compressed. file is approximately 8.5 MB. To install it, you require roughly 13MB of hard drive space. 21 DEFAULTS Installation Directory By default, the product installs into C:\Java WebServer2.0\ (Windows example) The directory path containing the installed Java Web Server 2.0 product is referred to as the. This term is used tbmughout the product documentation. Note: The default installation path means an entry is not made in the Start -> Programs listing. Installing into a directory path that contains spaces is not recommended. For example, installing into C:\Program Files\ may cause problems for envirorunent variables used by the Java Web Server. 22 Java Runtime Environment (JRE) Java Web Server 2.0 supports JDK 1.1.7 or JDK.l.1.7-compliant JREs. By default, JRE 1.1.7 is automatically installed in the \ire directory. Where is the the directory containing the installed Java Web Server product. For example C:\JavaWebServer2.0\jre\ Ports (Windows example) The Java Web Server 2.0 installs its services on the following ports: Web Service 8080 Secure Service 7070 These ports can be changed after installation using the Java Web Server Administration Tool, the product documentation tells you how. The Administration Tool is accessible on pott 9090. 23 INSTALLATION on WINDOWS 1. Place the self-extracting lite on your machine Download the Java Web Server self-extracting file (.cxe) from the Java Web Server web site (or copy the self-extracting file from the CD) onto your machine. 2. Extract installation files and launch setup Double-click on the self-extracting file to extract the Java Web Server temporary jnstallation files into the directory and launch the Setup program. 3. Follow the setup program's instructions Follow the jnstmctions in the Setup program to install Java Web Server in a directory location on your hard disk. Installation into a directory path containing spaces, such as C:\Program Files\ is not recommended as it may cause problems with environment variables used by the Java Web Server. By default, Setup installs Java Web Server in C:\JavaWebServer2.0 24 SERVLETS WHAT ARE SERVLETS ? Servlets are protocol- and platform-independent server side components, written in Java, which dynamically extend Java enabled servers. They provide a general framework for services buHt using the request-response paradigm. Their initial use is to provide secure web-based access to data which is presented using HTML web pages, interactively viewing or modifying that data using dynamic web page generation techniques. Since servlets run inside servers, they do not need a graphical user interfac.e. Otherwise, they are the server side counterpart to applets (which are used only on the client side of systems): they are Java application components which are downloaded, on demand, to the pmt of the system which needs them. Servlets are most often provided by organizations which provide customized multi-user services to their customer bases. However, serv'lets are also flexible enough to support standardized services such as serving static web pages through the HITP (or HTTPS) protocols, and proxy services. Since they are used for dynamic extensibility, they may be used in a plug-in style, supporting facilities such as search engines and semi-custom 25 applications. Servlets also provide a strong platform for semi-custom applications, such as web-based order entry or inventory systems. Although all servlets are written in Java, their clients may be written in any language. When servlets are used in the middle tiers of distributed application systems, they can in tum be clients to other services, written in any language. For example, servlets can use JDBC™ to contact an application's highly hmed relational databases. Communicating with other kinds of current or legacy systems may call for alternate software packages, as required by those systems. FEATURES OF SERVLETS The servlet API is already supported by most Java based web servers, and implementations are available for other popular web servers. This means that you get the Java Advantage when you use the servlet API: not only will your code not have memory leaks and suffer from hard-to-find pointer bugs, but your code runs on platforms from many server vendors. You don't need to lock yourself into a single-vendor server extension API, using errorprone languages such as Cor scripting languages. Instead, you can do all of your server (and client) development in a single development language. No longer does your team need to juggle multiple languages, and cope with the maintainability problems inherent in 26 sctipting languages. No longer do your web-based applications need to suffer the performance and portability penalties of CGI. Java is the professional programming tool you need to provide robust server solutions. Since servlets handle multiple requests concurrently, the requests can be synchronized with each other to support collaborative applications such as on-line conferencing. Since servlets are Java objects, they have instance-specific data. This means that in effect servlets are independent applications running within servers, without needing the complexity of additional classes (which are required by some alternative server extension APis. Servlets have access to some servlet-specific configuration data at initialization time. This allows different instances of the same servlet class to be iuitialized with difJerent data, and be managed as differently named servlets. Servlets have access to information about their clients. When used with secure protocols such as SSL, peer identities can be determined reliably. Servlets relying on HTTP also have access to HTTP-specific authentication data. Servlets have the Java advantage: memory access violations and strong typing violations are not possible. 27 Servlets are tightly integrated with servers. This integration allows a servlet to cooperate with the server in a ways a CGI program cannot. The elegance of servlet coding is striking. Servlet code is clean, Object oriented, modular, and amazingly simple. The reason for this simplicity is the servlet API itself, which includes methods and classes to handle many of the routine chores of servlet development. The servlet API is designed to be easily extensible. As it stands today, the API includes classes with specialized support for HTTP servlets. But at later date, it could be extended and optimized for another type of servlets either by sun or third party. 28 ORACLE DATABASE WHY ORACLE? Oracle, the database for Internet computing, changes the way infotmation is managed and accessed to meet the demands of the Internet age, while providing significant new features for traditional OnLine Transaction Processing (OLTP) and data warehouse applications. It provides advanced tools to manage all types of data in Web sites, and it also delivers the performa11ce, scalability, and availability necessary to support Very Large DataBase (VLDB) and mission-critical applications. Oracle introduces new support for Java by including a robust, integrated, and scalable Java Virtual Machine (VM) within the server, named Oracle JServer. This expands Oracle's support for Java into all tiers of applications, allowing Java programs to be deployed where they perform best--in the client, server, or middle tier--without recompiling or modifying the Java code. Oracle extends the functionality of advanced replication, focusing on mass-deployment applications. Data can be replicated to servers that are closer to users and have only the data those users need, providing better performance. Security has been improved. The replication manager has been rewritten in Java and is no longer constrained to run on a Windows-based machine. 29 While Orac1e has expanded its support of multimedia data through interMed.ia, and other complex data types through the separately packaged Visual Information Retrieval, Time Series, and Spatial options, it has also provided a new extensible architecture for independent software vendors (ISVs) and other developers to exploit when developing support for new types of data or specialized processing. There is significant enhancement to Oracle's object relational technology, and Oracle makes it available in both the standard edition and the Enterprise Edition. Oracle is designed to access and manage all your data using the style and infrastructure of the Intemet. Oracle is the most complete and comprehensive platform for building, deploying, and managing Internet and traditional applications USE OF ORACLE FOR N-QUEENS Oracle database is the DBMS software for the N Queen application. This component is basically divided into two parts, an XML file storage on the directory stmcture and a database to store Queen solutions. Directory structure is used as data storage for the XML files and Oracle 8i is used as a database to store the data in of the Queen solutions. These two parts wi11 be explained in the following section. Oracle 8i is used as database software to Queen solutions. To store Queen solutions a table named Queen is created and data is stored tlu·ough SQL. To generate the ql.leen 30 solutions using Rohl and Wirth algorithms, Java programs are created which generated queen solutions. These solutions are stored in a text :file. The data from these text files is then inserted into Oracle database using SQL Loader utility of the Oracle database. This utility takes the text files or any other type of fi les, pass them through a SQL Loader utility which converts the data into SQL format and inserts the data into the speci tied table in the database. The table to store the data is created by using Structured Query Language (SQL). SQL allows users to ACCESS data in Relational Data Base Management systems such as oracle, Sybase, Infbrmix, Microsoft SQL Server and others by allowing users to describe the data the user wishes to see. SQL also allows users to define the data in database, and manipulate the data. 31 FEATURES OF ORACLE The Oracle 8i database was downloaded from the Oracle website www.oracle.com. The database chosen was Oracle 8i enterprise edition. The primary reasons to chose this database was 1 Ease ofuse of Oracle database. 2 Oracle simplifies the development of applications. 3 Oracle simplifies the management oflntemet content. 4 Oracle simplifies the deployment of applications 5 Capacity to store large amount of data. 6 Increasing support of the Oracle database to the Java and XML 7 Ability of the Oracle database to connect to Java programs through Java Database Connectivity (JDDC). 8 Oracle provides the lowest cost platform for developing and deploying applications on the Internet. 32 Installation and Configuration of the Oracle database The installation of the Oracle database is done through standard installation wizard of the Oracle database. This wizard unzips the Oracle installation files and installs Oracle database through Oracle Universal Installer utility. The Oracle 8i product also comes with HTTP web server which is Apache web server and other utilities like replication support, Oracle inter-media and many more. But for the sake of Queen application, Oracle 8i is just used as a database as that was the purpose of using Oracle 8i. The control and application logic is being given to the middle tier which uses Java technology primcui.ly to control the functioning of the application. Installation Requirements Oracle8i Enterprise Edition or Oracle8i The Oracle8i Enterprise Edition or Oracle8i top-level component consists of the following installation types: • Typical • Minimal • Custom 33 The system requ.irements for Typical and Minimal are described below. The requirements for Custom depend upon the components selected for installation Requirement Operating System Windows NT 4.0 Service Pack Minimal Processor Recommended Processor RAM Hard Disk drive) Video Typical Windows NT 4.0 or higher 3.0 (with year 2000), 5.0 or above Pentium 166 or 200 Pentium 233 or 266 (256 recommended) 96 MB (256 recommended) 961 MB (plus an additional 22 MB on the system 16 color 34 LANGUAGE FOR MAPPING XML PROCESSOR (LMX) WHATISIMX? LMX stands for Language for mapping XML. Then LMX processor is capable of trausfonning one XML document into another and thus makes heavy use of the DOM API. LMX is an XML transformation language. It is a rule language that describes mapping between two sets of documents is logically similar but syntactically different XML documents. It is designed so that rules can be used bi-directional. That is, the same rule can be used for mapping documents with DTD a to documents with DID b and vice versa. LMX has many other application in addition converting messages. One is to convert an XJv1.L document to HTML document. Since HTML documents are universally viewable by browsers, converting a document to HTML effectively means rendering it. Thus an XML document can be browsed by browsers that have no native XML support. 35 LMX INN-QUEENS APPLICATION This processor converts XML information into HTML format. The information is contained in the XML format. When the user requests that information through View Doc or ListDoc servlets described earlier, this information needs to be converted into HTML form to be seen by the user in the user-friendly HTML manner. It converts the XML flies into HTML format and handles those files to ViewDoc and ListDoc servlets depending upon the type of request by the user. 36 RESULTS Following are the results achieved by developing theN-queens test-bed: 1 Developed a working a three-tier web application for the mathematical problem ofN-Queens using Java and XML technologies. 2 Generated a database to store the solutions and made the solutions available over the World Wide Web. 3 Generated an automatic mechanism to insert large queen solutions into the Oracle 8i database. 4 Created Java programs to fmd out the solutions to the mathematical problem for two algorithms namely Rohl and Wi.tth. 5 Successfully found and stored Queen solutions till 18 Queens and stored them in Oracle 8i database. Also solutions till Queen 14 were made available over the web. 6 Successfully accepted and stored the information into XML format. Also this information whenever needed is converted back into HTML format through a conversion processor. 7 Successfully installed and configmed Java Web Server to host theN-Queens application over the web. 37 FUTURE IMPROVEMENTS OF THEN-QUEENS TEST-BED In the future, we will try to improve this application with following features: Improving the user interface with Java Server Pages (JSP) In the future we will improve the user interface through JSP. This will make the user interface more interactive and increase the functionality of the user interface, rather that just being the front end ofthe application. Managing data more efficiently The number of the queen solutions for N> I 7 is enormously big. For example the number of solutions for N= 16 is . The current hardware capacity is not sufficient to store this much amount of data. Also adding hardware capacity also solves this problem partially. So we believe that we need to develop an effective data compression technique to store the data in the available hardware capacity and at the same time keeping the integrity of the data. Making this application available in the Wireless Mat;kup Language (WML)mode Currently we have the capacity to store the information in the XML format. With the help ofXML it is very easy to convert the information into Wireless markup Language (WML) mode. So in the future we are hying to provide the WML interface to this application so that this application can be accessed from the wireless devices. 38 APPENDIX List ofPrograms Title Test Serv1et Inputdoc Servlet Viewdoc Servlet Listdoc Servlet MakeCDF Servlet Usage The objective of this program is to take the number ofNQueens and type of algorithm from the user, to search for N-Queens solutions matching those parameters in Oracle database, and return the result in an HTML page. This program is a Java servlet that makes use of JDBC to connect to the backend Oracle database. InputDoc scrvlct accepts the .inf01mation, converts the information into World Wide Web Consortium (W3C) compatible XML format, and stores the XML docwnents in the directory of the machine hosting the enterprise development test-bed. This servlet allows the users to view the XML documents in the enterprise development test-bed. If any of the documents selected has a hyperlink to the original documents, the request goes to the ViewDoc servlet, which converts the XML document into more readable HTML format keeping the data intact. This servlet lists the available documents in the application. It shows the titles of the documents, along with the number which is assigned by InputDoc scrvlet to each incoming document, and time of creation of the document. CDF stands for Channel Definition Format. With the CDF format, it is possible to store the references to the XML documents in the remote server. In addition, CDF facilitates the updating of the documents from the remote server whenever new documents are created or old 39 documents are deleted on the remote server. DocManager Servlet This program provides management abilities for the rest of the programs. TEST SERVLET impmi j avax.servlet. *; import javax.servlet.http. *; import j ava.sq 1. *; import j ava.net. *; impo1i java.io. *; II Creating testservlet class by extending HttpServlet class. public class testservlet extends HttpServlet { Connection conn; private ServJetConfig config; public void init(ServletConfig config) throws ServletException { tbis.config=config; } public void service (HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException { II Setting the session as true HttpSession session= req.getSession(true); II Setting the content type as text/html res.setContcntType(''textlhtml"); PrintWriter out= res.getWriter(); I I Creating input stringss String input! = req.getParamcter(";inputl ";); String input2 = req.getParameter(";input2"); I I Printing the results out.printJn("; Queen Solutions "); Ol.lt.println("; "); 40 JNPUTDOC SERVLET II Importing required packages. import org.w3c.dom.Element; import com.ibm.xm l. parser. TXDocument; import java.io.IOException; import java.io.PrlntWriter; import java.io. Writer; import j ava.net.MaJ formedURLException; import java. net. URL; import javax.servlet.ServletException; import j avax. servlet.bttpHttpServlet; import javax.servlet.http.HttpServletRequest; import j avax.serv let. http .HttpServletResponse; import j avax. servlet.http .Http Utils; II Creating main class Doclnput whic extends HttpServlet class. public class Doclnput extends HttpServlet { } DocManager docman = DocManager.getlnstanceO; public void doGet(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException { res.setContentType(";text/plain; charset=''+docman.getEncodingO); PrintWriter writer = res.getWriter(); writer.print(this.docman.getString(";docman.input.get")); writer.close(); private void paramctcrError(HttpServletResponse res) throws IOException { res.setContentType(''textlhtml; charset=''+docman.getEncoding()); Print Writer writer = res.getWriterQ; writer. print( this. doc man. getString("; docman.input. error")); writer.close(); } 41 VIEWDOC SERVLET II Importing required packages. import javax.servlet.ServletConfig; import javax.servlet.ServletException; import javax.servlet. http. HttpServlet; import javax.scrvlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; import org.xml.sax.InputSource; II Creating main class Doclnput whic extends HttpServlet class. public class Doc View extends HttpServlet { Converter lmxconv; DocManager docman = DocManager.getinstance(); public void init(ServletConfig con:t) throws ServletException { II Get a filename ofLMX rule document with DocManager String lmxfilename = DocManager.getinstance().getString(";docrnan.rule"); if (lmx1ilename = null) throw new ServletException(";Can't start Doc View servlet bacause" +" docman.properties has no docman.rule entry.";); try{ I I Create a LMXConverter instance Non ValidatiugDOMParser damp= new Non ValidatingDOMParser domp.setExpandEntityReferences(true ); domp.parse(new InputSource(new FilelnputStream(lmxfilename))); this.lmxconv = new Converter(domp.getDocument()); } catch (Exception ioe){ throw new ServletException(";DocView: ";+ioe); } if(!this.lmxconv.isValid()){ tlrrow new ServletException(''DocView: LMX rule error.";); } 42 LISTDOC SBRVLET import com.ibm.xml.parser.Util; import java.io.IOBxception; import j ava.io.PJintWtiter; import java.util.StringTokenizer; import j avax.seivlet.ServletException; import javax.servlet. http.HttpServ let; import j avax.servlet. http.HttpServ letRequest; import javax.servlet.http.HttpServletResponse; //Creating main class DocList that extends HttpServlet class public class DocList extends HttpServlet { DocManager docman = DocManager.getlnstance(); private void parameterError(HttpServletResponse res) throws IOException { res.setContcntType(''text/html; charset=''-1 docman.getEncoding()); PrintWriter writer = res.getWriter(); writer.println(this.docman.getString(";docman.list.error")); writer.close(); } public void doGet(HttpServletRequest req, HttpServletResponse res)throws ServletException, IOException { II Check parameters String[] values= req.getParameterValues(";element"); if(values != nuJI && (values.length != 1 II values[O].length() = 0)) { this. parameterEnor(res ); return; } I I searchel is null or ";title" or ";body". String scarchel =values == null ? null : new String(values[O].getBytes(), docman.getEncoding() ); String searchstr = nuJI; values = req.getParameterValues(";string"); if(searchel != null) { // searchstr is valid when searchel isn't null. if (values == null II values.length != 1 II values[O].length() = 0){ this. parameterError(res); return; } 43 MAKECDFSERVLET II Importing required packages. import com.ibm.xrnl. parser. TXDocument; import com.ibm.xml. parser. TXElement; import java.io.IOException; import java.io.OutputStream Writer; import java.io.PrintWriter; import javax.servlet.ServletException; II Creating main class MakeCDF whic extends HttpServlet class. public class MakeCDF extends HttpServlet { static final String S_CHANNEL = ";CHANNEL"; static final String S_ITEM ="ITEM"; static final String S_TITLE ="TITLE"; static final String S_HREF = ";hrer'; DocManager docman = DocManager.getlnstance(); String servemame; public void doGet(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException { II Create the name of this server StringBuffer sb = new StringBuffer(); sb.append(req.getScheme()); sb.append(";:/1"); sb.append(req.getServerName()); if (req.getServerPort() > 0) sb.appcnd(";:";+req.getServeiPort()); this.servemame = sb.toString(); II ";http://foo.bar.com:8888" II Content-Type should be applicationlx -cdf. II We can not use charset= parameter because II its type is not text/*. res.setContentType("; application/x -cdf'); PrintWriter pw =new PrintWiiter (new OutputStream Writer(res.getOutputStream(), docman. getEncoding()) ); 44 DOC MANAGER SERVLET: import com.ibm.xml.parsers.Non ValidatingTXDOMParser; import com. ibm.xml.parser. TXDocument; import java.io.BufferedReader; import java.io.File; import java.io.FilelnputStream; import j ava.io.FileNotFoundException; import j ava.io .FileOutputS tream; import java.io.FileReader; II Creating main class DocManager public class DocManager { ResourceBundle resource = nuJl; String workdir =null; String seqfilename = null; TXDocument[] docs; int next; static DocManager thelnstauce = null; /** Return the instance.**/ public static DocManager getlnstance() { if(DocManager.thelnstance = null){ DocManager.thelnstance = new DocManager(); } return DocManager.theinstance; } I** Load property file. ";docman.properties" **I private DocManager(){ II Load docman* .properties try { this.rcsource = ResourceBundJe.getBundle(";docman"); } catch (MissingResourceException mre){ mre.ptintStackTrace();} II The file ";seq" contains the number of documents. this.seqfilename = this.getWorkDirectoryQ+"seq"; this.next = 0; BufferedReader br =null; try { br = new BufferedReader(new FileReader(this.seq.filename)); String line = br.readLine(); 45 REFERENCES [1] Deo, P., ";Enterprise Development Using JAVA and XML Technologies", Master's Thesis, UAB, 2001 [2] Aktunc, 0., Deo, P., Tanik.M.M., ";A Domain-Specific Collaboration Environment", SDPS Workshop Proceedings, p. 81-85, 2001. [3] Business-to-Business Integration for the New Network Economy, Active Software, October 2000. www.activesw.com [ 4] Information about Java servlet, JSP, EJB and J2EE, Sun Microsystems, 2001. www.Java.Sun.com (5] Information about XML, Microsoft, 2001. www.Microsoft.com [6] Introduction to multi-tier architectures, N-tier, 2001. www.n-tier.com [7] Two-tier and Three-tier architectures, SEI, 2001. www.SEI.cmu.edu [8] XML Suppottive Technologies, W3c, 2001. www.w3.org 46; http://uab.contentdm.oclc.org/cdm/ref/collection/uab_ece/id/151
-
18
-
19
Autoři: Fernandez, Ignatius
Zdroj: Beginning Oracle Database 12c Administration; 2015, p135-158, 24p
-
20
Nájsť tento článok vo Web of Science 
Full Text Finder