Siebel Connector setup with OIM 9.1

Hi,
I am trying to setup Siebel connector using VM ware images for OIM 9.1 and Siebel 7.8. I followed the document on deploying Siebel connector.I copied connector files. Imported connector xml files, defined IT resource for Siebel.
I ran a simple create test case under running test cases. I copied required jar file, edited global.properties with required values, ran native2ascii command and I get the following error:
E:\oracle\product\OIM9100\xellerate\Siebel\troubleshoot>java -DTproperties=E:\o
racle\product\OIM9100\xellerate\Siebel\troubleshoot\troubleShoot.properties -Dlo
g4j.configuration=file:/E:/oracle/product/OIM9100/xellerate/Siebel/troubleshoot/
log.properties TroubleShootingUtility C
INFO,17 Mar 2008 14:32:17,703,[XL_INTG.TROUBLESHOOTINGUTILITY],sPropertyFileNam
e :E:\oracle\product\OIM9100\xellerate\Siebel\troubleshoot\troubleShoot.properti
es
INFO,17 Mar 2008 14:32:17,843,[XL_INTG.SIEBEL],SIEBEL Create Connection Request
INFO,17 Mar 2008 14:32:17,875,[XL_INTG.SIEBEL],createSiebelConnection(): START
Siebel Connection creation.
<com.siebel.om.sisnapi.i>
<Error><ErrorCode>8235</ErrorCode> <ErrMsg>Hello Request 1 was abandoned after 4
7 ms. Connection: 0 (SBL-JCA-315) </ErrMsg></Error>
</com.siebel.om.sisnapi.i>
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.b(Unknown Source)
at com.siebel.om.conmgr.e.<init>(Unknown Source)
at com.siebel.om.conmgr.d.d(Unknown Source)
at com.siebel.om.om.b.a(Unknown Source)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java)
at com.thortech.xl.integration.siebel.utils.SiebelConnection.createSiebe
lConnection(Unknown Source)
at com.thortech.xl.integration.siebel.utils.XLSiebelUtilities.createSieb
elConnection(Unknown Source)
at com.thortech.xl.integration.siebel.proxy.SiebelProxyEmployeeProvision
Manager.createSiebelConnection(Unknown Source)
at TroubleShootingUtility.main(TroubleShootingUtility.java:110)
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.run(Unknown Source)
at java.lang.Thread.run(Thread.java:534)
[CMGR FATAL] Error: java.net.SocketException: Connection reset connection:0
<com.siebel.om.sisnapi.i>
<Error><ErrorCode>8235</ErrorCode> <ErrMsg>Hello Request 1 was abandoned after 0
ms. Connection: 0 (SBL-JCA-315) </ErrMsg></Error>
</com.siebel.om.sisnapi.i>
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.b(Unknown Source)
at com.siebel.om.conmgr.e.<init>(Unknown Source)
at com.siebel.om.conmgr.d.d(Unknown Source)
at com.siebel.om.om.b.a(Unknown Source)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java)
at com.thortech.xl.integration.siebel.utils.SiebelConnection.createSiebe
lConnection(Unknown Source)
at com.thortech.xl.integration.siebel.utils.XLSiebelUtilities.createSieb
elConnection(Unknown Source)
at com.thortech.xl.integration.siebel.proxy.SiebelProxyEmployeeProvision
Manager.createSiebelConnection(Unknown Source)
at TroubleShootingUtility.main(TroubleShootingUtility.java:110)
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.run(Unknown Source)
at java.lang.Thread.run(Thread.java:534)
[CMGR FATAL] Error: java.net.SocketException: Connection reset connection:0
<com.siebel.om.sisnapi.i>
<Error><ErrorCode>8235</ErrorCode> <ErrMsg>Hello Request 1 was abandoned after 3
1 ms. Connection: 0 (SBL-JCA-315) </ErrMsg></Error>
</com.siebel.om.sisnapi.i>
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.b(Unknown Source)
at com.siebel.om.conmgr.e.<init>(Unknown Source)
at com.siebel.om.conmgr.d.d(Unknown Source)
at com.siebel.om.om.b.a(Unknown Source)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java)
at com.thortech.xl.integration.siebel.utils.SiebelConnection.createSiebe
lConnection(Unknown Source)
at com.thortech.xl.integration.siebel.utils.XLSiebelUtilities.createSieb
elConnection(Unknown Source)
at com.thortech.xl.integration.siebel.proxy.SiebelProxyEmployeeProvision
Manager.createSiebelConnection(Unknown Source)
at TroubleShootingUtility.main(TroubleShootingUtility.java:110)
ERROR,17 Mar 2008 14:32:20,125,[XL_INTG.SIEBEL],createSiebelConnection(): Siebel
Connection Exception:Could not open a session in 4 attempts. {1} (SBL-JCA-200)
ERROR,17 Mar 2008 14:32:20,125,[XL_INTG.SIEBEL],SIEBEL Create Connection Request
BaseException:com.thortech.xl.integration.siebel.exception.BaseException: BaseE
xception: Siebel Connection JDB Exception: Could not open a session in 4 attempt
s. {1} (SBL-JCA-200)
com.thortech.xl.integration.siebel.exception.BaseException: BaseException: Siebe
l Connection JDB Exception: Could not open a session in 4 attempts. {1} (SBL-JCA
-200)
at com.thortech.xl.integration.siebel.proxy.SiebelProxyEmployeeProvision
Manager.createSiebelConnection(Unknown Source)
at TroubleShootingUtility.main(TroubleShootingUtility.java:110)
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.run(Unknown Source)
Any ideas as to why there is a connection error or what to look for to get more information.
Message was edited by:
user615489

