Configuring Multiple Servers to the Same Repository
When a singular client has multiple concurrent jobs, running all of them on a single server could prove inefficient and time-consuming. Distributing these jobs across multiple servers allows for parallel processing, thereby reducing processing times and improving overall efficiency.
In this document, we will explore how to connect multiple servers and configure them to point to the same database repository, while also addressing the need for efficient handling of multiple jobs from a single client.
Server configuration
To configure a server in the Enterprise Client, navigate to the Server Explorer panel. The Server Explorer contains information about your Cluster(s) and Server(s).
In the Server Explorer panel, navigate to the Connect to Server button. This allows you to connect to and configure a server in Enterprise Client.
If you are already connected to a server, a dialog box will prompt you to make sure if you want to disconnect from the current server in order to connect to another server. Click Yes.
In the Connect to Server dialog box, add your server connection information, such as the URI and Port Number. The Server URI will typically be the IP address or hostname of the machine where the Astera Integration server is installed. The default port is usually 9262 for a secure connection. Click on the Connect button to establish a connection once you are done configuring your server details.
Once the connection is successful, you will be prompted to login to the server. Click Yes.
In the Log in to Server dialog box, enter your relevant account details to login to the server. Once done, click the Log in button.
Note: Incase the login menu does not open, you can also open it from server > security > login
If your login attempt was successful, then you will be prompted to restart the client in order for the changes to be updated. Click Yes.
If the configuration and connection is successful, you should see the server listed in the Server Explorer tree. Once a server has been connected, we can now configure its cluster database repository.
Cluster Database Repository Configuration
To configure the Cluster Database Repository settings, right-click on the added Server in the Server Explorer Panel. Here, click on the Server Properties option.
This opens the Server Connection Properties. Here, we can configure the Cluster Database Repository to point towards a specific repository.
To configure the Cluster Database Repository setting, click on the Cluster DB Info button.
The Database Connection dialog box allows us to configure the Cluster Database Repository settings. Choose the type of database you are using (SQL Server or PostgreSQL) from the Data Provider drop-down list. Enter the credentials required to connect to the database. Select the database you will use for the repository from the drop-down list next to the Database option. The Server Name option allows you to enter the specific server instance where your repository is available. You can add the Server Name or IP Address of the specific server you want to use here. However, it is to be noted that the server must be on the same network as the client machine for this to work.
To save the newly configured server properties, right-click on the Server Connection Properties to save your configuration.
Repeating all of the above steps, we can connect to multiple servers and also configure them to point to the same repository, as per the required architecture.
Note: All client and server machines must be on the same network to avoid connectivity and configurations issues, as well as issues during operation.
This concludes the article on Configuring multiple servers to the same repository for load balancing in Enterprise Client.
Last updated
