1. UNIFYBroker Forum
  2. UNIFYBroker/Frontier ichris/chris21
  3. Bugs
0
Fixed

Upgrade from Identity Broker for chris21 v3.0.5 to 3.0.5.2

Shane Lim 13 years ago in UNIFYBroker/Frontier ichris/chris21 • updated by anonymous 9 years ago • 9

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
Shane Lim 13 years ago

This upgrade was done to verify the fixes for IdB for chris21 issues 9, 12, 13, 14.

It is also for verifying the steps require for upgrading at AHG and to test the Event Broker's synchronisation sequence configuration designed will work for the solution deployed.

Shane Lim 13 years ago

The associated IdB configuration files and error log is attached.

Rodney Pullini 13 years ago

I know what this is, my apology, new installer soon.

Shane Lim 13 years ago

Thanks Rodney. Much appreciated.

Please let me know when it available so that I can fix my Lab environment.

Rodney Pullini 13 years ago

This and previous issues are fixed in new installer for v3.0.5.2:

https://unifysolutions.jira.com/wiki/display/SUBIDBCHRS/Downloads

Rodney Pullini 13 years ago

Shane,

If there is another problem with this installer, then reopen this issue, instead of creating a new one.

Please update issues 9, 12, 13, 14, 15 when testing is accepted.

Shane Lim 13 years ago

Thanks Rodney!

Acknowledge your instruction.

Shane Lim 13 years ago

Test with the latest Identity Broker for chris21 v3.0.5.2 download

Upgrade Identity Broker for chris21 from v3.0.5 to v3.0.5.2 (by uninstalling old version and install the new version).

Verification tests:

  • Identity Broker service started successfully.
  • Perform "Full Import" on various chris21 Connectors (Person, Address, Placement, Termination etc) successfully.
  • Perform "Synchronise Import" on various chris21 Connectors (Person, Address, Placement, Termination etc) successfully.

    Note: I have not test the FIM's "Full Import" and "Delta Import" part of the cycle. This is not necessary for the resolution of this issue.

    PS: This upgrade of Identity Broker for chris21 v3.0.5.2 also resolved the following issues:
Shane Lim 13 years ago

Issue resolved and verified. Closed.

Customer support service by UserEcho