Creating Data Sources in MINT - Revision history

Alnaucler at 19:10, 20 February 2020

2020-02-20T19:10:15Z

← Older revision		Revision as of 21:10, 20 February 2020
Line 81:		Line 81:
	A virtual data source is particularly useful if there is the need to combine an IMSMA staging area with another database that contains additional data, e.g. on socioeconomic figures. The prerequisite though is the existence of a common key between the data sets.		A virtual data source is particularly useful if there is the need to combine an IMSMA staging area with another database that contains additional data, e.g. on socioeconomic figures. The prerequisite though is the existence of a common key between the data sets.
	</onlyinclude>		</onlyinclude>
	{{NavBox ~~Business Intelligence~~}}		{{NavBox Hub}}
	[[Category:~~VIE~~]]		[[Category:NoPublic]]

Evinek at 13:42, 6 January 2017

2017-01-06T13:42:58Z

← Older revision		Revision as of 15:42, 6 January 2017
Line 11:		Line 11:
	<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed.Drivers for Postgres and MySQL are included in MINT, others might need to be installed on request.</li>		<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed.Drivers for Postgres and MySQL are included in MINT, others might need to be installed on request.</li>
	<li>'''JNDI data source:''' Java Naming and Directory Interface (JNDI) is also a Java-based technology to connect to and query data. It is defined directly on the MINT server, centrally and only once. The advantages over a JDBC connection are in maintainability and performance - JNDI manages pools of connections instead of opening many separate connections on the database if several processes are accessing the data simultaneously.</li>		<li>'''JNDI data source:''' Java Naming and Directory Interface (JNDI) is also a Java-based technology to connect to and query data. It is defined directly on the MINT server, centrally and only once. The advantages over a JDBC connection are in maintainability and performance - JNDI manages pools of connections instead of opening many separate connections on the database if several processes are accessing the data simultaneously.</li>
	<li>'''Virtual data source:''' this type of data source allows combining multiple JDBC and JNDI data sources in order to make them available through a [[Creating MINT Domains\|domain]]. This is very useful if several databases/data sources, e.g. IMSMA and an additional source, need to be analyzed together. In such a case, it is crucial though to identify a common key that allows joining the data sets.</li>		<li>'''Virtual data source:''' this type of data source allows combining multiple JDBC and JNDI data sources in order to make them available through a common [[Creating MINT Domains\|domain]]. This is very useful if several databases/data sources, e.g. IMSMA and an additional source, need to be analyzed together. In such a case, it is crucial though to identify a common key that allows joining the data sets.</li>
	</ul>		</ul>
	== Create a data source ==__NOEDITSECTION__		== Create a data source ==__NOEDITSECTION__

Evinek at 13:36, 6 January 2017

2017-01-06T13:36:13Z

Evinek at 13:33, 6 January 2017

2017-01-06T13:33:52Z

← Older revision		Revision as of 15:33, 6 January 2017
Line 7:		Line 7:

	== Types of data sources ==__NOEDITSECTION__		== Types of data sources ==__NOEDITSECTION__
	There are different types of data sources. The most common ones to be defined in MINT~~/lightMINT~~ are the following:		There are different types of data sources. The most common ones to be defined in MINT are the following:
	<ul>		<ul>
	<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed. In both MINT and lightMINT, drivers for Postgres and MySQL are included, others might need to be installed on request.</li>		<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed. In both MINT and lightMINT, drivers for Postgres and MySQL are included, others might need to be installed on request.</li>

Evinek at 13:33, 6 January 2017

2017-01-06T13:33:26Z

← Older revision		Revision as of 15:33, 6 January 2017
Line 1:		Line 1:
	<onlyinclude>		<onlyinclude>
	{{TOC right}}		{{TOC right}}
	A connection to a database (for example to the [[IMSMA Staging Area]]) is called a '''Data Source'''. The first step for getting started with MINT ~~or lightMINT~~ is to create a data source. The tool needs to know where the data that has to be analysed is stored. A data source can be:		A connection to a database (for example to the [[IMSMA Staging Area]]) is called a '''Data Source'''. The first step for getting started with MINT is to create a data source. The tool needs to know where the data that has to be analysed is stored. A data source can be:
	* an IMSMA staging area database		* an IMSMA staging area database
	* any other database		* any other database

