Search This Blog

Saturday, February 28, 2009

Generic Technology Connector(GTC)

INTRODUCTION

Using Oracle Identity Manager, custom connector are created which is known as Generic Technology Connector, which is not dependant on API’s which are supported by target systems and the data repository type and schema in which identity data is stored by target systems.


BUSINESS CHALLENGES


Provisioning solution has gained popularity in the IT industry and most companies have successfully deployed Oracle’s Identity Manager for managing provisioning. Most complicated part of deploying a solution is creating the connectors which allow the provisioning system to integrate with the managed target systems. Oracle has many pre-defined connectors for OIM that are designed for target systems such as MS Active Directory. But for applications that are not supported out of the box such as custom Web Services, Generic Technology connectors can be used to integrate Oracle identity Manager and Target Systems. Oracle’s GTC technology focuses on communication with any trusted or target resource using standard protocols such as FTP, SMTP, HTTP and generic message formats such as SPML, WS-SPML, CSV, LDIF.

For example, when a person enters a Organization, his/her information is stored in HR System. In the Organization environment, multiple trusted sources for storing and creating user identities exist. The Identity Management Solution must have the ability to update the same common attributes from different sources depending on changes in the status of a person. When a person shifts to from a company within the same group of companies the authoritative source for Common Attributes may switch from HR system of one company to other company’s HR system.The Generic Technology Connector can be easily re-configured to change its authoritative source correspondingly, so that the employee data in the Identity Management System remains current.


General Architecture Overview of Generic Technology Connector






Features of Generic Technology Connectors


1.A generic technology connector acts as the bridge for reconciliation and provisioning operations between Oracle Identity Manager and a target system.

2.The reconciliation and provisioning modules of a generic technology connector are composed of reusable components that you select. Each component performs a specific function during provisioning or reconciliation.


Features Specific to the Reconciliation Module


1.Trusted Source Reconciliation
2.User Account Status Reconciliation
3.Full and Incremental Reconciliation
4.Batched Reconciliation
5.Reconciliation of Multi valued Attribute Data (Child Data) Deletion
6.Failure Threshold for Stopping Reconciliation

Other Features

The following features are not specific to the reconciliation or provisioning module:
1.Custom Data Fields and Field Mappings
2.Custom Providers
3.Multilanguage Support
4.Custom Date Formats
5.Propagation of Changes in OIM User Attributes to Target Systems

Conclusion

Oracle’s Generic Technology Connector aims at quick and easy design of Custom connectors to systems that are difficult to integrate in a short time. This improves the overall deployment time for a business application, by reducing the effort spent on the user management piece, thus reducing the time-to-market and increase in revenues from the corresponding application.




Wednesday, February 11, 2009

OIM 9.1.0.1 on JBOSS 4.2.3GA javax.security.auth.login.LoginException: java.lang.NoSuchFieldError

ERROR,11 Feb 2009 15:39:42,453,[XELLERATE.JBOSSLOGINHANDLER],Error in creating l
ogin context
javax.security.auth.login.LoginException: java.lang.NoSuchFieldError: TRACE
at org.jboss.logging.Log4jLoggerPlugin.isTraceEnabled(Log4jLoggerPlugin.
java:85)
at org.jboss.logging.Logger.isTraceEnabled(Logger.java:122)
at org.jboss.security.ClientLoginModule.initialize(ClientLoginModule.jav
a:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:756)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:1
86)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:6
80)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at Thor.API.Security.LoginHandler.jbossLoginHandler.login(Unknown Source
)
at Thor.API.Security.ClientLoginUtility.login(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.internalLogin(Unknown Source)

at com.thortech.xl.client.base.tcAppWindow.login(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.(Unknown Source)
at com.thortech.xl.client.base.tcAppWindow.main(Unknown Source)



Solution:

vBackup the original file log4j-1.2.8.jar in oimclient/xlclient/ext

copy the log4j.jar from JBOSS folder - JBOSS/server/default

Paste the file in client folder with original log4j-1.2.8.jar

Rename log4j.jar file to log4j-1.2.8.jar

start ur JBOSS.. this shd work.