The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "APEL/SSM2Configuration"
| Line 18: | Line 18: | ||
In the [messaging] section, instead of: | In the [messaging] section, instead of: | ||
<code> | <code>destination: /queue/ssm2test</code> | ||
you need: | you need: | ||
<code> | <code>destination: /queue/???</code> | ||
== Cloud Accounting == | == Cloud Accounting == | ||
| Line 30: | Line 30: | ||
In the [messaging] section, instead of: | In the [messaging] section, instead of: | ||
<code> | <code>destination: /queue/ssm2test</code> | ||
you need: | you need: | ||
<code> | <code>destination: /queue/???</code> | ||
[[Category:Accounting]] | [[Category:Accounting]] | ||
Revision as of 16:57, 17 January 2013
- Back to APEL/SSM
Configuring SSM 2
The supplied configuration will send messages to the test server CPU accounting SSM.
However, if you need to configure something differently, here are the instructions:
CPU Accounting in Production
This should only be done, once successful testing on the test server has been done. Please contact the APEL team for the setup instructions: APEL-SUPPORT@JISCMAIL.CO.UK
Storage Accounting
This is currently being tested, if you want to send StAR records to the test server you should make the following changes:
Update the configuration file /etc/apel/sender.cfg
In the [messaging] section, instead of:
destination: /queue/ssm2test
you need:
destination: /queue/???
Cloud Accounting
This is currently being tested, if you want to send Cloud Accounting records to the test server you should make the following changes:
Update the configuration file /etc/apel/sender.cfg
In the [messaging] section, instead of:
destination: /queue/ssm2test
you need:
destination: /queue/???