Most of the test clients use a configuration file where you need to configure things like Siebel Admin login, server name, etc. In some cases the configuration file contains the name of the OIM it resource where this is configured instead of the actual values.
Have you customized the E:\oracle\product\OIM9100\xellerate\Siebel\troubleshoot\troubleShoot.properties file with values that are relevant for your installation?
Best regards
/M
<disclaimer> I have never used the Siebel connector</disclaimer>

Similar Messages

RSA Authentication Manager connector exception with OIM 9.1.0.2

Hi,
I have installed RSA AM connector 9.1.0.7 on OIM 9.1.0.2 BP18 on Windows Server 2008 R2.
When I run the RSA recon schedule task, I get the following exception:
DEBUG,24 Feb 2012 12:11:13,227,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader:findClass - Data: loading class - Value: org.iscreen.impl.xml.PositionContext
*ERROR,24 Feb 2012 12:11:13,229,[OIMCP.RSAM],====================================================*
*ERROR,24 Feb 2012 12:11:13,229,[OIMCP.RSAM],oracle.iam.connectors.rsaauthmgr.usermgmt.tasks.RSALookupRecon : getGroups : An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
*ERROR,24 Feb 2012 12:11:13,229,[OIMCP.RSAM],====================================================*
*ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],================= Start Stack Trace =======================*
*ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],oracle.iam.connectors.rsaauthmgr.usermgmt.tasks.RSALookupRecon : getGroups*
*ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
*ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],Description : An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
*ERROR,24 Feb 2012 12:11:13,230,[OIMCP.RSAM],org.iscreen.impl.xml.XmlConfigurationException: An error occurred parsing the XML located at com/rsa/admin/SearchGroupsCommand_validators.xml. The location within the file is at /. The following was found that was in error: Unable to load/locate configuration file.*
at org.iscreen.impl.xml.XmlParser.getInput(XmlParser.java:215)
at org.iscreen.impl.xml.XmlParser.parse(XmlParser.java:116)
at org.iscreen.impl.xml.XmlServiceFactory.registerInclude(XmlServiceFactory.java:117)
at org.iscreen.impl.xml.XmlServiceFactory.loadConfig(XmlServiceFactory.java:285)
at org.iscreen.ValidationFactory.buildFactory(ValidationFactory.java:120)
Any idea what may be the issue???
Thanks.

As per given bug it is looking for jars which is missing
have you install connector using deployment manager?? if yes it copy required jars at target location. verify if not there copy jars in Scheduled Task folder.
Check the document if any external jars required and same put at ThirdParty folder

OIM 11.1.1.5.3 vs Siebel Connector log

Hi all,
I have a problem with OIM Siebel connector log file.
More in details: since I patched OIM from the version 11.1.1.5.0 to the 11.1.1.5.3 one (BP03 - patch ID 14891027), the Siebel Connector stops to log its normal operations (except errors).
Obviously I didn't change the Siebel Connector log configuration between two versions.
Here my logging.xml file
<?xml version="1.0" encoding="UTF-8"?>
<logging_configuration>
<log_handlers>
*<log_handler name='console-handler' class='oracle.core.ojdl.logging.ConsoleHandler' formatter='oracle.core.ojdl.weblogic.ConsoleFormatter' level='TRACE:32'/>*
<log_handler name='odl-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-diagnostic.log'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='useThreadName' value='true'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,composite_instance_id,component_instance_id,composite_name,component_name'/>
</log_handler>
<log_handler name='wls-domain' class='oracle.core.ojdl.weblogic.DomainLogHandler' level="WARNING"/>
<log_handler name='owsm-message-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/owsm/msglogging'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name'/>
</log_handler>
<log_handler name='em-log-handler' level='NOTIFICATION:32' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
<log_handler name='em-trc-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.trc'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>

*<log_handler name='siebel' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>*
*<property name='logreader:' value='off'/>*
*<property name='path' value='/var/log/weblogic/siebel-connector.log'/>*
*<property name='format' value='ODL-Text'/>*
*<property name='useThreadName' value='true'/>*
*<property name='locale' value='en'/>*
*<property name='maxFileSize' value='5242880'/>*
*<property name='maxLogSize' value='52428800'/>*
*<property name='encoding' value='UTF-8'/>*
*</log_handler>*


<log_handler name='db-um-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='/var/log/weblogic/oracle-dbum-connector.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>


<log_handler name='gtc-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='/var/log/weblogic/gtc-connector.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>

