{"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\/sk\/blog\/administrirovanie\/sposoby-integratsii-s-1s","title":{"rendered":"Sp\u00f4soby integr\u00e1cie s 1C","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Ak\u00e9 s\u00fa najd\u00f4le\u017eitej\u0161ie po\u017eiadavky na podnikov\u00e9 aplik\u00e1cie? Medzi najhlavnej\u0161ie patr\u00ed nasleduj\u00face \u00falohy:<\/p>\n<ul>\n<li>Jednoduchos\u0165 zmeny\/adapt\u00e1cie logiky fungovania aplik\u00e1cie na meniacim sa podnikate\u013esk\u00fdm potreb\u00e1m.<\/li>\n<li>Jednoduchos\u0165 integr\u00e1cie s in\u00fdmi aplik\u00e1ciami.<\/li>\n<\/ul>\n<p>\nSp\u00f4sob, ak\u00fdm sa v 1C rie\u0161i prv\u00e1 \u00faloha, bol stru\u010dne op\u00edsan\u00fd v sekcii \u201ePrisp\u00f4sobenie a podpora\u201c <noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1c\/blog\/267321\/\">tohto \u010dl\u00e1nku<\/a><\/noindex>; k tejto zauj\u00edmavej t\u00e9me sa e\u0161te vr\u00e1time v jednom z bud\u00facich \u010dl\u00e1nkov. Dnes sa v\u0161ak budeme zaobera\u0165 druhou \u00falohou, a to integr\u00e1ciou.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Integra\u010dn\u00e9 \u00falohy<\/h3>\n<p>\nIntegra\u010dn\u00e9 \u00falohy m\u00f4\u017eu by\u0165 r\u00f4zne. Pre rie\u0161enie niektor\u00fdch sta\u010d\u00ed jednoduch\u00e1 interakt\u00edvna v\u00fdmena \u00fadajov - napr\u00edklad na odoslanie zoznamu zamestnancov do banky na spracovanie plastov\u00fdch kariet na v\u00fdplatu. Pre zlo\u017eitej\u0161ie \u00falohy m\u00f4\u017ee by\u0165 potrebn\u00e1 \u00faplne automatizovan\u00e1 v\u00fdmena \u00fadajov, mo\u017eno s odvolan\u00edm sa na biznis logiku vonkaj\u0161ieho syst\u00e9mu. Existuj\u00fa \u00falohy, ktor\u00e9 s\u00fa \u0161pecifick\u00e9, ako integr\u00e1cia s vonkaj\u0161\u00edmi zariadeniami (napr\u00edklad obchodn\u00fdmi zariadeniami, mobiln\u00fdmi skenerami a pod.) alebo s dedi\u010dn\u00fdmi alebo \u00fazko \u0161pecializovan\u00fdmi syst\u00e9mami (napr\u00edklad so syst\u00e9mami na rozpozn\u00e1vanie RFID \u0161t\u00edtkov). Je mimoriadne d\u00f4le\u017eit\u00e9 pre ka\u017ed\u00fa \u00falohu vybra\u0165 najvhodnej\u0161\u00ed mechanizmus integr\u00e1cie.<\/p>\n<h3>Mo\u017enosti integr\u00e1cie s 1C<\/h3>\n<p>\nExistuj\u00fa r\u00f4zne pr\u00edstupy k implement\u00e1cii integr\u00e1cie s aplik\u00e1ciami 1C, ktor\u00fd z nich zvoli\u0165, z\u00e1vis\u00ed od po\u017eiadaviek \u00falohy.<\/p>\n<ol>\n<li>Implement\u00e1cia na z\u00e1klade <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000581.htm\">mechanizmov integr\u00e1cie<\/a><\/noindex>, poskytovan\u00fdch platformou, vlastn\u00e9ho \u0161pecializovan\u00e9ho API na strane aplik\u00e1cie 1C (napr\u00edklad s\u00faboru Web- alebo HTTP slu\u017eieb, ktor\u00e9 bud\u00fa vola\u0165 tretie strany na v\u00fdmenu \u00fadajov s aplik\u00e1ciou 1C). V\u00fdhodou tohto pr\u00edstupu je stabilita API vo\u010di zmene implement\u00e1cie na strane aplik\u00e1cie 1C. \u0160pecifickos\u0165 pr\u00edstupu - je potrebn\u00e9 meni\u0165 zdrojov\u00fd k\u00f3d typick\u00e9ho rie\u0161enia 1C, \u010do m\u00f4\u017ee potenci\u00e1lne vy\u017eadova\u0165 \u00fasilie pri zl\u00fa\u010den\u00ed zdrojov\u00fdch k\u00f3dov pri prechode na nov\u00fa verziu konfigura\u010dn\u00e9ho syst\u00e9mu. V tomto pr\u00edpade m\u00f4\u017ee pr\u00eds\u0165 na pomoc nov\u00e1 progres\u00edvna funk\u010dnos\u0165 - <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000883.htm\">roz\u0161\u00edrenia konfigur\u00e1cie<\/a><\/noindex>. Roz\u0161\u00edrenia s\u00fa vlastne mechanizmus pluginov, ktor\u00fd umo\u017e\u0148uje vytv\u00e1ra\u0165 doplnky aplikativn\u00fdch rie\u0161en\u00ed bez zmeny samotn\u00fdch aplikativn\u00fdch rie\u0161en\u00ed. Vytiahnutie integra\u010dn\u00e9ho API do roz\u0161\u00edrenia konfigur\u00e1cie umo\u017en\u00ed vyhn\u00fa\u0165 sa \u0165a\u017ekostiam pri zl\u00fa\u010den\u00ed konfigur\u00e1ci\u00ed pri prechode na nov\u00fa verziu typov\u00e9ho rie\u0161enia.\n<\/li>\n<li>Pou\u017eitie integra\u010dn\u00fdch mechanizmov platformy, ktor\u00e9 poskytuj\u00fa vonkaj\u0161\u00ed pr\u00edstup k objektov\u00e9mu modelu aplik\u00e1cie a nevy\u017eaduj\u00fa \u00fapravy aplik\u00e1cie alebo vytvorenie roz\u0161\u00edrenia. V\u00fdhodou tohto pr\u00edstupu je, \u017ee nie je potrebn\u00e9 meni\u0165 aplik\u00e1ciu 1C. Nev\u00fdhodou je, \u017ee ak bola aplik\u00e1cia 1C upraven\u00e1, m\u00f4\u017eu by\u0165 potrebn\u00e9 \u00fapravy v integrovanom aplik\u00e1cii. Pr\u00edkladom tohto pr\u00edstupu je pou\u017eitie protokolu OData pre integr\u00e1ciu, ktor\u00fd je implementovan\u00fd na strane platformy 1C:Pred podnik.\n<\/li>\n<li>Pou\u017eitie hotov\u00fdch aplikativn\u00fdch protokolov implementovan\u00fdch v typov\u00fdch rie\u0161eniach 1C. Mnoh\u00e9 typov\u00e9 rie\u0161enia od 1C a partnerov implementuj\u00fa na z\u00e1klade integra\u010dn\u00fdch mechanizmov poskytovan\u00fdch platformou svoje vlastn\u00e9 aplikativn\u00e9 protokoly zameran\u00e9 na konkr\u00e9tne \u00falohy. Pri pou\u017eit\u00ed t\u00fdchto mechanizmov nie je potrebn\u00e9 p\u00edsanie k\u00f3du na strane aplik\u00e1cie 1C, preto\u017ee vyu\u017e\u00edvame \u0161tandardn\u00e9 mo\u017enosti aplikativn\u00e9ho rie\u0161enia. Na strane aplik\u00e1cie 1C mus\u00edme iba vykona\u0165 ur\u010dit\u00e9 nastavenia.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Integra\u010dn\u00e9 mechanizmy na platforme 1C:Pred podnik<\/h3>\n<p><\/p>\n<h4>Import\/export s\u00faborov<\/h4>\n<p>\nPredpokladajme, \u017ee sa pred nami nach\u00e1dza \u00faloha obojsmernej v\u00fdmeny d\u00e1t medzi aplik\u00e1ciou 1C a \u013eubovo\u013enou aplik\u00e1ciou. Napr\u00edklad, mus\u00edme synchronizova\u0165 zoznam produktov (referen\u010dn\u00fd \u00fadaj Nomenklat\u00fara) medzi aplik\u00e1ciou 1C a \u013eubovo\u013enou aplik\u00e1ciou.<\/p>\n<p><img decoding=\"async\" alt=\"Sp\u00f4soby integr\u00e1cie s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/9678f09dfcf7f70de100ed74ada6019c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nNa vyrie\u0161enie takejto \u00falohy je mo\u017en\u00e9 nap\u00edsa\u0165 roz\u0161\u00edrenie, ktor\u00e9 exportuje referen\u010dn\u00fd \u00fadaj Nomenklat\u00fara do s\u00faboru ur\u010dit\u00e9ho form\u00e1tu (textov\u00fd, XML, JSON, \u2026) a dok\u00e1\u017ee tento form\u00e1t na\u010d\u00edta\u0165. <\/p>\n<p>Na platforme je implementovan\u00fd mechanizmus serializ\u00e1cie aplikativn\u00fdch objektov do XML, a to priamo, prostredn\u00edctvom met\u00f3d glob\u00e1lneho kontextu Zap\u00edsa\u0165XML\/\u010c\u00edta\u0165XML, ako aj pomocou pomocn\u00e9ho objektu XDTO (XML Data Transfer Objects).<\/p>\n<p>Ak\u00fdko\u013evek objekt v syst\u00e9me 1C:Pred podnik m\u00f4\u017ee by\u0165 serializovan\u00fd do XML reprezent\u00e1cie a naopak. <\/p>\n<p>T\u00e1to funkcia vr\u00e1ti reprezent\u00e1ciu objektu vo forme XML:<\/p>\n<pre><code class=\"1c\">Funkcia Objekt_V_XML(Objekt)\n    ZapisXML = Nov\u00fd ZapisXML();\n    ZapisXML.Ustanovi\u0165Riadok();\n    Zap\u00edsa\u0165XML(ZapisXML, Objekt);\n    Vr\u00e1ti\u0165 ZapisXML.Zavrie\u0165();\nKoniecFunkcie\n<\/code><\/pre>\n<p>\ntakto bude vyzera\u0165 export katal\u00f3gu Nomenklat\u00fara do XML pomocou XDTO:<\/p>\n<pre><code class=\"1c\">&amp;NaServeri\nProced\u00fara ExportXMLNaServeri()\t\n\tNov\u00fdSerializerXDTO  = SerializerXDTO;\n\tNov\u00e1ZapisXML = Nov\u00fd ZapisXML();\n\tNov\u00e1ZapisXML.Otvori\u0165S\u00fabor(\"C:DataNomenklat\u00fara.xml\", \"UTF-8\");\n\t\n\tNov\u00e1ZapisXML.Zap\u00edsa\u0165Ozn\u00e1menieXML();\n\tNov\u00e1ZapisXML.Zap\u00edsa\u0165Za\u010diatokElementu(\"Katal\u00f3gNomenklat\u00fara\");\n\t\n\tV\u00fdber = Katal\u00f3gy.Nomenklat\u00fara.Vybra\u0165();\n\t\n\tK\u00fdm V\u00fdber\u010eal\u0161\u00ed() Cyklus \n\t\tObjektNomenklat\u00fara = V\u00fdber.Z\u00edska\u0165Objekt();\n\t\tNov\u00fdSerializerXDTO.Zap\u00edsa\u0165XML(Nov\u00e1ZapisXML, ObjektNomenklat\u00fara, PriradenieTypuXML.Jasn\u00e9);\n\tKoniecCyklu;\n\t\n\tNov\u00e1ZapisXML.Zap\u00edsa\u0165KoniecElementu();\n\tNov\u00e1ZapisXML.Zavrie\u0165();\t\nKoniecProced\u00fary\n<\/code><\/pre>\n<p>\nJednoduchou \u00fapravou k\u00f3du exportujeme katal\u00f3g do JSON. Tovary bud\u00fa zap\u00edsan\u00e9 do po\u013ea; pre rozmanitos\u0165 prinesieme anglick\u00fa verziu syntaxe:<\/p>\n<pre><code class=\"1c\">&amp;NaServeri\nProced\u00fara ExportJSONNaServer()\n\tNov\u00fdXDTOSerializer  = XDTOSerializer;\n\tNov\u00fdJSONWriter = Nov\u00fd JSONWriter();\n\tNov\u00fdJSONWriter.Otvori\u0165S\u00fabor(\"C:DataNomenklat\u00fara.json\", \"UTF-8\");\n\t\n\tNov\u00fdJSONWriter.Zap\u00edsa\u0165Za\u010diatokObjektu();\n\tNov\u00fdJSONWriter.Zap\u00edsa\u0165N\u00e1zovVlastnosti(\"Katal\u00f3gNomenklat\u00fara\");\n\tNov\u00fdJSONWriter.Zap\u00edsa\u0165Za\u010diatokPo\u013ea();\n\t\n\tV\u00fdber = Katal\u00f3gy.Nomenklat\u00fara.Vybra\u0165();\t\n\t\n\tK\u00fdm V\u00fdber.Nasleduj\u00faci() Robi\u0165 \n\t\tObjektNomenklat\u00fara = V\u00fdber.Z\u00edska\u0165Objekt();\n\t\t\n\t\tNov\u00fdJSONWriter.Zap\u00edsa\u0165Za\u010diatokObjektu();\n\t\t\n\t\tNov\u00fdJSONWriter.Zap\u00edsa\u0165N\u00e1zovVlastnosti(\"Nomenklat\u00fara\");\n\t\tNov\u00fdXDTOSerializer.Zap\u00edsa\u0165JSON(Nov\u00fdJSONWriter, ObjektNomenklat\u00fara, PriradenieTypuXML.Nem\u00e4kk\u00e9);\n\t\t\n\t\tNov\u00fdJSONWriter.Zap\u00edsa\u0165KoniecObjektu();\n\tKoniecRobi\u0165;\n\t\n\tNov\u00fdJSONWriter.Zap\u00edsa\u0165KoniecPo\u013ea();\n\tNov\u00fdJSONWriter.Zap\u00edsa\u0165KoniecObjektu();\n\tNov\u00fdJSONWriter.Zavrie\u0165();\t\nKoniecProced\u00fary\n<\/code><\/pre>\n<p>\n\u010ealej zost\u00e1va len odovzda\u0165 \u00fadaje kone\u010dn\u00e9mu z\u00e1kazn\u00edkovi. Platforma 1C:Podnikanie podporuje z\u00e1kladn\u00e9 internetov\u00e9 protokoly HTTP, FTP, POP3, SMTP, IMAP, vr\u00e1tane ich bezpe\u010dn\u00fdch verzi\u00ed. Na prenos \u00fadajov je tie\u017e mo\u017en\u00e9 pou\u017ei\u0165 HTTP a\/alebo Web-slu\u017eby.<\/p>\n<h4>HTTP a web-slu\u017eby<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Sp\u00f4soby integr\u00e1cie s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1d4797d9298f793e19ee637fd26473b2.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Aplik\u00e1cie 1C m\u00f4\u017eu implementova\u0165 svoje HTTP a web-slu\u017eby, ako aj vyvol\u00e1va\u0165 HTTP a web-slu\u017eby, realizovan\u00e9 tret\u00edmi aplik\u00e1ciami. <\/p>\n<h4>REST rozhranie a protokol OData<\/h4>\n<p>\nOd verzie 8.3.5 platforma 1C:Podnikanie m\u00f4\u017ee automaticky <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/avtomaticheskiy-rest-interfeys-prikladnykh-resheniy\/\">formova\u0165 REST rozhranie<\/a><\/noindex> pre cel\u00e9 aplika\u010dn\u00e9 rie\u0161enie. Ak\u00fdko\u013evek objekt konfigur\u00e1cie (katal\u00f3g, dokument, register inform\u00e1ci\u00ed at\u010f.) m\u00f4\u017ee by\u0165 spr\u00edstupnen\u00fd na z\u00edskavanie a modifik\u00e1ciu \u00fadajov prostredn\u00edctvom REST rozhrania. Ako pr\u00edstupov\u00fd protokol platforma pou\u017e\u00edva protokol <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Open_Data_Protocol\">OData<\/a><\/noindex> verzia 3.0. Publikovanie OData slu\u017eieb sa vykon\u00e1va z menu Konfigur\u00e1tora \u201eAdministr\u00e1cia -&gt; Publikovanie na webov\u00fd server\u201c, pri\u010dom mus\u00ed by\u0165 za\u0161krtnut\u00e9 pol\u00ed\u010dko \u201ePublikova\u0165 \u0161tandardn\u00e9 rozhranie OData\u201c. Podporuj\u00fa sa form\u00e1ty atom\/XML a JSON. Po tom, \u010do je aplika\u010dn\u00e9 rie\u0161enie publikovan\u00e9 na webovom serveri, m\u00f4\u017eu k nemu extern\u00e9 syst\u00e9my pristupova\u0165 cez REST rozhranie pomocou HTTP po\u017eiadaviek. Pre pr\u00e1cu s aplik\u00e1ciou 1C prostredn\u00edctvom protokolu OData programovanie na strane 1C nie je potrebn\u00e9.<\/p>\n<p>Tak\u017ee URL vo forme <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Produkt<\/u> n\u00e1m vr\u00e1ti obsah katal\u00f3gu Produkt v XML form\u00e1te \u2014 kolekciu prvkov entry (z\u00e1hlavie spr\u00e1vy je vynechan\u00e9 pre stru\u010dnos\u0165):<\/p>\n<pre><code class=\"xml\">http:\/\/server\/Config\/odata\/standard.odata\/Catalog_Produkt(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\tKlimatiz\u00e1cia Mitsubishi\n\t\t\tV\u00fdkon 2,5 kW, re\u017eimy chodu: teplo\/studen\u00fd\n\t\t\n\t\n\n\n\thttp:\/\/server\/Config\/odata\/standard.odata\/Catalog_Produkt(guid'35d1f6e5-289b-11e6-8ba4-e03f49b16074')\n\t\n...\n<\/code><\/pre>\n<p>\nPridan\u00edm k URL re\u0165azca \u201e?$format=application\/json\u201c z\u00edskame obsah katal\u00f3gu Produkt vo form\u00e1te JSON (URL vo forme <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Produkt?$format=application\/json<\/u> ):<\/p>\n<pre><code>{\n\"odata.metadata\": \"http:\/\/server\/Config\/odata\/standard.odata\/$metadata#Catalog_Produkt\",\n\"value\": [{\n\"Ref_Key\": \"35d1f6e4-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAgAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000001\",\n\"Description\": \"Klimatiz\u00e1cia Mitsubishi\",\n\"Popis\": \"V\u00fdkon 2,5 kW, re\u017eimy chodu: teplo\/studen\u00fd\"\n},{\n\"Ref_Key\": \"35d1f6e5-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAwAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000002\",\n\"Description\": \"Klimatiz\u00e1cia Daikin\",\n\"Popis\": \"V\u00fdkon 3 kW, re\u017eimy chodu: teplo\/studen\u00fd\"\n}, \u2026\n<\/code><\/pre>\n<p><\/p>\n<h4>Extern\u00e9 zdroje \u00fadajov<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Sp\u00f4soby integr\u00e1cie s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1663b53846f3a6a8a03f386f1f6cd311.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nV niektor\u00fdch pr\u00edpadoch je v\u00fdmena \u00fadajov prostredn\u00edctvom <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000795.htm\">extern\u00fdch zdrojov \u00fadajov<\/a><\/noindex> m\u00f4\u017ee by\u0165 optim\u00e1lnym rie\u0161en\u00edm. Extern\u00e9 zdroje \u00fadajov s\u00fa aplika\u010dn\u00fd objekt konfigur\u00e1cie 1C, ktor\u00fd umo\u017e\u0148uje interakciu s akouko\u013evek datab\u00e1zou kompatibilnou s ODBC, a to ako na \u010d\u00edtanie, tak aj na z\u00e1pis. Extern\u00e9 zdroje \u00fadajov s\u00fa dostupn\u00e9 ako na Windows, tak aj na Linux.<\/p>\n<h4>Mechanizmus v\u00fdmeny \u00fadajov<\/h4>\n<p>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000269.htm\">Mechanizmus v\u00fdmeny \u00fadajov<\/a><\/noindex> je ur\u010den\u00fd pre vytv\u00e1ranie teritori\u00e1lne rozdelen\u00fdch syst\u00e9mov zalo\u017een\u00fdch na 1C:Enterprise a na organiz\u00e1ciu v\u00fdmeny \u00fadajov s in\u00fdmi informa\u010dn\u00fdmi syst\u00e9mami, ktor\u00e9 nie s\u00fa zalo\u017een\u00e9 na 1C:Enterprise.<\/p>\n<p>Tento mechanizmus sa akt\u00edvne vyu\u017e\u00edva pri implement\u00e1ci\u00e1ch 1C, pri\u010dom spektrum \u00faloh, ktor\u00e9 sa s jeho pomocou rie\u0161ia, je ve\u013emi \u0161irok\u00e9. Ide o v\u00fdmenu \u00fadajov medzi aplik\u00e1ciami 1C, ktor\u00e9 s\u00fa nain\u0161talovan\u00e9 v pobo\u010dk\u00e1ch organiz\u00e1cie, a o v\u00fdmenu medzi aplik\u00e1ciou 1C a webom e-shopu, ako aj o v\u00fdmenu \u00fadajov medzi serverovou aplik\u00e1ciou 1C a mobiln\u00fdm klientom (vytvoren\u00fdm pomocou mobilnej platformy 1C:Enterprise) a mnoho \u010fal\u0161\u00edch.<\/p>\n<p>Jedn\u00fdm z k\u013e\u00fa\u010dov\u00fdch pojmov v mechanizme v\u00fdmeny \u00fadajov je pl\u00e1n v\u00fdmeny. Pl\u00e1n v\u00fdmeny je osobitn\u00fd typ objektu aplika\u010dnej platformy 1C, ktor\u00fd ur\u010duje predov\u0161etk\u00fdm zlo\u017eenie \u00fadajov, ktor\u00e9 sa z\u00fa\u010dastnia v\u00fdmeny (ktor\u00e9 presne registre, dokumenty, faktur\u00e1cie at\u010f.). Pl\u00e1n v\u00fdmeny obsahuje aj inform\u00e1cie o \u00fa\u010dastn\u00edkoch v\u00fdmeny (tzv. uzloch v\u00fdmeny).<br \/>\nDruh\u00fdm komponentom mechanizmu v\u00fdmeny \u00fadajov je mechanizmus registr\u00e1cie zmien. Tento mechanizmus automaticky sleduje v syst\u00e9me zmeny \u00fadajov, ktor\u00e9 musia by\u0165 odovzdan\u00e9 kone\u010dn\u00fdm spotrebite\u013eom v r\u00e1mci pl\u00e1nu v\u00fdmeny. Pomocou tohto mechanizmu platforma sleduje zmeny, ku ktor\u00fdm do\u0161lo od poslednej synchroniz\u00e1cie, a umo\u017e\u0148uje minimalizova\u0165 objem \u00fadajov pren\u00e1\u0161an\u00fdch v r\u00e1mci \u010fal\u0161ej synchroniza\u010dnej rel\u00e1cie.<\/p>\n<p>V\u00fdm\u011bna dat prob\u00edh\u00e1 pomoc\u00ed XML zpr\u00e1v ur\u010dit\u00e9 struktury. Zpr\u00e1va obsahuje data, kter\u00e1 se zm\u011bnila od posledn\u00ed synchronizace s uzlem, a ur\u010dit\u00e9 servisn\u00ed informace. Struktura zpr\u00e1v podporuje \u010d\u00edslov\u00e1n\u00ed zpr\u00e1v a umo\u017e\u0148uje p\u0159ij\u00edm\u00e1n\u00ed potvrzen\u00ed od uzlu-p\u0159\u00edjemce o p\u0159ijet\u00ed zpr\u00e1v. Takov\u00e9 potvrzen\u00ed je obsa\u017eeno v ka\u017ed\u00e9 zpr\u00e1v\u011b p\u0159ich\u00e1zej\u00edc\u00ed od uzlu-p\u0159\u00edjemce ve form\u011b \u010d\u00edsla posledn\u00ed p\u0159ijat\u00e9 zpr\u00e1vy. \u010c\u00edslov\u00e1n\u00ed zpr\u00e1v umo\u017e\u0148uje platform\u011b pochopit, kter\u00e1 data byla ji\u017e \u00fasp\u011b\u0161n\u011b p\u0159ed\u00e1na na uzel-p\u0159\u00edjemce, a vyhnout se opakovan\u00e9mu p\u0159ed\u00e1v\u00e1n\u00ed, p\u0159i\u010dem\u017e se p\u0159ed\u00e1vaj\u00ed pouze data, kter\u00e1 se zm\u011bnila od p\u0159ijet\u00ed posledn\u00ed zpr\u00e1vy s potvrzen\u00edm o p\u0159ijat\u00fdch datech uzlem-p\u0159\u00edjemcem. P\u0159i takov\u00e9mto zp\u016fsobu pr\u00e1ce se zaji\u0161\u0165uje zaru\u010den\u00e1 doprava i p\u0159i nspolehliv\u00fdch p\u0159enosov\u00fdch kan\u00e1lech a ztr\u00e1t\u011b zpr\u00e1v.<\/p>\n<h4>Extern\u00e9 komponenty<\/h4>\n<p>\nV n\u011bkter\u00fdch p\u0159\u00edpadech, p\u0159i \u0159e\u0161en\u00ed integra\u010dn\u00edch \u00faloh, je t\u0159eba se vypo\u0159\u00e1dat se specifick\u00fdmi po\u017eadavky, nap\u0159\u00edklad protokoly interakce, form\u00e1ty dat, se kter\u00fdmi platforma 1C:Enterprise nep\u0159i\u010d\u00edt\u00e1. Pro takov\u00fd okruh \u00faloh je v platform\u011b zaji\u0161t\u011bna <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000545.htm\">technologie extern\u00edch komponent<\/a><\/noindex>, kter\u00e1 umo\u017e\u0148uje vytv\u00e1\u0159et dynamicky p\u0159ipojovan\u00e9 moduly, kter\u00e9 roz\u0161i\u0159uj\u00ed funk\u010dnost 1C:Enterprise. <\/p>\n<p>Typick\u00fdm p\u0159\u00edkladem \u00falohy s takov\u00fdmi po\u017eadavky m\u016f\u017ee b\u00fdt integrace aplika\u010dn\u00edho \u0159e\u0161en\u00ed 1C s obchodn\u00edm vybaven\u00edm, po\u010d\u00ednaje v\u00e1hami a kon\u010de pokladn\u00edmi p\u0159\u00edstroji a \u010dte\u010dkami \u010d\u00e1rov\u00fdch k\u00f3d\u016f. Extern\u00ed komponenty mohou b\u00fdt p\u0159ipojeny jak na stran\u011b serveru 1C:Enterprise, tak na klientsk\u00e9 stran\u011b (v\u010detn\u011b, v\u010detn\u011b webov\u00e9ho klienta a <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/vneshnie-komponenty-v-mobilnom-prilozhenii\/\">n\u00e1sleduj\u00edc\u00ed verze mobiln\u00ed platformy<\/a><\/noindex> 1C:Enterprise). Technologie extern\u00edch komponent p\u0159edpokl\u00e1d\u00e1 pom\u011brn\u011b jednoduch\u00e9 a srozumiteln\u00e9 programov\u00e9 (C++) rozhran\u00ed pro interakci komponenty s platformou 1C:Enterprise, kter\u00e9 mus\u00ed realizovat v\u00fdvoj\u00e1\u0159.<\/p>\n<p>Mo\u017enosti, kter\u00e9 se otev\u0159ou p\u0159i pou\u017eit\u00ed extern\u00edch komponent, jsou velmi \u0161irok\u00e9. Lze realizovat interakci podle specifick\u00e9ho protokolu v\u00fdm\u011bny dat s extern\u00edmi za\u0159\u00edzen\u00edmi a syst\u00e9my, implementovat specifick\u00e9 algoritmy zpracov\u00e1n\u00ed dat a form\u00e1t\u016f dat atd.<\/p>\n<h4>Zastaral\u00e9 integra\u010dn\u00e9 mechanizmy<\/h4>\n<p>\nNa platforme s\u00fa k dispoz\u00edcii integra\u010dn\u00e9 mechanizmy, ktor\u00fdch pou\u017eitie sa neodpor\u00fa\u010da v nov\u00fdch rie\u0161eniach; zostali z d\u00f4vodov sp\u00e4tnej kompatibility a pre pr\u00edpady, ke\u010f druh\u00e1 strana nem\u00f4\u017ee pracova\u0165 s modernej\u0161\u00edmi protokolmi. Jedn\u00fdm z nich je pr\u00e1ca s s\u00fabormi vo form\u00e1te DBF (podporovan\u00e9 vo vstavanom jazyku pomocou objektu XBase).<\/p>\n<p>\u010eal\u0161\u00ed zastaran\u00fd integra\u010dn\u00fd mechanizmus je pou\u017eitie technol\u00f3gie COM (dostupn\u00e9 iba na platforme Windows). Platforma 1C:Enterprise poskytuje dva sp\u00f4soby integr\u00e1cie pre Windows, ktor\u00e9 vyu\u017e\u00edvaj\u00fa technol\u00f3giu COM: Automation-server a Extern\u00e9 pripojenie. S\u00fa si ve\u013emi podobn\u00e9, ale jedn\u00fdm z podstatn\u00fdch rozdielov je to, \u017ee v pr\u00edpade Automation-servera sa sp\u00fa\u0161\u0165a plnohodnotn\u00e1 klientsk\u00e1 aplik\u00e1cia 1C:Enterprise 8, zatia\u013e \u010do v pr\u00edpade extern\u00e9ho pripojenia sa sp\u00fa\u0161\u0165a relat\u00edvne mal\u00fd vn\u00fatroprocesn\u00fd COM-server. To znamen\u00e1, \u017ee pri pr\u00e1ci cez Automation server je mo\u017en\u00e9 zapoji\u0165 funkcionalitu klientskej aplik\u00e1cie a vykon\u00e1va\u0165 akcie, ktor\u00e9 s\u00fa analogick\u00e9 interakt\u00edvnym akci\u00e1m pou\u017e\u00edvate\u013ea. Pri pou\u017eit\u00ed extern\u00e9ho pripojenia je mo\u017en\u00e9 vyu\u017ei\u0165 iba funkcie biznis logiky, a to bu\u010f na klientskej strane pripojenia, kde sa vytvor\u00ed vn\u00fatroprocesn\u00fd COM-server, alebo vyvol\u00e1va\u0165 biznis logiku na strane servera 1C:Enterprise.<\/p>\n<p>Technol\u00f3giu COM mo\u017eno tie\u017e pou\u017ei\u0165 na pr\u00edstup k extern\u00fdm syst\u00e9mom z k\u00f3du aplik\u00e1cie na platforme 1C:Enterprise. V tomto pr\u00edpade aplik\u00e1cia 1C funguje ako COM-klienta. Treba v\u0161ak pripomen\u00fa\u0165, \u017ee tieto mechanizmy bud\u00fa fungova\u0165 len v pr\u00edpade, \u017ee server 1C funguje v prostred\u00ed Windows.<\/p>\n<h3>Integra\u010dn\u00e9 mechanizmy implementovan\u00e9 v \u0161tandardn\u00fdch konfigur\u00e1ci\u00e1ch<\/h3>\n<p><\/p>\n<h4>Form\u00e1t EnterpriseData<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Sp\u00f4soby integr\u00e1cie s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/8930091e53309b9b808a719b747a6226.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nV niektor\u00fdch konfigur\u00e1ci\u00e1ch 1C (zoznam ni\u017e\u0161ie) bol na z\u00e1klade vy\u0161\u0161ie pop\u00edsan\u00e9ho platformov\u00e9ho mechanizmu v\u00fdmeny \u00fadajov implementovan\u00fd hotov\u00fd mechanizmus v\u00fdmeny \u00fadajov s extern\u00fdmi aplik\u00e1ciami, ktor\u00fd nevy\u017eaduje zmenu zdrojov\u00e9ho k\u00f3du konfigur\u00e1ci\u00ed (pr\u00edprava na v\u00fdmenu \u00fadajov sa vykon\u00e1va v nastaveniach aplikovan\u00fdch rie\u0161en\u00ed):<\/p>\n<ul>\n<li>\u201e1C:ERP Riadenie podniku 2.0\u201c <\/li>\n<li>\u201eKomplexn\u00e1 automatiz\u00e1cia 2\u201c <\/li>\n<li>\u201e\u00da\u010dtovn\u00edctvo podniku\u201c, ed\u00edcia 3.0 <\/li>\n<li>\u201e\u00da\u010dtovn\u00edctvo podniku KORP\u201c, ed\u00edcia 3.0 <\/li>\n<li>\u201eMaloobchod\u201c, ed\u00edcia 2.0 <\/li>\n<li>\"Z\u00e1kladn\u00e1 spr\u00e1va obchodovania\", ed\u00edcia 11 <\/li>\n<li>\"Spr\u00e1va obchodovania\", ed\u00edcia 11<\/li>\n<li>\"Mzdy a spr\u00e1va person\u00e1lu KORP\", ed\u00edcia 3<\/li>\n<\/ul>\n<p>\nNa v\u00fdmenu \u00fadajov sa pou\u017e\u00edva form\u00e1t <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_app\/enterprisedata\/\">EnterpriseData<\/a><\/noindex>, zalo\u017een\u00fd na XML. Form\u00e1t je obchodne orientovan\u00fd \u2013 op\u00edsan\u00e9 v \u0148om \u0161trukt\u00fary \u00fadajov zodpovedaj\u00fa obchodn\u00fdm entit\u00e1m (dokumentom a prvkom adres\u00e1rov), ktor\u00e9 s\u00fa predstaven\u00e9 v programoch 1C, napr\u00edklad: akt vykonan\u00fdch pr\u00e1c, pr\u00edjmov\u00fd pokladni\u010dn\u00fd doklad, kontrahent, nomenklat\u00fara a pod.<\/p>\n<p>V\u00fdmena \u00fadajov medzi aplik\u00e1ciou 1C a externou aplik\u00e1ciou m\u00f4\u017ee prebieha\u0165:<\/p>\n<ul>\n<li>cez vyhraden\u00fd s\u00faborov\u00fd adres\u00e1r <\/li>\n<li>cez FTP adres\u00e1r <\/li>\n<li>cez webov\u00fa slu\u017ebu, nasaden\u00fa na strane aplik\u00e1cie 1C. S\u00fabor s \u00fadajmi sa odosiela ako parameter webov\u00fdch met\u00f3d<\/li>\n<li>cez elektronick\u00fa po\u0161tu<\/li>\n<\/ul>\n<p>\nV pr\u00edpade v\u00fdmeny cez webov\u00fa slu\u017ebu extern\u00e1 aplik\u00e1cia iniciuje v\u00fdmenn\u00fd proces vyvolan\u00edm pr\u00edslu\u0161n\u00fdch webov\u00fdch met\u00f3d aplik\u00e1cie 1C. V ostatn\u00fdch pr\u00edpadoch inici\u00e1torom v\u00fdmeny bude aplik\u00e1cia 1C (umiestnen\u00edm s\u00faboru s \u00fadajmi do pr\u00edslu\u0161n\u00e9ho adres\u00e1ra alebo odoslan\u00edm s\u00faboru s \u00fadajmi na nakonfigurovan\u00fa emailov\u00fa adresu).<br \/>\nNa strane 1C sa tie\u017e nastavuje, s akou peri\u00f3dou bude doch\u00e1dza\u0165 k synchroniz\u00e1cii (pre varianty s v\u00fdmenou s\u00faborov cez adres\u00e1r a elektronick\u00fa po\u0161tu):<\/p>\n<ul>\n<li>pod\u013ea harmonogramu (s ur\u010denou peri\u00f3dou) <\/li>\n<li>manu\u00e1lne; pou\u017e\u00edvate\u013e bude musie\u0165 manu\u00e1lne spusti\u0165 synchroniz\u00e1ciu v\u017edy, ke\u010f to bude potrebova\u0165<\/li>\n<\/ul>\n<p><\/p>\n<h5>Potvrdenie spr\u00e1v<\/h5>\n<p>\nAplik\u00e1cie 1C ved\u00fa evidenciu odoslan\u00fdch a prijat\u00fdch spr\u00e1v synchroniz\u00e1cie a o\u010dak\u00e1vaj\u00fa to ist\u00e9 od extern\u00fdch aplik\u00e1ci\u00ed. To umo\u017e\u0148uje zapoji\u0165 mechanizmus \u010d\u00edslovania spr\u00e1v, op\u00edsan\u00fd vy\u0161\u0161ie v sekcii \"Mechanizmus v\u00fdmeny \u00fadajov\".<\/p>\n<p>Aplik\u00e1cie 1C po\u010das synchroniz\u00e1cie odosielaj\u00fa iba inform\u00e1cie o zmen\u00e1ch, ktor\u00e9 nastali v obchodn\u00fdch entit\u00e1ch od poslednej synchroniz\u00e1cie (aby sa minimalizoval objem odosielan\u00fdch inform\u00e1ci\u00ed). Pri prvej synchroniz\u00e1cii aplik\u00e1cia 1C exportuje v\u0161etky obchodn\u00e9 entity (napr\u00edklad polo\u017eky evidencie tovaru) vo form\u00e1te EnterpriseData do XML s\u00faboru (ke\u010f\u017ee v\u0161etky s\u00fa \u201enov\u00e9\u201c pre extern\u00fa aplik\u00e1ciu). Extern\u00e1 aplik\u00e1cia mus\u00ed spracova\u0165 inform\u00e1cie z prijat\u00e9ho XML s\u00faboru od 1C a pri nasleduj\u00facej synchroniz\u00e1cii umiestni\u0165 do s\u00faboru odosielan\u00e9ho do 1C, v \u0161peci\u00e1lnej sekcii XML, inform\u00e1ciu, \u017ee spr\u00e1va od 1C s ur\u010dit\u00fdm \u010d\u00edslom bola \u00faspe\u0161ne prijat\u00e1. Potvrdenie je pre aplik\u00e1ciu 1C sign\u00e1lom, \u017ee v\u0161etky obchodn\u00e9 entity boli \u00faspe\u0161ne spracovan\u00e9 externou aplik\u00e1ciou a inform\u00e1cie o nich u\u017e nie je potrebn\u00e9 odosiela\u0165. Okrem potvrdenia m\u00f4\u017ee XML s\u00fabor od externej aplik\u00e1cie obsahova\u0165 aj \u00fadaje na synchroniz\u00e1ciu zo strany aplik\u00e1cie (napr\u00edklad dokumenty o predaji tovaru a slu\u017eieb).<\/p>\n<p>Po prijat\u00ed potvrdenia aplik\u00e1cia 1C ozna\u010d\u00ed v\u0161etky zmeny, odoslan\u00e9 v predch\u00e1dzaj\u00facej spr\u00e1ve, ako \u00faspe\u0161ne synchronizovan\u00e9. Iba nesynchronizovan\u00e9 zmeny v obchodn\u00fdch entit\u00e1ch (vytv\u00e1ranie nov\u00fdch ent\u00edt, zmeny a odstra\u0148ovanie existuj\u00facich) bud\u00fa odoslan\u00e9 do externej aplik\u00e1cie pri nasleduj\u00facej synchroniz\u00e1cii.<\/p>\n<p><img decoding=\"async\" alt=\"Sp\u00f4soby integr\u00e1cie s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/b0d5509a53909e38886a15c2e03e7131.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPri prenose \u00fadajov z externej aplik\u00e1cie do aplik\u00e1cie 1C sa situ\u00e1cia zmen\u00ed na opa\u010dn\u00fa. Extern\u00e1 aplik\u00e1cia mus\u00ed spr\u00e1vne vyplni\u0165 sekciu potvrdenia v XML s\u00fabore a vlo\u017ei\u0165 obchodn\u00e9 \u00fadaje na synchroniz\u00e1ciu z jej strany vo form\u00e1te EnterpriseData.<\/p>\n<p><img decoding=\"async\" alt=\"Sp\u00f4soby integr\u00e1cie s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/d34b96efb7591770133b363b369c0019.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h5>Zjednodu\u0161en\u00e1 v\u00fdmena \u00fadajov bez potvrdzovania<\/h5>\n<p>\nPre pr\u00edpady jednoduchej integr\u00e1cie, ke\u010f sta\u010d\u00ed iba odosiela\u0165 inform\u00e1cie z externej aplik\u00e1cie do aplik\u00e1cie 1C a sp\u00e4tn\u00fd prenos \u00fadajov z aplik\u00e1cie 1C do externej aplik\u00e1cie nie je potrebn\u00fd (napr\u00edklad integr\u00e1cia online obchodu, ktor\u00fd odosiela inform\u00e1cie o predaji do \u201e1C:\u00da\u010dtovn\u00edctvo\u201c), existuje zjednodu\u0161en\u00e1 verzia pr\u00e1ce prostredn\u00edctvom webovej slu\u017eby (bez potvrdzovania), ktor\u00e1 nevy\u017eaduje nastavenia na strane aplik\u00e1cie 1C.<\/p>\n<h4>\u0160pecializovan\u00e9 integra\u010dn\u00e9 rie\u0161enia<\/h4>\n<p>\nExistuje typov\u00e9 rie\u0161enie \u201e1C:Konverzia d\u00e1t\u201c, ktor\u00e9 vyu\u017e\u00edva mechanismy platformy na konverziu a v\u00fdmenu \u00fadajov medzi typov\u00fdmi konfigur\u00e1ciami 1C, ale m\u00f4\u017ee by\u0165 tie\u017e pou\u017eit\u00e9 na integr\u00e1ciu s extern\u00fdmi aplik\u00e1ciami.<\/p>\n<h5>Integr\u00e1cia s bankov\u00fdmi rie\u0161eniami<\/h5>\n<p>\n\u0160tandard <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/100\/index.htm\">\u201eKlient banka\u201c<\/a><\/noindex>, vyvinut\u00e9 odborn\u00edkmi 1C pred viac ako 10 rokmi, sa vlastne stalo \u0161tandardom priemyslu v Rusku. Nasledovn\u00fdm krokom v tomto smere je technol\u00f3gia <noindex><a rel=\"nofollow\" href=\"http:\/\/directbank.1c.ru\/\">DirectBank<\/a><\/noindex>, ktor\u00e1 umo\u017e\u0148uje odosiela\u0165 platobn\u00e9 dokumenty do banky a prij\u00edma\u0165 v\u00fdpisy z banky priamo z programov syst\u00e9mu \u201e1C:Podnikanie\u201c stla\u010den\u00edm jedn\u00e9ho tla\u010didla v programe \u201e1C\u201c; v tomto pr\u00edpade nie je potrebn\u00e1 in\u0161tal\u00e1cia a spustenie \u010fal\u0161\u00edch programov na klientskom po\u010d\u00edta\u010di. <\/p>\n<p>Existuje tie\u017e <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/109\/\">\u0161tandard na v\u00fdmenu \u00fadajov v mzdov\u00fdch projektoch<\/a><\/noindex>.<\/p>\n<h5>In\u00e9<\/h5>\n<p>\nZasl\u00fa\u017eia si zmienku <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/131\/\">protokol v\u00fdmeny medzi syst\u00e9mom 1C:Podnikanie a webom<\/a><\/noindex>, \u0161tandard v\u00fdmeny obchodn\u00fdmi inform\u00e1ciami <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/90\/\">CommerceML<\/a><\/noindex> (vyvinut\u00fd spolo\u010dne s Microsoftom, Intelom, Price.ru a \u010fal\u0161\u00edmi spolo\u010dnos\u0165ami), <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/111\/\">\u0161tandard v\u00fdmeny \u00fadajov o oper\u00e1ci\u00e1ch akvizi\u010dn\u00fdch slu\u017eieb<\/a><\/noindex>.<br \/>\n<br \/>Zdroj: <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.5 - 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\/sk\/blog\/administrirovanie\/sposoby-integratsii-s-1s\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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\/sk\/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\udd47Sp\u00f4soby integr\u00e1cie s 1C | ProHoster","description":"Ak\u00e9 najd\u00f4le\u017eitej\u0161ie po\u017eiadavky s\u00fa kladen\u00e9 na biznis aplik\u00e1cie?","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/sposoby-integratsii-s-1s","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\/sk\/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\/sk\/wp-json\/wp\/v2\/posts\/36968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=36968"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/36968\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/27703"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=36968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=36968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=36968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}