Configure your SharePoint farm for Business Intelligence
•Descargar como PPTX, PDF•
2 recomendaciones•3,060 vistas
SharePoint farms have wide variety of shapes and sizes, and depend on multiple supporting technologies, including SQL Server, Active Directory, Reporting Services, and Analysis Services. Unfortunately, not all versions of the supporting technologies support the new Business intelligence features of SharePoint 2013 and Office 2013. This session will walk through multiple configuration scenarios designed to make the most of the BI investments in SharePoint and Office 2013. We will use demonstrations to outline what services are necessary to use the new data model and PowerView in Excel, when and where both PowerPivot and PowerPivot for SharePoint are needed, and what you need to do in your farm to take advantage of these features. In addition, we will explore some of the assets available to PerformancePoint Services, and what configurations can help bring out the best in its features. Finally, we will explore some best practices around configuring Reporting Services for SharePoint.
Recomendados
Recomendados
Más contenido relacionado
Último
Último (20)
Destacado
Destacado (20)
Configure your SharePoint farm for Business Intelligence
- 1. Configuring your December 1st, 2012 SharePoint farm for Business Intelligence John P White Chief Technical Officer UnlimitedViz Inc jpw@unlimitedviz.com @diverdown1964
- 2. Thank you to all of our Sponsors!!
- 4. It’s a little known fact….
- 6. Personal BI Team BI Organizational BI My Context Our Context The Org’s Context BI solution created by user. BI Solution created by power BI Solution created by IT, Context is only for user & exists user. Context is for a small Established corporate context & as document. team & it’s managed on a is reusable, scalable and backed server. up.
- 7. PowerPivot for SharePoint not required
- 9. Office Pro Plus license Requires AS SP Mode xVelocity model enabled SharePoint Enterprise and Excel Services as required CAL Deploys as SP Service PowerPivot add-in Included on SP media SQL Server BI or application included, must be Deploys as service Enterprise enabled application Deploys as SQL service PowerView and-in Requires AS SP Mode for on independent servers included, enabled as xVelocity and Power View Load balancing needed interactivity performed by Excel Services
- 10. PowerPivot for PowerPivot for Analysis Services SharePoint (SQL SharePoint (SQL SharePoint Mode Server 2008R2) Server 2012) (SQL 2012 SP1) Excel 2010 with Yes Yes* Yes* PowerPivot (2008 R2) Excel 2010 with Yes Yes Yes*** PowerPivot (2012) Excel 2010 with No Yes** Yes** PowerPivot (2012 SP1) Excel 2013 with or No No Yes Without PowerPivot * Can Only Refresh Slicers ** Cannot use SP1 features with Power View *** Limited to pre SP1 PowerPivot feature set
- 11. Deploys as SP service application Alerting Required for BISM/Power Self service subscriptions View Power View
- 12. Deploys as SP service application For analytic charts/grids
- 13. Excel Services Reporting Services PerformancePoint PowerPivot Other Stuff Analysis Services
- 14. Excel FE Profile Services Search ……. DB SSAS SSIS SharePoint Foundation SQL Server Server OS Server OS
- 15. FE Profile Excel Search ……. DB SSAS SSIS SSRS PP Services SharePoint Foundation SharePoint Foundation SQL Server Server OS Server OS
- 16. WFE Profile Excel Services Search ……. SSRS PP DB SSAS SSIS SharePoint Foundation SQL Server Server OS Server OS
- 31. Excel FE Profile Indexer Search Metadata …. SSRS PP Services SharePoint Foundation SQL Server Server OS
- 32. WFE Profile Excel Services Search ……. SSRS PP DB SSAS SSIS SharePoint Foundation SQL Server Server OS Server OS
- 33. FE Analysis Services – Profile Excel Services Search ……. SSRS PP SharePoint Mode SharePoint Foundation SharePoint Foundation SQL Server Server OS Server OS Server OS DB SSAS SSIS SQL Server Server OS
- 34. Excel FE Search SSRS PP Services Analysis Services – Profile Crawl Metadata SSS SharePoint Mode SharePoint Foundation SQL Server SharePoint Foundation Server OS Server OS Server OS DB SSAS SSIS SQL Server Server OS
- 35. FE Analysis Services – FE SharePoint Mode – – Analysis Services Profile Indexer Search ……. SSRS FE Analysis Services SharePoint Mode Profile Indexer Search ……. SSRS FE SharePoint Mode – Analysis Services SharePoint Foundation Profile Indexer Search ……. SSRS SQL Server Mode SharePoint Excel SharePoint Foundation Profile Search ……. SSRS PP Services SharePoint Foundation SharePoint Foundation SQL Server SharePoint Foundation SharePoint Foundation SQL Server SharePoint Foundation SQL Server SharePoint Foundation Server OS Server OS Server OS Server OS Server OS Server OS Server OS Server OS Server OS Server OS Server OS Server OS DB SSAS SSIS SQL Server Server OS
- 40. Analysis Services - SQL Server Analysis Services SharePoint Mode Excel Services No Yes No Reporting Services Yes Yes No Power View (RS) N/A Yes No PerformancePoint No Yes No Both SETUSER() and EFFECTIVEUSERNAME require elevated permissions (Administrator for AS, dbowner or sysadmin for SQL)
- 46. Remember to fill out your evaluation forms to win some great prizes! & Join us for SharePint today! Date & Time: Dec 1st, 2012 @6:00 pm Location: Pub Italia Address: 434 ½ Preston Street Parking: On street with meters $ Site: http://www.pubitalia.ca/
Notas del editor
- At the end of the day, please ensure your evaluation is signed and handed in for door prizes. The draw takes place in Room 102A.
- Here’s a little demonstration of what you can do when you have it all working together…The GSAF is a loose collection of all reported shark incidents
- Org BI has been with us forever – Decision Support Systems – Reliable and curated, but unresponsivePersonal BI evolved to plug the performance gap – problem is that it’s unreliable and out of controlAllow users to share, with oversight in a team scenario – that’s what SharePoint provides. A platform for reliable BI collaboration
- The products stack up much as expected, with SQL Server SKUs filling the Enterprise spaceOffice apps as expected cover much of the Personal BI space – with add-ins from the SQL teamThe team area is a mixture, with products from both teamsIt’s worth noting that the second most requested feature of any 3rd party BI application is export to Excel. Using SharePoint, Excel can actually be a client, meaning it can stop being a part of the problem and become a part of the solution.
- Another way to look at the tools – through their uses
- Big change is that xVelocity is included, as have PowerPivot and PowerViewParalleling that on the server, what was once simply PowerPivot for SharePoint has been segmented into its two constituent parts. It was always Analysis Services + automation, but it was tightly coupled. Now it can be scaled separately, and Excel Services handles the load balancingA number of other new features are available that may affect architecture, including per-user authentication
- Covering 3 Major AreasExcel ServicesReporting ServicesPerformancePoint
- Excel the client enables the personal BI.Office Pro Plus means NOT Home and Student, or RT – no model for surface… In 2013 xVelocity is built in, and PowerPivot and PowerView are included and must be enabled (show)To share workbooks, Excel services is necessary. Interaction with the data model requires Analysis Services SharePoint modeTo refresh automatically and use the Gallery, you need PowerPivot for SharePoint
- Although PowerPivot and Power View are included, they are disabled by default, and need to be enabled if you want to work with them. This is done easily enough – (Demo in Excel). Also, if you click the Power View button, it’ll offer to do it for you. In addition, the xVelocity engine isn’t used by default, it must be activated on a workbook by workbook basis. There are ample opportunities to do this – when importing data, when inserting imported data into the workbook, or when working with the data. Finally, if PowerPivot is enabled, using it will also create the model.
- 4 client versions, 3 server versions. SQL Server 2012 SP1 brings new features to the table – required for the new models
- What works with what? Essentially, you’re looking at good downward compatibilityOf note – Excel 2013 models won’t work with pre 2013 SharePoint farms. Just sayin’Upgrade your farm before your Office apps
- SSRS is comparatively generous – doesn’t even need a SharePoint licenseSharePoint mode does need at least a standard license (there’s an Express…)The really cool features need BI or EnterprisePowerView needs Tabular models
- PerformancePoint is an aggregatorRequires SP EnterpriseAS needs to be available for analytics charts or grids (either mode)
- Some pieces are built by the Office team, some by the SQL Server teamCan lead to confusion – consider ta common misunderstanding
- This is a very common small farm architecture. All the SQL bits on one server, all the SharePoint bits on anotherReporting Services and PowerPivot for SharePoint are on the SQL server mediaBoth require Farm joined servers to operate
- Far too often, this is what results. SharePoint gets laid down on the SQL boxSQL performance is impactedManagement headaches increase
- Correct approach is to put the SQL bits on the SharePoint server not the other way around
- Let’s walk through the setup of the 3 major groups, starting with Analysis Services SharePoint mode/PowerPivot
- These screens look the same for installation on Standalone or on SharePoint“SQL Server PowerPivot for SharePoint” is ConfusingNeed BI or Enterprise license to see this option
- - This is the only place where we see the terminology “Analysis Services”
- Must install into a named instanceLeaving it as PowerPivot not required, but recommended
- Must use a domain account – shouldn’t be a managed one
- - Accounts used to connect through BISM MUST be AdministratorsFarm account should be administratorNext up – Go to Excel Services Application settings and show the data model settings
- - At this point, we can register the engine with Excel Services, and we’re good
- From here only applies to installation on a SharePoint ServerRequired for scheduled refreshes, PowerPivot galleryDo NOT need to have the Analysis Services instance on the same server (but you can (classic mode))
- Already configured in this farm, so we’ll use screenshots. Starting with 2012, the configuration tool was added. When you run it, you get the option of configuring, repairing or removing PowerPivot for SharePointIf you want to remove it – use this tool
- The tool analyzes the system to determine what is necessary for configurationWhere input is needed, you see an alert
- I recommend changing the name of the application and the databaseDefault PowerPivot is a bad name, and GUIDs are evil
- - The tool will deploy assets to a single site collection. If you have multiple, this must be done manually
- When Ready, use the validate button, and all indicators should turn greenThere are a couple of post configuration steps that need to be doneChange the Excel Services default sizeAdd the Central Administration address into trusted pathsChange the prompting optionsGrant spServices correct permissions in the Administration databaseCheck the data model settings
- Setting Up:Service ApplicationSubscriptions and AlertsReport Library – Report Builder/Data Tools for ContentBISM Connection – Power View Report
- We’re not doing PowerPivot, so we select SQL Server feature installation.
- - RS – SharePoint is the Service Application- RS Add-in for SharePoint is the old fashioned add –in MUST be deployed on all front end servers!
- PerformancePoint is straightforwardCan be done by the “white wizard”
- As with any SharePoint service application, BI features can be scaled out nowA few differencesWorth walking through a growth scenario
- Start with an all in one SharePoint farm (NOT a standalone!)
- Let’s add or BI services to our SharePoint box. Simple enough
- Now lets move the server that the users interact with (the FE server) onto its own box. We can also separate out the model processing onto a standalone (non farm joined) server. This way, services execution doesn’t impact user requests.
- Another approach is to segment by functionNot strictly role basedLong running processes separated from user interacting processes
- - Obviously all of these services can themselves be scaled out and load balanced
- For SSRSService app needs to be installed on “application server” roles – Responsible for processing and rendering the reportAdd in must be installed on FE server – unlike the past where it was automatic. Connects to service appFor xVelocityAdd “PowerPivot for SharePoint” to standalone serversAdd “PowerPivot for SharePoint” add in to at least one “application server” roleBoth can be on one – will impact SP performance
- A non-comprehensive collection of things to be aware or “notes from the field”
- Explain Double hop problem Kerberos constrained delegation allows token passing, but hard to set upReporting Services has supported this for a long time via SetUser() – nobody understood itBISM implicitly supports EFFECTIVEUSERNAMEPerformancePoint and Excel Services now support EFFECTIVEUSERNAME against multidimensional sources
- Quick demo using SSRS on how this works
- - Connection account needs very elevated permissions to use (dbOwner or SysAdmin) Keep in mind the the service account for the services in question need Admin access to the Analysis Services server (makes a connection)EXCEL Services and PerformancePoint for AS, SSRS for SQL (except PowerView, which is BISM)
- Real value of SP as a platform is its integration capability. Whole > sum of partsDashboarding is obvious – pull together assets from all of the different tools using the web part framework.To consider – leverage other SharePoint assets – like the filter parts, in particular the current user filter. To use this filter effectively, your user profile subsystem must be healthy. Many people are unaware of it, or its extensible powerOld import system available in SP2013
- Integration in Action – Using a profile field to drive an SSRS parameter
- More integration – turning things around. How to Report on SharePoint DataSP data design makes it inefficient. Best to extract into a data warehouse like other transactional systemsImprove performance and simplify maintenanceWorkflowHistoryList is a prime exampleBlog entry of how to clean out
- Everyone has a red bar. Need to fix thisProblem is spurious rules – need to repair real problems – disable spurious rules