{"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\/cs\/blog\/administrirovanie\/sposoby-integratsii-s-1s","title":{"rendered":"Zp\u016fsoby integrace s 1C","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Jak\u00e9 jsou hlavn\u00ed po\u017eadavky na podnikov\u00e9 aplikace? Mezi nejd\u016fle\u017eit\u011bj\u0161\u00ed pat\u0159\u00ed n\u00e1sleduj\u00edc\u00ed \u00fakoly:<\/p>\n<ul>\n<li>Snadnost zm\u011bny\/adaptace logiky fungov\u00e1n\u00ed aplikace na m\u011bn\u00edc\u00ed se obchodn\u00ed \u00fakoly.<\/li>\n<li>Snadnost integrace s jin\u00fdmi aplikacemi.<\/li>\n<\/ul>\n<p>\nJak je v 1C \u0159e\u0161en prvn\u00ed \u00fakol, bylo stru\u010dn\u011b pops\u00e1no v sekci \"Kustomizace a podpora\" <noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1c\/blog\/267321\/\">tohoto \u010dl\u00e1nku<\/a><\/noindex>; k tomuto zaj\u00edmav\u00e9mu t\u00e9matu se je\u0161t\u011b vr\u00e1t\u00edme v jednom z budouc\u00edch \u010dl\u00e1nk\u016f. Dnes se ale zam\u011b\u0159\u00edme na druh\u00fd \u00fakol, a to integraci.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Integrace \u00fakol\u016f<\/h3>\n<p>\nIntegrace \u00fakol\u016f m\u016f\u017ee m\u00edt r\u016fznou podobu. Pro n\u011bkter\u00e9 \u00fakoly sta\u010d\u00ed jednoduch\u00e1 interaktivn\u00ed v\u00fdm\u011bna dat \u2013 nap\u0159\u00edklad pro zas\u00edl\u00e1n\u00ed seznamu zam\u011bstnanc\u016f bance k vystaven\u00ed plastov\u00fdch karet na mzdy. Pro slo\u017eit\u011bj\u0161\u00ed \u00fakoly m\u016f\u017ee b\u00fdt nezbytn\u00e1 pln\u011b automatizovan\u00e1 v\u00fdm\u011bna dat, mo\u017en\u00e1 s vyu\u017eit\u00edm obchodn\u00ed logiky extern\u00edho syst\u00e9mu. Existuj\u00ed tak\u00e9 specializovan\u00e9 \u00fakoly, jako je integrace s extern\u00edm vybaven\u00edm (nap\u0159\u00edklad obchodn\u00ed za\u0159\u00edzen\u00ed, mobiln\u00ed skenery atd.) nebo s d\u011bdi\u010dn\u00fdmi nebo \u00fazce specializovan\u00fdmi syst\u00e9my (nap\u0159\u00edklad syst\u00e9my pro rozpozn\u00e1v\u00e1n\u00ed RFID tag\u016f). Je z\u00e1sadn\u00ed pro ka\u017ed\u00fd \u00fakol vybrat nejvhodn\u011bj\u0161\u00ed mechanismus integrace.<\/p>\n<h3>Mo\u017enosti integrace s 1C<\/h3>\n<p>\nExistuj\u00ed r\u016fzn\u00e9 p\u0159\u00edstupy k realizaci integrace s aplikacemi 1C, kter\u00fd z nich zvolit \u2013 z\u00e1vis\u00ed na po\u017eadavc\u00edch \u00fakolu.<\/p>\n<ol>\n<li>Realizace zalo\u017een\u00e1 na <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000581.htm\">mechanismech integrace<\/a><\/noindex>, kter\u00e9 poskytuje platforma, vlastn\u00edm specializovan\u00e9m API na stran\u011b aplikace 1C (nap\u0159\u00edklad souboru Web- nebo HTTP slu\u017eeb, kter\u00e9 budou vyvol\u00e1vat extern\u00ed aplikace pro v\u00fdm\u011bnu dat s aplikac\u00ed 1C). V\u00fdhodou tohoto p\u0159\u00edstupu je odolnost API v\u016f\u010di zm\u011bn\u00e1m realizace na stran\u011b aplikace 1C. Specifikem p\u0159\u00edstupu je, \u017ee je t\u0159eba m\u011bnit zdrojov\u00fd k\u00f3d typov\u00e9ho \u0159e\u0161en\u00ed 1C, co\u017e m\u016f\u017ee potenci\u00e1ln\u011b vy\u017eadovat \u00fasil\u00ed p\u0159i slu\u010dov\u00e1n\u00ed zdrojov\u00fdch k\u00f3d\u016f p\u0159i p\u0159echodu na novou verzi konfigurace. V tomto p\u0159\u00edpad\u011b m\u016f\u017ee pomoci nov\u00e1 pokrokov\u00e1 funk\u010dnost \u2013 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000883.htm\">roz\u0161\u00ed\u0159en\u00ed konfigurace<\/a><\/noindex>. Roz\u0161\u00ed\u0159en\u00ed jsou v podstat\u011b mechanismem plugin\u016f, kter\u00fd umo\u017e\u0148uje vytv\u00e1\u0159en\u00ed dopl\u0148k\u016f aplikac\u00ed, ani\u017e by bylo nutn\u00e9 m\u011bnit samotn\u00e9 aplikace. Vy\u010dlen\u011bn\u00ed integra\u010dn\u00edho API do roz\u0161\u00ed\u0159en\u00ed konfigurace umo\u017en\u00ed vyhnout se komplikac\u00edm p\u0159i slou\u010den\u00ed konfigurac\u00ed b\u011bhem p\u0159echodu na novou verzi standardn\u00edho \u0159e\u0161en\u00ed.\n<\/li>\n<li>Pou\u017e\u00edv\u00e1n\u00ed integra\u010dn\u00edch mechanism\u016f platformy, kter\u00e9 poskytuj\u00ed extern\u00ed p\u0159\u00edstup k objektov\u00e9mu modelu aplikace a nevy\u017eaduj\u00ed \u00fapravy aplikace nebo vytv\u00e1\u0159en\u00ed roz\u0161\u00ed\u0159en\u00ed. V\u00fdhodou tohoto p\u0159\u00edstupu je, \u017ee nen\u00ed nutn\u00e9 m\u011bnit aplikaci 1C. Nev\u00fdhodou je, \u017ee pokud byla aplikace 1C upravena, mohou b\u00fdt vy\u017eadov\u00e1ny \u00fapravy v integrovan\u00e9 aplikaci. P\u0159\u00edklad tohoto p\u0159\u00edstupu \u2013 pou\u017eit\u00ed integra\u010dn\u00edho protokolu OData, implementovan\u00e9ho na stran\u011b platformy 1C:Enterprise (v\u00edce o n\u011bm n\u00ed\u017ee).\n<\/li>\n<li>Pou\u017e\u00edv\u00e1n\u00ed hotov\u00fdch aplikativn\u00edch protokol\u016f, realizovan\u00fdch v typov\u00fdch \u0159e\u0161en\u00edch 1C. Mnoh\u00e9 typov\u00e9 \u0159e\u0161en\u00ed od 1C a partner\u016f implementuj\u00ed na z\u00e1klad\u011b integra\u010dn\u00edch mechanism\u016f poskytovan\u00fdch platformou sv\u00e9 vlastn\u00ed aplikativn\u00ed protokoly, zam\u011b\u0159en\u00e9 na konkr\u00e9tn\u00ed \u00fakoly. P\u0159i pou\u017e\u00edv\u00e1n\u00ed t\u011bchto mechanism\u016f nen\u00ed nutn\u00e9 ps\u00e1t k\u00f3d na stran\u011b aplikace 1C, proto\u017ee vyu\u017e\u00edv\u00e1me standardn\u00ed mo\u017enosti aplikativn\u00edho \u0159e\u0161en\u00ed. Na stran\u011b aplikace 1C je t\u0159eba prov\u00e9st pouze ur\u010dit\u00e9 nastaven\u00ed.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Integra\u010dn\u00ed mechanismy na platform\u011b 1C:Enterprise<\/h3>\n<p><\/p>\n<h4>Import\/export soubor\u016f<\/h4>\n<p>\nP\u0159edstavme si, \u017ee m\u00e1me \u00fakol obousm\u011brn\u00e9 v\u00fdm\u011bny dat mezi aplikac\u00ed 1C a libovolnou aplikac\u00ed. Nap\u0159\u00edklad pot\u0159ebujeme synchronizovat seznam produkt\u016f (adres\u00e1\u0159 Nomenklatura) mezi aplikac\u00ed 1C a libovolnou aplikac\u00ed.<\/p>\n<p><img decoding=\"async\" alt=\"Zp\u016fsoby integrace s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/9678f09dfcf7f70de100ed74ada6019c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPro vy\u0159e\u0161en\u00ed takov\u00e9ho \u00fakolu lze napsat roz\u0161\u00ed\u0159en\u00ed, kter\u00e9 exportuje adres\u00e1\u0159 Nomenklatura do souboru ur\u010dit\u00e9ho form\u00e1tu (textov\u00fd, XML, JSON, \u2026) a um\u00ed tento form\u00e1t \u010d\u00edst. <\/p>\n<p>Na platform\u011b je implementov\u00e1n mechanismus serializace aplikativn\u00edch objekt\u016f do XML jak p\u0159\u00edmo, pomoc\u00ed metod glob\u00e1ln\u00edho kontextu ZapsatXML\/\u010c\u00edstXML, tak i s pomoc\u00ed pomocn\u00e9ho objektu XDTO (XML Data Transfer Objects).<\/p>\n<p>Jak\u00fdkoli objekt v syst\u00e9mu 1C:Enterprise m\u016f\u017ee b\u00fdt serializov\u00e1n do XML reprezentace a naopak. <\/p>\n<p>Tato funkce vr\u00e1t\u00ed reprezentaci objektu ve form\u00e1tu XML:<\/p>\n<pre><code class=\"1c\">Funkce Objekt_V_XML(Objekt)\n    Z\u00e1znamXML = Nov\u00fd Z\u00e1znamXML();\n    Z\u00e1znamXML.Ustanovit\u0158et\u011bzec();\n    ZapsatXML(Z\u00e1znamXML, Objekt);\n    N\u00e1vrat Z\u00e1znamXML.Zav\u0159\u00edt();\nKonecFunkce\n<\/code><\/pre>\n<p>\ntakto bude vypadat export katalogu Nomenklatura do XML pomoc\u00ed XDTO:<\/p>\n<pre><code class=\"1c\">&amp;NaServeru\nProcedura ExportXMLNaServeru()\t\n\tNov\u00fdS\u00e9riov\u00fdXDTO  = S\u00e9riov\u00fdXDTO;\n\tNov\u00fdZ\u00e1znamXML = Nov\u00fd Z\u00e1znamXML();\n\tNov\u00fdZ\u00e1znamXML.Otev\u0159\u00edtSoubor(\"C:DataNomenklatura.xml\", \"UTF-8\");\n\t\n\tNov\u00fdZ\u00e1znamXML.ZapsatOzn\u00e1men\u00edXML();\n\tNov\u00fdZ\u00e1znamXML.ZapsatZa\u010d\u00e1tekElementu(\"KatalogNomenklatura\");\n\t\n\tV\u00fdb\u011br = Katalogy.Nomenklatura.Vybrat();\n\t\n\tKdy\u017e V\u00fdb\u011br.N\u00e1sleduj\u00edc\u00ed() Cyklus \n\t\tObjektNomenklatura = V\u00fdb\u011br.Z\u00edskatObjekt();\n\t\tNov\u00fdS\u00e9riov\u00fdXDTO.ZapsatXML(Nov\u00fdZ\u00e1znamXML, ObjektNomenklatura, \u00da\u010delTypuXML.Explicitn\u00ed);\n\tKonecCyklu;\n\t\n\tNov\u00fdZ\u00e1znamXML.ZapsatKonecElementu();\n\tNov\u00fdZ\u00e1znamXML.Zav\u0159\u00edt();\t\nKonecProcedury\n<\/code><\/pre>\n<p>\nJednoduchou \u00fapravou k\u00f3du exportujeme katalog do JSON. Produkty budou zaps\u00e1ny do pole; pro rozmanitost uvedeme anglickou variantu syntaxe:<\/p>\n<pre><code class=\"1c\">&amp;NaServeru\nProcedura ExportJSONNaServeru()\n\tNov\u00fdXDTOS\u00e9riov\u00fd  = XDTOSeriov\u00fd;\n\tNov\u00fdJSONZapisova\u010d = Nov\u00fd JSONZapisova\u010d();\n\tNov\u00fdJSONZapisova\u010d.Otev\u0159\u00edtSoubor(\"C:DataNomenklatura.json\", \"UTF-8\");\n\t\n\tNov\u00fdJSONZapisova\u010d.ZapsatZa\u010d\u00e1tekObjektu();\n\tNov\u00fdJSONZapisova\u010d.ZapsatN\u00e1zevVlastnosti(\"KatalogNomenklatura\");\n\tNov\u00fdJSONZapisova\u010d.ZapsatZa\u010d\u00e1tekPole();\n\t\n\tV\u00fdb\u011br = Katalogy.Nomenklatura.Vybrat();\t\n\t\n\tZat\u00edmco V\u00fdb\u011br.N\u00e1sleduj\u00edc\u00ed() D\u011blej \n\t\tObjektNomenklatura = V\u00fdb\u011br.Z\u00edskatObjekt();\n\t\t\n\t\tNov\u00fdJSONZapisova\u010d.ZapsatZa\u010d\u00e1tekObjektu();\n\t\t\n\t\tNov\u00fdJSONZapisova\u010d.ZapsatN\u00e1zevVlastnosti(\"Nomenklatura\");\n\t\tNov\u00fdXDTOS\u00e9riov\u00fd.ZapsatJSON(Nov\u00fdJSONZapisova\u010d, ObjektNomenklatura, P\u0159id\u011blen\u00edTypuXML.Implicitn\u00ed);\n\t\t\n\t\tNov\u00fdJSONZapisova\u010d.ZapsatKonecObjektu();\n\tKonecD\u011bj;\n\t\n\tNov\u00fdJSONZapisova\u010d.ZapsatKonecPole();\n\tNov\u00fdJSONZapisova\u010d.ZapsatKonecObjektu();\n\tNov\u00fdJSONZapisova\u010d.Zav\u0159\u00edt();\t\nKonecProcedury\n<\/code><\/pre>\n<p>\nNyn\u00ed zb\u00fdv\u00e1 pouze p\u0159edat data koncov\u00e9mu u\u017eivateli. Platforma 1C:Enterprise podporuje hlavn\u00ed internetov\u00e9 protokoly HTTP, FTP, POP3, SMTP, IMAP, v\u010detn\u011b jejich zabezpe\u010den\u00fdch verz\u00ed. Pro p\u0159enos dat lze tak\u00e9 pou\u017e\u00edt HTTP a\/nebo webov\u00e9 slu\u017eby.<\/p>\n<h4>HTTP a webov\u00e9 slu\u017eby<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Zp\u016fsoby integrace s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1d4797d9298f793e19ee637fd26473b2.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Aplikace 1C mohou implementovat sv\u00e9 HTTP a webov\u00e9 slu\u017eby, stejn\u011b jako volat HTTP a webov\u00e9 slu\u017eby realizovan\u00e9 t\u0159et\u00edmi aplikacemi. <\/p>\n<h4>REST rozhran\u00ed a protokol OData<\/h4>\n<p>\nOd verze 8.3.5 m\u016f\u017ee platforma 1C:Enterprise automaticky <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/avtomaticheskiy-rest-interfeys-prikladnykh-resheniy\/\">formovat REST rozhran\u00ed<\/a><\/noindex> pro cel\u00e9 aplika\u010dn\u00ed \u0159e\u0161en\u00ed. Jak\u00fdkoli konfigura\u010dn\u00ed objekt (katalog, dokument, registr informac\u00ed atd.) m\u016f\u017ee b\u00fdt zp\u0159\u00edstupn\u011bn pro z\u00edsk\u00e1n\u00ed a modifikaci dat p\u0159es REST rozhran\u00ed. Jako p\u0159\u00edstupov\u00fd protokol platforma pou\u017e\u00edv\u00e1 protokol <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Open_Data_Protocol\">OData<\/a><\/noindex> verze 3.0. Publikace slu\u017eeb OData se prov\u00e1d\u00ed z nab\u00eddky Konfigur\u00e1toru \u201eAdministrace -&gt; Publikace na webov\u00e9m serveru\u201c, p\u0159ep\u00edna\u010d \u201ePublikovat standardn\u00ed rozhran\u00ed OData\u201c mus\u00ed b\u00fdt ozna\u010den. Podporov\u00e1ny jsou form\u00e1ty atom\/XML a JSON. Jakmile je aplika\u010dn\u00ed \u0159e\u0161en\u00ed publikov\u00e1no na webov\u00e9m serveru, mohou k n\u011bmu extern\u00ed syst\u00e9my p\u0159istupovat prost\u0159ednictv\u00edm REST rozhran\u00ed pomoc\u00ed HTTP po\u017eadavk\u016f. Pro pr\u00e1ci s aplikac\u00ed 1C prost\u0159ednictv\u00edm protokolu OData nen\u00ed pot\u0159eba programov\u00e1n\u00ed na stran\u011b 1C.<\/p>\n<p>Tak\u017ee, URL ve form\u00e1tu <u>http:\/\/\/\/odata\/standard.odata\/Catalog_\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430<\/u> n\u00e1m vr\u00e1t\u00ed obsah katalogu Nomenklatura ve form\u00e1tu XML \u2014 kolekci prvk\u016f entry (hlavi\u010dka zpr\u00e1vy byla vynech\u00e1na kv\u016fli stru\u010dnosti):<\/p>\n<pre><code class=\"xml\">http:\/\/server\/Config\/odata\/standard.odata\/Catalog_\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430(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\tKlima Mitsubishi\n\t\t\tV\u00fdkon 2,5 kW, re\u017eimy provozu: topen\u00ed\/chlazen\u00ed\n\t\t\n\t\n\n\n\thttp:\/\/server\/Config\/odata\/standard.odata\/Catalog_\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430(guid'35d1f6e5-289b-11e6-8ba4-e03f49b16074')\n\t\n...\n<\/code><\/pre>\n<p>\nP\u0159id\u00e1n\u00edm \u0159et\u011bzce \u201e?$format=application\/json\u201c k URL z\u00edsk\u00e1me obsah katalogu Nomenklatura ve form\u00e1tu JSON (URL ve form\u00e1tu <u>http:\/\/\/\/odata\/standard.odata\/Catalog_\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430?$format=application\/json<\/u> ):<\/p>\n<pre><code>{\n\"odata.metadata\": \"http:\/\/server\/Config\/odata\/standard.odata\/$metadata#Catalog_\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430\",\n\"value\": [{\n\"Ref_Key\": \"35d1f6e4-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAgAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000001\",\n\"Description\": \"Klima Mitsubishi\",\n\"\u041e\u043f\u0438\u0441\u0430\u043d\u0438\u0435\": \"V\u00fdkon 2,5 kW, re\u017eimy provozu: topen\u00ed\/chlazen\u00ed\"\n},{\n\"Ref_Key\": \"35d1f6e5-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAwAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000002\",\n\"Description\": \"Klima Daikin\",\n\"\u041e\u043f\u0438\u0441\u0430\u043d\u0438\u0435\": \"V\u00fdkon 3 kW, re\u017eimy provozu: topen\u00ed\/chlazen\u00ed\"\n}, \u2026\n<\/code><\/pre>\n<p><\/p>\n<h4>Extern\u00ed zdroje dat<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Zp\u016fsoby integrace s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1663b53846f3a6a8a03f386f1f6cd311.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nV n\u011bkter\u00fdch p\u0159\u00edpadech doch\u00e1z\u00ed k v\u00fdm\u011bn\u011b dat prost\u0159ednictv\u00edm <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000795.htm\">extern\u00edch zdroj\u016f dat<\/a><\/noindex> m\u016f\u017ee se uk\u00e1zat jako optim\u00e1ln\u00ed \u0159e\u0161en\u00ed. Vn\u011bj\u0161\u00ed datov\u00e9 zdroje jsou aplika\u010dn\u00edm objektem konfigurace 1C, kter\u00fd umo\u017e\u0148uje interakci s jakoukoli datab\u00e1z\u00ed kompatibiln\u00ed s ODBC jak pro \u010dten\u00ed, tak pro z\u00e1pis. Vn\u011bj\u0161\u00ed datov\u00e9 zdroje jsou dostupn\u00e9 jak ve Windows, tak v Linuxu.<\/p>\n<h4>Mechanismus v\u00fdm\u011bny dat<\/h4>\n<p>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000269.htm\">Mechanismus v\u00fdm\u011bny dat<\/a><\/noindex> je ur\u010den jak pro vytv\u00e1\u0159en\u00ed teritori\u00e1ln\u011b distribuovan\u00fdch syst\u00e9m\u016f na b\u00e1zi 1C:Enterprise, tak pro organizaci v\u00fdm\u011bny dat s jin\u00fdmi informa\u010dn\u00edmi syst\u00e9my, kter\u00e9 nejsou zalo\u017eeny na 1C:Enterprise.<\/p>\n<p>Tento mechanismus se aktivn\u011b vyu\u017e\u00edv\u00e1 p\u0159i implementac\u00edch 1C, a rozsah \u00fakol\u016f, kter\u00e9 se s jeho pomoc\u00ed \u0159e\u0161\u00ed, je velmi \u0161irok\u00fd. To zahrnuje v\u00fdm\u011bnu dat mezi aplikacemi 1C, nainstalovan\u00fdmi v pobo\u010dk\u00e1ch organizace, a v\u00fdm\u011bnu mezi aplikac\u00ed 1C a webovou str\u00e1nkou internetov\u00e9ho obchodu, a v\u00fdm\u011bnu dat mezi serverovou aplikac\u00ed 1C a mobiln\u00edm klientem (vytvo\u0159en\u00fdm pomoc\u00ed mobiln\u00ed platformy 1C:Enterprise), a mnohem v\u00edc.<\/p>\n<p>Jedn\u00edm z kl\u00ed\u010dov\u00fdch pojm\u016f v mechanismu v\u00fdm\u011bny dat je pl\u00e1n v\u00fdm\u011bny. Pl\u00e1n v\u00fdm\u011bny je speci\u00e1ln\u00ed typ aplika\u010dn\u00edho objektu platformy 1C, kter\u00fd definuje zejm\u00e9na slo\u017een\u00ed dat, kter\u00e1 se budou pod\u00edlet na v\u00fdm\u011bn\u011b (jak\u00e9 konkr\u00e9tn\u00ed referen\u010dn\u00ed informace, dokumenty, registry atd.). Pl\u00e1n v\u00fdm\u011bny rovn\u011b\u017e obsahuje informace o \u00fa\u010dastn\u00edc\u00edch v\u00fdm\u011bny (tzv. uzlech v\u00fdm\u011bny).<br \/>\nDruh\u00e1 sou\u010d\u00e1st mechanismu v\u00fdm\u011bny dat je mechanismus registrace zm\u011bn. Tento mechanismus automaticky sleduje v syst\u00e9mu zm\u011bny dat, kter\u00e9 maj\u00ed b\u00fdt p\u0159ed\u00e1ny kone\u010dn\u00fdm u\u017eivatel\u016fm v r\u00e1mci pl\u00e1nu v\u00fdm\u011bny. S pomoc\u00ed tohoto mechanismu platforma sleduje zm\u011bny, kter\u00e9 nastaly od posledn\u00ed synchronizace, a umo\u017e\u0148uje minimalizovat objem dat, kter\u00e1 jsou p\u0159ed\u00e1v\u00e1na v r\u00e1mci dal\u0161\u00edho synchroniza\u010dn\u00edho sezen\u00ed.<\/p>\n<p>V\u00fdmena \u00fadajov prebieha prostredn\u00edctvom XML spr\u00e1v ur\u010ditej \u0161trukt\u00fary. Spr\u00e1va obsahuje \u00fadaje, ktor\u00e9 sa zmenili od poslednej synchroniz\u00e1cie s uzlom, a nejak\u00e9 servisn\u00e9 inform\u00e1cie. \u0160trukt\u00fara spr\u00e1v podporuje \u010d\u00edslovanie spr\u00e1v a umo\u017e\u0148uje z\u00edska\u0165 potvrdenia od uzla-prij\u00edmate\u013ea o prijat\u00ed spr\u00e1v. Tak\u00e9to potvrdenie sa nach\u00e1dza v ka\u017edej spr\u00e1ve, ktor\u00e1 prich\u00e1dza od uzla-prij\u00edmate\u013ea, vo forme \u010d\u00edsla poslednej prijatej spr\u00e1vy. \u010c\u00edslovanie spr\u00e1v umo\u017e\u0148uje platforme pochopi\u0165, ak\u00e9 \u00fadaje u\u017e boli \u00faspe\u0161ne prenesen\u00e9 na uzol-prij\u00edmate\u013e a vyhn\u00fa\u0165 sa op\u00e4tovn\u00e9mu prenosu, pri\u010dom sa pren\u00e1\u0161aj\u00fa len \u00fadaje, ktor\u00e9 sa zmenili od prijatia poslednej spr\u00e1vy s potvrden\u00edm o prijat\u00fdch \u00fadajoch uzlom-prij\u00edmate\u013eom. Pri takejto sch\u00e9me pr\u00e1ce je zabezpe\u010den\u00e1 garantovan\u00e1 dod\u00e1vka aj pri nespo\u013eahliv\u00fdch komunika\u010dn\u00fdch kan\u00e1loch a strate spr\u00e1v.<\/p>\n<h4>Extern\u00e9 komponenty<\/h4>\n<p>\nV niektor\u00fdch pr\u00edpadoch, pri rie\u0161en\u00ed \u00faloh integr\u00e1cie, sa mus\u00edme stret\u00e1va\u0165 so \u0161pecifick\u00fdmi po\u017eiadavkami, ako napr\u00edklad protokoly interakcie, form\u00e1ty \u00fadajov, s ktor\u00fdmi platforma 1C:Enterprise nepo\u010d\u00edtala. Pre tak\u00fdto okruh \u00faloh je v platforme predpokladan\u00e1 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000545.htm\">technol\u00f3gia extern\u00fdch komponentov<\/a><\/noindex>, ktor\u00e1 umo\u017e\u0148uje vytv\u00e1ra\u0165 dynamicky pripojite\u013en\u00e9 moduly, ktor\u00e9 roz\u0161iruj\u00fa funk\u010dnos\u0165 1C:Enterprise. <\/p>\n<p>Typick\u00fdm pr\u00edkladom \u00falohy s podobn\u00fdmi po\u017eiadavkami m\u00f4\u017ee by\u0165 integr\u00e1cia aplik\u00e1cie 1C s obchodn\u00fdm zariaden\u00edm, po\u010d\u00ednaj\u00fac v\u00e1hami a kon\u010diac pokladni\u010dn\u00fdmi zariadeniami a skenermi \u010diarov\u00fdch k\u00f3dov. Extern\u00e9 komponenty m\u00f4\u017eu by\u0165 pripojen\u00e9 tak na strane servera 1C:Enterprise, ako aj na klientskej strane (vr\u00e1tane webov\u00e9ho klienta, ako aj <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/vneshnie-komponenty-v-mobilnom-prilozhenii\/\">nasleduj\u00facej verzie mobilnej platformy<\/a><\/noindex> 1C:Enterprise). Technol\u00f3gia extern\u00fdch komponentov predpoklad\u00e1 dostato\u010dne jednoduch\u00e9 a zrozumite\u013en\u00e9 programov\u00e9 (C++) rozhranie na interakciu komponentov s platformou 1C:Enterprise, ktor\u00e9 mus\u00ed implementova\u0165 v\u00fdvoj\u00e1r.<\/p>\n<p>Mo\u017enosti, ktor\u00e9 sa otv\u00e1raj\u00fa pri pou\u017e\u00edvan\u00ed extern\u00fdch komponentov, s\u00fa ve\u013emi \u0161irok\u00e9. M\u00f4\u017eeme realizova\u0165 interakciu pod\u013ea \u0161pecifick\u00e9ho protokolu v\u00fdmeny \u00fadajov s extern\u00fdmi zariadeniami a syst\u00e9mami, integrova\u0165 \u0161pecifick\u00e9 algoritmy spracovania \u00fadajov a form\u00e1tov \u00fadajov at\u010f.<\/p>\n<h4>Zastaral\u00e9 integra\u010dn\u00ed mechanismy<\/h4>\n<p>\nNa platform\u011b jsou k dispozici integra\u010dn\u00ed mechanismy, kter\u00e9 se nedoporu\u010duje pou\u017e\u00edvat v nov\u00fdch \u0159e\u0161en\u00edch; byly ponech\u00e1ny z hlediska zp\u011btn\u00e9 kompatibility a tak\u00e9 pro p\u0159\u00edpad, \u017ee by druh\u00e1 strana nemohla pracovat s modern\u011bj\u0161\u00edmi protokoly. Jedn\u00edm z nich je pr\u00e1ce s soubory form\u00e1tu DBF (podporov\u00e1no ve vestav\u011bn\u00e9m jazyce pomoc\u00ed objektu XBase).<\/p>\n<p>Dal\u0161\u00edm zastaral\u00fdm integra\u010dn\u00edm mechanismem je pou\u017eit\u00ed technologie COM (dostupn\u00e9 pouze na platform\u011b Windows). Platforma 1C:Enterprise poskytuje dva zp\u016fsoby integrace pro Windows, kter\u00e9 vyu\u017e\u00edvaj\u00ed technologii COM: Automatiza\u010dn\u00ed server a Extern\u00ed p\u0159ipojen\u00ed. Tyto zp\u016fsoby jsou si velmi podobn\u00e9, ale jedn\u00edm z hlavn\u00edch rozd\u00edl\u016f je to, \u017ee v p\u0159\u00edpad\u011b Automatiza\u010dn\u00edho serveru se spust\u00ed plnohodnotn\u00e1 klientsk\u00e1 aplikace 1C:Enterprise 8, zat\u00edmco v p\u0159\u00edpad\u011b extern\u00edho p\u0159ipojen\u00ed se spust\u00ed relativn\u011b mal\u00fd intraprocesn\u00ed COM-server. To znamen\u00e1, \u017ee v p\u0159\u00edpad\u011b pr\u00e1ce p\u0159es Automatiza\u010dn\u00ed server lze vyu\u017e\u00edt funkcionalitu klientsk\u00e9 aplikace, prov\u00e1d\u011bt akce analogick\u00e9 interaktivn\u00edm akc\u00edm u\u017eivatele. P\u0159i pou\u017eit\u00ed extern\u00edho p\u0159ipojen\u00ed lze vyu\u017e\u00edvat pouze funkce obchodn\u00ed logiky, p\u0159i\u010dem\u017e je mo\u017en\u00e9 je prov\u00e1d\u011bt jak na klientsk\u00e9 stran\u011b p\u0159ipojen\u00ed, kde se vytv\u00e1\u0159\u00ed intraprocesn\u00ed COM-server, tak vyvol\u00e1vat obchodn\u00ed logiku na stran\u011b serveru 1C:Enterprise.<\/p>\n<p>Technologii COM lze tak\u00e9 pou\u017e\u00edt pro p\u0159\u00edstup k extern\u00edm syst\u00e9m\u016fm z k\u00f3du aplikace na platform\u011b 1C:Enterprise. V tomto p\u0159\u00edpad\u011b aplikace 1C funguje jako COM-klient. Je v\u0161ak t\u0159eba p\u0159ipomenout, \u017ee tyto mechanismy budou fungovat pouze tehdy, pokud server 1C b\u011b\u017e\u00ed v prost\u0159ed\u00ed Windows.<\/p>\n<h3>Integra\u010dn\u00ed mechanismy realizovan\u00e9 ve standardn\u00edch konfigurac\u00edch<\/h3>\n<p><\/p>\n<h4>Form\u00e1t EnterpriseData<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Zp\u016fsoby integrace s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/8930091e53309b9b808a719b747a6226.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nV \u0159ad\u011b konfigurac\u00ed 1C (seznam n\u00ed\u017ee) byl na z\u00e1klad\u011b v\u00fd\u0161e popsan\u00e9ho platformov\u00e9ho mechanismu v\u00fdm\u011bny dat realizov\u00e1n hotov\u00fd mechanismus pro v\u00fdm\u011bnu dat s extern\u00edmi aplikacemi, kter\u00fd nevy\u017eaduje zm\u011bnu zdrojov\u00e9ho k\u00f3du konfigurac\u00ed (p\u0159\u00edprava na v\u00fdm\u011bnu dat se prov\u00e1d\u00ed v nastaven\u00edch aplikovan\u00fdch \u0159e\u0161en\u00ed):<\/p>\n<ul>\n<li>\u201e1C:ERP \u0158\u00edzen\u00ed podniku 2.0\u201c <\/li>\n<li>\u201eKomplexn\u00ed automatizace 2\u201c <\/li>\n<li>\u201e\u00da\u010detnictv\u00ed podniku\u201c, edice 3.0 <\/li>\n<li>\u201e\u00da\u010detnictv\u00ed podniku KORP\u201c, edice 3.0 <\/li>\n<li>\u201eMaloobchod\u201c, edice 2.0 <\/li>\n<li>\u201eZ\u00e1kladn\u00ed \u0159\u00edzen\u00ed obchodov\u00e1n\u00ed\u201c, vyd\u00e1n\u00ed 11 <\/li>\n<li>\u201e\u0158\u00edzen\u00ed obchodov\u00e1n\u00ed\u201c, vyd\u00e1n\u00ed 11<\/li>\n<li>\u201eMzdov\u00e1 a person\u00e1ln\u00ed spr\u00e1va KORP\u201c, vyd\u00e1n\u00ed 3<\/li>\n<\/ul>\n<p>\nPro v\u00fdm\u011bnu dat se pou\u017e\u00edv\u00e1 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 orientov\u00e1n na podnik\u00e1n\u00ed \u2013 popsan\u00e9 struktury dat odpov\u00eddaj\u00ed obchodn\u00edm subjekt\u016fm (dokument\u016fm a polo\u017ek\u00e1m katalogu), kter\u00e9 jsou reprezentov\u00e1ny v programech 1C, nap\u0159\u00edklad: potvrzen\u00ed o proveden\u00ed prac\u00ed, p\u0159\u00edjmov\u00fd pokladn\u00ed doklad, kontragent, nomenklatura apod.<\/p>\n<p>V\u00fdm\u011bna dat mezi aplikac\u00ed 1C a t\u0159et\u00edmi aplikacemi m\u016f\u017ee prob\u00edhat:<\/p>\n<ul>\n<li>prost\u0159ednictv\u00edm vyhrazen\u00e9ho souborov\u00e9ho adres\u00e1\u0159e <\/li>\n<li>p\u0159es FTP adres\u00e1\u0159 <\/li>\n<li>p\u0159es webovou slu\u017ebu nasazenou na stran\u011b aplikace 1C. Soubor s daty se p\u0159ed\u00e1v\u00e1 jako parametr webov\u00fdch metod<\/li>\n<li>p\u0159es elektronickou po\u0161tu<\/li>\n<\/ul>\n<p>\nV p\u0159\u00edpad\u011b v\u00fdm\u011bny p\u0159es webovou slu\u017ebu bude t\u0159et\u00ed aplikace iniciovat datovou v\u00fdm\u011bnu vol\u00e1n\u00edm odpov\u00eddaj\u00edc\u00edch webov\u00fdch metod aplikace 1C. V ostatn\u00edch p\u0159\u00edpadech bude inici\u00e1torem sezen\u00ed v\u00fdm\u011bny aplikace 1C (vlo\u017een\u00edm souboru s daty do odpov\u00eddaj\u00edc\u00edho adres\u00e1\u0159e nebo odesl\u00e1n\u00edm souboru s daty na nastavenou e-mailovou adresu).<br \/>\nTak\u00e9 se na stran\u011b 1C nastav\u00ed, jak \u010dasto bude doch\u00e1zet k synchronizaci (pro varianty s v\u00fdm\u011bnou soubor\u016f prost\u0159ednictv\u00edm adres\u00e1\u0159e a elektronick\u00e9 po\u0161ty):<\/p>\n<ul>\n<li>podle pl\u00e1nu (s danou periodicitou) <\/li>\n<li>manu\u00e1ln\u011b; u\u017eivatel bude muset manu\u00e1ln\u011b spou\u0161t\u011bt synchronizaci poka\u017ed\u00e9, kdy\u017e to bude pot\u0159ebovat<\/li>\n<\/ul>\n<p><\/p>\n<h5>Potvrzov\u00e1n\u00ed zpr\u00e1v<\/h5>\n<p>\nAplikace 1C vedou evidenci odeslan\u00fdch a p\u0159ijat\u00fdch zpr\u00e1v synchronizace a o\u010dek\u00e1vaj\u00ed to sam\u00e9 od t\u0159et\u00edch aplikac\u00ed. To umo\u017e\u0148uje vyu\u017e\u00edt mechanismus \u010d\u00edslov\u00e1n\u00ed zpr\u00e1v, popsan\u00fd v\u00fd\u0161e v \u010d\u00e1sti \u201eMechanismus v\u00fdm\u011bny dat\u201c.<\/p>\n<p>Aplikace 1C b\u011bhem synchronizace p\u0159en\u00e1\u0161ej\u00ed pouze informace o zm\u011bn\u00e1ch, kter\u00e9 nastaly v obchodn\u00edch entit\u00e1ch od posledn\u00ed synchronizace (aby se minimalizoval objem p\u0159en\u00e1\u0161en\u00fdch informac\u00ed). P\u0159i prvn\u00ed synchronizaci aplikace 1C exportuje v\u0161echny obchodn\u00ed entity (nap\u0159\u00edklad polo\u017eky z katalogu zbo\u017e\u00ed) ve form\u00e1tu EnterpriseData do XML souboru (proto\u017ee v\u0161echny jsou pro extern\u00ed aplikaci \"nov\u00e9\"). Extern\u00ed aplikace mus\u00ed zpracovat informace z p\u0159ijat\u00e9ho XML souboru od 1C a p\u0159i n\u00e1sleduj\u00edc\u00ed synchronizaci um\u00edstit do souboru, odes\u00edlan\u00e9ho do 1C, ve speci\u00e1ln\u00ed sekci XML informaci, \u017ee zpr\u00e1va od 1C s ur\u010dit\u00e9m \u010d\u00edslem byla \u00fasp\u011b\u0161n\u011b p\u0159ijata. Potvrzovac\u00ed zpr\u00e1va je pro aplikaci 1C sign\u00e1lem, \u017ee v\u0161echny obchodn\u00ed entity byly \u00fasp\u011b\u0161n\u011b zpracov\u00e1ny extern\u00ed aplikac\u00ed a informace o nich ji\u017e nen\u00ed pot\u0159eba p\u0159en\u00e1\u0161et. Krom\u011b potvrzen\u00ed m\u016f\u017ee XML soubor od extern\u00ed aplikace tak\u00e9 obsahovat data pro synchronizaci ze strany aplikace (nap\u0159\u00edklad dokumenty realizace zbo\u017e\u00ed a slu\u017eeb).<\/p>\n<p>Po obdr\u017een\u00ed potvrzovac\u00ed zpr\u00e1vy aplikace 1C ozna\u010duje v\u0161echny zm\u011bny, kter\u00e9 byly zasl\u00e1ny v p\u0159edchoz\u00ed zpr\u00e1v\u011b, jako \u00fasp\u011b\u0161n\u011b synchronizovan\u00e9. Pouze nesynchronizovan\u00e9 zm\u011bny v obchodn\u00edch entit\u00e1ch (vytv\u00e1\u0159en\u00ed nov\u00fdch entit, zm\u011bny a maz\u00e1n\u00ed existuj\u00edc\u00edch) budou odesl\u00e1ny do extern\u00ed aplikace p\u0159i n\u00e1sleduj\u00edc\u00ed synchronizaci.<\/p>\n<p><img decoding=\"async\" alt=\"Zp\u016fsoby integrace s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/b0d5509a53909e38886a15c2e03e7131.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nP\u0159i p\u0159enosu dat z extern\u00ed aplikace do aplikace 1C se situace obrac\u00ed. Extern\u00ed aplikace mus\u00ed odpov\u00eddaj\u00edc\u00edm zp\u016fsobem vyplnit sekci potvrzen\u00ed v XML souboru a um\u00edstit obchodn\u00ed data pro synchronizaci ze sv\u00e9 strany ve form\u00e1tu EnterpriseData.<\/p>\n<p><img decoding=\"async\" alt=\"Zp\u016fsoby integrace s 1C\" src=\"\/wp-content\/uploads\/2019\/08\/d34b96efb7591770133b363b369c0019.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h5>Zjednodu\u0161en\u00e1 v\u00fdm\u011bna dat bez potvrzov\u00e1n\u00ed<\/h5>\n<p>\nPro p\u0159\u00edpady jednoduch\u00e9 integrace, kdy sta\u010d\u00ed pouze p\u0159ed\u00e1vat informace z extern\u00ed aplikace do aplikace 1C a nen\u00ed pot\u0159ebn\u00fd zp\u011btn\u00fd p\u0159enos dat z aplikace 1C do extern\u00ed aplikace (nap\u0159\u00edklad integrace online obchodu, kter\u00fd p\u0159ed\u00e1v\u00e1 informace o prodeji do \u201e1C:\u00da\u010detnictv\u00ed\u201c), existuje zjednodu\u0161en\u00e1 varianta pr\u00e1ce p\u0159es webovou slu\u017ebu (bez potvrzov\u00e1n\u00ed), kter\u00e1 nevy\u017eaduje nastaven\u00ed na stran\u011b aplikace 1C.<\/p>\n<h4>Specializovan\u00e1 integra\u010dn\u00ed \u0159e\u0161en\u00ed<\/h4>\n<p>\nExistuje standardn\u00ed \u0159e\u0161en\u00ed \u201e1C:Konverze dat\u201c, kter\u00e9 vyu\u017e\u00edv\u00e1 mechanismy platformy pro konverzi a v\u00fdm\u011bnu dat mezi standardn\u00edmi konfiguracemi 1C, ale m\u016f\u017ee b\u00fdt tak\u00e9 pou\u017eito pro integraci s extern\u00edmi aplikacemi.<\/p>\n<h5>Integrace s bankovn\u00edmi \u0159e\u0161en\u00edmi<\/h5>\n<p>\nStandard <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/100\/index.htm\">\u201eKlient banka\u201c<\/a><\/noindex>, vyvinut\u00fd specialisty 1C p\u0159ed v\u00edce ne\u017e 10 lety, se v podstat\u011b stal standardem odv\u011btv\u00ed v Rusku. Dal\u0161\u00edm krokem v tomto sm\u011bru je technologie <noindex><a rel=\"nofollow\" href=\"http:\/\/directbank.1c.ru\/\">DirectBank<\/a><\/noindex>, kter\u00e1 umo\u017e\u0148uje odes\u00edlat platebn\u00ed dokumenty do banky a z\u00edsk\u00e1vat v\u00fdpisy z banky p\u0159\u00edmo ze syst\u00e9mov\u00fdch program\u016f \u201e1C:Podnik\u00e1n\u00ed\u201c stisknut\u00edm jednoho tla\u010d\u00edtka v programu \u201e1C\u201c; p\u0159i\u010dem\u017e nen\u00ed nutn\u00e9 instalovat a spou\u0161t\u011bt dal\u0161\u00ed programy na klientsk\u00e9m po\u010d\u00edta\u010di. <\/p>\n<p>Existuje tak\u00e9 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/109\/\">standard pro v\u00fdm\u011bnu dat v projektov\u00fdch platebn\u00edch syst\u00e9mech<\/a><\/noindex>.<\/p>\n<h5>Ostatn\u00ed<\/h5>\n<p>\nZaslou\u017e\u00ed si zm\u00ednku <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/131\/\">protokol v\u00fdm\u011bny mezi syst\u00e9mem 1C:Podnik\u00e1n\u00ed a webovou str\u00e1nkou<\/a><\/noindex>, standard v\u00fdm\u011bny obchodn\u00edch informac\u00ed <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/90\/\">CommerceML<\/a><\/noindex> (vyvinut\u00fd ve spolupr\u00e1ci s Microsoftem, Intelem, Price.ru a dal\u0161\u00edmi spole\u010dnostmi), <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/111\/\">standard pro v\u00fdm\u011bnu dat o transakc\u00edch akceptace<\/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.3 - 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\/cs\/blog\/administrirovanie\/sposoby-integratsii-s-1s\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"cs_CZ\" \/>\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\/cs\/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\udd47Zp\u016fsoby integrace s 1C | ProHoster","description":"Jak\u00e9 jsou nejd\u016fle\u017eit\u011bj\u0161\u00ed po\u017eadavky kladen\u00e9 na obchodn\u00ed aplikace?","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/sposoby-integratsii-s-1s","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/36968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=36968"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/36968\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/27703"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=36968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=36968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=36968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}