MGE-PortalWiki/DeveloperDocumentation: Difference between revisions
imported>KoljaHenckel No edit summary |
imported>KoljaHenckel No edit summary |
||
| Line 2: | Line 2: | ||
MGE-[[PortalWiki/DeveloperDocumentation]]: | MGE-[[PortalWiki/DeveloperDocumentation]]: | ||
* [[#project.cgi| | * [[#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 == | ||
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" | So in this case the linkname is converted to"GenDB_2_2_LINK", session name is converted to "GenDB_2_2_SESSION" | ||
Revision as of 09:29, 27 April 2005
MGE-PortalWiki/DeveloperDocumentation:
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.
How to jump to a selected project
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) 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... 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"