Changes between Version 17 and Version 18 of Documentation/Manuals/ARCNativeAPELClients

Timestamp:

Sep 24, 2013 8:13:31 AM (11 years ago)

Author:

Andrii Salnikov

Comment:

--

Documentation/Manuals/ARCNativeAPELClients

@@ -150 +150 @@
 }}}
 
-You can start with "testing" APEL server and open a GGUS ticket to verify if everything is OK. But once the solution will be verified for one site, another sites can go to production using the standard operations procedure:
- - declare "gLite-APEL" endpoing in GOCDB for grid-site
- - use PROD brockers from BDII
- - check ​http://goc-accounting.grid-support.ac.uk/rss/GOCBD-SITE-NAME_Sync.html and ​http://goc-accounting.grid-support.ac.uk/rss/GOCBD-SITE-NAME_Pub.html in a few days.
-
 ''4.'' Finally you need to create a CRON job to parse logs and sent records regularly. It can be simply {{{/etc/cron.daily/apel}}} that contains:
 {{{
@@ -162 +157 @@
 /usr/bin/apelclient
 }}}
+
+== Operational part to publish data to PROD Network ==
+
+ - declare "gLite-APEL" endpoing in GOCDB for grid-site (this step will add an endpoint DN to APEL's white-list and allows to  publish records)
+ - use PROD brockers received from Top-BDII in SSM configuration (see above)
+ - check that data appeared in EGI accounting database: http://accounting.egi.eu/egi.php?ExecutingSite=GOCBD-SITE-NAME
+ - enable monitoring of EGI accounting database for your grid-site with Nagios tests: declare "APEL" endpoint in GOCDB
+ - Nagios check results will be browsable in a few days using URLs: ​http://goc-accounting.grid-support.ac.uk/rss/GOCBD-SITE-NAME_Sync.html and ​http://goc-accounting.grid-support.ac.uk/rss/GOCBD-SITE-NAME_Pub.html
+ - expect to see APEL "OK" green box on EGI Dashboard
+
+To speed-up the process you can declare "APEL" and "gLite-APEL" endpoints simultaneously.
 
 == Compat version of logger for older ARC CE versions ==