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

Reflection timeouts and dropped records at CSIRO

* Scheduler is disabled
* No Import operations are in progress
* All connectors are in an exclusion group
* No Pending Changes on any other adapters

This is a placeholder.  Please do not action this ticket until full bug details have been provided.

0
Answered

SAP ABAP documentation

Hi Guys,

I have a client looking for some additional information regarding the ABAP modules required for idB for SAP comms. They would like to know 

  • Why we need them
  • Exactly what they do
  • What we pass to execute them
  • If they are "SAP Certified"
  • Who wrote them

Not sure if any of this exists.

They are trying to understand why broker does not use the OOTB modules to perform its tasks.

My understanding was that the modules were required in order to output the return values in an idB compliant manner.

Any information would assist

Cheers,
Ryan

Answer
Why we need them

ABAP is the designated method for interacting with SAP, that works across their releases.

Exactly what they do

The read modules allow us to read from one or more tables, shaping the data into a format that is consistent across each of the 'objects' that we read. The write modules allow us to add/update/upsert to one or more tables, in a format that is consistent across each of the 'objects' that we write.

What we pass to execute them

To perform a write we send the headers being updated, the 'shape' of the 'object' being updated, the details of the records being updated.

If they are "SAP Certified"

No, it was determined that it did not make commercial sense. You'll be able to see exactly what is contained within the modules once imported. However, we would be more than happy to discuss working with you on this if required.

Who wrote them

We make use of an SAP consultant who has over 15 years' experience working with ABAP.

0
Answered

Identity Broker for SAP - firewall

Eddie Kirkman 2 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 2 years ago 3

Looking at the doco I can see reference to the Remote Function Calls. Is there any information available about what ports it uses or is it something configurable at the SAP end? I have found SAP docs that point out the connecting system needs to be able to use TCP/IP but I cannot find any port info. I am trying to provide the relevant details to the SAP owners.

Answer
anonymous 2 years ago

https://wiki.scn.sap.com/wiki/display/TCPIP/Application+Server+ABAP was all I was able to find. Please pass on the information and let me know how it goes so that I can add the link into our documentation.

0
Fixed

Error in doco

Eddie Kirkman 2 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 2 years ago 1
Answer
anonymous 2 years ago

Thanks for letting us know Eddie, I've updated the documentation.

0
Answered

SAP version analysis

Eddie Kirkman 2 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 1 year ago 3

