Primer: IT Resource Types and IT Resources

IT Resource Types and IT Resources are related, an IT Resource Type defines the template for specific IT Resources. Think of it like a JavaBean with its various member variables and IT Resources as specific instances of that Bean. There are a couple of built-in types, Mail Server for example which provides the template for a specific Mail Server IT Resource that will be used to send various emails.

When importing a connector, you will get the IT Resource Type definition as well as be prompted for the specific values to create an IT Resource.

Each Type may have many specific IT Resources, for example you may have three different OID servers for each of your regional facilities. One Type 'LDAP Server' would provide the base for each of these 3 IT Resources.

Basically IT Resource Types and IT Resources define the physical connection to a specific resource, hostname, passwords, and so on. They are linked with Resource Objects which in conjunction with Resource Process Forms define the details of a managed object on the physical IT Resource, for example user accounts. One provisions a Resource Object on a specific IT Resource.

Primer for Provisioning Flows: Xellerate User/User Defined Fields

So I realized when I first started working with OIM that the documentation is somewhat lacking in detail and does little to help build a conceptual understanding of the how it works. Once you understand it, it is fairly intuitive. Just many moving parts. So I will share what I have learned in the next few posts about the basic flow of information through the system and how stuff works.

OIM/Xellerate User - User Form
The User Form/Xellerate User is the basic record that all entities have within the system. It start with a few basic fields, User ID, Password, First & Last Names, and a few date fields and some others. Like I said, basic. This "Form" is where you build up a profile of your user and the store the various bits of information that define your user and will be used to provision additional resources. The Xellerate User is one of the special 'system' resource objects defined when you install the system. Additional resource objects will be defined as you develop provisioning resources etc. The Xellerate User resource object is similar but slightly different that other resource objects.

You can extend the information you can store on this form by adding User Defined Fields (UDFs) through the design console. Maybe its a telephone number, or a department name, whatever. Add the fields that are appropriate to define your identity.

Within the Web Console, when you edit an user you are editing the User Form and its basic fields and UDFs.

These values are either updated manually through the Web Console, or more commonly updated through a trusted reconciliation process.