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.
Join transformation on different data type fields
It is more like a theoretical question but happen to Monash's implementation;
In Adaptor in IdB, we have 2 tables name A and B. We need to join A.x = B.y to get the attribute B.z.
However, x is integer and y is string and hence they do not match.
Is the any convert function for this?
SAP Connector: Passing {NOW} to Table Connector got wrong date format
In one of the table connector, there are conditions
BEGDA "less than or equal"
ENDDA "greater than or equal" {NOW}
It is expected that all records with Begin Date <= current date <= End Date will be return. However it returns none.
Did a APAB tracing with Monash SAP SME and it turns out
{NOW}is parsed to the wrong format. In the tracing, the value that ABAP code received is "1/23/2014 1:52:41 PM" while the expected value is "20140123"
Field names in employee connector will cause problems with Identity Broker v3.0
Identity Broker v3.0 introduced new restrictions on field names at the adapter level.
Suggested improvement for Identity Broker for SAP HCM v3.0.0 is adding another layer of interpretation for the employee connector allowing more human readable field names, and avoiding the use of InfoType:Field*SubType - where * is a special character. This will avoid high usage of transformations at the adapter level.
Read Table Connector optional fields
The Read Table connector makes all fields returned from SAP mandatory in the schema, which is difficult to configure due to the vast number of fields, and is also wasteful within the solution set. Please make all fields other than the primary key optional.
Communicator test tool enhancements - ability to create connector configurations.
Add ability to create connector configurations from the SAP Communicator test tool.
Error results when connecting to SAP HCM using SAP HCM wizard in Management Studio
When attempting to connect to SAP using the SAP HCM Wizard the following errors result:
Exception exported from Save exception
System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at SAP.Connector.Connection.Open()
at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open()
at Unify.UI.PlugIn.SAP.ConnectionWizard.TestSapCredentialsTask.PerformTask()
at Unify.UI.TimeoutTaskDecorator`1.PerformTask()
at Unify.UI.ExceptionTaskDecorator.PerformTask()
ConnectionError.rtf
Add ability to request multiple employee status types
Allow the employee connector to request more than one employee status type.
SapHR Test Harness Issues
A new version of the test harness was provided to us for testing this solution, version is 3.0.1.
I've extracted the archive and run the executable. The executable is not in the Identity Broker directory.
I get an error regarding missing DLLs
System.IO.FileNotFoundException: Could not load file or assembly 'SAP.Connector.Rfc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23' or one of its dependencies. The system cannot find the file specified. File name: 'SAP.Connector.Rfc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23' at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(AssemblyName assemblyRef) at SAP.Connector.RfcConnectorLoader.LoadRfcConnector() at SAP.Connector.RfcConnectorLoader.GetRfcConnection(IDestination dest) at SAP.Connector.Connection.GetNewConnection(IDestination dest) at SAP.Connector.Connection.GetConnection(IDestination dest) at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open() in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.Communicators.SapHRCommunicator\SapHrCommunicator.cs:line 451 at Unify.Communicators.SapHRCommunicator.TestHarness.btnConnect_Click(Object sender, EventArgs e) in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.TestHarness.SapHrCommunicator\TestHarness.cs:line 58 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
To try to get around this, I copied the missing DLL (there are two) from the Identity Broker service directory, but I then get the error
System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) at SAP.Connector.Connection.Open() at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open() in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.Communicators.SapHRCommunicator\SapHrCommunicator.cs:line 455 at Unify.Communicators.SapHRCommunicator.TestHarness.btnConnect_Click(Object sender, EventArgs e) in S:\hg\Connectors\SAP.HCM\Master\Source\Unify.TestHarness.SapHrCommunicator\TestHarness.cs:line 58
Event log error
Fault bucket , type 0 Event Name: PCA2 Response: Not available Cab Id: 0 Problem signature: P1: Unify.TestHarness.SapHrCommunicator.exe P2: 3.0.1.3 P3: Unify.TestHarness.SapHrCommunicator P4: UNIFY Identity Broker for SAP HCM P5: UNIFY Solutions Pty Ltd P6: 200 P7: -1 P8: P9: P10: Attached files: These files may be available here: C:\Users\a16716.TESTINTERNAL\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_Unify.TestHarnes_18e927a83648e251bb989378285ab8f6680a1e1_2d5cb42b Analysis symbol: Rechecking for solution: 0 Report Id: 2076e8d0-3f55-11e2-8a8f-005056ba0004 Report Status: 4
SAP timing configuration for IdB 3.*
The following is the timing configuration for one of 10 connectors defined in the IdB 2.* solution currently in Production:
<getAllEntities> <timing name="RecurringTimespan"> <timespan value="3600000000" /> </timing> </getAllEntities> <polling> <timing name="RecurringTimespan"> <timespan value="3600000000" /> </timing> </polling>
... i.e. reading this literally, both full AND delta every 6 minutes!!!
I had converted the above to the following for IdB 3.* - mainly for readability:
<getAllEntities> <timing name="Daily" offset="21:00:00" /> </getAllEntities> <polling> <timing name="RecurringTimespanStandardTime"> <timespan value="00:10:00" /> </timing> </polling>
... on the basis that it seemed silly to have both nodes set at the same frequency. I have been happily testing with this for the last couple of days ... but had started to notice that polling wasn't working .
I had not noticed the "delta import" button on the UNIFY Management Studio 3.* toolbar before Friday, but when I click on this for the above IdB 3.* connector configuration I get the following error in the IdB log:
Timestamp Severity Source Module Message 8/04/2013 1:49:57 PM Warning Change detection engine poll failed. Change detection engine "Change detection engine poll for connector Organisational Structure Connector failed with reason The connector 7d7e4969-2a73-4669-848c-67cb72c7867c does not support polling.. Duration: 00:00:00.0361342 Error details: System.NotSupportedException: The connector 7d7e4969-2a73-4669-848c-67cb72c7867c does not support polling. at Unify.Framework.ConnectorToPollingConnectorBridge.get_PollingConnector() at Unify.Framework.ConnectorToPollingConnectorBridge.PollChanges(IStoredValueCollection changeState) at Unify.Framework.EventNotifierPollingConnectorDecorator.PollChanges(IStoredValueCollection changeState) at Unify.Framework.ChangeDetectionPollJob.RunBase() at Unify.Framework.JobBase.Run() at Unify.Framework.MutexJobDecorator.Run() at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run() at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)"
I then went looking in the JIRA doco for this connector, including here, but couldn't find any doco about whether or not this connector should support polling.
Is the Production configuration wrong but nobody has ever noticed? It is consistent with version 2.4 of the spec which says the following:
15.2 Identity Broker
Connector Event Timespan Description
SAP HCM GetAllEntities 3600000000
SAP HCM Polling 3600000000
I suspect the SAP HCM connector has somehow never been a polling connector ... but I just wanted to make sure!
Modifications required to employee / manager relationship hierarchy
John Campbell is looking to modify the SAP ABAP modules in order to update the employee / manager relationship hierarchy model.
He has asked which ABAP module he should be looking at specifically.
Any ideas?
Customer support service by UserEcho