Alnaucler at 18:59, 29 September 2015

2015-09-29T18:59:40Z

← Older revision		Revision as of 20:59, 29 September 2015
Line 4:		Line 4:
	* an IMSMA staging area database		* an IMSMA staging area database
	* any other database		* any other database
	* an XML or Excel file -- the preferred way however is to import or dump the content of a file in a database and then connect MINT to the database. This solution simply scales better and is better manageable. Please get in touch with your [[Management ~~Consulting~~ Team\|GICHD IM advisor]] prior to including file-based data into MINT.		* an XML or Excel file -- the preferred way however is to import or dump the content of a file in a database and then connect MINT to the database. This solution simply scales better and is better manageable. Please get in touch with your [[Information Management Team\|GICHD IM advisor]] prior to including file-based data into MINT.

	== Types of data sources ==__NOEDITSECTION__		== Types of data sources ==__NOEDITSECTION__
Line 45:		Line 45:
	Once all information has been filled, the connection can be tested and saved.		Once all information has been filled, the connection can be tested and saved.

	{{Note\|The data sources are usually set up at the beginning of a MINT implementation and should not change. However, in case of doubt or if a new data source has to be created, contact your [[Management ~~Consulting~~ Team\|GICHD IM advisor]].}}		{{Note\|The data sources are usually set up at the beginning of a MINT implementation and should not change. However, in case of doubt or if a new data source has to be created, contact your [[Information Management Team\|GICHD IM advisor]].}}

	=== Define a JNDI data source ===__NOEDITSECTION__		=== Define a JNDI data source ===__NOEDITSECTION__
	Once the data sources for a specific MINT implementation are fixed, it is recommended to define JNDI data sources instead of JDBC ones. However, a JNDI data source has to be defined directly on the server and thus has to be set up by the global MINT administrator. Therefore, the creation of a JNDI data source has to be requested to the [[Management ~~Consulting~~ Team\|GICHD IM advisor]], and the following information has to be provided:		Once the data sources for a specific MINT implementation are fixed, it is recommended to define JNDI data sources instead of JDBC ones. However, a JNDI data source has to be defined directly on the server and thus has to be set up by the global MINT administrator. Therefore, the creation of a JNDI data source has to be requested to the [[Information Management Team\|GICHD IM advisor]], and the following information has to be provided:
	<ul>		<ul>
	<li>'''Name:''' name that allows identifying the data source</li>		<li>'''Name:''' name that allows identifying the data source</li>

Alnaucler at 09:15, 6 November 2014

2014-11-06T09:15:18Z

← Older revision		Revision as of 11:15, 6 November 2014
Line 4:		Line 4:
	* an IMSMA staging area database		* an IMSMA staging area database
	* any other database		* any other database
	* an XML or Excel file -- the preferred way however is to import or dump the content of a file in a database and then connect MINT to the database. This solution simply scales better and is better manageable. Please get in touch with your [[Management Consulting Team\|GICHD IM ~~focal point~~]] prior to including file-based data into MINT.		* an XML or Excel file -- the preferred way however is to import or dump the content of a file in a database and then connect MINT to the database. This solution simply scales better and is better manageable. Please get in touch with your [[Management Consulting Team\|GICHD IM advisor]] prior to including file-based data into MINT.

	== Types of data sources ==__NOEDITSECTION__		== Types of data sources ==__NOEDITSECTION__
