How to deploy an existing PerformancePoint dashboard to a new site? - sharepoint-2010

Apologies if the question is not worded appropriately.
I've created a dashboard using the dashboard designer and succesfully deployed it to our development server. Now I'd like to deploy it to our staging server - is there a way to do that?
I've tried pointing the designer at a different URL without success.
Thanks,
Phil

I ran into same issue and thanks to Umair for reminding me about the import option with the Dashboard Designer. You will open up designer in new location and then use the Import option and point to your ddwx file.
Here is the posting and references from the forum posting - Deploy PPS 2010 dashboard content to new server
I have an additional link in the forum post at the bottom that will send you to the link to the technet documentation as well.

If you only have SSAS reports and SSAS data sources then the PerformancePoint 2010 Content Deployment Tool might be of help.
I have used it to deploy dashboards and reports to another server without issues. It even lets you deploy remotely from dev to other servers if you have the needed permissions. Pretty neat tool, sadly it hasn't been updated recently and still lack a few key features (as the ones I described above).
PPS in SP2013 comes with this built in, but I haven't studied the details yet. Just picked it up from the PPS team in this blogpost
Never figured out a good way to deploy SP lists data connections and SSRS reports though.

Related

SharePoint 2013 Performance Point

Dashboard designer error:
The url is not available,does not reference a sharepoint site, or you
do not have permission to connect
This is happening to the site collections under one web application only in the whole Farm. Other web applications are working fine and I can open site collections through dashboard designer.
Any suggestions????
Unattended acc is all set, Site feature is activated, site collection is added to trusted location. On database side, app pool acc has db owner access to web app db. PPS is db owner there as well.
I think this indicates to a deployment issue on this app. Maybe something went wrong when deploying webparts, the assemblies couldnt be registered or were not copied correctly. It could also be a specific access restriction issue in SharePoint or in the file system that SharePoint relies on.
Without any log information it is hard to say what is really the problem - but - have a look at windows event log for any further indications, the general log files that sharepoint/asp.net write or also consider using monitoring tools that can tell you more details on what is happening here.
I recently wrote a blog on top deployment mistakes in SharePoint. I highlight exactly these deployment mistakes in more details: Link
Andi

TFS Admin Console

I wonder that about this problem: tfs_configuration & my tfs_testcollection in TFS Admin Console and SQL MS.
What is recommended solution for backups and restore tfs_configuration in TFS Admin Console ? I ask because sometimes it happens that collection and configuration are out of sync ? Could you recomend best solution for preventing these problems? Any msdn site or books or blog with solutions ?
Thank you in advance.
Lucas.
It's because this out of sync, is recommended you do the backup by Admin console, using the tools Backup! This feature will syncronize all database of TFS, including Reports, Sharepoint, etc..
The only supported and documented method of creating a backup in TFS is to use marked transaction logs. In versions before 2010 this was a manual process documented on MSDN. In 2010 the TFS team added a tool to the Power Tool to make it easyer. That tool was a big set up but was still a little flakie around the edges. In 2012 update 2 this was finally consistent enough to make it into the tool and be available in the Admin Console.
I have a blog post and video on how to configure the manual and power tool option: http://nakedalm.com/creating-a-backup-in-team-foundation-server-2010-using-the-power-tools/
You can find full documentation on MSDN.

How to properly configure application in Live Connect and project in Visual Studio 2013

