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.

0
Not a bug

Chris21 "Trying to pass a table-valued parameter with 6 column(s) where the corresponding user-defined table type requires 5 column(s)" during processing

In my newly upgraded customer environment I am seeing the following error when running an Import All for a Chris21 connector:

No entries were imported.  Could you please advise what I should do about it?

UNIFYBroker v5.3.2.0
UNIFYBroker/Chris21 v5.3.0.0

0
Planned

Error "EaiFlagDeleteAttribute field is required" when upgrading from an older Chris21 connector

When upgrading from a pre-UNIFYBroker v5 Chris21 environment I copied the Connector configuration XML across directly.  When associating the Chris21 Connector to the new v5 Agent, there was a UI error on save:

This happened because the newer version of the Chris21 Agent/Connector package has an additional attribute in the XML configuration that wasn't previously present (and UNIFYBroker doesn't automatically add it).

The solution is to edit the XML configuration file to add the attribute by hand then restart the UNIFYBroker service:

The value used for the attribute (eaiFlagDeleteAttribute="eaiunifyfl") were obtained by manually creating a new Chris21 Connector to see what value the system assigned to the attribute.

0
Won't fix

Cannot specify default (blank) Logon Application for the Chris21 Agent in the UI

In the Chris21 Agent form in the UNIFYBroker UI the "Logon Application" field is mandatory:


However the help for the the field says it can be left blank to not include it in the logon:

I was able to workaround this by editing the Agent configuration XML directly, to remove the value.  When I did so the value passed to Chris21 defaulted to "chris21".  So another workaround is likely to be entering "chris21" into the field directly rather than leaving it blank.

UNIFYBroker v5.3.2.0
Chris21 Connector v5.3.0.0

0
Planned

UNIFYBroker for chris21 v5.3.0 RTM Agent UI Issue

For the Chirs21 connector on the Agent screen Logon Application field should be optional. In the UNIFYBroker for chris21 v5.3.0 RTM it is mandatory.

0
Answered

Cannot retreive schema for Chris21 DET connector

Jack Cheng 5 months ago in UNIFYBroker/Frontier ichris/chris21 updated 4 months ago 7

Chris21 DET Connector is configured as follow:

However, retrieving schema failed with the below error in the log:

20190628,03:22:53,UNIFYBroker,Logging Engine,Information,Log file started.,Minimal
20190628,03:22:53,UNIFYBroker,Connector Engine,Error,"The schema for 'c21 DET Connector' connector was not updated for the following reason: System.AggregateException: One or more errors occurred. ---> System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Unify.Product.IdentityBroker.Chris21RecordtoChris21FieldDefinitionsAdapter.Transform(IChris21Record sourceValue, Boolean showTranslations)
at Unify.Product.IdentityBroker.Chris21Agent.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Chris21ConnectorBase.d__33.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Unify.Product.IdentityBroker.Chris21ConnectorSchemaProvider.GetSchema(ISchemaProviderFactoryInformation factoryInformation)
at Unify.Product.IdentityBroker.ConnectorEngine.SchemaProviderResult(IOperationalConnector`1 operationalConnector, Func`2 selector, IEnumerable`1 appliedFields)
---> (Inner Exception #0) System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Unify.Product.IdentityBroker.Chris21RecordtoChris21FieldDefinitionsAdapter.Transform(IChris21Record sourceValue, Boolean showTranslations)
at Unify.Product.IdentityBroker.Chris21Agent.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Unify.Product.IdentityBroker.Chris21ConnectorBase.d__33.MoveNext()<---
",Normal

Same error with a new Unify.IdentityBroker database as well.

The Frontiner chris21 agent connects without any error.

Answer

Run the following in the GTR form in chris21. This will run the same query the connector uses to retrieve its schema.

cbr="componentlist",screen="DET"
0
Answered

Timeout on Chris 21 Connectors

I'm getting timeouts on some Chris21 connectors. They seem to be intermittent, sometimes it works fine. Using v4.1.x Identity Broker and Chris21 connector. The error I get is as follows:

Are there any settings I can tweak on the IdB side to resolve this or is this Chris21 ending the connection early? I think there's a batch size setting or something similar but IdB is so slow to load with this customer I can't check again.

0
Answered

Chris21 Connector Failing - no status attribute

I'm getting the exact same error as in this ticket https://voice.unifysolutions.net/communities/6/topics/3223-import-all-entities-from-connector-chris21-secondment-connector-failed-with-reason-result-record

From the looks of things it's the exact same issue at the same customer. I don't know if Jerry ever resolved it. I've attached the log entry that's showing the error. It's using Idb and Chris 21 versions 4.1.x. Their Chris21 instance is version 8.16.17.

Adam suggested running some Chris 21 query as a resolution but I'm not sure where that query should be run. Is this likely to be a misconfiguration of Chris21 or something with IdB? This is in a test environment.

Please let me know if you need any more information.

0
Under review

Chris21 full import not completing

Matthew Davis (Engineering Manager) 7 months ago in UNIFYBroker/Frontier ichris/chris21 updated 7 months ago 1

Chris21 full import is getting partway through and then blocking - no errors thrown, just doesn't complete.

It's only processing 23,000 entities out of a total of 114,000.

0
Answered

Any known issues with C21 upgrades?

HSF are upgrading their C21 instance over the weekend so I just wanted to check if there's any known issues with upgrades and the broker c21 connector. They say it's an Engine update, going to version 8.16.5. They're using Identity Broker version 4. Any known issues?

Answer

Hi Daniel,

None that I have been made aware of. As you haven't mentioned what version of the connector, or what version of chris21 they are upgrading from, just ensure that you're on the latest available connector, as there was a change to the way logons were performed quite some time ago that we had to update the connector for (logonapplication became an invalid argument). Additionally, as with any upgrade (and in line with Frontier advice), ensure that the integration is included in the upgrade and test plan.

Thanks.

0
Answered

time offset and sliding date window

Unify.Product.IdentityBroker.AdapterEnginePlugInKey.extensibility.config.xml

Hi,

I need some help with 2 items : time offset and sliding date window in IdB Adapter transformations for a customer. They have chris21 as the source system.

IdB version: 4.1

Q1: Sliding Date Window

When an employee starts on a new position from a specific date (i.e 05 June 2018) the data flows in the connector and the data transformation is applied a day earlier(i.e on 04th June 2018). The implication is the job title is changed the day before the correct date. the customer wants to know whats wrong.

The transformation as configured: 


Q2: Time offset

When a user is terminated in chris21, he gets a termdate set and a simple transformation is applied to set the terminated flag as "True"/"False". But for example if a user has term date is 02 july 2018, by logic, it should add 24 hrs and set terminated flag to "true" 03 july 2018 midnight, but the terminated flag is set to "true" only around mid next day(i.e 04 july 2018 midday). Need some help fixing this issue.



Please help me to know where the issue is, thanks. really appreciate and thanks in advance


I have attached the Adapter xml, if you want for reference. Thanks.


Answer

A1: What are the values for posstart and posend fields? A Broker Date field is a timestamp with the time component forced to 00:00:00, so even if the timestamp value from chris is 4-6-2018 23:59:59, the corresponding date value in Broker will be 4-6-2018. Use the offset fields to adjust.

A2: Looking at your configuration, the sliding date window from Q1 is configured for local date values but the time offset flag transformation is not. Figure out what the correct setting should be, then if the flag is still being set incorrectly, follow the same process from A1. Also, offset used should be whole days for date fields due to the explanation above.