ÃÛ¶¹ÊÓƵ

Configure the application

Now that you’ve finished installing ÃÛ¶¹ÊÓƵ Commerce, you need to configure it. This topic provides some recommended configuration settings.

Set up cron

The UNIX task scheduler, cron, is critical to the application’s day-to-day operations. It schedules things like reindexing, newsletters, e-mails, and sitemaps. A crontab is a cron configuration.

You must install ÃÛ¶¹ÊÓƵ Commerce services in the crontab, or some core functionality (and some third-party extensions) do not function properly.

For more information about cron, including how to remove a crontab and run cron from the command line, see Configure and run cron.

Security settings and recommendations

After installation, we recommend the following:

If you installed by , make sure that when you deploy the application, you only include files and folders that are required for the production environment. Files and folders that are not required can potentially expose security risks.

Enable Apache server rewrites

If you use the Apache web server, you must enable server rewrites for pages to display properly. Otherwise, you see pages without styles and other issues.

Section on Apache server rewrites

Caching in a multi-webnode environment

If you have multiple web nodes, you cannot use the application’s default file caching because there is no synchronization between web nodes. In other words, the activity on one web node is written to that web node’s file system only. Subsequent activity, if performed on another web node, can result in unnecessary files being written or can result in errors.

Instead, use Redis for both the default cache and the page cache.

Server settings

This section briefly discusses settings that we recommend you consider for the server on which the application runs. Some of these settings are not directly related to the application; these are provided as suggestions only.

Log rotation

The UNIX logrotate utility enables you to administer systems that generate large numbers of log files. It allows automatic rotation, compression, removal, and mailing of log files. Each log file can be handled daily, weekly, monthly, or when the log file exceeds a specified size.

For more information, see one of the following:

Set up iptables rules to enable various services to communicate

Whether you have one server or many, you must open ports in the firewall to enable services to communicate. For example, if you use the Solr search engine with ÃÛ¶¹ÊÓƵ Commerce, you must enable it to communicate with the web server. If you have multiple web nodes, you must enable them to communicate with each other.

More information:

Security Enhanced Linux (SELinux) rules

We don’t have a recommendation for whether you use SELinux; however, if you do use it, you must configure services to communicate with each other similar to configuring iptables.

More information:

Set up an e-mail server

ÃÛ¶¹ÊÓƵ Commerce requires an e-mail server. We don’t recommend a particular server, but you can try any of the following:

Refine the search engine for enhanced performance:

Elasticsearch or OpenSearch is required for all installations as of 2.4.0.

Set up a message queue

Since version 2.3.0, ÃÛ¶¹ÊÓƵ Commerce has included message queue functionality. In earlier versions, it is available only for ÃÛ¶¹ÊÓƵ Commerce.

Settings for ÃÛ¶¹ÊÓƵ Commerce only

You can configure the following only if you use ÃÛ¶¹ÊÓƵ Commerce: