New BI Launch Pad Customization in SAP BI 4.2 SP5

A new and much welcome enhancement for the BI Launch Pad logon screen.

Although SAP is spending most of its analytics budget developing SAP Analytics Cloud, innovation is still happening on the BI Platform. In SAP BusinessObjects BI 4.2 SP5 (released in December 2017), SAP has introduced a new property for controlling the behavior of the Authentication drop-down box on the logon screen.

The behavior of the logon screen can be customized by copying the default file from C:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF\config\default to the adjacent directory C:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF\config\custom (see my original article about BI customization, Customizing SAP BusinessObjects BI 4.1 and BI 4.2).

A new property- logon.authentication.visibleList– now joins authentication.default and authentication.visible that controls which authentication types appear in the authentication drop-down list. By default authentication.visible is set to false, but most organizations have to set it to true so the Administrator can choose Enterprise authentication and everyone else can choose something like Windows AD, LDAP or SAP authentication.

logon.authentication.visibleList property for BI Launch Pad customization

Here is how the default list logon.authentication.visibleList=secLDAP,secWinAD,secSAPR3,secOraApps,secPSE1,secpsenterprise,secSiebel7,secEnterprise appears.

SAP BusinessObjects 4.2 SP5 BI Launch Pad customization

The new logon.authentication.visibleList parameter not only controls which authentication types are displayed, but also the order(!) that they are displayed in. As an example, I’ll move secEnterprise from the beginning to the end of the list.

SAP BusinessObjects 4.2 SP5 BI Launch Pad customization

And here’s what it looks like when I shorten the list to only the desired authentication types.

SAP BusinessObjects 4.2 SP5 BI Launch Pad customization

IMPORTANT: Remember that you must copy the contents of C:\Program Files (x86)\SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF\config\custom to C:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom before applying any patches, as the latter is the location the patch installer will redeploy web applications from. I also recommend keeping copies of any customized files on a project intranet or some other location that isn’t a SAP BusinessObjects server.

This small enhancement to the BI platform is a big deal that enables BI teams to simplify the interface, reducing both human error and help desk calls. I’m eagerly looking forward to additional BI platform enhancements that we’ll see later this year in BI 4.2 SP6 (July 2018 timeframe) and BI 4.2 SP7 (December 2018 timeframe).

State of the SAP BusinessObjects BI4 Upgrade – February 2018

SAP BusinessObjects 4.1, SAP Lumira 1.x and SAP Design Studio 1.x maintenance all come to an end in 2018. Here’s how to plan for the future.

It’s been a while since I’ve written one of these “State of the SAP BusinessObjects BI4 Upgrade” articles. In fact, I didn’t write one at all during 2017. But there are some key events happening in 2018 that are going to affect BI strategy for many SAP customers.

Read the State of the SAP BusinessObjects BI4 Upgrade – February 2018 on the SAP Community site.

I wrote the article one week before Michael Flannagan posted his Deeper Look into SAP’s BI and Analytics Strategy, but the points are still valid for SAP customers using the SAP BusinessObjects Business Intelligence suite.