You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by di...@apache.org on 2003/09/14 19:14:49 UTC
cvs commit: ws-site/targets/wsrp4j/images consumer_architecture.jpg overview1.jpg portal_overview.gif producer_architecture.jpg wsrp4j_components.gif
dims 2003/09/14 10:14:49
Added: targets/wsrp4j Thumbs.db WSRP4JDocs.doc arch-consumer.html
arch-producer.html arch.html index.html
install.html na.html
targets/wsrp4j/images consumer_architecture.jpg
overview1.jpg portal_overview.gif
producer_architecture.jpg wsrp4j_components.gif
Log:
commit wsrp4j site.
Revision Changes Path
1.1 ws-site/targets/wsrp4j/Thumbs.db
<<Binary file>>
1.1 ws-site/targets/wsrp4j/WSRP4JDocs.doc
<<Binary file>>
1.1 ws-site/targets/wsrp4j/arch-consumer.html
Index: arch-consumer.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="author" value="Stephan Laertz" content="Stephan Laertz">
<meta name="email" value="stephan.laertz@de.ibm.com">
<meta content="MSHTML 6.00.2600.0" name="GENERATOR">
<title>WSRP4J Installation</title>
</head>
<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"
link="#525d76">
<!-- TOP IMAGE -->
<table cellspacing="0" width="100%" border="0">
<tbody>
<tr>
<td colspan="2"><a href="http://www.apache.org/"><img
src="http://www.apache.org/images/asf_logo_wide.gif"
alt="The Apache Software Foundation" align="left" border="0"></a></td>
</tr>
</tbody>
</table>
<table cellspacing="4" width="100%" border="0">
<tbody>
<tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<!-- START:LEFT SIDE NAVIGATION --> <td valign="top" nowrap="nowrap"
width="20%">
<p> <strong>Project</strong> </p>
<ul>
<li> <a href="index.html">Welcome</a></li>
<li><a href="arch.html">Architecture</a></li>
<ul>
<li><a href="arch-producer.html">Producer</a></li>
<li><a href="arch-consumer.html">Consumer</a><br>
</li>
</ul>
<li><a href="na.html">News</a><br>
</li>
<li> <a href="na.html">Status</a></li>
<li><a href="na.html">Bugs</a><br>
</li>
</ul>
<p> <strong>Getting Started</strong> </p>
<ul>
<li> <a href="na.html">Installation</a> </li>
<li> <a href="na.html">Configuration</a> </li>
<li> <a href="na.html">FAQ</a> </li>
</ul>
<p> <strong>Links<br>
</strong> </p>
<ul>
<li> <a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">OASIS
WSRP</a></li>
<li><a
href="http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal">Pluto
Proposal</a><br>
</li>
<li><a href="http://jakarta.apache.org/tomcat/">Tomcat</a><br>
</li>
</ul>
</td>
<!-- END:LEFT SIDE NAVIGATION --><!-- START:RIGHT SIDE CONTENT --> <td
valign="top" align="left" width="80%">
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td bgcolor="#525d76"><font face="arial,helvetica,sanserif"
color="#ffffff"><a name="Welcome to The Charon Project"><strong>Consumer
Components</strong></a> </font></td>
</tr>
<tr>
<td> <blockquote>
Producer and consumer are provided with a very modular architecture enabling an easy exchange of module implementations.
All modules excel by interfaces based on the WSRP object model hiding the portal�s object model and thus gaining independence of changes in the portal implementation or design.
<br>
<br>
<IMG border="0" src="images/consumer_architecture.jpg" width="982"
height="540"><br>
<br>
<br>
<b>Protocol Handler </b><br>
The Protocol Handler is a standalone Swing based application that implements the consuming portal and the browser functionality. It aggregates the integrated WSRP portlets and forwards all invocations together with relevant context and request information to the remote WSRP service. The Swing consumer thereby uses the ConsumerEnvironment to collect all data required for a WSRP call.
<br>
<br>
<b>WSRP Object Model </b><br>
Most of the WSRP object model is being generated from the WSRP specification�s WSDL types.
<br>
<br>
<b>PortletDriver </b><br>
The PortletDriver is the task oriented abstraction of the generated WSRP stubs for markup and action invocation.
<br>
<br>
<b>WSRP service (stubs) </b><br>
The stubs generated by the axis SOAP implementation.
The stubs are also implementing the cookie handling - for more details see SessionHandler below.
<br>
<br>
<b>ProducerRegistry </b><br>
The ProducerRegistry stores and manages details about producer portals from which portlets were integrated or shall be integrated.
<br>
<br>
<b>SessionHandler </b><br>
The WSRP consumer implementation session handling is based on the SOAP stack�s session handling. The generated SOAP stubs are doing the cookie handling and are caching the cookies in instance variables. This means that one stub object instance is equivalent to one HTTP session which we map to one WSRP session (initCookie wise).
When a WSRP session did time out an InvalidCookie exception is being thrown and a new session must be established.
<br>
<br>
<b>URLHandler </b><br>
The URLHandler is responsible for the URL rewriting of the WSRP URLs embedded in the markup received from the remote portlet.
<br>
<br>
<b>PortletRegistry </b><br>
The PortletRegistry stores and provides access to WSRP specific data and descriptions of a remote Portlet.
<br>
<br>
<b>UserRegistry </b><br>
The UserRegistry is in the Swing consumer case very simplistic. As the browser is integrated there is always only one "dummy" user being managed.
</blockquote> </td>
</tr>
</tbody>
</table>
<!-- START:RIGHT SIDE CONTENT -->
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
</tr>
<tr>
<td><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<!-- FOOTER --> <tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<td colspan="2">
<div align="center"> <font color="#525d76" size="-1"><em>Copyright
?? 2003, Apache Software Foundation </em></font> </div>
</td>
</tr>
</tbody>
</table>
<!-- end the processing -->
</body>
</html>
1.1 ws-site/targets/wsrp4j/arch-producer.html
Index: arch-producer.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="author" value="Stephan Laertz" content="Stephan Laertz">
<meta name="email" value="stephan.laertz@de.ibm.com">
<meta content="MSHTML 6.00.2600.0" name="GENERATOR">
<title>WSRP4J Installation</title>
</head>
<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"
link="#525d76">
<!-- TOP IMAGE -->
<table cellspacing="0" width="100%" border="0">
<tbody>
<tr>
<td colspan="2"><a href="http://www.apache.org/"><img
src="http://www.apache.org/images/asf_logo_wide.gif"
alt="The Apache Software Foundation" align="left" border="0"></a></td>
</tr>
</tbody>
</table>
<table cellspacing="4" width="100%" border="0">
<tbody>
<tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<!-- START:LEFT SIDE NAVIGATION --> <td valign="top" nowrap="nowrap"
width="20%">
<p> <strong>Project</strong> </p>
<ul>
<li> <a href="index.html">Welcome</a></li>
<li><a href="arch.html">Architecture</a></li>
<ul>
<li><a href="arch-producer.html">Producer</a></li>
<li><a href="arch-consumer.html">Consumer</a><br>
</li>
</ul>
<li><a href="na.html">News</a><br>
</li>
<li> <a href="na.html">Status</a></li>
<li><a href="na.html">Bugs</a><br>
</li>
</ul>
<p> <strong>Getting Started</strong> </p>
<ul>
<li> <a href="na.html">Installation</a> </li>
<li> <a href="na.html">Configuration</a> </li>
<li> <a href="na.html">FAQ</a> </li>
</ul>
<p> <strong>Links<br>
</strong> </p>
<ul>
<li> <a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">OASIS
WSRP</a></li>
<li><a
href="http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal">Pluto
Proposal</a><br>
</li>
<li><a href="http://jakarta.apache.org/tomcat/">Tomcat</a><br>
</li>
</ul>
</td>
<!-- END:LEFT SIDE NAVIGATION --><!-- START:RIGHT SIDE CONTENT --> <td
valign="top" align="left" width="80%">
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td bgcolor="#525d76"><font face="arial,helvetica,sanserif"
color="#ffffff"><a name="Welcome to The Charon Project"><strong>Producer
Components</strong></a> </font></td>
</tr>
<tr>
<td> <blockquote>
<br>
Producer and consumer are provided with a very modular architecture enabling an easy exchange of module implementations.
All modules excel by interfaces based on the WSRP object model hiding the runtime environment�s (portal�s) object model and thus gaining independence of changes in the environment�s implementation or design.
<br>
<br>
<IMG border="0" src="images/producer_architecture.jpg" width="990"
height="441"><br>
<br>
<b>WSRPEngine</b><br>
The WSRPEngine is the WSRP implementation endpoint. This class must be deployed in the app server (Tomcat) as a web service.
The WSRPEngine implements the WSRP protocol specific ports (=interfaces) and does the corresponding protocol handling. There are four WSRP ports:<br>
<br>
Markup � deals with Portlet invocation and Session handling<br>
PortletManagement � covers lifecycle, descriptions and properties of portlets<br>
Registration � enables a consumer to register at the producer<br>
ServiceDescription � via this port a producer can describe itself and the services it provides.<br>
To be able to reuse Portal functionality regarding session and request handling when invoking a portlet the WSRPEngine must be able to access the HttpServletRequest.
<br><br>
<b>ConsumerRegistry</b><br>
This component manages and provides access to the registered Consumers.
<br><br>
<b>HandleGenerator </b><br>
This component is responsible for generating IDs / handles required for the WSRP protocol handling.
<br><br>
<b>WSRP Object Model</b> <br>
The WSRP object model is being generated from the WSRP specification�s WSDL types.
<br><br>
<b>Provider</b><br>
The Provider is the access point for the WSRPEngine to the Provider components which hide the provider (portal) implementation�s components required to handle and invoke portlets. All Subcomponents wrap corresponding provider components and map the WSRP object model to the provider object model.
<br><br>
<b>Portlet Invoker</b><br>
The PortletInvoker wraps the Provider�s invocation mechanisms and provides the Provider with the required environment.
<br><br>
<b>Description Handler </b><br>
The DescriptionHandler manages and provides the description of the provider regarding configuration properties like registration or session handling policy, etc.
It moreover provides the descriptions of the provided portlets depending on the registration.
<br><br>
<b>PortletPool </b><br>
The PortletPool manages the portlet instances and is responsible for the portlets' lifecycle management (clone, destroy).
<br><br>
<b>Portlet State Manager </b><br>
The PortletStateMananger enables a Producer to access a portlet�s state as a blob that than can be delegate to the consumer to be stored on consumer side.
<br><br>
<b>Session Handler</b> <br>
No additional session handling implementation for the Pluto provider is required as the session handling concept is completely HTTP (cookie) based and relies on consumer�s cookie handling.
<br><br>
<b>URL Composer</b> <br>
The URLComposer must be used for WSRP triggered portlet invocation to create WSRP URLs instead of the portal�s URL handling implementation. Therefore the URLComposer is being used by WSRP�s version of the DynamicInformationProvider which is being used by the Portlet API implementation to generate portlet URLs. There are two ways how URLs can be composed in a WSRP environment: <br>
Via templates that represent URLs that are valid on Consumer side and contain placeholders for all portlet specific URL components. <br>
Via URL rewriting. In that case WSRP specific URLs are being composed that will have to be rewritten by the Consumer.
</blockquote> </td>
</tr>
</tbody>
</table>
<!-- START:RIGHT SIDE CONTENT -->
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
</tr>
<tr>
<td><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<!-- FOOTER --> <tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<td colspan="2">
<div align="center"> <font color="#525d76" size="-1"><em>Copyright
?? 2003, Apache Software Foundation </em></font> </div>
</td>
</tr>
</tbody>
</table>
<!-- end the processing -->
</body>
</html>
1.1 ws-site/targets/wsrp4j/arch.html
Index: arch.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="author" value="Stephan Laertz" content="Stephan Laertz">
<meta name="email" value="stephan.laertz@de.ibm.com">
<meta content="MSHTML 6.00.2600.0" name="GENERATOR">
<title>WSRP4J Installation</title>
</head>
<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"
link="#525d76">
<!-- TOP IMAGE -->
<table cellspacing="0" width="100%" border="0">
<tbody>
<tr>
<td colspan="2"><a href="http://www.apache.org/"><img
src="http://www.apache.org/images/asf_logo_wide.gif"
alt="The Apache Software Foundation" align="left" border="0"></a></td>
</tr>
</tbody>
</table>
<table cellspacing="4" width="100%" border="0">
<tbody>
<tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<!-- START:LEFT SIDE NAVIGATION --> <td valign="top" nowrap="nowrap"
width="20%">
<p> <strong>Project</strong> </p>
<ul>
<li> <a href="index.html">Welcome</a></li>
<li><a href="arch.html">Architecture</a></li>
<ul>
<li><a href="arch-producer.html">Producer</a></li>
<li><a href="arch-consumer.html">Consumer</a><br>
</li>
</ul>
<li><a href="na.html">News</a><br>
</li>
<li> <a href="na.html">Status</a></li>
<li><a href="na.html">Bugs</a><br>
</li>
</ul>
<p> <strong>Getting Started</strong> </p>
<ul>
<li> <a href="na.html">Installation</a> </li>
<li> <a href="na.html">Configuration</a> </li>
<li> <a href="na.html">FAQ</a> </li>
</ul>
<p> <strong>Links<br>
</strong> </p>
<ul>
<li> <a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">OASIS
WSRP</a></li>
<li><a
href="http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal">Pluto
Proposal</a><br>
</li>
<li><a href="http://jakarta.apache.org/tomcat/">Tomcat</a><br>
</li>
</ul>
</td>
<!-- END:LEFT SIDE NAVIGATION --><!-- START:RIGHT SIDE CONTENT --> <td
valign="top" align="left" width="80%">
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td bgcolor="#525d76"><font face="arial,helvetica,sanserif"
color="#ffffff"><a name="Welcome to The Charon Project"><strong>Introduction</strong></a> </font></td>
</tr>
<tr>
<td> <blockquote>
<p>The <a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">OASIS
WSRP</a> standard defines pluggable, user-facing, interactive web services with a common, well-defined interface and protocol for processing user interactions and providing presentation fragments suitably for aggregation by portals. WSRP standardizes web services at the presentation layer on top of the existing web services stack, builds on the existing web services standards and will leverage additional web services standards efforts, such as security efforts now underway, as they become available. The WSRP interfaces are defined in the Web Services Description Language (WSDL). In addition, WSRP defines metadata for self-description for publishing and finding WSRP services in registries. All WSRP services are required to implement a SOAP binding and optionally may support additional bindings.
</p>
<p>In the definition of the WSRP standard and the <a
href="http://www.jcp.org/en/jsr/detail?id=168">JSR 168</a>, the OASIS Technical Committee and the JSR 168 Expert group have closely collaborated to make sure that that both fit together well in portal architectures. JSR 168 compliant portlets can be exposed as WSRP compliant web services and conversely, WSRP services can be integrated through generic portlet proxies written to the Portlet API (see Figure below).
</p><IMG border="0"
src="images/portal_overview.gif" width="436" height="280">
<p>The WSRP4J project provides the WSRP4J Producer, which allows implementing such WSRP compliant services based on a free, open source software stack consisting of Tomcat, Axis and WSRP4J which in turn includes Pluto, the JSR 168 reference implementation. In addition, the WSRP4J project provides a generic proxy portlet written to the Portlet API, the WSRP4J Consumer (see Figure below).
</p>
<IMG border="0" src="images/wsrp4j_components.gif"
width="436" height="280">
</blockquote></td>
</tr>
</tbody>
</table>
<!-- START:RIGHT SIDE CONTENT -->
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
</tr>
<tr>
<td><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<!-- FOOTER --> <tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<td colspan="2">
<div align="center"> <font color="#525d76" size="-1"><em>Copyright
?? 2003, Apache Software Foundation </em></font> </div>
</td>
</tr>
</tbody>
</table>
<!-- end the processing -->
</body>
</html>
1.1 ws-site/targets/wsrp4j/index.html
Index: index.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="author" value="Stephan Laertz" content="Stephan Laertz">
<meta name="email" value="stephan.laertz@de.ibm.com">
<meta content="MSHTML 6.00.2600.0" name="GENERATOR">
<title>WSRP4J Welcome</title>
</head>
<body text="#000000" link="#525d76" bgcolor="#ffffff">
<!-- TOP IMAGE -->
<table cellspacing="0" width="100%" border="0">
<tbody>
<tr>
<td colspan="2"><a href="http://www.apache.org/"><img
src="http://www.apache.org/images/asf_logo_wide.gif"
alt="The Apache Software Foundation" align="left" border="0"></a></td>
</tr>
</tbody>
</table>
<table cellspacing="4" width="100%" border="0">
<tbody>
<tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<!-- START:LEFT SIDE NAVIGATION --> <td valign="top" nowrap="nowrap"
width="20%">
<p> <strong>Project</strong> </p>
<ul>
<li> <a href="index.html">Welcome</a></li>
<li><a href="arch.html">Architecture</a></li>
<li><a href="na.html">News</a></li>
<li> <a href="na.html">Status</a> </li>
</ul>
<p> <strong>Getting Started</strong> </p>
<ul>
<li> <a href="na.html">Installation</a> </li>
<li> <a href="na.html">Configuration</a> </li>
<li> <a href="na.html">FAQ</a> </li>
</ul>
<p> <strong>Links<br>
</strong> </p>
<ul>
<li> <a
href="http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal">Pluto</a></li>
<li><a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">OASIS
WSRP</a></li>
</ul>
</td>
<!-- END:LEFT SIDE NAVIGATION --><!-- START:RIGHT SIDE CONTENT --> <td
valign="top" align="left" width="80%">
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td bgcolor="#525d76"><font face="arial,helvetica,sanserif"
color="#ffffff"><a name="Welcome to The Charon Project"><strong>Welcome</strong></a> </font></td>
</tr>
<tr>
<td>
<blockquote><P> Integration
of content and application into portals has been a task requiring
significant custom programming effort. Portal vendors or
organizations running portals had to write special adapter
portlets to allow portals to communicate with the different
applications and content providers to accommodate a variety of
interfaces and protocols. The <B
style="mso-bidi-font-weight: normal"><I
style="mso-bidi-font-style: normal">OASIS Web Services for Remote
Portals (WSRP)</I></B> standard simplifies integration of remote
applications/content into portals so that portal administrators
can pick from a rich choice of services and integrate it in their
portal <I style="mso-bidi-font-style: normal">without programming
effort</I>. As a result, WSRP becomes the means for content and
application providers to provide their services to organizations
running portals in a very easily consumable form.</P>
<P >
The
<B style="mso-bidi-font-weight: normal"><I
style="mso-bidi-font-style: normal">Apache WSRP4J</I></B> open
source project was initiated by IBM to facilitate quick adoption
of the WSRP standard by content and application providers and
portal vendors. They can use WSRP4J as a platform for developing
and hosting WSRP compliant web services. The OASIS WSRP standard
will enable thousands of portals to aggregate content from tens of
thousands of content and application providers offering hundreds
of thousands of user-facing, pluggable web services for millions
of end users/devices. </P>
<P >
We
hope the WSRP4J project will kick start broad adoption of the WSRP
standard and result in a large number of cool WSRP services
running on free, open source Apache software. </p>
</blockquote>
</td>
</tr>
<tr>
<td><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<!-- FOOTER --> <tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<td colspan="2">
<div align="center"> <font color="#525d76" size="-1"><em>Copyright
?? 1999-2003, Apache Software Foundation </em></font> </div>
</td>
</tr>
</tbody>
</table>
<!-- end the processing -->
</body>
</html>
1.1 ws-site/targets/wsrp4j/install.html
Index: install.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="author" value="Stephan Laertz" content="Stephan Laertz">
<meta name="email" value="stephan.laertz@de.ibm.com">
<meta content="MSHTML 6.00.2600.0" name="GENERATOR">
<title>WSRP4J Installation</title>
</head>
<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"
link="#525d76">
<!-- TOP IMAGE -->
<table cellspacing="0" width="100%" border="0">
<tbody>
<tr>
<td colspan="2"><a href="http://www.apache.org/"><img
src="http://www.apache.org/images/asf_logo_wide.gif"
alt="The Apache Software Foundation" align="left" border="0"></a></td>
</tr>
</tbody>
</table>
<table cellspacing="4" width="100%" border="0">
<tbody>
<tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<!-- START:LEFT SIDE NAVIGATION --> <td valign="top" nowrap="nowrap"
width="20%">
<p> <strong>Project</strong> </p>
<ul>
<li> <a href="../index.html">Welcome</a></li>
<li><a href="../arch.html">Architecture</a></li>
<li><a href="../news.html">News</a><br>
</li>
<li> <a href="../status.html">Status</a></li>
<li><a href="../bugs.html">Bugs</a><br>
</li>
</ul>
<p> <strong>Getting Started</strong> </p>
<ul>
<li> <a href="./install.html">Installation</a> </li>
<li> <a href="../config.html">Configuration</a> </li>
<li> <a href="../faq.html">FAQ</a> </li>
</ul>
<p> <strong>Links<br>
</strong> </p>
<ul>
<li> <a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">OASIS
WSRP</a></li>
<li><a
href="http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal">Pluto
Proposal</a><br>
</li>
<li><a href="http://jakarta.apache.org/tomcat/">Tomcat</a><br>
</li>
</ul>
</td>
<!-- END:LEFT SIDE NAVIGATION --><!-- START:RIGHT SIDE CONTENT --> <td
valign="top" align="left" width="80%">
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td bgcolor="#525d76"><font face="arial,helvetica,sanserif"
color="#ffffff"><a name="Welcome to The Charon Project"><strong>Installation</strong></a> </font></td>
</tr>
<tr>
<td>
<blockquote>
<p><br>
The WSRP4J Project provides 2 different provider components as well as
2 WSRP consumers. Each of these components can be installed separately
and has different prerequisites. The easiest way to install any of these
componetns is to execute the according batch file from the build
directory. Alternatively you can start the <span
style="font-style: italic;">build</span> batch file with the
appropriate argument. To get more information about available build
targets start <span style="font-style: italic;">build</span> with no
arguments.<br>
</p>
<span style="font-weight: bold;">install-swing-consumer</span><span
style="font-weight: bold;"></span><span style="font-weight: bold;"><br>
</span>By starting the <span style="font-style: italic;">install-swing-consumer</span>
batch file with no arguments the WSRP4J core project is rebuilt and on
success the WSRP4J Swing Consumer will be installed in the driver
directory of the WSRP4J distribution.<br>
<span style="font-weight: bold; font-style: italic;">Prereq's:
None</span><br>
<br>
<span style="font-weight: bold;">install-proxy-portlet<br>
</span>To install to proxy portlet consumer you need to
have a Pluto installation. After starting the <span
style="font-style: italic;">install-proxy-portlet</span> batch file
with no arguments you will be prompted for the directory of the Tomcat
installation which runs Pluto. The installation process tries to insert
an entry for the proxy portlet in the <span style="font-style: italic;">portletregistry.xml</span>
file of the <span style="font-style: italic;">/pluto</span> web
application. Please see the <a href="../config.html">Configuration
section</a> for further details on how to configure the proxy portlet
settings in Pluto.<br>
<span style="font-weight: bold; font-style: italic;">Prereq's:
Tomcat 4.1.x, Pluto Installation</span><br>
<br>
<span style="font-weight: bold;">install-provider-simple<br>
</span>WSRP4J also includes a WSRP producer which is able
to provide 'simple' WSRPlets as a WSRP service. To install this provider
simply execute the <span style="font-style: italic;">install-provider-simple</span>
batch with no arguments. <br>
<span style="font-weight: bold; font-style: italic;">Prereq's:
Tomcat 4.1.x</span><br>
<br>
<span style="font-weight: bold;">install-provider-pluto<br>
</span>Executing the <span style="font-style: italic;">install-provider-pluto</span>
batch installs the Pluto provider which is able to provide <a
href="http://www.jcp.org/en/jsr/detail?id=168">JSR168</a> compliant
portlets as web services. Since this provider runs in a Tomcat
environment and needs to have access to the portlets web application,
you manually need to add a context tag with the crossContext attribute
set to 'true' in the server.xml Tomcat configuration file. To do this
simply add the line '<Context path="/wsrp" docBase="wsrp"
crossContext="true"/>' anywhere between the <Host>
opening and closing tag.<br>
<span style="font-weight: bold; font-style: italic;">Prereq's:
Tomcat 4.1.x</span><br>
</blockquote>
<p> </p>
</td>
</tr>
</tbody>
</table>
<!-- START:RIGHT SIDE CONTENT -->
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
</tr>
<tr>
<td><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<!-- FOOTER --> <tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<td colspan="2">
<div align="center"> <font color="#525d76" size="-1"><em>Copyright
?? 2003, Apache Software Foundation </em></font> </div>
</td>
</tr>
</tbody>
</table>
<!-- end the processing -->
</body>
</html>
1.1 ws-site/targets/wsrp4j/na.html
Index: na.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="author" value="Stephan Laertz" content="Stephan Laertz">
<meta name="email" value="stephan.laertz@de.ibm.com">
<meta content="MSHTML 6.00.2600.0" name="GENERATOR">
<title>WSRP4J Installation</title>
</head>
<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"
link="#525d76">
<!-- TOP IMAGE -->
<table cellspacing="0" width="100%" border="0">
<tbody>
<tr>
<td colspan="2"><a href="http://www.apache.org/"><img
src="http://www.apache.org/images/asf_logo_wide.gif"
alt="The Apache Software Foundation" align="left" border="0"></a></td>
</tr>
</tbody>
</table>
<table cellspacing="4" width="100%" border="0">
<tbody>
<tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<!-- START:LEFT SIDE NAVIGATION --> <td valign="top" nowrap="nowrap"
width="20%">
<p> <strong>Project</strong> </p>
<ul>
<li> <a href="index.html">Welcome</a></li>
<li><a href="arch.html">Architecture</a></li>
<ul>
<li><a href="arch-producer.html">Producer</a></li>
<li><a href="arch-consumer.html">Consumer</a><br>
</li>
</ul>
<li><a href="na.html">News</a><br>
</li>
<li> <a href="na.html">Status</a></li>
<li><a href="na.html">Bugs</a><br>
</li>
</ul>
<p> <strong>Getting Started</strong> </p>
<ul>
<li> <a href="na.html">Installation</a> </li>
<li> <a href="na.html">Configuration</a> </li>
<li> <a href="na.html">FAQ</a> </li>
</ul>
<p> <strong>Links<br>
</strong> </p>
<ul>
<li> <a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">OASIS
WSRP</a></li>
<li><a
href="http://nagoya.apache.org/wiki/apachewiki.cgi?PlutoProposal">Pluto
Proposal</a><br>
</li>
<li><a href="http://jakarta.apache.org/tomcat/">Tomcat</a><br>
</li>
</ul>
</td>
<!-- END:LEFT SIDE NAVIGATION --><!-- START:RIGHT SIDE CONTENT --> <td
valign="top" align="left" width="80%">
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
<td bgcolor="#525d76"><font face="arial,helvetica,sanserif"
color="#ffffff"><a name="Welcome to The Charon Project"><strong>Under Construction</strong></a> </font></td>
</tr>
<tr>
<td>
Sorry! This page is under construction.
</td>
</tr>
</tbody>
</table>
<!-- START:RIGHT SIDE CONTENT -->
<table cellspacing="0" cellpadding="2" width="100%" border="0">
<tbody>
<tr>
</tr>
<tr>
<td><br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
<!-- FOOTER --> <tr>
<td colspan="2">
<hr noshade="noshade" size="1"> </td>
</tr>
<tr>
<td colspan="2">
<div align="center"> <font color="#525d76" size="-1"><em>Copyright
?? 2003, Apache Software Foundation </em></font> </div>
</td>
</tr>
</tbody>
</table>
<!-- end the processing -->
</body>
</html>
1.1 ws-site/targets/wsrp4j/images/consumer_architecture.jpg
<<Binary file>>
1.1 ws-site/targets/wsrp4j/images/overview1.jpg
<<Binary file>>
1.1 ws-site/targets/wsrp4j/images/portal_overview.gif
<<Binary file>>
1.1 ws-site/targets/wsrp4j/images/producer_architecture.jpg
<<Binary file>>
1.1 ws-site/targets/wsrp4j/images/wsrp4j_components.gif
<<Binary file>>