Managed Runtime Administration in Runtime Admin and Business Manager

Manage your organizations, projects, environments, and bundles associated with your Storefront Next storefront or a linked Composable storefront with various tools, including the Runtime Admin console, Business Manager, and Account Manager.

To automate these tasks, use the Managed Runtime API.

Use these interfaces to manage your storefront development resources.

• Business Manager with the Developer Workspace Beta: Environments, environment settings, deployments, environment variables, and redirects are accessible in Business Manager from the storefront page.
• Business Manager without the Developer Workspace Beta: Environments are accessible in Business Manager from the storefront page. Deployments, environment settings, environment variables, redirects are in Runtime Admin.
• Runtime Admin: The storefront uses Runtime Admin. Open Runtime Admin and select the project for the storefront.

Grant access in the interface the storefront uses.

• Runtime Admin: Ask a B2C Commerce administrator to add the Managed Runtime User or Managed Runtime Admin role in Account Manager. To assign organization and project roles, see Organization and Users in Managed Runtime Administration.
• Business Manager: Create roles and assign storefront permissions. See Manage Roles and Permissions for Your Storefront in Business Manager (Beta). A Business Manager admin needs the Business Administrator role in Account Manager, or a role for the Business Manager module and organization context with read-write access to storefronts. During the beta, a user who works in Business Manager also needs a matching Managed Runtime project role. See Create a Role in B2C Commerce in Salesforce Help.

An environment is the cloud infrastructure and configuration for one deployed storefront. When you create a storefront in Business Manager, the storefront includes the embedded content delivery network (eCDN) and a default domain. The default domain maps to the Managed Runtime site.

For environment concepts, including production environments, see the Managed Runtime Overview.

See Create an Environment in Business Manager.

All supported regions have a paired backup region for failovers. The region list is the same in Runtime Admin and Business Manager. Make sure that your application runs correctly in the selected primary and backup regions:

• Runtime Admin: See Deploy a Bundle.
• Business Manager: See Deploy Your Storefront from Business Manager (Beta).

• Business Manager (Developer Workspace Beta): Edit settings on the storefront page in Business Manager. See Edit Environment Settings.
• Business Manager: Go to Administration > Sites > Storefronts, click the storefront, and then next to the environment, click the caret and click Edit. Log in to Runtime Admin opens in a new tab and access Environment Settings.
• Runtime Admin: Log in to Runtime Admin. From the project, click the environment, and then click Environment Settings. Click Edit next to General settings or Advanced settings.

From environment settings, you can complete these tasks:

• Rename an environment or environment ID.
• Change the deployment region. See Supported Regions.
• Enable or disable source maps. See Source Maps.
• Mark an environment as production. See Production Environments.
• Enable or disable Log Center logs and metrics. In Runtime Admin, the controls are under Observability. See Log Center Logs and Metrics.
• Add, edit, or remove site IDs associated with an environment.

Managed Runtime supports the ARM processor architecture for Server-Side Rendering (SSR) for Storefront Next. The ARM architecture represents the underlying compute infrastructure used to render your storefront.

ARM processors offer several advantages.

• Enhanced Performance: ARM architecture provides efficient processing capabilities optimized for modern web workloads.
• Modern Infrastructure: Built on the latest cloud computing technologies.

See Environment Variables. That topic has the steps for Runtime Admin and for Business Manager.

Use a redirect to forward a request from one URL to another. Redirects can help avoid disruptions to the user experience caused by changes to your storefront. For example, consider a seasonal campaign page for spring. When the spring campaign ends and is replaced with a summer campaign, you can redirect from the spring URL to the summer URL.

Redirects is a powerful feature that can have significant security consequences on your storefront, including redirecting to malicious URLs or assets. Be careful when assigning roles to users that give them Redirect access.

• Runtime Admin: See Redirects in Managed Runtime Administration.
• Business Manager: See URL Redirects.

Log Center provides a single location to access logs from Managed Runtime (MRT) and your B2C Commerce instance. Log Center logs and Log Center metrics are independently configurable for any environment, as long as the environment is associated with a B2C Commerce instance. Unlike uptime monitoring, enabling Log Center logs or metrics doesn’t require marking the environment as production. See Debug Your Storefront in Production Using Log Center.

Enable Log Center logs and Log Center metrics independently in Environment Settings, under Observability.

See Also

• View Logs in Log Center
• Debug Your Storefront Next Site Using Log Center