...
Load Balancer - balances the load across the cluster nodes.
Elasticsearch – a search engine deployed on the server node as a micro service or as a separate process in the virtual private network.
Shared database – a shared database used by the nodes. Zephyr supports MySQL, MS SQL Server, and Oracle Database.
Shared directory – a shared folder where attachments are stored. In a cluster environment, this folder must be shared with write permissions. Network-attached storage (NAS) and similar devices are supported.
...
Expand | ||
---|---|---|
| ||
Share a folder by using NAS (network-attached storage) or a similar device: 1. Create a shared folder with read/write access in NAS (network-attached storage). 2. On all the nodes, open the Program Files\Zephyr\tomcat\webapps\flex\WEB-INF\classes\jdbc.properties file, find the line
and replace the C:/Program Files/Zephyr part with the IP address of the NAS shared folder. For example:
|
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Install the NFS (Network File System) server and client on CentOS 7. To do that: On the server side: 1. Install the required NFS packages by running the following command: 2. Create the Zephyrdata directory and allow access to it:
3. Start the following services and add them to the Boot Menu:
4. Open exports for editing –
– and type the following:
5. Start the NFS service by running the following command:
6. Add the NFS service override in the CentOS 7.0 firewall-cmd public zone service:
The NFS server is ready to work. On the client side: 1. Install the required NFS packages by running the following command:
2. Start the following services and add them to the Boot Menu:
3. Mount the NFS share on the client machine by running the command below:
4. Change the ZEPHYR_DATA path to the mounted path for all the nodes in the opt\Zephyr\tomcat\webapps\flex\WEB-INF\classes\jdbc.propeties file. For example:
5. You are connected to the NFS share. Now you can crosscheck it by running the following command:
|
...
Install Zephyr Enterprise on nodes. The installation steps on the first node differ from the steps you perform on the other nodes.
1. To install Zephyr Enterprise on the first node:
...
Expand | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
In the file, find the following line:
and replace it with the following:
|
...
Expand | ||
---|---|---|
| ||
1. In this file, find the line –
– and add the IP addresses of all the nodes instead of 127.0.0.1. For example:
2. Find the string line –
– and replace it with an IP address that has an asterisk instead of the last component. For example:
|
...
Remove the following lines:
Code Block |
---|
#unique identifier for the cluster node |
...
cluster.aws.enable=false |
...
HAZELCAST_PASSWORD=huser |
...
HAZELCAST_USERNAME=hpass |
Update the following information:
Code Block |
---|
cluster.key=node1 (this should be a unique name of the node) |
...
cluster.node.1.key=node1 |
...
cluster.node.1.url=172.17.18.141 (the IP address of node 1) |
...
cluster.node.count=4 |
...
cluster.node.2.key=node2 |
...
cluster.node.2.url= 172.17.18.157(the IP address of node 2) |
...
cluster.node.3.key=node3 |
...
cluster.node.3.url=172.17.18.223 (the IP address of node 3) |
...
cluster.node.4.key=node4 |
...
cluster.node.4.url=172.17.18.201 (the IP address of node 4) |
Expand | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|
Note |
---|
The |
...
Now you can use your nodes.