|
Installing GRIN-Global on a Non-Windows Server
|
| bet | 2/4 | | Sana | 21.03.2017 | | Hajmi | 320,5 Kb. | | #963 |
_________________ end of Pete’s message; doc follows:
Background Information
GRIN-Global was designed to primarily run in a Windows environment, but it is possible to have a non-Windows server house a MySQL, PostgreSQL, or Oracle database. However, to do so, you will need to first install GG on a Windows-based PC, and then port the database from the Windows-based PC over to the non-Windows server by backing up the Windows database and restoring it to the non-Windows server.
After porting the database to the non-Windows server, you will then point to the database in its new location with a parameter in the GRIN-Global Admin tool. Follow the detailed steps in this section for this type of installation.
|
The GRIN-Global (GG) system is a 3-tier based system. The three tiers are the: client, middle, and data tiers.
| -
The data tier is the database where the plant genetic resource data is permanently stored – GRIN-Global is designed to handle four database engines: SQL Server, MySQL, Oracle, PostgreSQL. Organizations can implement any one of these as their database engine.
-
The middle tier consists of three sub-components: the GG Public Website, the Search Engine, and Web Services. (Web Services sends and receives data used by any Client Tier application.)
-
The middle tier runs under the IIS web server on a Windows computer.
-
The GG client tier application – the Curator Tool – never talks to the data tier directly, but instead communicates only with the middle tier’s Web Services, using HTML and XML through port 80 on the IIS server. (By using port 80, the CT is very firewall friendly.)
-
Since the middle tier manages the data between the data tier and the client tier ( the Curator Tool), the CT never needs a database connector to the GG database because it never connects directly to that database; instead the CT requests data from the middle tier which in turn uses its database connector to retrieve the data from the remote database (data tier)
|
| |
