{"id":12078,"date":"2018-11-30T13:43:22","date_gmt":"2018-11-30T12:43:22","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/extend-a-oracle-access-manager-12-2-1-3-with-user-messaging-service\/"},"modified":"2024-09-11T08:50:58","modified_gmt":"2024-09-11T06:50:58","slug":"extend-a-oracle-access-manager-12-2-1-3-with-user-messaging-service","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/extend-a-oracle-access-manager-12-2-1-3-with-user-messaging-service\/","title":{"rendered":"Extend a Oracle Access Manager 12.2.1.3 with User Messaging Service"},"content":{"rendered":"

After upgrading a Oracle Access Manager from 11.1.2.3 to 12.2.1.3, one of my customer requested from me to configure the Forget Password feature. This feature requires the User Messaging Service that was part of the SOA software in previous versions. Now it is part of the Oracle Access Manager software and the WebLogic Domain can be extended with the UMS services.<\/p>\n

Extend WebLogic Domain<\/h3>\n

[oracle@vm03 ~]$ cd \/u01\/app\/fmw_oim_12213\/
\n[oracle@vm03 fmw_oim_12213]$ ls
\ncfgtoollogs coherence domain-registry.xml em idm inventory OPatch oracle_common oraInst.loc oui user_projects wlserver
\n[oracle@vm03 fmw_oim_12213]$ cd oracle_common\/common\/bin\/
\n[oracle@vm03 bin]$ .\/config.sh<\/code>
\n\"Conf1\"<\/a>
\nIn the next wizard, we will select the Oracle User Messaging Service Basic template that is a quick start template that defines the managed server, ums_server1, and targets all UMS components to that server.
\n\"Conf2\"<\/a>
\nWe keep the file store persistence store but it should be placed on a shared drive if it is planned to use a UMS WebLogic cluster.
\n\"Conf3\"<\/a>
\nThe OPSS was already configured in the OAM WebLogic Domain, there is noting to change in the two next wizards.
\n\"Conf4\"<\/a>
\n\"conf5\"<\/a>
\nIn the next wizards we get the JDBC connections from the RCU configuration schema.
\n\"conf6\"<\/a>
\n\"conf7\"<\/a>
\nThe UMS repository schema was already installed. The JDBC connections shows correctly and the JDBC connections test went smoothly.
\n\"conf8\"<\/a>
\n\"conf9\"<\/a>
\nWe had no keystore configured
\n\"conf10\"<\/a>
\nWe had to go through the topoligy to configure the UMS server and the UMS cluster.
\n\"conf11\"<\/a>
\nIn the next wizard, the new ums_server1 appeared listening on port 7003. This is the default for all new WebLogic Servers in the configuration wizard. Best is to change it to the default SOA port that is 8001 (it can help avoiding some troubles with hard coded ports in some applications).
\n\"conf12\"<\/a>
\nAs this OAM WebLogic Domain was configured with clusters, I had to create an UMS cluster named ums_cluster.
\n\"conf13\"<\/a>
\nI did not use server templatres neither dynamic servers. Nothing changed in the next two wizards.
\n\"conf14\"<\/a>
\n\"conf15\"<\/a>
\nAssigned the ums_server1 to the ums_cluster moving it from the right panel to the left panel under the ums_cluster.
\n\"conf16\"<\/a>
\nThe coherence cluster existed already in the OAM WebLogic Domain and the machine too. Not changes was done in the next two wizards.
\n\"conf17\"<\/a>
\n\"conf18\"<\/a>
\nThe ums_server1 was attached to the already existing machine moving it from the left panel to the right panel under the existing machine.
\n\"conf19\"<\/a>
\nThe deployments and the services were not changed. No actions was applied on the two next wizards.
\n\"conf20\"<\/a>
\n\"conf21\"<\/a>
\nWe kept the persistence file store file name as it was proposed by default.
\n\"conf22\"<\/a>
\nWe checked the summary and clicked the Update button to extend the OAM WebLogic Domain.
\n\"conf23\"<\/a>
\nAll went smoothly without errors.
\n\"conf24\"<\/a>
\nAfter the Domain has been Extended, it was started. The first time the ums_server1 had to be started manually using the startManagedWebLogic.sh script.<\/p>\n

Configure the UMS email driver.<\/h3>\n

We decided to use mails to send the One Time Pin token to the users requesting to reset their password.<\/p>\n

This configuration has to be done through the Fusion Middleware Enterprise Manager Console.
\n\"EM1\"<\/a>
\nSelect usermessaginserver (ums_server1)
\n\"EM2\"<\/a>
\n\"EM3\"<\/a>
\nAt the bottom of the page, look for the Email driver and click the configure button. The next page allows t create a new Email driver and then to configure it.
\n\"Em4\"<\/a>
\n\"EM5\"<\/a>
\nhere are the parameters that needs to be set for the UMS to be able to send mails.<\/p>\n