Adding the RDH to the BES - Revision history

PatrickWest: /* Basic Flow */

2010-05-18T16:39:32Z

Basic Flow

← Older revision		Revision as of 16:39, 18 May 2010
Line 56:		Line 56:
	#::<tt>BES.modules=dap,cmd,ascii,usage,www,nc,h4,rdh</tt>		#::<tt>BES.modules=dap,cmd,ascii,usage,www,nc,h4,rdh</tt>
	#: and add a new line specific to the RDH to configure it's Data Sources:		#: and add a new line specific to the RDH to configure it's Data Sources:
	#::<tt>BES.rdh.datasources=dataSourceOne,dataSourceTwo,dataSourceThree</tt><font color="red">where are these defined? - pcw</font>		#::<tt>BES.rdh.datasources=dataSourceOne,dataSourceTwo,dataSourceThree</tt> <font color="red">where are these defined? - pcw</font>
	# The user (re)starts the BES		# The user (re)starts the BES
	# At start-up the RDH loads it's configuration components from the bes.conf file.		# At start-up the RDH loads it's configuration components from the bes.conf file.

PatrickWest: /* Basic Flow */

2010-05-18T16:39:10Z

Basic Flow

← Older revision		Revision as of 16:39, 18 May 2010
Line 47:		Line 47:
	== Basic Flow ==		== Basic Flow ==
	<font size="-2" color="green">''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''</font>		<font size="-2" color="green">''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''</font>
	<br><font color="red">Instead of editing bes.conf, create a rdh.conf in the etc/bes/modules directory. Every conf file in that directory is loaded by the BES.</font>		<br><font color="red">Instead of editing bes.conf, create a rdh.conf in the etc/bes/modules directory. Every conf file in that directory is loaded by the BES. - pcw</font>

	# User (installer/configurer) installs (builds and installs or installs a binary) of the RDH code '''		# User (installer/configurer) installs (builds and installs or installs a binary) of the RDH code '''
Line 56:		Line 56:
	#::<tt>BES.modules=dap,cmd,ascii,usage,www,nc,h4,rdh</tt>		#::<tt>BES.modules=dap,cmd,ascii,usage,www,nc,h4,rdh</tt>
	#: and add a new line specific to the RDH to configure it's Data Sources:		#: and add a new line specific to the RDH to configure it's Data Sources:
	#::<tt>BES.rdh.datasources=dataSourceOne,dataSourceTwo,dataSourceThree</tt>		#::<tt>BES.rdh.datasources=dataSourceOne,dataSourceTwo,dataSourceThree</tt><font color="red">where are these defined? - pcw</font>
	# The user (re)starts the BES		# The user (re)starts the BES
	# At start-up the RDH loads it's configuration components from the bes.conf file.		# At start-up the RDH loads it's configuration components from the bes.conf file.

PatrickWest: /* Basic Flow */

2010-05-18T16:37:25Z

Basic Flow

← Older revision		Revision as of 16:37, 18 May 2010
Line 47:		Line 47:
	== Basic Flow ==		== Basic Flow ==
	<font size="-2" color="green">''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''</font>		<font size="-2" color="green">''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''</font>
	<font color="red">Instead of editing bes.conf, create a rdh.conf in the etc/bes/modules directory. Every conf file in that directory is loaded by the BES.</font>		<br><font color="red">Instead of editing bes.conf, create a rdh.conf in the etc/bes/modules directory. Every conf file in that directory is loaded by the BES.</font>

	# User (installer/configurer) installs (builds and installs or installs a binary) of the RDH code '''		# User (installer/configurer) installs (builds and installs or installs a binary) of the RDH code '''

PatrickWest: /* Basic Flow */

2010-05-18T16:37:04Z

Basic Flow

← Older revision		Revision as of 16:37, 18 May 2010
Line 47:		Line 47:
	== Basic Flow ==		== Basic Flow ==
	<font size="-2" color="green">''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''</font>		<font size="-2" color="green">''Often referred to as the primary scenario or course of events. In the basic flow we describe the flow that would be followed if the use case where to follow its main plot from start to end. Error states or alternate states that might be highlighted are not included here. This gives any browser of the document a quick view of how the system will work. Here the flow can be documented as a list, a conversation or as a story.(as much as required)''</font>
			<font color="red">Instead of editing bes.conf, create a rdh.conf in the etc/bes/modules directory. Every conf file in that directory is loaded by the BES.</font>

	# User (installer/configurer) installs (builds and installs or installs a binary) of the RDH code '''		# User (installer/configurer) installs (builds and installs or installs a binary) of the RDH code '''

Ndp: /* Basic Flow */

2009-05-05T23:10:55Z

Basic Flow

← Older revision		Revision as of 23:10, 5 May 2009
Line 58:		Line 58:
	# The user (re)starts the BES		# The user (re)starts the BES
	# At start-up the RDH loads it's configuration components from the bes.conf file.		# At start-up the RDH loads it's configuration components from the bes.conf file.
	# The RDH caches the list of Data Source Names into memory.		# The RDH caches the list of Data Source Names into a memory object (like a HashMap that relates resource ID to Data Source).

	== Alternate Flow ==		== Alternate Flow ==

Ndp: /* Resources */

2009-04-29T17:21:25Z

Resources

