Configure Habitat on Sitecore V9.1

To install Habitat on your local machine it's required to have Sitecore 9.1 instance on your system. First install sitecore 9.1 with the of below article.
https://sharjeelswork.blogspot.com/2019/04/sitecore-91-installation-step-by-step.html

Step 1:  Enable ASP.NET 4.7 
Open (Windows Feature on or off) from Control Panel. Click on check box for ASP.Net 4.7 and click ok. 



































Step 2: Download and Unzip Habitat-1.7.zip package from https://github.com/Sitecore/Habitat/releases
 Download Habitat-1.7







Unzip the package to a folder on your local machine, for me it’s placed in my system at
Location - F:\RSI\SharjeelsWork\RD\Habitat-1.7

Step 3: Modify Config Files
It is required to change in few configuration files. In those files you must update the settings with the appropriate values for your environment.
  • Habitat.Dev.config In the configuration folder, modify the   file. Modify the sourceFolder variable to match the path to your Habitat Src

Location: .\src\Project\Habitat\code\App_Config\Environment\Project\Habitat.Dev.config

  • Habitat.Website.config Modify the TargetHostName variable to match the path to your Habitat Sitecore instance (example: 9Dot1.sc)

Location: .\src\Project\Habitat\code\App_Config\Include\Project\Habitat.Website.config















  • Gulp-config.js Modify the instance Root variable to match the path to your Habitat Sitecore instance root (example: C:\inetpub\wwwroot\9Dot1.sc)

  • publishsettings.targets Modify the publishUrl to match the path to your URL             (Example: http://9dot1.sc) Location: .Configuration\publishsettings.targets



Step 4: Configure gulp and node js  First we configure gulp on the same location where our source code is placed. Run below commands in node.js cmd


npm install gulp-cli -g
npm install gulp -D
npx -p touch nodetouch gulpfile.js
After successful run of above commands install npm modele with command npm install
Step 5 :Open Visual Studio 2017 and Run as Administrator. Open the Habitat solution placed at Location- F:\RSI\SharjeelsWork\RD\Habitat-1.7. Now Open the Visual Studio 2017 Task Runner Explorer.

Go to Habitat Solution in VS 2017, run Task “default”


Errors: I got error in syncing unicorn as display in below screen shot.

To fix above error I just run http://9dot1.xconnect/ on my system and then re sync the unicorn item but again got same issue. After searching on net I got help from(https://community.sitecore.net/developers/f/5/t/10052). After applying steps written in this article I got error regarding Rainbow.SFS.SerializationFolderPathMaxLength issue
To fix this issue I made changes in Rainbow.config file and increase the value of Rainbow.SFS.SerializationFolderPathMaxLength upto 120.
Step 6: Rebuild search indexes  Go to your Sitecore Instance (example:http://{sitename}/sitecore).



Note: This is required for Habitat search-based features to work properly. Click on rebuild the indexes.
Step 7: Habitat setup done and ready to use. To verify please go to your IIS and browse the instance 


Habitat application will run on you system as shown in below screen.









On the basis of Habitat sample we can work on many things related to component in sitecore. As this solution is based on Helix based Design Principle so all the component behave as an individual module. 

Happy Learning!!!















Comments

Post a Comment

Popular posts from this blog

Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0

Image
I got above error after adding dependency in Maven POM xml file placed under newly created AEM arch type and running command  mvn -PautoInstallPackage clean install . Error : DependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.aem:uber-jar:jar:apis -> version 6.3.0 vs 6.4.0 After google and gone through few article I got command ( mvn -PautoInstallPackage -Padobe-public clean install) . Once I run this command this issue with jar compatibility was resolved. Happy Learning!!!
Read more

ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote'

I was getting below error while working with cache management on CM and CD server. Actually my code was working fine on CM server but I was not able to access or clear cache object on CD server because of wrong event selection.  PID[18108] Error       ManagedPoolThread #3 16:24:16 ERROR Exception while handling event Sitecore.Eventing.Remote.PublishEndRemoteEventException: System.AggregateExceptionMessage: One or more exceptions occurred while processing the subscribers to the 'publish:end:remote' event.Source: Sitecore.Kernelat Sitecore.Events.Event.EventSubscribers.RaiseEvent(String eventName, Object[] parameters, EventResult result)at Sitecore.Events.Event.RaiseEvent(String eventName, Object[] parameters)at Sitecore.Eventing.Subscription`1.Invoke(Object instance, EventContext context)at Sitecore.Eventing.EventProvider.RaiseEvent(Object event, Type eventType, EventContext context) Above error comes due to wrong event args access in CD server. T...
Read more

Dot Net Core Application Packaging using Octo

Image
Octo.exe is a command line tool that interacts with the Octopus Deploy REST API and includes a pack command to create packages either as Zip or NuGet packages for deployment with Octopus. Installation We recommend installing Octo as a global tool using .NET Core which makes Octo available as a command via the .NET CLI. If you have the .NET Core 2.1.300 SDK available you can install Octo onto a machine or build agent as a global tool with the following command: dotnet tool install Octopus.DotNet.Cli –global Publish your application There are two ways to publish your dot net core application. One you can do from command line and other from Dote net solution it self. Command Line Dot net publish source/sharjeelsWorkCore.Web --output published-app --configuration Release dotnet publish F:\RSI\SharjeelsWork\RD\Core\sharjeelsWorkCore\sharjeelsWorkCore\sharjeelsWorkCore.csproj --output published-app --configuration Release Dote Net Solution Right c...
Read more