Working with SMWP - Overview
 

Index

Introduction
Differences
Installation I
Installation II
Installation III
Uninstall

Working with SMWP

Parameter
Fragement Class
Page Class
XML Document (Page)



4 Working with SMWP

4.1 Starting the SMWP-Console

Start the SMWP console by executing following command on the command shell:

javaw -classpath "c:/smwp/console/lib/apache/xalan2.2.D6.jar;
c:/smpw/console/lib/oracle9i/classes12.jar;
c:/smwp/console/lib/oracle9i/xmlparserv2.jar;
c:/smwp/console/bin" dke.smwp.tools.Console

4.2 Using the SMWP-Console

The console user interface is separated into three parts (Figure 2):

  • menu bar
  • input window
  • output window

Figure 2: SMWP Console


Menu bar

The menu bar contains following structure:

  • File
    • Exit
      Exits the console
  • Edit
    • Submit
      Process the command entered into the input window

      Figure 3: SMWP Console - Menu Edit
    • Show Command History
      Shows a list of all executed SMWP commands. By clicking a list item followed by clicking "OK" it will be inserted into the input window.

      Figure 4: SMWP Console - Command History
  • Database
    • Regenerate all Pages
      Recreates all XML documents from scratch for all existing page classes
    • Drop all Pages
      Deletes all created XML documents

input window
SMWP-commands using a schema definition language are entered here. To execute the entered command click the >Edit>Submit on the menu bar. The schema definition language is described in the following chapters.

output window
Every executed SMWP command produces a feedback which is displayed on this window.

4.3 Overview of Elements managed by the SMWP Console

4.3.1 Parameter

The creation of fragment classes require the creation of fragment class parameters first. An fragment class parameter can be either from type value parameter or predicate parameter. The value parameter requires one tuple for each valid value while the predicate parameter uses statements, i.e. rank > 15 AND rank <=50. An predicate parameter can be used as substitute for an value parameter by using valid values directly in statements, i.e. name = "Styria".

Possible actions:

  • create value parameter
  • create predicate parameter
  • delete value parameter
  • delete predicate parameter

4.3.2 Fragment Class

The fragment class defines the parameters which are used for fragmentation of application realations. The fragment class wineries<region> states that the applicatoin relation wineries is fragmented by the parameter region. Tuples from an application relation can exist in one, more or no fragments at all.

Possible actions:

  • create primary fragment class
  • delete primary fragment class
  • alter primary fragment class
    • add and delete publication information
  • create derived fragment class
  • delete derived fragment class
  • alter derivey fragment class
    • add and delete publication information

4.3.3 Fragment

Fragment classes define everything which is required to generate fragments. An resulting fragment wineries<styria> contains all valid tuples of application relation wineries whose column region contains the value styria.

Possible actions:

  • None
    • fragments are logic constructs which are generated internally on demand

4.3.4 Page Class

Fragment classes are used to structure the data itself by defining which tuple is contained in which fragment. Page classes are used to display the data which is structured by fragment classes. A page class contains at least the fragment class it is defined upon (which is being called foundation fragment class) and more fragment classes which are at least parameterized by the same parameters as the foundation fragment class.

Possible actions:

  • create page class
  • delete page class
  • alter page class
    • add fragment class (and page references)
    • remove fragment class (and its page references)

4.3.5 Page

A page class is a single instance of an page class. The page class pc_wineries<region> which uses the fragment class wineries<region> as foundation fragment class

Possible actions:

  • None
    • Pages are represented as XML Documents which are generated via the creation of page classes.