David Taylors' Business Intelligence Blog

SAP BusinessObjects delivers great Business Intelligence solutions so that organizations can report off their existing data sources.  But what is the point of reporting of data that isn’t accurate anyway?  Although it is true that accurate data is pretty useless if you can get access to it, the converse is also true.  What is the point of a great end-user enabled system that includes inaccurate data?

My Top 5 Customers – Really?

Take a look at the report below.  (If you want to download this Xcelsius Model it is available below.)

Who are my top 5 customers?

Top 10 Customers

Did you say:  General Electric, Procter & Gamble, PepsiCo, Home Depot and Walmart?

Well, Sorry.  I’m afraid, that would be incorrect.

You see, what often happens in real-world situations is that organizations think they have more customers than they actually do.  That’s because within their CRM system, employees are able to add the same customer multiple times with multiple spellings.  This has happened in our case as well.  Let’s apply BusinessObjects Data Quality to this real-world situation.  With SAP BusinessObjects, you can take company names, customer names, addresses, etc. and standardize them, e.g. UPS = United Parcel Service = UPS Inc., WalMart = Wal*Mart = Wal-Mart, First Commerce Bank = 1st Commerce Bank.

My Top 5 Customers – Really!

Let’s have a look at this same report with Data Quality applied:

Top 10 Customers with Data Quality

Do you see the changes?

Walmart has jumped up into second place and United Parcel Service is now in fifth place.  We can also see the our profitability at Walmart is higher than we thought (26.8% instead of 18.7%) and United Parcel Service is actually lower that we thought (28.6% instead of 26.3%).  When you are making business decisions off your corporate data, it’s imperative that it is accurate and complete.

Here is the source data behind this chart and you can see how the lack of standardization has led to the incorrect results.  I have highlighted the offending records for you:

Raw Customer Data Behind the Top 10 Customers Report

Once we apply data quality and standardize the names, the order changes and I have a new top 5!  Often times our biggest customers, vendors, partners and products don’t get the credit they deserve for contributing to our success.  Once you’ve got data quality, you can know that you know that you know, the true numbers.

I’ve introduced this topic under the name of Data Quality, but Data Quality really falls under the broader topic of Data Stewardship or Data Governance.

You Don’t Know What You Don’t Know

The bottom line around data quality is that you don’t know what you don’t know.  If you manage a data warehouse which accepts feeds from dozens of systems, then it’s highly likely that you have a data quality problem and don’t even know it.  It’s a critical aspect of data warehousing.  Operational systems are notorious for bad data.  Last year, I read an excellent, practical guide to data quality called, Data Quality Assessment.  The book itself does not endorse a specific software vendor but all the principles found in the book would apply to any organization looking to improve their corporate data quality.

Downloads – See It Live

If you’d like to see an Xcelsius model of this chart live, I’ve made it available for download.  The source code for the .xlf is also available:
http://trustedbi.com/files/Importance of Data Quality.zip

Truth Is Stranger Than Fiction

Sometimes in life you run across situations that are hard to believe.  Here is an example where truth is stranger than fiction.  When you want to get someone’s attention when it comes to data quality, just tell them this example.  This data quality situation really happened and the results were disastrous.  This video is from Timo Elliott. When you click on it, it will take you to his website:

Timo's Data Quality Presentation (2min)

Do you have any good stories to share?  I’d love to hear them.

«Good BI»

When installing any SAP BusinessObjects software, I find that it’s always best to have WinRAR nearby.  Just as a spoonful of sugar, it helps the medicine go down, WinRAR give you the control you need when disk resources are tight.  I was reminded of this again when I downloaded the new version of Xcelsius 2008 SP3.  I couldn’t wait to see all the new features that everyone is talking about.  But first things first.  The best way to do this is to start with WinRAR.

Why WinRAR?

WinRAR is an archiving tool.  It is a great way to get around the annoying habit that that SAP BusinessObjects has of unzipping all the files into a temporary directory somewhere and then launching the setup.exe file.  I hate that.  I want to tell the installer what to do every step of the way.  Let’s take the new Xcelsius 2008 SP3 for example.  When you execute the archive exe file, it unpacks all the installation files.  Where does it put them?  Does it look at your TEMP or TMP environment variables? No, not necessarily.  It puts them in your C:DOCUME~1AdministratorLOCALS~1Temp directory.

