MIM Event Broker Forum

Welcome to the community forum for MIM Event 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
Fixed

Create Operation List - descriptions

Shane Day (Chief Technology Officer) 14 years ago updated by anonymous 9 years ago 2

Public name of operation list

As opposed to private name?

0
Fixed

Updating operation list settings clears all operations

Matthew Clark 14 years ago updated by anonymous 9 years ago 3

After adding an operation list comment to an operation list, I found my check and standard operations had all been cleared from the list. The schedule remains untouched by the looks of things.

0
Completed

Minor correction and suggestion for Cassini configuration instruction

Shane Lim 14 years ago updated by anonymous 9 years ago 11

I find the information on this page, Configuring for use with Cassini is not as straight forward and also a small omission of the .xml part of the file name.

I recommend it is changed to something similar to below

Configuration

The Event Broker Web engine configuration details can be found within the extensibility file located in %Event Broker Installation Directory%\Services\Extensibility:
Unify.Product.EventBroker.WebEnginePlugInKey.extensibility.config.xml

0
Completed

Configure Event Broker v3.0.0 for Cassini WebServer

Shane Lim 14 years ago updated by anonymous 9 years ago 6

I am trying to follow the instruction on Jira at Configuring for use with Cassini to deploy Event Broker v3.0.0 UI to Cassini WebServer v2.0.8.

  • I have download and installed Cassini WebServer v2.0.8
  • There is no instruction on how to deploy Event Broker's UI component on the same machine as the Event Broker's service (which I believe is located in the default installed location C:\Program Files (x86)\UNIFY Solutions\Event Broker\Web).
  • I opened the Cassini WebServer Manager, http://localhost:7756/ in IE
  • I have tried registering the appliction at C:\Program Files (x86)\UNIFY Solutions\Event Broker\Web\Global.asax using port 8080). But when accessing it I got the following error
    Server Error in '/' Application.
    --------------------------------------------------------------------------------
    
    Runtime Error 
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed. 
    
    Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
    
    
    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="RemoteOnly"/>
        </system.web>
    </configuration>
     
    
    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
    
    
    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="On" defaultRedirect="mycustompage.htm"/>
        </system.web>
    </configuration>
     

I am not certain whether this error is due to the issue with I cannot start the Event Broker service, see EB-263.

My main concern here is getting the right documentation/instructions ready and available so that I spend the minimal amount of time to get a Event Broker v3.0.0 deployed.

0
Answered

Installing the Event Broker Portal Workflow unclear where this should be installed

Shane Day (Chief Technology Officer) 14 years ago updated by anonymous 9 years ago 2

EB300:Installing the Event Broker Portal Workflow - it is unclear where this should be installed. On the FIM Portal server, I presume, however it would be good if this was clearly specified.

0
Fixed

Alert Icons Missing In Opera

Richard Courtenay 14 years ago updated by anonymous 9 years ago 5

Minor stuff, but just noticed the alerts dont have the icons under Operas browser

0
Fixed

Maximum string content length quota unhandled

Tony Sheehy 14 years ago updated by anonymous 9 years ago 1

If a string is entered - that is not caught by validation - that surpasses the Maximum string content length of 8192 an error will be thrown.

To reproduce this enter a description of that size into the Group description field.

0
Fixed

Malformed Logging search criterion causing perpetual stall

Tony Sheehy 14 years ago updated by anonymous 9 years ago 4

If a search criterion that will cause an exception is provided under Logging, it will not be caught / thrown / displayed and will hang on 'Processing'.

For an example, to recreate this behavior enter the following into the search criteria:
"<html>

0
Fixed

Incorrect and missing tooltips / captions and descriptions

Tony Sheehy 14 years ago updated by anonymous 9 years ago 2

The following are a list of tooltips and descriptions that need to be updated:

Incorrect

  • In the Check Operation drop-downs, 'SQL Changes' should be 'SQL Server Changes' and 'SQL Commit' should be 'SQL Server Commit'.
  • The page titles for both the LDAP Commit and Changes need to be altered to reflect their new names.
  • The 'No agents' prompt on the LDAP Changes page needs to be altered to reflect the revised name.
  • Both the views of the respective Group and Operation Lists actions of the Group controller require page titles.

Missing

  • The Home page needs a label and link detailing a situation in which no operation lists exist.
  • The Groups page needs a label detailing a situation in which no groups exist.
0
Fixed

SQL Server Changes operation cannot be added

Tony Sheehy 14 years ago updated by anonymous 9 years ago 2

SQL Server Changes check operations cannot be added to operation lists; which was subsequently caused by changing the plugin name of the shared view information of the SQL Server Changes operation and SQL Server execute operation.

The SQL Server changes and execute operations need to depend on separate view informations objects both inheriting from the original view information as a base class; where each unique view information would specify the plugin name separately.