Appboard/2.4/software components - Revision history

imported>Jason.nicholls: /* Overview */

2014-09-08T06:41:28Z

Overview

← Older revision		Revision as of 06:41, 8 September 2014
Line 7:		Line 7:
	This page details the individual software components. For a more general overview of how AppBoard works, refer to the [[appboard/2.4/overview\|Overview]] page.		This page details the individual software components. For a more general overview of how AppBoard works, refer to the [[appboard/2.4/overview\|Overview]] page.

	[[File:AppBoardComponents2.png\|frameless\|~~765px~~\|AppBoard Software Components]]		[[File:AppBoardComponents2.png\|frameless\|756px\|AppBoard Software Components]]

	== Main Components ==		== Main Components ==

imported>Jason.nicholls: /* Overview */

2014-09-08T06:38:01Z

Overview

← Older revision		Revision as of 06:38, 8 September 2014
Line 7:		Line 7:
	This page details the individual software components. For a more general overview of how AppBoard works, refer to the [[appboard/2.4/overview\|Overview]] page.		This page details the individual software components. For a more general overview of how AppBoard works, refer to the [[appboard/2.4/overview\|Overview]] page.

	[[File:~~AppBoardComponents~~.png\|~~frame~~\|AppBoard Software Components]]		[[File:AppBoardComponents2.png\|frameless\|765px\|AppBoard Software Components]]

	== Main Components ==		== Main Components ==

imported>Jason.nicholls: /* Authentication Service */

2014-07-14T05:09:09Z

Authentication Service

← Older revision		Revision as of 05:09, 14 July 2014
Line 27:		Line 27:
	==== Authentication Service ====		==== Authentication Service ====

	AppBoard provides it's own user, role, and domain based authentication ~~system~~ which can be managed internally or via integration with an external source. This includes LDAP-based systems such as Microsoft Active Directory, IBM Directory Server, Oracle Directory Server, Novel eDirectory, etc... AppBoard can also be customized to integrate with other authentication systems.		AppBoard provides it's own user, role, and domain based authentication service which can be managed internally or via integration with an external source. This includes LDAP-based systems such as Microsoft Active Directory, IBM Directory Server, Oracle Directory Server, Novel eDirectory, etc... AppBoard can also be customized to integrate with other authentication systems.

	If ~~using an~~ external authentication ~~systems~~ then the AppBoard server will need network ~~communications~~ access to those ~~systems~~.		If integrating with external authentication services then the AppBoard server will need network access to those services.

	==== Configuration Database ====		==== Configuration Database ====

imported>Jason.nicholls: /* AppBoard Server (Apache Tomcat) */

2014-07-14T05:06:49Z

AppBoard Server (Apache Tomcat)

← Older revision		Revision as of 05:06, 14 July 2014
Line 16:		Line 16:

	The server process listens on two ports, the main port on all interfaces for client traffic, and the shutdown port only on the local interface. These are configurable via [[appboard/2.4/admin/runtime_options\|runtime options]], including whether Tomcat is configured for HTTP or HTTPS.		The server process listens on two ports, the main port on all interfaces for client traffic, and the shutdown port only on the local interface. These are configurable via [[appboard/2.4/admin/runtime_options\|runtime options]], including whether Tomcat is configured for HTTP or HTTPS.

	The server process will also have to establish connections to enPortal proxied we applications, and AppBoard data sources. This is always unique to the deployment and depends on the mix of integrated applications in the overall solution.

	==== Data Integrations (AppBoard visualizations) ====		==== Data Integrations (AppBoard visualizations) ====

imported>Jason.nicholls: /* Data Integrations (AppBoard visualizations) */

2014-07-14T05:05:52Z

Data Integrations (AppBoard visualizations)

← Older revision		Revision as of 05:05, 14 July 2014
Line 21:		Line 21:
	==== Data Integrations (AppBoard visualizations) ====		==== Data Integrations (AppBoard visualizations) ====

	AppBoard visualizations are driven by data fetched from external data sources, or from files accessible to the AppBoard server. In the case of external data sources the server will have to establish connections to those data sources.		AppBoard visualizations are driven by data fetched from external data sources, or from files accessible to the AppBoard server. In the case of external data sources the server will have to establish connections to those data sources. The communications will depend on the type of data sources which may be web-based services, databases (via JDBC), or custom integrations.


	==== Web Integrations (enPortal proxied) ====		==== Web Integrations (enPortal proxied) ====

imported>Jason.nicholls: /* Main Components */

2014-07-14T05:04:12Z

Main Components

