Date: Thu, 28 Mar 2024 08:37:52 +0000 (UTC) Message-ID: <525034178.3900.1711615072116@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3899_128916401.1711615072115" ------=_Part_3899_128916401.1711615072115 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
BellaDati Import Node is a dedicated module, which provides the Import a= nd Transformation services. Import Nodes may run separately and independent= on the main server to achieve faster import performance.
Using Import nodes is recommended in following scenarios:
BellaDati Import Node binary distributions are available on http= s://my.belladati.com portal under Downloads -> BellaDati Import= Node.
Please make sure that the server time of BellaDati server and Import Nod= e server is the same (e.g. UTC).
Add the following parameter to the application.properties file of your b= elladati.war archive and redeploy it:
applica= tion.import.nodes=3Dnode1:2552,node2:2552,...,nodeX:2552
BellaDati Standalone users (installed by exe or dmg installers) can find= the application.properties file in BellaDati installation directo= ry (by default it's C:\Program Files\BellaDati, eventually /Ap= plications/BellaDati).
Port 2552 must be opened and accessible by the BellaDati main server.
node1, node2 etc. must be a valid hostname resolvable = by the machine, where BellaDati is running or IP address
Create the configuration file application.properties with the f= ollowing content:
applica= tion.url=3Dhttp://belladati_host application.production-mode=3Dtrue application.secure-mode=3Dtrue # JDBC resource jdbc.driverClassName=3Dorg.postgresql.Driver jdbc.url=3Djdbc:postgresql://db_host:5432/belladati_db jdbc.username=3Dbelladati_dbuser jdbc.password=3Dbelladati
Execute the following command:
java -X= mx2048m -Dconf=3Dapplication.properties -Dimport.node.host=3DIP_OF_THE_HOST= -Dimport.workers.size=3D10 -Dimport.node.name=3Dimport-node-1 -Done-jar.ma= in.class=3Dcom.belladati.remote.ImportNodeMain -jar belladati-import-node.j= ar &
The IP_OF_THE_HOST parameter has to be replaced by the real IP address= of the server, where BellaDati Import Node is running.
To specify the port of the import node, there's parameter import= .node.port which may be specified either in application.properties= or as a java -D parameter ( e.g. -Dimport.node.port=3D2553 )
You can easily check, whether the import node is running properly by ope= ning the Settings -> Import Node administration page directly in BellaDa= ti UI.
If there are multiple import nodes, BellaDati will use the node which ha= s more free workers.
Since BellaDati 2.9.7, BellaDati will execute the import locally in case= the import nodes are not available (e.g. because of network error).