EDQ Siebel Connector

Hi,
I want to have real time integration of UCM with EDQ. for that I'll be using the Siebel EDQ connector. Can you specify which Integration Objects and Business Services will be used for carrying out real time integration?
Thanks.
Regards,
Zankrut.

As OEDQ does not require any kind of synchronization of data from Siebel to any EDQ tables, we need to disable the DQSync functionality from within Siebel application by making two changes
a. In Siebel UI > Administration - Runtime Events screen > Action Sets view > query for Action Sets with Name = *DQ Sync* > uncheck the Active flag to inactivate all these action sets.
b. In Siebel UI > Administration - Data Quality screen > Data Quality Settings view > set the following parameters and values:
Parameter: Enable DQ Sync
Value: No
Thanks,
Shilpi

Similar Messages

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

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>

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

Returning Nulls in Siebel Connector

Hi
I have a situation where I am trying to cleanse a field and send back a Null (or empty string) from OEDQ (V11.1.1.7.3) to Siebel. Currently this does not seem to work i.e. the original Siebel text remains in the Siebel field and the Null is ignored.
Does anyone know if there is a setting to change this or a workaround (sending a space back works but is not elegant).
Many thanks
Darren

This is due to behaviour of the Siebel DQ interface rather than EDQ.
Sending a space back is the standard way of dealing with this. Siebel does treat this as no value so does not add a space to the field IIRC.

Exclude Matches between records from a Particular Source system EDQ+Siebel UCM

I have a requirement to modify the EDQ-CDS Individual Match processor.
I want to exclude the match between two records (Driver and Candidate) if they have same value in a particular field and i want the Value to be hard-coded or specified as reference Data in EDQ (eg: if both driver and candidate are from same source say 'Source ABC' only then NO MATCH , for all other source records match should happen).
We tried adding Match rule which does the 'Exact Match' comparison on the field 'source' and set the rule to 'NO MATCH' , but this is excluding the matching between records from any system, which is not my requirement. I am only looking to exclude the match when the Source value is say 'Source ABC'.
I think it should be possible with the Comparison type 'In Value' or 'In List ' or 'All in List'. But not sure who to use these comparison rules and there is not much documentation available EDQ online.
Any help on this appreciated.
We are on Siebel 8.2.2.4 + EDQ 11.1.1.7 on Solaris 64 bit.

In List is documented in the 12.1.3 online help. Before this, it was an extension to the product used by CDS.
It is very straight-forward. You add it as a comparison, and create a reference data set with your list of values in it. If the identifier value hits the list, the comparison evaluates to true.
I've pasted most of the help from 12.1.3 below:
Comparison: In List
The In List comparison provides a way of making the application of a Match rule conditional on one or both identifier values in a comparison being matched with a single value or list of values.
Use
Use this comparison as a way to apply a Match rule only to a subset of the data in the Match process. For example:
Where a Match rule is designed to match Middle Eastern names, only apply it if a Country identifier matches a list of Middle Eastern countries.
Where a Match rule is designed to match Electronic products, only apply it if a Product Category identifier matches a single value.
The comparison may also be used to eliminate matches that would otherwise be caught by Match rules lower in the decision table, if used in a Match rule with a 'No Match' result; for example, so that matches on certain rules are only presented if Country or Nationality values are not in a list of safe values.
Options
Option
Type
Purpose
Default Value
Require data in both records?
Yes/No
If Yes, both input identifier values must contain data. If they do not, the comparison will always be 'False'.
If No, only one input identifier value must contain data.
No
Match whole value?
Yes/No
If Yes, the whole identifier value (or values) specified must match.
If No, tokens within the identifier will be matched against the list. In this case, delimiters must be specified in the relevant fields below to determine how to split tokens.
No
Required value reference data
Reference Data
A Reference Data set with a list of values, for example a set of country codes.
Clear
Required value
Free text
A single value to match against. Note that if a Reference Data set and a value is specified, both are matched against.
Clear
Require match for all values?
Yes/No
If Yes, all tokens in the identifier value(s) must match against the required list or value.
If No, any one of the tokens must match.
This option is only used if Match whole value? is set to "No".
No
Delimiter characters reference data
Free text or browse
A Reference Data set with a list of delimiter characters used to tokenize identifier values before matching against the list.
This option is only used if Match whole value? is set to "No".
None
Delimiter characters
Free text
This field is used to specify the delimiter characters to use as an alternative to linking to a Reference Data set.
This option is only used if Match whole value? is set to "No".
Note: If a Reference Data list of delimiters and specific characters are entered here, both are considered delimiter characters.
None

Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.boots

