1 2 3 27 Previous Next

BI Platform

392 Posts

The idea is to create a session count (specially for concurrent users) to check the numbers of session in the system and notify by email.

 

First go to monitoring in the CMC

 

Go to watchlist and create new one.

-Write an appropiate name

-Select the number of States. In our case we select 3, because we want to have a caution state preventing the server to be in danger of running out of sessions.

-We are going to check the write to trending database option so we can see history of this metric.

-We are going to check add as KPI because we want to see the watchlist in out dashboard.

 

 

-Click on Next.

Under Central Management Server we search for the number of sessions established by concurrent users and we click over the arrow.

We select an a caution value for our metric. In our case as we have 100 concurrent users we select 70.

 

 

We click on Next and we go to Danger rules and repeat the above steps but now we define the danger level equals 90

 

Click on Next

 

Default options --> Click over directory

 

 

We write our email address and click okay,

 

 

We Save the new Watch and now is available in the watchlist:

 

 

Once we have created we can go to history of the metric and review its behaviour.

 

Hope this helps someone!!

 

Sorry if someone else created something similar.

 

thanks

Mauro

Business Intelligence Now - The 2016 Survey

 

 

 

data_s.pngOnce again we have industry experts and insiders Miko Yuk, David Dadoun and Tom Venables, and the Xoomworks BI team offering insight and questions in their fields of expertise. After completing the mandatory General BI section, our 2016 BI survey increases flexibility allowing you to choose which sections you wish to be involved with.
The survey is anonymous and we welcome extra input with free comment sections. Business Intelligence is a complex topic that spans the breadth of the business world, we value your input and thoughts to add to the base of knowledge.

The 2016 Business Intelligence Now Survey will be followed by a white paper investigating all the results and topics you have participated in. Do leave us your contact details to receive the 2016 white paper.

 

Average time to answer all questions: 25 minutes

Average time to answer the General BI questions: 10 minutes
Average time to answer the Data Visulisation questions: 3 minutes
Average time to answer the Data Governance questions: 5 minutes
Average time to answer the Data Security questions: 5 minutes
Average time to answer the Data Warehousing questions: 2 minutes

 

Business Intelligence Now - The 2016 Survey

 

Download 2015 whitepaper

Greetings BI Platform community,

 

I want to introduce the Open Beta phase of our exciting new Predictive Support Alerts offering from SAP Product Support.  For those of you that don't know me, I have been in Support @ SAP (out of our Vancouver, Canada office) for over 17 years now and most of that time has been spent working with our BI Platform Customers and Partners.

PSA copy.jpg

Over the last few years, SAP has been hard at work trying to evolve our support offerings and find new ways to assist our customers and accelerate the resolution time for what we classically refer to as Incidents.  One of our innovative new offerings is called "Predictive Support Alerts" (PSAs) and I am happy to be the program lead for this new offering.

 

So what are PSAs exactly?

 

From a high level, PSAs are essentially personalized alerts that are sent to you via email.  These alerts are based off of Landscape Reports that created using the BI Platform Support Tool that are sent to SAP Product Support from the tool itself.   SAP then analyses the landscape data that is uploaded and determines if any known issues are present in your environment.  If a known issue is discovered, you will receive a personalized email alert that tells you exactly how the issue affects you and most importantly, how to resolve it!

 

More details can be found at the below two links:

 

Wiki - Predictive Support Alerts Wiki

Blog - Call for BETA Participants (during the closed beta)

 

What is the Open Beta all about?

We did a closed beta with 12 customers/partners back in March/April.  This helped us uncover a few issues that we are currently working on.   These issues are documented in the above wiki and can be worked around for the most part.  We now want to open this program up to a wider audience before opening the flood gates so we can catch any other issues or suggestions that you may have.  So, we invite our SCN community members to participate in this open beta and provide your feedback.

 

How do you participate in the open beta?

To participate, you simply have to follow the steps below:

  1. Download the latest version of the (BIPST) BI Platform Support Tool  (completely free and a must have for all BI Administrators!)
  2. Configure your S-User/Email address in the BIPST (youTube video walkthrough - Publish to SAP Feature BIST v2 0 - YouTube)
  3. Publish at least 1 Landscape Report to SAP for analysis! - See above video or wiki for these steps
  4. Give Feedback to us via the sap_predictive_support_alerts@sap.com email address

 

That's it.  As soon as you send us a report, you are entered in the program and will be eligible to receive these proactive alerts!

 

Note: One of the known issues right now is that some networks block the secure FTP protocol we currently use to upload these reports automatically.  If you get an error when trying to publish your reports, you can simply email to us directly instead by clicking this link:

     Email to SAP

 

We have tried to answer most of the frequently asked questions in the above mentioned Wiki page but by all means, if you have any questions about the PSA program, the BI Platform support tool, or the beta program, please do not hesitate to comment on this blog or email us @ sap_predictive_support_alerts@sap.com

 

Here is an example of the type of alerts you would receive.  Yours of course would be customized to include your environment details!

PSA Beta #3 -Platform Search Indexed Docs 0 - Generic Masked.png

 

Thanks!

Jb

Last Wednesday at the North American iteration of its annual SAPPHIRE event, SAP's Bernd Leukert made some big news about SAP analytics during his keynote. Let's review the announcements then dive into their implications for those who maintain SAP's on-premise business intelligence platform.

What Was Announced At Sapphire?

 

