Identity Broker Forum
Welcome to the community forum for Identity Broker.
Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.
Entity does not need to be re-retrieved on update if no attachment handling present
The chris21 connector will always re-retrieve an updated entity from the repository for attachment handling. The retrieval should be moved entirely within the scope of the attachment handling section to avoid this needless performance hit.
Content type usability improvement
Update the agent UI so that the content type setting automatically switches when that agent type setting is changed:
| Agent Type | Content Type |
|---|---|
| WebServiceCommunicator | text/xml |
| HttpCommunicator | application/x-www-form-urlencoded |
Debug mode logs too many lines
Debug mode introduced for v3.0.6.1 logs each line from Chris21 a repeated number of times to the Identity Broker log, meaning the log grows larger than it needs to when attempting to debug a specific connector.
chris21 connector should throw an error if schema discovery is attempted on non-existent form
Chris21 schema discovery returns no schema if a form doesn't exist. It should instead error that the form could not be found.
IdB for chris21 seems to take significantly long period of time to perform "Full Import" from chris21 system
The Identity Broker for chris21 seems to take significantly long period of time to perform "Full Import" from chris21 system into Identity Broker Connector and then process/transform the data into the IdB Adapter.
I am not familar with the flow process and the analysing the log file content. Thus the below investigation may not be entirely correct. But the overall time taken for processing data does seems significantly long in Identity Broker for chris21.
The customer has 4999 records/users in chris21.
Analysis 1:
1 - When performing the "Import All Connectors" for all six (6) Connectors took approximately 32 minutes at other times it does seems to take significantly longer time, eg 45 minutes. During this time the CPU and disk accessing activities are at 100%.
Started at
20101215,07:22:14,Change detection engine import all items started.,Change detection engine,Information,Change detection engine import all items for connector Chris21 Address Connector started.,Normal
Finished at
20101215,07:54:15,Change detection engine import all items completed.,Change detection engine,Information,Change detection engine import all items for connector Chris21 Org Unit Connector completed. Duration: 00:02:34.7343750,Normal
2 - When performing the "Full Import" in FIM for chris21 MA it took approximately 10 minutes. At other times we believe it took significantly longer.
Started at
20101215,07:55:56,Adapter request to get attribute changes from adapter space.,Adapter,Information,Adapter request to get attribute changes from adapter space d5251d7d-05cc-4d35-916e-e99e06b9ffd3.,Normal
Finished at
20101215,08:05:46,Adapter get attribute changes completed.,Adapter,Information,Adapter get attribute changes for adapter space d5251d7d-05cc-4d35-916e-e99e06b9ffd3 completed. Duration: 00:09:49.8125000,Normal
It has been mentioned that the "Import All Connectors" should take only a few minutes. Thus I would like to request a review of the IdB Connector and Adapter configuration files (attached) as to what could possibly create this behaviour. It is mentioned that the gtrChunkSize="1000" could be in appropriate for the volume of data in chris21.
Analysis 2:
Another example: When performing the "Import All Connectors" for all six (6) Connectors took approximately 14 minutes
Start at
20101213,07:01:22,Change detection engine import all items started.,Change detection engine,Information,Change detection engine import all items for connector Chris21 Person Connector started.,Normal
Finished at
20101213,07:15:17,Change detection engine import all items completed.,Change detection engine,Information,Change detection engine import all items for connector Chris21 Placement Connector completed. Duration: 00:02:19.6875000,Normal
2 - When performing the "Full Import" in FIM for chris21 MA it took approximately 27 minutes 30 seconds.
Started at
20101213,07:25:53,Request to get all entities for adapter space.,Adapter,Information,Request to get all entities for adapter space d5251d7d-05cc-4d35-916e-e99e06b9ffd3.,Normal
Finished at
20101213,07:53:34,Adapter get all entities to adapter space completed.,Adapter,Information,Adapter get all entities to adapter space d5251d7d-05cc-4d35-916e-e99e06b9ffd3 returned 4999 entities. Duration: 00:27:41.0937500,Normal
Analysis 3:
"Import all connectors" in IdB took approximately 12 minutes. I do not have the log file
"Full Import" in FIM for chris21 MA took approximately 6 minutes.
Please help to review the Connector and Adapter configuration files and also advice if the above time is acceptable or not.
UnifyLog20101213-extract.csv
UnifyLog20101215-extracted.csv
Make logonapplication optional
From Frontier, the logonapplication shouldn't be required when logging in.
Identity Broker for chris21 delete "Termination Details" and perform "Synchronise Import" result in error/exception
This issue is encountered when testing and verifying [ IDB-13IDB-15
After deleting a "Termination Details" and then perform "Synchronisation Import" on the Termination connector result in the following exception:
20110117,00:03:31,Change detection engine poll started.,Change detection engine,Information,Change detection engine poll for connector Chris21 Termination Connector started.,Normal 20110117,00:03:31,chris21 GTR EAI Communicator,Poll,Information,Started successfully.,Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Poll,Information,"Completed polling successfully after [00:00:00.0625000] duration. getEaiFile=EMTER;getEaiKey=Number Key:Count=1;detnumber=102967 Starting deletion of chris21 GTR EAI change files.",Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Poll,Information,Completed successfully after [00:00:00.0937500] duration.,Verbose 20110117,00:03:31,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal 20110117,00:03:31,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Termination Connector reported 1 changes. Duration: 00:00:00,Normal 20110117,00:03:31,Chris21 Termination Connector,GetEntities,Information,Started successfully.,Verbose 20110117,00:03:31,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal 20110117,00:03:31,Get changes from connector completed.,Connector,Information,Get changes from connector Chris21 Termination Connector reported 1 changes. Duration: 00:00:00,Normal 20110117,00:03:31,Request to get changes from connector.,Connector,Information,Request to get changes from connector Chris21 Termination Connector.,Normal 20110117,00:03:31,Chris21 Termination Connector,GetEntity,Information,Started successfully.,Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Get,Information,Started successfully.,Verbose 20110117,00:03:31,chris21 GTR EAI Communicator,Get,Error,"Exception occured after [00:00:00.0781250] duration. System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey)",Verbose 20110117,00:03:31,Chris21 Termination Connector,GetEntity,Error,"Exception occured after [00:00:00.0781250] duration. System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntity(MultiKeyValue entityId)",Verbose 20110117,00:03:31,Chris21 Termination Connector,GetEntities,Error,"Exception occured after [00:00:00.0781250] duration. System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntity(MultiKeyValue entityId) at Unify.Connectors.Chris21GtrConnectorBase`1.<GetEntities>b__4(MultiKeyValue entityId) at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntities(IEnumerable`1 entityIds)",Verbose 20110117,00:03:31,Change detection engine poll failed.,Change detection engine,Warning,"Change detection engine poll for connector Chris21 Termination Connector failed with reason GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected.. Duration: 00:00:00.2031250 Error details: System.IO.InvalidDataException: GTR result record has an invalid ""status"" attribute value. status=""fail"" existing. status=""ok"" expected. at Unify.Framework.Chris21GtrWorker.CheckAttribute(IChris21GtrCommandLine chris21GtrCommandLine, String attributeName, String expectedAttributeValue) at Unify.Framework.Chris21GtrWorker.CheckGetResult(IChris21GtrRecord record) at Unify.Communicators.Chris21GtrCommunicatorBase.Get(IChris21GtrEntityKey entityKey) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntity(MultiKeyValue entityId) at Unify.Connectors.Chris21GtrConnectorBase`1.<GetEntities>b__4(MultiKeyValue entityId) at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at Unify.Connectors.Chris21GtrConnectorBase`1.GetEntities(IEnumerable`1 entityIds) at Unify.Framework.ConnectorToPollingConnectorBridge.GetEntities(IEnumerable`1 entityIds) at Unify.Framework.EventNotifierReadingConnectorDecoratorBase`1.GetEntities(IEnumerable`1 entityIds) at Unify.Framework.ChangeDetectionPollJob.RunBase() at Unify.Framework.MutexJobDecorator.Run() at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run() at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
The steps to reproduce:
- Terminate a user by creating the termination details record.
- Perform "Synchronise Import" on the Termination connector to obtain the delta change into Identity Broker entity repository. Success
- Perform "Delta Import" on FIM chris21 MA. Success
- Un-terminate the same user by deleting the termination details record
- Perform "Synchronise Import" on the Termination connector to obtain the delta change into Identity Broker entity repository. Failed, with the above error
Note: When this error occurred, the "eailst" record is removed (i.e no longer available in chris21). And no update to the Termination connector entity. The Person and Position connector does not encounter this issue.
The Identity Broker for chris21 Connector and Adapter configuration files attached. The Identity Broker log file containing the error also attached.
AdapterEngine.extensibility.config.xml
ConnectorEngine.extensibility.config.xml
Error occurred.jpg
UnifyLog20110117.csv
Clarification of Identity Broker for chris21 behaviours
The customers have to the following questions which I am not enough understanding of Identity Broker for chris21 and chris21 system to simlulate a termination of a user. I will attempt to provide my answer below. Please assist in clarifying or answering these questions if possible.
AHG
I've found that the Connector Delta Import process doesn't seem to pick up termination changes. When I do a Full Import the change comes through.
The steps I have followed are:
1. Terminate user in Chris21
2. Perform 'Synchronise Import' on the connectors
3. Run the Chris21 MA Delta Import process
The Synch stats show that there are no changes that have been picked up.
If I perform a Full Import using the Chris21 MA I still have no changes.
Shane Lim - I understanding is the "Synchronise Import" on the Termination Connector to bring in the delta change into the Termination connector table. This delta change would then be processed/transformed into the Adapter table. When the user perform the "Delta Import" in FIM chris21 MA the delta change in the Adapter table would flow in FIM chris21 MA.
Having said this I have not done this scenario before since I have no knowledge how to terminate a user in chris21.
AHG
If I complete a full import on all the connectors, then a delta import using the Chris21 MA I have the update I expect. Is this the correct behaviour? I had expected that performing a Synch Import would pick up such a change, or am I mistaken?
Shane Lim I expect the "Synchronise Import" in Unify Management Studion followed by the "Delta Import" in FIM chris21 MA to pick up the delta change.
AHG
The other question is, out of curiosity, when I terminate someone, should I be able to just import from the Termination connector seeing as the only change that was made to Chris21 is the addition of a termination record? Currently this doesn't work, I get the same GTR error we were getting last week. I have to first import from Person, then the Termination connector.
Shane Lim I expect that each Identity Connector be able to perform the "Synchronise Import" independently.
PS: Cabrini Health fundamentally using the same Identity Broker for chris21 Connector and Adapter configuration files and they have not report experiencing the same behaviour here.
AHG
Something else I have noticed is that for the Metaverse to be updated by the change made to AD to disable the account for the terminated employee, I have to perform a Full Import using the ADDS MA and then a Delta Sync. Again, I had expected that a delta import should do the job, but, I may be mistaken?
Could you please clarify this for me as perhaps i'm misunderstanding when we need to perform a Full Import versus a Delta Import. I thought we really only needed to perform a Full Import when we are populating the Metaverse and the Connected Spaces for the first time. After that I thought Delta's should give us any changes made but that doesn't seem to be the case. I am running through multiple cycles as you recommended so I can ensure the data change flows through all the different steps properly.
Shane Lim
My understanding and expectation is that a "Full Import" in the Unify Management Studio and in the "Full Import" in the FIM chris21 MA is not necessary after the initial "Full Import" is completed. But then we do have the schedule in the Identity Broker for chris21 Connector configuration for performing getAllEntities.
Thus now I am no certain what the expected behaviour.
Please assist.
Upgrade from Identity Broker for chris21 v3.0.5 to 3.0.5.2
Perform upgrade of Identity Broker for chris21 from v3.0.5 to 3.0.5.2 (by uninstalling older version and install the newer version).
Make no change to any of the Identity Broker's Connector and Adapter configuration for chris21.
Restart Identity Broker service successully.
Performed "Clear All..."
Performed "Import All Connectors..." result in the following errors for all Connectors for chris21.
20110203,23:18:56,Adapter clear started.,Adapter,Information,Adapter d5251d7d-05cc-4d35-916e-e99e06b9ffd3 clear started.,Normal 20110203,23:18:58,Adapter clear completed.,Adapter,Information,Adapter d5251d7d-05cc-4d35-916e-e99e06b9ffd3 clear completed in duration 00:00:02.7343750.,Normal 20110203,23:19:27,Change detection engine import all items started.,Change detection engine,Information,Change detection engine import all items for connector Chris21 Person Connector started.,Normal 20110203,23:19:27,Chris21 Person Connector,GetAllEntities,Information,Started successfully.,Verbose 20110203,23:19:27,chris21 GTR EAI Communicator,List,Information,Started successfully.,Verbose 20110203,23:19:28,chris21 GTR EAI Communicator,List,Warning,"Logout failed with the following message: GTR line type is recognized but not valid [Command].",Verbose 20110203,23:19:28,chris21 GTR EAI Communicator,List,Information,Completed successfully after [00:00:00.0468750] duration.,Verbose 20110203,23:19:28,Chris21 Person Connector,GetAllEntities,Information,Completed successfully after [00:00:00.0468750] duration.,Verbose 20110203,23:19:28,Request to get all entities from connector.,Connector,Information,Request to get all entities from connector Chris21 Person Connector.,Normal 20110203,23:19:28,chris21 GTR EAI Communicator,List,Information,Chunking [2000] is implemented after [00:00:00.0468750] duration.,Verbose 20110203,23:19:28,Get all entities from connector failed.,Connector,Warning,"Get all entities from connector Chris21 Person Connector failed with reason GTR line type is recognized but not valid [Command].. Duration: 00:00:00.0156250 Error details: System.IO.InvalidDataException: GTR line type is recognized but not valid [Command]. at Unify.Framework.Chris21GtrWorker.ExtractListResult(ICollection`1 entities, IChris21GtrRecord record, Int32 entityKeyCount) at Unify.Communicators.Chris21GtrCommunicatorBase.<ListWithChunking>d__0.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnFirst>d__1c`1.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext() at Unify.Framework.ActionOnExceptionEnumerator`1.MoveNext() at Unify.Framework.EnumerableExtensions.<ActionOnLast>d__16`1.MoveNext() at Unify.Framework.EnumerableExtensions.<ProduceAutoPages>d__9`1.MoveNext() at Unify.Framework.Visitor.ThreadsafeVisitorEvaluator`1.Visit() at Unify.Framework.Visitor.VisitEvaluateOnThreadPool[T](IEnumerable`1 visitCollection, Action`2 visitor, Int32 maxThreads) at Unify.Framework.RepositoryChangeDetectionWorkerBase.PerformChangeDetection(IEnumerable`1 connectorEntities) at Unify.Framework.ChangeDetectionImportAllJob.ImportAllChangeProcess() at Unify.Framework.ChangeDetectionImportAllJob.RunBase() at Unify.Framework.MutexJobDecorator.Run() at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run() at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal
Is there any other configuration that I may need to update or change?
AdapterEngine.extensibility.config.xml
ConnectorEngine.extensibility.config.xml
UnifyLog20110203.csv
Identity Broker for chris21 downgrade stop Identity Broker service from starting
Post upgrade of Identity Broker for chris21 from version 3.0.5 to 3.0.5.2
I ran into the issue that I cannot perform "Synchronisation Import" or "Full Import" on any exist chris21 Connectors. See end of issue IDBCHRS-13 for details of the error.
Since I need my Lab environment for other work for chris21 I downgrade Identity Broker for chris21 back to version 3.0.5. This is done by uninstalling Identity Broker for chris21 v3.0.5.2 and install Identity Broker for chris21 v3.0.5.
I also restore to Connector and Adapter configuration file to the known working ones.
When starting the Identity Broker service I encounter the following error:
Unify.Framework.UnifyServerInitializeException: Could not load file or assembly 'Unify.Framework.LogWorker.Interfaces, Version=3.0.5.0, Culture=neutral, PublicK eyToken=84b9288cb2633de4' or one of its dependencies. The located assembly's man ifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly ' Unify.Framework.LogWorker.Interfaces, Version=3.0.5.0, Culture=neutral, PublicKe yToken=84b9288cb2633de4' or one of its dependencies. The located assembly's mani fest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'Unify.Framework.LogWorker.Interfaces, Version=3.0.5.0, Culture=neutr al, PublicKeyToken=84b9288cb2633de4' at Unify.Connectors.Chris21GtrConnectorFactoryBase`3.CreateComponent(IMultiKe yedConnectorFactoryInformation factoryInformation) at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factory Information) at Unify.Framework.ConnectorEngineConnectorGenerator.CreateComponent(IMultiKe yedConnectorFactoryInformation factoryInformation) at Unify.Framework.ConnectorGenerator.CreateComponent(IConnectorGeneratorInfo rmation factoryInformation) at Unify.Framework.PollingConnectorEngineConfigurationFactory.CreateConnector ConfigurationBase(XElement xmlConfiguration, IConnectorHelper connectorHelper, I Timing pollingTiming, INotificationMessageService messageService, ITiming getAll EntitiesTiming, IConnectorGroup connectorGroup) at Unify.Framework.PollingConnectorConfigurationFactoryBase`2.CreateComponent (IConnectorConfigurationFactoryInformation`1 factoryInformation) at Unify.Framework.PlugInGeneratorBase`4.CreateComponent(TFactoryInfo factory Information) at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfi gurationFromNode(THelper connectorHelper, XElement connectorNode, TConnectorConf igurationCollection connectorConfigurationCollection, IConnectorGroup connectorG roup) at Unify.Framework.ConnectorConfigurationGeneratorBase`4.CreateConnectorConfi gurationCollection(XElement xmlCollection, THelper connectorHelper) at Unify.Framework.ConnectorEngine.Initialize() at Unify.Framework.UnifyEngine.Initialize() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\M icrosoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure lo gging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus ion!EnableLog]. --- End of inner exception stack trace --- at Unify.Framework.UnifyEngine.Initialize() at Unify.Services.Connect.Debug.ProgramProxy.Execute()
I thought that the core files are somehow wrong version thus I uninstall Identity Broker Service v3.0.5.6 and re-install it. The problem persist.
Any advise or assistant on how to resolve this issue would be much appreciated.
Thank you.
Customer support service by UserEcho
