• tomcat (/usr/lib/jvm/java/bin/java -server -Xms128m -Xmx512m -Dglite.log.path=/var/log/cream -Dcatalina.ext.dirs=/usr/share/tomcat5/shared/lib:/usr/share/tomcat5/common/lib -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSource)

• blahpd (/usr/bin/blahpd). This is automatically started by starting tomcat

• resource BDII (/usr/sbin/slapd -f /etc/bdii/bdii-slapd.conf -h ldap://0.0.0.0:2170 -u ldap, /usr/bin/python /usr/sbin/bdii-update -c /etc/bdii/bdii.conf -d)

• gridftp server (/usr/sbin/globus-gridftp-server)

• LB locallogger (/usr/bin/glite-lb-logd, /usr/bin/glite-lb-interlogd)

• mysqld (/usr/libexec/mysqld). Actually mysqld could be deployed and run in another machine different than the CREAM CE)

• new blparser daemons (/usr/bin/BNotifier, /usr/bin/BUpdaterxxx) if the new BLAH blparser is used. They are automatically started by blahpd, which is started by tomcat

• old blparser daemon (xxx) if the old BLAH blparser is used. xxx runs where the batch system log files are available (which can be the CREAM CE node or a different node)

• Init script for resource BDII: /etc/init.d/bdii {start|stop|restart|condrestart|status}

• Init script for old blparser: /etc/init.d/glite-ce-blparser {start|stop|restart|status}

• Init script for new blparser: /etc/init.d/glite-ce-blahparser {start|stop|restart|status}. Actually the new blparser is automatically started by blahpd, which is started by tomcat

• CREAM configuration file (/etc/glite-ce-cream/cream-config.xml). This file is created by yaim-cream-ce. A template is installed as /etc/glite-ce-cream/cream-config.xml.template. An example of this configuration file is available xxx

• BLAH configuration file (/etc/blah.config). This file is created by yaim-cream-ce. A template is installed as /etc/blah.config.template. An example of this configuration file is available xxx

• BLparser configuration file (/etc/blparser.conf) only for the old blparser. This file is created by yaim-cream-ce. A template is installed as /etc/blparser.conf.template). An example of this configuration file is available xxx.

• glexec configuration file (/etc/glexec.conf). This file is created by yaim-cream-ce. An example of this configuration file is available xxx

• LCAS configuration file for glexec (/etc/lcas/lcas-glexec.db). This file is created by yaim-cream-ce. An example of this configuration file is available xxx

• LCMAPS configuration file for glexec (/etc/lcmaps/lcmaps-glexec.db). This file is created by yaim-cream-ce. An example of this configuration file is available xxx

• LCAS configuration file for gridftpd (/etc/lcas/lcas.db). This file is created by yaim-core. An example of this configuration file is available xxx

• LCMAPS configuration file for gridftpd (/etc/lcmaps/lcmaps.db). This file is created by yaim-core. An example of this configuration file is available xxx

• ARGUS configuration file for gridftpd (xxx) only when the CREAM CE is configured to use ARGUS. This file is created by yaim-cream-ce. An example of this configuration file is available xxx

Service Reference Card

Daemons running

The following processes should run on a CREAM CE:

• tomcat5
• blahpd. This is automatically started by starting tomcat
• Resource bdii
• Gridftp server: globus-gridftp
• glite-lb-locallogge: glite-lb-logd and glite-lb-interlogd
• mysqld (actually mysqld could be deployed and run in another machine different than the CREAM CE)
• New blparser daemons (bnotifier and bupdater) if the new BLAH blparser is used
• Old blparser daemon (xxx) if the old BLAH blparser is used. xxx runs where the batch system log files are available (which can be the CREAM CE node or a different node)

* BLAH blparser

This can be started via the /opt/glite/etc/init.d/glite-ce-blparser init script

The BLAH blparser runs where the batch system log files are available (which can be the CREAM CE node or a different node)

Init scripts and options (start|stop|restart|...)

• Init script for tomcat: /etc/init.d/tomcat5 {start|stop|restart|condrestart|try-restart|reload|force-reload|status|version}

• Init script for resource bdii: /etc/init.d/bdii {start|stop|restart|condrestart|status}

• Init script for gridftp server: /etc/init.d/globus-gridftp {start|stop|restart|status}

• Init script for LB locallogger: /opt/glite/etc/init.d/glite-lb-locallogger {start,stop,restart,status}

• Init script for mysql: /etc/init.d/mysqld {start|stop|status|condrestart|restart}

• Init script for old blparser: /opt/glite/etc/init.d/glite-ce-blparser {start|stop|restart|status}

• Init script for new blparser: xxx. Actually the new blparser is automatically started by blahpd, which is started by tomcat

Configuration files location with example or template

Logfile locations (and management) and other useful audit information

Open ports

Possible unit test of the service

Where is service state held (and can it be rebuilt)

Cron jobs

Security information

Access control Mechanism description (authentication & authorization)

How to block/ban a user

Network Usage

Firewall configuration

Security recommendations

Security incompatibilities

List of externals (packages are NOT maintained by Red Hat)

Other security relevant comments

Utility scripts

-- MassimoSgaravatto - 2011-04-07