When attempting to create a new Account in siebel integrated with OEDQ the following error occurs.
ERROR
Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.bootstrap.library.path)(SBL-APS-00118)
STEPS
The issue can be reproduced at will with the following steps:
1) from EDQ director we have imported the EDQ_CDS,EDQ-REFERENCE DATA & EDQ_HISTORICAl DATA packages sucessfully.
2) Created dnd.param file in SIebel server SDQCOnnector folder.
3) Copied the libdnd.so file to siebsrvr lib directory(32 bit)
3) In dnd.param file we have mentioned the javalib file and instllation directory path(<Siebsrvr roo>/dnd/install)
4) Unzipped the EDQ-Siebel Connector files in dnd/install folder
5) Copied the dnd.properties file in dnd/install directory and modified it accordingly to point to installed EDQ instance.
6) Configured the Siebel components for EDQ integration.
7) Realtime EDQ jobs are running.
8) Create a new Account
Env details are
On : 8.2.2.14 [IP2014] version, Client Functionality
EDQ 11.1.1.7.4
IBM JDK 1.7 32 bit
Using Open UI
Any Champ have faced this issue and overcame it please let me know the resolution steps. your help is
Regards
Monoj Dey
9007554589

Hi Monoj,
A few questions:
- What OS is Siebel running on?
- What version of the Siebel connector are you using?
- Which libdnd.so file are you using?
- What's the contents of your dnd.parms file?
thanks,
Nick

EDQ Log options for monitoring Web services

Hi
We have a specific need to monitor the web service calls through EDQ (EDQ CDS integration with Siebel). Can you assist with the options to set in logging.properties which will allow us to see the web service logs without the log information crowding it out?
Kind regards
Craig

Hi,
The best way to log traffic between Siebel and EDQ is to enable logging in the EDQ Siebel Connector and then examine the connector log files. You will then see requests and responses here - it is the best place as it will work across several EDQ servers if you have many in use.
See Section 4, item 3 in this document:
Oracle&reg; Enterprise Data Quality
3. (Optional) If detailed trace information on connector requests is required (for example, for temporary debugging purposes) add the following lines to the dnd.parms file to enable logging:
logfile: sdq%05d.log jlogfile: jsdq%05d.log "
It is also possible to enable logging by writing data out of EDQ itself, for example to append to a text file the data sent into match by adding a writer just before the match processor and configuring an export task to a text file in append mode, but this is server specific and less easy to disable later.
Regards,
Mike

Agent going to not ready after call hangup, Siebel CRM Connector, reason code 50002

Hi Everyone,
We have Contact Center Enterprise UCCE 8.5.2 with CTOS integrated Siebel CRM 8.1.1 using
Cisco Unified CRM connector
On daily basis we are receiving about 100 incidents that Agents goes to not ready after
talking to customer. and the reporting gives the reason code 50002.
As per Cisco its because of CTI server Failure/Agent desktop closed/network Problem. But
In real there is no network issue, Agent not closing the Agent desktop. Also if this is
the case agent should be logged out but in pratical its stays logged in but moved to
not-ready state(Reason 50002)
It could be miss communication between UCCE and Siebal CRM connector.
One more thing its not happening with one customer only it happening in many deployment on
Version 8. Especially the one integrated with Siebel.
If anyone face the same issue please share the experience and the solution if found any!
Regards,
Atif Tanveer

Atif,
If memory serves me right, CTI events are controlled and communicated by Siebel connector. So when your users close Siebel or any other CTI controlling connector this will be same as closing CTIOS or CAD without proper logoff. This will keep the phone out of synch and keep the user automatically into not ready to prevent any callers going to this device.
Simple answer you have to train users and make sure they close Close applications properly.
Thanks,
Baseer.

OIM connector for Siebel

Experts, please suggest some resources and guides for OIM connector for Siebel.
Is this ur http://www.oracle.com/technetwork/middleware/id-mgmt/downloads/connectors-101674.html ok.

Download and extract the connector.
You'll see one directory called "documentation". You'll find everything there related to Siebel Connector.

Siebel CRM Reason Code Commands