Maybe it’s me, or maybe it’s Murphy’s Law.  I don’t know.  What I do know is that the BusinessObjects Installation exe files that you download from the Service Portal can be unzipped directly using WinRAR.  This means I don’t have to rely on the self-extraction exe.

WinRAR is easy to find.   If you want to use the latest version you can download it from the WinRAR website and you will receive a temporary license.  If you like it, you can buy it.  Alternatively if you like it but don’t need all the new features, you can get a free license here.

I am running WinRAR 3.61, but WinRAR 3.5 is fine too.

Extracting the BusinessObjects Software

Once WinRAR is installed, it will create convenient right-click menus.  In this case let me extract all the files from the new xcelsius2008sp3.exe file I downloaded from the SAP portal.  If I right-click on the install file, I can choose to Extract the files.   50% of the time I use Extract Here, the other 50% of the time I use the item I have selected below: Extract to {directory}, in this case Extract to xcelsius2008sp3.

Right-click Menu, Extract To

I like this option the best because it will extract files to a convenient location where I can access this easily.  When the extract begins, it will create the subdirectory if one does not already exist.

After the files are extracted, I can manually start the setup.exe myself.  Do remember that it does take a few minutes before you see the first installation splash screen so be patient.  In you are unsure, always check your task manager processes before starting it again.

Now it’s time to enjoy all those new features available from the SAP Download site.

«Good BI»

Have you ever been confused by directions or road signs?  Sometimes information doesn’t bring clarity.  Hopefully this blog will bring some clarify to potential issues you might encounter in your upgrade to SP2.  I can’t believe this is my 4th post about the subject.

Issues When Moving From Fix Pack 1.6+ to SP2

I made the move to SP2 several weeks ago from XI 3.1 FP 1.3, but what I have since discovered is that not everyone’s journey has been so straight forward.  If a BusinessObjects system was using XI 3.1 FP 1.6 or later, then you may run into issues after you upgrade to SP2.

It seems that at the time SP2 was being built, all the fixes up to FP 1.5 were included; however there have been a number of additional FixPack releases SAP BusinessObjects XI 3.1 since then.  SAP has released Fix Pack 1.6, 1.7 and 1.8.  These three releases included DLLs that were newer than the DLLs in the SP2 release because they contained fixes that were not originally in SP2.  If this is the case for you will want to move to Fix Pack 2.1 immediately.

What happened?

What I’ve discovered is that due to the desire to keep the size of Service Packs as small as possible, the service pack does not overwrite all the DLLs on the system.  Instead, the service packs looks at your system and only replaces those DLLs which are older than the DLLs within your BusinessObjects XI 3.1 environment.  This means that if you upgraded to FP 1.6, 1.7 or 1.8, some DLLs will be newer than the DLLs contained within SP2.  This can introduce incompatibilities.

For example, if you use WebIntelligence, you may notice that after sometime the WebIntelligence Server stops functioning and you get the following message when opening a WebIntelligence document:

Cannot Initialize Report Engine server: (Error: RWI 00226) (Error:INF)

The Good News

The Good News is that engineering has already identified this issue and has fixed it through the release of Fix Pack 2.1.  If you read the release notes of Fix Pack 2.1, you will see the following:

BusinessObjects XI 3.1 and Crystal Reports 2008 Service Pack 2 Fixed Issues
This Service Pack can only be applied on top of BusinessObjects
Enterprise XI 3.1 / Crystal Reports 2008 SP1. This Service Pack
includes all XI 3.1 FixPacks up to 1.5. Note If you install XI 3.1
SP2 in top of FixPack 1.6 or later, reinstall the latest 2.x FixPack.
Each machine in your deployment must be updated separately with
the patches you require. A separate patch is available for each
BusinessObjects product that has a standalone installation.

There it is.  Tucked into the release notes of Fix Pack 2.1 it explains that if you are on a later fix pack, you need to install Fix Pack 2.1.  I would welcome your suggestions to pass on to the BusinessObjects engineering team of ways to avoid this in the future.

«Good BI»

Over the last several months, we’ve worked to make customers aware of one of the major issues with the latest upgrade within the XI 3.1 product stack.  The main issue has been that the upgrade is simply too slow.  Way too slow.  I knew that the SAP BusinessObjects product development team has been working on resolving this issue and we have some great news.

Recap