</log_handlers>
<loggers>
<logger name="" level="WARNING:1">
<handler name="odl-handler"/>
<handler name="wls-domain"/>
<handler name="console-handler"/>
</logger>
<logger name="oracle" level="NOTIFICATION:1"/>
<logger name="oracle.adf"/>
<logger name="oracle.adf.desktopintegration"/>
<logger name="oracle.adf.faces"/>
<logger name="oracle.adf.controller"/>
<logger name="oracle.adfinternal"/>
<logger name="oracle.adfinternal.controller"/>
<logger name="oracle.jbo"/>
<logger name="oracle.adfdt"/>
<logger name="oracle.adfdtinternal"/>
<logger name="oracle.bam"/>
<logger name="oracle.bam.adapter"/>
<logger name="oracle.bam.common"/>
<logger name="oracle.bam.system"/>
<logger name="oracle.bam.middleware"/>
<logger name="oracle.bam.adc.security"/>
<logger name="oracle.bam.common.security"/>
<logger name="oracle.bam.adc.ejb.BamAdcServerBean"/>
<logger name="oracle.bam.reportcache.ejb.ReportCacheServerBean"/>
<logger name="oracle.bam.eventengine.ejb.EventEngineServerBean"/>
<logger name="oracle.bam.ems.ejb.EMSServerBean"/>
<logger name="oracle.bam.adc.api"/>
<logger name="oracle.bam.adc"/>
<logger name="oracle.bam.eventengine"/>
<logger name="oracle.bam.ems"/>
<logger name="oracle.bam.webservices"/>
<logger name="oracle.bam.web"/>
<logger name="oracle.bam.reportcache"/>
<logger name="oracle.bpm"/>
<logger name="oracle.bpm.analytics"/>
<logger name="oracle.integration"/>
<logger name="oracle.integration.platform.blocks.cluster"/>
<logger name="oracle.integration.platform.blocks.deploy.coordinator"/>
<logger name="oracle.integration.platform.blocks.event.saq"/>
<logger name="oracle.integration.platform.blocks.java"/>
<logger name="oracle.integration.platform.faultpolicy"/>
<logger name="oracle.integration.platform.testfwk"/>
<logger name="oracle.soa"/>
<logger name="oracle.soa.adapter"/>
<logger name="oracle.soa.b2b"/>
<logger name="oracle.soa.b2b.apptransport"/>
<logger name="oracle.soa.b2b.engine"/>
<logger name="oracle.soa.b2b.repository"/>
<logger name="oracle.soa.b2b.transport"/>
<logger name="oracle.soa.b2b.ui"/>
<logger name="oracle.soa.bpel"/>
<logger name="oracle.soa.bpel.console"/>
<logger name="oracle.soa.bpel.engine"/>
<logger name="oracle.soa.bpel.engine.activation"/>
<logger name="oracle.soa.bpel.engine.agents"/>
<logger name="oracle.soa.bpel.engine.bpel"/>
<logger name="oracle.soa.bpel.engine.compiler"/>
<logger name="oracle.soa.bpel.engine.data"/>
<logger name="oracle.soa.bpel.engine.delivery"/>
<logger name="oracle.soa.bpel.engine.deployment"/>
<logger name="oracle.soa.bpel.engine.dispatch"/>
<logger name="oracle.soa.bpel.engine.sensor"/>
<logger name="oracle.soa.bpel.engine.translation"/>
<logger name="oracle.soa.bpel.engine.ws"/>
<logger name="oracle.soa.bpel.engine.xml"/>
<logger name="oracle.soa.bpel.entity"/>
<logger name="oracle.soa.bpel.jpa"/>
<logger name="oracle.soa.bpel.system"/>
<logger name="oracle.soa.dvm"/>
<logger name="oracle.soa.management.facade.api"/>
<logger name="oracle.soa.mediator"/>
<logger name="oracle.soa.mediator.common"/>
<logger name="oracle.soa.mediator.common.cache"/>
<logger name="oracle.soa.mediator.common.error"/>
<logger name="oracle.soa.mediator.common.error.recovery"/>
<logger name="oracle.soa.mediator.common.message"/>
<logger name="oracle.soa.mediator.dispatch"/>
<logger name="oracle.soa.mediator.dispatch.resequencer.toplink"/>
<logger name="oracle.soa.mediator.filter"/>
<logger name="oracle.soa.mediator.instance"/>
<logger name="oracle.soa.mediator.management"/>
<logger name="oracle.soa.mediator.metadata"/>
<logger name="oracle.soa.mediator.monitor"/>
<logger name="oracle.soa.mediator.resequencer"/>
<logger name="oracle.soa.mediator.resequencer.besteffort"/>
<logger name="oracle.soa.mediator.resequencer.fifo"/>
<logger name="oracle.soa.mediator.resequencer.standard"/>
<logger name="oracle.soa.mediator.service"/>
<logger name="oracle.soa.mediator.serviceEngine"/>
<logger name="oracle.soa.mediator.transformation"/>
<logger name="oracle.soa.mediator.utils"/>
<logger name="oracle.soa.mediator.validation"/>
<logger name="oracle.soa.scheduler"/>
<logger name="oracle.soa.services.common"/>
<logger name="oracle.soa.services.identity"/>
<logger name="oracle.soa.services.notification"/>
<logger name="oracle.soa.services.rules"/>
<logger name="oracle.soa.services.rules.obrtrace"/>
<logger name="oracle.soa.services.workflow"/>
<logger name="oracle.soa.services.workflow.common"/>
<logger name="oracle.soa.services.workflow.evidence"/>
<logger name="oracle.soa.services.workflow.metadata"/>
<logger name="oracle.soa.services.workflow.persistency"/>
<logger name="oracle.soa.services.workflow.query"/>
<logger name="oracle.soa.services.workflow.report"/>
<logger name="oracle.soa.services.workflow.runtimeconfig"/>
<logger name="oracle.soa.services.workflow.soa"/>
<logger name="oracle.soa.services.workflow.task"/>
<logger name="oracle.soa.services.workflow.task.dispatch"/>
<logger name="oracle.soa.services.workflow.task.routing"/>
<logger name="oracle.soa.services.workflow.user"/>
<logger name="oracle.soa.services.workflow.verification"/>
<logger name="oracle.soa.services.workflow.worklist"/>
<logger name="oracle.soa.services.workflow.performance"/>
<logger name="oracle.soa.services.cmds"/>
<logger name="oracle.soa.wsif"/>
<logger name="oracle.soa.xref"/>
<logger name="oracle.ucs"/>
<logger name="oracle.sdp"/>
<logger name="oracle.sdpinternal"/>
<logger name="oracle.sdp.messaging"/>
<logger name="oracle.sdp.messaging.client"/>
<logger name="oracle.sdp.messaging.driver"/>
<logger name="oracle.sdp.messaging.engine"/>
<logger name="oracle.sdp.messaging.parlayx"/>
<logger name="oracle.sdp.messaging.server"/>
<logger name="oracle.wsm"/>
<logger name="oracle.wsm.msg.logging" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="owsm-message-handler"/>
<handler name="wls-domain"/>
</logger>
<logger name='oracle.sysman' level='NOTIFICATION:32' useParentHandlers='false'>
<handler name='em-log-handler'/>
<handler name='em-trc-handler'/>
</logger>

