BusinessObjects XI - Prompt for Block Type

BusinessObjects Web Intelligence reports can’t prompt the end users to display the data in table or chart on a report using its built-in features. However, this can be achieved by using a sophisticated technique that is demonstrated below.

• Prompt for Table or Chart when refreshing a document
• In Desktop Intelligence, this was easy with “Hide Block”
• But we can make it work in Web Intelligence, too

• We start in Universe Designer, and create a Prompt object
• Disclaimer: This object will not parse, but will work when used with other objects

• Next, we create a query, using the new object

• None of those objects are used in the report
• Create 2 variables for each universe object:

Chart Year: =If(UserResponse("Display Data in
Table or Chart?")="Chart";[Year])
Table Year: =If(UserResponse("Display Data in
Table or Chart?")="Table";[Year])

• Create a table using the “Table” variables
• Create a chart using the “Chart” variables
• Set the Table and Chart to not be shown when empty
• Place the chart on top of the table

The Result:

Criteria for Selecting a BI Tool – Thoughts?

Tool selection is an important part of the Business Intelligence implementation process and many software companies have flooded the space in recent years. At Guident, we have implemented hundreds of BI solutions using technologies from many of the industry leading BI software vendors. All of the leading BI software products have very powerful features and Guident believes they can be used successfully when implemented properly. However, it does require a very experienced BI professional to evaluate the differences and determine what factors really impact a given implementation. Guident has our own set of criteria to help our clients with their tool selection, but we’d like to hear from you. Let us know what criteria you are considering or have considered when evaluating a BI tool for your enterprise reporting needs.
Leave us a comment and we will incorporate your criteria and thoughts into a follow-up blog entry. We’ll collect and consolidate your comments into one of the following 6 categories:

1. Semantic/Metadata layer
2. Reports
3. Dashboards
4. Security
5. Advanced Querying and Ad hoc Reporting
6. Out of the Box Solutions

When leaving comments, please let us know the criteria you are using to evaluate a tool and the category your criteria fits into.

BusinessObjects XI and OpenLDAP

Supported BOXI authentication methods / plug-ins


BusinessObjects 3.1 supports three modes of user authentication:

1. Default Enterprise authentication which allows for complete user and security administration within the BusinessObjects Enterprise itself
2. Utilization of a LDAP plug-in that allows the BusinessObjects Enterprise (BOE) to add, sync and authenticate users with a 3rd party LDAP directory
3. Utilization of a Windows Active Directory (AD) / NT security plug-in to add and map users of an external database with those in the BOE.

This write-up provides a high-level overview of configuring BusinessObjects with OpenLDAP 4.1.17 on a Windows platform. BusinessObjects already has built-in plug-ins to support LDAP for Sun iPlanet Directory Server, Lotus Domino Directory Server, IBM Secureway, and Novell Directory Services (NDS). OpenLDAP is simply an open-source flavor of the user / group directory that coincidentally uses the same attribute mappings as Sun DS; for example:

It is important to note that attribute mappings must coincide between the LDAP directory and the BusinessObjects Enterprise for the authentication to work properly.

Now let’s review a LDAP structure that maps accordingly with the attributes above. In the example below, attributes are color coded to reflect how the mappings from the LDAP directory correspond to those set within the Central Management Console (CMC) of BusinessObjects:

Adding Dynamic LDAP Groups to The BOE
Once the source LDAP directory is configured properly, the LDAP Configuration Wizard under the Authentication section of CMC is used to configure BOXI. Enter all required information and when prompted to add groups, the full distinguished name (dn) of the dynamic LDAP group(s) must be entered as shown in the screenshot below.

Note: If there is no existing / corresponding Enterprise user account contained within the BOE, select “Create a new account for every added LDAP alias” when prompted for how new LDAP users and aliases are created. However, if Enterprise accounts exist and match exactly to usernames contained within the LDAP directory, select “Assign each added LDAP alias to an account with the same name.”

Managing Dynamic LDAP Groups within CMC
Once LDAP groups are synced with the BOE, they can be managed as with any other group contained in the Enterprise. Simply go to the Groups section in the CMC and set rights as needed. A recommended practice is to instantiate an Enterprise group and set the desired rights on it. Next, make the LDAP group a member of that parent Enterprise group so it inherits its rights. This allows any future LDAP groups to be added as needed, rather than setting rights explicitly on the new group itself.