lcmaps_jobrep.mod -vomsdir <path> -certdir <path> [server=<MySQL hostname/dns-name>] [dsn=<DSN-name>] [port=<port nr.>] [driver=<path/file>] [database=<database-name>] [username=<database username>] [password=<database password>] [-jr_config <path/file>]
The Job Repository module collects the user, job and user-mapping information when a job has been assigned to a fabric and handled by LCMAPS. This information is stored into a SQL database. It is essential that this information is kept secure due to the nature of the data it stores.
This will select the Data Source Name (DSN) that has been set in a odbc.ini file. In the odbc.ini file are one or more Database sources described with the needed settings to connect to a database. (Note: also partial connection settings are supported (3rd party support))
specifies the host that has the database to connect to.
specifies the port number on the host to override the default portnumber
specifies the path and filename of the shared object distributed by the MyODBC package. ODBC needs a driver file to know what kind of database it will be connecting to.
specifies the name of the database that has to be connected to. One machine can host several databases. The default name to fill in is: "JobRepository".
specifies the database username that the LCMAPS module must use to authorize itself with.
specifies the database password that the LCMAPS module must use to authorize itself with. (Note: Disadviced to use this in the lcmaps.db file because it is publicly accessable)
The path and file specification leads to the root-only-readable file that should contain the database password (or more things like the username) to prevent that a simple user could comprimse the information that is in the database. There is a specific format for this file. All these database parameters must be semi-colon delimited. The same parameters as states above are used. This means that in the lcmaps.db all these parameters could be in this file. Also that is not really adviced due to practical reasons (shifting of servers for example) then you'll just have to edit one file. The lcmaps.db file in this case. This means that you can mix these parameters as you like between the files. All these parameters are concatinated after each other. When parameters are more then ounce defined the last one in the concatinated string will be effectivly used. (default: /opt/edg/etc/lcmaps/jobrep_config)
This is the same directory as the LCMAPS VOMS Extract module looks at. This where the VO certificates are stored. (default: /etc/grid-security/vomsdir/). Note: this parameter can not be used in the jobrep_config file.
This is the same directory as the LCMAPS VOMS Extract module looks at. This where the user certificates end up (temporarily) (default: /etc/grid-security/certificates/). Note: this parameter can not be used in the jobrep_config file.
Generated on Sun May 29 21:22:13 2005 for lcmaps by
1.3.5