on 07-22-2015 7:10 AM
Hello Experts,
Has anyone worked on the Alert consumer Job called "AlertConsumerJobV2". This has a description "Simple alert consuming solution for generation of emails. Enhances and replaces the job AlertConsumerJob. It offers additional parameters and the possibility to use an email template.".
It says that you can use template for alert email. If anyone worked, can you please share the steps? Thanks in advance.
Regards,
Arijit
Hi,
Check Configuring a Local Consumer on AS Java - Administering Process Integration (PI) - SAP Library and more specifically the part about the additional parameters. All necessary information is available.
Kind regards,
Dimitri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Dimitri, That is what I was wondering that whether we need to use the same User Defined Message Search config to get the value in variable used in template or not. So basically we need use the name of the criteria as the variable in the email template. In my case if the criteria name is AccountNumber(which I configured using User-Defined Message Search Configuration), the email template should have the variable as $AccountNumber$ to get the value of AccountNumber for that interface.
Please let me know if I am wrong.Thanks for your help!!
Regards
Arijit
Dear Dimitri,
I have tested but the "$uds_attributes$:" is still not working.
I created user defined search.
I tested that and it works
Now I maintained UDS attribute in the email template like below.
UDS attributes: $SearchName$
However while the email is generated for a failure, the valuer for the UDS attribute is not coming. but all other details are looking good.
Any idea and help would be much appreciated.
Thanks
Arijit
Dear Dimitri,
I already had a look into that and followed the steps. Also as you can see from above screen shots that my UDS configuration is working in message monitoring. But while I use that UDS search criteria in email template then it is unable to pick the value. Any other thoughts??
Thanks,
Arijit
PFB the text from my template file
The Message ID for the failed message is $msg_id$ . You can check the failed message here : $monitoring_url$
PFB the more details for the failed message.
Error Details:
[Severity : $severity$]
[Internal ID : $alert_rule_id$]
[Alert Rule name : $alert_rule_name$]
[Alert creation time : $timestamp$]
[PI Component : $pi_component$]
[ICO/iFlow ID : $scenario_id$]
[Scenario Name : $scenario_name$]
[Error Category : $error_category$]
[Error Code : $error_code$]
[Error Label : $error_label$]
[Error Text : $error_text$]
[Additional Error Parameters : $error_parameters$]
[Message ID : $msg_id$]
[Sender Party : $msg_from_party$]
[Sender Component : $msg_from_component$]
[Receiver Party : $msg_to_party$]
[Receiver Component : $msg_to_component$]
[Interface Name : $msg_interface$]
[Interface Namespace : $msg_interface_namespace$]
[User Defined Data : $uds_attributes$]
[Adapter Type : $adapter_type$]
[Adapter Namespace : $adapter_namespace$]
[Communication Channel name : $channel_name$]
[Comm Channel Party Name : $channel_party$]
[Comm Channel Component Name : $channel_component$]
[Message Monitoring URL : $monitoring_url$]
[Message Monitoring URL : $secure_monitoring_url$]
yes i think that is wrong....because in the Note i didn't see any place where they have mentioned to use the filter name as the value.
This template will be common for all the Alert rules, so suppose you have 5 interfaces and all have different UDS values defined. How will your value work as you are mentioning UDS filter value of only one interface in the template.
use this value in template.
[User Defined Data : $uds_attributes$]
$uds_attribute$ is the default value, this will read all the UDS value for the interfaces and print it in the alert mail.
Regards
Osman
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.