Production Deployment ChecklistΒΆ Given below is a checklist that will guide you to set up your production environment for WSO2 Integrator: MI. Guideline Details Security hardening Guidelines for hardening the security of a WSO2 deployment in a production environment can be discussed under three high-level categories: Product-level security OS-level security Network-level security Related links Security Guidelines for a Production Deployment Hostname By default, WSO2 products identify the hostname of the current machine through the Java API. However, it is recommended to configure the hostname by setting the hostname parameter in the deployment.toml file. [server]hostname="localhost" Related links Changing the hostname Registry and governance The WSO2 Integrator: MI runtime uses a file-based registry instead of a database. If you share the registry folder or the repository/deployment/server folder (which contains carbonapps) across cluster nodes, mount them over NFS with the hard option. SMB/CIFS shares cache metadata aggressively and can cause Carbon application (CApp) deployment to fail. File-based registry for the WSO2 Integrator: MI runtime. Performance Tuning Most of the performance tuning recommendations are common to all WSO2 products. However, each WSO2 product may have additional guidelines for optimizing the performance of product-specific features. Performance tuning - WSO2 Integrator: MI Firewalls The following ports must be accessed when operating within a firewall: 8290 - Default HTTP port used by the WSO2 Integrator: MI for proxy services and APIs. 8253 - Default HTTPS port used by the WSO2 Integrator: MI for proxy services and APIs. 9164 - Default HTTPS port used by the WSO2 Integrator: MI Management APIs. Proxy servers If the runtime is hosted behind a proxy such as ApacheHTTPD, you can configure the runtime to use the proxy server. See the following topics for instructions: Configuring a proxy server for the WSO2 Integrator: MI runtime. High availability In the cloud native deployment, high availability should be achieved via the container orchestration system ( Ex: Kubernetes ). There are builtin readiness and liveness probes available in WSO2 Integrator: MI. In a VM deployment, we can use a load balancer with multiple nodes as described here to achieve high availability. Data backup and archiving Implement a backup and recovery strategy for your system.