{"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\/sq\/blog\/administrirovanie\/sposoby-integratsii-s-1s","title":{"rendered":"Metodat e integrimit me 1C","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Cilat jan\u00eb k\u00ebrkesat m\u00eb t\u00eb r\u00ebnd\u00ebsishme p\u00ebr aplikacionet biznesore? N\u00eb mesin e tyre jan\u00eb detyrat m\u00eb kryesore si m\u00eb posht\u00eb:<\/p>\n<ul>\n<li>Leht\u00ebsia e modifikimit\/adaptimit t\u00eb logjik\u00ebs s\u00eb pun\u00ebs s\u00eb aplikacionit p\u00ebr detyrat e ndryshueshme t\u00eb biznesit.<\/li>\n<li>Leht\u00ebsia e integrimit me aplikacione t\u00eb tjera.<\/li>\n<\/ul>\n<p>\nSi zgjidhet detyra e par\u00eb n\u00eb 1C, \u00ebsht\u00eb p\u00ebrshkruar shkurtimisht n\u00eb seksionin \"Kastomizimi dhe mb\u00ebshtetja\"; ne do t\u00eb kthehemi p\u00ebrs\u00ebri n\u00eb k\u00ebt\u00eb tem\u00eb interesante n\u00eb nj\u00eb nga artikujt e ardhsh\u00ebm. Sot do t\u00eb flasim p\u00ebr detyr\u00ebn e dyt\u00eb, at\u00eb t\u00eb integrimit. <noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1c\/blog\/267321\/\">ky artikull<\/a><\/noindex>Detyrat e integrimit<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Detyrat e integrimit mund t\u00eb jen\u00eb t\u00eb ndryshme. P\u00ebr disa detyra, mjafton nj\u00eb shk\u00ebmbim interaktiv t\u00eb t\u00eb dh\u00ebnave \u2013 p\u00ebr shembull, p\u00ebr t\u00eb d\u00ebrguar n\u00eb bank\u00eb list\u00ebn e punonj\u00ebsve p\u00ebr regjistrimin e kartave plastike p\u00ebr paga. P\u00ebr detyra m\u00eb komplekse, mund t\u00eb nevojitet nj\u00eb shk\u00ebmbim t\u00eb dh\u00ebnash t\u00eb automatizuar plot\u00ebsisht, ndoshta me thirrje n\u00eb logjik\u00ebn biznesore t\u00eb nj\u00eb sistemi t\u00eb jasht\u00ebm. Ka detyra me karakter t\u00eb specializuar, si integrimi me pajisje t\u00eb jashtme (p\u00ebr shembull, pajisjet tregtare, skaner\u00ebt mobil\u00eb, etj.) ose me sisteme t\u00eb trash\u00ebguara ose t\u00eb specializuara (p\u00ebr shembull, me sistemet e njohjes s\u00eb etiketave RFID). \u00cbsht\u00eb jasht\u00ebzakonisht e r\u00ebnd\u00ebsishme p\u00ebr \u00e7do detyr\u00eb t\u00eb zgjidhet mekanizmi m\u00eb i p\u00ebrshtatsh\u00ebm i integrimit.<\/h3>\n<p>\nMund\u00ebsit\u00eb e integrimit me 1C<\/p>\n<h3>Ekzistojn\u00eb qasje t\u00eb ndryshme p\u00ebr realizimin e integrimit me aplikacionet 1C; cili prej tyre t\u00eb zgjidhet varet nga k\u00ebrkesat e detyr\u00ebs.<\/h3>\n<p>\nRealizimi mbi baz\u00ebn e<\/p>\n<ol>\n<li>mekanizmave t\u00eb integrimit <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000581.htm\">, t\u00eb ofruara nga platforma, t\u00eb nj\u00eb API t\u00eb specializuar t\u00eb vet\u00eb aplikacionit 1C (p\u00ebr shembull, nj\u00eb grup sh\u00ebrbimesh Web ose HTTP, t\u00eb cilat do t\u00eb th\u00ebrrasin aplikacione t\u00eb jashtme p\u00ebr shk\u00ebmbimin e t\u00eb dh\u00ebnave me aplikacionin 1C). Avantazhi i k\u00ebtij qasjeje \u00ebsht\u00eb q\u00eb API \u00ebsht\u00eb i q\u00ebndruesh\u00ebm ndaj ndryshimeve t\u00eb realizimit n\u00eb an\u00ebn e aplikacionit 1C. Karakteristika e qasjes \u00ebsht\u00eb se k\u00ebrkon ndryshimin e kodit t\u00eb burimit t\u00eb zgjidhjes s\u00eb tipit t\u00eb 1C, q\u00eb potencialisht mund t\u00eb k\u00ebrkoj\u00eb p\u00ebrpjekje gjat\u00eb bashkimit t\u00eb kodit t\u00eb burimit gjat\u00eb kalimit n\u00eb nj\u00eb version t\u00eb ri t\u00eb konfiguracionit. N\u00eb k\u00ebt\u00eb rast, mund t\u00eb ndihmoj\u00eb funksionaliteti i ri progresiv \u2014<\/a><\/noindex>zgjerimet e konfiguracionit <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000883.htm\">zgjerimi i konfigurimit<\/a><\/noindex>. Zgjerimet jan\u00eb, n\u00eb thelb, nj\u00eb mekaniz\u00ebm p\u00ebr shtesa q\u00eb lejon krijimin e plot\u00ebsimeve p\u00ebr zgjidhjet aplikative, pa ndryshuar vet\u00eb zgjidhjet aplikative. Nxjerrja e API-t t\u00eb integrimit n\u00eb zgjerimin e konfiguracionit do t\u00eb shmang\u00eb v\u00ebshtir\u00ebsit\u00eb gjat\u00eb bashkimit t\u00eb konfiguracioneve gjat\u00eb kalimit n\u00eb nj\u00eb version t\u00eb ri t\u00eb zgjidhjes standarde.\n<\/li>\n<li>P\u00ebrdorimi i mekanizmave t\u00eb integrimit t\u00eb platform\u00ebs, t\u00eb cil\u00ebt ofrojn\u00eb qasje nga jasht\u00eb n\u00eb modelin e objektit t\u00eb aplikacionit dhe nuk k\u00ebrkojn\u00eb ndryshime n\u00eb aplikacion ose krijimin e zgjerimeve. Avantazhi i k\u00ebtij qashti \u00ebsht\u00eb se nuk nevojitet ndryshimi i aplikacionit 1C. Disavantazhi \u00ebsht\u00eb se n\u00ebse aplikacioni 1C \u00ebsht\u00eb rregulluar, mund t\u00eb k\u00ebrkohen rregullime n\u00eb aplikacionin e integruar. Nj\u00eb shembull i k\u00ebtij qashtjeje \u00ebsht\u00eb p\u00ebrdorimi i protokollit OData p\u00ebr integrim, i implementuar nga platforma 1C:Nd\u00ebrmarrja (m\u00eb shum\u00eb rreth tij m\u00eb posht\u00eb).\n<\/li>\n<li>P\u00ebrdorimi i protokolleve aplikative t\u00eb gatshme, t\u00eb implementuara n\u00eb zgjidhjet standarde 1C. Shum\u00eb zgjidhje standarde nga 1C dhe partner\u00ebt e saj implementojn\u00eb n\u00eb baz\u00eb t\u00eb mekanizmave t\u00eb integrimit, protokolle aplikative t\u00eb tyre q\u00eb jan\u00eb t\u00eb orientuara ndaj detyrave specifike. Kur p\u00ebrdoren k\u00ebta mekanizma, nuk \u00ebsht\u00eb e nevojshme t\u00eb shkruhet kod n\u00eb an\u00ebn e aplikacionit 1C, pasi ne p\u00ebrdorim mund\u00ebsit\u00eb standarde t\u00eb zgjidhjes aplikative. N\u00eb an\u00ebn e aplikacionit 1C, na nevojitet vet\u00ebm t\u00eb kryejm\u00eb disa konfigurime.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Mekanizmat e integrimit n\u00eb platform\u00ebn 1C:Nd\u00ebrmarrje<\/h3>\n<p><\/p>\n<h4>Import\/eksport t\u00eb skedar\u00ebve<\/h4>\n<p>\nP\u00ebr t\u00eb zgjidhur nj\u00eb detyr\u00eb t\u00eb till\u00eb, supozojm\u00eb q\u00eb kemi p\u00ebrpara nesh nj\u00eb detyr\u00eb p\u00ebr exchange dyansh\u00ebm t\u00eb t\u00eb dh\u00ebnave mes aplikacionit 1C dhe nj\u00eb aplikacioni t\u00eb rast\u00ebsish\u00ebm. P\u00ebr shembull, na nevojitet t\u00eb sinkronizojm\u00eb list\u00ebn e produkteve (referenca Nomenklatura) mes aplikacionit 1C dhe nj\u00eb aplikacioni t\u00eb rast\u00ebsish\u00ebm.<\/p>\n<p><img decoding=\"async\" alt=\"Metodat e integrimit me 1C\" src=\"\/wp-content\/uploads\/2019\/08\/9678f09dfcf7f70de100ed74ada6019c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nP\u00ebr t\u00eb zgjidhur nj\u00eb detyr\u00eb t\u00eb till\u00eb, mund t\u00eb shkruajm\u00eb nj\u00eb zgjerim q\u00eb eksporton referenc\u00ebn Nomenklatura n\u00eb nj\u00eb skedar t\u00eb formatit t\u00eb caktuar (tekst, XML, JSON, \u2026) dhe \u00ebsht\u00eb n\u00eb gjendje t\u00eb lexoj\u00eb k\u00ebt\u00eb format. <\/p>\n<p>N\u00eb platform\u00eb \u00ebsht\u00eb implementuar nj\u00eb mekaniz\u00ebm p\u00ebr serializimin e objekteve aplikative n\u00eb XML si drejtp\u00ebrdrejt, p\u00ebrmes metodave t\u00eb kontekstit global ShkruajXML\/LeximiXML, ashtu edhe me ndihm\u00ebn e objektit ndihm\u00ebs XDTO (XML Data Transfer Objects).<\/p>\n<p>\u00c7do objekt n\u00eb sistemin 1C:Nd\u00ebrmarrje mund t\u00eb serializohet n\u00eb nj\u00eb paraqitje XML dhe anasjelltas. <\/p>\n<p>Kjo funksion do t\u00eb kthej\u00eb paraqitjen e objektit n\u00eb form\u00ebn XML:<\/p>\n<pre><code class=\"1c\">Funksioni Objekt_N\u00eb_XML(Objekti)\n    ShkruajXML = E Re ShkruajXML();\n    ShkruajXML.P\u00ebrcaktoDaten();\n    ShkruajXML(ShkruajXML, Objekti);\n    Kthe ShkruajXML.Mbylle();\nFundFunksioni\n<\/code><\/pre>\n<p>\nkjo do t\u00eb jet\u00eb pamja e eksportit t\u00eb katalogut Nomenklatura n\u00eb XML p\u00ebrmes XDTO:<\/p>\n<pre><code class=\"1c\">&amp;N\u00ebServer\nProcedura EksportXMLN\u00ebServer()\n\tRisiSerializatorXDTO  = SerializatorXDTO;\n\tShkruajXMLERe = E Re ShkruajXML();\n\tShkruajXMLERe.HapeSkedarin(\"C:DataNomenklatura.xml\", \"UTF-8\");\n\t\n\tShkruajXMLERe.ShkruajP\u00ebrshkriminXML();\n\tShkruajXMLERe.ShkruajFilliminElementit(\"KatalogNomenklatura\");\n\t\n\tZgjedhja = Katalogu.Nomenklatura.Zgjidh();\n\t\n\tNd\u00ebrsa Zgjedhja.N\u00ebTjet\u00ebr() Cikli \n\t\tObjektiNomenklatur\u00eb = Zgjedhja.MerrObjektin();\n\t\tRisiSerializatorXDTO.ShkruajXML(ShkruajXMLERe, ObjektiNomenklatur\u00eb, Q\u00ebllimiXML.Explicit);\n\tFundCikli;\n\t\n\tShkruajXMLERe.ShkruajFundElementit();\n\tShkruajXMLERe.Mbylle();\nFundProcedura\n<\/code><\/pre>\n<p>\nDuke e modifikuar disi kodin, ne eksportojm\u00eb katalogun n\u00eb JSON. Produktet do t\u00eb shkruhen n\u00eb nj\u00eb mas\u00eb; p\u00ebr larmishm\u00ebri, do t\u00eb japim nj\u00eb variant anglisht t\u00eb sintaks\u00ebs:<\/p>\n<pre><code class=\"1c\">&amp;N\u00ebServer\nProcedura EksportJSONN\u00ebServer()\n\tRisiSerializatorXDTO  = RisiSerializatorXDTO;\n\tRisiShkruaj\u00ebsJSON = E Re Shkruaj\u00ebsJSON();\n\tRisiShkruaj\u00ebsJSON.HapeSkedarin(\"C:DataNomenklatura.json\", \"UTF-8\");\n\t\n\tRisiShkruaj\u00ebsJSON.ShkruajFilliminObjektit();\n\tRisiShkruaj\u00ebsJSON.ShkruajEmrinPron\u00ebs(\"KatalogNomenklatura\");\n\tRisiShkruaj\u00ebsJSON.ShkruajFilliminM\u00ebnyr\u00ebs();\n\t\n\tZgjedhja = Katalogu.Nomenklatura.Zgjidh();\t\n\t\n\tNd\u00ebrsa Zgjedhja.N\u00ebTjet\u00ebr() B\u00ebni \n\t\tObjektiNomenklatur\u00eb = Zgjedhja.MerrObjektin();\n\t\t\n\t\tRisiShkruaj\u00ebsJSON.ShkruajFilliminObjektit();\n\t\t\n\t\tRisiShkruaj\u00ebsJSON.ShkruajEmrinPron\u00ebs(\"Nomenklatura\");\n\t\tRisiSerializatorXDTO.ShkruajJSON(RisiShkruaj\u00ebsJSON, ObjektiNomenklatur\u00eb, Q\u00ebllimiXML.P\u00ebrfshire);\n\t\t\n\t\tRisiShkruaj\u00ebsJSON.ShkruajFundObjektit();\n\tFundB\u00ebni;\n\t\n\tRisiShkruaj\u00ebsJSON.ShkruajFundM\u00ebnyr\u00ebs();\n\tRisiShkruaj\u00ebsJSON.ShkruajFundObjektit();\n\tRisiShkruaj\u00ebsJSON.Mbylle();\nFundProcedura\n<\/code><\/pre>\n<p>\nM\u00eb pas mbetet vet\u00ebm t\u00eb kaloni t\u00eb dh\u00ebnat te konsumatori p\u00ebrfundimtar. Platforma 1C:Nd\u00ebrmarrje mb\u00ebshtet protokollet kryesore t\u00eb internetit HTTP, FTP, POP3, SMTP, IMAP, p\u00ebrfshir\u00eb versionet e tyre t\u00eb sigurta. Po ashtu, p\u00ebr kalimin e t\u00eb dh\u00ebnave mund t\u00eb p\u00ebrdoren HTTP dhe\/ose Sh\u00ebrbime Web.<\/p>\n<h4>Sh\u00ebrbime HTTP dhe web<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Metodat e integrimit me 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1d4797d9298f793e19ee637fd26473b2.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Aplikacionet 1C mund t\u00eb realizojn\u00eb sh\u00ebrbime HTTP dhe web, si dhe t\u00eb th\u00ebrrasin sh\u00ebrbime HTTP dhe web t\u00eb realizuara nga aplikacione t\u00eb tjera. <\/p>\n<h4>REST nd\u00ebrfaqja dhe protokolli OData<\/h4>\n<p>\nDeri n\u00eb versionin 8.3.5, platforma 1C:Nd\u00ebrmarrje mund t\u00eb formoj\u00eb automatikisht <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/avtomaticheskiy-rest-interfeys-prikladnykh-resheniy\/\">nj\u00eb nd\u00ebrfaqe REST<\/a><\/noindex> p\u00ebr t\u00eb gjith\u00eb zgjidhjen aplikative. \u00c7do objekt konfigurimi (katalog, dokument, regjist\u00ebr informacioni etj.) mund t\u00eb b\u00ebhet i disponuesh\u00ebm p\u00ebr marrjen dhe modifikimin e t\u00eb dh\u00ebnave p\u00ebrmes nd\u00ebrfaqes REST. Si protokoll qasje, platforma p\u00ebrdor protokollin <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Open_Data_Protocol\">OData<\/a><\/noindex> versioni 3.0. Publikimi i sh\u00ebrbimeve OData b\u00ebhet nga menuja e Konfiguratorit \"Administrimi -&gt; Publikimi n\u00eb serverin web\", kutia \"Publiko nd\u00ebrfaqen standarde OData\" duhet t\u00eb jet\u00eb e sh\u00ebnuar. Formatet atom\/XML dhe JSON mb\u00ebshteten. Pas publikimit t\u00eb zgjidhjes aplikative n\u00eb serverin web, sistemet e jashtme mund t'i aksesojn\u00eb ato p\u00ebrmes nd\u00ebrfaqes REST duke p\u00ebrdorur k\u00ebrkesa HTTP. P\u00ebr t\u00eb punuar me aplikacionin 1C n\u00ebp\u00ebrmjet protokollit OData, programimi n\u00eb an\u00ebn e 1C nuk k\u00ebrkohet.<\/p>\n<p>Pra, URL e form\u00ebs <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Nomenklatura<\/u> do t\u00eb na kthej\u00eb p\u00ebrmbajtjen e katalogut Nomenklatura n\u00eb formatin XML \u2014 nj\u00eb koleksion elementesh entry (titulli i mesazhit \u00ebsht\u00eb l\u00ebn\u00eb jasht\u00eb p\u00ebr shkak t\u00eb shkurt\u00ebsis\u00eb):<\/p>\n<pre><code class=\"xml\">http:\/\/server\/Config\/odata\/standard.odata\/Catalog_Nomenklatura(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\tKondicioner Mitsubishi\n\t\t\tKapaciteti 2,5 kW, modet e pun\u00ebs: ngrohje\/freshk\n\t\t\n\t\n\n\n\thttp:\/\/server\/Config\/odata\/standard.odata\/Catalog_Nomenklatura(guid'35d1f6e5-289b-11e6-8ba4-e03f49b16074')\n\t\n\t...\n<\/code><\/pre>\n<p>\nDuke shtuar n\u00eb URL-n\u00eb e m\u00ebposhtme \"?$format=application\/json\", ne do t\u00eb marrim p\u00ebrmbajtjen e katalogut Nomenklatura n\u00eb formatin JSON (URL e form\u00ebs <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Nomenklatura?$format=application\/json<\/u> ):<\/p>\n<pre><code>{\n\"odata.metadata\": \"http:\/\/server\/Config\/odata\/standard.odata\/$metadata#Catalog_Nomenklatura\",\n\"value\": [{\n\"Ref_Key\": \"35d1f6e4-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAgAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000001\",\n\"Description\": \"Kondicioner Mitsubishi\",\n\"\u03a0\u03b5\u03c1\u03b9\u03b3\u03c1\u03b1\u03c6\u03ae\": \"Kapaciteti 2,5 kW, modet e pun\u00ebs: ngrohje\/freshk\"\n},{\n\"Ref_Key\": \"35d1f6e5-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAwAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000002\",\n\"Description\": \"Kondicioner Daikin\",\n\"\u03a0\u03b5\u03c1\u03b9\u03b3\u03c1\u03b1\u03c6\u03ae\": \"Kapaciteti 3 kW, modet e pun\u00ebs: ngrohje\/freshk\"\n}, \u2026\n<\/code><\/pre>\n<p><\/p>\n<h4>Burime t\u00eb jashtme t\u00eb t\u00eb dh\u00ebnave<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Metodat e integrimit me 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1663b53846f3a6a8a03f386f1f6cd311.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nN\u00eb disa raste, shk\u00ebmbimi i t\u00eb dh\u00ebnave p\u00ebrmes <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000795.htm\">burimeve t\u00eb jashtme t\u00eb t\u00eb dh\u00ebnave<\/a><\/noindex> mund t\u00eb jet\u00eb zgjidhja optimale. Burimet e jashtme t\u00eb t\u00eb dh\u00ebnave jan\u00eb nj\u00eb objekt aplikativ i konfigurimit 1C, q\u00eb lejon nd\u00ebrveprimin me \u00e7do baz\u00eb t\u00eb dh\u00ebnash q\u00eb p\u00ebrputhet me ODBC si p\u00ebr lexim ashtu edhe p\u00ebr shkruar. Burimet e jashtme t\u00eb t\u00eb dh\u00ebnave jan\u00eb t\u00eb disponueshme si n\u00eb Windows ashtu edhe n\u00eb Linux.<\/p>\n<h4>Mekanizmi i shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave<\/h4>\n<p>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000269.htm\">Mekanizmi i shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave<\/a><\/noindex> \u00ebsht\u00eb i destinuar si p\u00ebr krijimin e sistemeve territorialisht t\u00eb shp\u00ebrndara mbi 1C:Enterprise, ashtu edhe p\u00ebr organizimin e shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave me sisteme t\u00eb tjera informative q\u00eb nuk bazohet n\u00eb 1C:Enterprise.<\/p>\n<p>Ky mekaniz\u00ebm p\u00ebrdoret aktivisht n\u00eb implementimet e 1C, dhe gama e detyrave q\u00eb zgjidhen me ndihm\u00ebn e tij \u00ebsht\u00eb mjaft e gjer\u00eb. Kjo p\u00ebrfshin shk\u00ebmbimin e t\u00eb dh\u00ebnave midis aplikacioneve 1C, t\u00eb instaluara n\u00eb deg\u00ebt e organizat\u00ebs, si dhe shk\u00ebmbimin midis aplikacionit 1C dhe sitit t\u00eb dyqanit online, dhe shk\u00ebmbimin e t\u00eb dh\u00ebnave midis aplikacionit server 1C dhe klientit mobil (t\u00eb krijuar me ndihm\u00ebn e platform\u00ebs mobile 1C:Enterprise), dhe shum\u00eb m\u00eb tep\u00ebr.<\/p>\n<p>Nj\u00eb nga konceptet ky\u00e7e n\u00eb mekanizmin e shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb plani i shk\u00ebmbimit. Plani i shk\u00ebmbimit \u00ebsht\u00eb nj\u00eb lloj i ve\u00e7ant\u00eb objekti aplikativ t\u00eb platform\u00ebs 1C, t\u00eb cilat p\u00ebrcaktojn\u00eb, p\u00ebr shembull, p\u00ebrb\u00ebrjen e t\u00eb dh\u00ebnave q\u00eb do t\u00eb marrin pjes\u00eb n\u00eb shk\u00ebmbim (cilat sakt\u00ebsisht katalog\u00eb, dokumente, regjistra etj.). Plani i shk\u00ebmbimit p\u00ebrmban gjithashtu informacion rreth pjes\u00ebmarr\u00ebsve n\u00eb shk\u00ebmbim (t\u00eb ashtuquajturit pika shk\u00ebmbimi).<br \/>\nShtesa e dyt\u00eb e mekanizmit t\u00eb shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb mekanizmi i regjistrimit t\u00eb ndryshimeve. Ky mekaniz\u00ebm ndjek automatikisht n\u00eb sistem ndryshimet e t\u00eb dh\u00ebnave q\u00eb duhet t\u00eb d\u00ebrgohen konsumator\u00ebve t\u00eb fundit n\u00eb kuad\u00ebr t\u00eb planit t\u00eb shk\u00ebmbimit. Me ndihm\u00ebn e k\u00ebtij mekanizmi, platforma ndjek ndryshimet q\u00eb kan\u00eb ndodhur nga sinjalizimi i fundit, dhe lejon minimizimin e sasis\u00eb s\u00eb t\u00eb dh\u00ebnave q\u00eb d\u00ebrgohen n\u00eb kuad\u00ebr t\u00eb seanc\u00ebs s\u00eb ardhshme t\u00eb sinjalizimit.<\/p>\n<p>Shk\u00ebmbimi i t\u00eb dh\u00ebnave ndodh p\u00ebrmes mesazheve XML me nj\u00eb struktur\u00eb t\u00eb caktuar. Mesazhi p\u00ebrmban t\u00eb dh\u00ebnat q\u00eb kan\u00eb ndryshuar nga sinkronizimi i fundit me nyj\u00ebn, si dhe disa informacione sh\u00ebrbyese. Struktura e mesazheve mb\u00ebshtet num\u00ebrimin e mesazheve dhe lejon marrjen e konfirmimeve nga nyja pran\u00ebse p\u00ebr pranimet e mesazheve. Ky konfirmim p\u00ebrmbushet n\u00eb \u00e7do mesazh q\u00eb vjen nga nyja pran\u00ebse, n\u00eb form\u00ebn e numrit t\u00eb mesazhit t\u00eb fundit t\u00eb pranuar. Num\u00ebrimi i mesazheve lejon platform\u00ebn t\u00eb kuptoj\u00eb cilat t\u00eb dh\u00ebna jan\u00eb transferuar me sukses n\u00eb nyj\u00ebn pran\u00ebse, duke shmangur p\u00ebrs\u00ebritjen e transferimit dhe duke kaluar vet\u00ebm t\u00eb dh\u00ebnat e ndryshuara nga prania e mesazhit t\u00eb fundit me pranim nga nyja d\u00ebrgues. Me k\u00ebt\u00eb skem\u00eb funksionimi, sigurohet dor\u00ebzimi i garantuar edhe n\u00eb kanale t\u00eb pasigurt t\u00eb transmetimit dhe humbje mesazhesh.<\/p>\n<h4>Komponent\u00ebt e jasht\u00ebm<\/h4>\n<p>\nN\u00eb disa raste, kur zgjidhni probleme t\u00eb integrimit, \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrballeni me k\u00ebrkesa specifike, p\u00ebr shembull, protokollet e nd\u00ebrveprimit, format e t\u00eb dh\u00ebnave, me t\u00eb cilat platforma 1C:Enterprise nuk parashikon t\u00eb punoj\u00eb. P\u00ebr k\u00ebt\u00eb grup problemesh, platforma parashikon <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000545.htm\">teknologjin\u00eb e komponent\u00ebve t\u00eb jasht\u00ebm<\/a><\/noindex>, e cila lejon krijimin e moduleve q\u00eb lidhen dinamikisht, duke zgjeruar funksionalitetin e 1C:Enterprise. <\/p>\n<p>Nj\u00eb shembull tipik i nj\u00eb problemi me k\u00ebto k\u00ebrkesa mund t\u00eb jet\u00eb integrimi i zgjidhjes aplikative 1C me pajisjet tregtare, duke filluar nga pesha dhe duke p\u00ebrfunduar me kasa dhe skanera kodesh. Komponent\u00ebt e jasht\u00ebm mund t\u00eb lidhen si n\u00eb an\u00ebn e serverit 1C:Enterprise ashtu edhe n\u00eb pjes\u00ebn klient (duke p\u00ebrfshir\u00eb gjithashtu klientin n\u00eb ueb dhe <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/vneshnie-komponenty-v-mobilnom-prilozhenii\/\">versionin e ardhsh\u00ebm t\u00eb platform\u00ebs mobile t\u00eb<\/a><\/noindex> 1C:Enterprise). Teknologjia e komponent\u00ebve t\u00eb jasht\u00ebm parashikon nj\u00eb nd\u00ebrfaqe programimi (C++) mjaft t\u00eb thjesht\u00eb dhe t\u00eb kuptueshme p\u00ebr nd\u00ebrveprimin e komponentit me platform\u00ebn 1C:Enterprise, e cila duhet t\u00eb realizohet nga zhvilluesi.<\/p>\n<p>Mund\u00ebsit\u00eb q\u00eb hapen me p\u00ebrdorimin e komponent\u00ebve t\u00eb jasht\u00ebm jan\u00eb mjaft t\u00eb gjera. Mund t\u00eb realizoni nd\u00ebrveprimin sipas nj\u00eb protokolli specifik t\u00eb shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave me pajisje dhe sisteme t\u00eb jashtme, t\u00eb integroni algoritme specifike p\u00ebr p\u00ebrpunimin e t\u00eb dh\u00ebnave dhe formateve t\u00eb t\u00eb dh\u00ebnave etj.<\/p>\n<h4>Mekanizmat e vjetra t\u00eb integrimit<\/h4>\n<p>\nN\u00eb platform\u00eb jan\u00eb t\u00eb disponueshme mekanizmat e integrimit q\u00eb nuk rekomandohen t\u00eb p\u00ebrdoren n\u00eb zgjidhjet e reja; ato jan\u00eb l\u00ebn\u00eb p\u00ebr arsye t\u00eb kompaktibilitetit mbrapa, si dhe n\u00eb rast se pala tjet\u00ebr nuk mund t\u00eb punoj\u00eb me protokollet m\u00eb moderne. Nj\u00ebri prej tyre \u00ebsht\u00eb puna me skedar\u00eb n\u00eb formatin DBF (mb\u00ebshtetet n\u00eb gjuh\u00ebn e integruar me an\u00eb t\u00eb objektit XBase).<\/p>\n<p>Nj\u00eb mekaniz\u00ebm tjet\u00ebr i vjetruar i integrimit \u00ebsht\u00eb p\u00ebrdorimi i teknologjis\u00eb COM (disponohet vet\u00ebm n\u00eb platform\u00ebn Windows). Platforma 1C:Enterprise ofron dy m\u00ebnyra integrimi p\u00ebr Windows, q\u00eb p\u00ebrdorin teknologjin\u00eb COM: Serveri i Automattizmit dhe Lidha Ejashteme. Ato jan\u00eb shum\u00eb t\u00eb ngjashme, por nj\u00eb nga ndryshimet themelore \u00ebsht\u00eb se n\u00eb rastin e Serverit t\u00eb Automattizmit nis nj\u00eb aplikacion t\u00eb plot\u00eb klienti 1C:Enterprise 8, nd\u00ebrsa n\u00eb rastin e lidhjes externe nis n\u00eb nj\u00eb server COM relativisht t\u00eb vog\u00ebl brenda procesit. K\u00ebshtu, n\u00eb rastin e pun\u00ebs p\u00ebrmes Serverit t\u00eb Automattizmit, mund t\u00eb shfryt\u00ebzoni funksionalitetin e aplikacionit klient, duke kryer veprime t\u00eb ngjashme me veprimet interaktive t\u00eb p\u00ebrdoruesit. Kur p\u00ebrdoret lidhja externe, mund t\u00eb p\u00ebrdoren vet\u00ebm funksionet e logjik\u00ebs biznesore, t\u00eb cilat mund t\u00eb realizohen si n\u00eb an\u00ebn e klientit t\u00eb lidhjes, ku krijohet serveri brenda procesit, ashtu edhe t\u00eb thirren logjika e biznesit n\u00eb an\u00ebn e serverit 1C:Enterprise.<\/p>\n<p>Gjithashtu, teknologjia COM mund t\u00eb p\u00ebrdoret p\u00ebr t'u adresuar sistemeve t\u00eb jashtme nga kodi i aplikacionit n\u00eb platform\u00ebn 1C:Enterprise. N\u00eb k\u00ebt\u00eb rast, aplikacioni 1C sh\u00ebrben si klient COM. Por duhet theksuar se k\u00ebto mekanizma do t\u00eb funksionojn\u00eb vet\u00ebm n\u00eb rast se serveri 1C operon n\u00eb nj\u00eb ambient Windows.<\/p>\n<h3>Mekanizmat e integrimit t\u00eb realizuar n\u00eb konfigurimet standarde<\/h3>\n<p><\/p>\n<h4>Formati EnterpriseData<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Metodat e integrimit me 1C\" src=\"\/wp-content\/uploads\/2019\/08\/8930091e53309b9b808a719b747a6226.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nN\u00eb disa konfigurime 1C (lista m\u00eb posht\u00eb) mbi baz\u00ebn e mekanizmit t\u00eb p\u00ebrmendur m\u00eb sip\u00ebr p\u00ebr shk\u00ebmbim t\u00eb t\u00eb dh\u00ebnave \u00ebsht\u00eb realizuar nj\u00eb mekaniz\u00ebm i gatsh\u00ebm p\u00ebr shk\u00ebmbim t\u00eb t\u00eb dh\u00ebnave me aplikacione t\u00eb jashtme, q\u00eb nuk k\u00ebrkon ndryshimin e kodit burimor t\u00eb konfigurimeve (p\u00ebrgatitja p\u00ebr shk\u00ebmbim t\u00eb t\u00eb dh\u00ebnave b\u00ebhet n\u00eb cil\u00ebsimet e zgjidhjeve aplikative):<\/p>\n<ul>\n<li>\u00ab1C:ERP Menaxhimi i nd\u00ebrmarrjes 2.0\u00bb <\/li>\n<li>\u00abAutomatizimi i Kompleksit 2\u00bb <\/li>\n<li>\u00abKontabiliteti i Nd\u00ebrmarrjes\u00bb, edicioni 3.0 <\/li>\n<li>\u00abKontabiliteti i Nd\u00ebrmarrjes KORP\u00bb, edicioni 3.0 <\/li>\n<li>\u00abPik\u00eb Shitjeje\u00bb, edicioni 2.0 <\/li>\n<li>\u00abMenaxhimi i Tregtis\u00eb Baz\u00eb\u00bb, redaktimi 11 <\/li>\n<li>\u00abMenaxhimi i Tregtis\u00eb\u00bb, redaktimi 11<\/li>\n<li>\u00abPaga dhe Menaxhimi i Personelit KORP\u00bb, redaktimi 3<\/li>\n<\/ul>\n<p>\nP\u00ebr nd\u00ebrrimin e t\u00eb dh\u00ebnave p\u00ebrdoret formati <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_app\/enterprisedata\/\">EnterpriseData<\/a><\/noindex>, i bazuar n\u00eb XML. Formati \u00ebsht\u00eb orientuar drejt biznesit - strukturat e p\u00ebrshkruara n\u00eb t\u00eb p\u00ebrputhen me entitetet e biznesit (dokumentet dhe elementet e regjistrave), t\u00eb paraqitura n\u00eb programet 1C, p\u00ebr shembull: akti i pun\u00ebve t\u00eb kryera, urdhri i paraqitjes n\u00eb kas\u00eb, kontraktori, nomenklatura etj.<\/p>\n<p>Nd\u00ebrrimi i t\u00eb dh\u00ebnave midis aplikacionit 1C dhe aplikacionit t\u00eb jasht\u00ebm mund t\u00eb ndodh\u00eb:<\/p>\n<ul>\n<li>n\u00ebp\u00ebrmjet nj\u00eb katalogu t\u00eb dedikuar t\u00eb skedar\u00ebve <\/li>\n<li>n\u00ebp\u00ebrmjet katalogut FTP <\/li>\n<li>n\u00ebp\u00ebrmjet nj\u00eb sh\u00ebrbimi web, i vendosur n\u00eb an\u00ebn e aplikacionit 1C. Skedari me t\u00eb dh\u00ebnat d\u00ebrgohet si paramet\u00ebr i metodave web<\/li>\n<li>n\u00ebp\u00ebrmjet post\u00ebs elektronike<\/li>\n<\/ul>\n<p>\nN\u00eb rastin e nd\u00ebrrimit n\u00ebp\u00ebrmjet sh\u00ebrbimit web, aplikacioni i jasht\u00ebm do t\u00eb inicioj\u00eb seanc\u00ebn e nd\u00ebrrimit t\u00eb t\u00eb dh\u00ebnave duke thirrur metodat e p\u00ebrcaktuara t\u00eb aplikacionit 1C. N\u00eb rastet e tjera, iniciatori i seanc\u00ebs s\u00eb nd\u00ebrrimit do t\u00eb jet\u00eb aplikacioni 1C (duke vendosur skedarin me t\u00eb dh\u00ebnat n\u00eb katalogun p\u00ebrkat\u00ebs ose duke d\u00ebrguar skedarin me t\u00eb dh\u00ebnat n\u00eb adres\u00ebn e mailit t\u00eb caktuar).<br \/>\nGjithashtu, n\u00eb an\u00ebn e 1C konfigurohet frekuenca me t\u00eb cil\u00ebn do t\u00eb ndodhi sinkronizimi (p\u00ebr opsionet me nd\u00ebrrim t\u00eb skedar\u00ebve n\u00ebp\u00ebrmjet katalogut dhe post\u00ebs elektronike):<\/p>\n<ul>\n<li>sip\u00e1s nj\u00eb orari (me nj\u00eb frekuenc\u00eb t\u00eb caktuar) <\/li>\n<li>duke e b\u00ebr\u00eb manualisht; p\u00ebrdoruesi do t\u00eb duhet t\u00eb nis\u00eb manualisht sinkronizimin \u00e7do her\u00eb q\u00eb t\u00eb ket\u00eb nevoj\u00eb<\/li>\n<\/ul>\n<p><\/p>\n<h5>Konfirmimi i mesazheve<\/h5>\n<p>\nAplikacionet 1C mbajn\u00eb sh\u00ebnim p\u00ebr mesazhet e d\u00ebrguara dhe t\u00eb pranuara t\u00eb sinkronizimit dhe presin t\u00eb nj\u00ebjt\u00ebn nga aplikacionet e jashtme. Kjo e lejon p\u00ebrdorimin e mekanizmit t\u00eb num\u00ebrimit t\u00eb mesazheve, t\u00eb p\u00ebrshkruar m\u00eb sip\u00ebr n\u00eb seksionin \u201cMekanizmi i nd\u00ebrrimit t\u00eb t\u00eb dh\u00ebnave\u201d.<\/p>\n<p>Aplikacionet 1C gjat\u00eb sinkronizimit transmetojn\u00eb vet\u00ebm informatat p\u00ebr ndryshimet q\u00eb kan\u00eb ndodhur me entitetet biznesore q\u00eb nga sinkronizimi i fundit (p\u00ebr t\u00eb minimizuar sasin\u00eb e informacionit t\u00eb transmetuar). Gjat\u00eb sinkronizimit t\u00eb par\u00eb, aplikacioni 1C do t\u00eb shkarkoj\u00eb t\u00eb gjitha entitetet biznesore (p\u00ebr shembull, element\u00ebt e regjistrit t\u00eb nomenklatur\u00ebs) n\u00eb formatin EnterpriseData n\u00eb nj\u00eb skedar XML (pasi t\u00eb gjith\u00eb ato jan\u00eb \"t\u00eb reja\" p\u00ebr aplikacionin e jasht\u00ebm). Aplikacioni i jasht\u00ebm duhet t\u00eb p\u00ebrpunoj\u00eb informacionin nga skedari XML i ardhur nga 1C dhe gjat\u00eb sesionit t\u00eb ardhsh\u00ebm t\u00eb sinkronizimit t\u00eb vendos\u00eb n\u00eb skedarin q\u00eb d\u00ebrgohet n\u00eb 1C, n\u00eb nj\u00eb seksion t\u00eb ve\u00e7ant\u00eb XML, informacionin q\u00eb mesazhi nga 1C p\u00ebr nj\u00eb num\u00ebr t\u00eb caktuar \u00ebsht\u00eb pranuar me sukses. Mesazhi i konfirmimit \u00ebsht\u00eb p\u00ebr aplikacionin 1C nj\u00eb sinjal se t\u00eb gjitha entitetet biznesore jan\u00eb p\u00ebrpunuar me sukses nga aplikacioni i jasht\u00ebm dhe nuk \u00ebsht\u00eb m\u00eb e nevojshme t\u00eb transmetohet informacion rreth tyre. P\u00ebrve\u00e7 konfirmimit, skedari XML nga aplikacioni i jasht\u00ebm gjithashtu mund t\u00eb p\u00ebrmbaj\u00eb t\u00eb dh\u00ebna p\u00ebr sinkronizimin nga ana e aplikacionit (p\u00ebr shembull, dokumentet e realizimit t\u00eb produkteve dhe sh\u00ebrbimeve).<\/p>\n<p>Pas marrjes s\u00eb mesazhit t\u00eb konfirmimit, aplikacioni 1C sh\u00ebnon t\u00eb gjitha ndryshimet e d\u00ebrguara n\u00eb mesazhin e m\u00ebparsh\u00ebm si t\u00eb sinkronizuara me sukses. Vet\u00ebm ndryshimet e nesinkronizuara n\u00eb entitetet biznesore (krijimi i entiteteve t\u00eb reja, ndryshimi dhe fshirja e ekzistueseve) do t\u00eb d\u00ebrgohen n\u00eb aplikacionin e jasht\u00ebm gjat\u00eb sesionit t\u00eb ardhsh\u00ebm t\u00eb sinkronizimit.<\/p>\n<p><img decoding=\"async\" alt=\"Metodat e integrimit me 1C\" src=\"\/wp-content\/uploads\/2019\/08\/b0d5509a53909e38886a15c2e03e7131.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nKur d\u00ebrgohen t\u00eb dh\u00ebnat nga aplikacioni i jasht\u00ebm n\u00eb aplikacionin 1C, skenari ndryshon n\u00eb t\u00eb kund\u00ebrt. Aplikacioni i jasht\u00ebm duhet t\u00eb plot\u00ebsoj\u00eb seksionin e konfirmimit n\u00eb skedarin XML p\u00ebrkat\u00ebs dhe t\u00eb vendos\u00eb t\u00eb dh\u00ebnat biznesore p\u00ebr sinkronizim nga ana e tij n\u00eb formatin EnterpriseData.<\/p>\n<p><img decoding=\"async\" alt=\"Metodat e integrimit me 1C\" src=\"\/wp-content\/uploads\/2019\/08\/d34b96efb7591770133b363b369c0019.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h5>Shk\u00ebmbimi i thjeshtuar i t\u00eb dh\u00ebnave pa konfirmim<\/h5>\n<p>\nP\u00ebr raste t\u00eb integrimit t\u00eb thjesht\u00eb, kur mjafton vet\u00ebm t\u00eb transmetohet informacioni nga aplikacioni i jasht\u00ebm n\u00eb aplikacionin 1C dhe nuk nevojitet kthimi i t\u00eb dh\u00ebnave nga aplikacioni 1C n\u00eb aplikacionin e jasht\u00ebm (p\u00ebr shembull, integrimi i dyqanit online q\u00eb transmeton informacionin e shitjeve n\u00eb \"1C: Kontabilitetin\"), ka nj\u00eb variant t\u00eb thjeshtuar t\u00eb funksionimit p\u00ebrmes nj\u00eb sh\u00ebrbimi web (pa konfirmim), q\u00eb nuk k\u00ebrkon konfigurime nga ana e aplikacionit 1C.<\/p>\n<h4>Zgjidhje t\u00eb specializuara t\u00eb integrimit<\/h4>\n<p>\nEkziston nj\u00eb zgjidhje standarde \"1C: Konvertimi i t\u00eb dh\u00ebnave\", e cila p\u00ebrdor mekanizmat e platform\u00ebs p\u00ebr t\u00eb konvertuar dhe shk\u00ebmbyer t\u00eb dh\u00ebna midis konfigurimeve standarde t\u00eb 1C, por gjithashtu mund t\u00eb p\u00ebrdoret p\u00ebr integrimin me aplikacione t\u00eb jashtme.<\/p>\n<h5>Integrimi me zgjidhjet bankare<\/h5>\n<p>\nStandarti <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/100\/index.htm\">\"Klienti bank\"<\/a><\/noindex>, e zhvilluar nga specialist\u00ebt e 1C m\u00eb shum\u00eb se 10 vjet m\u00eb par\u00eb, faktikisht ka b\u00ebr\u00eb standardin e industris\u00eb n\u00eb Rusi. Hapi tjet\u00ebr n\u00eb k\u00ebt\u00eb drejtim \u00ebsht\u00eb teknologjia <noindex><a rel=\"nofollow\" href=\"http:\/\/directbank.1c.ru\/\">DirectBank<\/a><\/noindex>, e cila lejon d\u00ebrgimin e dokumenteve t\u00eb pages\u00ebs n\u00eb bank\u00eb dhe marrjen e ekstrakteve nga banka menj\u00ebher\u00eb nga programet e sistemit \"1C: Nd\u00ebrmarrjet\" me nj\u00eb klikim n\u00eb programin \"1C\"; n\u00eb k\u00ebt\u00eb rast nuk k\u00ebrkohet instalimi dhe ekzekutimi i programeve shtes\u00eb n\u00eb kompjuterin e klientit. <\/p>\n<p>Ka gjithashtu <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/109\/\">standardi p\u00ebr shk\u00ebmbimin e t\u00eb dh\u00ebnave n\u00eb projektet e pagave<\/a><\/noindex>.<\/p>\n<h5>T\u00eb tjera<\/h5>\n<p>\nMeritojn\u00eb p\u00ebrmendjen <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/131\/\">protokolli i shk\u00ebmbimit midis sistemit 1C: Nd\u00ebrmarrje dhe sitit<\/a><\/noindex>, standardi i shk\u00ebmbimit t\u00eb informacionit tregtar <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/90\/\">CommerceML<\/a><\/noindex> (i zhvilluar n\u00eb bashk\u00ebpunim me Microsoft, Intel, Price.ru dhe kompani t\u00eb tjera), <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/111\/\">standardi i shk\u00ebmbimit t\u00eb t\u00eb dh\u00ebnave p\u00ebr operacionet e ekvaira<\/a><\/noindex>.<br \/>\n<br \/>Burimi: <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.2.1 - 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\/sq\/blog\/administrirovanie\/sposoby-integratsii-s-1s\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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\/sq\/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\udd47M\u00ebnyrat e integrimit me 1C | ProHoster","description":"Cilat jan\u00eb k\u00ebrkesat m\u00eb t\u00eb r\u00ebnd\u00ebsishme p\u00ebr aplikacionet biznesore?","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/sposoby-integratsii-s-1s","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/36968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=36968"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/36968\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/27703"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=36968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=36968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=36968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}