The problem only affects Windows and only the BusinessObjects Enterprise package. The problem arises due to limitations of the Microsoft Patch (msp) technology performing disk checking when managing large numbers of files… and the BusinessObjects Enterprice package has lots of those! When run in silent install mode, the installation is significantly faster, but this advantage only works on some versions of Windows (those using Microsoft Installer 3).

RE-RELEASE is available!

If you have an older copy of the SP2 release on your servers, you may just want to update them.  If you go to Service Marketplace, you will see that there is an updated version of the Service Pack (Server+Client) available for download.  These downloads have been updated.

Click image to enlarge

So was the issue completely fixed?  Well, no… not exactly.   In order to get the installer to run fast in interactive mode, either the installer would have to be modified to use the older msi technology or Microsoft will have to fix the issue.  In the meantime, what SAP BusinessObjects has been able to do is to give us an updated version of the installer that is always fast when run in SILENT MODE…. that is… with all versions of Microsoft Installer (3.0/3.1/4.0/4.5).  Therefore be aware.  You must continue to follow the silent installation procedures outlined in my previous posts, however you no longer have to be concerned with what version of the Microsoft Installer is on the Windows Operating System.

And if you are on Unix?  Well, this was never a problem in that case.  This problem only affects the Windows platform.

Thanks!

Finally, thanks to the teams at SAP BusinessObjects for getting this fix released.

«Good BI»

I wanted to write a quick follow-up post to the one I posted earlier about the BusinessObjects XI 3.1 SP2 install.  Now that I’ve done several I wanted to give you some additional heads up on some things.  This is what I’ve learned:

Be Careful of Language Packs

The install can take a long time even with the silent install – If you decided to just install all the language packs what you will find is that each language packs adds just under 30 minutes to the install time per language.  In other words, if you installed English, German, and French your installation will take almost a full extra hour.  The installation daisy chains the installations together.  First it will all the SP2 updates and the english language pack.  Next, it will install French and then German.

Comprende?

Is My Install Done Yet?

When running a silent install you can include the options /qn+ to have the setup.exe program inform you when the installation is done…

setup.exe /qn+ -r <responsefilepath><filename>.ini

there’s only one surprise.  The installer will information you that the installation is complete.  What it doesn’t tell you is that it will install the language packs next.  Yep that’s right… It’s done but not REALLY done.  But because it’s running a silent install you won’t know it.  This is related to the previous issue.  After the main installation completed, it tells you the installation is complete.  It THEN begins to install each of the languages packs.  If you look in the task manager you will see that msiexec.exe is still running.  Be very careful and make sure those language packs have completed before you start trying to clean up the install files.

Good Luck

The issue of the installation of the BusinessObjects XI 3.1 SP2 was a main topic of our recent GABOUG meeting.  There was a strong recommendation from customers to make sure and install the SP2 hotfix that came out just after the release of SP2.  I haven’t read through the technical notes, but apparently there were problems with some SAP universes getting corrupted.  This hotfix will solve that problem.

«Good BI»

Happy Friday!  Hope you’ve had a great week…

A Little Help from My Friends

Ever feel like you need a little help?  I do all the time… and I really appreciate all my other friends out in the blogosphere who help me along the way.  When it comes to working with SAP BusinessObjects, there are two things that I always have trouble finding from time to time.  Where do I find the SAP BusinessObjects Software and the Documentation?  There are lots of links to choose from within the SAP Service Marketplace and so you don’t accidentally get lost, I recommend you add two shortcuts to your browser..

All SAP BusinessObjects Software

For access to all releases of the SAP BusinessObjects Product Suite including all the EPM, GRC and Information Management solutions, go to:
http://service.sap.com/bosap-downloads

All SAP BusinessObjects Documentation

For access to all the documentation of all the current and past releases including release notes, user guides, administration guides, glossaries, reference guides, go to:
http://help.sap.com/businessobject/product_guides/

If you have some favorite SAP BusinessObjects links that you think others should know about, feel free to post them here as a reply to this post.

«Good BI»

I came across a recently technical support article that I felt was so important,  I wanted to pass it on to anyone and everyone who might be upgrading their SAP BusinessObjects XI 3.1 environment to SP2.  If you try the installation, BEWARE!  Without following the advice below you might find that it takes several hours!  Below are the instructions I gleaned for a recently published technical article.

SP2 Is Slow to Install

