gLite > gLite 3.2 > glite-APEL > Update to glite-APEL 3.2.2-0.sl5  



gLite 3.2

glite-APEL - Update to version 3.2.2-0.sl5

Date 07.06.2010
Priority Normal



Introducing glite-APEL in SL5

This is the new version of the APEL publisher, which keeps all functionalities from previous patches. Changes included in this patch are architectural changes, namely:

  • ActiveMQ is used as the new transport mechanism
  • Dependency on R-GMA has been removed
  • New configuration file for ActiveMQ settings

Authentication in the new version is certificate based, and ACLs are built on DNs. In order to publish successfully, please ensure the host certificate DN of your glite-MON is correctly populated in GOCDB.

IMPORTANT: When migrating from a glite-MON (glite 3.1) to this new node, the database must be moved over to the new node following these steps after configuring APEL in the CE(s):

  1. Create a backup of the database in the glite-MON: [glite-mon#] mysqldump -u username -p > mon_backup.sql
  2. Insert the backup into the new glite-APEL node: [glite-apel#] mysql -u username -p < mon_backup.sql
This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #59592 [apel-publisher] The notified size of the RSA key pair is hardcoded

Updated rpms

Name Version Full RPM name Description
bouncycastle-glite 1.42-3.jdk5 bouncycastle-glite-1.42-3.jdk5.noarch.rpm Bouncy Castle Crypto Package for Java
glite-APEL 3.2.2-0.sl5 glite-APEL-3.2.2-0.sl5.x86_64.rpm glite-APEL for version R_3_2_2_0
glite-apel-core 2.0.12-8 glite-apel-core-2.0.12-8.noarch.rpm Core components of the Apel accounting application
glite-apel-publisher 2.0.12-7 glite-apel-publisher-2.0.12-7.noarch.rpm Apel account record publisher
glite-apel-yaim 1.0.1-0 glite-apel-yaim-1.0.1-0.noarch.rpm glite-apel-yaim_R_1_0_1_0
glite-version 3.2.2-1 glite-version-3.2.2-1.noarch.rpm Shows version information for the installed gLite node types
glite-yaim-core 4.0.12-1 glite-yaim-core-4.0.12-1.noarch.rpm YAIM core package

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)