This topic contains some best practice principles that Micro Focus recommends.
- Deploy artifacts (region definition, resource definition, executables etc) to a database (a data-store is ideal), rather than
a disk. This enables central control of the artifacts, and artifacts can be used by multiple regions and machines.
- Deployment of artifacts (new programs for example) can be automated using the command line tools supplied. Look at the seedbdeploy.cmd
batch program as an example of how to do this.
Enterprise Server for .NET deployment can host one or more regions. Each region can be configured to look for artifacts in different locations. It is
possible therefore to have the same infrastructure (same listeners, dispatchers and SEPs ) hosting a production and a test
- If you are planning on using Azure to host your deployments, get it all working in an on-premise deployment first. Once everything
is working on-premise, deploying to Azure is simple. All the executables are the same, so no need to recompile. You also then
have a debug environment that can be used to help locate application faults in Azure.
- Use the
Enterprise Server for .NET administration tool to administer configuration. Configuration entered this way is validated to a high degree and the likelihood
of errors is minimized.