Confirm database operation can execute an Oracle stored procedure. The client stored procedure has two string input parameters and no output.

Download: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-1968077.html
Example data: http://www.java2s.com/Tutorial/Oracle/0540__Function-Procedure-Packages/Creatingaprocedure.htm

The following are a series of views for which invalid routing ids / values will cause errors:

• Edit action of the Agents controller, specifying a non-existent agent id or incorrectly formatted Guid. e.g. "Test"
• Create Schedule action of the Operation controller, specify a non-existant id or incorrectly formatted Guid.
• Operation Lists action of the Group controller, specifying an incorrectly formatted Guid.
• Logs action of the Logging controller, specifying an incorrectly formatted DateTime e.g. "Test"

An enquiry was received asking about Event Broker and auditing, in addition to other clients using Event Broker for transforming FIM audit drop files.

Please create a new plugin operation to transform FIM audit drop files (DSML).

Have a look at [~bob.bradley:Using Event Broker to archive exported changes for an MA].

Consider making a generic Xslt plugin. Supported input file type should be DSML; output html, W7 (TCIM) (csv and xml), configurable xslt.

The output files could be using built in xslt files, or possibly allow for other methods of transformation (a xslt transformation might not be the best method to create a csv).

This is related to task 236 https://unifysolutions.jira.com/browse/EB-236

Firstly I'd like to see a "test connection" button on the creation page, rather than going through with incorrect settings and finding out after the fact.

Secondly is there any reason you have to enter the password twice on the AD Agent and LDAPDirectory Agents. We aren't creating a new password, just authenticating, so to my mind you should only need to supply the password once.

I have managed to successfully configured

• Identity Broker Agent
• The corresponding Check Operation for Identity Broker Changes operation
• The run profile operation for "Delta Import and Delt Sync"

The Operation List is enabled and working.

When there is a change in the Identity Broker and the Operation being carried out successfully I cannot find any corresponding log entry for the Operations being performed in the log file.

I thought be perhaps by default it does not have the log filter level for logging this information. Thus I modified the Unify.Product.EventBroker.LoggingEnginePlugInKey.extensibility.config.xml to include the severity for "All" as below:

<?xml version="1.0" encoding="utf-8" ?>

<LoggingEngine changeId="

" logDaysKeep="5" filePrefix="UnifyLog">
<LogWriter name="AsyncLogWriterComposite">
<logFilter name="Severity" severity="All" />
<LogWriter name="Console" />
</LogWriter>
</LoggingEngine>

And restarted the Event Broker service.

In the FIM Sync Manager there are corresponding of FIM Operation log with status as success.

I still could not find any log entry in regarding to the Operation being performed in log file.

Did I missed something here or is this by design?

As much as possible, Management Studio should be populated with tooltips and page descriptions to explain:

• Parameters, describing their use, and where applicable, their format
• Descriptions of plugin, group and agent purposes
• Page titles should also be used on all pages

There is nothing that stands out about an exclusion group compared to a normal group on the groups page, or on the page of the group itself unless it has trigger members. The UI representation of the group should be updated with some sort of mark to distinguish it as an exclusion group, both on the groups page, and on the page of the group itself.

The FIM/ILM AD Management agent allows the nomination of a list of specified DCs in connection priority order, to override the default arbitary selection of any DC on a domain. When the AD Sync Changes plugin is used in a multi DC environment where there are even minor replication delays, the plug-in can fire before the DC to which the AD MA performs the delta import (change log read) has been updated, causing the change to be missed (in particular object deletions it seems). The above scenario could be mitigated if the plugin configuration was allowed to mimic this exact capability, thereby reducing (if not elminating) the possibility that changes are missed.

For more details refer to the blog post below.

Although ILM pending exports are present for an MA ("CIT AD") and a corresponding Outgoing Operation List is defined for this MA specified with (default) "Autorun on Outgoing Provisioning Pending", the export run profile "E" for this MA is never fired. The log (in Debug mode) shows no pending exports or any errors.

I don’t know what the solution would be but if you change the web config to make evb hosted at a different address or port then the shortcut to event broker becomes out of date.