*<logger name="XL_INTG.SIEBEL" level="TRACE:32" useParentHandlers="false">*
*<handler name="siebel"/>*
*<handler name="console-handler"/>*
*</logger>*


<logger name="Xellerate.Server">
<handler name="console-handler"/>
</logger>
<logger name="Xellerate.Database">
<handler name="console-handler"/>
</logger>
<logger name="Xellerate.AccountManagement">
<handler name="console-handler"/>
</logger>
<logger name="oracle.iam.reconciliation">
<handler name="console-handler"/>
</logger>


<logger name="OIMCP.DBUM" level="TRACE:32" useParentHandlers="false">
<handler name="db-um-handler"/>
<handler name="console-handler"/>
</logger>
<logger name="OIMCP.DBUMCOMMON" level="TRACE:32" useParentHandlers="false">
<handler name="db-um-handler"/>
<handler name="console-handler"/>
</logger>


<logger name="Xellerate.GC.FrameworkReconciliation" level="TRACE:32" useParentHandlers="false">
<handler name="gtc-handler"/>
</logger>
<logger name="Xellerate.GC.Provider.ReconciliationFormat" level="TRACE:32" useParentHandlers="false">
<handler name="gtc-handler"/>
</logger>

</loggers>
</logging_configuration>Can anyone help me, please?
Thanks in advance,
Daniele

I had a liitle progress here. For the missing mandatory fields, once you are done the mapping during the creation of GTC, go to Design Console to add mandatory fields, such as user type which is not available in the creation process of GTC. Please see:
=> http://st-curriculum.oracle.com/obe/fmw/oim/10.1.4/oim/obe12_using_gtc_for_reconciliation/using_the_gtc.htm#t5
Now actually I have exactly the same proplem as this one:
=> Re: Creating GTC in OIM 11g (11.1.1.3.0)
=> Event Recieved
=> Data Validation Succeded
=> No User Match Found
=> Creation Faild
=> Notes: ORA Error Code =>ORA-01400: cannot insert NULL into () ORA Error Stack =>ORA-06512: at DEV_OIM.OIM_SP_RECONBLKUSERCRUD", line 722
I am looking into this, will keep you posted.
Ningfeng

Remedy connector not working with OIM 9.1.0.2