Installing XI 3.1 Service Pack 2 on a Windows environment may take a long time (several hours) to complete and here’s why.

• The problem is with the process of the MSP (Microsoft Patch) installer that we are using for the SP2 install on Windows platform.
• The install/validate check routine in this process takes approximately around 80% of the install time.
• When using this installer the process to find and replace a large amount of files takes a long time.

Workaround

As the main bottleneck in the Install process is a MSFT Install/Validate check routine, the workaround is to skip the check by performing a Silent Install
There is a significant reduction in the total time taken.   NOTE:  We can skip the check only on MSI 3.x., the silent install does not help on MSI 4.x.  Please refer to the installation guide for xi31_sp2_install_en.pdf and refer to page 21.

Regarding how to run in Silent mode:

1. We need to  generate an ini file firstly with the command line: setup.exe -w <response filepath><filename>.ini
2. Remember to EXIT OUT of the install once you get to the START INSTALLATION dialog box.  Once here choose Cancel.  Now your .ini file should be written out to the directory you specified.
3. Next,  run the silent install with the command line: setup.exe -r <response filepath><filename>.ini where <response filepath> is the path to the .ini file you created created in step 1.
4. You then need to run the silent install with the commandline:  setup.exe /qn+

Make sure and read through the installation guide BEFORE you continue.

This runs the installer with all default options and automatically redeploys the war files to the BOBJ-installed Tomcat

Caution:
Note that because the Install/Validate check routine is skipped in order to improve performance, there is a potential scenario where the machine may run out of resources e.g. lack of disk space, partway through the installation. In such a scenario, the system should be rolled back to where it was before originally, and the appropriate logs will be made (assuming logging was enabled).

Limitation of workaround

There were changes between MSI 3.x and MSI 4.x, such that the MSFT Install/Validate check routine is also always executed in machines with MSI 4.x, regardless of whether it is a GUI or Silent installation. Accordingly, the silent install does not help if the MSI 4.x has been installed on the Windows.  Regarding how to know the version of MSI installed on the computer currently, we may right click the file C:windowssystem32msiexec.exe, choose “Properties”, check tab “Version”, or you can run, from the commandlilne, “msiexec /?” and hit enter. There is no way to downgrade the MSI from 4.x to 3.x except re-installing Windows.

SAP Note 1356691 for the XI 3.1 Service Pack 2 Install and Deployment Guide PDF. The section for Silent Install begins on page 21.

Memorial Day was a great day to reflect on the sacrifices of so many for the freedoms and liberties will all enjoy. Thank you veterans!!

After attending a local Memorial Day Rememberance and Celebration, I spent some time cleaning my office and I came across an excellent article which I wanted to pass along.  So often when I talk to organizations about Business Intelligence, I ask them about their business requirements so that I can understand their current business pain.  All to often what follows is feature function laundry list of capabilities they are sure they can’t live without.  Time after time, the BI requirements given to software vendors are not tied to a specific business problem. This is a recipe for disaster.

The following article is an article from DM Review entitled, Business Requirements for BI and the BI Portfolio: How to Get it Right:
http://www.b-eye-network.com/print/6887

This article does a great job at pointing out the weaknesses of generic BI requirements and why functional requirements are not enough.  If you have BI requirements and are evaluating BI tools, I highly recommend you take a few minutes to read this article.

«Good BI»

At SAP BusinessObjects I work in the role of a Solution Advisor and I have a collection of Xcelsius dashboard examples.  I also receive new Xcelsius models from my colleagues from time to time.  Several months ago I ran across a strange problem with my Xcelsius powerpoints.  When I moved documents from one machine to another I began having problems openning these powerpoints and viewing my Xcelsius models.

Can’t be Activated in Aggravating

When opening powerpoint, I would see the following Windows error:

Some Controls on the Presentation can't be activated. They might not be registered on this computer.

I was left wondering if this was a problem with the new Powerpoint 2007, so an incompatibility between Xcelsius 4.5 and 2008.  After some research and an excellent article from the Xcelsius Journal, I was relieved to find out it was neither.  It was all about the flash viewer within Powerpoint.

Solving This Devilish Problem

