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()

CloudBroker requires the following:

• SSL on all communication

IDBAD will fail if the end-point address (a public DNS entry) is different to the certificate supplied by the AD end-point, something that is entirely likely to happen if a customer cannot use their NAT to set up SSL and terminate at that address. For example:

IDBAD is set to connect to unify-demo-idbchrslite-1-ad.cloudapp.net, however the AD certificate is issued by the domain CA which makes the certificate idbpc21-ad.demo.unifysolutions.net.

The AD connector should permit the certificate to be determined by a name in the our configuration. The certificate must still be valid against the local machine certificate store.

From Bob Bradley:

Leading on from Event Broker, how about a mobile version of Event Broker with monitoring/alerting built in? Product roadmap?
Thinking of FIM custodian wanting peace of mind – clearing sync bottlenecks while out on the road such as restarting the service after an outage.
Explain my thoughts a bit more later … but prompted by a Microsoft email plugging “Prism” for developing apps for the Microsoft equivalent of the IPhone AppStore.

Receiving the same error as mentioned in SALMAT-23..

Attempted to clear the XML_FILE_PATH value as mentioned by Patrick Johannessen - as a result, Aurion defaults back to a local path.
When setting the path still receiving the permission error mentioned above.

Which service account should have permissions to the XML_FILE_PATH?

I understand this an in old issue and may be stretching memory - But any help would be appreciated

Whenever I try and access the "PlugIns" page I immediately get this error:

"An existing connection was forcibly closed by the remote host"

Default settings, console service and Visual Studio for the web project. Adam suspects it might be because I have no PlugIns installed.

The Delete Connector/Adapter Group button on the Connector/Adapter page is raised slightly above the neighbouring icons. The Delete Adapter Group button also has the wrong tooltip text.

The is operative transformation functions well when a start and end date are specified. However, if the end date is not specified, as is common in many systems with position information, an employee with a start date in the past is considered not operative. The transformation should be updated to consider a null end date DateTime.MaxValue or equivalent.

A few things:

What I feel is missing with IdB is the ability to control it via Event Broker. With the improvements to EvB's scheduling, it would be great to be able to use it to run synchronisations in IdB.

It would be a great thing to export IdB config into a human readable format, or have a parser that can process an export file for inclusion into documentation in a similar fashion to the MIIS documentation toolset in the MIIS resource kit.

Also, please, please, please that XML image node must go!

I understand from the doco that "polling " means a delta import from the connected system - true ?
We will need a connector built for DBB CSO and there will be 16,500 students to import from source.
It makes sense to build this new connector with delta import (and full) from connected system meaning "polling"
Which current IB connectors support polling?
Is building a new SQL connector with polling straightforward for the PG?

TIA

I have developed some generic XSLT stylesheets while working on FIM @ DEEWR to generate documentation for both Event Broker 3.0 and Identity Broker 3.0. These stylesheets are designed as an extension to the standard generated FIM documentation by utilizing the same "Object Visualizer" Powershell/XSL/HTA tool that is freely downloaded from the FIM Microsoft TechNet website (follow references to this tool from the FIM JIRA project).

The latest version of these XSLT documents are available from myself on request.