Hi,
I am using the OIM connector, BMC Remedy User Management 9.0.4.12 with OIM 9.1.0.2 BP18 on Weblogic 10.3.2
I have followed the connecter documentation at "http://docs.oracle.com/cd/E11223_01/doc.904/e10422/deploy.htm#BGBIFBHG".
The connecter is installed successfully. The dependency files are placed in the directories as per section 2.3 of the above note. And the Communication between Remedy server and OIM is not SSL.
When I run the schedule task for “Remedy Lookup Reconciliation”, I get the error. I have checked that all the dependencies are in the correct location and the path variables are set properly:
DEBUG,29 Feb 2012 15:03:28,092,[XELLERATE.SERVER],Class/Method: SchedulerTaskLocater /removeLocalTask entered.
DEBUG,29 Feb 2012 15:03:28,092,[XELLERATE.SERVER],Class/Method: SchedulerTaskLocater /removeLocalTask left.
Exception in thread "QuartzWorkerThread-0" java.lang.NoClassDefFoundError: Could not initialize class com.remedy.arsys.api.Proxy
at com.remedy.arsys.api.DefaultProxyManager.getProxy(DefaultProxyManager.java:60)
at com.remedy.arsys.api.Util.ARSetServerPort(Util.java:1461)
at com.thortech.xl.schedule.hostAccess.ReconcileBMCLookUp.connect(Unknown Source)
at com.thortech.xl.schedule.hostAccess.ReconcileBMCLookUp.getLookUpData(Unknown Source)
at com.thortech.xl.schedule.hostAccess.ReconcileBMCLookUp.execute(Unknown Source)
at com.thortech.xl.scheduler.tasks.SchedulerBaseTask.run(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
DEBUG,29 Feb 2012 15:03:56,337,[XELLERATE.SCHEDULER],Loading Scheduled task class com.thortech.xl.scheduler.core.quartz.QuartzWrapperusing ADP classloader
DEBUG,29 Feb 2012 15:03:56,337,[XELLERATE.ADAPTERS],Class/Method: tcADPClassLoader/getClassLoader entered.
Let me know if you have an idea on what maybe going wrong here..
Thanks.

As per given bug it is looking for jars which is missing
have you install connector using deployment manager?? if yes it copy required jars at target location. verify if not there copy jars in Scheduled Task folder.
Check the document if any external jars required and same put at ThirdParty folder

Configuring ACF2 connector with OIM 11gR2

Hi Experts,
I am working on configuring ACF2 connector with OIM 11gr2, In an intermediatory step we need to copy VOYAGER_ID.properties file. The comment against this file is written as: Rename VOYAGER_ID with the name "Voyager server's VOYAGER_ID control file property".
Can anybody please tell what does this actually mean?
thanks

Rename the copied file to match the VOYAGER_ID property. For example, if the target system has VOYAGER_ID = VOYAGE14, then the .properties file should be named VOYAGE14.properties.
The Voyager reconciliation agent sends a unique identifier value, called VOYAGER_ID, each time a reconciliation event occurs. This value must match the name of the .properties file being used by the topsecret-adv-agent-recon.jar file for reconciliation.

OIM connector compatible with Exchange2010

Hi,
Please let me know if any OOTB Exchange server connector avaialble for OIM which is compatible with Exchange server 2010
Thanks in advance

http://docs.oracle.com/cd/E11223_01/doc.910/e11198/intro.htm#CHDGDDGJ
v9.1.1.7 of connector supports Exchn 2010 on Windows 2003/2008
-Bikash

Existing OIM 11.1.1.5.0 setup with other oracle DB

Hi,
I have OIM 11.1.1.5.0 setup with Oracle Database 11.2.0.1.0 on a RHEL 5.3 machine. It is working fine.
Now I need to point OIM 11.1.1.5.0 with other existing Oracle Database 11.2.0.1.0, which is in another RHEL 5.3 machine.
Is it possible to implement this setup? Please anyone suggest me on this.
Thanks in advance.
Regards,
Karthick Sugumaran

Hi delhi,
Thanks so much. I compledted the setup using the the document "OIM 11gR1: Schema Backup and Restoration using Data Pump Client Utility [ID 1359656.1]" which you have mentioned in the above.
Now I can able to use OIM application using another server Database instead of already existing Database.
Thanks & Regards,
Karthick Sugumaran

OIM Siebel Connector Real-Time

Hi All
I am using the direct provisioning for the OIM Siebel Connector.
Can I make this provisioning process to be a real time without human intervention ?
At the current time, I am adding an LDAP resource and Siebel resource to each user manually to start the provisioning process. Is there anyway to automate this process to remove the human intervention ?
Thanks

You can create a schedule task to initiate provisioning through APIs
Or
Use Access Policy. Whenever user will get created into OIM, he will get Siebel Resource

ESSO PG Connector Issue in OIM 11G

I setup ESSO Provision Gateway Connector in OIM 11G.
But during "add credential task" I get error:
"*The add_credential execution failed. Error: Error in sending instruction from provisioning manager in Api Command (400) Bad Request. Add Credential Command failed to get invoked*".
In Event Log of the Windows Server 2008 with the Provision Gateway I saw:
"*Unexpected end tag. Line 6, position 1015*", "*server cannot clear headers after http headers have been sent*".
It means a syntax error in xml request of connector to web-service of Provision Gateway.
Wireshark shows me sent xml-request:
"<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1">
<wsse:UsernameToken><wsse:Username>cn=adm,o=petro</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">12345678</wsse:Password><wsse:Nonce>QFJ903k1GFWnAoqZ/Npijg==</wsse:Nonce><wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2010-12-07T11:47:02.502Z</wsu:Created></wsse:UsernameToken></wsse:Security></soapenv:Header><soapenv:Body><AddCredential xmlns="http://passlogix.com/UP/"><strRequest><?xml version = '1.0' encoding = 'UTF-8'?>
<addRequest><attributes><attr name="objectclass"><value>urn.oasis.names.tc:SPML:1:0#GenericString</value></attr><attr name="provisioningAgent"><value>Provisioning Agent</value></attr><attr name="ssoUserId"><value>SGP63234</value></attr><attr name="creationTime"><value>2010-12-07 11:47:02.491Z</value></attr><attr name="executionTime"><value>2010-12-07 11:47:02.490Z</value></attr><attr name="applicationId"><value>SAP</value></attr><attr name="userId"><value>EBELOV</value></attr><attr name="description"><value>SAP</value></attr><attr name="password"><value>Q123</value></attr><attr name="thirdField"><value>888</value></attr></attributes></addRequest></strRequest></AddCredential></soapenv:Body></soapenv:Envelope>*</#document>*"
I saved it to xml-file and opened in Internet Explorer and there was error.
Then I decided to watch the view of this request in OIM 9.1.0.2 to compare with request in OIM 11G.
I found out next one:
the main difference was in last tag "*</#document>*".
I take this tag off from xml-file, taken from request of OIM 11G and saved the file.
Edited xml-file was correct.
Is it error in connector or in OIM 11G?How to solve it?Can anyone help me?

Hi!
I get the same error during Add Credential task with the ESSO PG connector in OIM 11g.....
The add_credential execution failed. Error: Error in Sending instruction from the provisioning manager in API Command (400)Bad Request.
com.passlogix.integration.provision.client.CommandInvocationException: Error in Sending instruction from the provisioning manager in API Command (400)Bad Request
Where I can check the xml file?
You could solve the problem?
Thanks in advance!!!

I have to integrate a webservice based resource with OIM 9.1.0.2 ,

I have to integrate a webservice based resource with OIM 9.1.0.2 , weblogic version 10.1.4.3
I have following details for that resource:
1) IP:
2) port :
3) Admin id:
4)password:
5) WSDL:
Please guide me in integrating the resource.