My question here is pretty simple: how to properly (and 100%) configure both Live Connect and project in Visual Studio 2013 in order for the local application run and authenticate an user properly against Microsoft account.
My question may be simple, but the answer is most likely not as simple. I've been reading countless articles and possible tutorials about this, but they are all fragmented and divided into small parts that do not really conciliate each other.
So below is the situation better described, with the steps I have followed.
[Steps Followed]
1) I have created a simple MVC application using Visual Studio 2013.
2) I have configured the project (using its properties) to use IIS Express with current Project Url : https://localhost:44302/
The project runs quite well, and external authentication with Facebook, Google and Twitter run very well too. Now for the tricky part:
3) I have created account with Microsoft and successfully created application in the Live Connect Developer Center.
4) Since configuring the field Redirect URLs to a simple http://localhost:<port> will not work (well...just because they didn't want it to, I suppose), I have additionally done the following..
5) Mapped in hosts file the following domain to localhost: # 127.0.0.1 mytestdomain.localtest.me
6) Reconfigured in Live Connect the Redirect URLs field to use the newly mapped domain: http://mytestdomain.localtest.me (although I have tried this with or without the port as well).
[End result]
With this configuration, the site runs properly locally. However, when I try to sign in with Microsoft account credentials (so, when I click the "Microsoft" button), I have redirected and received the following message:
"We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later."
I honestly do not understand why wouldn't this work, when a couple of articles suggested that doing these specific steps would make it work.
What can I be missing, why would this happen at all?
If someone can write here what am I missing and we could all join effort and create in this topic a full fledged, 100% working configuration for local application testing with Microsoft authentication, I believe it would help everyone. If such topic already exist and you can point me to it (because clearly I have missed it) it would also be great.
Thank you in advance,
Mad
Actually I just found out a proper and direct answer to my question. I totally missed it somehow during the last few days of research.
Microsoft's blog has all you need to make it work, and now mine does too. No big explanations and discussions, just basic and direct step by step article.
For those who could not find it and stumbled upon my topic here in StackOverflow, here is the link. Follow it word by word, and it will work.
Answer : Configuring your ASP.NET application for Microsoft OAuth account

Sonatype Insight - Application Health Check - Is it ok to share application composition details to the remote Sonatype Insight Server

Has anybody used the Sonatype Insight-Application Health Checker ? It requires you to scan your application ( war, jar, zip etc ) and then uploads its findings onto the Sonatype Insight Server. After this, you get the report via the email which also contains an online link to the interactive report.
The problem that i find with this approach is that my application composition details get uploaded to a remote server ( outside my organizational control ) and then the report gets published at an online link which can be accessed by anyone. I do not want this. Is there a way to generate this report without uploading the details to the 'remote server' ?
But the bigger question is, are application owners and organizations ready to share their application composition details to a server outside their reach while performing IP audits on their applications ?
Please let me know what the general pereception about this is ?
Generally, if you're only sending meta-data about your open source usage - that's not sensitive information.
If you have privacy issues, you can also check out White Source software that provide similar service on cloud.
lots of people use the system to generate a quick and easy manifest of their application based on open source component use. If you a are concerned about anyone else theoretically knowing what open source components you are using, then you may be interested in our on-premises version of this tool for enterprises.

Team Foundation Server reporting stops refreshing after adding a CMMi repository

I have this problem and did not find in the site a case like mine.
Here is the thing.
I created a TFS 2008 with the scrum template (Conchango). It was a clean install (a fresh OS, a fresh SQL Server, a fresh machine, etc…). So everything worked like a charm.
I created 3 Scrum repositories, assigned permissions, uploaded files and so on… 3 teams started working on them, and everything was super!
Up to this point the server only had 3 scrum repositories and nothing else.
Then, I had to create a new repository, but with the CMMi template (the one provided with TFS).
Again everything works (the Sharepoint site, the source control, documents..) … BUT…. Reports stopped refreshing!!!
Does anybody know how to fix it?
Any help will be really appreciated
Should you need more info please let me know
Found someone with the same problem, reports do stop working after adding CMMI project :)
The following link has an explaination of how to fix it:
http://blog.salvoz.com/2008/01/26/TFSWarehouseIssues.aspx
First of all, you didn't create a new repository. You created a new team project.
Secondly, the trick is to go find out why the reports stopped refreshing! There's no well-known bug, "reports stop refreshing when adding a CMMI Team Project: here's what to do". You'll need to go look on the database tier server and see if there are any problems listed in the event logs or the SQL Server logs. Then track it down.
I had one situation where Analysis Services crashed, restarted and crashed again - because I hadn't set up operator notification. It's necessary to look, in order to see.