Get started with Optimizely Configured Commerce
Get started with Configured Commerce
Starting a project with Optimizely Configured Commerce requires some configuration and setup before development can begin. The steps below explain what is needed to get up and running with Configured Commerce.
Integrate Configured Commerce with other Optimizely products
Environment setup for developers
To set up your Configured Commerce developer environment, the following must be completed You understand Git technology and command line tools. You have created a private GitHub repository and have access to edit collaborators.
Customer and partner co-development
Optimizely Configured Commerce and its related products have traditionally been implemented by our experienced and certified solution implementation partners. Configured Commerce differs from other Configured solutions in that it is natively deep and rich with features and functionality, while remaining fully extensible and integrates smoothly with other external systems (ERPs, Tax services, Payment Gateways, etc.
Keep mobile in mind
To help you plan for and build Configured Commerce extensions that will work with the Configured Commerce Mobile App both now and/or in the future, consider the following scenarios when approaching development. Optimizely recommends adding custom business logic on the API and/or server side first.
WebAPI controller
The WebAPI controller contains the RoutePrefix which identifies its RESTful path. Configured Commerce modules that expose a RESTful API layer must derive from BaseApiController.
Module services
The main purpose of services within a module is to operate the handler factory. This is where the Chain of Responsibility is executed.
Provision a cloud project
The implementation team is responsible for all development work. As a result, they must initiate the request to provision Optimizely Configured Commerce environments in the cloud for Optimizely customers.
Add or update websites for a cloud project
You may decide to add or update websites, or subdomains, to your existing project. Before you do, see Microsite support in Spire for websites using the Spire CMS, or the Multi-site management articles for sites using the Classic CMS.
Activate a license
Configured Commerce uses remote activation for licensing. This means that a remote call is made each time the Admin Console is accessed, regardless of the hosting solution.
Add the domain to the Admin Console
For the Admin Console to display the contents of the website within the newly created domain, it needs to be added to the Admin Console. Complete the following steps to add the domain to the Admin Console Go to the Admin Console > Websites Click Edit for the desired Website or click Add Website On the Details finger tab, enter the appropriate domain(s) in the Domain Name(s) field.
Cloud customer launch checklist
The following checklist of events, notes, and owning groups is meant to provide a general outline and checklist for initial Site Launches of Optimizely Configured Commerce to Production should be adequately vetted against the specific additional considerations and/or projects needs by the implementation Partner to account for any unique considerations due to a given Site Implementation is meant to be universal but should be broadly applicable to any Cloud Site Launch should continue to be updated and reviewed over the course of Platform updates.
Go-live with Configured Commerce
See the Cloud Customer Launch Checklist for project milestones, request lead times, and required tasks. Understanding how to go-live with your Configured Commerce Sandbox is an important and exciting process.
Go-live performance spot check
During project implementation, the partner tests and monitors site performance in QA and development environments, looking for site-specific data or custom code that could cause performance issues. A few weeks before go-live, as part of the Cloud Customer Launch Checklist , Optimizely performs a spot check of the site performance in sandbox to help ensure a successful launch.
Resources for developers
Guidance on platform architecture and prescribed extension points. This includes general getting started information, as well as standard functionality and behavior.
Third-party library policy
Optimizely Configured Commerce supports a standard set of third-party libraries that fulfill common requirements such as SFTP and XML parsing. Optimizely Configured Commerce supports the Polly and Polly.
Download WIS
If you do not see the WindowsIntegrationService folder in your local copy of Configured Commerce, download and unzip the following folder into your Configured Commerce project folder and follow the installation instructions WindowsIntegrationService https //world. optimizely.
Upgrade AngularJS from 1.3.15 to 1.7.9
As part of Configured Commerce 4. 6, our reference themes and the Admin Console have been upgraded to the latest version of AngularJS.
Troubleshoot Cloudsuite Distribution in v1 sandbox environments
Due to Infor’s changeover of SSL cipher suites for CSD environments, Optimizely has discovered that v1 (Pod) sandbox environments do not have the correct cipher suite to support this connection. This is a temporary issue as the near-term goal is to move all customers to containers.
Customizations with VMI
Partners enabling VMI for the first time on Classic must check for any CSS, HTML, or Typescript customizations to OOTB modals. If so, they can find an existing modal that uses 100% OOTB functionality and interact with it to see if the modal is useable without any additional intervention.