We are needing to enable some commands on the Cisco CTIOS Siebel connector and just not sure where they are enabled or edited at.
We are using connecter provided by CISCO for CTI between Siebel and CISCO. Connector provides the enabled command to Siebel that siebel can send as device command like "DeviceCommand = "ChangeNotReadyState"" using communication configuration DEF file.
Currently we have business requirement:
CTI agents can set their state to NOT READY on a click of button with reason code selected by the agents irrespective of there current state.
We configured the button, but the button is enabled only when the device command "ChangeNotReadyState" is enabled. Can it be possible to enable this button always and we can are able to change agents state at CTIOS level(CISCO)? Can we send "ChangeNotReadyState" command to CISCO irrespective of agents current state
Here is what we have done so far:
We configured DEF according to ORACLE support recommendation (ID 543337.1 listed below in this mail)
RELEVANT PARTIAL DEF FILE:
[Command:DSC_NOTREADY_POP_EXE]
   SubCommand_1 = "DSC_NOTREADY_NOPOPUP"
   SubCommand_2 = "DSC_NOTREADY_POPUP"
   SubCommand_3 = "CleanDashBoard"
   Comment      = "YQ8279: Add for Direct not ready Button Aug2012"
   Description = "Not Ready"
   ExecuteAll   = "TRUE"
   Hidden       = "TRUE"
[Command:DSC_NOTREADY_NOPOPUP]
   Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
   Description   = "Not Ready"
   DeviceCommand = "ChangeNotReadyState"
   FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
   Hidden        = "TRUE"
[Command:DSC_NOTREADY_POPUP]
   Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
   Description   = "Not Ready"
   DeviceCommand = "ChangeNotReadyState"
   FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
   Hidden        = "TRUE"
   CmdData       = "PopupforReason"
   [CmdData:PopupforReason]
      Comment          = "YQ8279: Add for Direct not ready Button Aug2012"
      Param.ReasonCode = "[Name]"
      SelectApplet     = "Transfer Multiple LOV Popup Applet"
      SelectBusComp    = "List Of Values"
      SelectBusObj     = "List Of Values"
      SelectParam      = "TRUE"
      SelectQuerySpec = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle      = "Please select the reason for changing status to Not-Ready"
So with above configuration suggested by oracle support we are sending "ChangeNotReadyState" device command twice in a manner so that it will be processed one after the other. But it is not happing, second command is not going through as its not enabled after Siebel issued it once. Please see below logs and highlights.
SCOMM LOG: <In Time Context >
ChangeNotReadyState Command is enabled (status = 16)
see image 1 on attached doc
Now user applied the command once :
See Image 2 on attached doc
Now "ChangeNotReadyState" device command is disabled .
Can we make it "ChangeNotReadyState" enabled via connecter always by making some registry setting or some setup.
See image 3 on attached doc
Oracle Support Suggestion:
Not able to select Not Ready Reason Code [ID 543337.1]
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147
Symptoms
In the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
Cause
Users were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
Solution
Suggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
   SubCommand_1 = "NotReadyForGVoiceStd"
   SubCommand_2 = "NotReadyForGVoiceAuxCode"
   SubCommand_99 = "NotReadyForGVoiceEnabler"
   Description   = "Set not redy for voice"
   Hidden        = "TRUE"
   ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
   Description   = "Set not ready for voice"
   DeviceCommand = "NotReady"
   Hidden        = "True"
   Title        = "Voice not Ready"
   CmdData       = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
   Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
   Description   = "Seçect Reason Code for Voice"
   DeviceCommand = "NotReady"
FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
   Hidden        = "True"
   HotKey        = "Alt+A"
   Title        = "Aux Mode"
   Profile       = "Gplus Voice1"
   CmdData       = "ReasonCodePopup"
   [CmdData:ReasonCodePopup]
      Param.ReasonCode               = "[Name]"
      Param.ReasonValue               = "[Value]"
      Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
      SelectApplet                    = "Value Type Pick Applet"
      SelectBusComp                   = "List Of Values"
      SelectBusObj                    = "List Of Values"
      SelectParam                     = "TRUE"
      SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle                     = "Please select the reason for changing status to Not-Ready"

Thanks for your response Cherilynn,
You are correct for a vanilla agetn desktop. However, if the agent has to become available to move from one aux reason to another, the agent may get a call in that process. With customiization, we can allow changing from one aux code to another without having to make the agent ready. Oracle suggested a solution but to do this, we need to enable and modify certain parameters within Cisco. What we are trying to find out is where are these parameters set, ex: AgentWorkMode and AgentWorkMode2, ChangeNotReadyState...
ORACLE SUPPORT SR
Not able to select Not Ready Reason Code [ID 543337.1]
SymptomsIn the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
CauseUsers were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
SolutionSuggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
Then we can call another communications command that starts the popup for the LOV of aux codes.
Here the agent will have enough time to pick the code with no more inbound calls.
The device commands for the command group are as follow:
[Command:NotReadyForGVoiceGroup]
   SubCommand_1 = "NotReadyForGVoiceStd"
   SubCommand_2 = "NotReadyForGVoiceAuxCode"
   SubCommand_99 = "NotReadyForGVoiceEnabler"
   Description   = "Set not redy for voice"
   Hidden        = "TRUE"
   ExecuteAll = "TRUE"