Hi,
You can use the OOTB SPML GTC connector available in OIM, if you already have the target Webservice/WSDL available.

Error configuring Microsoft SQLSERVER 2005 with OIM 9.1.0.1

Hi All,
I was trying to Configure Microsoft SQLSERVER 2005 as a IT Resource with OIM 9.1.0.1. However after completing all the configuration,
When I tried assigning the configured SQLSERVER IT Resource to a User, following error is thrown:
Response: wrong number of arguments
Response Description: Unknown response received
Notes:
*Assigned to User: System Administrator[XELSYSADM]*
Error Details
Setting task status... "wrong number of arguments" does not correspond to a known Response Code. Using "UNKNOWN".
If anyone has encountered this error before, then please help.
Thanks
Sunny
Edited by: ajmerasunny on May 14, 2009 5:57 PM

Are you using the Database User Management connector and trying to provision accounts to a MS SQL Server? Can you also post the logs from the error.
-Kevin

Exchange 11g connector : error with 2003 mailbox databases

Hi,
I have installed the Exchange 11g connector in a OIM 11g R2 server. I successfully ran the "Exchange User Mailbox Database Group Lookup Reconciliation" job and recon-ed a mailbox for a specific user (Exchange 2010 mailbox) account using the "Exchange Target Resource User Reconciliation".
But the fun stops there, when I try the execute the "Exchange Target Resource Delete User Reconciliation" job, I get the following error (see #1) in the result. I don't have any new event in the Event viewer. When I check the connector server I see a similar error (see #2). I tried to manually run the powershell command with the connector server user and it works properly (see #3).
The problem seems to be related the Exchange 2003 mailboxes, since when I try to recon a mailbox for a user with a 2003 mailbox, I get a similar "database not found" error. There again, if I check the same user using the service account, I can get it's mailbox.
Any idea what might be the problem ? Any more debugging I can try ?
Thanks
h4. #1 - In the scheduled task result :
org.identityconnectors.framework.common.exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Couldn't find database "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)". Make sure you have typed it correctly.
at Org.IdentityConnectors.Exchange.RunSpaceInstance.CheckErrors(IList errors)
at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Collection`1 commands)
at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Command item)
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
h4. #2 - In the connector server log :
30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeConnector, Method -> CreateFilterTranslator, Message -> Method Entered
30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> CreateFilterTranslator, Message -> Method Entered
30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeConnector, Method -> ExecuteQuery, Message -> Method Entered
30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> ExecuteQuery, Message -> Method Entered
30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Method entered
30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Returning cmd Get-Mailbox
30/05/2013 10:49:36 AM <INFORMATION>: Class-> ExchangeUtility, Method -> GetCommand, Message -> Exiting the method
30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Method Entered
30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> PowerShell Command: Get-Mailbox
30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: IgnoreDefaultScope Value:
30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: ReadFromDomainController Value:
30/05/2013 10:49:36 AM <INFORMATION>: Class-> PowerShellExchangeServiceImpl, Method -> InvokePipeline, Message -> Parameter: ResultSize Value:Unlimited
ConnectorServer.exe Error: 0 : Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Problem while PowerShell execution Org.IdentityConnectors.Framework.Common.Exceptions.ConnectorException: Couldn't find database "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)". Make sure you have typed it correctly.
at Org.IdentityConnectors.Exchange.RunSpaceInstance.CheckErrors(IList errors)
at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Collection`1 commands)
at Org.IdentityConnectors.Exchange.RunSpaceInstance.InvokePipeline(Command item)
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.InvokePipeline(Command cmd)
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.SearchUser(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options, ObjectClassInfo ocInfo)
at Org.IdentityConnectors.Exchange.Service.Impl.PowerShellExchangeServiceImpl.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options)
at Org.IdentityConnectors.Exchange.ExchangeConnector.ExecuteQuery(ObjectClass oclass, String query, ResultsHandler handler, OperationOptions options)
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(SearchOp`1 search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options)
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.RawSearcherImpl`1.RawSearch(Object search, ObjectClass oclass, Filter filter, ResultsHandler handler, OperationOptions options)
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.SearchImpl.Search(ObjectClass oclass, Filter originalFilter, ResultsHandler handler, OperationOptions options)
at Org.IdentityConnectors.Framework.Impl.Api.Local.Operations.ConnectorAPIOperationRunnerProxy.Invoke(Object proxy, MethodInfo method, Object[] args)
at ___proxy1.Search(ObjectClass , Filter , ResultsHandler , OperationOptions )
at Org.IdentityConnectors.Framework.Impl.Server.ConnectionProcessor.ProcessOperationRequest(OperationRequest request)
DateTime=2013-05-30T14:49:37.1880494Z
h4. #3 - Powershell using the service account
Get a 2003 database
[PS] C:\Windows\system32>Get-MailboxDatabase "ORME-DE-COUR\Premier groupe de stockage\Banque de boîtes aux lettres (ORME-DE-COUR)"
Name Server Recovery ReplicationType
Banque de boîtes aux lettre... ORME-DE-COUR False None
Get a 2003 mailbox
[PS] C:\Windows\system32>Get-Mailbox -Filter "DisplayName -eq 'Marchand Robert 0'"
Name Alias ServerName ProhibitSendQuota
marchanr marchanr orme-de-cour unlimited
Edited by: SG on May 30, 2013 11:57 AM
Edited by: SG on May 30, 2013 1:41 PM

Any update on this? I have the exact same problem...
Thanks,
--jtellier

Target Recon does not link accounts with OIM user

Hi all,
We have developed a custom connector (provisioning and reconciliation connector) to integrate a custom LDAP server.
It is not a trusted source, so, we are performing a target reconciliation.
We have OIM populated with all the users (by a bulk load from a HR resource). Then, when we integrate the LDAP server resource, in the first time reconciliation, we expect that OIM will link LDAP accounts with OIM users, using OIM User ID and LDAP uid attribute for matching.
Our reconciliation connector creates reconciliation events ok, but we always get "not match found" as reconciliation event status.
In the Process Definition we have configured "User ID" as key field, mathed with "User ID" Field of the Resource Object, and uid LDAP attribute.
We have defined all the reconciliation fields in the Resource Objetc.
Why OIM is not matching resource account with OIM users, creating a resource (provisioned resource) for each OIM user?
It seems that OIM is trying to match reconciliation events against already provisioned resources for users, and not against OIM users.
Any ideas?

Hi,
After running bulk loading from the HR resource, all your target Users will get created at OIM. Now if you try to run Target Resource Reconciliation against that LDAP targetfor these records, the first thing OIM will do is to execute the reconciliation rule. After successful matching of this rule OIM will see for Process matching. So try this out after defining a reconciliation rule for your Resource Object with the following rule element values.
User Profile Data - User Login
Operator - Equals
Attribute - uid LDAP attribute *(Primary Field at the target Or the filed against which you want the matching at OIM)*
Transform - None
Object should be Your RO + Rule should be Valid and Active
After this matching you need to have the Reconciliation Action rules in place as well. Check that the following two rules exist:
Go to Resource Object -> Object Reconciliation -> Reconciliation Action Rules
1) One Entity match Found - Establish link \\\\\ *(must for your case)* \\\\\
2) One Process Match Found - Establish link
If not create the rules and Try then.
Regards
Edited by: rajsunny on Jan 27, 2009 4:20 AM

