When the HTML to PDF Server runs in a Azure Service Fabric it can be accessed through an IP address which is automatically assigned at deployment time and a TCP port which is 40001 by default.
The Azure Service Fabric Application can be found in 'Server\Azure\ServiceFabric\TCP_ServiceFabric' folder of the location where you extracted the Zip archive of the software. The folder contains the Visual Studio source project in 'Src' subfolder.
Add one or more sections with content The Visual Studio Solution for Azure Service Fabric Application there is in 'Server\Azure\ServiceFabric\TCP_ServiceFabric\Src' folder.
Before publishing the service you can set in the 'Server\Azure\ServiceFabric\TCP_ServiceFabric\Src\EvoAzureServiceFabric\ApplicationPackageRoot\ApplicationManifest.xml' configuration file various options like a service password or the maximum number of conversions running at the same time.
The first step is to create a Service Fabric Cluster.
To create a Service Fabric Cluster from Visual Studio, open the 'EvoAzureServiceFabric.sln' solution in Visual Studio, right click on 'EvoAzureServiceFabric' project and choose 'Publish' option from the contextual menu.
In the publish panel choose your Azure account and under 'Connection Endpoint' choose 'Create new cluster...'.
In the new popup panel in the 'Cluster' tab choose a name for the cluster, your Azure account subscription, a location for the service. In 'Certificate' tab enter a password for the certificate which is used when accessing the service explorer web page. In the 'VM Detail' tab enter an username and a password for the virtual machine and a 'Virtual machine size' for example a machine with 2 Cores and 8 GB RAM. In the 'Advanced' tab, in the ports list add the EVO HTML to PDF Server port number 40001.
Click the 'Create' button to create the Service Fabric Cluster.
The next step is to publish the application in the Service Fabric Cluster.
To publish the application in the Service Fabric Cluster from Visual Studio, open the 'EvoAzureServiceFabric.sln' solution in Visual Studio, right click on 'EvoAzureServiceFabric' project and choose 'Publish' option from the contextual menu.
In the publish panel choose your Azure account and under 'Connection Endpoint' choose the cluster you created at the previous step. You can leave the other options with their default values.
Click the 'Publish' button to publish the application in Service Fabric Cluster.
You'll be able to see the evolution of the deployment process in Visual Studio. When the deployment is complete you can login into your account of Microsoft Azure Portal to obtain the public IP address of the HTML to PDF service.
In Azure Portal you can find the Azure Service Fabric Application you created if you select 'All resources' item from the menu of the Azure Management Portal. Click the link to Service Fabric cluster from the list of resources to open the Service Fabric cluster 'Overview' panel. In that panel you can see the service DNS name under 'Client connection endpoint' section. It should look by default like 'clustername.location.cloudapp.azure.com'. You can use this DNS name IP address to connect the client library to service in our demo applications and in your applications.
You can also obtain the public IP address to be used in Load Balancer resource created for the cluster. Click that resource in the resources list to open its 'Overview' panel. In that panel you can find the IP address under the 'Public IP address' section. You can use this IP address to connect the client library to service in our demo applications and in your applications.
Before publishing the service you can set in the 'Server\Azure\ServiceFabric\TCP_ServiceFabric\Src\EvoAzureServiceFabric\ApplicationPackageRoot\ApplicationManifest.xml' configuration file various options like a service password or the maximum number of conversions running at the same time. The configuration options are listed below.
Distributed Option - This option is false by default and it can be enabled to run each conversion in a separate process. It offers more isolation between parallel conversions but it can be slower.
MaxConcurrentClients Option - This option has value 12 by default and it indicates how many conversions are running in parallel. If the maximum number of parallel conversions was reached the subsequent conversion are queued until an execution slot becomes available.
ServicePassword Option - This option is empty by default and it can be set with a password string to be verified by the service before accepting a conversion request.
Impersonation Options - The ImpersonationUsername, ImpersonationPassword, ImpersonationDomain and ImpersonationLogonMode options are empty by default and they can be used to run the service under a specific user account on the hosting Windows machine.
You can remove the Service Fabric Cluster from your Azure account management portal.