Although I had long since upgraded my flash player within my Firefox browser, Powerpoint continued to hold on to the old flash version.  Although I upgraded my flash player within Internet Explorer, Powerpoint didn’t seem to see it.  Instead it was still using an old flash player and therefore I continued to get the message:  Some controls on this presentation can’t be activated.  They might not be registered on this computer.   It was so frustrating.  Eventually I was forced to manually perform a flash uninstall and a fresh reinstall.

Uninstalling Your Flash Player

For additional details about uninstalling your flash player, I recommend you refer to this article: http://kb2.adobe.com/cps/141/tn_14157.html

As a shortcut to the files referred to in this article, I have provided references to the Windows Uninstall programs here:
http://download.macromedia.com/pub/flashplayer/current/uninstall_flash_player.exe

Next, you will need to launch Internet Explorer and go to the adobe website.
http://get.adobe.com/flashplayer/

In some cases, you may want to manually download the installer for use offline.   Consider going to this site and downloading the flash player installer for manual installations.
http://get.adobe.com/flashplayer/otherversions/

Back Flashy Presentations

Now that you’ve upgraded the flash player referenced by Powerpoint, you can get back to viewing those flashy Xcelsius presentations.  In the future I would expect Microsoft and Adobe to fix this problem.  I hope I never have to see this message again:  Some controls on this presentation can’t be activated.  They might not be registered on this computer.

«Good BI»

[UPDATED 10/1/2010 - See Below]

I was recently involved with the configuration of Kerberos with a customer and as I was reading about it in the documentation, I realized that there were a number of areas that lacked the clarity I needed to understand what information SAP BusinessObjects needed to know about my environment.

The Service Account

Permissions are one of the first areas that might trip you up.  In my case I used the same user for the service account that you use for configuring the SIA and that has read access to Active Directory.  It will simplify things for you.  You should also make the service account a local admin on the Business Objects Enterprise Servers.  The service should be a non-dialog user.

Step 1 – Create the SPN

As a Domain Admin, Create the SPN for all of your CMS Servers.  You will need to create an SPN for the fully qualified domain name, as well as the short name.  In my case I have two machines which are running a CMS on each.  I will refer to these machines as cms1 and cms2.

Example:

SETSPN.exe -A BOBJCentralMS/cms1 serviceaccountname

SETSPN.exe -A BOBJCentralMS/cms1.mydomain.local serviceaccountname

SETSPN.exe -A BOBJCentralMS/cms2 serviceaccountname

SETSPN.exe -A BOBJCentralMS/cms2.mydomain.local serviceaccountname

(In the above example:  host – cms1 and cms2, domain – mydomain.local, username  - serviceaccountname)

Step 2 – Confirm the SPN

In the Windows Server Support tools you will find lfifde.exe.  You can use this to application to confirm that the SPN has been correctly associated with the username.

Example:

ldifde -d "dc=mydomain,dc=local" -r "servicePrincipalName=BOBJCentralMS*" -p subtree -l "dn,servicePrincipalName" –f C:ldifdeoutput.txt

When you run the command, you should see something like:

Connecting to "adc1.mydomain.local"
Logging in as current user using SSPI
Exporting directory to file C:ldifdeoutput.txt
Searching for entries...
Writing out entries..
1 entries exported

When you open C:ldifdeoutput.txt, you should see something like:

dn: CN=mydomain, serviceaccountname,OU=Service Accounts,OU=Accounts, DC=mydomain,DC=local
changetype: add
servicePrincipalName: BOBJCentralMS/cms1.mydomain.local
servicePrincipalName: BOBJCentralMS/cms1
servicePrincipalName: BOBJCentralMS/cms2.mydomain.local
servicePrincipalName: BOBJCentralMS/cms2

Important Note: Keep track of the way that serviceaccountname is spelled within the first line of C:ldifdeoutput.txt.  You will need to use it later and it IS case sensitive.

Step 3 – Create Files for Kerberos

On your CMS Servers (cms1 & cms2 in this example) create two files for Kerberos.  The documentation indicates that you should be able to control the locations of the files using your java options.  I was unable to get Kerberos to work unless they were in the default location of C:WINNT, therefore I made a C:WINNT directory for the files.

File 1: krb5.ini

[libdefaults]
default_realm = MYDOMAIN.LOCAL
dns_lookup_kdc = true
dns_lookup_realm = true
[realms]
MYDOMAIN.LOCAL = {
default_domain = MYDOMAIN.LOCAL
kdc = MYDOMAIN.LOCAL
}

