JSS Server Setup for Headless Architecture with Sitecore v9.1


In this article I am trying to setup JSS server for disconnected developer mode. Advantage of Disconnected mode is that application can be deployed without availability of sitecore instance. In this mode sitecore content can be mocked in flat files like(yml/json/js).
Benefit to work on disconnected architecture are as 
• Browser automatic render changes done by developer.
• Execution will be fast as data is coming from flat/local files. 
• Development will be fast as complete server is based on node js.




Note : Disconnected mode will be helpful to handle site which is having huge traffic. It provides additional scaling options, better scalability, and lower hosting costs for heavy traffic.

Prerequisite: 
• Install node, JSS and angular with the help of my last article.
• Install Sitecore V9+ as explained in my previous article.
JSS License for Sitecore: 
• JSS server-side functionality requires an JSS-enabled license file.
• To check if your license is a JSS-enabled license, open your license.xml in a text editor and search for Sitecore.JSS - if it's found, you're ready to use JSS. Not there? Read on.



Sitecore Component for scaled server installation
It is required to download and install package from sitecore site (https://dev.sitecore.net/Downloads/Sitecore_JavaScript_Services.aspx)To maintain sitecore server for production which may have one or many CD server. This package is required in server configuration for scaling purpose.




Install this package from sitecore development tool – installation wizard. Upload the package and install it.






After package installation please verify that installed package with below url from your sitecore instance.
http://jssapp.9dot1.sc/sitecore/api/layout/render/jss?item=/&sc_apikey=TEST




Configure a site name for JSS app with sitecore instance in site definition configuration file.


After configuring site on required route add a website or binding in existing website in IIS. Here I created a new site in IIS and entered site name in host file.








API Key for JSS
Sitecore service client (SSC) provide the API key for service which is used by JSS. Also the same API is used by many sitecore features like 
• Layout Service
• GraphQL
• Tracking Service
• Dictionary Service

Login to your jss sitecore instance as mine is available with url on my local system. http://jssapp.9dot1.sc/sitecore
Now open content editor and go to location /sitecore/system/Settings/Services/API Keys
Add a new key inside AppKey folder as I had created with name NewsApiKey




CORS Origins: If you will be using connected mode (quite likely), the APIs will need to support CORS so that your dev server (default: http://localhost:3000) is allowed to make HTTP calls to the JSS services. For purely local development setup, use * to allow all origins. In production, only allow specific origins (multiple origins are ;-delimited).

AllowedControllers: Use the following value. It is also possible to use *, but explicitly whitelisting controllers is a best practice. If you use additional custom SSC API controllers, they would need to be added to this list. Note that GraphQL endpoints require both the GraphQLController to be whitelisted, as well as the GraphQL endpoint URL (with GraphQL:/path/to/endpoint/from/config):

  Sitecore.LayoutService.Mvc.Controllers.LayoutServiceController; 

  Sitecore.JavaScriptServices.Globalization.Controllers.DictionaryServiceController; 

  Sitecore.Services.GraphQL.Hosting.Mvc.GraphQLController;

  GraphQL:/api/yourappname




Verification: Make a request to the Layout Service on your Sitecore 
Host: http://9dot1.sc/sitecore/api/layout/render/jss?item=/&sc_apikey={EEB0638F-B5B9-4F00-8AC9-9D9C0741AFA1}



Now I am able to access API from sitecore instance. In this way setup is completed now I will focus on deployment of JSS application with sitecore in my next article.


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

Operators in Asterisk with Linux

Operators When you create an Asterisk dialplan, you’re really writing code in a specialized scripting language. This means that the Asterisk dialplan—like any programming language—recognizes symbols called operators that allow you to manipulate variables. Let’s look at the types of operators that are available in Asterisk: Boolean operators These operators evaluate the “truth” of a statement. In computing terms, that essentially refers to whether the statement is something or nothing (non-zero or zero, true or false, on or off, and so on). The Boolean operators are: expr1 | expr2 This operator (called the “or” operator, or “pipe”) returns the evaluation of expr1 if it is true (neither an empty string nor zero). Otherwise, it returns the evaluation of expr2. expr1 & expr2 This operator (called “and”) returns the evaluation of expr1 if both expressions are true (i.e., neither expression evaluates to an empty string or zero). Otherwise, it returns zero. expr1 {=,
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. There are two event args in
Read more