OK...Here goes my dissertation on how Managed Reporting works...
Managed Reporting let's you provide end users with as much or as little WebFOCUS funtionality as you choose. A repository of information is created containing info on users, priveledges, roles, groups, domains, and reporting objects. The repository can be file based (default), or in 7.1.x and above be an "external" repository in an RDBMS, active directory, or LDAP using the MR Realm Driver. Note that even in an eternal repository situation, portion of the repository (reporting objects) remain in the file based system. Expolring each of these components a bit further;
1. Priveledges are the functional items a user can perform. ie. Create a report from a reporting object, Save a report, Share a report, Save entered parameter values, Schedule reports, Access the Report Output Library, Create new data connections, Create new reporting objects, etc.
2. Roles are groupings of priveledges. There are predefined roles, or you can create custom roles. The default roles are MR Administrator, Developer, Analytical User, User, and Run Only User.
3. Users are assigned roles and thus inherit those priveledges.
4. Groups are groupings of users who will be assigned to one or more domains.
5. Domains are functional areas that will contain common reporting objects, reports, and users. Examples could be to mirror your organizational structure ie an Accounting Domain, an HR Domain, a Sales Domain, etc. If the MRE is for external users the Domain structure may look like...Customer1 Domain..Customer2 Domain...Customer3 Domain, etc.
6. Reporting objects are either fully functional reports that a developer has created and placed in the MRE environment for users to click on and run, or reports that accept input parameters from the user at run time, or reports that a user can add fileds to, change sort orders, display characteristics, etc, or they are blank objects that only provide a lsit of fields to the user giving the user the responsibilty to created their own report based on the filed list. Reports can be published as "Standard Reports", which are run only, Reporting Objects, which can be used by certain user/roles to base a new report on if needed or desired. A report can be shared to other domain users (all users in the domain will see the shared report) so it can be run by other users, or can be saved by a different user as a "My Report", which then becomes a new reporting object for that user.
The tool used for MRE/BID report customization is Report Assistant (RA). Run as either an HTML or Applet version, RA is a scaled down version of a report painter, but it does allow a lot of fuctionality. A developer can place defines, joins, and where statements in to a reporting object that a user has no access to modify or even view. Users can then add their own defines, computes or filters (based on their priveledges), to the object to create their own report. All reports/objects created from an existing object inherit all of those "hidden" defines, joins, and filters. If the "base" object is deleted, all the reports created from it will be broken.
The MRE/BID environment is based on FOCUS Master File Descriptions that are created against your data which means columns can be excluded from use by the users. It also means SQL pass-thru is NOT an option.
Users can access this environment through either MRE or BID. BID allows you to customize the look and feel of the interface and is HTML based. You can customize logos, colors, tool sets, and menu options in BID.
Hope this short dissertation helps, if there are items I didn't touch on or other questions, please let me know.
If any else has something to add, please do...this is a large subject.
Kevin
WF 7.6.10 / WIN-AIX