{"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\/ro\/blog\/administrirovanie\/sposoby-integratsii-s-1s","title":{"rendered":"Modalit\u0103\u021bi de integrare cu 1C","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Care sunt cele mai importante cerin\u021be pentru aplica\u021biile de afaceri? Printre cele mai esen\u021biale se num\u0103r\u0103 urm\u0103toarele sarcini:<\/p>\n<ul>\n<li>Facilitatea de modificare\/adaptare a logicii de func\u021bionare a aplica\u021biei la cerin\u021bele de afaceri \u00een continu\u0103 schimbare.<\/li>\n<li>Facilitatea de integrare cu alte aplica\u021bii.<\/li>\n<\/ul>\n<p>\nModul \u00een care se rezolv\u0103 prima sarcin\u0103 \u00een 1C a fost descris pe scurt \u00een sec\u021biunea \u00abPersonalizare \u0219i suport\u00bb <noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1c\/blog\/267321\/\">acestui articol<\/a><\/noindex>; ne vom \u00eentoarce la aceast\u0103 tem\u0103 interesant\u0103 \u00eentr-unul din articolele viitoare. Ast\u0103zi \u00eens\u0103, vom discuta despre a doua sarcin\u0103, integrarea.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Sarcinile de integrare<\/h3>\n<p>\nSarcinile de integrare pot fi variate. Pentru unele, este suficient un schimb de date interactiv simplu \u2014 de exemplu, pentru a trimite c\u0103tre banc\u0103 lista angaja\u021bilor pentru emiterea cardurilor de salariu. Pentru sarcini mai complexe, poate fi necesar un schimb de date complet automatizat, posibil cu apeluri la logica de afaceri a unui sistem extern. Exist\u0103 sarcini de o natur\u0103 specializat\u0103, precum integrarea cu echipamente externe (de exemplu, echipamente de v\u00e2nzare, scanere mobile etc.) sau cu sisteme mo\u0219tenite sau specializate (de exemplu, cu sisteme de recunoa\u0219tere a etichetelor RFID). Este extrem de important, pentru fiecare sarcin\u0103, s\u0103 alegem mecanismul de integrare cel mai potrivit.<\/p>\n<h3>Posibilit\u0103\u021bile de integrare cu 1C<\/h3>\n<p>\nExist\u0103 diferite abord\u0103ri pentru implementarea integr\u0103rii cu aplica\u021biile 1C, alegerea uneia depinde de cerin\u021bele sarcinii.<\/p>\n<ol>\n<li>Implementarea pe baza <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000581.htm\">mecanismelor de integrare<\/a><\/noindex>, furnizate de platform\u0103, a unui API specializat propriu pe partea aplica\u021biei 1C (de exemplu, un set de servicii Web sau HTTP, care vor apela aplica\u021bii externe pentru a schimba date cu aplica\u021bia 1C). Avantajul acestei abord\u0103ri este stabilitatea API-ului fa\u021b\u0103 de modific\u0103rile implement\u0103rii pe partea aplica\u021biei 1C. O caracteristic\u0103 a abord\u0103rii este c\u0103 este necesar\u0103 modificarea codului surs\u0103 al solu\u021biei standard 1C, ceea ce poate necesita eforturi suplimentare la fuziunea codurilor surs\u0103 \u00een cazul trecerii la o nou\u0103 versiune a configura\u021biei. \u00cen acest caz, poate interveni o nou\u0103 func\u021bionalitate progresiv\u0103 \u2014 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000883.htm\">extensii ale configura\u021biei<\/a><\/noindex>. Extensiile sunt, \u00een esen\u021b\u0103, un mecanism de plugin-uri care permite crearea de extensii pentru solu\u021biile aplica\u021biilor, f\u0103r\u0103 a modifica aplica\u021biile \u00een sine. Extragerea API-ului de integrare \u00een extensia de configurare va evita dificult\u0103\u021bile \u00een combinarea configura\u021biilor atunci c\u00e2nd se trece la o nou\u0103 versiune a solu\u021biei standard.\n<\/li>\n<li>Utilizarea mecanismelor de integrare ale platformei, care ofer\u0103 acces extern la modelul obiectual al aplica\u021biei \u0219i nu necesit\u0103 modific\u0103ri ale aplica\u021biei sau crearea unei extensii. Avantajul acestui abord\u0103ri este c\u0103 nu trebuie s\u0103 modific\u0103m aplica\u021bia 1C. Dezavantajul este c\u0103, dac\u0103 aplica\u021bia 1C a fost modificat\u0103, pot fi necesare ajust\u0103ri \u00een aplica\u021bia integrat\u0103. Un exemplu al acestui tip de abordare este utilizarea protocolului OData pentru integrare, implementat pe partea platformei 1C:Enterprise (mai multe detalii despre acesta mai jos).\n<\/li>\n<li>Utilizarea protocoalelor aplica\u021biilor deja existente, implementate \u00een solu\u021biile standard 1C. Multe solu\u021bii standard de la 1C \u0219i parteneri implementeaz\u0103, pe baza mecanismelor de integrare furnizate de platform\u0103, propriile protocoale aplica\u021biei, orientate c\u0103tre sarcini specifice. Atunci c\u00e2nd utiliz\u0103m aceste mecanisme, nu este necesar\u0103 scrierea de cod pe partea aplica\u021biei 1C, deoarece beneficiem de func\u021bionalit\u0103\u021bile standard ale solu\u021biei aplica\u021biei. Pe partea aplica\u021biei 1C, trebuie doar s\u0103 facem anumite configur\u0103ri.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Mecanismele de integrare din platforma 1C:Enterprise<\/h3>\n<p><\/p>\n<h4>Import\/Export de fi\u0219iere<\/h4>\n<p>\nS\u0103 presupunem c\u0103 avem de-a face cu sarcina de a realiza un schimb de date bidirec\u021bional \u00eentre aplica\u021bia 1C \u0219i o aplica\u021bie arbitrara. De exemplu, trebuie s\u0103 sincroniz\u0103m lista de produse (catalogul Nomenclatur\u0103) \u00eentre aplica\u021bia 1C \u0219i o aplica\u021bie arbitrar\u0103.<\/p>\n<p><img decoding=\"async\" alt=\"Modalit\u0103\u021bi de integrare cu 1C\" src=\"\/wp-content\/uploads\/2019\/08\/9678f09dfcf7f70de100ed74ada6019c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nPentru a rezolva aceast\u0103 sarcin\u0103, se poate scrie o extensie, care export\u0103 catalogul Nomenclatur\u0103 \u00eentr-un fi\u0219ier de un anumit format (text, XML, JSON, \u2026) \u0219i poate citi acest format. <\/p>\n<p>Platforma implementa un mecanism de serializare a obiectelor aplica\u021biei \u00een XML at\u00e2t direct, prin metodele contextului global ScrieXML\/LeerXML, c\u00e2t \u0219i prin intermediul unui obiect auxiliar XDTO (XML Data Transfer Objects).<\/p>\n<p>Orice obiect din sistemul 1C:Enterprise poate fi serializat \u00een reprezentarea XML \u0219i invers. <\/p>\n<p>Aceast\u0103 func\u021bie va returna reprezentarea obiectului sub form\u0103 de XML:<\/p>\n<pre><code class=\"1c\">Func\u021bia Obiect_V_XML(Obiect)\n    \u00cenregistrareXML = Nou\u0103 \u00cenregistrareXML();\n    \u00cenregistrareXML.SetString();\n    ScrieXML(\u00cenregistrareXML, Obiect);\n    \u00centoarce \u00cenregistrareXML.Close();\nSf\u00e2r\u0219itulFunc\u021biei\n<\/code><\/pre>\n<p>\na\u0219a va ar\u0103ta exportul catalogului Nomenclatur\u0103 \u00een XML folosind XDTO:<\/p>\n<pre><code class=\"1c\">&amp;AtServer\nProcedur\u0103 ExportXMLPeServer()\n\tNouSerealizatorXDTO  = SerealizatorXDTO;\n\tNou\u0103\u00cenregistrareXML = Nou\u0103 \u00cenregistrareXML();\n\tNou\u0103\u00cenregistrareXML.OpenFile(\"C:DataNomenclatura.xml\", \"UTF-8\");\n\t\n\tNou\u0103\u00cenregistrareXML.WriteXMLDeclaration();\n\tNou\u0103\u00cenregistrareXML.WriteStartElement(\"CatalogNomenclatur\u0103\");\n\t\n\tSelec\u021bie = Cataloguri.Nomenclatur\u0103.Select();\n\t\n\t\u00cen timp ce Selec\u021bie.Next() Ciclul \n\t\tObiectNomenclatur\u0103 = Selec\u021bie.GetObject();\n\t\tNouSerealizatorXDTO.WriteXML(Nou\u0103\u00cenregistrareXML, ObiectNomenclatur\u0103, TipDestina\u021bieXML.Declarativ);\n\tSf\u00e2r\u0219itulCiclului;\n\t\n\tNou\u0103\u00cenregistrareXML.WriteEndElement();\n\tNou\u0103\u00cenregistrareXML.Close();\t\nSf\u00e2r\u0219itulProcedurii\n<\/code><\/pre>\n<p>\nPrintr-o simpl\u0103 adaptare a codului, export\u0103m catalogul \u00een JSON. Produsele vor fi scrise \u00eentr-un array; pentru diversitate, vom prezenta varianta \u00een englez\u0103 a sintaxei:<\/p>\n<pre><code class=\"1c\">&amp;AtServer\nProcedur\u0103 ExportJSONPeServer()\n\tNouSerealizatorXDTO  = SerealizatorXDTO;\n\tNouScriitorJSON = Nou ScriitorJSON();\n\tNouScriitorJSON.OpenFile(\"C:DataNomenclatura.json\", \"UTF-8\");\n\t\n\tNouScriitorJSON.WriteStartObject();\n\tNouScriitorJSON.WritePropertyName(\"CatalogNomenclatur\u0103\");\n\tNouScriitorJSON.WriteStartArray();\n\t\n\tSelec\u021bie = Cataloguri.Nomenclatur\u0103.Select();\t\n\t\n\t\u00cen timp ce Selec\u021bie.Next() F\u0103 \n\t\tObiectNomenclatur\u0103 = Selec\u021bie.GetObject();\n\t\t\n\t\tNouScriitorJSON.WriteStartObject();\n\t\t\n\t\tNouScriitorJSON.WritePropertyName(\"Nomenclatur\u0103\");\n\t\tNouSerealizatorXDTO.WriteJSON(NouScriitorJSON, ObiectNomenclatur\u0103, TipAsignmentXML.Implicit);\n\t\t\n\t\tNouScriitorJSON.WriteEndObject();\n\tSf\u00e2r\u0219itulF\u0103;\n\t\n\tNouScriitorJSON.WriteEndArray();\n\tNouScriitorJSON.WriteEndObject();\n\tNouScriitorJSON.Close();\t\nSf\u00e2r\u0219itulProcedurii\n<\/code><\/pre>\n<p>\nApoi va r\u0103m\u00e2ne doar s\u0103 transmi\u021bi datele consumatorului final. Platforma 1C:Enterprise suport\u0103 principalele protocoale internet HTTP, FTP, POP3, SMTP, IMAP, inclusiv versiunile lor sigure. De asemenea, pentru transferul de date se pot folosi HTTP \u0219i\/sau Web-servicii.<\/p>\n<h4>Servicii HTTP \u0219i web<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Modalit\u0103\u021bi de integrare cu 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1d4797d9298f793e19ee637fd26473b2.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Aplica\u021biile 1C pot implementa propriile servicii HTTP \u0219i web, precum \u0219i apela servicii HTTP \u0219i web implementate de aplica\u021bii externe. <\/p>\n<h4>Interfa\u021ba REST \u0219i protocolul OData<\/h4>\n<p>\n\u00cencep\u00e2nd cu versiunea 8.3.5, platforma 1C:Enterprise poate genera automat <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/avtomaticheskiy-rest-interfeys-prikladnykh-resheniy\/\">interfa\u021ba REST<\/a><\/noindex> pentru \u00eentreaga solu\u021bie aplica\u021bional\u0103. Orice obiect de configurare (catalog, document, registru de informa\u021bii etc.) poate fi accesibil pentru ob\u021binerea \u0219i modificarea datelor prin intermediul interfe\u021bei REST. \u00cen calitate de protocol de acces, platforma utilizeaz\u0103 protocol <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Open_Data_Protocol\">OData<\/a><\/noindex> versiunea 3.0. Publicarea serviciilor OData se face din meniul Configuratorului \u201eAdministrare -&gt; Publicare pe serverul web\u201d, bifeaz\u0103 op\u021biunea \u201ePublicare interfa\u021b\u0103 standard OData\u201d. Sunt acceptate formatele atom\/XML \u0219i JSON. Dup\u0103 ce solu\u021bia aplicativ\u0103 este publicat\u0103 pe serverul web, sistemele externe pot accesa aceasta printr-o interfa\u021b\u0103 REST utiliz\u00e2nd cereri HTTP. Pentru a lucra cu aplica\u021bia 1C prin protocolul OData, nu este necesar programarea pe partea de 1C.<\/p>\n<p>Astfel, URL-ul de forma <u>http:\/\/&lt;server&gt;\/&lt;configura\u021bie&gt;\/odata\/standard.odata\/Catalog_Produs<\/u> ne va returna con\u021binutul catalogului Produs \u00een format XML \u2014 o colec\u021bie de elemente entry (antetul mesajului este omis pentru concizie):<\/p>\n<pre><code class=\"xml\">&lt;entry&gt;\n\t&lt;id&gt;http:\/\/server\/Config\/odata\/standard.odata\/Catalog_Produs(guid'35d1f6e4-289b-11e6-8ba4-e03f49b16074')&lt;\/id&gt;\n\t&lt;category term=\"StandardODATA.Catalog_Produs\" scheme=\"http:\/\/schemas.microsoft.com\/ado\/2007\/08\/dataservices\/scheme\"\/&gt;\n\t&lt;title type=\"text\"\/&gt;\n\t&lt;updated&gt;2016-06-06T16:42:17&lt;\/updated&gt;\n\t&lt;author\/&gt;\n\t&lt;summary\/&gt;\n\t&lt;link rel=\"edit\" href=\"Catalog_Produs(guid'35d1f6e4-289b-11e6-8ba4-e03f49b16074')\" title=\"edit-link\"\/&gt;\n\t&lt;content type=\"application\/xml\"&gt;\n\t\t&lt;m:properties&gt;\n\t\t\t&lt;d:Ref_Key&gt;35d1f6e4-289b-11e6-8ba4-e03f49b16074&lt;\/d:Ref_Key&gt;\n\t\t\t&lt;d:DataVersion&gt;AAAAAgAAAAA=&lt;\/d:DataVersion&gt;\n\t\t\t&lt;d:DeletionMark&gt;false&lt;\/d:DeletionMark&gt;\n\t\t\t&lt;d:Code&gt;000000001&lt;\/d:Code&gt;\n\t\t\t&lt;d:Description&gt;Aer condi\u021bionat Mitsubishi&lt;\/d:Description&gt;\n\t\t\t&lt;d:Descriere&gt;Putere 2,5 kW, moduri de func\u021bionare: c\u0103ldur\u0103\/rece&lt;\/d:Descriere&gt;\n\t\t&lt;\/m:properties&gt;\n\t&lt;\/content&gt;\n&lt;\/entry&gt;\n&lt;entry&gt;\n\t&lt;id&gt;http:\/\/server\/Config\/odata\/standard.odata\/Catalog_Produs(guid'35d1f6e5-289b-11e6-8ba4-e03f49b16074')&lt;\/id&gt;\n\t&lt;category term=\"StandardODATA.Catalog_Produs\" scheme=\"http:\/\/schemas.microsoft.com\/ado\/2007\/08\/dataservices\/scheme\"\/&gt;\n...\n<\/code><\/pre>\n<p>\nAd\u0103ug\u00e2nd la URL \u0219irul \u201e?$format=application\/json\u201d, vom ob\u021bine con\u021binutul catalogului Produs \u00een format JSON (URL de forma <u>http:\/\/&lt;server&gt;\/&lt;configura\u021bie&gt;\/odata\/standard.odata\/Catalog_Produs?$format=application\/json<\/u> ):<\/p>\n<pre><code>{\n\"odata.metadata\": \"http:\/\/server\/Config\/odata\/standard.odata\/$metadata#Catalog_Produs\",\n\"value\": [{\n\"Ref_Key\": \"35d1f6e4-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAgAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000001\",\n\"Description\": \"Aer condi\u021bionat Mitsubishi\",\n\"Descriere\": \"Putere 2,5 kW, moduri de func\u021bionare: c\u0103ldur\u0103\/rece\"\n},{\n\"Ref_Key\": \"35d1f6e5-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAwAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000002\",\n\"Description\": \"Aer condi\u021bionat Daikin\",\n\"Descriere\": \"Putere 3 kW, moduri de func\u021bionare: c\u0103ldur\u0103\/rece\"\n}, \u2026\n<\/code><\/pre>\n<p><\/p>\n<h4>Surse externe de date<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Modalit\u0103\u021bi de integrare cu 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1663b53846f3a6a8a03f386f1f6cd311.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u00cen unele cazuri, schimbul de date prin <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000795.htm\">surse externe de date<\/a><\/noindex> poate fi solu\u021bia optim\u0103. Sursele externe de date sunt un obiect aplicativ de configurare 1C, care permite interac\u021biunea cu orice baz\u0103 de date compatibil\u0103 ODBC at\u00e2t pentru citire, c\u00e2t \u0219i pentru scriere. Sursele externe de date sunt disponibile at\u00e2t pe Windows, c\u00e2t \u0219i pe Linux.<\/p>\n<h4>Mecanismul de schimb de date<\/h4>\n<p>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000269.htm\">Mecanismul de schimb de date<\/a><\/noindex> este destinat at\u00e2t pentru crearea de sisteme distribuite geografic bazate pe 1C:Enterprise, c\u00e2t \u0219i pentru organizarea schimbului de date cu alte sisteme informa\u021bionale, care nu se bazeaz\u0103 pe 1C:Enterprise.<\/p>\n<p>Acest mecanism este folosit activ \u00een implement\u0103rile 1C, iar spectrul de sarcini rezolvate cu ajutorul acestuia este foarte larg. Acesta include schimbul de date \u00eentre aplica\u021biile 1C instalate \u00een filialele organiza\u021biei, schimbul \u00eentre aplica\u021bia 1C \u0219i site-ul magazinului online, \u0219i schimbul de date \u00eentre aplica\u021bia server 1C \u0219i clientul mobil (creat cu ajutorul platformei mobile 1C:Enterprise), \u0219i multe altele.<\/p>\n<p>Unul dintre conceptele cheie \u00een mecanismul de schimb de date este planul de schimb. Planul de schimb este un tip special de obiect aplicativ al platformei 1C, care define\u0219te, printre altele, compozi\u021bia datelor care vor participa la schimb (care anume registri, documente, \u0219i altele). Planul de schimb con\u021bine de asemenea informa\u021bii despre participan\u021bii la schimb (a\u0219a-numitele noduri de schimb).<br \/>\nA doua component\u0103 a mecanismului de schimb de date este mecanismul de \u00eenregistrare a modific\u0103rilor. Acest mecanism urm\u0103re\u0219te automat \u00een sistem modific\u0103rile de date care trebuie transmise consumatorilor finali \u00een cadrul planului de schimb. Cu ajutorul acestui mecanism, platforma urm\u0103re\u0219te modific\u0103rile care au avut loc de la ultima sincronizare \u0219i permite minimizarea volumului de date transmise \u00een cadrul urm\u0103toarei sesiuni de sincronizare.<\/p>\n<p>Schimbul de date se realizeaz\u0103 prin intermediul mesajelor XML cu o structur\u0103 specific\u0103. Mesajul con\u021bine datele care s-au modificat de la ultima sincronizare cu nodul \u0219i anumite informa\u021bii de servicii. Structura mesajelor suport\u0103 numerotarea mesajelor \u0219i permite primirea de confirm\u0103ri de la nodul receptor cu privire la primirea mesajelor. Aceast\u0103 confirmare este inclus\u0103 \u00een fiecare mesaj care vine de la nodul receptor sub forma num\u0103rului ultimului mesaj primit. Numerotarea mesajelor permite platformei s\u0103 \u00een\u021beleag\u0103 ce date au fost deja transferate cu succes la nodul receptor \u0219i s\u0103 evite retransmiterea, trimi\u021b\u00e2nd doar datele care s-au schimbat de la primirea ultimului mesaj de c\u0103tre nodul expeditor, care are o confirmare a datelor primite de nodul receptor. Aceast\u0103 schem\u0103 de lucru garanteaz\u0103 livrarea chiar \u0219i \u00een condi\u021bii de canal de transmisie nesigure \u0219i pierdere de mesaje.<\/p>\n<h4>Componente externe<\/h4>\n<p>\n\u00cen anumite cazuri, \u00een solu\u021bionarea sarcinilor de integrare, este necesar s\u0103 se fac\u0103 fa\u021b\u0103 cerin\u021belor specifice, cum ar fi protocoalele de interac\u021biune, formatele de date cu care platforma 1C:Enterprise nu prevede lucrul. Pentru aceast\u0103 categorie de sarcini, platforma prevede <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000545.htm\">tehnologia componentelor externe<\/a><\/noindex>, care permite crearea de module conectabile dinamic, extinz\u00e2nd func\u021bionalitatea 1C:Enterprise. <\/p>\n<p>Un exemplu tipic de sarcin\u0103 cu astfel de cerin\u021be poate fi integrarea solu\u021biei aplica\u021bionale 1C cu echipamente comerciale, \u00eencep\u00e2nd de la c\u00e2ntare \u0219i termin\u00e2nd cu casele de marcat \u0219i scanerele de coduri de bare. Componentele externe pot fi conectate at\u00e2t pe partea serverului 1C:Enterprise, c\u00e2t \u0219i pe partea clientului (inclusiv, de exemplu, \u0219i clientul web, precum \u0219i <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/vneshnie-komponenty-v-mobilnom-prilozhenii\/\">urm\u0103toarea versiune a platformei mobile<\/a><\/noindex> 1C:Enterprise). Tehnologia componentelor externe prevede un interfa\u021b\u0103 de programare (C++) destul de simpl\u0103 \u0219i clar\u0103 pentru interac\u021biunea componentei cu platforma 1C:Enterprise, care trebuie s\u0103 fie realizat\u0103 de dezvoltator.<\/p>\n<p>Posibilit\u0103\u021bile deschise prin utilizarea componentelor externe sunt foarte largi. Se poate realiza interac\u021biunea printr-un protocol specific de schimb de date cu dispozitive externe \u0219i sisteme, se pot integra algoritmi specifici de procesare a datelor \u0219i formate de date etc.<\/p>\n<h4>Mecanisme de integrare dep\u0103\u0219ite<\/h4>\n<p>\nPlatforma ofer\u0103 mecanisme de integrare care nu sunt recomandate pentru utilizare \u00een solu\u021biile noi; aceste mecanisme sunt men\u021binute din motive de compatibilitate retrograd\u0103, dar \u0219i \u00een cazul \u00een care cealalt\u0103 parte nu poate lucra cu protocoale mai moderne. Unul dintre acestea este lucrul cu fi\u0219iere \u00een format DBF (sus\u021binut \u00een limbajul \u00eencorporat prin obiectul XBase).<\/p>\n<p>Un alt mecanism de integrare dep\u0103\u0219it este utilizarea tehnologiei COM (disponibil\u0103 doar pe platforma Windows). Platforma 1C:Enterprise ofer\u0103 dou\u0103 moduri de integrare pentru Windows, folosind tehnologia COM: server de automatizare \u0219i conexiune extern\u0103. Acestea sunt foarte asem\u0103n\u0103toare, dar una dintre principalele diferen\u021be este c\u0103, \u00een cazul serverului de automatizare, se lanseaz\u0103 o aplica\u021bie client 1C:Enterprise 8 complet\u0103, iar \u00een cazul conexiunii externe, se lanseaz\u0103 un server COM de proces relativ mic. Asta \u00eenseamn\u0103 c\u0103, atunci c\u00e2nd se lucreaz\u0103 prin serverul de automatizare, se poate utiliza func\u021bionalitatea aplica\u021biei client, efectu\u00e2nd ac\u021biuni similare cu cele interactive ale utilizatorului. C\u00e2nd se utilizeaz\u0103 conexiunea extern\u0103, se pot folosi doar func\u021biile logicii de afaceri, care pot fi realizate at\u00e2t pe partea clientului conexiunii, unde se creeaz\u0103 serverul COM de proces, c\u00e2t \u0219i apel\u00e2nd logica de afaceri pe serverul 1C:Enterprise.<\/p>\n<p>De asemenea, tehnologia COM poate fi utilizat\u0103 pentru a accesa sisteme externe din codul aplica\u021biei pe platforma 1C:Enterprise. \u00cen acest caz, aplica\u021bia 1C ac\u021bioneaz\u0103 ca un client COM. Trebuie re\u021binut c\u0103 aceste mecanisme vor func\u021biona doar dac\u0103 serverul 1C func\u021bioneaz\u0103 \u00eentr-un mediu Windows.<\/p>\n<h3>Mecanismele de integrare implementate \u00een configura\u021biile standard<\/h3>\n<p><\/p>\n<h4>Formatul EnterpriseData<\/h4>\n<p>\n<img decoding=\"async\" alt=\"Modalit\u0103\u021bi de integrare cu 1C\" src=\"\/wp-content\/uploads\/2019\/08\/8930091e53309b9b808a719b747a6226.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n\u00centr-o serie de configura\u021bii 1C (lista de mai jos), pe baza mecanismului de schimb de date descris mai sus, a fost realizat un mecanism de schimb de date cu aplica\u021bii externe, f\u0103r\u0103 a necesita modific\u0103ri ale codului surs\u0103 al configura\u021biilor (preg\u0103tirea pentru schimbul de date se face \u00een set\u0103rile solu\u021biilor aplicative):<\/p>\n<ul>\n<li>\u201e1C:ERP Managementul \u00eentreprinderii 2.0\u201d <\/li>\n<li>\u201eAutomatizare complex\u0103 2\u201d <\/li>\n<li>\u201eContabilitatea \u00eentreprinderii\u201d, edi\u021bia 3.0 <\/li>\n<li>\u201eContabilitatea \u00eentreprinderii CORP\u201d, edi\u021bia 3.0 <\/li>\n<li>\u201eRetail\u201d, edi\u021bia 2.0 <\/li>\n<li>\u201eGestionarea comer\u021bului de baz\u0103\u201d, edi\u021bia 11 <\/li>\n<li>\u201eGestionarea comer\u021bului\u201d, edi\u021bia 11<\/li>\n<li>\u201eSalarii \u0219i managementul resurselor umane CORP\u201d, edi\u021bia 3<\/li>\n<\/ul>\n<p>\nPentru schimbul de date se folose\u0219te formatul <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_app\/enterprisedata\/\">EnterpriseData<\/a><\/noindex>, bazat pe XML. Formatul este orientat c\u0103tre afaceri - structurile de date descrise corespund entit\u0103\u021bilor de afaceri (documentelor \u0219i elementelor din directoare) prezente \u00een programele 1C, de exemplu: act de lucr\u0103ri finalizate, ordin de \u00eencasare, contraentitate, nomenclatur\u0103 etc.<\/p>\n<p>Schimbul de date \u00eentre aplica\u021bia 1C \u0219i o aplica\u021bie extern\u0103 se poate realiza:<\/p>\n<ul>\n<li>printr-un director de fi\u0219iere dedicat <\/li>\n<li>printr-un director FTP <\/li>\n<li>printr-un serviciu web, instalat pe partea aplica\u021biei 1C. Fi\u0219ierul cu date este transmis ca parametru al metodelor web<\/li>\n<li>prin email<\/li>\n<\/ul>\n<p>\n\u00cen cazul schimbului prin serviciul web, aplica\u021bia extern\u0103 va ini\u021bia sesiunea de schimb de date prin apelarea metodelor web corespunz\u0103toare ale aplica\u021biei 1C. \u00cen celelalte cazuri, ini\u021biatorul sesiunii de schimb va fi aplica\u021bia 1C (prin plasarea fi\u0219ierului cu date \u00een directorul corespunz\u0103tor sau trimiterea fi\u0219ierului cu date la adresa de email configurat\u0103).<br \/>\nDe asemenea, pe partea 1C se configureaz\u0103 la ce frecven\u021b\u0103 se va realiza sincronizarea (pentru variantele cu schimb de fi\u0219iere prin director \u0219i email):<\/p>\n<ul>\n<li>conform unui program (cu o frecven\u021b\u0103 specificat\u0103) <\/li>\n<li>manual; utilizatorul va trebui s\u0103 lanseze manual sincronizarea de fiecare dat\u0103 c\u00e2nd va avea nevoie<\/li>\n<\/ul>\n<p><\/p>\n<h5>Confirmarea mesajelor<\/h5>\n<p>\nAplica\u021biile 1C \u021bin eviden\u021ba mesajelor de sincronizare trimise \u0219i primite \u0219i a\u0219teapt\u0103 acela\u0219i lucru din partea aplica\u021biilor externe. Acest lucru permite utilizarea mecanismului de numerotare a mesajelor, descris mai sus \u00een sec\u021biunea \u201eMecanismul de schimb de date\u201d.<\/p>\n<p>Aplica\u021biile 1C, \u00een timpul sincroniz\u0103rii, transmit doar informa\u021biile despre schimb\u0103rile ap\u0103rute \u00een entit\u0103\u021bile de afaceri din timpul ultimei sincroniz\u0103ri (pentru a minimiza volumul de informa\u021bii transmise). La prima sincronizare, aplica\u021bia 1C va expedia toate entit\u0103\u021bile de afaceri (de exemplu, elementele din catalogul produselor) \u00een formatul EnterpriseData \u00eentr-un fi\u0219ier XML (deoarece toate acestea sunt \u201enoi\u201d pentru aplica\u021bia extern\u0103). Aplica\u021bia extern\u0103 trebuie s\u0103 proceseze informa\u021biile din fi\u0219ierul XML primit de la 1C \u0219i, la urm\u0103toarea sesiune de sincronizare, s\u0103 plaseze \u00een fi\u0219ierul trimis c\u0103tre 1C, \u00eentr-o sec\u021biune special\u0103 XML, informa\u021bia c\u0103 mesajul de la 1C cu un anumit num\u0103r a fost primit cu succes. Mesajul de confirmare reprezint\u0103 pentru aplica\u021bia 1C un semnal c\u0103 toate entit\u0103\u021bile de afaceri au fost procesate cu succes de aplica\u021bia extern\u0103 \u0219i nu mai este necesar\u0103 transmiterea de informa\u021bii despre acestea. Pe l\u00e2ng\u0103 confirmare, fi\u0219ierul XML al aplica\u021biei externe poate con\u021bine, de asemenea, date pentru sincronizarea din partea aplica\u021biei (de exemplu, documente de livrare a bunurilor \u0219i serviciilor).<\/p>\n<p>Dup\u0103 primirea mesajului de confirmare, aplica\u021bia 1C marcheaz\u0103 toate schimb\u0103rile transmise \u00een mesajul anterior ca fiind sincronizate cu succes. Numai schimb\u0103rile nesincronizate \u00een entit\u0103\u021bile de afaceri (crearea de entit\u0103\u021bi noi, modificarea \u0219i \u0219tergerea celor existente) vor fi trimise aplica\u021biei externe la urm\u0103toarea sesiune de sincronizare.<\/p>\n<p><img decoding=\"async\" alt=\"Modalit\u0103\u021bi de integrare cu 1C\" src=\"\/wp-content\/uploads\/2019\/08\/b0d5509a53909e38886a15c2e03e7131.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nAtunci c\u00e2nd datele sunt transmise de la aplica\u021bia extern\u0103 c\u0103tre aplica\u021bia 1C, situa\u021bia se inverseaz\u0103. Aplica\u021bia extern\u0103 trebuie s\u0103 completeze sec\u021biunea de confirmare \u00een fi\u0219ierul XML \u00een mod corespunz\u0103tor \u0219i s\u0103 plaseze datele de afaceri pentru sincronizare din partea sa \u00een formatul EnterpriseData.<\/p>\n<p><img decoding=\"async\" alt=\"Modalit\u0103\u021bi de integrare cu 1C\" src=\"\/wp-content\/uploads\/2019\/08\/d34b96efb7591770133b363b369c0019.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h5>Schimb de date simplificat f\u0103r\u0103 confirmare<\/h5>\n<p>\nPentru cazurile de integrare simpl\u0103, c\u00e2nd este suficient s\u0103 se transmit\u0103 informa\u021bia de la aplica\u021bia extern\u0103 c\u0103tre aplica\u021bia 1C \u0219i nu este necesar\u0103 o retur de date din aplica\u021bia 1C c\u0103tre aplica\u021bia extern\u0103 (de exemplu, integrarea unui magazin online care transmite informa\u021bii despre v\u00e2nz\u0103ri c\u0103tre \u201e1C:Contabilitate\u201d), exist\u0103 o variant\u0103 simplificat\u0103 de lucru prin intermediul unui serviciu web (f\u0103r\u0103 confirmare), care nu necesit\u0103 set\u0103ri pe partea aplica\u021biei 1C.<\/p>\n<h4>Solu\u021bii de integrare specializate<\/h4>\n<p>\nExist\u0103 o solu\u021bie standard \u201e1C: Conversia datelor\u201d, care utilizeaz\u0103 mecanismele platformei pentru conversia \u0219i schimbul de date \u00eentre configura\u021biile standard 1C, dar poate fi utilizat\u0103 \u0219i pentru integrarea cu aplica\u021bii externe.<\/p>\n<h5>Integrarea cu solu\u021biile bancare<\/h5>\n<p>\nStandard <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/100\/index.htm\">\u201eClient bancar\u201d<\/a><\/noindex>, dezvoltat\u0103 de speciali\u0219tii 1C acum mai bine de 10 ani, a devenit practic un standard al industriei \u00een Rusia. Pasul urm\u0103tor \u00een aceast\u0103 direc\u021bie este tehnologia <noindex><a rel=\"nofollow\" href=\"http:\/\/directbank.1c.ru\/\">DirectBank<\/a><\/noindex>, care permite trimiterea documentelor de plat\u0103 c\u0103tre banc\u0103 \u0219i primirea extraselor din banc\u0103 direct din programele sistemului \u201e1C: Enterprise\u201d cu o simpl\u0103 ap\u0103sare de buton \u00een programul \u201e1C\u201d; \u00een acest caz, nu este necesar\u0103 instalarea \u0219i rularea unor programe suplimentare pe computerul clientului. <\/p>\n<p>Exist\u0103 de asemenea <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/109\/\">un standard pentru schimbul de date \u00een proiectele de salarii<\/a><\/noindex>.<\/p>\n<h5>Altele<\/h5>\n<p>\nMerit\u0103 men\u021bionate <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/131\/\">protocolul de schimb \u00eentre sistemul 1C: Enterprise \u0219i site-ul<\/a><\/noindex>, standardul de schimb al informa\u021biilor comerciale <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/90\/\">CommerceML<\/a><\/noindex> (dezvoltat \u00eempreun\u0103 cu Microsoft, Intel, Price.ru \u0219i alte companii), <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/111\/\">standardul de schimb al datelor pentru opera\u021biunile de achizi\u021bie<\/a><\/noindex>.<br \/>\n<br \/>Sursa: <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\/ro\/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=\"ro_RO\" \/>\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\/ro\/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\udd47Modalit\u0103\u021bi de integrare cu 1C | ProHoster","description":"Care sunt cele mai importante cerin\u021be pentru aplica\u021biile de afaceri?","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/sposoby-integratsii-s-1s","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\/ro\/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\/ro\/wp-json\/wp\/v2\/posts\/36968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=36968"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/36968\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media\/27703"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=36968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=36968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=36968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}