Higgins/Solutions

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

Identity Provider

Deployment Scenario				OS	Runtime	Source & Build	Binding	Issues	URL	Owner
CardSpace Managed Card Provider				n/a	n/a	psf	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
RSS-SSE RP Test Site	Fedora 5	JVM 5.0, Tomcat 5.X		RSS-SSE	open	site	SergeiY
I-Card Manager Web Application (WAR)	All	JVM 5.0, Tomcat 5.X	viewcvs, WAR				SergeiY
RPPS Web Application (WAR)	All	JVM 5.0, Tomcat 5.X	viewcvs, WAR	WebServices, RSS-SSE			SergeiY
RSS-SSE RP Test Application (WAR)	All	JVM 5.0, Tomcat 5.X	viewcvs, WAR	HTTP, RSS-SSE	open	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:

1. Deployment Scenario - link to wiki page describing deployment scenario
   • Included Component - see Components
     • Included plug-in (if applicable)
       • Consumed non-Higgins service (if any)
2. OS - OS that this deployment actually runs on (if live) or has been tested on. Put in parens the OS number if more than OS instance is involved
3. Runtime - Runtime environment for component (e.g. JVM & version, Tomcat & version, etc.)
4. Packaging - how will component be made available for installation
5. Binding - how will externally consumed services of deployment scenario be consumed
6. Open - open enhancements and bugs (Bugzilla)
7. URL - endpoint that hosts a test service (hosted by Eclipse Foundation)
8. Owner - person with overall responsibility for this deployment scenario (not individual components)

See Also

• Higgins Home