NOTE:  If you want to query a particular domain controller you should be able to specify it on the line kdc=, however if AD is set up correctly then your domain name should resolve to the nearest domain controller.  You may want to check the configuration by typing “nslookup mydomain.local” at a command prompt.

File 2: bscLogin.conf

com.businessobjects.security.jgss.initiate {
com.sun.security.auth.module.Krb5LoginModule required debug=true;
};

[UPDATE: 10/1/2010]
Notice that debug=true…this means that when you try to authenticate, you should get a message in the log.  If authentication is failing on you…look in the log to make sure that you are seeing an entry for the attempt.  If you do not see a login, then bscLogin.conf is not even getting loaded, and there is something misconfigured.  This is a great hint for troubleshooting later.
[END UPDATE]

Step 4 –Rights to the Service Account

Next we need to grant the Service Account rights to act as part of the operating system.  These 7 steps walk you through the process.

1. Click Start > Control Panel > Administrative Tools > Local Security Policy.
2. Expand Local Policies, then click User Rights Assignment.
3. Double-click Act as part of the operating system.
4. Click Add.
5. Enter the name of the service account you created, then click OK.
6. Ensure that the Local Policy Setting check box is selected, and click OK.
7. Repeat the above steps on each machine running a BusinessObjects Enterprise.

[UPDATE: 10/1/2010]

Step 4b – Missing STEP

1. Set your java options to look in your C:winnt folder.
2. Go to start->Tomcat->Tomcat configuration
3. Go to the java options tab and set the following java options:

   -Djava.security.auth.login.config=C:/winnt/bscLogin.conf
    -Djava.security.krb5.conf=C:/winnt/krb5.ini

4. Hit OK and restart Tomcat

Thanks everyone for your feedback and pointing out this missing step.

[END UPDATE]

Step 5 – Testing Kerberos

We can now test Kerberos with the kinit.exe utility.   An example of this command for a service account called servact would be:

C:Program FilesBusiness Objectsjavasdkbinkinit.exe servact@TESTM03.COM Password

Syntax Example:

<InstallDirectory>Business Objectsjavasdkbinkinit.exe serviceaccountname@MYDOMAIN.LOCAL password

IMPORTANT NOTE: If you still have a problem, ensure that the case you entered for your domain and service principal name match exactly with what is set in Active Directory.  The easiest way to find the proper casing for the account is to look at the C:ldifdeoutput.txt file we created in Step 2 – Confirm the SPN.

Step 6 – Configuring Active Directory

We  can configure the Active Directory Plug-in within SAP BusinessObjects.

1. Launch the CMC (http://yourserver:8080/CmcApp) and go to the Authentication section of the CMC (Central Management Console).
2. Double-click on Windows AD
3. Select “Enable” Windows AD
4. Click the AD Administration Name.
   • For the user enter the NTLM name…for example: MYDOMAINserviceaccountname
   • For the password enter the password
   • For the Default AD Domain Enter the full domain name in all caps: MYDOMAIN.LOCAL
   • Click update.
5. Add a Mapped AD Member Group by typing the group name in the box and clicking add…for example: MYDOMAINBOEUsers
6. Under Authentication Options:
   1. Click Use Kerberos authentication and make sure the Cache Security Context is checked.
   2. For the Service Principal name enter the service account name with the casing exactly as it appears in the C:ldifdeoutput.txt created in step 2 followed by an @ sign followed by the domain in all caps.  EXAMPLE: serviceaccountname@MYDOMAIN.LOCAL
   3. Check the box that says Enable Single Sign on for selected authentication mode.
7. Under AD Alias Options, configure the options here however are appropriate for your environment.
8. Under Attribute Binding Options, we need to check both boxes
9. Under AD Group Graph, configure as desired
10. Under On-demand AD Update, configure as desired
11. Click Update

Step 7 – Configuring Tomcat

Configure tomcat to use WinAD as the default Authentication mechanism for infoview:

1. Open <Install Directory>Tomcat55webappsInfoViewAppWEB-INFweb.xml in your favorite text editor.
2. Search for authentication.default and change the value to: secWinAD
3. Use Central Configuration Manager (CCM) to restart Tomcat.

Conclusion

Please let me know if this guide was useful.  Setting up Kerberos with SAP BusinessObjects can be tricky and it’s only when I hear from you that I know whether or not these posts are hitting the mark.

«Good BI»