The prerequisites for SAP connector (https://unifysolutions.jira.com/wiki/display/IDBSAP51/Prerequisites) state that:

An implementation of Identity Broker for SAP ERP Human Capital Management requires version analysis as the ABAP modules are developed against a specific version of SAP and service pack.
Please contact support@unifysolutions.net for module version compatibility.

Any idea what information I will need to provide to support?

Answer
anonymous 1 year ago

I should also point out that we state that SAP must be v4.6c or greater (see here), which as far as I know is still correct.

0
Answered

Version of IdB for SAP

Eddie Kirkman 2 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 2 years ago 2

Looking at testing the SAP connector for IdB at a customer (in a DEV lab) and getting a little confused as to what versions I should use. I was going to go with IdB 5.1 RC2, but can only find one msi file under https://unifysolutions.jira.com/wiki/display/SUBIDB/Downloads and when I run it it is the x64 version.

The prerequisites for SAP HCM connector v5.1 state that the 32 bit version of Identity Broker must be used https://unifysolutions.jira.com/wiki/display/IDBSAP51/Prerequisite

Where do I get the 32 bit version, or do I need to select an earlier IdB version (e.g. 5.0.4)?

Answer
anonymous 2 years ago

It's referring to the 32-bit executable, not the installer. The x64 installer (now the only one available in Identity Broker v5.1+) contains the 32-bit and 64-bit executable.

0
Fixed

SAP error generated when running a full import on Employee connector - Incomplete logon data

Joe Varkey 8 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 3 years ago 7

When attempting to run a full import on Employee connector the following error is produced:

20110221,03:50:29,Logging Engine,Logging Engine,Information,Log file started.,Minimal
20110221,03:50:29,Change detection engine import all items started.,Change detection engine,Information,Change detection engine import all items for connector Employee Connector started.,Normal
20110221,03:50:31,Change detection engine import all items failed.,Change detection engine,Warning,"Change detection engine import all items for connector Employee Connector failed with reason An error occurred attempting to connect to the SAP system, received : SAP.Connector.RfcLogonException: Incomplete logon data.
at SAP.Connector.Connection.Open()
at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open(). Duration: 00:00:01.7187500
Error details:
Unify.Communicators.SapHRCommunicator.SapHrCommunicatorException: An error occurred attempting to connect to the SAP system, received : SAP.Connector.RfcLogonException: Incomplete logon data.
at SAP.Connector.Connection.Open()
at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open()
at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.Open()
at Unify.Communicators.SapHRCommunicator.SapHrCommunicator.GetEmployees(String statusType, DateTime startDate, DateTime endDate, String infoType, IEnumerable`1 subTypes, IEnumerable`1 employeeIdRecords)
at Unify.Connectors.SapHrEmployeeConnector.ProcessGetEntities(IEnumerable`1 employeeRecords)
at Unify.Connectors.SapHrEmployeeConnector.GetAllEntities(IStoredValueCollection storedValueState)
at Unify.Framework.ConnectorToReadingConnectorBridge.GetAllEntities(IStoredValueCollection storedValueState)
at Unify.Framework.EventNotifierReadingConnectorDecoratorBase`1.GetAllEntities(IStoredValueCollection storedValues)
at Unify.Framework.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Framework.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.JobBase.Run()
at Unify.Framework.MutexJobDecorator.Run()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)",Normal

0
Answered

Can not run SAP Connector - BadImageFormatException

Richard Courtenay 6 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 3 years ago 3

I get the following error when trying to perform a Full Import of the configured SAP Employee Connector

20121121,01:02:23,Change detection engine import all items failed.,Change detection engine,Warning,"Change detection engine import all items for connector Employee Connector failed with reason An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B). Duration: 00:00:00
Error details:
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.Communicators.SapHRCommunicator.SapHrCommunicator.GetEmployees(String statusType, DateTime startDate, DateTime endDate, String infoType, IEnumerable`1 subTypes, IEnumerable`1 employeeIdRecords)
at Unify.Connectors.SapHrEmployeeConnector.ProcessGetEntities(IEnumerable`1 employeeRecords)
at Unify.Framework.ConnectorToReadingConnectorBridge.GetAllEntities(IStoredValueCollection storedValueState)
at Unify.Framework.EventNotifierReadingConnectorDecoratorBase`1.GetAllEntities(IStoredValueCollection storedValues)
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

I originally had the x64 version of Identity Broker installed and later realised that this is unsupported by the SAP Connector. Uninstalled it and went with an x86 version, as well as the x86 installer of the SAP connector. The net rrsult being that my environment has:
[*] Identity Broker 3.0.7.6 x86
[*] Identity Broker for SAP HCM 3.0.1.3 x86

I've attached my connector config.

The error appears to be identical to that reported at https://unifysolutions.jira.com/browse/ALDMLS-20 for previous Identity Broker versions.

After failing to resolve this in the DSEWPaC environment, I installed an x86 version of Identity Broker locally and the SAP connector and reproduced the error on my own system.

0
Answered

SAP Connector v4.1: BadImageFormatException

Huu Tran 5 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by Curtis Lusmore 1 year ago 3

1. Deployed IdbV4.1
2. Deployed SAP connector v4.1
4. Cut and paste to ConnectorEngine config file from v308 working config files
5. Open idb admin page and found the following eror:

20131007,01:43:40,UNIFY Identity Broker,AgentEngine,Warning,"The test of agent somerset.its.monash.edu.au SAP HCM Agent failed with message 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.Product.IdentityBroker.SapHrCommunicator.Open()
at Unify.Product.IdentityBroker.SapHrCommunicator.TestConnection()
at Unify.Product.IdentityBroker.AgentEngine.Test(Guid agentId).",Normal

Config file and log file attached


Unify.Product.IdentityBroker.ConnectorEnginePlugInKey.extensibility.config.xml
UnifyLog20131007.csv
Answer

As discussed over the weekend, this is due to the prerequisite of running Identity Broker in 32 bit mode for the Identity Broker for SAP HCM connector.

0
Answered

sapConnector timing out in 64bit mode

Monash 4 years ago in UNIFYBroker/SAP ERP Human Capital Management • updated by anonymous 3 years ago 14

Trying to do a full import on multiple SAP connectors in 64bit mode..

Change detection engine import all items for connector sapOrgUnit failed with reason The request channel timed out while waiting for a reply after 00:00:59.9960936. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.. Duration: 00:01:00.1614898

Unify.Service.Connect.exe.config