Line 45:		Line 45:
	Once all information has been filled, the connection can be tested and saved.		Once all information has been filled, the connection can be tested and saved.

	{{Note\|The data sources are usually set up at the beginning of a MINT implementation and should not change. However, in case of doubt or if a new data source has to be created, contact your [[Management Consulting Team\|GICHD IM ~~focal point~~]].}}		{{Note\|The data sources are usually set up at the beginning of a MINT implementation and should not change. However, in case of doubt or if a new data source has to be created, contact your [[Management Consulting Team\|GICHD IM advisor]].}}

	=== Define a JNDI data source ===__NOEDITSECTION__		=== Define a JNDI data source ===__NOEDITSECTION__
	Once the data sources for a specific MINT implementation are fixed, it is recommended to define JNDI data sources instead of JDBC ones. However, a JNDI data source has to be defined directly on the server and thus has to be set up by the global MINT administrator. Therefore, the creation of a JNDI data source has to be requested to the [[Management Consulting Team\|GICHD IM ~~focal point~~]], and the following information has to be provided:		Once the data sources for a specific MINT implementation are fixed, it is recommended to define JNDI data sources instead of JDBC ones. However, a JNDI data source has to be defined directly on the server and thus has to be set up by the global MINT administrator. Therefore, the creation of a JNDI data source has to be requested to the [[Management Consulting Team\|GICHD IM advisor]], and the following information has to be provided:
	<ul>		<ul>
	<li>'''Name:''' name that allows identifying the data source</li>		<li>'''Name:''' name that allows identifying the data source</li>

Dionysia at 15:55, 7 October 2014

2014-10-07T15:55:56Z

← Older revision		Revision as of 17:55, 7 October 2014
Line 78:		Line 78:
	A virtual data source is a combination of two or more other data sources. Therefore, the existence of other data sources (typically JDBC and/or JNDI) is a prerequisite. To define a virtual data source, choose '''Virtual Data Source''' in the drop-down menu of the Add Data Source page. The following page appears.		A virtual data source is a combination of two or more other data sources. Therefore, the existence of other data sources (typically JDBC and/or JNDI) is a prerequisite. To define a virtual data source, choose '''Virtual Data Source''' in the drop-down menu of the Add Data Source page. The following page appears.
	[[File:MINT_add_data_source_Virtual.png\|center]]		[[File:MINT_add_data_source_Virtual.png\|center]]
	As for other data sources, a name, ID, optional description and a repository location have to be provided. Then, the lower pane allows choosing several data sources from previously defined ones. Choose two or more data sources that need to be analyzed together. When creating a [[~~Create~~ MINT Domains\|domain]] selected tables of these different data sources can then be joined.		As for other data sources, a name, ID, optional description and a repository location have to be provided. Then, the lower pane allows choosing several data sources from previously defined ones. Choose two or more data sources that need to be analyzed together. When creating a [[Creating MINT Domains\|domain]] selected tables of these different data sources can then be joined.
	A virtual data source is particularly useful if there is the need to combine an IMSMA staging area with another database that contains additional data, e.g. on socioeconomic figures. The prerequisite though is the existence of a common key between the data sets.		A virtual data source is particularly useful if there is the need to combine an IMSMA staging area with another database that contains additional data, e.g. on socioeconomic figures. The prerequisite though is the existence of a common key between the data sets.
	</onlyinclude>		</onlyinclude>
	{{NavBox Business Intelligence}}		{{NavBox Business Intelligence}}
	[[Category:VIE]]		[[Category:VIE]]

Dionysia at 15:53, 7 October 2014

2014-10-07T15:53:48Z

← Older revision		Revision as of 17:53, 7 October 2014
Line 11:		Line 11:
	<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed. In both MINT and lightMINT, drivers for Postgres and MySQL are included, others might need to be installed on request.</li>		<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed. In both MINT and lightMINT, drivers for Postgres and MySQL are included, others might need to be installed on request.</li>
	<li>'''JNDI data source:''' Java Naming and Directory Interface (JNDI) is also a Java-based technology to connect to and query data. It is defined directly on the (MINT/lightMINT) server, centrally and only once. The advantages over a JDBC connection are in maintainability and performance - JNDI manages pools of connections instead of opening many separate connections on the database if several processes are accessing the data simultaneously.</li>		<li>'''JNDI data source:''' Java Naming and Directory Interface (JNDI) is also a Java-based technology to connect to and query data. It is defined directly on the (MINT/lightMINT) server, centrally and only once. The advantages over a JDBC connection are in maintainability and performance - JNDI manages pools of connections instead of opening many separate connections on the database if several processes are accessing the data simultaneously.</li>
	<li>'''Virtual data source:''' this type of data source allows combining multiple JDBC and JNDI data sources in order to make them available through a [[Creating Domains\|domain]]. This is very useful if several databases/data sources, e.g. IMSMA and an additional source, need to be analyzed together. In such a case, it is crucial though to identify a common key that allows joining the data sets.</li>		<li>'''Virtual data source:''' this type of data source allows combining multiple JDBC and JNDI data sources in order to make them available through a [[Creating MINT Domains\|domain]]. This is very useful if several databases/data sources, e.g. IMSMA and an additional source, need to be analyzed together. In such a case, it is crucial though to identify a common key that allows joining the data sets.</li>
	</ul>		</ul>
	== Create a data source ==__NOEDITSECTION__		== Create a data source ==__NOEDITSECTION__

Dionysia at 15:53, 7 October 2014

2014-10-07T15:53:16Z

← Older revision		Revision as of 17:53, 7 October 2014
Line 78:		Line 78:
	A virtual data source is a combination of two or more other data sources. Therefore, the existence of other data sources (typically JDBC and/or JNDI) is a prerequisite. To define a virtual data source, choose '''Virtual Data Source''' in the drop-down menu of the Add Data Source page. The following page appears.		A virtual data source is a combination of two or more other data sources. Therefore, the existence of other data sources (typically JDBC and/or JNDI) is a prerequisite. To define a virtual data source, choose '''Virtual Data Source''' in the drop-down menu of the Add Data Source page. The following page appears.
	[[File:MINT_add_data_source_Virtual.png\|center]]		[[File:MINT_add_data_source_Virtual.png\|center]]
	As for other data sources, a name, ID, optional description and a repository location have to be provided. Then, the lower pane allows choosing several data sources from previously defined ones. Choose two or more data sources that need to be analyzed together. When creating a [[Create Domains\|domain]] selected tables of these different data sources can then be joined.		As for other data sources, a name, ID, optional description and a repository location have to be provided. Then, the lower pane allows choosing several data sources from previously defined ones. Choose two or more data sources that need to be analyzed together. When creating a [[Create MINT Domains\|domain]] selected tables of these different data sources can then be joined.
	A virtual data source is particularly useful if there is the need to combine an IMSMA staging area with another database that contains additional data, e.g. on socioeconomic figures. The prerequisite though is the existence of a common key between the data sets.		A virtual data source is particularly useful if there is the need to combine an IMSMA staging area with another database that contains additional data, e.g. on socioeconomic figures. The prerequisite though is the existence of a common key between the data sets.
	</onlyinclude>		</onlyinclude>
	{{NavBox Business Intelligence}}		{{NavBox Business Intelligence}}
	[[Category:VIE]]		[[Category:VIE]]

← Older revision		Revision as of 15:36, 6 January 2017
Line 9:		Line 9:
	There are different types of data sources. The most common ones to be defined in MINT are the following:		There are different types of data sources. The most common ones to be defined in MINT are the following:
	<ul>		<ul>
	<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed. ~~In both MINT and lightMINT, drivers~~ for Postgres and MySQL are included, others might need to be installed on request.</li>		<li>'''JDBC data source:''' Java Database Connectivity (JDBC) is a Java-based data access technology. It allows access to relational databases, such as Postgres, MySQL, etc. For each database technology, a specific driver is needed.Drivers for Postgres and MySQL are included in MINT, others might need to be installed on request.</li>
	<li>'''JNDI data source:''' Java Naming and Directory Interface (JNDI) is also a Java-based technology to connect to and query data. It is defined directly on the (MINT~~/lightMINT)~~ server, centrally and only once. The advantages over a JDBC connection are in maintainability and performance - JNDI manages pools of connections instead of opening many separate connections on the database if several processes are accessing the data simultaneously.</li>		<li>'''JNDI data source:''' Java Naming and Directory Interface (JNDI) is also a Java-based technology to connect to and query data. It is defined directly on the MINT server, centrally and only once. The advantages over a JDBC connection are in maintainability and performance - JNDI manages pools of connections instead of opening many separate connections on the database if several processes are accessing the data simultaneously.</li>
	<li>'''Virtual data source:''' this type of data source allows combining multiple JDBC and JNDI data sources in order to make them available through a [[Creating MINT Domains\|domain]]. This is very useful if several databases/data sources, e.g. IMSMA and an additional source, need to be analyzed together. In such a case, it is crucial though to identify a common key that allows joining the data sets.</li>		<li>'''Virtual data source:''' this type of data source allows combining multiple JDBC and JNDI data sources in order to make them available through a [[Creating MINT Domains\|domain]]. This is very useful if several databases/data sources, e.g. IMSMA and an additional source, need to be analyzed together. In such a case, it is crucial though to identify a common key that allows joining the data sets.</li>
	</ul>		</ul>
Line 17:		Line 17:
	There are two easy ways of creating a data source:		There are two easy ways of creating a data source:
	<ol>		<ol>
	<li>~~In MINT, in the top menu, click~~ on '''Create → Data Source'''</li>		<li>Click on '''Create → Data Source'''</li>
	<li>~~In MINT and lightMINT: right~~-click on the folder in which the data source should be stored, and choose '''Add Resource → Data Source'''</li>		<li>Right-click on the folder in which the data source should be stored, and choose '''Add Resource → Data Source'''</li>
	</ol>		</ol>
	[[File:MINT_add_data_source.png\|center]]		[[File:MINT_add_data_source.png\|center]]
Line 37:		Line 37:
	<li>'''Database:''' name of the database to connect to, e.g. staging.</li>		<li>'''Database:''' name of the database to connect to, e.g. staging.</li>
	<li>'''URL:''' this is the full URL connection to the database. It is filled automatically, in the right syntax, with the information entered above (host, port, database).</li>		<li>'''URL:''' this is the full URL connection to the database. It is filled automatically, in the right syntax, with the information entered above (host, port, database).</li>
	<li>'''User Name:''' name of a database user that can connect to the database. For example, the user imsma can usually connect to the staging area. It is recommended though to define a read-only user on the database and use this one to connect ~~with~~ MINT~~/lightMINT~~.</li>		<li>'''User Name:''' name of a database user that can connect to the database. For example, the user imsma can usually connect to the staging area. It is recommended though to define a read-only user on the database and use this one to connect from MINT.</li>
	<li>'''Password:''' password of the above defined database user.</li>		<li>'''Password:''' password of the above defined database user.</li>
	<li>'''Time Zone:''' leave the default (Use database setting) - the time zone of the database is then the reference time zone.</li>		<li>'''Time Zone:''' leave the default (Use database setting) - the time zone of the database is then the reference time zone.</li>
Line 55:		Line 55:
	<li>'''Port:''' port on which the database is running on the host defined above. The default port number for Postgres is 5432.</li>		<li>'''Port:''' port on which the database is running on the host defined above. The default port number for Postgres is 5432.</li>
	<li>'''Database:''' name of the database to connect to, e.g. staging.</li>		<li>'''Database:''' name of the database to connect to, e.g. staging.</li>
	<li>'''User Name:''' name of a database user that can connect to the database. For example, the user imsma can usually connect to the staging area. It is recommended though to define a read-only user on the database and use this one to connect ~~with~~ MINT~~/lightMINT~~.</li>		<li>'''User Name:''' name of a database user that can connect to the database. For example, the user imsma can usually connect to the staging area. It is recommended though to define a read-only user on the database and use this one to connect from MINT.</li>
	<li>'''Password:''' password of the above defined database user.</li>		<li>'''Password:''' password of the above defined database user.</li>
	</ul>		</ul>