Simplifying multi-server web site deployment (v.24)

In version 24 we are introducing a feature that addresses a common issue for websites deployed across multiple APP servers.

The problem

Currently, when a customer uses our service for multiple APP servers, each website for their database is started on each of these servers during deployment. This isn't ideal because:

  1. It can break licensing agreements.
  2. It can cause unnecessary load on all servers.

The solution

Our new feature introduces a straightforward way to control where your websites start. Here's how it works:

  • Specify the Server: In the definition of each website, there is a new field where you can specify which server should start it.
  • Default to Primary: If you don't specify a server, the website will start on the primary server.

What does this mean for you?

The feature does not require any additional actions from our customers before the upgrade to Version 24. We will handle all the necessary settings.

The only change is that, when a customer that uses multiple instances wants to add a new website, they need to specify the UIN of the APP server where they want it to start. Not sure which server to choose? No worries - reach out to your service partner or our team for assistance.

We believe this new feature will make your web deployments smoother and more efficient. As always, we're here to support you every step of the way.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk