XEServer Profile Requirements

Before you create a build, read the following profile requirements for creating a profile in Edifecs Application Manager for a Beta release of the Compute service.

• Advanced XEServer modules, such as, XEConnect, XES Module for Claim Forms, XES Module for FHIR, Transaction Management (TM), and so on, are not supported. Only the basic XEServer and XEngine components are supported.
• Profile images that require custom artifacts, which XEServer does not include by default, such as, JMS and JDBC drivers, Java and Kafka libraries, MFT activation keys, XERegistry, XESelector, and so on, are not supported.
• Edifecs recommends that you do not use the FS, Data Storage, JMS, MFT components to store data in VMs, because a Docker container uses a file system that is not mounted onto any persistent data storage and this can lead to data loss in case of system crashes and failures.
• The Compute service does not support partial images (patches) for XEServer and XEngine.
• You should define all the system macro variables inside a profile image or specify them in an environment.