instalation odoo

7/23/2019 Instalation odoo

http://slidepdf.com/reader/full/instalation-odoo 1/11

Corner Notes

[email protected]

Dalam catatan ini dipresentasikan tahapan penggunaan Slony untuk replikasi dansinkronisasi database postgres. Contoh kasus menggunakan database Odoo dalamenvironment Windows digambarkan sebagai berikut:

Slony Cluster

192.168.50.2Slave Host

192.168.50.1Master Host

Data Replication

pg_hba.conf pg_service.conf 192.168.50.1.slonpreamble.skinitcluster.skaddnode.skaddpaths.skbuildset.sk

addtables.sksubscribeset.sk

pg_hba.conf pg_service.conf 192.168.50.2.slon

Dalam gambar tersebut komputer 192.168.50.1 berperan sebagai master host dan192.168.50.2 sebagai slave host. Data akan direplikasi dan disinkronisasi dari master hostke slave host. File konfigurasi dan script yang dibutuhkan dalam kegiatan ini dicantumkandalam list diatas yaitu pg_hba.conf, pg_service.conf, *.slon dan *.sk akan dijelaskan dalamtahapan berikut:

1. Langkah pertama adalah menginstall slony menggunakan Application Stack Builder.

mailto:[email protected]





2. Selanjutnya persiapkan database master dan slave.a. Buat backup database master yang akan direplikasi sbb:

cd C:\Program Files\PostgreSQL\9.4\bin

pg_dump -U postgres -n public -s -f C:\master.backup odoo_node1

b. Copy backup file ke slave host, kemudian restore ke database slave sbb:

cd C:\Program Files\PostgreSQL\9.4\bin

psql -U postgres -f C:\master.backup odoo_node2

3. Buat Login Role baru di master host dan slave host dengan Role PrivilegesSuperuser dan Can Modify Catalog Directly.



4.

Edit file C:\Program Files\PostgreSQL\9.4\data\ pg_hba.conf baik dimaster host maupun slave host, kemudian reload menggunakan pgAdmin (Tools >Reload Configuration).

File pg_hba.conf di master host sbb:# TYPE DATABASE USER ADDRESS METHOD# IPv4 local connections:host odoo_node1 slony 192.168.50.2/32 md5



host all all 127.0.0.1/32 md5# IPv6 local connections:host all all ::1/128 md5

File pg_hba.conf di slave host sbb:

# TYPE DATABASE USER ADDRESS METHOD# IPv4 local connections:host odoo_node2 slony 192.168.50.1/32 md5host all all 127.0.0.1/32 md5# IPv6 local connections:host all all ::1/128 md5

5. Buat folder di master host dan slave host berisi file pg_service.conf dan setenvironment variable PGSYSCONFDIR ke folder tersebut. Untuk contoh ini file

pg_service.conf disimpan dalam folder C:\slonycluster. Folder tersebut untukselanjutnya dijadikan sebagai working directory.

File pg_service.conf di master host sbb:

[192.168.50.1-slonik]dbname=odoo_node1user=slonypassword=slony

[192.168.50.2-slonik]

dbname=odoo_node2host=192.168.50.2user=slonypassword=slony

File pg_service.conf di slave host sbb:

[192.168.50.1-slonik]dbname=odoo_node1host=192.168.50.1user=slonypassword=slony

[192.168.50.2-slonik]dbname=odoo_node2user=slonypassword=slony



6. Langkah selanjutnya membuat script untuk menginisiasi cluster, menambahkanslave node, dan menambahkan paths untuk menghubungkan node dalam cluster.Script berikut dibuat dan dijalankan di master host dengan working directoryC:\slonycluster.

File preamble.sk# file preamble.skcluster name = slony_cluster;node 1 admin conninfo = 'service=192.168.50.1-slonik';node 2 admin conninfo = 'service=192.168.50.2-slonik';

File initcluster.sk#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file initcluster.skinclude <preamble.sk>;init cluster (id=1, comment='hostname=192.168.50.1');



File addnode.sk# file addnode.skinclude <preamble.sk>;store node (id=2, comment='hostname=192.168.50.2', event node=1);

File addpaths.sk#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file addpaths.skinclude <preamble.sk>;store path (server=1, client=2, conninfo='service=192.168.50.1-slonik');store path (server=2, client=1, conninfo='service=192.168.50.2-slonik');

File runslonik.bat

# @ECHO OFFREM file runslonik.batREMREM Batch file to run slonikC:\"Program Files"\PostgreSQL\9.4\bin\slonik < %1

Eksekusi perintah berikut di master host:C:\slonycluster>runslonik initcluster.skC:\slonycluster>runslonik addnode.skC:\slonycluster>runslonik addpaths.sk

7. Buat file 192.168.50.1.slon di master host dan file 192.168.50.2.slon di slave host.Kemudian simpan file tersebut dalam folder C:\slonycluster.

File 192.168.50.1.slon di master host sbb:# file 192.168.50.1.sloncluster_name='slony_cluster'conn_info='service=192.168.50.1-slonik'

File 192.168.50.2.slon di slave host sbb:# file 192.168.50.2.sloncluster_name='slony_cluster'conn_info='service=192.168.50.2-slonik'



8. Register Slony service dan engine di master host dan slave host Selanjutnyajalankan Slony service dengan membuka Control Panel > Administrative Tools >Services, pilih Slony service dan klik link Start Service.

Eksekusi perintah berikut di master host:

C:\slonycluster>set PATH=C:\Program Files\PostgreSQL\9.4\bin;%PATH%C:\slonycluster>slon -regservice SlonyC:\slonycluster>slon -addengine Slony C:\slonycluster\192.168.50.1.slon

Eksekusi perintah berikut di slave host:C:\slonycluster>set PATH=C:\Program Files\PostgreSQL\9.4\bin;%PATH%C:\slonycluster>slon -regservice SlonyC:\slonycluster>slon -addengine Slony C:\slonycluster\192.168.50.2.slon

9. Tahap selanjutnya adalah membuat script untuk menambahkan replication set kereplication cluster, menambahkan table ke replication set, dan script untuksubscribe slave node ke replication set. Replication set dibuat sesuai dengankebutuhan. Dalam contoh ini dibuat 3 buah replication set untuk table yang berelasidengan res_users, product_product, dan product_taxes_rel.



File buildset1.sk#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file buildset1.skinclude <preamble.sk>;create set (id=1, origin=1, comment='source tables for repset #1');

File addtables1.sk#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file addtables1.skinclude <preamble.sk>;

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 1, FULLY QUALIFIED NAME = 'public.res_users', ADDSEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 2, FULLY QUALIFIED NAME = 'public.mail_alias', ADDSEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 3, FULLY QUALIFIED NAME = 'public.res_company',ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 4, FULLY QUALIFIED NAME ='public.crm_case_section', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 5, FULLY QUALIFIED NAME = 'public.res_partner',ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 6, FULLY QUALIFIED NAME = 'public.pos_config',ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 7, FULLY QUALIFIED NAME = 'public.ir_model', ADDSEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 8, FULLY QUALIFIED NAME = 'public.res_currency',ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 9, FULLY QUALIFIED NAME ='public.account_account', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 10, FULLY QUALIFIED NAME = 'public.res_font', ADDSEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 11, FULLY QUALIFIED NAME ='public.stock_location', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 12, FULLY QUALIFIED NAME ='public.report_paperformat', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 13, FULLY QUALIFIED NAME = 'public.product_uom',ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 14, FULLY QUALIFIED NAME ='public.resource_calendar', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 15, FULLY QUALIFIED NAME = 'public.res_country',ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 16, FULLY QUALIFIED NAME ='public.res_country_state', ADD SEQUENCES=true);



SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 17, FULLY QUALIFIED NAME ='public.res_partner_title', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 18, FULLY QUALIFIED NAME = 'public.ir_sequence',ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 19, FULLY QUALIFIED NAME ='public.product_pricelist', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 20, FULLY QUALIFIED NAME ='public.stock_picking_type', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 21, FULLY QUALIFIED NAME ='public.account_journal', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 22, FULLY QUALIFIED NAME ='public.product_removal', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 23, FULLY QUALIFIED NAME ='public.product_putaway', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 24, FULLY QUALIFIED NAME ='public.product_uom_categ', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 25, FULLY QUALIFIED NAME ='public.stock_warehouse', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 26, FULLY QUALIFIED NAME ='public.procurement_rule', ADD SEQUENCES=true);SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 27, FULLY QUALIFIED NAME ='public.stock_location_route', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 28, FULLY QUALIFIED NAME ='public.account_analytic_journal', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=1, ORIGIN = 1, ID = 29, FULLY QUALIFIED NAME ='public.account_account_type', ADD SEQUENCES=true);

File subscribeset1.sk#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik#file subscribeset1.sk for adding subscribers to replication set 1include <preamble.sk>;subscribe set (id=1, provider=1, receiver=2, forward=yes);

sync(id=1);wait for event (origin=1, confirmed=2, wait on=1, timeout=1800);

Eksekusi perintah berikut di master host untuk replication set #1C:\slonycluster>runslonik buildset1.skC:\slonycluster>runslonik addtables1.skC:\slonycluster>runslonik subscribeset1.sk



File buildset2.sk

#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file buildset2.skinclude <preamble.sk>;create set (id=2, origin=1, comment='source tables for repset #2');


SET ADD TABLE (SET ID=2, ORIGIN = 1, ID = 30, FULLY QUALIFIED NAME ='public.product_product', ADD SEQUENCES=true);SET ADD TABLE (SET ID=2, ORIGIN = 1, ID = 31, FULLY QUALIFIED NAME ='public.product_template', ADD SEQUENCES=true);SET ADD TABLE (SET ID=2, ORIGIN = 1, ID = 32, FULLY QUALIFIED NAME ='public.product_category', ADD SEQUENCES=true);SET ADD TABLE (SET ID=2, ORIGIN = 1, ID = 33, FULLY QUALIFIED NAME = 'public.pos_category',ADD SEQUENCES=true);SET ADD TABLE (SET ID=2, ORIGIN = 1, ID = 34, FULLY QUALIFIED NAME ='public.project_project', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=2, ORIGIN = 1, ID = 35, FULLY QUALIFIED NAME =

'public.account_analytic_account', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=2, ORIGIN = 1, ID = 36, FULLY QUALIFIED NAME ='public.hr_timesheet_invoice_factor', ADD SEQUENCES=true);

File subscribeset2.sk#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file subscribeset2.sk for adding subscribers to replication set 2include <preamble.sk>;subscribe set (id=2, provider=1, receiver=2, forward=yes);sync(id=1);wait for event (origin=1, confirmed=2, wait on=1, timeout=1800);




File buildset3.sk

#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file buildset3.skinclude <preamble.sk>;create set (id=3, origin=1, comment='source tables for repset #3');


SET ADD TABLE (SET ID=3, ORIGIN = 1, ID = 37, FULLY QUALIFIED NAME = 'public.account_tax',ADD SEQUENCES=true);SET ADD TABLE (SET ID=3, ORIGIN = 1, ID = 38, FULLY QUALIFIED NAME ='public.account_tax_code', ADD SEQUENCES=true);

SET ADD TABLE (SET ID=3, ORIGIN = 1, ID = 39, FULLY QUALIFIED NAME ='public.product_taxes_rel', KEY='product_taxes_rel_prod_id_tax_id_key', ADDSEQUENCES=false);

File subscribeset3.sk#!C:\"Program Files"\PostgreSQL\9.4\bin\slonik# file subscribeset3.sk for adding subscribers to replication set 3include <preamble.sk>;subscribe set (id=3, provider=1, receiver=2, forward=yes);sync(id=1);wait for event (origin=1, confirmed=2, wait on=1, timeout=1800);


instalation odoo

Documents