First, SAP has aligned its analytics portfolio under the familiar BusinessObjects brand (see Steve Lucas' blog, Modern Analytics for the Digital Age). SAP Cloud for Analytics is now SAP BusinessObjects for Cloud, while the on-premise BI offering gets a slight tweak back to its older SAP BusinessObjects Enterprise name. SAP Lumira (and Design Studio - see Blair Wheadon's blog, SAP Lumira and Design Studio Convergence) becomes SAP BusinessObjects Lumira. Recently acquired RoamBI becomes- you guessed it- SAP BusinessObjects RoamBI. Whether you love the BusinessObjects brand or hate it (and more than one SAP executive couldn't resist making disparaging remarks when the teleprompter forced them to say it), the portfolio is much easier to comprehend under a single brand. The SAP BusinessObjects brand is joining SAP Ariba, SAP Fieldglass, SAP Hybris, SAP SuccessFactors- sub-brands recently prefixed with "SAP" as opposed to phased out. It doesn't hurt that classic BusinessObjects customers (those that only use the BI suite, not SAP's business applications) that have felt alienated from SAP's historic product moves will feel warm and fuzzy, too.

Second, the road map received several small tweaks, particularly for Lumira and Design Studio. However the big picture is still the one that SAP has been painting since their BI tool convergence was announced two years ago. The big news for BI competency center managers is that two packaging levels are becoming three. A new Premium edition is joining the Standard and Professional editions of the on-premise BI suite, adding predictive analytics and big data capabilities previously available as stand-alone options.

What Should SAP BI Competency Managers Do Now?


SAP BusinessObjects Enterprise 4.2 Support Pack 2 has been in general availability since March 2015 and boasts an impressive list of new features (see related SCN article, What's New in SAP BI 4.2). Customers still running any patch level of BI 4.0 should give the upgrade strong consideration, as it places a lot of new functionality on an even stronger Apache Tomcat 8 + SAP JVM 8 foundation. Customers running the newer BI 4.1 release should still give 4.2 consideration, particularly if they're interested in the long list of new Web Intelligence features (see Christian Ah-Soon's SCN article, SAP BI 4.2 - What's New in Web Intelligence). If you've recently upgraded to BI 4.1 it may be difficult to make the business case to upgrade again, unless your plans include adding SAP Lumira or SAP Design Studio (or both!) to your landscape. There are so many features described in the "What's New" document, but here are my personal "top 10" reasons that I'd use in a business case to upgrade to SAP BI 4.2 SP2.

 

  1. New Web Intelligence functionality including custom grouping (introduced in BI 4.1 SP2), free-hand SQL (introduced in BI 4.1 SP6), geolocation charts, global input controls and shared components.
  2. Direct access from Web Intelligence to SAP HANA without need for a universe
  3. Create universes on SAP BEx queries (provides ability to customize/humanize BEx without modifying original BEx)
  4. Faster Web Intelligence refresh times using parallel query
  5. Desktop browser and mobile view/refresh for Lumira documents via BI Launch Pad
  6. Linked universe support in Information Design Tool
  7. Improved application stability courtesy of Apache Tomcat 8 and SAP JVM 8 and improved platform support for IE 11 and Java 8 JRE
  8. Improved migration tools for customers still using older (and now unsupported) editions like XI 3.1
  9. New recycle bin functionality means administrators can recover accidentally deleted content (see Jason Gardieff's related article, Retrieving Accidentally Deleted Objects in SAP BI 4.2 Using the Recycle Bin)
  10. Improved insight and system control for administrators via BI Administrators' Cockpit (see my related article, The BI Administrator’s Cockpit)

 

As you can see from the list, there are both technical and functional reasons to upgrade - something for everyone. You may have heard that SAP BusinessObjects Enterprise 4.2 Support Pack 3 - currently on schedule to arrive around August - will add key features from the Web Intelligence Java client to the DHTML client. Keep in mind that while the most "popular" missing features are coming first in SP3, the HTML client won't be at parity with the Java client until SP4 arrives, now planned for Q1 2017. Any additional retirement of Adobe Flash is also unlikely to happen before SP4 (see my related article, Adobe Flash- Dying but not Dead Just Yet). I'm not an SAP employee, but keep in mind the usual disclaimers about talking about the future.

 

SAPPHIRE 2016 Dallas Marks Registration Badge 400.jpg

 

Next, the rebranding of SAP BusinessObjects for Cloud implies a degree of inter-operability with the on-premise BI platform, but not as much as business users may assume. SAP BusinessObjects for Cloud can connect to UNX universes via a (secured) web application server; however, it is not possible as of this writing to host any "classic" content like Crystal Reports or Web Intelligence in the cloud. This means that SAP BusinessObjects for Cloud can augment your on-premise BI strategy in some interesting, low maintenance ways. But it certainly isn't a replacement for your existing on-premise SAP BI. At least not yet. And while classic UNV universes continue to be supported, SAP BusinessObjects for Cloud is another reminder that organizations should begin using the Information Design Tool and its UNX format on new projects.

 

Regardless of how and what your BI competency center chooses to upgrade in 2016, never forget that we're in the people business serving business intelligence, not in the business intelligence business serving people. Fortunately, BI 4.2 has some great new features that people will love.

 

Want to learn more? On June 24, SAP is hosting another #askSAP webinar to answer your questions about the BI 4.2 platform. You can register here. What are your impressions of the analytics news from SAP SAPPHIRE? What are your plans for BI 4.2?

We recently came across an issue where our scheduled jobs on BI 4.1 platform wouldn't run as expected; they would just not start. We have a clustered server setup and the job servers are running on couple of nodes. When this happens, the job server status on CMC would appear to be fine. We have raised this issue with SAP support and working on finding a resolution. In the meantime, we used the below Power Shell script as a work around to restart the job service when the schedules don't run as expected.

 

Solution

We scheduled a simple web intelligence report that runs every 5 mins; Using PS, we checked for the status of this report through Auditing database. When there are no entries made in the auditing database for a set threshold time, we use CCM.exe to restart the JobServer.

 

 

 

#Auditing database credentials
$dataSource = "Auditing Database Server"
$user = "Auditing database user"
$pwd = 'Auditing database password'
$database = "Auditng Database Name"
$threshold_mins = 10
$connectionString = "Server=$dataSource;uid=$user; pwd=$pwd;Database=$database;Integrated Security=False;"
#Win AD authentication to SQL Server
#$connectionString = "Server=$dataSource;Database=$database;Integrated Security=True;"
#Query to check the scheduled report event in auditing database
#-480 mins is to adjust for local time Western Australia Standard Time
$query = "select count(0) from ADS_EVENT where Event_Type_ID=1011 and Object_name='Webi Heart Beat v1.0' and Start_time>=dateadd(minute,-480-$threshold_mins ,getdate())"
$connection = New-Object System.Data.SqlClient.SqlConnection
$connection.ConnectionString = $connectionString
$connection.Open()
$command = $connection.CreateCommand()
$command.CommandText = $query
$result = $command.ExecuteReader()
#write-output $result.HasRows
while($result.read())
{
    Write-Output $result.GetValue(0)
    if ($result.GetValue(0) -gt 0)
    {
        Write-Output "Job Server Ok"
    }
    else
    {
    //Code to send email
    send-mailmessage -to "abc@xyz.com" -from "abc@xyz.com" -subject "Job Server being restarted" -SmtpServer smtp.xyz.com.au
    //Code to restart the server
  Invoke-Expression '& "C:\Program Files\SAP BusinessObjects Enterprise XI 4.0\win64_x64\ccm.exe" -managedstop SIA_BOBJ_DEV.AdaptiveJobServer -username administrator -password ######'
    Invoke-Expression '& "C:\Program Files\SAP BusinessObjects Enterprise XI 4.0\win64_x64\ccm.exe" -managedstart SIA_BOBJ_DEV.AdaptiveJobServer -username administrator -password ######'
    }
}
$connection.Close()

Large, Global SAP BI4.x new deployment

“Humans and data quality errors are inseparable” MIT Symposium

Big data and Business Intelligence

Business Intelligence software and systems created a level of automation to handle the big data revolution. That automation should remove the cognitive biases and confirmation biases humans have evolved dealing with data.

Complex BI systems are designed and implemented by humans. They have the same failings and bad cognitive attributes. A BI system can suffer the same performance problems. The larger the BI program, the greater the data flow. The more chance of performance issues due to errors in design, and implementation. A speaker at an MIT Chief Data Officer Symposium in 2013 said: “if humans are involved in the production of data, you should expect it to be imperfect.”

“Bad data is first and foremost a human phenomenon” MIT Symposium.

Build in the quality

The philosophy of quality control is not new. The aviation industry became a champion in the 1920’s. Aircraft production boomed during that decade. The high human error rate was a sobering statistic. Automation in production eliminated many quality problems. The aim was to build in the quality not inspect it in.

In 2015 Xoomworks BI produced a presentation for SAPinsider at Nice titled “A Step-by-Step Process to Design and Manage Successful SAP BI Implementations and Upgrades for Large Deployments.”(The long title itself could contain human errors.) The aim was to provide a framework to reduce the error rate in design and implementation. Build in the quality, not inspect it in. Following a multi-tiered architecture design also makes the task of troubleshooting easier.

Gartner has been hailing, analysing, and deriding BI software for several years. The analysts often report on poor performance and success rates of BI implementation. Their Magic Quadrant takes a software approach looking at the strengths and weaknesses of their leaders and followers. A useful guide but ignoring the human element in the design and implementation that could mean success or failure of any BI system. And in the final analysis, even the best software will fail when deployed if the system is not well designed.

The Correct Approach Leads To The Right Solution:

Axioms

Leave questions open, don’t worry about not knowing the answers. Get information, test and prove things yourself. Don’t make decisions based on bad facts that lead to bad conclusions.

Record and share your knowledge. Do it with clear technical documents for all processes. Add who does what, where, and how and keep it updated.

Always put yourself in the customer’s shoes. One single report may have more value than any other. Test and explore all project variables and dependencies.

Be curious when looking for RCA of any issue, starting from OS issues up to app issues.

Just because things look right for the user, it doesn’t mean it is right at the back end.

Five Tier Architecture

An SAP BI4.x implementation depends on everything. Network components, OS settings, authentication, access, security. The implementation depends on all the connected data sources. The implementation on human behaviour and human failings. We have talked previously about human behaviour in the field of Change Management for users, here we look at the design and implementation.

The goal is to have an unbreakable, dynamic configuration. A configuration with the ability to change and remain error free as a BI solution.

“You purposefully need to create standardised systems, processes and methods. Otherwise, you will always have high failure rates and poor performance.” Lifetime Reliability Solutions

The design architecture for a new deployment follows five steps

Sandbox. This environment tests and explores issues within other environments. Sandbox can test new SAP BI4.x functionality, and software upgrades or patches. The test environment can also look at new integration with other software or private fix regression testing.

Development. Developers use this environment to create BI content. Development data sources will be connected. The information doesn’t have to be valid, just be structured as Production data source.

Acceptance. This environment is used to validate the configuration of a build. A comparison is made with connected Acceptance databases before sending the content to the next step, Quality. Data sources will contain an old copy of Production data to allow validation of formatting. That will also allow validation of calculation results and single report performances.

Quality. This environment validates via an internal BI Centre of Excellence (COE). It looks at the quality of the BI content generated. Performance tests need to be carried out in a real-life scenario. Validating production data volumes, testing concurrent usage, scheduling and publication under a worst-case scenario.

Production. This environment is used for the final reporting, consumption, and job processing for the connected Production data sources.

Understanding the full capabilities of SAP BI4.x and the features is a necessity. With that knowledge, the best solution can be found for the requirements of the business. Building relationships with the people who will be involved in design and implementation is another necessity. Understanding their positions and clearly defining their roles and responsibilities.

Post Design

The strategy is to define and run a proof of concept to prove the business requirements are met. This phase will bring out technical issues. Troubleshoot, fix, and document all the issues using a similarly rigorous and defined approach as for the design. There will be configuration after the installation, for success it is important not to take short cuts. Security configuration is vital, how you assign groups and custom access levels.

Existing deployments

A business intelligence system is an existing deployment once it has started running, and it can be monitored as such. SAP BI4.x growth and usage are dynamic. The situation can change daily depending on the type and level of controls which are implemented. There will be ongoing maintenance and software upgrades to undertake.

An example

The problem wasn’t with the processor speed but the channel throughput specification for that CPU in production. The CPU with a higher frequency had 100MHz Front-Side Bus, whereas the CPU model used on the test system had a 400MHz FSB.

Intel and AMD noticed the speed problem many years ago for simple calculations on a large data set. The FSB couldn’t keep up with the CPU. Whereas with complex calculations, the greater time spent in the CPU meant the FSB could keep up. The human error in this example was a failure to have detailed information on the chosen hardware.

Errors do not have to end in failure

It is important not to design an over-complex BI system architecture. An architecture proposal may look good on paper. If a system has installed components surplus to the business requirement, redundant issues may be raised during a proof of concept phase. The redundancy may be enough to jeopardise a new project.

Human design and involvement will produce errors using any approach to design and deployment. If the correct procedures are followed fixing them becomes part of that procedure. Errors do not have to end in failure.

A step by-step process to design and manage a successful sap bi implementation or upgrade for large deployments v2 from Xoomworks Business Intelligence

Learn More:

Big Data’s Human Error Problem, Information Week, 10/2013

2013 MIT CDOIQ Symposium, 2013

The hidden truths in human error rate tables, Lifetime Reliability Solutions

Frontside BUS, Technopedia

IBM Security Services 2014 Cyber Security Intelligence Index, IBM Security, 2014

The Frontside Bus Bottleneck, Technewsworld, 09/2013

Xoomworks BI

Gartner

Since upgrading to BI 4.2 and Tomcat 8 we observed in Analysis Office (Version 2.2) a Single Sign On problem when would like to connect to BI platform via Windows AD and Kerberos (Vintela). In prior versions SSO worked without any problems.

 

The error message was the following (error occurs only when opening a workbook via Analysis Office; opening a workbook directly from BI launchpad works as usual):

Logon to BIP-server failed. The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

 

To solve this problem you have to add the following command line parameter in the JAVA Options within the tomcat configuration.

 

-Dorg.apache.catalina.core.ApplicationContext.GET_RESOURCE_REQUIRE_SLASH=true

 

tomcat_java_opts.JPG

 

On Apache Tomcat 8 Configuration Reference you can find addtional information about this parameter.

 

https://tomcat.apache.org/tomcat-8.0-doc/config/systemprops.html

SAP BO BI 4 Security – Quick & dirty security: the short-cut can become the longest cut

“Your security model is a living breathing entity.” Xoomworks BI 2015

“Oil and Gas organisations must move beyond operating strategies based on myths and confusion about SAP security.” CEO Onapsis, Gartner Security & Risk Management Summit 2015.

“Research findings show the vast majority of SAP systems evaluated contained critical vulnerabilities that exposed them to espionage, sabotage, and fraud.” Onapsis research labs.

“The criticality of the threat to infrastructure was recognised by the FBI.”  Nasdaq

“We found one of the biggest problems was shortcuts being taken.” Xoomworks BI 2015

Onapsis were Silver Sponsors at 2015 Gartner Security & Risk Management Summit. They revealed some salutary research. They identified common threats to SAP BI systems. They are the threats to business-critical data.

In the oil and gas industry threats came from:

  • Competitors.
  • Disgruntled employees.
  • Foreign states.
  • Hacktivists.

They identified four common approaches:

  • Customer information.
  • Credit card breaches.
  • Customer and supplier portals.
  • Database warehousing.

Breaches in security could be accidental. For example, 30,000 users receiving 16 reports due to a stray “view” permission, causing a production outage, and causing a data breach.

Breaches in security could be corruption. A recent high-profile security breach; U.S. Secretary of State Hillary Rodham Clinton is an example of bad practice. She wilfully strayed outside the parameters of accepted behaviour with no adequate monitoring. In Clinton’s case, she physically extracted material with a high-security rating and placed them on a personal server. The leaks were traced from emails. The FBI’s current investigation into Mrs. Clinton involves over 100 agents.

Business Intelligence tools have many functions. They organise, extract and analyse data. The data resides in complex systems. Security (or the strong right arm of BI) reflects that complexity. We often deal with security in SAP Business Objects. When we break down the function or the output we require from security and adapt to how it is designed, organisations and users simplify their task.

Complex processes have always needed a way to be drawn. Frank Gilbreth the process analyst of the 20th Century created a flow-process chart. He broke down complex tasks into individual parts. The parts to be examined and improved. Computer programmers of the 1970’s borrowed the idea. They used the IPO (Input-Process-Output) chart. The commonality was starting with the Output. Then designing the system to deliver it. No different to security in a complex Business Intelligence system. Start with the desired result and design a flexible system to deliver it. A system that grows with an organisation.

Follow some simple rules, I would go so far as to say axioms. Doing so reduces the chance of something going wrong. BI deals with massive amounts of data. Security must secure the data and control the access to it. The access will mean the data is available only to the right person, at the right time, for the chosen purpose.

In 2015, Xoomworks BI gave a presentation on SAP BusinessObjects Security: Authentication, Security Token Service Problems, Pitfalls, Tips & Tricks. It was one of numerous “how to”, “help me please” presentations by experts. These include the definitive guides produced by SAP. Here we are extracting a few of the general principles.

AT Xoomworks BI, we found one of the biggest problems was shortcuts being taken. Rather than following a security structure and keeping to the good path. Complexity is part of the story with security; it impacts performance as the structure grows and stays flexible.

Objects

As far back as 2011 SAP was publishing 65 security notes per month. That is Microsoft and Oracle level. Demonstrating how seriously they considered security. SAP BusinessObjects security is now an Object based system, not user-centric. Everything in BO is an object. That means everything to which security can be applied. Not just data, users are also nothing but objects. Permissions are granted to these objects. They can be folders, groups, servers, and more.

Users will reside within a group. That group resides in your user and group structure. SAP BO has predefined access rights and the ability to assign granular rights. Predefined access levels: No Access, View, Schedule, View On Demand, Full Control. No Access is not a denial; it sets permission to “Not Specified” which can be overridden. Full control means a user can modify an object up to its deletion. The others lie in between.

Never assign granular rights to content. That is the easiest way for information to go to the wrong people. Keep to groups, and give them Custom Access Levels (CAL). If you have a user with a specialised security requirement, set up a group for them. Then assign security for the group. You can add people to the group when you need. They’re in that group so they can have the group permissions.

Groups

Content Groups: Grants rights to folders. The folders contain the content. For example, the marketing group will have access to the marketing folders.

Application Groups: Grants rights to applications. For example, the members of marketing will have permission to create documents in the marketing group.

Split groups in to two defined sections. This is a step towards simplifying your security model. Every user becomes a member of a content group, and an application group. As required they become members of other groups. If a user leaves a group, he loses permissions for that group. The replacement user adopts the permissions when they enter the group. Permissions never rest with the user, but with the group. Documents follow the same pattern. Permissions never rest with a document. Folders are created with appropriate security and the documents live within that.

Custom Access Levels

“We can say that securing SAP Business Objects properly is not possible if custom access levels are not used.” GB & Smith. They go on to say “Complexity arises from the fact that a custom access level is applied to a resource. Calculating the impact, it could have on sub-resources, sub-groups, and users is thus required.” CAL’s are apart from the pre-defined access levels in BO security.

Building CAL’s is sequential and cumulative for any object

Each access level builds on the rights granted by the previous level. Administrators can set frequently needed or common security levels uniformly. A better and safer option than setting individual rights or trawling through the 1,000 granular rights.

Tip: Assign each right in only one CAL. Build up a user type’s permission by assigning multiple CAL’s. If Info Consumer is your lowest level, an info worker will have both info Consumer and info Worker CAL’s assigned to them.

For example, two groups, procurement managers, and procurement employees. As two groups they require access to 20 documents. The documents are in the BO enterprise system. But the managers require more rights than the employees. Rights not covered by the pre-defined levels. Don’t add groups to 20 documents. That would require modifying their rights in 20 places.

Rather two new custom access levels can be created. Call them Procurement Managers and Procurement Employees. Both groups are added as principles to the documents. Their rights can be modified when needed. The access levels apply to both groups across the 20 documents.

Application and Content CAL’s

While it is possible to create a single CAL which covers both Application and Content permissions, it is better to ensure the CALs satisfy a single purpose.

Create separate CALs for Application (e.g., WebI, CMC, Crystal Reports) and Content (e.g., reports, universes, connections.)

CALs should be broken down into the various functional areas as well as being modular.

Info Worker should have all previous access levels as well as the CALs named after their user types.

Security Token Service – Brokered Authentication

Security Token Service (STS) is not a new concept. Brokered authentication has been used to grant access to applications and web services for many years. STS was introduced in SAP BO BI 4.0. It is a one-way trust; BW systems trust BI4, but it does not trust the BW systems. A neat idea to place an intermediary.

In a multi BW system, a user logs in with one method and can still use another method’s functionality. So sign on with a single sign-on (SSO) to one BW, and connect to another with the same SSO as the credentials are brokered. In a complex environment, an STS can streamline authentication. In fact, the more complex, the more STS helps.

The STS can replace a Secure Network Configuration (SNC) setup between BI 4 and a BW. The SNC will only be used for legacy workflows; new workflows will use the STS. You can see detailed setup guides on our slide presentation, and on the links within that document.

The last but not final words

Keeping on top of your requirements is vital. Adjust the security model as and when required. Never assume that shortcuts are not being taken.

It is a fact that the more complex security and authentication are, the greater the impact on performance. Security Token Services and aliasing users can make your security solution simpler.

Make your security model as flexible as possible.

Finally, If you intend to run for the U.S. Presidency, treat your data security with some respect.

For further reading:

Discussing the complex challenges of SAP Security, MWR Info Security, August, 2013

SAP BusinessObjects Security: Authentication, Security Token Service Problems, Pitfalls, Tips & Tricks, XWBI, 2015

The Gilbreth Network, Frank and Lillian Gilbreth brief biographical information.

SAP BusinessObjects Security: implementation, issues and challenges, GB & Smith, November 2015, Drouvin

Brokered Authentication: Security Token Service (STS), Microsoft Patterns & Practices, December 2005

Onapsis announces Oil and Gas Companies at Risk from SAP Vulnerabilities, Nasdaq Globe Newswire, June 2015

From Gartner Security & Risk Managament Summit 2015, SAP Vulnerabilities, June, 2015

State Department Confirms FBI Investigation, Washington Times, February 2016.

Trip Report, Gartner Security & Risk Management Summit 2015, Gartner June 2015

For any questions: drop us a line

It is a fact; many SME’s continue to postpone their BusinessObjects upgrades despite the platform being unsupported.

Many old BusinessObjects customers continue to use BO 6.5 or BOXlr2, again despite the fact prices for SME’s have dropped enormously. We looked into the phenomenon to gain an understanding of it. We wanted to lay down the facts, deliver some home truths, and give SME’s a reality check to dispel the common myths.

There is a perception amongst some SME’s that BusinessObjects, now carrying the SAP label, and described as Enterprise Software, is expensive, and the future unpredictable. Fears exist over how SAP’s investment in BusinessObjects and its development will progress. The fact is BusinessObjects is still here years after the acquisition by SAP, and SAP BusinessObjects Edge is priced for SME’s to offer a fully functioning BI suite of tools, added to which Edge connects to anything not just SAP BW or HANA.

The value of the acquisition of BusinessObjects was over $6.5 billion, at the time SAP CEO Henning Kagermann stated the driver was growing new business. That business was the increasing demand for BI capabilities within the software. Almost a structural change for SAP that is unlikely to be reversed. Analysts at the time saw the future of business applications to be the ability to use them in a more intelligent fashion, a fact in today’s analytical business environment. An IDC analyst put it well at the time “You’ll do your analysis from the BI interface and then dive directly into the transactional data you want to examine.” Those capabilities are increasing and improving, as is the accessibility of BI to SME’s.

It is a false economy to assume the cheaper alternative is to rebuild a BI system using new tools as opposed to renewing. Long term SAP is no more expensive than Tableau or Qlik, and Edge priced as it is can be the first option on the list.

The myths, we discovered five common misconceptions held by SME’s blocking their BusinessObjects upgrades.

  • Software cost
  • Project cost
  • Lack of skills
  • Training impact
  • Looking into other tools

Software Costs

The terms SAP and Enterprise Software do not mean the software will be out of the reach of an SME, nor that a project will be overly complex and take five years to implement. SAP invested in many small companies. For example SAP BI (BusinessObjects), Data Services, and Sybase IQ. All acquisitions, and all with SME versions that easily undercut the cost of the enterprise versions. A complete toolset means building dashboards, producing reports, sharing them via the portal and email, creating a self-service BI approach and an enterprise level security integration.As an example, the pricing below is based on the current standard cost of Edge. Varying discounts are more than likely available based on how many users are required.The fear of SMEs to upgrade from BusinessObjects to SAP
As with any product with a lifecycle, at some stage, the market must be segmented, and the growth and penetration for each assessed and quantified. The old approach was often discriminatory pricing between the segments leading to an uneven value proposition. The modern approach is to offer the high value to all levels of business with appropriate functionality for the pricing. SME’s are a growth segment, and products are designed and priced to offer the highest value. Howard Dresner considered a thought leader in BI put it well “larger enterprises continue to generate the big deals, but they are far fewer in number than SME deals. SME is a growth segment for vendors.”

Project costs

  • The truth of the extent of project cost depends on the complexity of your data and reporting requirements.
  • The installation can be done on premise, on virtual servers or a cloud server.
  • Building the data layer can be very quick with a current DB schema that explains the joins between your tables, or consulting someone that has the knowledge.
  • Creating a report in WebIntelligence is very quick, and easy to use, with a little training business users can take a self-service approach.

SME’s have an agility advantage in coordinating a project; the decision-making tree is shorter than at enterprise level. An assessment of an SME’s data environment will take less time, executives are closer to the data and identify how they wish to utilise their data for best competitive advantage. Factors that keep project costs lower for SME’s than larger businesses that may suffer from bureaucracy.

Lack of skills

There are numerous options to cover this myth. Xoomworks BI itself, as a niche specialised consultancy offers help. The budgets aren’t in the same league as the big players, plus having a near shore office we reduce the overall cost, maintaining the quality of our work.Gartner as early as 2005 identified lack of user skills and knowledge of best practice to be the greatest barrier to deploying business intelligence software. The fact is the democratisation of Business Intelligence within organisations is increasing, due to demand. That demand has led to BI being accessible to all levels of users. Business Intelligence tools must cater to the requirements of business users. The tools are moving towards analysis from reporting, the business use and discovery are succeeding the delivery of information. Business users now require the ability to the full functionality of the analytical tools without having an expert level of data science or high-level IT skills.

Training impact

Taking WebIntelligence as an example, it has improved, the look and feel changed, but it is essentially the same tool. The need for training can be dependent on the version currently being used. The important factor is that training is always available, hands-on and tailored, one to one or groups, and it can be specific to the user levels and their requirements.


The millennial generation seems to be grasping training and its benefits. Recurrent and continued training is essential to the success of a BI project and system, it freshens the skill set and, more importantly, keeps the level of trust in the BI and data high. An analyst at a recent BI conferencepointed out “A lack of understanding about technology can breed distrust. And good communications between all involved can reduce misunderstanding up front.” She went on to say with great prescience in my opinion “everybody is a data generator and consumer. Computing and analysis are no longer synonymous with IT; they are a common way of life for everyone. Millennials change the way data is reported and consumed; a generational shift is changing the importance of training.”

Looking into other tools

I always find this an interesting topic to discuss. I take the approach of going back to the actual requirements. What do you need the tool to deliver. And a complete suite of tools will always offer an advantage regarding economy, utility, and ease of use. Looking at BusinessObjects, it is the complete tool integrating a variety of functions and options. The smaller niche tools tend to do one thing very well but are lacking in overall capabilities, such as security or a self-service approach.


Consider the cost of rebuilding everything, training every employee on a new tool. Then consider the long-term viability of a new tool, will it cater to future requirements, and be scalable. Edge is fully compatible with the Enterprise version of SAP BusinessObjects when an organisation reaches the threshold above SME they can upgrade to the Enterprise version. It is an easy migration for the BI content, the users, groups, reports, dashboards.


Consider the change management implications to an organisation of starting again with a new BI system. Changing the behaviour of the users until they feel comfortable to use and exploit any BI system is vital to the system returning a productive use. Removing that comfort zone takes an organisation back to the level of beginning the change management process. Change management requires the alteration of individual behaviour and as our recent Xoomworks BI State of Business Intelligence Survey showed, cooperation between departments, CIO’s, CFO’s, for the self-service paradigm to be accepted and work. Power users and leaders tend to dictate on a departmental basis their requirements for reporting. Consistent reporting is necessary throughout a business at all levels, an upgrade maintaining the underlying platform keeps that consistency.


In reality, the cost argument, or myth, needs to be removed from the decision to upgrade, the facts don’t support it for SME’s that by their nature and size demand cost-effective solutions. The industry is filling that demand with products that reflect the growth for BI in the SME sector.If you add data governance and security to the equation of upgrade versus rebuilding a BI system with new tools, the upgrade case becomes more powerful. Maintaining a platform, upgrading, keeps existing data governance and reduces the chance of lost or corrupted data. As our BI survey showed, everyone is aware of the importance of data governance, but few feel they are in control of it.


Taking SAP BusinessObjects Edge as an example of a product designed for SME’s it will have a different license structure to the enterprise version, both being licensed based systems. For instance:

  • Single-server installation (no clustering)
  • Edge has a maximum of 50 concurrent licenses. Working by a 10% concurrency this technically allows 500 users to use the platform but only 50 concurrently.
  • Edge has a maximum of 250 named user licenses.

 

I view that aspect as being in line with the size and structure of an SME; the functionality will offer the same high level as an enterprise version.

I got real problems with performance in BI Launch Pad. For instance, my reports were opening very long time, navigation in BI Launch Pad was awful.


1. Let's modify the Tomcat setting, because by default they have low value.
o JavaHeapSize (-Xmx) from 2G to 4G
o MaxThreads from default (200) to 900
1.1 JavaHeapSize we should modify:
cd <bo inst folder>/sap_bobj/tomcat/bin
modify setenv.sh

# set the JAVA_OPTS for tomcat

Code:
JAVA_OPTS="-d64 -Dbobj.enterprise.home=${BOBJEDIR}enterprise_xi40 -Djava.awt.headless=true -Djava.net.preferIPv4Stack=false -Xmx4g -XX:MaxPermSize=384m -XX:+HeapDumpOnOutOfMemoryError -Xloggc:<bo_inst_folder>/sap_bobj/tomcat/logs/tomcat.gc.log -XX:+PrintGCDetails -XX:+UseParallelOldGC"


1.2 MaxThreads we would modify:
cd <bo_inst_folder>/sap_bobj/tomcat/conf modify
server.xml

Define a non-SSL HTTP/1.1 Connector on port 8080

Code:
    -->
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxThreads="900" URIEncoding="UTF-8"/>
  <!-- A "Connector" using the shared thread pool-->
  <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    -->

 

 

 

2. Cleaning of old installed patches and service packs from BO. What does it mean?
Just go to <bo inst folder> and run ./modifyOrRemoveProducts.sh (for Linux):
It is clear that i have many various installation on my server. But it is important to delete old installation!

 

3. Cleaning of logging directory, in <bo inst folder>/sap_bobj/logging
o Deleting Trace-Files
o Deleting Logs old than 30 days
4. Tuning APS, for start you can use CMC Wizard.
5. APS properties for tracing set to unspecified (-> means bo_trace.ini are used)

 

Level - Description
Unspecified - Force the use of BO_trace.ini to be used
None - Only critical events such as failures will be logged
Low - Ignores warning and status messages
Medium - Only Status messages with least important will be ignored
High - Includes all the logging messages

 

6. Disabling of unused services in the CMC, for instance, Crystal, Analyses services.

 

7. Reorganisation of database statistics of BO-Repository and BO-Auditing.

 

This one is high important point. As you know, every database has to manage its statistics according to number of rows. And if you do not collect stat, than you performance as well as refresh rate are decreasing.

SAP Design Studio apps, Crystal Reports, Webi reports etc. can now be integrated with the SAP Fiori Launchpad. In this blog we’ll look at how these reports/dashboards from the SAP BusinessObjects BI platform can be integrated with SAP Fiori landscape.


SAPFioriSAPBI.png


Before you jump on the how-to section, i recommend watching this demo video which shows how the reports/dashboards look in SAP Fiori launchpad.

 

 


Ok, I hope you watched the demo, now we’ll look at the how-to part.


The following walks you through the steps to integrate a SAP Design Studio application with SAP Fiori, however you can follow the same steps to integrate any report or dashboard with SAP Fiori.

 

Step 1: Generate the OpenDoc URL from the SAP BI Launchpad

  • Login to the SAP BI Launchpad and right click on the report or SAP Design Studio app that you want to make it available in SAP Fiori Launchpad, and select Document Link

     FIBI1.png

  • Copy the link to a notepad.

 

Step 2: Create New Launchpad

  • Login to SAP Fiori front-end server, and run transaction code LPD_CUST
  • Click New Launchpad, and enter the details as shown in the below figure.
  • Click continue

     FIBI2.png

  • Next, create an application by clicking New Application
  • Enter the details as shown in the figure

Link Text: Liquidity Forecast

Application type: URL

Paste the URL which we copied in Step 1 in Additional Parameters

Application Alias: LiquidityForecastApp

     FIBI3.png

Step 3: Create Semantic Object

            In SAP GUI, run transaction code /UI2/SEMOBJ, and add a new semantic object as shown in the figure below.

    FIBI4.png

 

Step 4:  Create a new Catalog

  • Login to SAP Fiori Launchpad Designer from your browser.

http://<server>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=<client>?scope=CUST

  • Create a new catalog by clicking FIBI5.png
  • Select Standard, and then enter the below details.
  • Click Save

    FIBI6.png

Step 5: Create a New tile and the Target Mapping

  • Add a new tile in the Catalog by clicking FIBI7.png
  • Enter the General and Navigation details as shown below

FIBI8.png

  • Click Save
  • Now click FIBI9.png to add a target mapping. Enter the following details:

FIBI10.png

 

Step 6: Create a New Group

  • Select the Groups tab in the SAP Fiori Launchpad Designer.
  • Create a new group by clicking FIBI5.png
  • Enter the below details and click Save

          FIBI11.png

 

Step 7: Create New Role for the Catalog and Group

  • In the SAP front-end system, run transaction code PFCG
  • Enter a role name and click Single Role
  • In the role menu add the Catalog and Group which we created in the previous steps.

FIBI12.png

  • Click Save
  • Select the User tab and enter the user ID/ID’s who needs access to this SAP BI Catalog.

FIBI13.png

  • Click Save

 

Login to SAP Fiori Launchpad and you should now see the tile, catalog, and the group. Please watch the complete demo here.  


Happy Learning!

 

-Anil Bavaraju

SAP Press Author - SAP Fiori Implementation and Development

Img20.png

This article is a continuation of: New complete tutorial for setting up Introscope 9.5 Stand-alone Monitoring for SAP BI Platform 4.x (Part 1)

 

 

Step 4:  Configure each BI node and Application Server node using ACTool

 

ACTool is a free program which automates the BI / Tomcat server configurations for Introscope Monitoring.  In this step, we will configure our BI / Tomcat node using the ACTool program.  For detailed information about ACTool, refer to the ACTool User Guide.pdf under the docs directory of the ACTool download.


  1. Browse to SAP Note 2137275 and click on link provided in the Solution section under Get the tool:

    -1.png

  2. Download the zip file sap_actool-2.24.0-bin.zip and copy it to a temporary directory on your BI / Tomcat servers (in this example, C:\actool)
     
    -2.png

  3. Extract the contents of sap_actool-2.24.0-bin.zip to your temporary directory.
     
    -3.png
     
  4. Browse into the <actool>\conf directory.  Delete the file products.xml and rename the file products_bolight.xml to products.xml (we are replacing the original products.xml).  Then, edit the file boe.properties with a text editor
     
  5. Enter values for the following properties then save the changes to boe.properties:
     
    Property NameExample ValueDescription
    boe.systemmycmsnameThis is your CMS server name that you used to logon to the CMS (don't use the @clustername)
    boe.useradministratorThis is your CMS administrator user account
    boe.passwordPassword123The CMS administrator password
    boe.cmc.introscope.hostwiemhostnameThis is the hostname of your Introscope Enterprise Manager
    boe.cmc.introscope.port6001This is the port number of your Introscope Enterprise Manager
    tomcat.service.nameBOEXI40TomcatThis is the service name of the Apache Tomcat server on this host
    tomcat.service.port8080This is the http port number of the Apache Tomcat server
    wily.EM.hostwiemhostnameThis is the hostname of your Introscope Enterprise Manager (same as boe.cmc.introscope.host)
    wily.EM.port6001This is the port number of your Introscope Enterprise Manager (same as boe.cmc.introscope.port)
    smdagent.pathC:\usr\sap\DAA\SMDA98This is the path where you installed the Diagnostic Agent (up to the SMDAxx folder).  In this example, I installed the Diagnostic Agent to the C:\ drive using system DAA and instance 98


  6. In the folder where you extracted ACTool, double click run_actool.bat.  Type 2 and enter to choose the option SAP BI PLATFORM 4.x then type 1 and press enter for the option to Execute.
     
    -4.png
     
  7. Next, press enter to start all the configurations or refer to the selective options below:

    SELECTIVE OPTIONS:

    - If this host does not have Apache Tomcat, you can enter 2,3,4,8,9,19 to skip the Apache Tomcat setup

    - If this host does not have BI components but only Apache Tomcat, enter options 4,12,14,15 to only setup Apache Tomcat and SAP Host Agent (or if you didn't install the Diagnostic Agent choose options 12,14,15)



     
    -6.png

  8. When the script is completed, you can close it by typing 'quit' and press enter.  Step 19 may report a failure, this indicates that the SMD Agent must be restarted manually.  Restart the services, SAPDAA_98, and SAPHostControl
     
    SAP_DAA.png

  9. Finally, restart the SIA and Apache Tomcat on this server.
     
    -7.png
      
     

Step 5:  Validate the installation/configuration is working

 

  1. First, logon to your BI Launchpad and refresh some Webi / Crystal / Dashboard documents to generate metrics.
  2. Next, open the Introscope WebView in a web browser (for example http://wiemhostname:8081/webview )
  3. Enter the default logon information (user: Admin password: Admin89)

    admin.png

  4. Click on Investigator, then expand *SuperDomain* and expand the hostname you just configured.

    webview.png
  5. Confim that this host has the SAP HostAgent Process, SBOP ENTERPRISE\HOST, and Tomcat nodes under the host name.

    Note:
    If there is no Tomcat instance on this node, then only check for SAP HostAgent Process and SBOP ENTERPRISE/HOST
    If there is no SIA on this node then only check for SAP HostAgent Process and Tomcat or if you didn't install the Diagnostic Agent, only check for Tomcat

  6. Next, in the WebView, click on the Console tab, and confirm that metrics appear under dashboards Apache Tomcat Memory, BOE 4.0 PLATFORM, and BOE 4.0 WEBI SERVER DETAIL

 

        dash0.png

        dash1.png

        dash2.png

Previously, I posted on the SCN an article on how to setup Introscope Monitoring for the BI Platform.  This article is a replacement to the previous article posted here: A complete guide to setup CA APM Introscope 9 for monitoring SAP BI Platform 4.1 on Windows [PART 1/2]

 

Due to changes in the new SAP Solution Manager Diagnostic Agent 7.4, there has been a period of time where it was not possible to setup Introscope monitoring for the BI Platform unless you had the full SAP Solution Manager stack in your environment.  After some research, testing, and working with various teams here at SAP, I'm happy to announce that you can once again setup Introscope monitoring for your BI landscape.

 

This article is applicable to those SAP BusinessObjects customers who:

 

  • Do not have an SAP Solution Manager system
  • Do not have an SAP Basis team or ABAP / Netweaver experience
  • Would prefer to only implement Introscope Monitoring tools without the full SAP Solution Manager stack

 

 

BEFORE YOU START:  Please be aware, this article is for setting up CA APM Introscope in stand-alone mode aka BOLight (without Solution Manager).  If your goal is to setup Solution Manager for BI, please check the following SAP Notes for instructions:

 

 

 
Here is the workflow we will follow:

 

  • Step 1:  Download the installation media from the Software Download Centre
  • Step 2:  Install the Introscope Enterprise Manager
  • Step 3:  Install the Diagnostic Agent on each BI node and application server node
  • Step 4:  Configure each BI node and application server node using AC Tool
  • Step 5:  Validate the installation/configuration is working

 

 

Step 1:  Download the installation media from the Software Download Centre

 

First, we need to download each piece of software from the Service Marketplace.  The files required for this configuration are part of the SAP Solution Manager files on the Software Download Center.   If your company has a Standard or Enterprise Support contract, you should have usage rights and access to download SAP Solution Manager software. If you find that your S-USER does not have access to download one of these files, open a message under component XX-SER-SWFL and request access to download the file.  If you are installing to an operating system other than Windows x64 or if you are having trouble finding the files by browsing, then use the search option to search for the file names under Support Packages and Patches and locate the version appropriate for your platform.  In the table below, you can copy the file name and paste it into the search box as it is the exact search term that should be used.  Furthermore, if you find that the downloads do not complete successfully using the links below, then instead search for the files in the Software Download Center and add them to your download basket.  Once they have been added to your download basket, you can then download them via the software SAP Download Manager.

 

 

File NameLinkDetails
SAPCAR 7.20DOWNLOADSAPCAR is used to extract files from SAR archives (similar to winRAR).  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the SAPCAR version for your specific platform
WILY INTROSCOPE ENTERPRISE MGR 9.5DOWNLOADInstall media for the CA APM Introscope Enterprise Manager.  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the WIEM version for your specific platform
WILY INTRO EM MGMT MODULES 9.5 SP6DOWNLOADManagement modules and customizations files which contain SAP instrumentation and BOE dashboards
SWPM10SP10DOWNLOADThis is the Software Provisioning Manager (replaces the older sapinst).  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the SWPM version for your specific platform
721 UC Kernel for SWPM SP10DOWNLOADThis is the Kernel file and includes the Diagnostic Agent 7.4.  Note, this file is platform specific.  The link provided is for Windows x64 platforms.  If you are installing to another platform, please search for and download the Kernel version for your specific platform
eula.txt
(Right click and save target as)
DOWNLOADLicense agreement for CA APM Introscope
osgiPackages.v9.5.6.0.windows.zip  (Right click and save target as)DOWNLOADOSGI Packages required for Introscope Enterprise Manager installation

 

 

Step 2:  Install the Introscope Enterprise Manager

 

SAP provides a read-only version of CA APM Introscope (RTV version) for free as part of your support contract.  This means that you can leverage the monitoring and root cause functionality provided by Introscope, without spending additional money on a full license.  Should you decide that you want to create alerts, customize dashboards, or utilize the Websphere/Weblogic power packs, then I encourage you to contact your account executive about upgrading to the SAP Extended Diagnostics package (SED).

 

The Introscope Enterprise Manager should be installed on a dedicated server which has 24/7 uptime.  All of the performance metrics are stored in the SmartStor database which is maintained by the Introscope Enterprise Manager.  For best performance, you should install to a dedicated hard disk with plenty of available disk space (300gb or more).  The Introscope Enterprise Manager makes frequent read/writes to this disk and works best if nothing else is reading/writing to this disk in parallel.

 

  1. Copy the Introscope Enterprise Manager 9.5 SP6 media (WILYISEM06_0-70000324.zip), Introscope 9.5 SP6 customizations (WILYISMM06_0-70000299.zip), eula.txt, and osgiPackages.v9.5.6.0.windows to a temporary folder on the host where you will be installing the Introscope Enterprise Manager

    1.png

  2. Extract WILYISEM06_0-70000324.zip to a folder WILYISEM06_0-70000324 then move eula.txt and osgiPackages.v9.5.6.0.windows.zip to this folder
     
       2.png
  3. Edit the file eula.txt and change "reject" to "accept" to accept the end user license agreement

    3.png

  4. Edit the file ca-eula.txt and change "reject" to "accept" to accept the end user license agreement

    4.png

  5. Edit the file installer.properties.  If you want to change the default install location, update the property USER_INSTALL_DIR. Next, set silentInstallChosenFeatures to All

    5.png

  6. Double-click on the file introscope9.5.6.0windowsAMD64SAP.exe to launch the silent installer.  Wait about 2 minutes and check the install directory for failed log files.  If no failed log is generated then the install worked.  Confirm the install worked by checking your start menu

    6.png

  7. Next, we need to turn up the Max Java heap setting for Introscope Enterprise Manager.  Browse to your Introscope install bin directory and edit the file C:\usr\sap\ccms\apmintroscope\bin\EMService.conf.  Change the Maximum Java Heap Size to 2048

    7.png

  8. Next, extract the file WILYISMM06_0-70000299.zip to folder WILYISMM06_0-70000299.  Browse to folder WILYISMM06_0-70000299 then select all files and copy them to your clipboard

    8.png

  9. Browse to the location where you installed CA APM Introscope Enterprise Manager (by default: C:\usr\sap\ccms\apmintroscope) then paste the contents of your clipboard to this folder.  When prompted, check the option Do this for all current items and select Yes to merge the contents.

    9.png

  10. Next, go to Administrative Tools and restart the Introscope Enterprise Manager service

    10.png

  11. Copy the files SAP_BOBJ.jar and SAP_Apache_Tomcat_Basis.jar from <DRIVE>:\usr\sap\ccms\apmintroscope\sap\extra_modules to <DRIVE>:\usr\sap\ccms\apmintroscope\deploy

  12. Open a web browser, then browse to the Introscope WebView.  For example (where wiemhostname is your Introscope Enterprise Manager hostname):  http://wiemhostname:8081/webview
  13. Logon to Introscope using the default credentials.  User: Admin and Password: Admin89

    admin.png

  14. On the Console tab, click the drop-down menu for Dashboard to choose a dashboard
  15. Confirm that the BOE 4.0 dashboards are installed.  Confirm the Apache Tomcat dashboards are installed

    dash4.png

 

Step 3:  Install the Diagnostic Agent on each BI node and application server node

 

In this step, we will install the Diagnostic Agent 7.4 on each BI node and Web Application Server node.  If the BI node and Web Application Server node are on the same host (as shown in this example), then you only need to install the Diagnostic Agent once.

 

  1. Copy SAPCAR*.exe, the SWPM (SWPM10SP10_1-20009707.SAR) and Kernel file (51050688_6.zip) to a temporary directory on your BI server (in this example C:\media)

    _1.png
  2. Extract the contents of 51050688_6.zip to this temporary directory.  The extracted Kernel folder will be named Krnl_7.21_WIN__IA32__IA64__x64__SP10_

    _2a.png


  3. Open a command prompt and browse to your temporary directory and run the command:

    SAPCAR_617-80000938.EXE -xvf SWPM10SP10_1-20009707.SAR

    _2.png

  4. After the files are extracted, execute the command

    sapinst.exe SMD_INSTALLATION_SCENARIO=ishub

    _3.png

  5. After the Software Provisioning Manager starts, scroll down to the bottom of available options, expand Generic Options, Diagnostics in SAP Solution Manager, then choose Install - Diagnostics Agent and click Next

    _4.png
  6. Next, uncheck the option "Provide the path to each archive seperately" and check "Provide Path to Installation Media".  Click the Add button, then under Media Locations, click the browse button and browse to the location where you extracted the Kernel folder Krnl_7.21_WIN__IA32__IA64__x64__SP10_.  Once you have selected the Kernel folder, click Next.

    _6.png


  7. On the next page, confirm that the hostname is correct and click Next.

    _7.png

  8. By default, the agent installs to the C:\ drive.  Change the Destination Drive if you prefer the files to land on a different drive.  Click Next.

    _9.png

  9. The installer will create 2 user accounts on the localhost for the agent service accounts.  Click Next.

    _10.png


  10. Enter in strong passwords (uppercase and lowercase letters, numbers, special chars etc) for each user account being created by the agent installer

    _11.png
  11. You may receive some warnings about the Operating System Version, it is ok to continue on. Click Next then click No.

    _12.png

  12. Next, enter a strong password to use for the new account sapadm and click Next

    _13.png



  13. When prompted if we want to add SAPServiceDAA to the trusted users list, choose Yes.

    _15.png

  14. You will be prompted to choose an Instance Number, leave this as the default of instance 98 and click Next.

    _16.png

  15. When prompted to Choose the SLD destination, select No SLD Destination and click Next.

    _18.png

  16. When prompted for the Connection of the Diagnostics Agent to SAP Solution Manager, choose Do not configure connection then click Next.

  17. On the Unpack Archives screen, click Next.

  18. On the Parameter Summary page, click Next and the install will begin.

  19. Once the installation finishes, you are done installing the Solution Manager Diagnostic Agent.

 

Continue to part 2:  New complete tutorial for setting up Introscope 9.5 Stand-alone Monitoring for SAP BI Platform 4.x (Part 2)

WHAT IS THE ANALYTICS VALUE MAP?

 

The Value Map for Analytics helps you quickly identify the relevant SAP Enterprise Support services, tools, and expertise for a particular objective relating to your SAP Analytics product such as an implementation or upgrade.
Whether you are interested in discovering SAP Best Practices for BI Platform or setting up a BI4 Monitoring solution, you can benefit from our social collaboration platform - SAP Jam.

We can help you to build a road-map to support your whole project with documentation created from customer feedback and with forums to discuss your opinions, challenges or to post your questions to SAP experts and to interact with other customers.

SAP Analytics experts are available via SAP Jam to support you through your project.
Discover best practices, reduce effort and improve results!
It is open for Enterprise Support and PSLE customers to join.


SO WHAT TYPE OF CONTENT IS AVAILABLE?


In the Value Map we have put together all of the relevant Empowerment offerings from the SAP Enterprise Support Academy related to BI Platform (and other analytics products). You can work directly with a Focus Adviser to plan a support roadmap of ES deliverables to help ensure your projects are safeguarded, and landscape is operating optimally.  These offerings include:

  • Meet the Expert live meetings and recordings
  • EGI (Expert Guided Implementation) sessions – these are live guided tutorials held over the course of 3-5 days to help you setup BI Platform managed system setup and EWA activation in Solution Manager among other topics.
  • QuickIQ – short tutorials on administrative and operational tasks
  • Best Practice documentation on a wide variety of topics
  • We also have details about remote delivered CQC services to safeguard major events such as a new Implementation or Upgrade project. 

In conjunction with these fixed offerings (all free for Enterprise Support and PSLE customers) you also have the collaboration potential of the SAP JAM infrastructure to give us your feedback and let us know if you feel there are any knowledge gaps that exist. Based on your input we can work to create content you would like to see, when possible.
We also have weekly feed updates to bring you the latest support related news.

 


HOW CAN I JOIN?


For further information on the Enterprise Support Value Map Analytics, please visit our SAP Enterprise Support Academy landing page or register here to join now.
When registering via the link above, select “Analytics Value Map – SAP Enterprise Support” from the drop-down list and fill in your Company details and any objective you may have.

We look forward to working with you!


Here's a quick preview...

Analytics VM preview.PNG

 

Analytics Value Map Team. 

Hi Folks! Following my initial series of Geek Tweaks on SAP BusinessObjects Lumira today we will be seeing some Geek tweaks on our famous BI Platform. BI Platform at this form of writing is in version 4.2 currently on GA which promises lot of enhancements, improvements and new features which we have been waiting. You can read more about the new features http://scn.sap.com/community/bi-platform/blog/2016/01/11/sap-bi-42--bi-platform-new-features

 

Some of the tweaks explain the internals of the Platform and are for information purposes and some of them might be dangerous to try in your environment. You are responsible for performing any tweaks related to this.

 

“God does not make mistakes, the rest of us better take backup”

 

List all Internal BI Service

SAP BI Platform is built on principle of modular design and exposes its end points as Services so that other applications, clients can consume and communicate with them. Some of the internal SDK operations are also relay on web service to get their job done.

BI Platform uses the famous Apache Axis2 as its engine to process and expose the service. You can find the list of internal services used by the dswsbobje by using the following URL.

 

http://<host>:<port>/dswsbobje/services/listServices

 

This can be also used to check if the service is running or not. If this particular service has issues, SAP BusinessObjects Design Studio may not be able to communicate with BI Platform.

There are some more other services to explore from your webapps folder which is found under <BOBJ Install>\SAP BusinessObjects\tomcat\webapps

Changing the location of Data folder

The Data folder that is present in SAP BI platform acts as a cache and is also responsible for storing the session. Each node in the cluster will have separate folder in the format of hostname_SIAport. In addition to it, some of the services will also have its own folder to store their content.

The data folder should be in a High speed IO disk with less latency for high performance of the BI system. By default, it is located at the following location <BOBJ Install>\ SAP BusinessObjects Enterprise XI 4.0\Data

You can mount a high speed storage on this location so that BOBJ can then take advantage of it. On Linux based deployment it can be done by using the mount command while in Windows it can be done with the power of mklink


mklink /J “<BOBJ Install>\ SAP BusinessObjects Enterprise XI 4.0\Data” “<Destination>”

 

Finding and changing PID of BOBJ Process

BOBJ platform consists of lot of processing servers which internally spins up numerous process each having unique PID (Process Identifiers). These PID are used to identify the process and start them. You can find the same of each process in your task manager running under the service account which is used to start SIA.

 

1.png

 

All of the process always run in the same PID. That is because it is easy to operate a process when its PID is known. BOBJ stores all of the PID files in the following location

 

<BOBJ Install>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\serverpids

 

Although changing them is not recommended, changing the PID on the process file and restarting SIA would result in the process running with the new PID.

 

Default Bootstrap BI Platform files

SAP BI platform has a set of default bootstrap files that are created during the install time. Those files hold configuration information and details about the deployment and the instance. The location of these configuration files is

<BOBJ Install>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64

_boe_<nodename>.bootstrap contains the default deployment information in XML, internal Java process configuration and values for various key that the BI Platform uses.

_boe_<nodename>.dbinfo contains the encrypted database information that is used by BOBJ to access the DB

_boe_<nodename>.keyfile contains the encrypted key that is used by BOBJ to encrypt the artefacts in DB

 

Tweak Advance Configuration

BOBJ is a versatile platform with ever growing features, one of the important aspects of it is the fact that it’s modular and configurable. Hidden amidst of BOBJ files are some advance configurations which can be found at

64 bit

<BOBJ Install>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\config

32 bit

C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\config

 

The configuration folder contains a lot of configuration information including the version of BI Platform and other XML based configuration used by each process in BI Platform.

 

1.png

WebI Properties

Locate and open the file webiProperties.txt document to find some rendering options that are set for WebI

 

1.png

 

Apart from this, there are quite a bit of configurations that cannot be covered in this post. Lookout for future posts on those advance configurations.

 

Starting the CMS in console mode

Console mode is used when the CMS is refused to start or when there are some issues with it which needs some advanced debugging. Often console is used by SAP to debug the CMS when an issue is raised to them. Using the console mode can cause irreparable data corruption or data loss.

 

More details on the console mode is given on SAP Note 1828536

 

Securing your BOBJ with FIPS 140-2

BOBJ has support for FIPS based encryption. FIPS stands for Federal Information Processing Standard which is standards that specify requirements for cryptography modules. If your company compiles with this standard, you can enable FIPS to leverage the option in BI Platform.


Simply add the switch –fips to the SIA command in SIA properties to enable fips.


1.png

FIPS mode is stricter and prevents old clients that does not follow this to connect to BI Platform. If you are using old clients this may not be an option for you.


That’s all folks in this posts, Keep lookout for more Geek tweaks and if you have any, feel free to post below in comments.

Actions

Filter Blog

By author:
By date:
By tag: