Sitecore Consultant. Sitecore MVP 2021 - 2026
Do you see this error while starting the SOLR?
Check the Environment Variable JAVA_HOME and if the path of the jre is correct.
In my case due to the recent JAVA sdk update the path was not changed in environmental variable to reflect the actual path.
So one of the issue could be the incorrect path. Change this to the actual path.
And here we have the SOLR service running
Login to the OrderCloud portal.
https://portal.ordercloud.io/login
You will be shown the Dashboard and an option to create New Sitecore OrderCloud Marketplace
Step 1 – Select Region
While writing this blog there are 4 Regions avaialble for you to select. As per the document you should create Marketplace in Us-West region by default so as to seed using headstart. If you want to use regions other than Us-West you might have to request this to OrderCloud team.
Select region Us-West from the region option.
Step 2 – Autoselected Environment
By default the Sandbox environment is selected for you to try the OrderCloud. If you want to access Staging or Production contact OrderCloud team.
Step 3 – Provide Mareketplace ID [optional]
Provide the Marketplace Id if you want to have your own name. Id’s are Writable i.e. if you chose your ID OrderCloud will generate the same for you or you may let the OrderCloud auto generate the ID.
Chose the Marketplace ID
Step 4 – Provide Marketplace Name
Provide Marketplace name or description here. Click on Create Marketplace.
A new Marketplace will be created and you will be redirected to the Settings tab of the Marketplace with Instance details and other Basic info.
You should also see your newly created Marketplace in Dashboard
Now lets try creating a Marketplace with the same name in the same region i.e. Us-West
You can see OderCloud doesn’t allow to create a new Maretplace with the same name
If you also try creating a Marketplace with the same name in different region it wont allow-
Create a new Marketplace without providing the ID
A new Marketplace is created and OrderCloud gave it a Unique ID
Create a file with touch command
To create a new file, use touch command followed by the name of the file-
This should create a empty file.
touch thirdfile.txt
To create multiple files using touch command-
touch thirdfile-1.txt thirdfile-2.txt
Create a file with cat command
To create a new file with cat command use redirection operator followd by file name.
This will allow to add content to the file
cat > fourthfile.txt
Cratea a file using echo command
To create a new file using echo command use redirection operator followed by file name will create empty file or add content before redirection operator to add content while creating a file.
echo "This is fifth file." > fifthfile.txt
Create a empty file with echo command
echo > sixthfile.txt
DPKG – Debian Package Manager used to install, uninstall, list and check the status of the package
It comes with .deb file.
DPKG does not honour dependecies hence we need to use APT for Ubuntu
APT stands for Advanced Packaging Tool and relies on DPKG
Use apt update command to refresh the repository-
sudo apt update
Use apt upgrade to upgrade exisitng package-
sudo apt upgradeTo install a package-
sudo apt install <package name>To uninstall or remove package-
sudo apt remove <package name>To search package e.g:- python-dev
sudo apt search python-dev
To list all the packages in repository-
sudo apt list
Everything in Linux is file
There are following type of files-
Regular files – Images/scripts/configuration and Data files
Directory – Type of files which saves other files and directories
Special files – have other types
Use file command to get the file type-
file <<filename>>
Use ls -ld command to get the file type-
ls -ld firstfile.txt
First character represents the file type
| Identifier | File Type |
| d | Directory |
| – | Regular File |
| c | Character Device |
| l | Lin |
| s | Socket File |
| p | Pipe |
| b | Block Device |
Filesystem Hierarchy
/- Root Partition
/opt – any third party program should be put in this directory
/mnt- mounts the file system from external network temporary to this folder
/tmp- copy any temporary files to this location
/media – copy any media files in this folder
/dev – contains the file character device file like external devices like mouse and keyboard
/bin – basic programs and binaries are located in this directory
/etc – configuration files
/lib and /lib64 – contains shared libraries
/usr – user related data reside in this folder
/var – system writes data such as logs
A runlevel is a categorization number that determines what services are started and
what services are stopped
| Runlevel # | Name | Description |
| 0 | Halt | All services are shut down and the server is stopped |
| 1 | Single User Mode | The root account is automatically logged in to the server and other users cannot log in to the server |
| 2 | Multiuser Mode | Users can log in to the server through CLI and network service are not started |
| 3 | Extended Multiuser Mode | Users can log in to the server through CLI and network service are started |
| 4 | User Defined | User can cusomize the runlevel |
| 5 | Graphical Mode | User can log in through CLI and GUI with network services started |
| 6 | Reboot | The server is rebooted |
Check the current runlevel use following command-
runlevel
To see the default target
systemctl get-default
To change the default target use following command
systemctl set-default multi-user.target
Understand the OS versoin and Linux machine hardware
Use uname command to display information of kernel
uname
For more information of kernel use-
uname -r
5 is Kernel Version
11 is Major Version
0 is Minor Version
1022 is patch release
azure is specific info
To understand CPU of machine use lscpu command
lscpuIn this case Architecture is x86_64 with CPU socket 1 and threads that run in parallel is 4.
To understand physical disk use lsblk command
lsblksda shows block devices of type disk
Use lsmem command to get the memory of the Linux machine
lsmem
Use free -m command to get the free memory i.e. total vs used memory
free -m
Append the command with sudo to run the command as super user
Sitecore 10.2 uses Sitecore Headless Rendering 19.0.0. See link here
See this blog for prerequisites and setting jss using next js in disconnected mode.
Follow below steps after the steps completed in above blog
Download Sitecore Headless Services for Sitecore XM
Prerequisite
Install Sitecore 10.2 XP0 on local development environment. See hte blog here if not already installed
Install downloaded package for Headless Service
Run the next js app in connected mode
Before working on connected mode create API Key
Navigate to – /sitecore/system/Settings/Services/API Keys
Create a new API Key e.g.:- nextjsservice
API key here is Item ID
Create a custom binding-
For this create a self signed certificate with a custom domain name in this case – next-jss-prj.dev.local
New-SelfSignedCertificate -CertStoreLocation C:\certificates -DnsName "next-jss-prj.dev.local" -FriendlyName "My First Next JSS App" -NotAfter (Get-Date).AddYears(10)
Create a new https binding and assign the newly create SSL certificate
Add domain to the host file – next-jss-prj.dev.local
Inititate JSS
Run the command
npm init sitecore-jss nextjsWhere would you like your new app created? C:\projects\nextjs
Initializing ‘nextjs’…
What is the name of your app? next-jss-prj.dev.local
What is your Sitecore hostname (used if deployed to Sitecore)? next-jss-prj.dev.local
How would you like to fetch Layout and Dictionary data? REST
How would you like to prerender your application? SSG
Would you like to include any add-on initializers? nextjs-styleguide – Includes example components and setup for
working disconnected
Initializing ‘nextjs-styleguide’…
Which additional language do you want to support (en is already included and required)? da-DK
Setup JSS
jss setupIs your Sitecore instance on this machine or accessible via network share? [y/n]: y
Path to the Sitecore folder (e.g. c:\inetpub\wwwroot\my.siteco.re):
Invalid input.
Path to the Sitecore folder (e.g. c:\inetpub\wwwroot\my.siteco.re): C:\inetpub\wwwroot\xp102sc.dev.local
Sitecore hostname (e.g. http://myapp.local.siteco.re; see /sitecore/config; ensure added to hosts): next-jss-prj.dev.local
Invalid input. Must start with http(s)
Sitecore hostname (e.g. http://myapp.local.siteco.re; see /sitecore/config; ensure added to hosts): https://next-jss-prj.dev.local
Sitecore import service URL [https://next-jss-prj.dev.local/sitecore/api/jss/import]: https://next-jss-prj.dev.local/sitecore/api/jss/import
Sitecore API Key (ID of API key item): {2318A20A-6DF1-4AB8-B49E-F933A3B79160}
Please enter your deployment secret (32+ random chars; or press enter to generate one):
Deployment secret– Leave this blank as this will generate new secret key
Deployment secret key is generate and stored in <<jss development folder>>\sitecore\config\next-jss-prj.deploysecret.config
JSS connection settings saved to scjssconfig.json
Connection and the deployment secret is created, now this needs to be deployed to Sitecore instance so the JSS app is able to establish a connection with Sitecoore
To deploy the config setting deploy the config to Sitecore instance-
jss deploy config
Configs are copied to Sitecore instance App_Config\Include\zzz…
Deploy the artifacts to Sitecore instance-
Since we don’t know hte thumbprint use the below command with –acceptCertificate as test
jss deploy app –includeContent –includeDictionary –acceptCertificate test
This will provide the thumbprint. highllighted in red
Copy the certificate and try deploying again-
jss deploy app –includeContent –includeDictionary –acceptCertificate E4:54:12:A0:7E:D5:95:9B:B0:C2:00:17:3A:26:1B:AD:71:73:9F:05
if you see this error while importing – Message: An item name must satisfy the pattern: ^[\w*\$][\w\s-\$]*((\d{1,})){0,1}$ (controlled by the setting ItemNameValidation)
Change the ItemnameValidation to .* while importing and revert back to original in Sitecore.config file. Refer this –
To run the app run following command
jss start:connected
If you receive this error-
Execute following command to get this working on port 3000
$env:NODE_TLS_REJECT_UNAUTHORIZED=0Execute JSS start again-
jss start:connectedERROR-
Connection to your rendering host failed with a Not Found error. Ensure the POST endpoint at URL http://localhost:3000/api/editing/render has been enabled.
Copy the deploy secret and update the – value of setting of JavaScriptServices.ViewEngine.Http.JssEditingSecret in Sitecore.JavaScriptServices.ViewEngine.Http with the deploy secret.
This now work in connected mode. Any content changes in Sitecore should reflect localhost:3000 and Sitecore instance (https://next-jss-prj.dev.local/)
Sitecore next js working in connected mode with SSL
Error-
Exception thrown while importing JSS app
Exception: System.UnauthorizedAccessException
Message: The current user does not have write access to this item. User: sitecore\JssImport, Item: ContentBlock ({23CE8001-F405-5E50-AE61-AD3057660BBD})
Source: Sitecore.Kernel
Resolution-
Error-
Resolution-
Check if the API key is correct at the location – /sitecore/system/Settings/Services/API Keys
Also check if the CORS and Allowed Controllers are set correctly
For developement environment put * for both the highlighted fields
Prerequisite
Install Node js – Download the latest node js from here
Install JSS CLI
npm install -g @sitecore-jss/sitecore-jss-cli
Create a new next js app using JSS CLI
Note the project name should be valid as per below error
next-jss-prj1 is not a valid name; you may use lowercase letters, hyphens, and underscores only.
Numbers not allowed in project name
jss create next-jss-prj nextjs
Installs all the required artifacts in the specified folder
Run the next jss app in desconneted mode-
jss start
The app should listen to port 3000
Errors–
JSS CLI is running in global mode because it was not installed in the local node_modules folder.
Resolution– Install jss cli locally. Also ensure you are in correct directory. Should be in project directory
npm install @sitecore-jss/sitecore-jss-cli
Follow these steps to install Sitecore Commerce 10.2 On Premise. To successfully install refer to Installation Guide provided by Sitecore.
Before installing Sitecore Commerce install Sitecore XP 10.2. See this blog to install Sitecore XP 10.2 using SIF. Say the XP site name is- xp0.sc
Hosting Environment Requirements/ Download and Install following software-
IMPORTANT – As per the release notes –
The deployment of SXA has been removed from the Commerce installation, and instead installed as a Platform pre-requisite before installing Commerce packages.
Install Powershell Extension for Sitecore – Download Sitecore PowerShell Extension for Sitecore
Install Sitecore Experiemce Accelerator 10.2.0 – Download Sitecore Experience Accelerator 10.2.0
Also Commerce Ops service is removed from deployment configuration this will reduce deployment time and hosting cost.
Before starting the installation ensure XP 10.2 instance is working and indexed. If not indexed rebuild all search indexes-
Download Sitecore Experience Commerce 10.2
Step-by-step installation process-
2. Copy and extract Sitecore.Commerce.WDP.2021.11-8.0.218.zip file to c:\scinstallation\xc folder
3. Copy Sitecore Experience Accelerator 10.2.0 rev. 04247.zip file c:\scinstallation\xc folder
4. Copy Sitecore.PowerShell.Extensions-6.3 – IAR.zip file to c:\scinstallation\xc folder
5. Extract Web Platform Transfomer nuget package and copy Microsoft.Web.XmlTransform.dll to c:\scinstallation\xc folder
6. Extract SIF.Sitecore.Commerce.7.0.37 to c:\scinstallation\xc folder. Rename this to SIF
7. Folder structure should look like this-
8. Install Sitecore.PowerShell.Extensions-6.3 – IAR.zip package in your earlier installed Sitecore instance
9. Install Sitecore Experience Accelerator 10.2.0 rev. 04247.zip pakcagein your earlier installed Sitecore instance
11. Open Deploy-Sitecore-Commerce.ps1 file in SIF folder to update the following-
12. Create Commerce Engine Connect Client Secret for the Sitecore Identity Server
$bytes = New-Object Byte[] 32
$rand = [System.Security.Cryptography.RandomNumberGenerator]::Create()
$rand.GetBytes($bytes)
$rand.Dispose()
$newClientSecret = [System.Convert]::ToBase64String($bytes)
echo $newClientSecret
13. [Optional] Update Sitecore domain or keep it default
14. Update other DB related settings
15. Update SOLR details-
Execute Deploy-Sitecore-Commerce.ps1 script to install commerce
IMPORTANT – After deployment is complete Disable TLS 1.3 over TCP for all the sites and all bindings
Errors-
Error -The remote server returned an error: (400) Bad Request. on GetIdServerToken
Resolution – Check your admin credentials if correctly configured in installation script.
Error – Commerce roles site not reachable
Resolution- Check if the SSL certificate for Comerce Engine is in Trusted Root Certification Authorities. If not copy the relevant certs to same.