Skip to main content

Notice: This Wiki is now read only and edits are no longer 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"

(Columns)
m
Line 3: Line 3:
 
{| class="wikitable" style="text-align:left; width="100%" align="left" valign="top" border="1" cellpadding="5" cellspacing="0"
 
{| class="wikitable" style="text-align:left; width="100%" align="left" valign="top" border="1" cellpadding="5" cellspacing="0"
 
|-style="background:grey; color:black"
 
|-style="background:grey; color:black"
! width="30%" border="1" align="left" valign="top" colspan="3" | Deployment Scenario
+
! 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" | OS
 
! width="10%" border="1" align="left" valign="top" | Runtime
 
! width="10%" border="1" align="left" valign="top" | Runtime
Line 12: Line 12:
 
! width="10%" border="1" align="left" valign="top" | Owner
 
! width="10%" border="1" align="left" valign="top" | Owner
 
|-style="background:#d6dee9; color:black"
 
|-style="background:#d6dee9; color:black"
|colspan="3" | [[Managed Card Provider]]  
+
|colspan="4" | [[Managed Card Provider]]  
 
|SUSE 10?
 
|SUSE 10?
 
|
 
|
Line 22: Line 22:
 
|-
 
|-
 
|
 
|
|colspan="2" | [[Token Service]]
+
|colspan="3" | [[Token Service]]
 
|"
 
|"
 
|Tomcat
 
|Tomcat
Line 32: Line 32:
 
|-
 
|-
 
|
 
|
|colspan = "2" | [[Identity Attribute Service]]
+
|colspan = "3" | [[Identity Attribute Service]]
 
|"
 
|"
 
|?
 
|?
Line 43: Line 43:
 
|
 
|
 
|
 
|
| LDAP Context Provider
+
|colspan = "2" | LDAP Context Provider
 +
|"
 +
|?
 +
|?
 +
|?
 +
|n/a
 +
|n/a
 +
|n/a
 +
|-
 +
|
 +
|
 +
|
 +
|Local LDAP Server
 
|"
 
|"
 
|?
 
|?
Line 52: Line 64:
 
|n/a
 
|n/a
 
|-style="background:#d6dee9; color:black"
 
|-style="background:#d6dee9; color:black"
|colspan="3" | [[Local Higgins Service]]
+
|colspan="4" | [[Local Higgins Service]]
 
|
 
|
 
|
 
|
Line 61: Line 73:
 
|
 
|
 
|-style="background:#d6dee9; color:black"
 
|-style="background:#d6dee9; color:black"
|colspan="3" | [[Zero Footprint Higgins Service]]
+
|colspan="4" | [[Zero Footprint Higgins Service]]
 
|
 
|
 
|
 
|
Line 74: Line 86:
  
 
===Columns===
 
===Columns===
* Deployment Scenario (3 columns) - Wiki page describing deployment scenario / name of component used / name of plug-in used
+
* Deployment Scenario - Wiki page describing deployment scenario
 +
** name of component used
 +
*** name of plug-in used (if applicable)
 +
**** name of required non-Higgins service (if any)
 
* OS - OS that each component requires, and has been tested on
 
* OS - OS that each component requires, and has been tested on
 
* Runtime - Runtime environment for component
 
* Runtime - Runtime environment for component

Revision as of 00:03, 13 November 2006

This is a new wiki page that will list the various deployment architectures/scenarios that the Higgins project intendes to support

Deployment Scenario OS Runtime Packaging Binding Open URL Owner
Managed Card Provider SUSE 10? TBD TBD TBD
Token Service " Tomcat WAR WS-Trust, WS-Transfer? n/a n/a n/a
Identity Attribute Service " ? ? ? n/a n/a n/a
LDAP Context Provider " ? ? ? n/a n/a n/a
Local LDAP Server " ? ? ? n/a n/a n/a
Local Higgins Service
Zero Footprint Higgins Service

.

Columns

  • Deployment Scenario - Wiki page describing deployment scenario
    • name of component used
      • name of plug-in used (if applicable)
        • name of required non-Higgins service (if any)
  • OS - OS that each component requires, and has been tested on
  • Runtime - Runtime environment for component
  • Packaging - how will component be made available for installation
  • Binding - how will externally consumed services of deployment scenario be consumed
  • Open - open enhancements and bugs (Bugzilla)
  • URL - endpoint that hosts a test service (hosted by Eclipse Foundation)
  • Owner - person with overall responsibility for this deployment scenario (not individual components)

Back to the top