1.1.1.1
REGNET-IST-2000-26336
Portal Prototytpes
Project acronym
REGNET
Work package
WP 2 Implementation of the System and reparation of Services and Product
Generation
Sub - Task
T 2.2.1 Portal Development
Date of delivery
2001-10-26
Code name
RN_T221v02_MOT_prototypes
Objective
Validate the Portal Architecture
Distribution Type
Restricted
Authors (Partner)
MOT
Contact Person
Roberto Cicci ([email protected])
Keywords List
Version
Date
Log
01
2001-10-18
First Version
02
2001-10-26
Basics on Portal-S&R interface
Contract nr.
Version 01
IST-2000-26336
draft  final 
System Implementation
Portal Prototypes
TABLE OF CONTENTS
1
2
3
Introduction _________________________________________________________________ 3
1.1
Purpose __________________________________________________________________ 3
1.2
Overview _________________________________________________________________ 3
Prototypes Description and Specifications ________________________________________ 4
2.1
WAP Portal _______________________________________________________________
2.1.1
Requirements__________________________________________________________
2.1.2
Design Description ______________________________________________________
2.1.3
Assumptions __________________________________________________________
2.1.4
Test & Debug Requirements ______________________________________________
2.1.5
Configuration Information ________________________________________________
2.1.6
Tools Specifications _____________________________________________________
4
4
4
5
5
5
6
2.2
S&R Subsystem ___________________________________________________________
2.2.1
Design Description ______________________________________________________
2.2.2
Assumptions __________________________________________________________
2.2.3
Test & Debug Requirements ______________________________________________
2.2.4
Configuration Information ________________________________________________
2.2.5
Tools Specifications _____________________________________________________
6
6
6
6
6
6
Prototypes Interfaces__________________________________________________________ 7
3.1
81915555
WAP Portal – S&R Subsystem ________________________________________________ 7
REGNET IST-2000-26336
Page 2 of 8
System Implementation
Portal Prototypes
1 Introduction
1.1
Purpose
Among the objectives of the first increment of WP2 process, there is the validation of
architectures defined in System Specifications during WP1. Some of the parters were asked to
develop a simple prototype that demonstrate the feasibility of critical points stated in deliverable D2.
This document describes the scope, functionalities, and interfaces of above mentioned
prototypes in the context of Portal node, with the following goals:
1.2

foster the documentation of prototypes’ code, in order to make it as reusable as possible for
the next development increments.

promote the integration of prototypes, in order to validate the communication mechanisms
proposed in D2
Overview
The first increment of WP2 development proposes some prototyping in order to validate various
technology choices defined in D2. In detail, the following prototypes will be developed:

WAP Portal

S&R subsystem

Communication Infrastructure (Portal + J2EE/SOAP + PHP/SOAP)
Communication infrastructure could be validated in both these ways:

via stand-alone prototypes, each one interfacing with stub components in place of real
communicating components

interfacing the planned prototypes for small simple functionalities
81915555
REGNET IST-2000-26336
Page 3 of 8
System Implementation
Portal Prototypes
2 Prototypes Description and Specifications
2.1
WAP Portal
2.1.1 Requirements
The main objective of the Wap Portal Prototype is to validate the overall architecture and the
interactions among subsystems. In particular the prototype will be focused on the integration between
the portal and the Search and Retrieval subsystem.
2.1.1.1
Functional Requirements
The Wap Portal Prototype will satisfy only a subset of the functional requirements specified in the
Interim Report 1.4.1.
The specific requirements that it will meet are the following:

Provides an access point to the Search & Retrieval subsystem (FR-PT-01-02)

Support simple searches (FR-PT-04-02)

Displays results returned by the Search & Retrieval subsystem (FR-PT-02-01)
2.1.1.2
Technical Requirements
The requirements that we will meet are the following:

Multi-tier architecture;

Distributed architecture;

Portability;

Support WAP-based browsers connected via a wireless access;