Queries Related with OIM 11g

Hi Experts,
I have few basic queries related with OIM 11.1.1.3
1) Can we use GTC connector to export data of users (Newly created users on daily basis) to CSV file?
I think No, But just wanted to confirm with you guys.
2) The LdapConfig utils in OIM11.1.1.3 provides facility to replicate the users in OID. Like whenever I am creating a user in OIM..Its creating it in OID as well.
My question here is:
a) Since we dont have any process form here so how can i add a new attribute in the data which is getting created in OID through OIM? Like I want to provision a custome attribute along with existing attributes..how will i achieve this?
b) In OIM11.1.1.3, In what scenario we can use OID connector and LdapConfig settings? Like..when to use connector..for provisoning data in OID.
Rajiv,Kevin,Sunny...waiting for ur valuable inputs :)
Regards,
J
Edited by: J_IDM on May 18, 2011 2:56 AM

Thanks Rajiv,
We have process form. We don't have Object Form but we have Request Dataset for that.
But since my OID is configured using LdapConfig and I am not using OID connector. So I dont see any process form associated with my OID.
How can i add new attribute here (Suppose carLicense I need to provision to OID)?
You'll use OID connector when you'll have OID as a target system.
Even I am not using any connector but my users are succesfully created in OID..using OIM 11g.
So I just wanted to know..under what circumstances we should go for LdapConfig(Auto OID user creation) and OID connector in OIM 11g
Thanks very much!!
J

