Change in AD connector 11.1.1.5.0

Hi,
I have installed AD connector 11.1.1.5.0 recently. I have noticed that it requires creating 2 resource if you want to run the Trusted Recon (AD User Trusted) as well as Target Recon (AD User).
If AD is required as trusted Resource then the AD Resource Lookup should be :
A ) Lookup.Configuration.ActiveDirectory.Trusted
And if you want to use AD as target Resource then AD Resource Lookup should be:
B) Lookup.Configuration.ActiveDirectory
So if AD is your trusted Resource and you also want to have AD User recon in you IDM then you have to create 2 Resources one for Trusted Recon with Lookup A) and 2nd for Target Resource with Lookup B) mentioned above.
Whereas in previous AD connectors (9.x.x) there was no need to crate 2 separate resource, it seems like Oracle has kind of forced NOT to use trusted source as target source?
Please correct me if I am wrong in my understanding.

Thanks Guys ...the issue was with .net framework on windows machine. I have installed 3.5.1 .net framework and get past this error. Now i am getting connectorKey(bundleName=ActiveDirectory.Connector bundleVersion=1.1.0.6380 connectorName= Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector) not found
My connector Server home directory is C:\Program Files(X86)\Identity Connectors\Connector Server. I have unzip the ActiveDirectory.Connector-1.1.0.6380.zip file and copied the ActiveDirectory.Connector-1.1.0.6380 folder under connector server but issue still remains same. I have even copied all the content of the ActiveDirectory.Connector-1.1.0.6380 folder and paste them directly in the connector server folder but still the issue is same. I have restarted the connector server after every instance. Am i missing anything in this step?

Similar Messages

Any Way to Change Thickness of Connector Lines for all lines of a Chart?

Post Author: ScottL
CA Forum: Charts and Graphs
Hi All,
I am trying to change the thickness of a Chart's Connector Lines for all lines of a chart and cannot find a way to accomplish this. I can go into Report Preview and individually change the thickness one at a time, but what if I do not know how many lines I will have (as in a Line Chart) ? I can't find a way to do this through Crystal Reports XI.
Many thanks in advance!
Scott

