only My site

Wednesday, June 26, 2013

SharePoint 2010 farm topologies

Testing and Verifying SP2010 after software Installation and configuration


Even though you are ready to head out the door and head home since you are probably doing this on a night or weekend, it is really important to fight the urge to leave too soon. You really need to do some basic testing and verification before you leave. It will be a lot better to find out about any problems now rather than when the next business day has already started.
Here is what I recommend doing before you leave:
  1. Browse to each of your SharePoint web applications and log in with your user account and make sure you can hit the home page of each of them.
  2. While you are there, try to open up and edit a document in the browser using one of the Office 2010 Web Apps (Word, PowerPoint, Excel or OneNote).
  3. Browse to your My Site and verify that everything is working normally.
  4. Add a unique phrase to a test page somewhere in one of your Sites (I always use the phrase “jabborwocky” Smile) and then go run an incremental Search crawl from Central Administration. After the crawl completes, go back to your Site Collection and search for the phrase. Verify that it comes up in the results.
  5. Run an incremental User Profile Synchronization from the User Profile Administration page. While it is running, logon to the desktop of the new Application Server, and find this program and run it: c:\program files\microsoft office servers\14.0\synchronization service\uishell\miisclient.exe. This is the Forefront Identity Management (FIM) client application that you can use to see the details of the AD synchronization process. Several jobs will be run by FIM. Verify that they all complete successfully with no error messages.
  6. In Central Administration, go into Manage Service Applications and click on Managed Metadata Service and select Manage in the ribbon. Verify that the Term Store management interface loads and that you can add/change/delete a Term Set and some Terms.
  7. Finally, reboot your WFE and Application Server. When they come back up, check your Windows System and Application event logs on those servers and verify that there are no SharePoint-related critical or warning events that you haven’t seen before you scaled out to three tiers.
  8. Browse to your primary web application one more time before you head out the door.
Source : http://sharepointsolutions.com/sharepoint-help/blog/2011/02/how-to-scale-out-a-sharepoint-2010-farm-from-two-tier-to-three-tier-by-adding-a-dedicated-application-server/

Thursday, June 13, 2013

Bootstrap CSS framework - faster and easier web development

Sleek, Intuitive and powerful front-end framework for faster and easier web development

http://twitter.github.io/bootstrap/base-css.html#typography
 

Tuesday, June 4, 2013

Apply Theme for Publishing site


public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
   ApplyTheme(properties);
}
/// <summary>
/// Sets master page and css properties for the site collection
/// </summary>
/// <param name="properties"></param>
private void ApplyTheme(SPFeatureReceiverProperties properties)
{
SPSite site = (SPSite)properties.Feature.Parent;
if (site != null)
{
// System Master Page
Uri masterUri = new Uri(site.RootWeb.Url + "/_catalogs/masterpage/v4.master");
site.RootWeb.MasterUrl = masterUri.AbsolutePath;
// Publishing Master Page
Uri customMasterUri = new Uri(site.RootWeb.Url + "/_catalogs/masterpage/mycustom.master");
site.RootWeb.CustomMasterUrl = customMasterUri.AbsolutePath;
//logo and css
site.RootWeb.SiteLogoUrl = "/_layouts/MyProjectName/Images/mycustomlogo.jpg";
site.RootWeb.AlternateCssUrl = "/Style Library/MyProjectName/css/mycustomcss.css";
site.RootWeb.Update();
}
}