Access Keys:
Skip to content (Access Key - 0)

Activity 2.2.1 Tool 1.1 Installation

Workbench Installations

Database and Workbench installers will be separated so that the user first chooses a crop database to be downloaded and installed and then installs or updates the Workbench.

  • One database installer will install a database for a new crop which contains only standard breeding methods, locations and user defined fields. This installer must ask the user to specify a crop and database description and a central administrator.
  • The database installer must be capable of detecting the existence of MySQL in the IBP-CWS system and installing it if it is not found.
  • The installer should detect the existence of previously installed central databases and check whether the downloaded one is a new crop which should be added or a later version for an existing crop which should be updated. (Note we need to add a version number field to the installation table. At the moment the version is carried as a string at the end of the database description.)
  • The database installer should be able to detect whether the Workbench has already been installed and whether it should be updated so that users can avoid downloading the full workbench installer if they do not need it.
  • The Workbench installer should install or update all components of the workbench including the released applications. Each workbench release should carry a version number indicating the schema version, the middleware version and the workbench version. The workbench database should contain a list of version numbers for the included applications, also showing the schemas and middleware version they conform to.
  • The Workbench installer needs to identify the workbench administrator for a new installation or verify the administrator for an updated installation. A new workbench database should be installed for a new installation, but should only be updated for an updated installation.
  • Each application could have its own installer capable of updating only that application in the CWS if necessary

Each Workbench user may be a member of several projects. A Project on the WorkBench specifies the crop which identifies the central (public) data resources that will be accessible to the project. This includes a central GMS database, a central DMS database, a GDMS database. Each project provides access to local (private) data resources. These data resources include a local GMS, DMS, IMS and GDMS. Users are identified by authentication codes (username and password) at the Workbench level and then via automatic sign on for access to specific projects with private data resources. (Private simply means 'requiring authentication for access' and several users may have access to the same private (local) data).

Users assigned to each workbench installation have read-only access to the central databases (or a copies of them) in the workbench data store. They also have different levels of access to local project databases of project for which they are membersw. Information on all local projects is retained in the Workbench database. And information on all local databases in contained in the INSTALLATION table of each Crop Database. A similar table in each local database, contains only information pertaining to the specific local database. Applications are thus able to determine which installation is being opened.

The INSTALLATION Table (INSTLN)

Columns - Long Name (Name) Description Type Length (bytes)
INSTALLATION_NO (INSTALID) Unique number for each installation. 1 for central GMS. Integer 2
ADMIN_USER_ID (ADMIN) USER_ID of the administrator for this installation Integer 2
UPDATE_DATE (UDATE) Date of last central GMS update from this installation Long 4
UPDATE_GID (UGID) Last local germplasm ID updated Long 4
UPDATE_LOCN (ULOCN) Last local location ID updated Long 4
UPDATE_CID (UCID) Last local change ID updated Long 4
UPDATE_NID (UNID) Last local name ID updated Long 4
UPDATE_AID (UAID) Last local attribute ID updated Long 4
UPDATE_LDID (ULDID) Last local location descriptor updated Long 4
UPDATE_METHN (UMETHN) Last local method ID updated Integer 2
UPDATE_FLDNO (UFLDNO) Last local user field ID updated Integer 2
UPDATE_REFNO (UREFNO) Last local reference ID updated Integer 2
UPDATE_PERSONID (UPID) Last Person ID updated Long 4
UPDATE_LISTID (ULISTID) Last List ID updated Long 4
INSTALLATION_DES (IDESC) Description of the installation Text 255
DMS_STATUS (DMS_STATUS) Zero unless the local DMS is being updated in which case it is one. Long 4
UPDATE_LRECID (ULRECID) Last LRECID updated Long 4

Administration

Configuration

Adaptavist Theme Builder (3.3.3-conf210) Powered by Atlassian Confluence 2.10.3, the Enterprise Wiki.
Free theme builder license