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.

EVB 3 remains hosted at localhost regardless of hostname config.
Hi Guys,
We're having issues with EVB onsite at APRA today.
It's installed in the self hosted configuration, with the following current config:
applicationPath="..\Web"
hostname="sydprdfim02evb"
port="8081"
Despite multiple attempts at different hostnames, the interface remains hosted at http://localhost:8081
Am i missing something?

Timestamp in Log
Time Stamp in log is showing 01:00 also for 13:00. How can I change that? I would like to have 1PM displayed as 13:00.

About page has no link to EBSUB (Subscriber downloads)
The About page has a link to PUBEB, and is the most likely landing point on our site for a client (or PS staff!) looking for the latest downloads for EvB. A link on the About page to the SUBEB site and/or a link from PUBEB to SUBEB would be very helpful indeed. It all makes sense when explained to you or you work it out yourself, but navigation is still less than intuitive for the unfamilliar.

Revisit installer package naming
For the next minor version, the installer package names should be revisited to ensure that they are in line with the branding objectives of UNIFY and the trademarked names for the product.

Default retry settings
The default value settings for retries need to be reviewed and changed to optimise service performance ... e.g. the default retries for ANY export run profile operation (where the outgoing pending check operation is used) should be zero, since the outgoing pending criteria check will occur again anyway, and retry logic will only clog up the processing queue. Similarly for most inbound operations ... in fact very rarely do we want retries to occur at all. Maybe there are some occasions where we need it, but this is turning out to be mostly redundant.

Merge Existing PowerShell operations into a single PowerShell Script operation
There are currently three Power Shell operations which have not been clearly separated (namely with distinguishable use cases).
These three are the PowerShell Execute, PowerShell Function and PowerShell Script operations.
Merge the PowerShell Execute and Function operations into the Script operation through upgrades.

Ability to add operation lists without needing menu
As requested by Shane Day, it can be annoying having to open the operation list menu to add operations. It could be made easier by having a line or rectangle appear when mouseover any position in the tree and allow the user to add an operation that way.

Implement support for Active Directory notifications
Support for subscribing to Active Directory notifications to eliminate need to poll AD.

Add ability to run operation lists from within operation lists.
This could be achieved as either an Operation, or a step-type on Success/Fail etc.
Customer support service by UserEcho