Index
Introduction
Differences
Installation I
Installation II
Installation III
Uninstall
Working with SMWP
Parameter
Fragement Class
Page Class
XML Document (Page)
|
3. Installation
3.1 System Requirements
- Java Development Kit (JDK) 1.3.1
- Java Servlet Development Kid (JSDK) 2.0
- Apache Tomcat Webserver 4.1
- Apache Cocoon 2.0
- Oracle 9i and corresponding JDBC-driver
3.1.1 Assumptions for the Installation Process
The installation process is described based upon following assumptions:
operating system |
Windows 2000 |
Web-Server |
Apache Tomcat 4.1 installed in c:\programme\tomcat |
Web-Server Document Root |
HTML Document Root in c:\programme\tomcat\htdocs |
Java Virtual Machine |
Java Version 1.3.1 installed in c:\programme\jdk1.3.1 |
SMWP installation directory |
SMWP files in
c:\smwp |
Document root for Apache Cocoon |
Document Root for Cocoon in
c:\programme\tomcat\cocoon |
Document root for Apache Tomcat Web-applications |
Document Root in
c:\programme\tomcat\webapps |
Table 1: Assumptions for the installation process
3.2 System Overview
The SMWP-Prototype is separated into following sub-systems:
- Database: stores all relations, trigger, java stored procedures required
for SMWP
- Java Stored Procedures: generates pages (XML documents) from fragment
class relations using metadata relations; keeps the pages up to date
- Console: User interface for managing parameters, fragment classes
and page classes
- Servlets: loads pre-generated XML documents from database and provides
them with proper XSL Style sheets
- XML Transformer: transforms XML documents via dynamically generated
XSL style sheets into HTML documents

Figure 1: SMWP - System architecture
Metadata contains information about fragmentation parameters, reference
relations, fragmentation relations, fragment classes, page classes and
pages (XML documents). It contains the link between the logical view (fragment
classes, page class
) and its physical representation (fragment
class relations, fragmentation relations, XML documents
)
DML (Data Modelling Language) is used to create, modify and delete reference
relations, fragmentations relations, fragment class relations and all
required triggers for SMWP.
The SMWP Console is used to create the database and web schema, i.e. fragment
classes and page classes which result in pre-generated XML documents (pages).
It automatically creates relations and triggers needed for fragmentation
and stores the corresponding metadata in supplied relations. The pre-generated
XML documents are kept synchronous with its corresponding database contents
by Java Stored Procedures which are invoked by triggers. These triggers
are mapped to the created fragment class relations.
The web server Apache Tomcat is used to visualize the pre-generated XML
documents. Servlets load the pre-generated XML documents from database
and provide them with proper XSL Style sheets for HTML representation.
Apache Cocoon which runs inside Apache Tomcat processes XML and XSL documents
into HTML documents which can be displayed within common Internet Browsers
like Internet Explorer or Netscape.
|