← Older revision		Revision as of 17:21, 29 April 2009
Line 86:		Line 86:
	\|Availability		\|Availability
	\|Source System		\|Source System
	\|-
	~~\|<font size="-2" color="green">''name''</font>~~
	~~\|<font size="-2" color="green">''Organization that owns/ manages resource''</font>~~
	~~\|<font size="-2" color="green">''Short description of the resource''</font>~~
	~~\|<font size="-2" color="green">''How often the resource is available''</font>~~
	~~\|<font size="-2" color="green">''Name of system which provides resource''</font>~~
	\|-		\|-
	\| BES		\| BES

Ndp: /* Summary */

2009-04-29T17:12:18Z

Summary

← Older revision		Revision as of 17:12, 29 April 2009
Line 17:		Line 17:
	* The names of the ODBC Data Sources for which it is going to serve data.		* The names of the ODBC Data Sources for which it is going to serve data.

	~~It then connects to the Data Sources and uses the introspection methods of ODBC to collect~~ information ~~about the tables and views~~ in ~~the target database. (This activity may happen at startup~~ and ~~be refreshed asynchronously, or it may be gathered each time a request for the cataolg/inventory~~ is ~~received)) From this inventory the RDH builds a catalog of DAP datasets which get described by the bes:showInfo and bes:showCatalog commands~~.		The RDH caches that information in memory and is then ready to respond to requests.

	This use case covers just how the RDH handler is added to the BES~~, how it uses~~ it's configuration ~~to establish a connection with an RDBMS, and building the catalog~~.		This use case covers just how the RDH handler is added to the BES and the process of ingesting and caching it's configuration.

	== Actors ==		== Actors ==

Ndp: /* Resources */

2009-04-28T19:02:26Z

Resources

← Older revision		Revision as of 19:02, 28 April 2009
Line 93:		Line 93:
	\|<font size="-2" color="green">''Name of system which provides resource''</font>		\|<font size="-2" color="green">''Name of system which provides resource''</font>
	\|-		\|-
	\|BES		\| BES
	\|Data Provider		\| Data Provider
	\|The data server		\| The data server
	\|Once installed, it can be hard to get the admin to make changes		\| Once installed, it can be hard to get the admin to make changes
	\|N/a		\| N/a
	\|-		\|-
	\|ODBC Driver		\| ODBC Driver
	\|~~The data provider~~		\| Data Provider
	\|The ODBC driver compatible with the target RDBMS.		\| The ODBC driver compatible with the target RDBMS.
	\|Open source availability for most open source RDBMSs. Purchase availability fr others.		\| Open source availability for most open source RDBMSs. Purchase availability fr others.
	\|Hardware running the ~~server and/or staging the data~~.		\| Hardware running the BES.
	\|-		\|-
	\|ODBC configuration		\| ODBC configuration
	\|~~The data provider~~		\| Data Provider
	\|A system level ODBC configuration		\| A system level ODBC configuration
	\|		\| Operating system dependent. Complexity of creation a function of target OS.
	\|Hardware running the ~~server and/or staging the data~~.		\| Hardware running the BES.

	\|-		\|-
	\|ODBC Data Sources		\| ODBC Data Sources
	\|~~The data provider~~		\| Data Provider
	\|A Data Source definition for each RDBMS database to be served as a DAP Dataset		\| A Data Source definition for each RDBMS database to be served as a DAP Dataset
	\|		\| Operating system dependent. Complexity of creation a function of target OS.
	\|Hardware running the ~~server and/or staging the data~~.		\| Hardware running the BES.

	\|-		\|-
	\|~~ODBC configuration~~		\| Target RDBMS(s)
	\|~~The data provider~~		\| Database Operator/Provider
	\|A system ~~level ODBC configuration~~		\| The relational database management system(s) that will provide the data server by the RDH.
	\|Depends on ~~how easy~~ it ~~is for the metadata writer to get access to the server~~'s~~/data's file~~ system		\| Depends on level of operators permission in the RDBMS and it's host system. At minimum SQL SELECT access must be available on all databases, tables, and views which will be served.
	\|Hardware running the ~~server and/or staging~~ the ~~data~~.		\| Hardware running the RDMS. Not required to be the same system running the BES.

	\|}		\|}

Ndp: /* Resources */

2009-04-28T18:51:21Z

Resources

← Older revision		Revision as of 18:51, 28 April 2009
Line 107:		Line 107:
	\|ODBC configuration		\|ODBC configuration
	\|The data provider		\|The data provider
	\|A ~~correctly configured System~~ ODBC		\|A system level ODBC configuration
			\|
			\|Hardware running the server and/or staging the data.

			\|-
			\|ODBC Data Sources
			\|The data provider
			\|A Data Source definition for each RDBMS database to be served as a DAP Dataset
			\|
			\|Hardware running the server and/or staging the data.

			\|-
			\|ODBC configuration
			\|The data provider
			\|A system level ODBC configuration
	\|Depends on how easy it is for the metadata writer to get access to the server's/data's file system		\|Depends on how easy it is for the metadata writer to get access to the server's/data's file system
	\|Hardware running the server and/or staging the data.		\|Hardware running the server and/or staging the data.

	\|}		\|}

Ndp: /* Resources */

2009-04-28T18:46:21Z

Resources

@@ Line 92: / Line 92: @@
 |<font size="-2" color="green">''How often the resource is available''</font>
 |<font size="-2" color="green">''Name of system which provides resource''</font>
 |}