Skip to Content
0

Analysis for Office AD SSO problem with Tomcat 8 Check

Mar 07 at 02:16 PM

37

avatar image

The new and updated version or BI Platform Support Tool 2.1.1 now supports Tomcat 7, and it has some new features and alerts.

Like the one mentioned in the subject.

Now I can't help wondering, why I receive an alert for an AO issue with Tomcat 8, when I am clearly running Tomcat 7.

Either the alert or text should change if it is relevant for me, or it should only be shown if I was in fact using Tomcat 8

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Toby Johnston
Mar 07 at 04:21 PM
0

Hi Thomas,

Thanks for posting. We are investigating this and will come back asap

Regards
Toby

Show 5 Share
10 |10000 characters needed characters left characters exceeded

Thanks,

I really do enjoy BIPST, but if it gives to many false positives, then it can be a bit uphill arguing with SAP support sometimes when they see your Landscape report.;)

/Thomas

0

Hi Thomas,

The alerts are really there to alert you to potential issues. Of course, they are typically just recommendations and things to investigate and not necessarily 100% indication of an issue. If you find false positives that you know are not an issue, you can go to Alerts-->User/Complex/System alerts and modify, delete, or disable the alerts for future report runs. We do our best to keep the alerts up to date based on KBASE and most recent whitepapers.

Regarding the AO issue, Leslie Mui from our team is looking into the logic and will reply back soon.

Cheers
Toby

1

Hey Thomas,

I checked over the last couple years worth of tickets and it seems that the parameter isn't the only thing which can cause the same error to pop up - There's a couple of other problems which cause the same error - bad web.xml config, errors in other config files, etc. I'll remove the alert since even if added, it might be a false positive.

I'd recommend disabling the alert for now.

Are there any other alerts which you think appear too often, or aren't helpful when you interact with support?

Thanks,
Leslie

1

First of all, let me thank the whole team behind the BI Platform Support Tool.

I think it is a great and valuable tool for anyone who has and work with a BusinessObjects platform.

Let me also elaborate what I meant by false positives.
This tool is obviously great for when you contact SAP support, to show the state of you BI Platform, and as an consultant, use this tool ourselves for the same purpose.

Now, the “issue” is, if you cannot read pass some of these alerts you receive, e.g. like giving an alert if Lumira is installed in the server even if the service is disabled, and similar things.

Not to disrespect SAP support, but I have more than on one occasion have to explain then, that just because Lumira was installed, it did not necessarily mean that that was the root cause of the issue, since Lumira was not running.

My point is, that the alerts should not be considered absolutes, and if they are, then they need to be graduated.

I mean, just because you have not changed the default value for the number of retries in the FRS, should not mean you do not have a clean bill of health.

So if the alerts provided is the “standard” them I would just like them to be correct and relevant, and not like the reason for this question, to raise an alert for something that is not related to this platform installation.

Anyway, keep up the good work, and looking forward to see what else you have in your bag of goodies.

Br
/Thomas

0

Hi Thomas,

This is valuable feedback, thank you.

Let me address a few of your points:

1. Regarding how alerts are treated by SAP Support:

  • I'll add a disclaimer in the alerts report stating that the alerts are meant to be clues and items to evaluate but not an absolute indicator of a problem.
  • There is some training happening this year with BI support which will reinforce the above^ to avoid this type of response from support and for them to think more critically when an alert is triggered.

2. The number of FRS retries alert has been removed. This alert came from the solution manager go-live service and after some deep diving into the code we found that the parameter does not do what we think it does (the admin guide is not exactly correct or specific enough in it's description). We are following up with dev to see if it's possible to make it more useful at which point the alert would make sense. There's more info in the below post if you're interested in learning more: https://answers.sap.com/questions/425920/frs-alert-maximum-retries-for-file-access.html

3. So if the alerts provided is the “standard” them I would just like them to be correct and relevant

We do our best to make them as accurate as possible but we do run into issues once they are released to the wild. As you are aware there's a million possible variables which would be introduced in the BI environment. We do our best to correct any issues asap :)

Thanks for the support!

Regards
Toby

0