I think it's even easier to just match frame the "source file"... put your playhead on the clip you want to speed change in your sequence. Then type optioncmdf. Perform the speed change in the Viewer, then simply cut it in... Might help to put it up above the older, use the double arrow selection tool facing right to move the clips past this change later... pull the upper track speed changed clip down over the old, and viola.
Gotta say though, it's a lot easier to perform the speed change in the Viewer, and edit it all in as you go rather than doing it after you've put the clip in a sequence. (not always possible to determine what the speed change should be maybe, but sure easier.... FCP 7 handles this problem a lot better for sure, and worth the upgrade price if your machine is compatible.
Jerry

Changing Wire and connector from an PB3400 AC adapter.

Any ideas to repair the connector (exactly, change the wire that links with the connector) from a powerbook 3400 AC adapter? Looks like a 3.5mm audio jack but i need to know how it works.
I received a Powerbook G4 AC adapter today, looks similar too except for the jack size (2.5.mm). Voltage and power values are technically the same ([email protected] -> almost 45W). Can i adapt it to use with my powerbook(and how)?

@ExJamJus, I checked the Lenovo System Update and turns out an updated version of the Power Manager and Video driver was available. Installing these has fixed this issue.
Thank you all for your help.
T420 4178-6KG (Jan 2012 - now)
T61 6460-7EU (Aug 2008 - Jan 2012) [sold]
T41p 2373 (Oct 2009 - July 2012)

Ex2007 - Ex2013 Migration - Change in Send Connector = Transport.ServerCertMismatch.Monitor

I am in the final stages of a 2007->2013 migration that has gone very well. I was just about to move my Send Connector over to the Exchange 2013 side when my monitors alarmed that "Transport.ServerCertMismatch.Monitor" had gone unhealthy.
There is not a whole lot of information out there, but I did find this in each of the MBX logs:
Microsoft Exchange could not find a certificate that contains the domain name mail.domain.com in the personal store on the local computer. Therefore, it is unable to support
the STARTTLS SMTP verb for the connector Internet e-mail with a FQDN parameter of mail.domain.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there
is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
I checked my SAN and I do have mail.domain.com in it. I also confirmed that the Send Connector was using mail.domain.com as its HELO/EHLO reply. I have cycled the service and that did not seem to help either. Mail will still flow in my
testing, but I do not like unhealthy statuses so I would prefer to fix it.
Thoughts?

Did you install and enable an SSL certificate with the "mail.domain.com" SAN on the Exchange 2013 CAS for the available Exchange services?
Normally, when migrating from Exchange 2007, you need to request a new SSL certificate which includes the legacy namespace in the SAN field and install it both on the new Exchange 2013 and the legacy Exchange 2007 servers.
Step by Step Screencasts and Video Tutorials

Where ODBC Connector is defined in Windows registry?

Good day!
I have an app which use ODBC Connector, and it don't works as well. When I trying to access ODBC programmatically, I get an error from ODBC Driver Manager, smth like: " Data source not found and no driver specified, the default "
(my OS language is different, so it's not verbatim).
I changed MySQL ODBC Connector many times, I tried different versions and tried specify driver in registry manualy (in branch HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI). Also, I had tried to track how does it work step by step, and I stop at odbc32.dll. As I think it is ODBC Driver Manager which can't find smth necessary, but what?

This is more of a Windows Registry issue than a LabVIEW issue, does anyone know a good place to get support for that. My Google-Fu is failing me . All attempts to search for anything relating to Windows Registry and Icons tends to lead to changing the default icons in Windwos (My Computer, Recycle Bin, etc.).
Unless there is a way for me to add the .ICO as a resource within the .exe that defaults to the file somehow. I'm not seeing anything within LabVIEW to facilitate this, however...

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

Unable to define connector for multiple backend systems in BRM

Hi,
I am on GRCFND_A V.11 and SP04
I have multiple backend systems integrated with GRC box. So far I was using one backend connector as default one for role maintenance but it is not feasible if you have to create roles in variuos backend connected systems. I know one way to do so, i can keep changing the default connectors whenever i need to create roles but that is obviously not at all the onw any one would like to go with.
So, I tried to create unique connector groups for every individul backend connectors. But the issue is, the moment i assign the backend connector to the respective connector groups, the same gets reflected to other connector groups as well. So, whenever i either add or delete some of the connectors to any connector groups it gets modified/changed from all of the connector groups.
These are the backend connectors where i have to create roles from BRM whenever needed.
These are the connector groups:
I followed to the ink: GRC AC 10 BRM: Default Connectors with Multiple Back-end R/3 Systems , which is the same as mine issue, but not able to come to the solution point.
would appreciate for your quick response.
Thanks,
Ameet

Could anyone suggest solution to the above mentioned issue please?

AD Connector upgrade from v9.1.0 to v9.1.1.4

Hi all,
I need to upgrade the Active Directory Connector from v9.1.0 to v9.1.1.4. I have read the connector upgrade documentation and the upgrade path is the following:
1- v9.1.0 to v9.1.0.1 (upgrade)
2- v9.1.0.1 to v9.1.1 (full installation)
3- v9.1.1 to v9.1.1.1 (upgrade)
4- v9.1.1.1 to v9.1.1.4 (upgrade)
The problem is that the step 2, upgrading from v9.1.0.1 to v.9.1.1 requires a full installation, does that mean that I'll loose all the customizations in the connector? I know that direct upgrade from release 9.1.0.1 to v9.1.1 is not supported, but is there any work around to upgrade the connector without performing the full install and loosing the customizations? Please, any help will be appreciated.
Thank you in advance.

That's tricky because their are usually huge changes between two connector versions if Oracle says that it cannot be upgraded.
In other words you would require study of these changes and try to simulate it by yourself in your Dev. Or identify the customizations in your past environment and then redo (as you suggested yourself). The second option is a bit difficult but clean.
Thanks
Sunny

Issue in AD connector upgrade from 9.1.1.7.0 to ICF based 11.1.1.5.0 in OIM11gR2 PS1

Hi,
I am facing issue while AD upgrade from 9.1.1.7.0 to 11.1.1.5.0(ICF) in OIM11gR2 PS1 environment in Linux environment.
In the last step where we need to select the connector objects to be upgraded, issue is for AD User ( Process form and definition) and AD Group (Process form).
The issue is related to the IT Resource Definition and it says, "Error: Could not resolve dependency. AD Server [ITResourceDef]".
In the preceding steps- for process forms field, process definition tasks and IT resource mapping, I am retaining/add everything ( all the existing tasks, fields, parameters).
Can anyone help me on this? or if anyone has peform the upgradation of AD from 9.1.1.7 to 11.1.1.5 (ICF), can they tell me the steps to do or anything about the above error?
Thanks
Piyush

That's tricky because their are usually huge changes between two connector versions if Oracle says that it cannot be upgraded.
In other words you would require study of these changes and try to simulate it by yourself in your Dev. Or identify the customizations in your past environment and then redo (as you suggested yourself). The second option is a bit difficult but clean.
Thanks
Sunny

Business Connector and XI

Dear Sir,
Are there any preson change from Business Connector to use XI instead ?? Please kindly advise . how did you convert from BC to XI
Thank you and best regards,
Vimol

Hi Vimol,
Check this "How to" guide, for the required information
https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202&_OBJECT=011000358700005272252005E
other How to guides,
https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
have a look at this also...
Re: Connectors and Xi...
also,
XI FAQ/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this will help you.
Regards,
Saurabh...
Reward with points if found helpful.

GRC PC 10 - Source Connector update impact to AC 10

Hello
We had an issue with one of our controls where we were utilizing an ABAP sub scenario. The job would not finish and remain "in progress" for any scenarios involving a GRC satellite system (e.g. ECC, SRM). SAP advised us to change the source connector in the "Maintain Connectors and Connection Types" in SPRO so that the source system is GRC instead of the satellite system. We tested the updated assignment and noted that the update worked.
Our concern is what, if any, impact these changes will have to our AC side. I have done a bit of research and noticed that the "source connector" field is not needed for AC so there may not be an impact. We are going to test provisioning to confirm but also wanted to query the SCN to see if anyone else had experience with this. I've included a screen shot below that displays the updates we made to the source connector.
Does anyone know if updating the source connector will have an impact on the GRC AC side?

Hi Stacey,
Updating the source connector should not impact any AC functionality, you make a test and in case
it impacts then could be some other reason which we can check.
Regards,
Silky Sharma

GroupWise Connector issue

I may have found a possible bug in the 1.2.5 rev 299 version of DS. I have a SLES 11 SP2 server patched up running 1.2.5 build 299. The server sits in a DMZ with the IP address of 192.168.x.x which is NAT'd to 134.192.x.x. In prior versions up to 1.2.4 I go into the GroupWise Connector and change the GroupWise Connector IP address from the 192.168 address to the 134.192 address and restart the connector and everything works fine. In 1.2.5 when I change the IP address and try to restart the Connector I get an error about the connectors.xml not configured correctly and GroupWise Connector won't start. When I change it back to the internal IP 192.168.x.x it starts up fine. The problem is that if I don't change the IP to the NAT'd version then e-mail won't come in after the initial sync. If I remove DS from the server and downgrade to 1.2.4 it works fine. I did check the Connectors.xml file and it did change the IP address. Any help would be appreciated.
Thanks,
Dave Flax

redds,
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://forums.novell.com/

FIXED - Exchange 2013 - Can I Recreate Default Frontend Receive Connector SAFELY?

Hi
I'm need of some urgent assistance please.
I had a fully functional Exchange 2013 server and decided to create a receive connector for a photocopier/scanner to included its static IP  port number 25.
I accidentally chose Hub Transport role and not FrontEndTransport role which appears to have messed up port 25 connectivity on mail coming in from the internet. When I stopped and restarted the Transport Service within services.msc I then got this error.
Source: MSExchangeTransport
Event ID: 1036
Task Category: SmtpReceive
Level: Error
Description: Inbound direct trust authentication failed for certificate %1. The source IP address of the server that tried to authenticate to Microsoft Exchange is [%2]. Make sure EdgeSync is running
properly.
I proceeded to delete the offending Receive connector for the scanner/photocopier and restart the server, the transport service started ok this time but still I cant receive mail from the outside world.
My question: Can I delete the automatically created default Frontend "servername" connector which contains the proper settings then recreate it again with the same settings and NOT harm/delete all the users emails or the mailstore
or anything bad for that matter?
I have the details on how to create the connector but just wanted to check that's its ok to remove it and re-add it again now that everything was setup and running fine. I'm hoping the recreated Connector will fix what I broke.
Appears what I have done has broken my connectivity to telnet to port 25 to the exchange server from the outside world although oddly I can telnet to the server from a command prompt on the exchange server (telnet "servername" 25) and
getpresented with the exchange server responding. The tickbox for anonymous is ticked already. Port 25 already is forwarded from the firewall to the exchange server and was working fine till I made the error.
Any help is greatly appreciated. Thankyou.

OK so I found some more details online and decided to take the plunge (after a backup was taken) and my problem is now fixed. Although thank you to the 40 people that atleast looked at my query.
This worked for me, please read, backup and decide yourself if you wish to follow my steps.
1. I Read this to understand more on how I broke it in the first place  :
First section of this......
https://exchangemaster.wordpress.com/tag/smtp/
then
http://support.microsoft.com/kb/2958036
2. Deleted the Default Frontend "servername" Receive connector
3. Recreated it using these guidelines below. (I included them all for your ref). Source https://social.technet.microsoft.com/Forums/exchange/en-US/32e13998-a84e-4f10-8557-3f7ce6fdb824/2013-default-receive-connectors:
[PS] C:\>Get-ReceiveConnector | fl Name,AuthMechanism,RemoteIPRanges,TransportRole,permissiongroups,MaxMessageSize
Name             : Default EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Name             : Client Proxy EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Name             : Default Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Name             : Outbound Proxy Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Name             : Client Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : ExchangeUsers
MaxMessageSize   : 35 MB (36,700,160 bytes)
4. Recreated the Receive connector for my photocopier/scanner but this time choose Frontend Transport role and Not the default Hubtransport. Restarted the server, crossed my fingers and everything worked!! (Apparently restarting both transport services
is sufficient, but hey I just want to be sure it works from reboot in future.
Exchange SP1 will break any custom receive connectors that you have made prior to installing the update (nor even warn you that you're about to create an addition hub transport connector on port 25 after the SP1 update, there should
be only one hubtransport on port 25 as I understand it, its ok for Frontend transport) . The transport service will not start, so to save you the hassle of deleting your custom connector just run this command from an elevated exchange powershell command to
change the custom connector from hubtransport to Frontend Transport then start the transport service. ( you may have to kill the Transport service .exe process in task manager, then start the transport services after this amendment from the services.msc panel)
Set-ReceiveConnector –Identity "Your Receive connector name" –TransportRole FrontendTransport
Alternatively, delete and re-create the receive connector and set its role to
FrontendTransport and NOT HUBTRANSPORT !!!!!!!!!!!
This issue occurs if there is a receive connector of Transport type
HubTransport that has the binding set to port 25 on the affected Exchange 2013 server. On an Exchange 2013 server that has both back-end and front-end roles, only the
FrontendTransport server-type receive connector should have the binding set to port 25.
To fix this issue, run the following cmdlet to change the connector type from
HubTransport to FrontendTransport:
Source: http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-server-2013-sp1-transport-service-stops-and-does-not-restart.html

Exchange Connector adds Workflow user as related Item to Review Activity

We use Servcie Manager 2012 R2 with Exchange Connector 2.0
For some reason, the Exchange Connector adds the workflow user to the review activity as a related config item. The sender of the email would make sence, but the workflow user does not.
Does the Exchange Connector 3.0 Rerelease also add the workflow user?
Is there a possibility to avoid this behavior?
tia
Patrick Wahlmüller

Hi Patrik !
Never saw that before, what i can say is that the upgrade/change to Exchange COnnector 3.0 is easy low-risk and you add MS-Support possibilities for it.
Go for 3.0 !
R.

AE 5.2 Defining SAP Connectors

Hello,
Can someone identify to me the process in defining NEW SAP connectors for Access Enforcer 5.2?
I have been configuring AE and have the process working for creating new users where the user receives the email identifying their password and the system they have been defined to once the provisioning is completed
The SAP BASIS group who performed the installation have defined the connections as "VIRSAR3_01_MODEL and VIRSAR3_02_MODEL", for the DEV and PRD systems respectively.
Our production system is known to users as SAPPRD and I would like to create a SAP connector that shows that as the name rather than "VIRSAR3_02_MODEL"
I have tried to use the Define Connectors from the AE customization panel but have not had success in saving the definitions.
I am thinking that the VIRSAR3_02_MODEL name may be a default used during installation and there may be more than just going to the AE Define Connector panel to add additional connectors or name them differently.
Appreciate if someone can identify the proper steps I need to take; I would think the SAP BASIS group will need to be involved. This is somewhat new to them also.
Thanks
Jerry Synoga
[email protected]

Hello Listeners,
I have researched this issue with our BASIS group and we have now become more familiar with the AE Connectors;
The ones that I have been given are what is defined with the NetWeaver installation and are defaulted to the VIRSAR3_01_MODEL and VIRSAR3_02_MODEL; these then become available in the AE Configuration process for defining SAP Connectors; these are the JCO connectors and will work if used for AE provisioning of NEW / Change users
It is recommended by SAP that for this type of connection you should use a non-JCO connector which should be defined using the AE Configuration> Connector> Define SAP process; when I tried to do this and change the "name" of the connector, I would receive the ACTION FAILED message; the system log identified the error as a Duplicate Key (too bad the AE message was not that informative);
we discovered that the Key setting was made up of the "short description" field of the Define Connector process; since I only changed the 'name" field, I was hitting the duplicate key error; one would have thought that the 'name" field, which would always be unique, would comprise of the key;
The JCO connectors should be used according to SAP for communication between tools such as AE and CC ( Access Enforcer communicating with Compliance Calibrator; this is something I plan on getting to in the near future
Conclusion is that if you need to change the JCO connector names to something other than the defaults, you can do this if you have access to the NETWEAVER ADMINISTRATION functions;
The non-JCO SAP connector can be defined for communication between AE and the SAP backbends system; remember that the 'short description" field should be unique among all the connectors - JCO and non-JCO
With this knowledge I have successfully completed the connector definitions and now have a better understanding of this process
Hope this lengthy explanation helps others
Thank You
Jerry Synoga
jerry,.[email protected]

Change in AD connector 11.1.1.5.0

Similar Messages

Maybe you are looking for