SJSDS recon issue with oim 11g

I got the following logging message while reconciling SJSDS (sun directory server) with oim 11g. All the recon statuses were success (group, role, user, trusted user), but no data was from SJSDS.
Did anyone has any idea about it?
Thanks
John
[2011-06-19T10:01:47.352-05:00] [oim_server1] [NOTIFICATION] [IAM-0080013] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 0000J2cQzfw5qYWFLzfP8A1DzNVx0000A0,0] [APP: oim#11.1.1.3.0] [arg: 194] [arg: 0] [arg: JobDetails] [arg: UPDATE] Kernel executing default validation with process id, event id, entity and operation 194.0.JobDetails.UPDATE
[2011-06-19T10:01:47.376-05:00] [oim_server1] [NOTIFICATION] [IAM-1020024] [oracle.iam.scheduler.impl.quartz] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 0000J2cQzfw5qYWFLzfP8A1DzNVx0000A0,0] [APP: oim#11.1.1.3.0] [arg: 194.242.JobDetails.UPDATE.entityId=null] Execute default action handler with 194.242.JobDetails.UPDATE.entityId=null
[2011-06-19T10:01:47.447-05:00] [oim_server1] [NOTIFICATION] [] [oracle.iam.platform.kernel.dao] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 0000J2cQzfw5qYWFLzfP8A1DzNVx0000A0,0] [APP: oim#11.1.1.3.0] Inserting records for orchestration cleanup
[2011-06-19T10:01:47.475-05:00] [oim_server1] [NOTIFICATION] [IAM-0080046] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 0000J2cQzfw5qYWFLzfP8A1DzNVx0000A0,0] [APP: oim#11.1.1.3.0] [arg: Done] Completed orchestration with action result - Done
[2011-06-19T10:01:47.705-05:00] [oim_server1] [NOTIFICATION] [] [oracle.iam.platform.authz.impl] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: 0000J2cQzfw5qYWFLzfP8A1DzNVx0000A0,0] [APP: oim#11.1.1.3.0] [[
*---Stack Trace Begins[[This is not an exception. For debugging purposes]]---*
oracle.iam.platform.authz.impl.OESAuthzServiceImpl.doCheckAccess(OESAuthzServiceImpl.java:212) oracle.iam.platform.authz.impl.OESAuthzServiceImpl.hasAccess(OESAuthzServiceImpl.java:190)
oracle.iam.platform.authz.impl.OESAuthzServiceImpl.hasAccess(OESAuthzServiceImpl.java:182)
oracle.iam.platform.authz.impl.AuthorizationServiceImpl.hasAccess(AuthorizationServiceImpl.java:173)
oracle.iam.scheduler.impl.util.SchedulerAccessUtils.checkOperationAccess(SchedulerAccessUtils.java:22)
oracle.iam.features.scheduler.agentry.operations.LookupActor.prepare(LookupActor.java:1555)
oracle.iam.features.scheduler.agentry.operations.LookupActor.refresh(LookupActor.java:2969)
oracle.iam.features.scheduler.agentry.operations.LookupActor.receiveEvent(LookupActor.java:2807)
oracle.iam.consoles.faces.mvc.canonic.Model.handleIntent(Model.java:922)
oracle.iam.consoles.faces.mvc.canonic.Controller.doHandleIntent(Controller.java:528)
oracle.iam.consoles.faces.mvc.canonic.Controller.doSelectAction(Controller.java:203)
oracle.iam.consoles.faces.event.NavigationListener.processAction(NavigationListener.java:97)
... 34 lines skipped..
oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmtNavigationFilter.java:115)
... weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:100)
... 15 lines skipped..
weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
---Stack Tracefor this call Ends---
]]

As the log says thats not an exception. Anyway why dont you enable the connector logs and see what does the connector complaint about. Refer the Enable Logging section in the connector PDF
Thanks
SRS

Siebel Connector setup with OIM 9.1

Similar Messages

Maybe you are looking for