[Command:NotReadyForGVoiceStd]
   Description   = "Set not ready for voice"
   DeviceCommand = "NotReady"
   Hidden        = "True"
   Title        = "Voice not Ready"
   CmdData       = "NotReadyAuxCode"
[CmdData:NotReadyAuxCode]
   Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
[Command:NotReadyForGVoiceAuxCode]
   Description   = "Seçect Reason Code for Voice"
   DeviceCommand = "NotReady"
FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
   Hidden        = "True"
   HotKey        = "Alt+A"
   Title        = "Aux Mode"
   Profile       = "Gplus Voice1"
   CmdData       = "ReasonCodePopup"
   [CmdData:ReasonCodePopup]
      Param.ReasonCode               = "[Name]"
      Param.ReasonValue               = "[Value]"
      Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
      SelectApplet                    = "Value Type Pick Applet"
      SelectBusComp                   = "List Of Values"
      SelectBusObj                    = "List Of Values"
      SelectParam                     = "TRUE"
      SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
      SelectTitle                     = "Please select the reason for changing status to Not-Ready"
Regards,
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147

Issue importing Siebel data model into OPM

I am using OPM 10.2 and havaing a issue importing the Siebel data model in to OPM. I also have 10.2 Siebel connector installed on the desktop.
In OPM I cannot see the Siebel --> Import Data Model option in the menu.
Is there any configuration change that need to happen in OPM to do this?
Edited by: SP1D3R MAN on 17/11/2011 18:02

1. Make sure that you have the Siebel Connector 10.2.1 from Oracel Software delivery Cloud (formerly E-Devliery), there was a bug with the earlier 10.2 where the Policy Modeling Plugin was not working.
2. Make sure that the files Oracle.Modeling.Siebel.Exchange.dll, Oracle.Modeling.Siebel.Plugin.dll exist the the Plugins sub-directory of Policy Modeling (default location C:\Program Files\Oracle\Policy Modeling\plugins)
3. Make sure you are using Policy Modeling 10.2
if you need to manually copy the dll's they can be found in the siebel connector download at program files\Oracle\Policy Modeling\plugins\

Not able to install Siebel Determination Server

Hi,
I have installed Oracle policy modelling (10.4.1) successfully, able to make rules.
Now I have installed Siebel connector, done all the changes at Siebel side.
How ever I am facing challenges in deploying Siebel Determinations Server, request you to please share the steps how to deploy Siebel Web determinations server.
Or if you can share any document for the same on my email id
<removed by moderator so that you don't get spammed for all Eternity>
would be highly appreciated.
Regards,
Vineet Agarwal

Hi Vineet,
Bit old version OPA Siebel connector youtube video at here.
Policy Automation - OPA Connector for Siebel Overview Part One
http://www.youtube.com/watch?v=JZ8ocHeR7L8
Policy Automation - OPA Connector for Siebel Part Two
http://www.youtube.com/watch?v=6TMovRHihI0
May you need describe here what exactly problem you have with your web server name and version.
So that people can more detail advise at here.
Also on the OPA 10.41 has Helth check tools for Siebel connector.
http://www.youtube.com/watch?v=VjCZnlWlVYY
Thanks
Mayumi

OPA 10.4 "Inferred Entity Instances", possible to integrate with Siebel?

Hi,
In OPA 10.4, I found a new feature "Inferred Entity Instances" using which we can create benefit plans, Opportunities, Service Request,Order lines using only rules.
Does it mean we can create an Opportunity/Service Request/Order line by writing the information only in the rule when OPA 10.4 is integrated with Siebel?
Thanks,
Subhradeep

The current Siebel Connector only supports OPA 10.3, which does not have inferred entity instances.
The upcoming release of the Siebel Connector will support new 10.4 OPA features including inferred entities.
Cheers
Frank

JD Edwards Connector

Does anyone have any input on the pros/cons for purchasing the JD Edwards (Siebel) Connector? It's new with OWB 11g.
What does it really 'buy' you that you couldn't do by just doing an import?

jnederlo,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

EDQ Siebel Connector

Similar Messages

Maybe you are looking for