OIM 11g: Adding a new tag to notification template

Question

Hi:
OIM 11g comes with some pre-defined notification templates, like 'Generated Password Template', 'Reset Password Template'.
You can see those thru the admin console, System Management, Notifications.
I would like to add a new Tag to one of those notifications, like 'Generated Password'. It currently includes the User Login and Password. I would like to include the User Name to the notification Body.
Can I do this?? How can I accomplish this??
I try to edit the template, and in the documentation, they mention the Event Name and Available variables. I don't see this 'Available Variables' to select from when I edit the notification template.
I am using OIM 11g 11.1.1.5.
Thank you for your help..

Answer 1

Modify the OOTB notification Template for including a few extra attributes
-Identify the template and the event type which you want to modify. For example let’s assume we will modify the OOTB ‘Request Creation’, the corresponding xml for this event type is in the following MDS path:
\metadata\iam-features-request\notification\RequestCreationEvent.xml
Note: The path as specified in the OIM11G documentation might be incorrect
-Modify this xml to point to a custom resolver class as follows:
<?xml version='1.0' encoding='UTF-8'?>
<Events xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../notification/metadata/NotificationEvent.xsd">
<EventType name="RequestCreation">
<Resolver class="com.iam.notification.CustomNotificationResolver">
<Param Name="Request" DataType="X2-Entity" EntityName="Request"/>
</Resolver>
</EventType>
</Events>-Import the xml back to the MDS database
-Create a jar (custom resolver class) and a plugin.xml, bundle them up as a zip and register the plug-in using ‘ant/API’s’ as you want
-Modify the OOTB notification templates as required
-Send email to verify if your changes are being reflected
You can create your own customized templates based on the OOTB one but the ‘Resolver Class’ would not be able to pick up this new template because the only purpose of the resolver class is to override a couple of methods (‘getAvailableData’ & ‘getReplacedData’), so that you can add some extra attributes to be read in your template, but the ‘Template Name’ remains the same as it is hard-coded.
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import oracle.iam.notification.impl.NotificationEventResolver;
import oracle.iam.notification.vo.NotificationAttribute;
public class CustomNotificationResolver implements NotificationEventResolver {
     public List<NotificationAttribute> getAvailableData(String eventType, Map<String, Object> params) throws Exception {
          return null;
     public HashMap<String, Object> getReplacedData(String eventType, Map<String, Object> params) throws Exception {
          HashMap<String, Object> resolvedData = new HashMap<String, Object>();
         resolvedData.put("requestId", params.get("RequestId"));
         resolvedData.put("requestType", params.get("RequestType"));
         resolvedData.put("userId", params.get("UserId"));
         resolvedData.put("userName", params.get("Name"));
         resolvedData.put("baseUrl", params.get("BaseURL"));
         resolvedData.put("myCustomField1", "myCustomField1");
         resolvedData.put("myCustomField2", "myCustomField2");
         resolvedData.put("myCustomField3", "myCustomField3");
          return resolvedData;
}Credits to Sunny for coming up with the solution. Since he seems busy, I took the liberty of posting his solution here.
HTH,
BB