Higgins/Solutions

Overview

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

Deployment Scenario				OS	Runtime	Source & Build	Binding	Open	URL	Owner
CardSpace-compatible IdP				n/a	n/a	n/a	n/a	TBD	Wag (IdP) Woof (RP)	DSanders
	Token Service			Open SUSE 10.2	JVM 5.0, Tomcat X.X	viewcvs, ide, cli, instructions	WS-Trust, WS-Transfer	open	n/a	MikeM
	Identity Attribute Service			Open SUSE 10.2	JVM 5.0	viewcvs, ide, cli	Java Interfaces	open	n/a	JimS
	LDAP Context Provider			Open SUSE 10.2	JVM 5.0	viewsvn, ide, cli, downloads	Java Interfaces	n/a	n/a	TomD
	Open LDAP Server (or other LDAP server)			Open SUSE 10.2	OS	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 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:

1. Deployment Scenario - link to wiki page describing deployment scenario
2. 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
3. Runtime - Runtime environment for component (e.g. JVM & version, Tomcat & version, etc.)
4. 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
5. Binding - how will externally consumed services of deployment scenario be consumed
6. Open - open enhancements and bugs (Bugzilla) for this deployment scenario (Note: none are currently defined)
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