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
(→Pure Higgins Deployment Configurations) |
(→Overview) |
||
Line 1: | Line 1: | ||
==Overview== | ==Overview== | ||
− | A '''Deployment | + | A '''Deployment Configuration''' is a specific combination of [[Components]] that, when assembled and deployed, results in an application or service that is identifiable to an end-user as a "whole" app or service. |
==Pure Higgins Deployment Configurations== | ==Pure Higgins Deployment Configurations== |
Revision as of 00:34, 19 September 2007
Contents
Overview
A Deployment Configuration is a specific combination of Components that, when assembled and deployed, results in an application or service that is identifiable to an end-user as a "whole" app or service.
Pure Higgins Deployment Configurations
- H1a Identity Agent Deployment
- Identity Agent for Firefox
- H1b Identity Agent Deployment
- Identity Agent for IE
- H2 Identity Agent Deployment
- Identity Agent for Firefox on Linux and OSX
- H3 Identity Agent Deployment
- Identity Agent for Firefox on Linux, OSX and Windows
- H4 Identity Agent Deployment
- Identity Agent for RCP Apps
- STS/IdP Deployment
- STS/IdP service
- IdAS Deployment
- Identity Attribute Service
- RP Site Deployment
- Relying Party site
Nightly Builds
- Nightly Component Builds
- Though certainly not a "deployment configuration" in the usual sense, the Higgins project automatically builds some of the Components every night.
Higgins-based Deployment Configurations
This section lists known deployment configurations developed external to the Higgins project, but based on Higgins components.
- Bandit STS/IdP Deployment
- Higgins-based STS/IdP service
- Eclipse ALF Project