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.
Difference between revisions of "Higgins/Solutions"
< Higgins
(→Higgins I-Card Broker Enterprise Application (EAR)) |
(→Conventions Used) |
||
| Line 176: | Line 176: | ||
The tables on this wiki page have the following column structure: | The tables on this wiki page have the following column structure: | ||
# '''Deployment Scenario''' - link to wiki page describing deployment scenario | # '''Deployment Scenario''' - link to wiki page describing deployment scenario | ||
| − | # '''OS''' - OS that this deployment | + | # '''OS''' - OS that this deployment either (a) runs on (see URL column) or 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.) | # '''Runtime''' - Runtime environment for component (e.g. JVM & version, Tomcat & version, etc.) | ||
# '''Source & Build''' | # '''Source & Build''' | ||
Revision as of 16:07, 5 February 2007
Overview
Higgins Components when complete (version 1.0) will be able to be used as lego blocks to construct a number of Deployment Scenarios each of which is documented (or will be!) on this page.
A Deployment Scenario is a specific combination of Components and the build and deployment instructions, build scripts and other 3rd party libraries. Each Deployment Scenario is documented in a separate table on this page (or should be!). 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.
Identity Provider
| Deployment Scenario | OS | Runtime | Source & Build | Binding | Issues | URL | Owner | |||
|---|---|---|---|---|---|---|---|---|---|---|
| CardSpace Managed Card Provider | n/a | n/a | [[CardSpace Managed Card Provider PSF | psf], cli] | n/a | TBD | TBD | Daniel | |||
| Token Service | SUSE(1) | JVM 5.0, Tomcat X.X | WAR | WS-Trust, WS-Transfer | n/a | n/a | ||||
| Identity Attribute Service | SUSE(1) | ? | ? | ? | n/a | n/a | ||||
| LDAP Context Provider | SUSE(1) | ? | ? | ? | n/a | n/a | ||||
| OpenLDAP Server | SUSE(2) | ? | ? | ? | 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.
Higgins I-Card Broker Enterprise Application (EAR)
| Deployment Scenario | OS | Runtime | Source & Build | Binding | Open | URL | Owner | |
|---|---|---|---|---|---|---|---|---|
| Higgins I-Card Broker Enterprise Application (EAR) | Fedora 5 | JVM 5.0, JavaEE | viewcvs, ide, cli | SergeiY | ||||
| I-Card Manager Web Application (WAR) | Fedora 5 | JVM 5.0, SJSAS 9.0 | viewcvs, ide, cli | HTTP | site | SergeiY | ||
| I-Card Manager EJB Module (JAR) | Fedora 5 | JVM 5.0, SJSAS 9.0 | viewcvs, ide, cli | RMI | n/a | SergeiY | ||
| RPPS Web Application (WAR) | Fedora 5 | JVM 5.0, Tomcat 5.x | viewcvs, ide, cli | WebServices, RSS-SSE | WS endpoint | SergeiY | ||
| RSS-SSE RP Test Application (WAR) | Fedora 5 | JVM 5.0, Tomcat 5.x | viewcvs, ide, cli | HTTP, RSS-SSE | site | SergeiY | ||
.
Nightly Builds
Though certainly not a "deployment" in the usual sense, the Higgins project automatically builds some of the Components every night.
| Deployment Scenario | OS | Runtime | Source & Build | Binding | Open | URL | Owner | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Nightly Component Builds | SUSE | Ant | psf | n/a | TBD | build.eclipse.org | EvgeniyV | |||
.
Conventions Used
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 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.)
- Source & Build
- ide link to .psfs (anonymous and committer) to build this deployemnt
- cli link to command line instructions for how to build this deployment
- 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)