I am seeing error while provisioning to DBUM connector
org.identityconnectors.framework.impl.api.local.ConnectorPoolManager getPool2
INFO: Creating new pool: ConnectorKey( bundleName=org.identityconnectors.dbum bundleVersion=12.3.0 connectorName=org.identityconnectors.dbum.DBUMConnector )
org.identityconnectors.dbum.DBUMConnector init
INFO: Connection Properties are {integratedSecurity=true, database=QPulse6Training}
org.identityconnectors.framework.server.impl.ConnectionListener processOperationRequest
SEVERE: com/microsoft/sqlserver/jdbc/SQLServerDriver has been compiled by a more recent version of the Java Runtime (class file version 60.0), this version of the Java Runtime only recognizes class file versions up to 52.0
java.lang.UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver has been compiled by a more recent version of the Java Runtime (class file version 60.0), this version of the Java Runtime only recognizes class file versions up to 52.0
INFO: Creating new pool: ConnectorKey( bundleName=org.identityconnectors.dbum bundleVersion=12.3.0 connectorName=org.identityconnectors.dbum.DBUMConnector )
org.identityconnectors.dbum.DBUMConnector init
INFO: Connection Properties are {integratedSecurity=true, database=QPulse6Training}
org.identityconnectors.framework.server.impl.ConnectionListener processOperationRequest
SEVERE: com/microsoft/sqlserver/jdbc/SQLServerDriver has been compiled by a more recent version of the Java Runtime (class file version 60.0), this version of the Java Runtime only recognizes class file versions up to 52.0
java.lang.UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver has been compiled by a more recent version of the Java Runtime (class file version 60.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Solution:
1) Check the version of the jar required for your target
mssql-jdbc-<latest_version>.jar
Note: check the jdk version for your target and oim.
If you are 11g then the jar must be compatible with jdk1.7 but if you are on 12c then it should be working be jdk1.8. same way check the jdk versions on your connector server and target database.
1) Check the version of the jar required for your target
mssql-jdbc-<latest_version>.jar
Note: check the jdk version for your target and oim.
If you are 11g then the jar must be compatible with jdk1.7 but if you are on 12c then it should be working be jdk1.8. same way check the jdk versions on your connector server and target database.
2) Register this jar on oim server using UploadJars utility
3) Give the reference of this jar in setDomainEnv.sh
POST_CLASSPATH="/opt/oracle/apps/OIM_Middleware/oracle_common/modules/thirdparty/mssql-jdbc-9.4.0.jre8.jar${CLASSPATHSEP}${POST_CLASSPATH}"
export POST_CLASSPATH
4) If you have connector server, make sure you have this latest jar enclosed in the bundle on the connector server as well.