In this article
Note: Commerce Admin Portal is not needed when running Commerce Service in single-tenant mode. Only install Commerce in Multi-Tenant mode if you are going to connect one instance or Commerce to two or more instances of LS Central.
Prior to using the Admin Portal, you must add two modules to the IIS setup (this may not be needed on latest Windows versions):
- Open MS Web Platform Installer and install the CORS and URL Rewrite modules.
The Commerce admin portal is accessible by browsing to http://<omnihost>/CommercePortal/ where you need to log in. The default login for the admin user is:
- User name: CommerceUser
- Password: LSCommerceUser
Note: Change the password for production.
The admin user can
- Create a portal user
- Manage portal users
- Enable / disable users
- Give users access to different tenant configurations
- Create a new tenant
- Manage tenants
- Edit all tenants
- Enable / disable tenants
- See LSKeys for all tenants
Regular portal users can
- Edit tenant configurations
- Only the tenants assigned to logged in user by the admin user
- See LSKeys for tenants available to this user
When you are logged in, you will see all the different configurations that are available.
The Admin user has access to a tenant named DEFAULT, that config is used as default for all the other tenant configurations.
Single-Tenant
If you are running a single-tenant setup, the configurations that are not in the AppSettings.config file will default to the values set in the DEFAULT tenant settings. You can edit all settings that do not correspond to the values in the AppSettings.config, because the values in the AppSettings file overwrite the other settings.
Note: Do not create a tenant if you are running a single-tenant setup.
Multi-Tenant
The same goes for other tenants in a multi-tenant setup. If the setting is not specifically set for a tenant, the DEFAULT tenant setting value will be used.
When you click the Add tenant button, a copy of the DEFAULT config is made. You can then start adding the tenant specific values.
Note: When connecting to LS Central in SaaS, Ping test may give q user error for Central WS. Just ping again, and it should give the correct result. The reason for this is that first the Ping is registering the Token needed to access Central in SaaS.
Each tenant gets an LS Key that needs to be sent with the API header as LSRETAIL-KEY when calling Commerce. In Magento, this key is added to the configuration page, see General Configuration - Retail.