Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Higgins/Solutions"

(I-Card Manager Web App)
(Redirecting to Solutions)
 
(286 intermediate revisions by 8 users not shown)
Line 1: Line 1:
==Overview==
+
#REDIRECT [[Solutions]]
A '''Deployment Scenario''' is a specific combination of [[Components]] that, when assembled and deployed result in an application or service that is identifiable to an end-user as a "whole" app or service. This page is intended to explain how to assemble building block [[Components]] into running apps and services. The indended audience is technical, but more about assembling, building and deploying, as opposed to "developing."
+
 
+
Some of the Deployment Scenarios are web services or webapps that have been deployed on Eclipse servers and can be used for testing and and development-related purposes. Examples would include a CardSpace-compatible IdP service (what Microsoft would call a "Managed Card Provider" (not to be confused with our use of the term provider)), or a MediaWiki app that supports OpenID sign-in, etc.
+
 
+
Each Deployment Scenario should be desribed in its own section on this page, and should include a table with rows that describe the [[Components]] involved. This table should include build scripts and other 3rd party libraries.
+
 
+
==Deployment Scenarios==
+
 
+
===CardSpace-interoperable Identity Provider/STS===
+
{| class="wikitable" style="text-align:left; border="1" cellpadding="5" cellspacing="0"
+
|-style="background:grey; color:black"
+
! width="30%" border="1" align="left" valign="top" colspan="2" | Deployment Scenario
+
! width="10%" border="1" align="left" valign="top" | OS
+
! width="10%" border="1" align="left" valign="top" | Runtime
+
! width="15%" border="1" align="left" valign="top" | Assemble & Deploy
+
! width="10%" border="1" align="left" valign="top" | Binding
+
! width="10%" border="1" align="left" valign="top" | Open
+
! width="10%" border="1" align="left" valign="top" | URL
+
! width="10%" border="1" align="left" valign="top" | Owner
+
|-style="background:#d6dee9; color:black"
+
|colspan="2" | [[CardSpace-interoperable IdP/STS]]
+
|n/a
+
|n/a
+
|n/a
+
|n/a
+
|TBD
+
|[http://wag.bandit-project.org Wag (IdP)]<br>[http://woof.bandit-project.org Woof (RP)]
+
|[mailto:dsanders@novell.com DSanders]
+
|-
+
|
+
|[[Token Service]]
+
|Open SUSE 10.2
+
|JVM 5.0, Tomcat X.X
+
|[http://wiki.eclipse.org/index.php/Components#Token_Service here]
+
|WS-Trust, WS-Transfer
+
|[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Higgins&component=TOKEN+PROVIDER open]
+
|n/a
+
|[mailto:mikemci@us.ibm.com MikeM]
+
|-
+
|
+
|[[Identity Attribute Service]]
+
|Open SUSE 10.2
+
|JVM 5.0
+
|[http://wiki.eclipse.org/index.php/Components#Identity_Attribute_Service here]
+
|Java Interfaces
+
|[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Higgins&component=IdAS open]
+
|n/a
+
|[mailto:jimse@novell.com JimS]
+
|-
+
|
+
|LDAP Context Provider
+
|Open SUSE 10.2
+
|JVM 5.0
+
|[https://forgesvn1.novell.com/svn/bandit/trunk/Higgins viewsvn], ide, cli, [http://www.bandit-project.org/index.php/Common_Identity_Downloads downloads]
+
|Java Interfaces
+
|n/a
+
|n/a
+
|[mailto:tdoman@novell.com TomD]
+
|-
+
|
+
|Open LDAP Server<br>(or other LDAP server)
+
|Open SUSE 10.2
+
|OS
+
|[http://www.openldap.org/software/download/ Open LDAP downloads]
+
|LDAP
+
|n/a
+
|n/a
+
|n/a
+
|-
+
|}
+
.
+
 
+
 
+
 
+
===Identity Agent (in-browser selector, hosted IdA)===
+
* Requires the user to install the [[Higgins Browser Extension]] (HBX). HBX relies on a hosted Identity Agent (IdA) service
+
 
+
===Identity Agent (rich client selector, hosted IdA)===
+
* Requires the user to install the [[Higgins Browser Extension]] (HBX) and the ISS Client UI rich client card selector. ISS Client UI relies on a hosted Identity Agent service
+
 
+
===Identity Agent (rich client selector, local IdA)===
+
* Requires the user to install the [[Higgins Browser Extension]] (HBX) and the ISS Client UI rich client card selector. ISS Client UI relies on a local Identity Agent service.
+
 
+
===I-Card Manager Web App===
+
{| class="wikitable" style="text-align:left; border="1" cellpadding="5" cellspacing="0"
+
|-style="background:#d6dee9; color:black"
+
! width="30%" border="1" align="left" valign="top" | Deployment Scenario
+
! width="10%" border="1" align="left" valign="top" | OS
+
! width="10%" border="1" align="left" valign="top" | Runtime
+
! width="15%" border="1" align="left" valign="top" | Assemble & Deploy
+
! width="10%" border="1" align="left" valign="top" | Binding
+
! width="10%" border="1" align="left" valign="top" | Open
+
! width="10%" border="1" align="left" valign="top" | URL
+
! width="10%" border="1" align="left" valign="top" | Owner
+
|-
+
|[[I-Card Manager Web Application]] (WAR)
+
|Fedora 5
+
|JVM 5.0, Tomcat 5.x, SJSAS 9.0
+
|[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/app/org.eclipse.higgins.broker/apps/icard/icard-war/?root=Technology_Project viewcvs], ide, [[Building I-Card Manager Application | cli]]
+
|WS
+
|TBD
+
|site
+
|[mailto:sergey@parityinc.net SergeiY]
+
|}
+
.
+
 
+
===RPPS Web Service===
+
{| class="wikitable" style="text-align:left; border="1" cellpadding="5" cellspacing="0"
+
|-style="background:#d6dee9; color:black"
+
! width="30%" border="1" align="left" valign="top" | Deployment Scenario
+
! width="10%" border="1" align="left" valign="top" | OS
+
! width="10%" border="1" align="left" valign="top" | Runtime
+
! width="15%" border="1" align="left" valign="top" | Assemble & Deploy
+
! width="10%" border="1" align="left" valign="top" | Binding
+
! width="10%" border="1" align="left" valign="top" | Open
+
! width="10%" border="1" align="left" valign="top" | URL
+
! width="10%" border="1" align="left" valign="top" | Owner
+
|-
+
|[[RPPS Web Application]] (WAR)
+
|Fedora 5
+
|JVM 5.0, Tomcat 5.x
+
|[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/app/org.eclipse.higgins.broker/apps/rpps/?root=Technology_Project viewcvs], ide, cli
+
|WS, RSS-SSE
+
|TBD
+
|WS endpoint
+
|[mailto:sergey@parityinc.net SergeiY]
+
|}
+
.
+
 
+
===RSS-SSE RP Test Application===
+
{| class="wikitable" style="text-align:left; border="1" cellpadding="5" cellspacing="0"
+
|-style="background:#d6dee9; color:black"
+
! width="30%" border="1" align="left" valign="top" | Deployment Scenario
+
! width="10%" border="1" align="left" valign="top" | OS
+
! width="10%" border="1" align="left" valign="top" | Runtime
+
! width="15%" border="1" align="left" valign="top" | Assemble & Deploy
+
! width="10%" border="1" align="left" valign="top" | Binding
+
! width="10%" border="1" align="left" valign="top" | Open
+
! width="10%" border="1" align="left" valign="top" | URL
+
! width="10%" border="1" align="left" valign="top" | Owner
+
|-
+
|[[RSS-SSE RP Test Application]] (WAR)
+
|Fedora 5
+
|JVM 5.0, Tomcat 5.x
+
|[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.higgins/app/org.eclipse.higgins.broker/apps/rssrp/?root=Technology_Project viewcvs], ide, cli
+
|WS, RSS-SSE
+
|TBD
+
|[http://higgins.eclipse.org/rssrp/ site]
+
|[mailto:sergey@parityinc.net SergeiY]
+
|}
+
.
+
 
+
===Nightly Builds===
+
Though certainly not a "deployment" in the usual sense, the Higgins project automatically builds some of the [[Components]] every night.
+
{| class="wikitable" style="text-align:left; border="1" cellpadding="5" cellspacing="0"
+
|-style="background:grey; color:black"
+
! width="30%" border="1" align="left" valign="top" colspan="4" | Deployment Scenario
+
! width="10%" border="1" align="left" valign="top" | OS
+
! width="10%" border="1" align="left" valign="top" | Runtime
+
! width="15%" border="1" align="left" valign="top" | Assemble & Deploy
+
! width="10%" border="1" align="left" valign="top" | Binding
+
! width="10%" border="1" align="left" valign="top" | Open
+
! width="10%" border="1" align="left" valign="top" | URL
+
! width="10%" border="1" align="left" valign="top" | Owner
+
|-style="background:#d6dee9; color:black"
+
|colspan="4" | [[Nightly Component Builds]]
+
|SUSE
+
|Ant
+
|[[Nightly Component Builds PSF | psf]]
+
|n/a
+
|TBD
+
|build.eclipse.org
+
|[mailto:evgeniy@parityinc.net EvgeniyV]
+
|-
+
|}
+
.
+
 
+
==Conventions Used V2==
+
Each Deployment Scenario is documented by a table. In cases where this is a multi-row table, there should  be a short paragraph on this page that describing how the multiple machines are used together. For example: if row/machine#1 is running Firefox with HBX and row/machine#2 is running the I-Card Manager then using the browser you'll be able to do <something>.
+
 
+
* The deployment owner is responsible for maintenance of this table
+
* Each computer involved has its own row. This row describes that computer's configuration (OS, runtime, etc.).
+
 
+
Table Columns
+
# '''Deployment Scenario''' - link to wiki page describing deployment scenario (see "Deployment Description" section below)
+
# '''OS''' - OS that this machine either (a) runs on (see URL column) or (b) has been tested on. Put in parens the OS number if more than OS instance is involved
+
# '''Runtime''' - Runtime environment for this machine (e.g. JVM & version, Tomcat & version, etc.)
+
# '''Binding''' - how will the service running on this machine be consumed
+
# '''Open''' - open enhancements and bugs (Bugzilla) for this deployment scenario (Note: none are currently defined)
+
# '''URL''' - endpoint that hosts a test version of the service (hosted by Eclipse Foundation)
+
# '''Owner''' - person with overall responsibility for this deployment scenario (not individual components)
+
 
+
===Example Table===
+
{| class="wikitable" style="text-align:left; border="1" cellpadding="5" cellspacing="0"
+
|-style="background:#d6dee9; color:black"
+
! width="30%" border="1" align="left" valign="top" | Deployment Scenario
+
! width="10%" border="1" align="left" valign="top" | OS
+
! width="10%" border="1" align="left" valign="top" | Runtime
+
! width="10%" border="1" align="left" valign="top" | Binding
+
! width="10%" border="1" align="left" valign="top" | Open
+
! width="10%" border="1" align="left" valign="top" | URL
+
! width="10%" border="1" align="left" valign="top" | Owner
+
|-
+
|CardSpace-interoperable IdP/STS
+
|Open SUSE 10.2
+
|JVM 5.0<br>Tomcat 5.0
+
|WS-Trust<br>WS-Transfer
+
|TBD
+
|[http://wag.bandit-project.org Wag (IdP)]
+
|[mailto:dsanders@novell.com DSanders]
+
|}
+
 
+
===Deployment Description===
+
This wiki page must contain the following sections:
+
# Overview --describes briefly the service running on this machine
+
# Assembly and Build
+
#* A table with a row for each Higgins component required and a row for each non-Higgins component JAR, etc required. Each row has these columns:
+
#*# Name of component/jar
+
#*# Link to description --in the case of Higgins components and projects this should be a link to the [[Components]]page#<component-name> AND the row prefix (e.g. "A" or "B")
+
# Deployment
+
#* Deployment "hints": things you might have had to do to "configure" the files. For example the STS and LDAP CP have several configuration files that need to be explained a little for anyone wanting to replicate the deployment to their own servers. Another example: Tomcat configuration
+
#* Any unusual steps related to configuring non-Higgins components
+
The Assembly and Build instructions section would start off with a bulleted list of components and other external stuff that you'll need. We can include links to the various required rows on the Components page tables as we've started doing.
+
 
+
==Conventions Used V1==
+
The tables on this wiki page have the following column structure:
+
# '''Deployment Scenario''' - link to wiki page describing deployment scenario
+
# '''OS''' - OS that this deployment either (a) runs on (see URL column) or (b) has been tested on. Put in parens the OS number if more than OS instance is involved
+
# '''Runtime''' - Runtime environment for component (e.g. JVM & version, Tomcat & version, etc.)
+
# '''Assemble & Deploy'''
+
#* Links to documentation
+
# '''Binding''' - how will externally consumed services of deployment scenario be consumed
+
# '''Open''' - open enhancements and bugs (Bugzilla) for this deployment scenario (Note: none are currently defined)
+
# '''URL''' - endpoint that hosts a test service (hosted by Eclipse Foundation)
+
# '''Owner''' - person with overall responsibility for this deployment scenario (not individual components)
+
 
+
==See Also==
+
* [http://eclipse.org/higgins Higgins Home]
+

Latest revision as of 13:18, 12 March 2008

Redirect to:

Back to the top