GSM and GPRS support;
Interactions between the Portal and the Search and Retrieval subsystem will be perfomed through the
RMI protocol.
2.1.2 Design Description
At a high level the design of the Wap Portal prototype can be shown by the following picture:
81915555
REGNET IST-2000-26336
Page 4 of 8
System Implementation
Portal Prototypes
The phone will perform the requests to the Web server through the WAP protocol.
2.1.3 Assumptions
To support the maximun number of Wap phones the prototype will be compatible to the following
set of constraints:
Max card size:
1492 bytes
Max image size:
1492 bytes
Rows in display:
4
Cols in display:
14
Horizontal pixels in display:
95
Vertical pixels in display:
45
Text style:
Small, Bold
Calling numbers within WML:
yes
HTTP Redirect:
yes
The supported Wap Browser will be compliant with the Wireless Application Protocol Wireless
Markup language Specification Version 1.2.
2.1.4 Test & Debug Requirements
Testing and debugging will be performd on an emulated environment and on the real handset
2.1.5 Configuration Information
All project files will be under configuration management using Cvs
81915555
REGNET IST-2000-26336
Page 5 of 8
System Implementation
Portal Prototypes
2.1.6 Tools Specifications
2.2

JDK 1.3

MADK (Motorola Application Development Kit) with Motorola wireless IDE

Openwave SDK WAP Edition 5.0

Jakarta Jetspeed

Jakarta Tomcat

Jakarta Ant
S&R Subsystem
2.2.1 Design Description
2.2.2 Assumptions
2.2.3 Test & Debug Requirements
2.2.4 Configuration Information
2.2.5 Tools Specifications
81915555
REGNET IST-2000-26336
Page 6 of 8
System Implementation
Portal Prototypes
3 Prototypes Interfaces
3.1
WAP Portal – S&R Subsystem
As stated above, the S&R component is accessible via RMI to the Portal (as well as to some other
components implemented in Java). According to system specifications, the information exchanged is
XML data with the schema shown in the following table:
TBD compliance with D2
TBD agreement with Martin
<?xml version="1.0"?>
<xsd:schema targetNamespace="http://www.regnet.org"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.regnet.org"
elementFormDefault="qualified">
<xsd:include schemaLocation="xer.xsd"/>
<xsd:element name="SearchRequest">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="General"/>
<xsd:element ref="QueryDef"/>
<xsd:element ref="Response" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="General">
<xsd:complexType>
<xsd:all>
<xsd:element name="UserId" type="xsd:string" minOccurs="0"/>
<xsd:element name="Source" type="xsd:string" minOccurs="0"/>
<xsd:element name="SessionId" type="xsd:string" minOccurs="0"/>
<xsd:element name="ResultSetId" type="xsd:string" minOccurs="0"/>
<xsd:element name="InterfaceLanguage" type="xsd:language" default="en"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
<xsd:element name="QueryDef">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Targets"/>
<xsd:element ref="Query"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Targets">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="databaseNames"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Response">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="sortSequence">
<xsd:complexType>
<xsd:sequence minOccurs="0" maxOccurs="unbounded">
<xsd:element name="SortKeySpec" type="SortKeySpec"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="NoOfResultsRequested"
type="NoOfResponseRecords" default="10"/>
<xsd:element name="PreferredResponsStruct">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ResponseFormat" type="ResponseFormat"/>
<xsd:element name="ResponseType" type="ResponseFormat"/>
</xsd:sequence>
81915555
REGNET IST-2000-26336
Page 7 of 8
System Implementation
Portal Prototypes
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:simpleType name="NoOfResponseRecords">
<xsd:restriction base="xsd:nonNegativeInteger">
<xsd:minInclusive value="1"/>
<xsd:maxInclusive value="50"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="ResponseFormat">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="cross-domain"/>
<xsd:enumeration value="native”/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name=”ResponseType”>
<xsd:restriction base=”xsd:string”>
<xsd:enumeration value=”short”/>
<xsd:enumeration value=”medium”/>
<xsd:enumeration value=”complete”/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
Table 1 – S&R XML-Schema
The Wap Portal and the Search & Retrieval prototypes will run on the same server machine or on two
different machines on the same Intranet (i.e. the prototypes don’t deal with firewall issues).
3.1.1 Interfaces
81915555
REGNET IST-2000-26336
Page 8 of 8