[Chapter 2. configuration (Setup )],

[Chapter 2. configuration (Setup )],
2.1. Engine Files

Each node requires some attributes to connect the node to a database and register it with a parent node. These attributes are defined in a file named xxxx. properties, which is placed in the engines folder under the root directory of the installation copy of javasricds. The name of a file name is generally based on the engine. name attribute, but this is not required.

To give a node an identifier, the following attributes are required. Attributes in the conf/initric. properties file can be overwritten by configurations in the configuration file of a specific engine. If the properties in the conf/initric. properties file are changed, they will take effect for all engines in this installation copy. Note: When defining these attributes, you can use the variable $ (hostName) to replace the Host Name of the machine, for example, external. id = $ (hostName ).

Engine. name

This is an arbitrary name used to access a specific engine using an http url. Each node configured in the Engines directory must have a unique engine name. This engine name is also used as the domain name of the registered JMX bean.

Group. id

A node group is the group to which the node belongs. Synchronization is performed between node groups. This means that you only need to specify multiple nodes in the same group once.

External. id

The External id of a node is very meaningful to users. It provides the ability to integrate the node into the deployed system. For example, the external id of a node may be a distribution store number or a region number. External id can be used in conditional expressions and synchronization data subsets. Transparently, each node has a unique number to track synchronization events. If you want to assign the same external id to multiple nodes, it is also possible (because there is a unique number above ).

Sync. url

The node synchronization operation is the URL address used for communication. When starting and heartbeat, the node uses this URL to update data in the database. The URL format is http: // {hostname }:{ port}/{webcontext}/sync/{engine. name }.

{Webcontext} is empty during standalone deployment. It is usually the name of the war file deployed on an application server.

If there is only one engine in a replica ricds server, {engine. name} can be blank.

 

When a new node is started for the first time, the node does not have synchronization information. It contacts the registration server to join the network, and then receives the configuration information of the registration server. All node configurations are stored on the registration server. The URL must be executed using the following attributes:

Registration. url

The URL of the registration server that the node needs to contact. The purpose of contacting the registration server is to receive the configuration information of the server. When registering a service, metrics ricds is part of the overall deployment architecture. The value of Registration. url is usually equal to the value of sync. url on the Registration server.

Important

Note that the value of registration. url of a registration server node is either null or the same as that of its sync. url.

During a deployment, the database connection pool needs to be created using the JDBC driver. Therefore, you need to set the following attributes:

Db. driver

The name of the JDBC Driver Class.

Db. url

The jdbc url used to connect to the specified database.

Db. user

The username of the database. It is used to log on to, create, and update the metrics ricds table.

Db. password

Password of the above Database User Name

 

You can view Section B .1 "Startup Parameters" to obtain more attributes that can be specified in the engine property file.