change the ‘req’ with ‘this.getRequestState()’ and it is possible to compile the code.

You are absolutely right. I would suspect it is supposed to be the HttpServletRequest or the IdM specific req variable coming from the JSP. The GenericEditForm doesn’t decalare this field? I guess obviously not since your code doesn’t compile, but this was written for Sun IdM 8.0… Sorry I included such a bad variable name that even I as the author can’t tell you what it is. As for how you can fix this problem, you’d have to look into what type of argument the GenericViewSource constructor expects.

Unfortunately, I don’t have my old IdM code lying around anymore, though, and even left the IdM world about a year ago — with no plans of going back.

In the createViewSource method in class MyCustomForm there is a, seemingly unknown, identifier ‘req’. The code does not compile because of this. How can I fix the code?

Best Regards,
Anders

Thanks for this helpful article. I would really appreciate if you could help me on achieving following requirement:

I have few custom extended attributes in SIM like groupname, endpointname and I have a custom java resource adapter configured on SIM 7.1. What I am doing is that I am trying to fetch value of these extended attributes in my custom java resource adapter and provision resource with these values.

For the first time, while creating the user and assigning the custom java resource adapter in SIM, I am able to retrieve value of my extended attributes using following function:
public WSUser getUser(WSUser user) {
WSuser user;
user.getAttributeValue(“groupname”);
}
and provision the user in the resource.

However, when I again click on the user, I am getting null value. It seems to me that only while submitting the form, I am able to retrieve the value. I have tried various others methods also but none of them worked for me.

I would really appreciate if you could provide me some pointers.

Thanks
Sunny
ajmera.sunny@gmail.com

I have been fighting with “Customizing Forms” for nearly 2 weeks now!

It’s amazing just how SUN’s website offers no help whatsoever! They always talk about WHAT needs to be done. But, they never explain HOW it should be done.

Most of the things I was able to accomplish — I did via trial & error.

I was finally able to modify a User Form, and import it into the IDM instance.

It’s a simple User Form for inputing such details as : firstname, lastname, address, telepghone, etc, etc.

It seems to be working fine.

However, there is one big problem : after inputing the data, I save it without a hassle. But, whenever I try to VIEW or EDIT that user, the form shows up blank.

In other words, I get an empty Form. Most of the data I input has disappeared.

The only fields that still retain their data are : firstname, lastname, email.

I am guessing that the reason why this is so is because : for all the field names, I used the prefix “global” (global.firstname, global.address, etc, etc)

But, probably, IDM does not recognize a fieldname such as : “global.hometelephone”, or “global.height” or “global.weight”

I don’t know if this is important.

If it is, then, somewhere in IDM’s repository, there is a list of all valid field names, all beginning with “global”. And ONLY those field names are acceptable.

Is this the case??

Does anyone have an idea of what my problem is?

Thanks

I def. see the need for a IdM java programming site, and it would probably be a good idea to set up such a thing. But that’s not for me

using custom viewers is the way the IdM creators did most of IdM itself. Unfortunately, the technology is completely undocumented During the last year of implementing SUN IdM-based system, I digged out the way view handlers might be used and I’m completely happy with them. Did you ever thougth of creating a site dedicated specially to “IdM Java programming”, so we and other people can share their experience in the field?

I used your article to build a custom page with IdM 7.1. My form uses the User View with a custom Form and a custom JSP. I built my custom view handler by extending the UserViewer class, but that causes a weird problem.

When using the UserViewer class as a View handler, IDM resolves the Form by itself using the System Configuration (Form configured on the page Configure -> Form and process mapping in IDM Admin). Logged in with a user, it returns the Form with the Form type: endUserChangePassword.

I want to have a custom page returned, so in the method getForm(), like in your example, I do:

formId = “MyCustomForm”;
return super.getForm(vm, view, formId, options);

The result seems to work since my custom form is displayed. However, the “Checkout view” and “Refresh View” steps don’t go through my Form, only the “render HTML”. This method override fails to affect the global behaviour of my form… And so all my Derivation or Expansions set in the form are not executed, which is a huge problem.

Any ideas?! I can provide the necessary code if anybody can help.

Thanks.