{"id":36968,"date":"2019-10-31T22:15:01","date_gmt":"2019-10-31T19:15:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/sposoby-integratsii-s-1s\/"},"modified":"2019-10-31T22:15:01","modified_gmt":"2019-10-31T19:15:01","slug":"sposoby-integratsii-s-1s","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/sposoby-integratsii-s-1s","title":{"rendered":"Integr\u0101cijas veidi ar 1C","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>K\u0101di ir vissvar\u012bg\u0101kie pras\u012bbas biznesa lietojumprogramm\u0101m? Da\u017eas no galvenaj\u0101m ir \u0161\u0101das uzdevumi:<\/p>\n<ul>\n<li>Lietojumprogrammas darba lo\u0123ikas vieglums, piel\u0101gojoties main\u012bgaj\u0101m biznesa vajadz\u012bb\u0101m.<\/li>\n<li>Integr\u0101cijas vieglums ar cit\u0101m lietojumprogramm\u0101m.<\/li>\n<\/ul>\n<p>\nTas, k\u0101 1C risina pirmo uzdevumu, tika \u012bsi aprakst\u012bts sada\u013c\u0101 \"Piel\u0101go\u0161ana un atbalsts\" <noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1c\/blog\/267321\/\">\u0161\u012b raksta<\/a><\/noindex>; m\u0113s v\u0113l atgriez\u012bsimies pie \u0161\u012bs interesant\u0101s t\u0113mas k\u0101d\u0101 no n\u0101kotnes rakstiem. \u0160odien run\u0101sim par otro uzdevumu, par integr\u0101ciju.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Integr\u0101cijas uzdevumi<\/h3>\n<p>\nIntegr\u0101cijas uzdevumi var b\u016bt da\u017e\u0101di. Da\u017eos gad\u012bjumos pietiek ar vienk\u0101r\u0161u interakt\u012bvu datu apmai\u0146u - piem\u0113ram, lai nos\u016bt\u012btu bankai darbinieku sarakstu, lai noform\u0113tu algu plastmasas kartes. Sare\u017e\u0123\u012bt\u0101kiem uzdevumiem var b\u016bt nepiecie\u0161ama piln\u012bb\u0101 automatiz\u0113ta datu apmai\u0146a, iesp\u0113jams, ar \u0101r\u0113jas sist\u0113mas biznesa lo\u0123ikas piesl\u0113gumu. Ir uzdevumi, kas ir specializ\u0113ta rakstura, piem\u0113ram, integr\u0101cija ar \u0101r\u0113jiem apr\u012bkojumiem (piem\u0113ram, tirdzniec\u012bbas apr\u012bkots, mobilie skeneri utt.) vai ar mantoju\u0161\u0101m vai specializ\u0113t\u0101m sist\u0113m\u0101m (piem\u0113ram, RFID mar\u0137iera atpaz\u012b\u0161anas sist\u0113m\u0101m). \u013boti svar\u012bgi katram uzdevumam izv\u0113l\u0113ties vispiem\u0113rot\u0101ko integr\u0101cijas meh\u0101nismu.<\/p>\n<h3>Integr\u0101cijas iesp\u0113jas ar 1C<\/h3>\n<p>\nIr da\u017e\u0101di pieejas, k\u0101 \u012bstenot integr\u0101ciju ar 1C lietojumprogramm\u0101m, kuru izv\u0113l\u0113ties - atkar\u012bgs no uzdevuma pras\u012bb\u0101m.<\/p>\n<ol>\n<li>\u012asteno\u0161ana, balstoties uz <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000581.htm\">integr\u0101cijas meh\u0101nismiem<\/a><\/noindex>, ko nodro\u0161ina platforma, t\u0101s pa\u0161u specializ\u0113to API 1C lietojumprogrammas pus\u0113 (piem\u0113ram, Web- vai HTTP pakalpojumu komplekti, kas tiks izsaukti no tre\u0161o personu lietojumprogramm\u0101m, lai apmain\u012btos ar datiem ar 1C lietojumprogrammu). \u0160\u012b pieejas priek\u0161roc\u012bba ir API iztur\u012bba pret izmai\u0146\u0101m 1C lietojumprogrammas pus\u0113. Pieejas \u012bpatn\u012bba ir t\u0101da, ka j\u0101maina 1C tipisk\u0101 risin\u0101juma avota kods, kas potenci\u0101li var pras\u012bt piep\u016bli, apvienojot avota kodus, p\u0101rejot uz jaunu konfigur\u0101cijas versiju. \u0160aj\u0101 gad\u012bjum\u0101 var noder\u0113t jauna progres\u012bva funkcionalit\u0101te \u2014 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000883.htm\">konfigur\u0101cijas papla\u0161in\u0101jumi<\/a><\/noindex>. Papla\u0161in\u0101jumi ir b\u016bt\u012bb\u0101 spraud\u0146u meh\u0101nisms, kas \u013cauj izveidot piel\u0101gojumus lietojumprogramm\u0101m, nemainot pa\u0161as lietojumprogrammas. Integr\u0101cijas API p\u0101rvieto\u0161ana konfigur\u0101cijas papla\u0161in\u0101jum\u0101 \u013caus izvair\u012bties no sare\u017e\u0123\u012bjumiem, apvienojot konfigur\u0101cijas, p\u0101rejot uz jauno standarta risin\u0101juma versiju.\n<\/li>\n<li>Platformas integr\u0101cijas meh\u0101nismu izmanto\u0161ana, kas nodro\u0161ina piek\u013cuvi \u0101rpus\u0113 pie lietojumprogrammas objektu mode\u013ca un neprasa lietojumprogrammas p\u0101rb\u016bvi vai papla\u0161in\u0101jumu izveidi. \u0160\u012b pieejas priek\u0161roc\u012bba ir t\u0101, ka nav j\u0101maina 1C lietojumprogramma. M\u012bnuss ir tas, ka, ja 1C lietojumprogramma ir bijusi p\u0101rveidota, tad var b\u016bt nepiecie\u0161amas p\u0101rveides integr\u0113taj\u0101 lietojumprogramm\u0101. \u0160\u0101da pieejas piem\u0113rs ir OData protokola izmanto\u0161ana integr\u0101cijai, kas ir \u012bstenots 1C: Uz\u0146\u0113muma platformas pus\u0113 (s\u012bk\u0101k par to zem\u0101k).\n<\/li>\n<li>Gatavo lietojumprogrammu protokolu izmanto\u0161ana, kas ir \u012bstenoti standarta 1C risin\u0101jumos. Daudzi standarta risin\u0101jumi no 1C un partneriem \u012bsteno savus lietojumprogrammu protokolus, kas ir balst\u012bti uz platformas nodro\u0161in\u0101tajiem integr\u0101cijas meh\u0101nismiem, orient\u0113joties uz konkr\u0113t\u0101m uzdevumu pras\u012bb\u0101m. Izmantojot \u0161os meh\u0101nismus, nav nepiecie\u0161ams rakst\u012bt kodu 1C lietojumprogrammas pus\u0113, jo m\u0113s izmantojam standarta lietojumprogrammas iesp\u0113jas. 1C lietojumprogrammas pus\u0113 mums ir j\u0101nok\u0101rto tikai noteiktas iestat\u012bjumi.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Integr\u0101cijas meh\u0101nismi 1C:Uz\u0146\u0113muma platform\u0101<\/h3>\n<p><\/p>\n<h4>Failu imports\/eksports<\/h4>\n<p>\nPie\u0146emsim, ka mums ir uzdevums veikt divvirzienu datu apmai\u0146u starp 1C lietojumprogrammu un patva\u013c\u012bgu lietojumprogrammu. Piem\u0113ram, mums j\u0101sinhroniz\u0113 pre\u010du saraksts (Nomenklat\u016bras re\u0123istrs) starp 1C lietojumprogrammu un patva\u013c\u012bgu lietojumprogrammu.<\/p>\n<p><img decoding=\"async\" alt=\"Integr\u0101cijas veidi ar 1C\" src=\"\/wp-content\/uploads\/2019\/08\/9678f09dfcf7f70de100ed74ada6019c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nLai atrisin\u0101tu \u0161\u0101du uzdevumu, var izveidot papla\u0161in\u0101jumu, kas eksport\u0113 Nomenklat\u016bras re\u0123istru fail\u0101 noteikt\u0101 form\u0101t\u0101 (teksta, XML, JSON utt.) un sp\u0113j las\u012bt \u0161o form\u0101tu. <\/p>\n<p>Platform\u0101 ir \u012bstenots lietojumprogrammu objektu seri\u0101liz\u0101cijas meh\u0101nisms XML form\u0101t\u0101, gan tie\u0161i, izmantojot glob\u0101l\u0101 konteksta metodes Izrakst\u012btXML\/Las\u012btXML, gan ar pal\u012bdz\u012bgu objektu XDTO (XML datu p\u0101rs\u016bt\u012b\u0161anas objekti).<\/p>\n<p>Jebkur\u0161 objekts 1C:Uz\u0146\u0113muma sist\u0113m\u0101 var tikt seri\u0101liz\u0113ts XML att\u0113l\u0101 un otr\u0101di. <\/p>\n<p>\u0160\u012b funkcija atgriez\u012bs objekta att\u0113lu XML form\u0101t\u0101:<\/p>\n<pre><code class=\"1c\">Funkcija Objekts_XML(Objekts)\n    IerakstsXML = Jauns IerakstsXML();\n    IerakstsXML.Iest\u0101d\u012btRindu();\n    Ierakst\u012btXML(IerakstsXML, Objekts);\n    Atgriezt IerakstsXML.Aizv\u0113rt();\nGalaFunkcijas\n<\/code><\/pre>\n<p>\nt\u0101 izskat\u012bsies noliktavas eksports XML, izmantojot XDTO:<\/p>\n<pre><code class=\"1c\">&amp;UzServera\nProced\u016bra EksportsXMLUzServera()\t\n\tJaunsSeri\u0101lizatorsXDTO  = Seri\u0101lizatorsXDTO;\n\tJaunsIerakstsXML = Jauns IerakstsXML();\n\tJaunsIerakstsXML.Atv\u0113rtFailu(\"C:DataNomenklat\u016bra.xml\", \"UTF-8\");\n\t\n\tJaunsIerakstsXML.Ierakst\u012btApliecin\u0101jumuXML();\n\tJaunsIerakstsXML.Ierakst\u012btElementaS\u0101kumu(\"NoliktavaNomenklat\u016bra\");\n\t\n\tAtlas\u012b\u0161ana = Noliktavas.Nomenklat\u016bra.Atv\u0113rt();\n\t\n\tKam\u0113r Atlas\u012b\u0161ana.N\u0101kamais() Cikls \n\t\tObjektsNomenklat\u016bra = Atlas\u012b\u0161ana.Ieg\u016btObjektu();\n\t\tJaunsSeri\u0101lizatorsXDTO.Ierakst\u012btXML(JaunsIerakstsXML, ObjektsNomenklat\u016bra, XMLVeidaPie\u0161\u0137ir\u0161ana.Destin\u0113ta);\n\tGalaCikls;\n\t\n\tJaunsIerakstsXML.Ierakst\u012btElementaBeigas();\n\tJaunsIerakstsXML.Aizv\u0113rt();\t\nGalaProced\u016bra\n<\/code><\/pre>\n<p>\nVienk\u0101r\u0161i p\u0101rveidojot kodu, m\u0113s eksport\u0113jam noliktavu JSON form\u0101t\u0101. Preces tiks ierakst\u012btas mas\u012bv\u0101; lai da\u017e\u0101dotu, sniegsim ang\u013cu izteiksmes sintaksi:<\/p>\n<pre><code class=\"1c\">&amp;UzServera\nProced\u016bra EksportsJSONUzServer()\n\tJaunsXDTOSeri\u0101lizators  = XDTOSeri\u0101lizators;\n\tJaunsJSONRakst\u012bt\u0101js = Jauns JSONRakst\u012bt\u0101js();\n\tJaunsJSONRakst\u012bt\u0101js.Atv\u0113rtFailu(\"C:DataNomenklat\u016bra.json\", \"UTF-8\");\n\t\n\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012btS\u0101kumaObjektu();\n\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012bt\u012apa\u0161\u012bbasNosaukumu(\"NoliktavaNomenklat\u016bra\");\n\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012btS\u0101ktMas\u012bvu();\n\t\n\tAtlas\u012b\u0161ana = Noliktavas.Nomenklat\u016bra.Atv\u0113rt();\t\n\t\n\tKam\u0113r Atlas\u012b\u0161ana.N\u0101kamais() Dari \n\t\tNomenklat\u016brasObjekts = Atlas\u012b\u0161ana.Ieg\u016btObjektu();\n\t\t\n\t\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012btS\u0101kumaObjektu();\n\t\t\n\t\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012bt\u012apa\u0161\u012bbasNosaukumu(\"Nomenklat\u016bra\");\n\t\tJaunsXDTOSeri\u0101lizators.Ierakst\u012btJSON(JaunsJSONRakst\u012bt\u0101js, Nomenklat\u016brasObjekts, XMLVeidaPie\u0161\u0137ir\u0161ana.Iepaz\u012bstino\u0161a);\n\t\t\n\t\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012btBeiguObjektu();\n\tGalaDari;\n\t\n\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012btBeiguMas\u012bvu();\n\tJaunsJSONRakst\u012bt\u0101js.Ierakst\u012btBeiguObjektu();\n\tJaunsJSONRakst\u012bt\u0101js.Aizv\u0113rt();\t\nGalaProced\u016bra\n<\/code><\/pre>\n<p>\nT\u0101l\u0101k paliek tikai nodot datus galapat\u0113r\u0113t\u0101jam. 1C:Uz\u0146\u0113mums platforma atbalsta galvenos interneta protokolus HTTP, FTP, POP3, SMTP, IMAP, tostarp to dro\u0161\u0101s versijas. Datu p\u0101rs\u016bt\u012b\u0161anai var izmantot ar\u012b HTTP un\/vai t\u012bmek\u013ca pakalpojumus.<\/p>\n<h4>HTTP un t\u012bmek\u013ca pakalpojumi<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Integr\u0101cijas veidi ar 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1d4797d9298f793e19ee637fd26473b2.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>1C lietojumprogrammas var ieviest savus HTTP un t\u012bmek\u013ca pakalpojumus, k\u0101 ar\u012b izsaukt HTTP un t\u012bmek\u013ca pakalpojumus, ko \u012bstenoju\u0161as tre\u0161o pu\u0161u lietojumprogrammas. <\/p>\n<h4>REST interfeiss un protokols OData<\/h4>\n<p>\nS\u0101kot no versijas 8.3.5, 1C:Uz\u0146\u0113mums platforma var autom\u0101tiski <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/avtomaticheskiy-rest-interfeys-prikladnykh-resheniy\/\">veidot REST interfeisu<\/a><\/noindex> visai pielietojuma risin\u0101jumam. Jebkuru konfigur\u0101cijas objektu (noliktava, dokuments, inform\u0101cijas re\u0123istrs utt.) var padar\u012bt pieejamu datu ieg\u016b\u0161anai un modific\u0113\u0161anai caur REST interfeisu. Platforma izmanto protokolu piek\u013cuvei. <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Open_Data_Protocol\">OData<\/a><\/noindex> versija 3.0. OData pakalpojumu public\u0113\u0161ana notiek no konfiguratora izv\u0113lnes \u201eAdministr\u0113\u0161ana -&gt; Publik\u0101cija t\u012bmek\u013ca server\u012b\u201d, j\u0101b\u016bt atz\u012bm\u0113tam lodzi\u0146am \u201ePublic\u0113t standarta OData saskarni\u201d. Tiek atbalst\u012bti form\u0101ti atom\/XML un JSON. P\u0113c tam, kad lietojumprogrammas risin\u0101jums ir public\u0113ts t\u012bmek\u013ca server\u012b, tre\u0161\u0101s puses sist\u0113mas var piek\u013c\u016bt tam caur REST saskarni, izmantojot HTTP piepras\u012bjumus. Lai str\u0101d\u0101tu ar 1C lietojumprogrammu caur OData protokolu, programm\u0113\u0161ana 1C pus\u0113 nav nepiecie\u0161ama.<\/p>\n<p>T\u0101tad URL veid\u0101 <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Produkti<\/u> atgriez\u012bs mums Katalogs Produktu saturu XML form\u0101t\u0101 \u2014 elementu entry kolekciju (zi\u0146ojuma galvene ir izlaista \u012bsumam):<\/p>\n<pre><code class=\"xml\">http:\/\/serveris\/Config\/odata\/standard.odata\/Catalog_Produkti(guid'35d1f6e4-289b-11e6-8ba4-e03f49b16074')\n\t\n\t<title \/>\n\t2016-06-06T16:42:17\n\t\n\t<summary \/>\n\t\n\t\n\t\t\n\t\t\t35d1f6e4-289b-11e6-8ba4-e03f49b16074\n\t\t\tAAAAAgAAAAA=\n\t\t\tfalse\n\t\t\t000000001\n\t\t\tKondicionieris Mitsubishi\n\t\t\tJauda 2,5 kW, darb\u012bbas re\u017e\u012bmi: siltums\/aukstums\n\t\t\n\t\n\n\n\thttp:\/\/serveris\/Config\/odata\/standard.odata\/Catalog_Produkti(guid'35d1f6e5-289b-11e6-8ba4-e03f49b16074')\n\t\n...\n<\/code><\/pre>\n<p>\nPievienojot URL-\u0101 virkni \u201e?$format=application\/json\u201d, ieg\u016bsim Katalogs Produktu saturu JSON form\u0101t\u0101 (URL veid\u0101 <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Produkti?$format=application\/json<\/u> ):<\/p>\n<pre><code>{\n\"odata.metadata\": \"http:\/\/serveris\/Config\/odata\/standard.odata\/$metadata#Catalog_Produkti\",\n\"value\": [{\n\"Ref_Key\": \"35d1f6e4-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAgAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000001\",\n\"Description\": \"Kondicionieris Mitsubishi\",\n\"Apraksts\": \"Jauda 2,5 kW, darb\u012bbas re\u017e\u012bmi: siltums\/aukstums\"\n},{\n\"Ref_Key\": \"35d1f6e5-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAwAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000002\",\n\"Description\": \"Kondicionieris Daikin\",\n\"Apraksts\": \"Jauda 3 kW, darb\u012bbas re\u017e\u012bmi: siltums\/aukstums\"\n}, \u2026\n<\/code><\/pre>\n<p><\/p>\n<h4>\u0100r\u0113jie datu avoti<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Integr\u0101cijas veidi ar 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1663b53846f3a6a8a03f386f1f6cd311.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDa\u017eos gad\u012bjumos datu apmai\u0146a caur <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000795.htm\">\u0101r\u0113jiem datu avotiem<\/a><\/noindex> var\u0113tu b\u016bt optim\u0101ls risin\u0101jums. \u0100r\u0113jie datu avoti ir 1C konfigur\u0101cijas lietojumobjekts, kas \u013cauj sadarboties ar jebkuru ODBC sader\u012bgu datu b\u0101zi gan las\u012b\u0161anai, gan rakst\u012b\u0161anai. \u0100r\u0113jie datu avoti ir pieejami gan Windows, gan Linux.<\/p>\n<h4>Datu apmai\u0146as meh\u0101nisms<\/h4>\n<p>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000269.htm\">Datu apmai\u0146as meh\u0101nisms<\/a><\/noindex> ir paredz\u0113ts gan teritoriju izplat\u012btu sist\u0113mu veido\u0161anai, pamatojoties uz 1C:Enterprise, gan datu apmai\u0146as organiz\u0113\u0161anai ar cit\u0101m inform\u0101cijas sist\u0113m\u0101m, kas nav pamats 1C:Enterprise.<\/p>\n<p>\u0160is meh\u0101nisms tiek akt\u012bvi izmantots 1C ievie\u0161an\u0101, un uzdevumu spektrs, ko tas risina, ir \u013coti pla\u0161s. Tas ietver datu apmai\u0146u starp 1C lietojumprogramm\u0101m, kas uzst\u0101d\u012btas organiz\u0101cijas fili\u0101l\u0113s, k\u0101 ar\u012b apmai\u0146u starp 1C lietojumprogrammu un interneta veikala vietni, un datu apmai\u0146u starp 1C servera lietojumprogrammu un mobilo klientu (izveidotu, izmantojot 1C:Enterprise mobilo platformu), un daudz ko citu.<\/p>\n<p>Viens no galvenajiem j\u0113dzieniem datu apmai\u0146as meh\u0101nism\u0101 ir apmai\u0146as pl\u0101ns. Apmai\u0146as pl\u0101ns ir \u012bpa\u0161s 1C platformas lietojumobjekta veids, kas nosaka, jo \u012bpa\u0161i, datu sast\u0101vu, kas piedal\u012bsies apmai\u0146\u0101 (kuri tie\u0161i katalogi, dokumenti, re\u0123istri utt.). Apmai\u0146as pl\u0101ns satur ar\u012b inform\u0101ciju par apmai\u0146as dal\u012bbniekiem (t.s. apmai\u0146as mezgliem).<br \/>\nOtr\u0101 datu apmai\u0146as meh\u0101nisma sast\u0101vda\u013ca ir izmai\u0146u re\u0123istr\u0113\u0161anas meh\u0101nisms. \u0160is meh\u0101nisms autom\u0101tiski seko izmai\u0146\u0101m sist\u0113m\u0101, kuras j\u0101nos\u016bta galapat\u0113r\u0113t\u0101jiem apmai\u0146as pl\u0101na ietvaros. \u0160\u012b meh\u0101nisma pal\u012bdz\u012bbu platforma seko izmai\u0146\u0101m, kas notiku\u0161as kop\u0161 p\u0113d\u0113j\u0101s sinhroniz\u0101cijas, un \u013cauj minimiz\u0113t datu apjomu, kas tiek nodots n\u0101kam\u0101 sinhroniz\u0101cijas sesijas laik\u0101.<\/p>\n<p>Datu apmai\u0146a notiek, izmantojot noteikta form\u0101ta XML zi\u0146ojumus. Zi\u0146ojums satur datus, kas main\u012bju\u0161ies kop\u0161 p\u0113d\u0113j\u0101s sinhroniz\u0101cijas ar mezglu, k\u0101 ar\u012b k\u0101du tehnisku inform\u0101ciju. Zi\u0146ojumu strukt\u016bra atbalsta zi\u0146ojumu numur\u0113\u0161anu un \u013cauj sa\u0146emt apstiprin\u0101jumus no sa\u0146\u0113m\u0113ju mezgla par zi\u0146ojumu sa\u0146em\u0161anu. \u0160\u0101ds apstiprin\u0101jums ir iek\u013cauts katr\u0101 zi\u0146ojum\u0101, kas n\u0101k no sa\u0146\u0113m\u0113ju mezgla, k\u0101 p\u0113d\u0113j\u0101 sa\u0146emt\u0101 zi\u0146ojuma numurs. Zi\u0146ojumu numur\u0113\u0161ana \u013cauj platformai saprast, kuri dati jau ir veiksm\u012bgi nodoti sa\u0146\u0113m\u0113ju mezglam, un nov\u0113rst atk\u0101rtotu nodo\u0161anu, nododot tikai datus, kas main\u012bj\u0101s kop\u0161 p\u0113d\u0113j\u0101 zi\u0146ojuma sa\u0146em\u0161anas ar kv\u012bti par sa\u0146emtiem datiem no sa\u0146\u0113m\u0113ju mezgla. \u0160\u0101ds darb\u012bbas modelis nodro\u0161ina garant\u0113tu pieg\u0101di pat nep\u0101rliecino\u0161os p\u0101rraides kan\u0101los un zi\u0146ojumu zuduma gad\u012bjum\u0101.<\/p>\n<h4>\u0100r\u0113jie komponenti<\/h4>\n<p>\nDa\u017eos gad\u012bjumos, risinot integr\u0101cijas uzdevumus, n\u0101kas saskarties ar specifisk\u0101m pras\u012bb\u0101m, piem\u0113ram, mijiedarb\u012bbas protokoliem, datu form\u0101tiem, kuru apstr\u0101de nav paredz\u0113ta 1C:Enterprise platform\u0101. \u0160\u0101da veida uzdevumiem platforma nodro\u0161ina <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000545.htm\">\u0101r\u0113jo komponentu tehnolo\u0123iju<\/a><\/noindex>, kas \u013cauj izveidot dinamiski piesl\u0113dzamus modu\u013cus, kas papla\u0161ina 1C:Enterprise funkcionalit\u0101ti. <\/p>\n<p>Tipisks piem\u0113rs uzdevumam ar l\u012bdz\u012bg\u0101m pras\u012bb\u0101m var\u0113tu b\u016bt 1C lietojumprogrammas integr\u0101cija ar tirdzniec\u012bbas apr\u012bkojumu, s\u0101kot no svariem un beidzot ar kase\u0161u apar\u0101tiem un sv\u012btrkodu skeneriem. \u0100r\u0113jie komponenti var b\u016bt piesl\u0113gti gan 1C:Enterprise servera pus\u0113, gan klienta da\u013c\u0101 (ieskaitot, protams, t\u012bmek\u013ca klientu, k\u0101 ar\u012b <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/vneshnie-komponenty-v-mobilnom-prilozhenii\/\">n\u0101kamo mobilo platformas versiju<\/a><\/noindex> 1C:Enterprise). \u0100r\u0113jo komponentu tehnolo\u0123ija paredz pietiekami vienk\u0101r\u0161u un saprotamu programmat\u016bras (C++) saskarni, ar kuru komponenti var mijiedarboties ar 1C:Enterprise platformu, kuru j\u0101realiz\u0113 izstr\u0101d\u0101t\u0101jam.<\/p>\n<p>Iesp\u0113jas, kas rodas, izmantojot \u0101r\u0113j\u0101s komponentes, ir \u013coti pla\u0161as. Var realiz\u0113t mijiedarb\u012bbu saska\u0146\u0101 ar specifisku datu apmai\u0146as protokolu ar \u0101r\u0113j\u0101m ier\u012bc\u0113m un sist\u0113m\u0101m, ieb\u016bv\u0113t specifiskus datu apstr\u0101des algoritmus un datu form\u0101tus u.t.t.<\/p>\n<h4>Noveco\u0161an\u0101s integr\u0101cijas meh\u0101nismi<\/h4>\n<p>\nPlatform\u0101 ir pieejami integr\u0101cijas meh\u0101nismi, kurus ieteicams neizmantot jaun\u0101s risin\u0101jumos; tie ir atst\u0101ti atpaka\u013csader\u012bbas apsv\u0113rumu d\u0113\u013c, k\u0101 ar\u012b gad\u012bjum\u0101, ja otra puse nesp\u0113j str\u0101d\u0101t ar modern\u0101kiem protokoliem. Viens no tiem ir darbs ar DBF form\u0101ta failiem (tiek atbalst\u012bts ieb\u016bv\u0113taj\u0101 valod\u0101, izmantojot XBase objektu).<\/p>\n<p>V\u0113l viens novecojis integr\u0101cijas meh\u0101nisms ir COM tehnolo\u0123ijas izmanto\u0161ana (pieejama tikai Windows platform\u0101). 1C:Uz\u0146\u0113mums sniedz divus integr\u0101cijas veidus Windows, kas izmanto COM tehnolo\u0123iju: Automation serveri un \u0100r\u0113jo savienojumu. Tie ir \u013coti l\u012bdz\u012bgi, ta\u010du viena no pamatat\u0161\u0137ir\u012bb\u0101m ir t\u0101da, ka Automation servera gad\u012bjum\u0101 tiek palaists pilnv\u0113rt\u012bgs 1C:Uz\u0146\u0113mums 8 klienta lietojumprogramma, savuk\u0101rt \u0101r\u0113j\u0101 savienojuma gad\u012bjum\u0101 tiek palaists sal\u012bdzino\u0161i neliels iek\u0161processa COM serveris. Proti, str\u0101d\u0101jot caur Automation serveri, var izmantot klienta lietojumprogrammas funkcionalit\u0101ti, veicot darb\u012bbas, kas l\u012bdz\u012bgas lietot\u0101ja interakt\u012bv\u0101m darb\u012bb\u0101m. Izmantojot \u0101r\u0113jo savienojumu, var izmantot tikai biznesa lo\u0123ikas funkcijas, kuras var veikt gan savienojuma klienta pus\u0113, kur izveidojas iek\u0161processa COM serveris, gan veikt biznesa lo\u0123ikas izsaukumu 1C:Uz\u0146\u0113muma servera pus\u0113.<\/p>\n<p>COM tehnolo\u0123iju var izmantot ar\u012b, lai piek\u013c\u016btu \u0101r\u0113j\u0101m sist\u0113m\u0101m no 1C:Uz\u0146\u0113mums programmas koda. \u0160aj\u0101 gad\u012bjum\u0101 1C lietojumprogramma darbojas k\u0101 COM klients. Ta\u010du j\u0101piebilst, ka \u0161ie meh\u0101nismi darbosies tikai tad, ja 1C serveris funkcion\u0113 Windows vid\u0113.<\/p>\n<h3>Integr\u0101cijas meh\u0101nismi, kas realiz\u0113ti tipiskaj\u0101s konfigur\u0101cij\u0101s<\/h3>\n<p><\/p>\n<h4>EnterpriseData form\u0101ts<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Integr\u0101cijas veidi ar 1C\" src=\"\/wp-content\/uploads\/2019\/08\/8930091e53309b9b808a719b747a6226.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDa\u017e\u0101s 1C konfigur\u0101cij\u0101s (apak\u0161\u0113jais saraksts) uz iepriek\u0161min\u0113t\u0101 platformas datu apmai\u0146as meh\u0101nisma pamata ir izstr\u0101d\u0101ts gatavs datu apmai\u0146as meh\u0101nisms ar \u0101r\u0113jiem lietojumiem, kas neprasa izmai\u0146as konfigur\u0101ciju avota kod\u0101 (datu apmai\u0146as sagatavo\u0161ana tiek veikta pielietojumu risin\u0101jumu iestat\u012bjumos):<\/p>\n<ul>\n<li>\u00ab1C:ERP Uz\u0146\u0113muma vad\u012bba 2.0\u00bb <\/li>\n<li>\u00abKompleks\u0101 automatiz\u0101cija 2\u00bb <\/li>\n<li>\u00abUz\u0146\u0113muma gr\u0101matved\u012bba\u00bb, 3.0 izdevums <\/li>\n<li>\u00abUz\u0146\u0113muma gr\u0101matved\u012bba KORP\u00bb, 3.0 izdevums <\/li>\n<li>\u00abMazumtirdzniec\u012bba\u00bb, 2.0 izdevums <\/li>\n<li>\u00abTirdzniec\u012bbas vad\u012bba pamatversija\u00bb, redakcija 11 <\/li>\n<li>\u00abTirdzniec\u012bbas vad\u012bba\u00bb, redakcija 11<\/li>\n<li>\u00abAlgas un person\u0101la vad\u012bba KORP\u00bb, redakcija 3<\/li>\n<\/ul>\n<p>\nDatu apmai\u0146ai tiek izmantots form\u0101ts <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_app\/enterprisedata\/\">EnterpriseData<\/a><\/noindex>, kas balst\u012bts uz XML. Form\u0101ts ir biznesam orient\u0113ts \u2013 taj\u0101 aprakst\u012bt\u0101s datu strukt\u016bras atbilst biznesa objektiem (dokumentiem un katalogu elementiem), kas tiek att\u0113loti 1C programm\u0101s, piem\u0113ram: izpild\u012bto darbu akts, ien\u0101ko\u0161ais kasieru r\u0113\u0137ins, partneris, nomenklat\u016bra u.tml.<\/p>\n<p>Datu apmai\u0146a starp 1C lietojumprogrammu un tre\u0161\u0101s puses lietojumprogrammu var notikt:<\/p>\n<ul>\n<li>caur noteiktu failu katalogu <\/li>\n<li>caur FTP katalogu <\/li>\n<li>caur t\u012bmek\u013ca servisu, kas izvietots 1C lietojumprogrammas pus\u0113. Fails ar datiem tiek p\u0101rs\u016bt\u012bts k\u0101 parametrs t\u012bmek\u013ca metodei<\/li>\n<li>caur elektronisko pastu<\/li>\n<\/ul>\n<p>\nJa apmai\u0146a notiek caur t\u012bmek\u013ca servisu, tre\u0161\u0101s puses lietojumprogramma uzs\u0101ks datu apmai\u0146as sesiju, izsaucot attiec\u012bg\u0101s 1C lietojumprogrammas t\u012bmek\u013ca metodes. Cit\u0101s situ\u0101cij\u0101s sesijas iniciators b\u016bs 1C lietojumprogramma (ievietojot failu ar datiem attiec\u012bgaj\u0101 katalog\u0101 vai s\u016btot failu ar datiem uz iestat\u012btu e-pasta adresi).<br \/>\nAr\u012b 1C pus\u0113 tiek iestat\u012bts, cik bie\u017ei notiks sinhroniz\u0101cija (failu apmai\u0146as un elektronisk\u0101 pasta variantos):<\/p>\n<ul>\n<li>saska\u0146\u0101 ar grafiku (ar noteiktu bie\u017eumu) <\/li>\n<li>roku; lietot\u0101jam katru reizi b\u016bs manu\u0101li j\u0101uzs\u0101k sinhroniz\u0101cija, kad tas b\u016bs nepiecie\u0161ams<\/li>\n<\/ul>\n<p><\/p>\n<h5>Zin\u0101\u0161anu apstiprin\u0101\u0161ana<\/h5>\n<p>\n1C lietojumprogrammas uzskaita nos\u016bt\u012btos un sa\u0146emtos sinhroniz\u0101cijas zi\u0146ojumus un gaida to pa\u0161u no tre\u0161\u0101s puses lietojumprogramm\u0101m. Tas \u013cauj izmantot zi\u0146ojumu numur\u0113\u0161anas meh\u0101nismu, kas iepriek\u0161 aprakst\u012bts noda\u013c\u0101 \u00abDatu apmai\u0146as meh\u0101nisms\u00bb.<\/p>\n<p>1C lietojumprogrammas sinhroniz\u0101cijas laik\u0101 p\u0101rraida tikai inform\u0101ciju par izmai\u0146\u0101m, kas notiku\u0161as ar biznesa ent\u012btij\u0101m kop\u0161 p\u0113d\u0113j\u0101s sinhroniz\u0101cijas (lai samazin\u0101tu p\u0101rs\u016bt\u0101m\u0101s inform\u0101cijas apjomu). Pirmaj\u0101 sinhroniz\u0101cij\u0101 1C lietojumprogramma izvad\u012bs visas biznesa ent\u012btijas (piem\u0113ram, pre\u010du katalogu elementus) form\u0101t\u0101 EnterpriseData XML fail\u0101 (jo t\u0101s visus ir \u201ejauni\u201d \u0101r\u0113jai lietojumprogrammai). \u0100r\u0113jai lietojumprogrammai j\u0101apstr\u0101d\u0101 inform\u0101cija no sa\u0146emt\u0101 XML faila no 1C, un n\u0101kamaj\u0101 sinhroniz\u0101cijas sesij\u0101 j\u0101iek\u013cauj fail\u0101, kas tiek nos\u016bt\u012bts 1C, \u012bpa\u0161\u0101 XML sekcij\u0101 inform\u0101cija, ka zi\u0146ojums no 1C ar noteiktu numuru ir veiksm\u012bgi sa\u0146emts. Zi\u0146ojumu apstiprin\u0101jums ir sign\u0101ls 1C lietojumprogrammai, ka visas biznesa ent\u012btijas ir veiksm\u012bgi apstr\u0101d\u0101tas \u0101r\u0113j\u0101 lietojum\u0101 un inform\u0101cija par t\u0101m vairs nav j\u0101nodod. Papildus apstiprin\u0101jumam XML fails no \u0101r\u0113j\u0101s lietojumprogrammas var satur\u0113t datus sinhroniz\u0101cijai no lietojumprogrammas puses (piem\u0113ram, pre\u010du un pakalpojumu realiz\u0101cijas dokumentus).<\/p>\n<p>Sa\u0146emot zi\u0146ojuma apstiprin\u0101jumu, 1C lietojumprogramma atz\u012bm\u0113 visas izmai\u0146as, kas tika p\u0101rs\u016bt\u012btas iepriek\u0161\u0113j\u0101 zi\u0146ojum\u0101, k\u0101 veiksm\u012bgi sinhroniz\u0113tas. Tikai ne-sinhroniz\u0113t\u0101s izmai\u0146as biznesa ent\u012btij\u0101s (jaunu ent\u012btiju izveide, eso\u0161o izmai\u0146as un dz\u0113\u0161ana) tiks nos\u016bt\u012btas \u0101r\u0113jai lietojumprogrammai n\u0101kam\u0101s sinhroniz\u0101cijas sesijas laik\u0101.<\/p>\n<p><img decoding=\"async\" alt=\"Integr\u0101cijas veidi ar 1C\" src=\"\/wp-content\/uploads\/2019\/08\/b0d5509a53909e38886a15c2e03e7131.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nDatu p\u0101rs\u016bt\u012b\u0161anas laik\u0101 no \u0101r\u0113j\u0101s lietojumprogrammas uz 1C lietojumprogrammu aina main\u0101s uz pret\u0113jo. \u0100r\u0113jai lietojumprogrammai j\u0101aizpilda XML faila apstiprin\u0101juma sekcija atbilsto\u0161i un j\u0101iek\u013cauj biznesa dati sinhroniz\u0101cijai no savas puses form\u0101t\u0101 EnterpriseData.<\/p>\n<p><img decoding=\"async\" alt=\"Integr\u0101cijas veidi ar 1C\" src=\"\/wp-content\/uploads\/2019\/08\/d34b96efb7591770133b363b369c0019.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h5>Vienk\u0101r\u0161ota datu apmai\u0146a bez apstiprin\u0101\u0161anas<\/h5>\n<p>\nSitu\u0101cij\u0101s, kad ir pietiekami tikai p\u0101rs\u016bt\u012bt inform\u0101ciju no \u0101r\u0113j\u0101s lietojumprogrammas uz 1C lietojumprogrammu un nav nepiecie\u0161ams datu atgrie\u0161ana no 1C lietojumprogrammas \u0101r\u0113jai lietojumprogrammai (piem\u0113ram, integr\u0113jot tie\u0161saistes veikalu, kas sniedz p\u0101rdo\u0161anas inform\u0101ciju \u201e1C:Gr\u0101matved\u012bba\u201d), ir pieejama vienk\u0101r\u0161ota darb\u012bbas iesp\u0113ja caur t\u012bmek\u013ca pakalpojumu (bez apstiprin\u0101\u0161anas), kas neprasa iestat\u012bjumus 1C lietojumprogrammas pus\u0113.<\/p>\n<h4>Speci\u0101li integr\u0101cijas risin\u0101jumi<\/h4>\n<p>\nPast\u0101v standarta risin\u0101jums \u00ab1C: Datu konversija\u00bb, kas izmanto platformas meh\u0101nismus datu konversijai un apmai\u0146ai starp standarta 1C konfigur\u0101cij\u0101m, ta\u010du to var izmantot ar\u012b integr\u0101cijai ar tre\u0161o pu\u0161u lietotn\u0113m.<\/p>\n<h5>Integr\u0101cija ar banku risin\u0101jumiem<\/h5>\n<p>\nStandarts <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/100\/index.htm\">\u00abKlients banka\u00bb<\/a><\/noindex>, ko izstr\u0101d\u0101ja 1C speci\u0101listi vair\u0101k nek\u0101 10 gadus atpaka\u013c, faktiski k\u013cuvis par industrijas standartu Krievij\u0101. N\u0101kamais solis \u0161aj\u0101 virzien\u0101 ir tehnolo\u0123ija <noindex><a rel=\"nofollow\" href=\"http:\/\/directbank.1c.ru\/\">DirectBank<\/a><\/noindex>, kas \u013cauj nos\u016bt\u012bt maks\u0101jumu dokumentus bankai un sa\u0146emt izrakstus no bankas tie\u0161i no 1C programmas, nospie\u017eot vienu tausti\u0146u programmat\u016br\u0101 \u00ab1C\u00bb; \u0161aj\u0101 proces\u0101 nav nepiecie\u0161ama papildu programmu uzst\u0101d\u012b\u0161ana un palai\u0161ana klienta dator\u0101. <\/p>\n<p>Ir ar\u012b <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/109\/\">standarts datu apmai\u0146ai algas projektos<\/a><\/noindex>.<\/p>\n<h5>Cits<\/h5>\n<p>\nV\u0113rts piemin\u0113t <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/131\/\">apmai\u0146as protokolu starp 1C: Uz\u0146\u0113muma sist\u0113mu un vietni<\/a><\/noindex>, komerci\u0101l\u0101s inform\u0101cijas apmai\u0146as standarts <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/90\/\">CommerceML<\/a><\/noindex> (izstr\u0101d\u0101ts sadarb\u012bb\u0101 ar Microsoft, Intel, Price.ru un cit\u0101m komp\u0101nij\u0101m), <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/111\/\">standarts datu apmai\u0146ai par nor\u0113\u0137inu oper\u0101cij\u0101m<\/a><\/noindex>.<br \/>\n<br \/>Avots: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1c\/blog\/308420\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a\u0430\u043a\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0438\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u0435\u0434\u044a\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043a \u0431\u0438\u0437\u043d\u0435\u0441-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c? \u041e\u0434\u043d\u0438\u043c\u0438 \u0438\u0437 \u0441\u0430\u043c\u044b\u0445 \u0433\u043b\u0430\u0432\u043d\u044b\u0445 \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0437\u0430\u0434\u0430\u0447\u0438: \u041b\u0435\u0433\u043a\u043e\u0441\u0442\u044c \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f\/\u0430\u0434\u0430\u043f\u0442\u0430\u0446\u0438\u0438 \u043b\u043e\u0433\u0438\u043a\u0438 \u0440\u0430\u0431\u043e\u0442\u044b \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043a \u043c\u0435\u043d\u044f\u044e\u0449\u0438\u043c\u0441\u044f \u0431\u0438\u0437\u043d\u0435\u0441-\u0437\u0430\u0434\u0430\u0447\u0430\u043c. \u041b\u0435\u0433\u043a\u043e\u0441\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0438 \u0441 \u0434\u0440\u0443\u0433\u0438\u043c\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c\u0438. \u0422\u043e, \u043a\u0430\u043a \u0440\u0435\u0448\u0430\u0435\u0442\u0441\u044f \u0432 1\u0421 \u043f\u0435\u0440\u0432\u0430\u044f \u0437\u0430\u0434\u0430\u0447\u0430, \u0431\u044b\u043b\u043e \u043a\u0440\u0430\u0442\u043a\u043e \u043e\u043f\u0438\u0441\u0430\u043d\u043e \u0432 \u0440\u0430\u0437\u0434\u0435\u043b\u0435 \u00ab\u041a\u0430\u0441\u0442\u043e\u043c\u0438\u0437\u0430\u0446\u0438\u044f \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0430\u00bb \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438; \u043c\u044b \u0435\u0449\u0435 \u0432\u0435\u0440\u043d\u0435\u043c\u0441\u044f \u043a \u044d\u0442\u043e\u0439 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u043e\u0439 \u0442\u0435\u043c\u0435 \u0432 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u0431\u0443\u0434\u0443\u0449\u0438\u0445 \u0441\u0442\u0430\u0442\u0435\u0439. [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27703,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36968","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a\u0430\u043a\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0438\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u0435\u0434\u044a\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043a \u0431\u0438\u0437\u043d\u0435\u0441-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c?\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/sposoby-integratsii-s-1s\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"lv_LV\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0421\u043f\u043e\u0441\u043e\u0431\u044b \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0438 \u0441 1\u0421 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a\u0430\u043a\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0438\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u0435\u0434\u044a\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043a \u0431\u0438\u0437\u043d\u0435\u0441-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c?\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/sposoby-integratsii-s-1s\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:15:01+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:15:01+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Integr\u0101cijas veidi ar 1C | ProHoster","description":"K\u0101di ir galvenie pras\u012bbas biznesa lietotn\u0113m?","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/sposoby-integratsii-s-1s","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0421\u043f\u043e\u0441\u043e\u0431\u044b \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0438 \u0441 1\u0421 | ProHoster","og:description":"\u041a\u0430\u043a\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0438\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u0435\u0434\u044a\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043a \u0431\u0438\u0437\u043d\u0435\u0441-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c?","og:url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/sposoby-integratsii-s-1s","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:15:01+00:00","article:modified_time":"2019-10-31T19:15:01+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"36968","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 05:33:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:35:27","updated":"2026-01-22 05:33:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/36968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=36968"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/36968\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/27703"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=36968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=36968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=36968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}