Skip to Content

Extension Framework revisited: Input Validation with rhidmo

In this post I’d like to announce rhidmo, a new tool which makes it extremely easy to develop and transport input validations for SAP ID Mgmt user interfaces.

Rhidmo is a J2EE application which implements the Extension Framework API. It uses the free JavaScript interpreter rhino to allow input validation scripts written in JavaScript.

The big advantage of rhidmo is that it removes one of the big drawbacks of the Extension Framework which consists of the fact that if you implement input validations for SAP ID Mgmt you need to write Java code and deploy it on the WebAS Java where the SAP ID Mgmt UI packages have been deployed. For each bugfix, for each additional validation you need to modify the Java code and redeploy it. This is a major headache, not only for companies where the responsibilities of the ID Mgmt system and the WebAS Java machine are in different departments.


With rhidmo, you develop your input validation for the UIs in JavaScript in the SAP ID Mgmt mmc console. Then you register which script is supposed to validate which user interface. Once you have deployed the rhidmo ear file every time you need to change something you just change the corresponding script function. If you want to add a new validation for a new user interface you just write a new script and register it. All changes have immediate effect. No need to redeploy anything. When you transport development from the DEV to the QA system you just do an Identity Center transport. No additional headache about transporting Java binaries, no coordination with other departments in your company.

And here is how it works: When a user hits the save button in a UI rhidmo gets called. With the task id of the user interface that is provided to rhidmo it computes which global script is registered for validation. Then this script is loaded and executed by the JavaScript interpreter. If the script returns a string this string is displayed as error message in the user interface. If it returns nothing this means the input was correct and the control is returned.

Rhidmo is not only easy to deploy and use. In addition, it brings a couple of great features that allow for complex validation scenarios. Rhidmo not only provides a couple of easy methods to retrieve and search objects in the Identity Store, it also provides full access to ABAP and Java backends. This way, you can retrieve information about the lock status of a user or his role assignments from the UI and you don’t need to rely on asynchronous background computation.


Rhidmo is a commercial product by ktechnologies but there is a trial version available you can download for free. The trial version is fully functional. There is a limitation, however. You can only validate one UI at a time. See the recording where I install the rhidmo trial version on an SAP ID Mgmt 7.2 system. When you download rhidmo make sure you also have a look at the examples page and the short reference on the product web site.

In addition to announcing rhidmo I’d like to announce a series about this product here on SAP Developer Network. In my coming posts, learn all about how to do RFC and SPML calls in order to access backend data from the UI validation script, how to use the onLoad hook available in the Extension Framework of SAP ID Mgmt 7.2 and much more.

1 Comment
You must be Logged on to comment or reply to a post.