Hi,
Service Pack (SP) 3 for PerformancePoint Server was finally released.
Here are the links to the downloads
Here is the link for the updated SP3 online documentation - http://technet.microsoft.com/en-us/library/cc514367.aspx
For more info:
http://denglishbi.spaces.live.com/Blog/cns!CD3E77E793DF6178!2066.entry
Best Regards,
Tal
Hi,
For those of you who encountered the issue of removing empty rows in a scorecard, I’d like to tell you about this very helpful link which helped me solve the issue:
http://blogs.msdn.com/performancepoint/archive/2008/04/09/hiding-empty-rows-in-a-scorecard-code-sample.aspx
In addition, I have some remarks from my own personal experience:
1. Make sure the DLL is strongly named. There are good posts for that at :
a. How to install an assembly into the Global Assembly Cache - http://support.microsoft.com/kb/815808
b. How to give strong name to DLL and how to install DLL in GAC -
http://www.c-sharpcorner.com/UploadFile/hemantpatil/111222007032935AM/1.aspx
2. Add the assembly (.dll file) to the PPS GAC server, and the [KeyName].snk to the relevant location in all your MOSS servers that will host the PPS dashboard.
3. Add the line below to the <CustomViewTransform> section of the relevant Web.config (Monitoring, Preview and MOSS viewers) :
<add key="HideEmptyRowsTransform" value=" MyCompany.GridViewTransforms. HideEmptyRowsTransform, [NameOfMyAssembly] , Version=1.0.0.0, Culture=neutral, PublicKeyToken=[ MyAssemblyPublicKeyToken]"/>
- Replace the [NameOfMyAssembly] to the name of your assembly.
- Replace the [MyAssemblyPublicKeyToken] with the public key token of your assembly.
Tal
Related Post : http://blogs.msdn.com/fooshen/archive/2008/10/18/performance-point-server-2007-and-ajax-on-sharepoint.aspx
If you have Microsoft Performance Point Server 2007 installed, and you do not have ASP.Net AJAX extension installed (probably like me, I use .Net 3.5), you will probably get errors in your site when you have a Performance Point Dashboard Item webpart loaded:
Could not load file or assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file.
Well instead of installing ASP.Net AJAX Extension 1.0, we can still make it work via Assembly Redirections. Here's how:
1. Locate the web.config file for your SharePoint site, as well as the PerformancePoint Monitoring Designer web service and its Preview directory.
2. Use any text editor (or Visual Studio), and do a search/replace to replace all references to System.Web.Extensions 1.0.61025.0 to .Net's3.5.0.0.
3. Add the following line to your web.config under the <configuration> node:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="1.0.61025.0" newVersion="3.5.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
Remember there are 3 web.configs that needs to change here:
- under PPSMonitoring/WebService
- under PPSMonitoring/Preview
- your SharePoint site
Now your PerformancePoint webparts will load fine in SharePoint (and you can use the Dashboard Designer) without having to install ASP.Net AJAX Extension!
But wait.. there's one more thing - if you tried to put in a custom-built webpart that uses AJAX (System.Web.Extensions 3.5.0.0) on the same page as your PerformancePoint dashboard items, you will get errors complaining that it cannot cast ScriptManager to ScriptManagerLoader. Huh?
What happens is that PerformancePoint's webparts load its own ScriptManagerLoader, derived from the ScriptManager class. One easy solution to make all webparts AJAX-happy is to declaratively instantiate our ScriptManager in SharePoint's Master Page instead.
From SharePoint Designer, locate your current Master Page and add the following line at the very top:
<%@ Register TagPrefix="PPS" Namespace="Microsoft.PerformancePoint.Scorecards.WebParts" Assembly="Microsoft.PerformancePoint.Scorecards.WebParts, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>
Next, right after the <form> tag, add the following:
<PPS:ScriptManagerLoader runat="server" id="ScriptManager1" EnablePartialRendering="true"/>
Here, before our AJAX webparts attempt to load its own ScriptManager, it first checks whether an instance is already created on the page. Since we have this on our master page, it won't try to add its ScriptManager again, and ditto to our PerformancePoint web parts. Since PerformancePoint's ScriptManagerLoader is derived from ScriptManager, it will still work if our webpart expects ScriptManager.
AJAX-ified SharePoint and PerformancePoint webparts living in harmony
If you have both MOSS 2007 ( Microsoft Office SharePoint Server) and Reporting Services ( not in SharePoint integrated mode) installed on the same IIS virtual server, then you have to make the below updates in web.config for them to work
1) In the Root web.config to comment out the below. Otherwise the reportserver will give sessionState partitionResolver Issue
<!-- <sessionState mode="SQLServer" timeout="60" allowCustomSqlDatabase="true" partitionResolverType="Microsoft.Office.Server.Administration.SqlSessionStateResolver, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
-->
2) In both Reportserver and ReportManager vdir web.config, the following should be added under appSettings. Otherwise you will get ReportViewer error messages
<remove key="ReportViewerMessages" />
This is because , by default MOSS uses /reports url for it’s report center and it’s the same virtual dir url for native SQL Reporting Services report manager as well.
Usefull links for installing reporing services 2008 along with reporting services 2005 on the same machine :
http://www.kingjustin.com/post/2008/08/Reporting-Services-2008-Invalid-Namespace.aspx
This is usually due to an entry missing from the web.config of your MOSS site but the entry should be made when you install PPS.
Your MOSS web.config is usually found in C:\Inetpub\wwwroot\wss\VirtualDirectories\XXXX\ where XXXX is the port that you have Sharepoint installed on.
You should have the following entry in the <SafeControls> section of the config file:
<SafeControl Assembly="Microsoft.PerformancePoint.Scorecards.WebParts, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="Microsoft.PerformancePoint.Scorecards.WebParts" TypeName="*" Safe="True" />
Once you have added it run IISReset from a commnd prompt and try your dashboard again.
related posts : http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2390017&SiteID=17
If the ERROR "Web part Error unexpected error has occured" is exists - the best think to do is to re-installing and re-configuring the Monitoring Server.
more posts : http://blogs.msdn.com/performancepoint/archive/2007/11/12/how-do-i-deploy-the-monitoring-web-part-on-a-separate-sharepoint-web-application-on-the-same-sharepoint-web-server.aspx
This new initiative will also serve to differentiate the robust IBM offering, and avoid the confusion generated by the many definitions and related terminology that have been generated relative to the topic of business performance management. Business Innovation and Optimization is not a market category; rather, it represents a collection of software technology capabilities, best practices, and industry expertise to address needs and functionality identified in several market categories, including:
- Business Performance Management
- Enterprise Performance Management
- Corporate Performance Management
- Business Intelligence
- Business Services Management
- Business Process Management
- Business Activity Monitoring
BPM is a paradigm that enables success by proactively managing business performance and the attainment of business measurements, in addition to reactively resolving individual business issues when required.Managing and optimizing business performance is a critical requirement for maximizing business profitability and returning shareholder value. In fact, in many situations, it is a critical requirement for remaining viable in today’s fast-moving and competitive business environment. Company executives are also feeling pressure from a growing intolerance for missed performance targets.And with performance measurement periods becoming shorter, management simply must have the capability to more proactively influence the outcome. To do this requires monitoring and tracking capabilities that can generate current, complete, and accurate information upon which they can immediately act. This information provides the required business intelligence for proactively managing business performance.
Forrester Research and IDC are both doing research on the intersections and convergence of BI and BPM. IDC has coined the term Intelligent Process Automation (IPA) to help explain the convergence and complementary nature of the BPM and BI markets. Both research organizations are commenting on the need to make BI actionable and process improvement repeatable. Most organizations using BI solutions don’t see sustainable, repeatable business improvement for three key reasons:
-
Most functional business line owners don’t know the details of their daily business processes
-
BI metrics and analytics aren’t made actionable
-
Existing applications and systems that track process don’t map to the way people work
Despite these challenges, companies pour millions of dollars into analytics, reporting, infrastructure, and systems every year and don’t see full return on their investments. Many common escalation issues and exceptions to common business rules are handled as one-offs, in a combination of manual work, e-mail, and meetings. BI awareness doesn’t turn into action, much less repeatable improvement. The opportunity is to turn that information into action. This is where Business Process Management (BPM) picks up and BI leaves off—by making intelligence actionable.
While developing PPS dashboards, I discovered that sometimes there are filters errors.
The main reason is members names – filter don’t like usinging " or '. It is very important to clean all the data from any characters such as " or ' before start using filter.
Using Filters with Proclarity Dashboards
While transferring parameters to Proclarity reports – there is a URL limit string that we have to know.
It is recommended to use Filters with a single selection and not multiple selections.
To cover the gap between BI and BPM solution there I decided to start clarify the synergy those solution provide. In this blog I will focus on BPM as a Performance management and not as Process management solutions.
The first question is how does BPM differ from BI?
BPM - Business Performance Management, is actually the application of BI (business intelligence) to address a strategic business need.
BPM is a collection of BI tools, domain expertise, and specialized applications to help a company, plan, monitor, and hopefully improve its performance. Whether a BPM vendor sells and manufactures BI tools or not, they are always part of the BPM solution, maybe just bundled in and hidden.
BPM makes extensive use of relational databases, multi-dimensional databases (OLAP), data-marts, unstructured data repositories, extract transform and load tools, report and query capabilities, portals, and dashboards.
A Performance Dashboard is a BI dashboard tool populated with a collection of key performance indicators, sometimes called a scorecard (Balanced or not). The current momentum and interest in BPM is helping drive the accelerating adoption of BI across the enterprise and explains why every BI vendor wants to be part of BPM either through mergers or partnerships