Creating A New Deployment Project

This procedure creates a new deployment project, which can be published/ deployed into Azure.

  1. Open the Enterprise Server for .NET Administration tool.

  2. Right-click the Azure Deployment node (1) and select Add.

    A wizard will guide you through the basic deployment configuration.

  3. Enter the service name and Azure SDK version you want to give this deployment (see 1 and 2 above).

    When the project is deployed, the service will be created if it is not present.

    If you want to copy a configuration from a previously-defined deployment, click Copy Configuration (see 3 above).

    1. The configuration files and generated files that are produced by this process are stored in the %public%\Documents\Micro Focus\Enterprise Developer\Azure folder. In the example above, the configuration file mycics.config is created in the %public%\Documents\Micro Focus\Enterprise Developer\Azure\ folder. The generated contents of a deployment are stored in a folder below that, called public%\Documents\Micro Focus\Enterprise Developer\Azure\mycics.
  4. Click Next to continue.

    The next panel configures the management certificate.

  5. Click Generate (1 above).

    A browser window opens, which takes you to the Azure portal to generate and download the certificate.

    Once you have downloaded a certificate, import it by clicking Import (2 above) and navigating to the stored certificate and selecting it. When the certificate has been imported, you are presented with the following panel:

  6. Click Next to continue.

  7. Select the location in which you want the service deployment to reside. If you click the ellipsis (1 above) you are presented with the available regions for your deployment.

    Micro Focus recommends deploying to the same location as your database. If you choose a different location, that could result in significant additional latency in Enterprise Server for .NET processing.

  8. Click Next to continue.

  9. Enter the database instance ID of the SQL Azure server you want to use for the deployment (1 above). This is the ID provided by the SQL Azure setup process, e.g. wzi3vhmgv1. You can also click the ellipsis (2 above) to get a list of database servers associated with the subscription. If you have not created a database server to use, you must do so first.
  10. Enter the user ID associated with the SQL server (3 above). This will have been set during the database server creation.
  11. Enter the password associated with the SQL server (4 above).

    If you are using an SQL Azure server, and it exists, you can test the connection by clicking Test Connection (5 above).

  12. Click Next to continue.

    The system uses Azure storage accounts to store the deployment package and diagnostic data, as well as information stored on Azure storage drives. The storage accounts do not have to belong to the subscription used for the deployment.

  13. Enter the Storage Account Name to be used for deployment and Azure drive storage (1 above).You can click the ellipsis (2 above) to get a list of storage accounts associated with the subscription.
  14. Enter the Storage Account Key associated with storage account. If you selected the storage account using the ellipsis button, this is populated automatically.

  15. Click Next to continue.

    This storage account is used to store the diagnostic information emitted by the system, CTF traces and Windows Event Log.

    The Storage account defaults to the same details as on the previous panel, but can be changed if you need the information to be kept separate for some reason.

  16. Amend as required and click Next to continue.

  17. If you want to access the virtual machines hosting the worker roles in Azure using Remote Desktop, for example to check deployment, enable the checkbox.
  18. Enter the account user name (1 above).
  19. Select the certificate to use to secure the connection to the remote desktop (2 above).
  20. Enter a password to use to secure the connection (3 above), and confirm it (4 above).
  21. Choose an account expiration date (5 above). By default this is set far in the future.
  22. Click Next to continue.

    On this panel you can insert a region that will be associated with the deployment.

    By default, the wizard will insert two demo regions for you, designed to work with the demonstration regions definitions shipped with the product. You can delete these using the administration tool if you want, once the wizard is complete.

  23. Click Add Region (1 above) to add a new region.

    A new row is inserted.

  24. Enter the Region Name and select the Region Type from the drop-down list (2 above).

    The wizard is now at a point where it can complete.

  25. Click Finish to commit the new deployment configuration.