Microsoft

Blog Categories

Subscribe to RSS feed

Archives

Parshva Vora

Parshva Vora is a Technical Architect at Perficient since 2009 and has extensive experience building enterprise solutions, portals and software products using Microsoft technologies.

Posts by this author: RSS

Sitecore acquires commerceserver.net

Last week, Sitecore announced acquisition of commerceserver.net from SMITH(formerly Ascentium), a global digital agency that develops and supports it. Commerceserver.net is a continuation of Microsoft Commerce Server. Acquisition of commerceserver.net complements well as it brings B2B and B2C e-commerce capabilities to Sitecore’s Customer Experience Platform(CXP). As per Sitecore press note, “Sitecore’s acquisition lays the foundation for the industry’s first .NET based, enterprise-grade Customer Experience Management (CXM) platform with a native, fully integrated e-commerce engine.”

Sitecore LogoComServ_H

 

 

 

 

Commerceserve.net is developed on .Net stack and integrates well with Microsoft technologies so existing customers can choose to integrate it tightly with Sitecore’s customer experience platform. Sitecore will continue to offer it as a stand alone product as well. Commereceserver.net’s cloud offering is currently available through AWS market place and it has plans to make it available for Windows Azure. Read the full anouncement here

 

Sitecore Wins Critic’s Choice Award for Best Enterprise CMS!

Yet another win for Sitecore! Sitecore wins Critic’s Choice Award in “Best Enterprise CMS” category after winning People’s Choice Award in the same category last month.  Sitecore and winner of the last year, Adobe CQ5 which is re-branded as Experience Manager were running neck and neck for People’s Choice Award but Sitecore won it in the end. Unlike People’s Choice Award, Critic’s Choice Award isn’t based on nominations and as per CMSCritic, a panel comprised of reputable judges consider and evaluate all CMS products. Read the full announcement here .

Sitecore Logo

CMSCritic further notes that strong content management capabilities coupled with digital marketing components makes Sitecore a well rounded platform for enterprises. Predictive personalization, ability to serve personalized content based on analytics gathered across different channels, have become the major reason for enterprises to choose Sitecore over other CMS products as this usually translates into increased customer engagement and hence better ROI. Gartner also noted it in its latest Magic Quadrant report and has recognized Sitecore as an industry leader. Read full Gartner report here.

 

Sitecore in Windows Azure

What is Sitecore Azure?

In simple words, it is your Sitecore implementation running in Windows Azure, a popular cloud computing platform from Microsoft. Sitecore Azure provides development and deployment tools to support Sitecore CMS and DMS(Digital Marketing System)  in Windows Azure.

Windows Azure: As you may already know, Windows Azure services are available both as IaaS (Infrastructure as a service) and PaaS(Platform as a service). To be precise it offers four execution models for your application:

  1. Virtual machines(IaaS)
  2. Cloud Services(PaaS)
  3. Web sites
  4. Mobile services

Please see Window Azure page to know more of various execution models and other information.

Sitecore – PaaS and IaaS

Sitecore Azure – PaaS: Your Sitecore environment in Azure is maintained and patched automatically, instead of you working with virtual machines directly and managing them. Your implementation can be scaled out by adding large building blocks such as instances, web roles and farms.

Sitecore in Windows Azure – IaaS: You can get a virtual machine, created out of a standard disk image or your own disk image and you are responsible for patching, installing updates and maintaining it. It offers you more control, with added maintenance liability though.

Subscription Options

Sitecore Azure subscription – It is a PaaS offering where your Sitecore installations were managed by automated Sitecore features.  You can also use your existing Windows Azure subscription for Sitecore Azure installation.

Windows Azure subscription: You could choose to subscribe to Windows Azure directly and manage Sitecore on your own. You can still use deployment tools that Sitecore Azure uses.

(more…)

Accessing Sitecore items – A structured approach

It is very trivial to retrieve items from Sitecore content repository. Like any other CMS, Sitecore provides APIs for reading and enumerating items and item fields and there is nothing special about it. Without wasting time, let’s talk code straight away. Consider following two lines of code typically found in code behind of a SubLayout:

 Sitecore.Data.Items.Item item = Sitecore.Context.Database.GetItem("/sitecore/content/home/products/tv");

            if (item != null)
            {
                String title = item["Title"]; //Sharp 47.9" LED TV
                double price = Convert.ToDouble(item["Price"]); //1200
                double size = Convert.ToDouble(item["Size"]);// 47.9

            }

Assume the following data template inheritance:

Data template inheritance

(more…)

Integrate your Salesforce.com implementation into Sitecore CMS

Gone are days when going online for an enterprise was considered a proud moment and the only purpose its public facing website served was an instant ‘brochure’ for visitors about its products and offerings. Nowadays visitors can not only browse the information but also can purchase directly on the website or show an interest into particular product or service. Predictive personalization, among many powerful capabilities Sitecore has, is the most notable one as it tracks visitor’s behavior and maps to a predefined pattern which is used then to show relevant content to the visitor.

