Skip to main content

SFCC Development environment setup- II Create Digital Server Connection

You need to connect your eclipse to your Sandbox or Staging Instance to upload code and debugging.


  • ·         File > New > Digital Server Connection


          Project Name: Digital Server [You can give any name in your choice]
          Use default Location: Default enabled, you can change the location


          Connection Setting     


  • Host Name : Fully qualified domain name of your instance [without http or https]
  • User name  : username of your instance
  • Password     : Password of your instance




 


  • Select the version directory to upload the code. Each version is a separate directory to contain Cartridges so it should be called version directory





The server uses the code version in the Active directory field. Select this version if you want your code changes to be visible in the storefront.

  • Whether you click next or Finish depends on whether you are creating storefront cartridge. If you are following the Developer Getting Started trail, you have not yet created a cartridge.

    If you haven't yet created a cartridge, click Finish.
    If you've already created a cartridge, click Next to associate the cartridge with the server.
        • Select the cartridges you want to associate with the server, and click Finish.
 


  • If the Do you want to download the API source cartridges now? Message appears, click yes. These cartridges let you take advantage of new B2C Commerce features, providing a strong foundation for your ecommerce storefront.


  • ·         Click Yes.

  • ·         During the download, the log output scrolls in the Studio console. When the download is complete, the Cartridge Explorer view appears within Studio

  • ·         Refresh the server connection and verify that the latest B2C Commerce API is downloaded to your Studio workspace. 
    • In a workspace, it is possible to import or create multiple Projects (Cartridge) but only select the necessary cartridges for the project to upload.
     
    • We can select or deselect after creating the connection at Project References (Right click on Server Name → Properties → Project References → select / deselect cartridges)
     
After creating a Digital Server, right-click on the created Server name to open the Digital Server menu.
  • Active Server: 

    In the same workspace, you can create multiple Digital Server Connection to many different sandboxes. But only one server can be active at the same time. Code after the change will be uploaded to the server to be active


  •  Auto-Upload :The code changes will be automatically uploaded to the server to be active.
  •  Change Upload Staging Directory: Change the version of the uploaded code.
  •  Download Digital API: Download the SFCC API update.
  • Download Web Service API: Download the updated SOAP web service (Defined in the web references and webreferences2 of the cartridge.).
    Upload Cartridges: Upload all selected cartridges in the Project References section to the sandbox.
     


Comments

Popular posts from this blog

SFCC Development environment setup-III Create a Storefront Project

Creating a storefront project depends on whether you are using SFRA or SGJC. SFCC recommends SFRA for new implementation In this section we will see how to create a storefront using SFRA Create Custom SFRA cartridges Implementing a site requires at least one custom cartridge. However, if you intend to create multiple sites, we suggest you create multiple custom cartridges. Each cartridge can separate functionality specific to a brand or locale, so that you can reuse most of your cartridge stack for a new site Cartridges can be created using  sgmf -scripts   This script is useful for creating Storefront Reference Architecture overlay cartridges. All of the scripts are executable through CLI [ https://www.npmjs.com/package/sgmf-scripts ] Follow the steps to install  sgmf -scripts globally and use the script to create new custom cartridge 1.   Update the node by using below command D :\ SFCC \ temp \ demo - site > npm   install - ...

Salesforce Commerce Cloud Hooks - SFCC Hooks

Hooks in SFCC is a CommonJS script module. Hooks can be configured as a piece of functionality to use it in a specific point in your application flow or at a specific event. You can use these hook s with a Salesforce B2C Commerce storefront application OCAPI hook s B2C Commerce provides extension points to call scripts before or after specific OCAPI calls Custom hook s You can define custom extension points and call them in your storefront code using the B2C Commerce script System package HookMgr class methods. You can then access the hook in either OCAPI or your storefront code. This flexibility makes them useful for functionality in a multichannel set of applications based on the same site. Hook Definition The package.json file will have the hook file entry for a cartridge. The hook file definitions shown as below {     "hooks" :  "./hooks.json" } The hook file defines a uniquely named extension point and...

Salesforce Commerce Cloud Create Custom Job Step-I Task Oriented Script Module

Creating custom task oriented job steps involves the following steps, 1.   Create a  CommonJS module that  exposes a function to be called as the main function for the job step 2.   When administrators create jobs using Business Manager, they set parameters that are available as scriptable objects for the module's function 3.   The  dw.job.JobStepExecution object allows read-only access to information about the current step execution and job execution.  4.   To control the exit status, the script module's function can return a  dw.system.Status object 5.   If the script finishes with an unhandled exception, the exit status code is ERROR, and the error status flag is true by default 6.   If no status object is returned and no exception occurs, the status code is OK by default.  Consider the following use case to explain the Task oriented job steps.  The system want to update the profile information...