MGE-PortalWiki/DeveloperDocumentation - Revision history

Admin: 10 revisions

2011-10-26T06:14:31Z

10 revisions

← Older revision	Revision as of 08:14, 26 October 2011
(No difference)

imported>JomunaChoudhuri at 08:38, 24 August 2005

2005-08-24T08:38:13Z

← Older revision		Revision as of 10:38, 24 August 2005
Line 2:		Line 2:
	= MGE-[[PortalWiki/DeveloperDocumentation]]: =		= MGE-[[PortalWiki/DeveloperDocumentation]]: =

	* [[#Configs.pm\|How / where to set global ~~varialbes~~ for the server]]		* [[#Configs.pm\|How / where to set global variables for the server]]
	* [[#portal.cgi\|look and feel - Overview]]		* [[#portal.cgi\|look and feel - Overview]]
	* [[#project.cgi\|Projects]]		* [[#project.cgi\|Projects]]
Line 8:		Line 8:

	[[Anchor(Configs.pm)]]		[[Anchor(Configs.pm)]]
	== How / where to set global ~~varialbes~~ for the server ==		== How / where to set global variables for the server ==

	Global variables and settings have to be changed in the Configs.pm file in the cgi-bin directory.		Global variables and settings have to be changed in the Configs.pm file in the cgi-bin directory.

imported>KoljaHenckel at 09:33, 2 May 2005

2005-05-02T09:33:29Z

← Older revision		Revision as of 11:33, 2 May 2005
Line 3:		Line 3:

	* [[#Configs.pm\|How / where to set global varialbes for the server]]		* [[#Configs.pm\|How / where to set global varialbes for the server]]
	* [[#project.cgi\|~~How to jump to a selected project~~]]		* [[#portal.cgi\|look and feel - Overview]]
			* [[#project.cgi\|Projects]]
	* [[#portal.cgi\|How to implement new tools]]		* [[#portal.cgi\|How to implement new tools]]

Line 16:		Line 17:

	e.g. the internal servers adresses are different to the external ones, also the internal Blaststorage path is different to the external.		e.g. the internal servers adresses are different to the external ones, also the internal Blaststorage path is different to the external.

			[[Anchor(portal.cgi)]]
			== Look and feel - Overview ==
			The html interface used for the portal is generated by the portal.cgi. This is where the menu bar on the left side is configured and which .pm files or subfunctions give back the desired information on the right side when selecting the menuvalues.

	[[Anchor(project.cgi)]]		[[Anchor(project.cgi)]]
	== How to ~~jump~~ to a selected project ==		== Projects ==

			=== What does project.cgi do? ===

			When logging in at the portal a session is initiallized and a gpms-applicationframe is set.

			With this, the function $app_frm->get_available_projects() gives back alls available projects the user has access to.
			The Projecttypes indicate the different application. With this information project.cgi links to the applications with the special options needed.
			(see below)

			=== How to be linked to a selected project ===

	Project.cgi gets the projectname and the projecttype to give back the correct link and preferencences for the selected application.		Project.cgi gets the projectname and the projecttype to give back the correct link and preferencences for the selected application.

imported>KoljaHenckel at 09:13, 27 April 2005

2005-04-27T09:13:15Z

← Older revision		Revision as of 11:13, 27 April 2005
Line 41:		Line 41:
	To iplement a new tool, the portal.cgi has to be edited:		To iplement a new tool, the portal.cgi has to be edited:

	a new subfunction (e.g. _show_mowse) has to be defined to ~~geive~~ back the html ~~contend~~ of the mowse_web.pm file.		a new subfunction (e.g. _show_mowse) has to be defined to give back the html-content of the mowse_web.pm file.

	Then the tool has to be added in the Tools-section with the call of the new function (for examples have a look in the portal.cgi)		Then the tool has to be added in the Tools-section in portal.cgi with the call of the new function (for examples have a look in the portal.cgi)

imported>KoljaHenckel at 08:45, 27 April 2005

2005-04-27T08:45:12Z

← Older revision		Revision as of 10:45, 27 April 2005
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	MGE-[[PortalWiki/DeveloperDocumentation]]:		= MGE-[[PortalWiki/DeveloperDocumentation]]: =

	* [[#Configs.pm\|How / where to set global varialbes for the server]]		* [[#Configs.pm\|How / where to set global varialbes for the server]]
Line 21:		Line 21:

	Project.cgi gets the projectname and the projecttype to give back the correct link and preferencences for the selected application.		Project.cgi gets the projectname and the projecttype to give back the correct link and preferencences for the selected application.
			Hidden information (like the password and projectname) can be given by using the hidden imput type for forms. (some applications like GenDB-2.2 need to get the password and the username to create a new session, because the passwordfile of the application is a differnt one to the server).

	The projecttype (e.g. SAMS) defines the variables for the links and the cookie name for the applications ($SAMS_LINK and $SAMS_SESSION)		The projecttype (e.g. SAMS) defines the variables for the links and the cookie name for the applications ($SAMS_LINK and $SAMS_SESSION)
	these varibles have to be defined in the Configs.pm, exported there and imported in the project.cgi		these varibles have to be defined in the Configs.pm, exported there and imported in the project.cgi

	Normally the namedeclarations of the projecttypes work fine for that...		Normally the namedeclarations of the projecttypes (SAMS, MircoLIMS, PRODB, EMMAII, GenDB, GPMS.. work fine for that, but ..
	Probelm: ''GenDB-2.2_LINK'' is no correct perlvariable when using strict. !!!		Probelm: ''GenDB-2.2_LINK'' is no correct perlvariable when using strict. !!!
	So in this case the linkname is converted to ''GenDB_2_2_LINK'', session name is converted to ''GenDB_2_2_SESSION''		So in this case the linkname is converted to ''GenDB_2_2_LINK'', session name is converted to ''GenDB_2_2_SESSION''
			''' has to be changed sometime!'''

	[[Anchor(portal.cgi)]]		[[Anchor(portal.cgi)]]

imported>KoljaHenckel at 08:39, 27 April 2005

2005-04-27T08:39:10Z

@@ Line 4: / Line 4: @@
 * [[#Configs.pm|How / where to set global varialbes for the server]]
 * [[#project.cgi|How to jump to a selected project]]
 [[Anchor(Configs.pm)]]
@@ Line 24: / Line 25: @@
 Normally the namedeclarations of the projecttypes work fine for that...
-Probelm: GenDB-2.2_LINK is no correct perlvariable when using strict. !!!
+Probelm: ''GenDB-2.2_LINK'' is no correct perlvariable when using strict. !!!
-So in this case the linkname is converted to"GenDB_2_2_LINK", session name is converted to "GenDB_2_2_SESSION"
+So in this case the linkname is converted to ''GenDB_2_2_LINK'', session name is converted to ''GenDB_2_2_SESSION''

imported>KoljaHenckel at 08:29, 27 April 2005

2005-04-27T08:29:57Z

← Older revision		Revision as of 10:29, 27 April 2005
Line 2:		Line 2:
	MGE-[[PortalWiki/DeveloperDocumentation]]:		MGE-[[PortalWiki/DeveloperDocumentation]]:

	* [[#project.cgi\|~~how~~ to jump to a selected project]]		* [[#Configs.pm\|How / where to set global varialbes for the server]]
			* [[#project.cgi\|How to jump to a selected project]]

			[[Anchor(Configs.pm)]]
			== How / where to set global varialbes for the server ==

			Global variables and settings have to be changed in the Configs.pm file in the cgi-bin directory.

			Things like Directories of the server (template and cgi-bin directories) or special variables ($SAMS_LINK, or $SAMS_SESSION) are defined here. They are exported and have to be imported in scripts where they have to be used.

			''' These variables have to be adjusted for interal and external use!! '''

			e.g. the internal servers adresses are different to the external ones, also the internal Blaststorage path is different to the external.

	[[Anchor(project.cgi)]]		[[Anchor(project.cgi)]]
	== How to jump to a selected project ==		== How to jump to a selected project ==

	~~To project~~.cgi gets the projectname and the projecttype to give back the correct link and preferencences for the selected application.		Project.cgi gets the projectname and the projecttype to give back the correct link and preferencences for the selected application.
	The projecttype (e.g. SAMS) defines the variables for the links and the cookie name for the applications ($SAMS_LINK and $SAMS_SESSION)		The projecttype (e.g. SAMS) defines the variables for the links and the cookie name for the applications ($SAMS_LINK and $SAMS_SESSION)
	these varibles have to be defined in the Configs.pm, exported there and imported in the project.cgi		these varibles have to be defined in the Configs.pm, exported there and imported in the project.cgi
Line 13:		Line 25:
	Normally the namedeclarations of the projecttypes work fine for that...		Normally the namedeclarations of the projecttypes work fine for that...
	Probelm: GenDB-2.2_LINK is no correct perlvariable when using strict. !!!		Probelm: GenDB-2.2_LINK is no correct perlvariable when using strict. !!!
	So in this case the linkname is converted to"~~GenDB22_LINK~~", session name is converted to "~~GenDB22_SESSION~~"		So in this case the linkname is converted to"GenDB_2_2_LINK", session name is converted to "GenDB_2_2_SESSION"

imported>KoljaHenckel at 07:49, 26 April 2005

2005-04-26T07:49:16Z

← Older revision		Revision as of 09:49, 26 April 2005
Line 13:		Line 13:
	Normally the namedeclarations of the projecttypes work fine for that...		Normally the namedeclarations of the projecttypes work fine for that...
	Probelm: GenDB-2.2_LINK is no correct perlvariable when using strict. !!!		Probelm: GenDB-2.2_LINK is no correct perlvariable when using strict. !!!
	So in this case the linkname is "GenDB22_LINK" session name is"GenDB22_SESSION"		So in this case the linkname is converted to"GenDB22_LINK", session name is converted to "GenDB22_SESSION"

imported>KoljaHenckel at 07:48, 26 April 2005

2005-04-26T07:48:48Z

← Older revision		Revision as of 09:48, 26 April 2005
Line 13:		Line 13:
	Normally the namedeclarations of the projecttypes work fine for that...		Normally the namedeclarations of the projecttypes work fine for that...
	Probelm: GenDB-2.2_LINK is no correct perlvariable when using strict. !!!		Probelm: GenDB-2.2_LINK is no correct perlvariable when using strict. !!!
			So in this case the linkname is "GenDB22_LINK" session name is"GenDB22_SESSION"

imported>KoljaHenckel at 07:40, 26 April 2005

2005-04-26T07:40:46Z

← Older revision	Revision as of 09:40, 26 April 2005
(No difference)