← Older revision		Revision as of 05:04, 14 July 2014
Line 19:		Line 19:
	The server process will also have to establish connections to enPortal proxied we applications, and AppBoard data sources. This is always unique to the deployment and depends on the mix of integrated applications in the overall solution.		The server process will also have to establish connections to enPortal proxied we applications, and AppBoard data sources. This is always unique to the deployment and depends on the mix of integrated applications in the overall solution.

	AppBoard ~~may also be configured to user an external authentication source such as LDAP-based (Microsoft Active Directory, IBM Directory Server, Oracle Directory Server, Novel eDirectory, etc...~~)~~, or through custom authenticators.~~		==== Data Integrations (AppBoard visualizations) ====

	=== Configuration Database ===		AppBoard visualizations are driven by data fetched from external data sources, or from files accessible to the AppBoard server. In the case of external data sources the server will have to establish connections to those data sources.


			==== Web Integrations (enPortal proxied) ====

			enPortal proxied web integrations require the server to establish connections to the proxied web applications. Refer to the [[enportal/5.4/overview/software_components\|enPortal Software Components]] page for more information on the components to enPortal. Please note that both AppBoard and enPortal reside in the same Tomcat process and share some components.

			==== Authentication Service ====

			AppBoard provides it's own user, role, and domain based authentication system which can be managed internally or via integration with an external source. This includes LDAP-based systems such as Microsoft Active Directory, IBM Directory Server, Oracle Directory Server, Novel eDirectory, etc... AppBoard can also be customized to integrate with other authentication systems.

			If using an external authentication systems then the AppBoard server will need network communications access to those systems.

			==== Configuration Database ====

	In a default install the configuration database is purely in-memory and running within the Tomcat process. In other words, there is no external process or network communication.		In a default install the configuration database is purely in-memory and running within the Tomcat process. In other words, there is no external process or network communication.

imported>Jason.nicholls: /* Overview */

2014-07-14T04:53:47Z

Overview

← Older revision		Revision as of 04:53, 14 July 2014
Line 3:		Line 3:
	== Overview ==		== Overview ==

	AppBoard consists of a number of software components working together to deliver the overall features. In ~~actual~~ deployments the architecture may ~~also~~ include ~~some custom (~~external ~~to AppBoard) components in addition to the core AppBoard product~~, and ~~any~~ external ~~product integrations~~.		AppBoard consists of a number of software components working together to deliver the overall features. In real deployments the architecture may include external authentication sources, external web integrations proxied via enPortal, and external data sources used by AppBoard.

	This page details the individual software components. For a more general overview of how AppBoard works, refer to the [[appboard/2.4/overview\|Overview]] page.		This page details the individual software components. For a more general overview of how AppBoard works, refer to the [[appboard/2.4/overview\|Overview]] page.

imported>Jason.nicholls at 04:49, 14 July 2014

2014-07-14T04:49:36Z

← Older revision		Revision as of 04:49, 14 July 2014
Line 1:		Line 1:
	{{DISPLAYTITLE:Software Components}}		{{DISPLAYTITLE:AppBoard Software Components}}
	[[Category:AppBoard 2.4]]		[[Category:AppBoard 2.4]]
	== Overview ==		== Overview ==

imported>Jason.nicholls: /* Configuration Database */

2014-07-14T04:13:09Z

Configuration Database

← Older revision		Revision as of 04:13, 14 July 2014
Line 23:		Line 23:
	=== Configuration Database ===		=== Configuration Database ===

	In a default install the configuration database is purely in-memory and running within the Tomcat process. In other words, there is no external process or ~~ports~~.		In a default install the configuration database is purely in-memory and running within the Tomcat process. In other words, there is no external process or network communication.

	In clustering or high-availability environments AppBoard can be configured to use an external configuration database. This is via a JDBC driver and requires network connectivity to the external database.		In clustering or high-availability environments AppBoard can be configured to use an external configuration database. This is via a JDBC driver and requires network connectivity to the external database.

imported>Jason.nicholls: /* AppBoard Server (Apache Tomcat) */

2014-07-14T04:11:18Z

AppBoard Server (Apache Tomcat)

← Older revision		Revision as of 04:11, 14 July 2014
Line 15:		Line 15:
	The AppBoard and enPortal server components run within a single Apache Tomcat process. In default installs this also includes the in-memory configuration database (also see below for more information).		The AppBoard and enPortal server components run within a single Apache Tomcat process. In default installs this also includes the in-memory configuration database (also see below for more information).

	The server process listens on two ports, the main port on all interfaces for client traffic, and the shutdown port only on the local interface. These are configurable via [[appboard/2.4/admin/runtime_options\|runtime options], including whether Tomcat is configured for HTTP or HTTPS.		The server process listens on two ports, the main port on all interfaces for client traffic, and the shutdown port only on the local interface. These are configurable via [[appboard/2.4/admin/runtime_options\|runtime options]], including whether Tomcat is configured for HTTP or HTTPS.

	The server process will also have to establish connections to enPortal proxied we applications, and AppBoard data sources. This is always unique to the deployment and depends on the mix of integrated applications in the overall solution.		The server process will also have to establish connections to enPortal proxied we applications, and AppBoard data sources. This is always unique to the deployment and depends on the mix of integrated applications in the overall solution.