If your company’s public facing website like ours is powered by Sitecore CMS and a tool of choice for sales folks in your company is Salesforce.com, wouldn’t it be nice to share an intelligence and analytics gathered by Sitecore with Salesforce.com and turn a casual visit into a lead? Wouldn’t it help your sales guy to better understand customers’ behavior and buying patterns? You can essentially drive your Salesforce.com through your public facing website. Similarly showing information stored in Salesforce.com on to Sitecore web site or utilizing it to personalize the content could result into rich experience for web site visitors. Empowering visitors to search documents and information stored in Salesforce.com(SFDC) or view SFDC reports can help your sales people stay focused by not requiring them to manage content through Sitecore CMS.

Enabling information exchange between these two vast systems can truly leverage your company’s investments into Sitecore and Salesforce.com. SFDC objects such as leads, accounts, contacts, opportunities and custom objects are accessible through REST APIs. These APIs are categorized into two: customer APIs and partner APIs. Customer APIs are for a project that is specific to a customer or a situation while partner APIs can be used to develop if a project is meant to be used by several customers. Similarly Sitecore exposes information stored into it such in form of APIs or web services. One may write a custom layer that can bridge two systems. Also a third party connector called S4S(Sitecore for Salesforce) from FuseIT can be used to connect two systems. To the best of my knowledge, it is the only such connector available in the market.

(more…)

Search Engine Optimization for SharePoint 2013 Sites (Part II)

SEO features in SharePoint 2013 are bundled into a SearchEngineOptimization feature. Its feature.xml file references two element files – searchengineoptimization.xml(SEO.xml) and searchengineoptimization1.xml(SEO1.xml). SEO.xml defines elements that make up its UI by extending ribbon interface. It also registers few candidate web controls with AdditionalPageHead delegate control. Delegate control is a powerful mechanism to alter application behavior declaratively. One or more candidate controls are added to control tree dynamically based on the sequence number(lower sequence number will be added first) depending upon the configuration of a delegate control. All web controls are defined under Microsoft.SharePoint.Publishing namespace.

SEO.xml also adds an SEOSettings application page(_layouts/15/SEOSettings.aspx) where you can configure canonical URL and verify site ownership.

searchengineoptimziation.xml

SEO1.xml defines all SEO properties for page such as browser title, meta description, sitemap priority, sitemap change frequency as site columns. It means you can access these fields pragmatically like any other site columns. Note that “Sealed” property for all fields is set to true which means that they aren’t extensible.

(more…)

SharePoint 2013 – Farm and App level ECTs in BCS

SharePoint 2013 introduces the concept of App level External Content Type(ECT) which allows model representing external entities to be packaged along with app in single unit so later it can be accessed by app to understand and integrate external data without outer dependencies.

External Content Types(ECTs) and External List – BCS(Business Connectivity Services) is an umbrella term in SharePoint referring to functionalities and activities for modeling, management and manipulation of external data. Schema of an external entity or business concept is represented in SharePoint by an external content type much like a content type describes native SharePoint entities. External List can then hold items of specific external content type, again the way List can have items of one or more content types. The major difference is External list can contain items of only one external content type.

What is inside BDC model?

(more…)

Client data access with OData and CSOM in SharePoint 2013

SharePoint 2013 has improved OData support. In fact, it offers full-blown OData compliant REST based interface to program against. For those who aren’t familiar with OData, OData is an open standard for querying and updating data that relies on common web standard HTTP. Read this OData primer for more details.

The obvious benefits are:

1. SharePoint data can be made available on non-Microsoft platforms and to mobile devices
2. SharePoint can connect and bring in data from any OData sources

Client Programming Options: In SharePoint 2010, there were primarily three ways to access SharePoint data from the client or external environment.

 1. Client side object model(CSOM) - SharePoint offers three different set of APIs, each intended to be used in certain type of client applications. (more…)

Consuming OData sources in SharePoint 2013 App step by step

SharePoint 2013  has an out-of-box supports for connecting to OData sources using BCS. You no longer are required to write .Net assembly connector to talk to external OData sources.

1. Open Visual Studio 2012 and create a new SharePoint 2013 App project. This project template is available after installing office developer tools for Visual Studio 2012.

Create App

Select App Settings

2. Choose a name for the app and type in the target URL where you like to deploy the App. Also choose the appropriate hosting option from the drop-down list. For on promise deployment select “SharePoint-Hosted”. You can change the URL later by changing “Site URL” property of the App in Visual Studio.

3.Add an external content type as shown in the snapshot below. It will launch a configuration wizard. Type in OData source URL you wish to connect to and assign it an appropriate name. For this demo purpose, I am using publicly available OData source NorthWind. (more…)