{"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\/no\/blog\/administrirovanie\/sposoby-integratsii-s-1s","title":{"rendered":"M\u00e5ter \u00e5 integrere med 1C","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Hva er de viktigste kravene til forretningsapplikasjoner? Noen av de mest sentrale inkluderer f\u00f8lgende oppgaver:<\/p>\n<ul>\n<li>Letthet i \u00e5 endre\/tilpasse applikasjonens logikk til skiftende forretningsbehov.<\/li>\n<li>Letthet i integrasjon med andre applikasjoner.<\/li>\n<\/ul>\n<p>\nHvordan den f\u00f8rste oppgaven l\u00f8ses i 1C, ble kort beskrevet i seksjonen \u00abTilpasning og st\u00f8tte\u00bb; <noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1c\/blog\/267321\/\">this article<\/a><\/noindex>vi vil komme tilbake til dette interessante emnet i en av fremtidige artikler. I dag skal vi snakke om den andre oppgaven, integrasjon.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Integrasjonsoppgaver<\/h3>\n<p>\nIntegrasjonsoppgavene kan v\u00e6re forskjellige. For \u00e5 l\u00f8se enkelte oppgaver er det tilstrekkelig med en enkel interaktiv datautveksling \u2013 for eksempel for \u00e5 sende en liste over ansatte til banken for utstedelse av l\u00f8nnskort. For mer komplekse oppgaver kan det v\u00e6re n\u00f8dvendig med en helt automatisert datautveksling, muligens med henvisning til forretningslogikken i det eksterne systemet. Det finnes ogs\u00e5 spesialiserte oppgaver, som integrasjon med eksternt utstyr (for eksempel betalingssystemer, mobile skannere osv.) eller med arvet eller spesialiserte systemer (for eksempel RFID-lesesystemer). Det er avgj\u00f8rende \u00e5 velge den mest hensiktsmessige integrasjonsmekanismen for hver oppgave.<\/p>\n<h3>Integrasjonsmuligheter med 1C<\/h3>\n<p>\nDet finnes ulike tiln\u00e6rminger til \u00e5 implementere integrasjon med 1C-applikasjoner, hvilken som velges avhenger av kravene til oppgaven.<\/p>\n<ol>\n<li>Implementering basert p\u00e5 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000581.htm\">integrasjonsmekanismer<\/a><\/noindex>, levert av plattformen, eller sitt eget spesialiserte API p\u00e5 siden av 1C-applikasjonen (for eksempel en serie Web- eller HTTP-tjenester som vil bli kalt av tredjepartsapplikasjoner for datautveksling med 1C-applikasjonen). Fordelen med denne tiln\u00e6rmingen er robustheten til API-et mot endringer i implementeringen p\u00e5 siden av 1C-applikasjonen. En s\u00e6rtrekk ved tiln\u00e6rmingen er at det kreves endringer i kildekoden til den typiske l\u00f8sningen i 1C, noe som potensielt kan kreve innsats ved sammensl\u00e5ing av kildekodene n\u00e5r man g\u00e5r over til en ny konfigurasjonsversjon. I dette tilfellet kan ny progresiv funksjonalitet komme til hjelp \u2013 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000883.htm\">konfigurasjonsutvidelser<\/a><\/noindex>. Utvidelser er i essensen en plugin-mekanisme som gj\u00f8r det mulig \u00e5 lage tillegg til applikasjonsl\u00f8sninger uten \u00e5 endre selve applikasjonsl\u00f8sningene. \u00c5 flytte integrasjons-API-en til konfigurasjonsutvidelsen vil unng\u00e5 komplikasjoner ved sammensl\u00e5ing av konfigurasjoner n\u00e5r man g\u00e5r over til en ny versjon av standardl\u00f8sningen.\n<\/li>\n<li>Bruken av integrasjonsmekanismer fra plattformen som gir ekstern tilgang til objektmodellen i applikasjonen uten at det kreves endringer i applikasjonen eller opprettelse av utvidelser. Fordelen med denne tiln\u00e6rmingen er at man ikke trenger \u00e5 endre 1C-applikasjonen. Ulempen er at hvis 1C-applikasjonen har blitt modifisert, kan det v\u00e6re n\u00f8dvendig med tilpasninger i den integrerte applikasjonen. Et eksempel p\u00e5 en slik tiln\u00e6rming er bruk av OData-protokollen for integrasjonen, implementert p\u00e5 1C:Enterprise-plattformen (mer om det nedenfor).\n<\/li>\n<li>Bruk av ferdige applikasjonsprotokoller implementert i standardl\u00f8sninger fra 1C. Mange standardl\u00f8sninger fra 1C og partnere implementerer sine egne applikasjonsprotokoller basert p\u00e5 integrasjonsmekanismene som tilbys av plattformen, og disse er rettet mot spesifikke oppgaver. N\u00e5r man bruker disse mekanismene, er det ikke n\u00f8dvendig \u00e5 skrive kode p\u00e5 1C-applikasjonssiden, da vi benytter de innebygde mulighetene til applikasjonsl\u00f8sningen. P\u00e5 1C-applikasjonen m\u00e5 vi bare utf\u00f8re visse innstillinger.<\/li>\n<\/ol>\n<p><\/p>\n<h3>Integrasjonsmekanismer i 1C:Enterprise-plattformen<\/h3>\n<p><\/p>\n<h4>Import\/eksport av filer<\/h4>\n<p>\nLa oss anta at vi st\u00e5r overfor oppgaven med toveiskommunikasjon mellom 1C-applikasjonen og en vilk\u00e5rlig applikasjon. For eksempel trenger vi \u00e5 synkronisere produktlisten (Oppslagsord Nomenklatur) mellom 1C-applikasjonen og en vilk\u00e5rlig applikasjon.<\/p>\n<p><img decoding=\"async\" alt=\"M\u00e5ter \u00e5 integrere med 1C\" src=\"\/wp-content\/uploads\/2019\/08\/9678f09dfcf7f70de100ed74ada6019c.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nFor \u00e5 l\u00f8se denne oppgaven kan vi skrive en utvidelse som eksporterer oppslagsord Nomenklatur til en fil i et bestemt format (tekst, XML, JSON, \u2026) og kan lese dette formatet. <\/p>\n<p>Plattformen har implementert en mekanisme for serialisering av applikasjonsobjekter til XML b\u00e5de direkte, gjennom metodene i global kontekst SkriveXML\/LeseXML, og ved hjelp av et hjelpeobjekt XDTO (XML Data Transfer Objects).<\/p>\n<p>Ethvert objekt i 1C:Enterprise-systemet kan bli serialisert til XML-representasjon og omvendt. <\/p>\n<p>Denne funksjonen vil returnere objektets representasjon i form av XML:<\/p>\n<pre><code class=\"1c\">\u0424\u0443\u043d\u043a\u0446\u0438\u044f \u041e\u0431\u044a\u0435\u043a\u0442_\u0412_XML(\u041e\u0431\u044a\u0435\u043a\u0442)\n    \u0417\u0430\u043f\u0438\u0441\u044cXML = \u041d\u043e\u0432\u044b\u0439 \u0417\u0430\u043f\u0438\u0441\u044cXML();\n    \u0417\u0430\u043f\u0438\u0441\u044cXML.\u0423\u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c\u0421\u0442\u0440\u043e\u043a\u0443();\n    \u0417\u0430\u043f\u0438\u0441\u0430\u0442\u044cXML(\u0417\u0430\u043f\u0438\u0441\u044cXML, \u041e\u0431\u044a\u0435\u043a\u0442);\n    \u0412\u043e\u0437\u0432\u0440\u0430\u0442 \u0417\u0430\u043f\u0438\u0441\u044cXML.\u0417\u0430\u043a\u0440\u044b\u0442\u044c();\n\u041a\u043e\u043d\u0435\u0446\u0424\u0443\u043d\u043a\u0446\u0438\u0438\n<\/code><\/pre>\n<p>\n\u0442\u0430\u043a \u0431\u0443\u0434\u0435\u0442 \u0432\u044b\u0433\u043b\u044f\u0434\u0435\u0442\u044c \u044d\u043a\u0441\u043f\u043e\u0440\u0442 \u0441\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u0438\u043a\u0430 \u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430 \u0432 XML \u043f\u0440\u0438 \u043f\u043e\u043c\u043e\u0449\u0438 XDTO:<\/p>\n<pre><code class=\"1c\">&amp;\u041d\u0430\u0421\u0435\u0440\u0432\u0435\u0440\u0435\n\u041f\u0440\u043e\u0446\u0435\u0434\u0443\u0440\u0430 \u042d\u043a\u0441\u043f\u043e\u0440\u0442XML\u041d\u0430\u0421\u0435\u0440\u0432\u0435\u0440\u0435()\t\n\t\u041d\u043e\u0432\u044b\u0439\u0421\u0435\u0440\u0438\u0430\u043b\u0438\u0437\u0430\u0442\u043e\u0440XDTO  = \u0421\u0435\u0440\u0438\u0430\u043b\u0438\u0437\u0430\u0442\u043e\u0440XDTO;\n\t\u041d\u043e\u0432\u0430\u044f\u0417\u0430\u043f\u0438\u0441\u044cXML = \u041d\u043e\u0432\u044b\u0439 \u0417\u0430\u043f\u0438\u0441\u044cXML();\n\t\u041d\u043e\u0432\u0430\u044f\u0417\u0430\u043f\u0438\u0441\u044cXML.\u041e\u0442\u043a\u0440\u044b\u0442\u044c\u0424\u0430\u0439\u043b(\"C:Data\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430.xml\", \"UTF-8\");\n\t\n\t\u041d\u043e\u0432\u0430\u044f\u0417\u0430\u043f\u0438\u0441\u044cXML.\u0417\u0430\u043f\u0438\u0441\u0430\u0442\u044c\u041e\u0431\u044a\u044f\u0432\u043b\u0435\u043d\u0438\u0435XML();\n\t\u041d\u043e\u0432\u0430\u044f\u0417\u0430\u043f\u0438\u0441\u044cXML.\u0417\u0430\u043f\u0438\u0441\u0430\u0442\u044c\u041d\u0430\u0447\u0430\u043b\u043e\u042d\u043b\u0435\u043c\u0435\u043d\u0442\u0430(\"\u0421\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u0438\u043a\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430\");\n\t\n\t\u0412\u044b\u0431\u043e\u0440\u043a\u0430 = \u0421\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u0438\u043a\u0438.\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430.\u0412\u044b\u0431\u0440\u0430\u0442\u044c();\n\t\n\t\u041f\u043e\u043a\u0430 \u0412\u044b\u0431\u043e\u0440\u043a\u0430.\u0421\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0439() \u0426\u0438\u043a\u043b \n\t\t\u041e\u0431\u044a\u0435\u043a\u0442\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430 = \u0412\u044b\u0431\u043e\u0440\u043a\u0430.\u041f\u043e\u043b\u0443\u0447\u0438\u0442\u044c\u041e\u0431\u044a\u0435\u043a\u0442();\n\t\t\u041d\u043e\u0432\u044b\u0439\u0421\u0435\u0440\u0438\u0430\u043b\u0438\u0437\u0430\u0442\u043e\u0440XDTO.\u0417\u0430\u043f\u0438\u0441\u0430\u0442\u044cXML(\u041d\u043e\u0432\u0430\u044f\u0417\u0430\u043f\u0438\u0441\u044cXML, \u041e\u0431\u044a\u0435\u043a\u0442\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430, \u041d\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435\u0422\u0438\u043f\u0430XML.\u042f\u0432\u043d\u043e\u0435);\n\t\u041a\u043e\u043d\u0435\u0446\u0426\u0438\u043a\u043b\u0430;\n\t\n\t\u041d\u043e\u0432\u0430\u044f\u0417\u0430\u043f\u0438\u0441\u044cXML.\u0417\u0430\u043f\u0438\u0441\u0430\u0442\u044c\u041a\u043e\u043d\u0435\u0446\u042d\u043b\u0435\u043c\u0435\u043d\u0442\u0430();\n\t\u041d\u043e\u0432\u0430\u044f\u0417\u0430\u043f\u0438\u0441\u044cXML.\u0417\u0430\u043a\u0440\u044b\u0442\u044c();\t\n\u041a\u043e\u043d\u0435\u0446\u041f\u0440\u043e\u0446\u0435\u0434\u0443\u0440\u044b\n<\/code><\/pre>\n<p>\n\u041f\u0443\u0442\u0435\u043c \u043d\u0435\u0441\u043b\u043e\u0436\u043d\u043e\u0439 \u043f\u0435\u0440\u0435\u0434\u0435\u043b\u043a\u0438 \u043a\u043e\u0434\u0430 \u044d\u043a\u0441\u043f\u043e\u0440\u0442\u0438\u0440\u0443\u0435\u043c \u0441\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u0438\u043a \u0432 JSON. \u0422\u043e\u0432\u0430\u0440\u044b \u0431\u0443\u0434\u0443\u0442 \u0437\u0430\u043f\u0438\u0441\u0430\u043d\u044b \u0432 \u043c\u0430\u0441\u0441\u0438\u0432; \u0434\u043b\u044f \u0440\u0430\u0437\u043d\u043e\u043e\u0431\u0440\u0430\u0437\u0438\u044f \u043f\u0440\u0438\u0432\u0435\u0434\u0435\u043c \u0430\u043d\u0433\u043b\u043e\u044f\u0437\u044b\u0447\u043d\u044b\u0439 \u0432\u0430\u0440\u0438\u0430\u043d\u0442 \u0441\u0438\u043d\u0442\u0430\u043a\u0441\u0438\u0441\u0430:<\/p>\n<pre><code class=\"1c\">&amp;AtServer\nProcedure ExportJSONOnServer()\n\tNewXDTOSerializer  = XDTOSerializer;\n\tNewJSONWriter = New JSONWriter();\n\tNewJSONWriter.OpenFile(\"C:Data\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430.json\", \"UTF-8\");\n\t\n\tNewJSONWriter.WriteStartObject();\n\tNewJSONWriter.WritePropertyName(\"\u0421\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u0438\u043a\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430\");\n\tNewJSONWriter.WriteStartArray();\n\t\n\tSelection = Catalogs.\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430.Select();\t\n\t\n\tWhile Selection.Next() Do \n\t\tNomenclatureObject = Selection.GetObject();\n\t\t\n\t\tNewJSONWriter.WriteStartObject();\n\t\t\n\t\tNewJSONWriter.WritePropertyName(\"\u041d\u043e\u043c\u0435\u043d\u043a\u043b\u0430\u0442\u0443\u0440\u0430\");\n\t\tNewXDTOSerializer.WriteJSON(NewJSONWriter, NomenclatureObject, XMLTypeAssignment.Implicit);\n\t\t\n\t\tNewJSONWriter.WriteEndObject();\n\tEndDo;\n\t\n\tNewJSONWriter.WriteEndArray();\n\tNewJSONWriter.WriteEndObject();\n\tNewJSONWriter.Close();\t\nEndProcedure\n<\/code><\/pre>\n<p>\n\u0414\u0430\u043b\u0435\u0435 \u043e\u0441\u0442\u0430\u043d\u0435\u0442\u0441\u044f \u0442\u043e\u043b\u044c\u043a\u043e \u043f\u0435\u0440\u0435\u0434\u0430\u0442\u044c \u0434\u0430\u043d\u043d\u044b\u0435 \u043a\u043e\u043d\u0435\u0447\u043d\u043e\u043c\u0443 \u043f\u043e\u0442\u0440\u0435\u0431\u0438\u0442\u0435\u043b\u044e. \u041f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 1\u0421:\u041f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0435 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442 \u043e\u0441\u043d\u043e\u0432\u043d\u044b\u0435 \u0438\u043d\u0442\u0435\u0440\u043d\u0435\u0442-\u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b HTTP, FTP, POP3, SMTP, IMAP, \u0432\u043a\u043b\u044e\u0447\u0430\u044f \u0438\u0445 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u044b\u0435 \u0432\u0435\u0440\u0441\u0438\u0438. \u0422\u0430\u043a\u0436\u0435 \u0434\u043b\u044f \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u043c\u043e\u0436\u043d\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c HTTP \u0438\/\u0438\u043b\u0438 Web-\u0441\u0435\u0440\u0432\u0438\u0441\u044b.<\/p>\n<h4>HTTP- \u0438 \u0432\u0435\u0431-\u0441\u0435\u0440\u0432\u0438\u0441\u044b<\/h4>\n<p>\n<img decoding=\"async\" alt=\"M\u00e5ter \u00e5 integrere med 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1d4797d9298f793e19ee637fd26473b2.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>\u041f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f 1\u0421 \u043c\u043e\u0433\u0443\u0442 \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u044b\u0432\u0430\u0442\u044c \u0441\u0432\u043e\u0438 HTTP- \u0438 \u0432\u0435\u0431-\u0441\u0435\u0440\u0432\u0438\u0441\u044b, \u0430 \u0442\u0430\u043a\u0436\u0435 \u0432\u044b\u0437\u044b\u0432\u0430\u0442\u044c HTTP- \u0438 \u0432\u0435\u0431-\u0441\u0435\u0440\u0432\u0438\u0441\u044b, \u0440\u0435\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u0435 \u0441\u0442\u043e\u0440\u043e\u043d\u043d\u0438\u043c\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c\u0438. <\/p>\n<h4>REST \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u0438 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b OData<\/h4>\n<p>\n\u041d\u0430\u0447\u0438\u043d\u0430\u044f \u0441 \u0432\u0435\u0440\u0441\u0438\u0438 8.3.5 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 1\u0421:\u041f\u0440\u0435\u0434\u043f\u0440\u0438\u044f\u0442\u0438\u0435 \u043c\u043e\u0436\u0435\u0442 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u0435\u0441\u043a\u0438 <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/avtomaticheskiy-rest-interfeys-prikladnykh-resheniy\/\">\u0444\u043e\u0440\u043c\u0438\u0440\u043e\u0432\u0430\u0442\u044c REST \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441<\/a><\/noindex> \u0434\u043b\u044f \u0432\u0441\u0435\u0433\u043e \u043f\u0440\u0438\u043a\u043b\u0430\u0434\u043d\u043e\u0433\u043e \u0440\u0435\u0448\u0435\u043d\u0438\u044f. \u041b\u044e\u0431\u043e\u0439 \u043e\u0431\u044a\u0435\u043a\u0442 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0438 (\u0441\u043f\u0440\u0430\u0432\u043e\u0447\u043d\u0438\u043a, \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442, \u0440\u0435\u0433\u0438\u0441\u0442\u0440 \u0441\u0432\u0435\u0434\u0435\u043d\u0438\u0439 \u0438 \u0442.\u0434.) \u043c\u043e\u0436\u043d\u043e \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u044b\u043c \u0434\u043b\u044f \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u0438\u044f \u0438 \u043c\u043e\u0434\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u0434\u0430\u043d\u043d\u044b\u0445 \u0447\u0435\u0440\u0435\u0437 REST \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441. \u0412 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Open_Data_Protocol\">OData<\/a><\/noindex> versjon 3.0. Publisering av OData-tjenester utf\u00f8res fra menyen i Konfiguratoren \u00abAdministrasjon -&gt; Publisering p\u00e5 webserver\u00bb, avmerkingsboksen \u00abPubliser standard OData-grensesnitt\u00bb m\u00e5 v\u00e6re merket. Atom\/XML og JSON-formater st\u00f8ttes. Etter at den applikative l\u00f8sningen er publisert p\u00e5 webserveren, kan tredjepartssystemer f\u00e5 tilgang til den via REST-grensesnittet ved hjelp av HTTP-foresp\u00f8rsel. For \u00e5 arbeide med 1C-applikasjonen via OData-protokollen kreves det ingen programmering p\u00e5 1C-siden.<\/p>\n<p>Dermed vil en URL som <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Nomenklatura<\/u> returnere innholdet i katalogen Nomenklatura i XML-format \u2014 en samling elementer entry (meldingshodet utelatt for kortfattethet):<\/p>\n<pre><code class=\"xml\">http:\/\/server\/Config\/odata\/standard.odata\/Catalog_Nomenkatura(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\tAirconditioner Mitsubishi\n\t\t\tEffekt 2,5 kW, driftsmoduser: varme\/kulde\n\t\t\n\t\n\n\n\thttp:\/\/server\/Config\/odata\/standard.odata\/Catalog_Nomenkatura(guid'35d1f6e5-289b-11e6-8ba4-e03f49b16074')\n\t\n...\n<\/code><\/pre>\n<p>\nVed \u00e5 legge til strengen \u00ab?$format=application\/json\u00bb til URL-en, f\u00e5r vi innholdet i katalogen Nomenklatura i JSON-format (en URL som <u>http:\/\/\/\/odata\/standard.odata\/Catalog_Nomenkatura?$format=application\/json<\/u> ):<\/p>\n<pre><code>{\n\"odata.metadata\": \"http:\/\/server\/Config\/odata\/standard.odata\/$metadata#Catalog_Nomenkatura\",\n\"value\": [{\n\"Ref_Key\": \"35d1f6e4-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAgAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000001\",\n\"Description\": \"Airconditioner Mitsubishi\",\n\"Beskrivelse\": \"Effekt 2,5 kW, driftsmoduser: varme\/kulde\"\n},{\n\"Ref_Key\": \"35d1f6e5-289b-11e6-8ba4-e03f49b16074\",\n\"DataVersion\": \"AAAAAwAAAAA=\",\n\"DeletionMark\": false,\n\"Code\": \"000000002\",\n\"Description\": \"Airconditioner Daikin\",\n\"Beskrivelse\": \"Effekt 3 kW, driftsmoduser: varme\/kulde\"\n}, \u2026\n<\/code><\/pre>\n<p><\/p>\n<h4>Eksterne datakilder<\/h4>\n<p>\n<img decoding=\"async\" alt=\"M\u00e5ter \u00e5 integrere med 1C\" src=\"\/wp-content\/uploads\/2019\/08\/1663b53846f3a6a8a03f386f1f6cd311.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nI noen tilfeller skjer datautveksling via <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000795.htm\">eksterne datakilder<\/a><\/noindex> kan vise seg \u00e5 v\u00e6re en optimal l\u00f8sning. Eksterne datakilder er et applikasjonsobjekt for 1C-konfigurasjon som gj\u00f8r det mulig \u00e5 samhandle med enhver ODBC-kompatibel database b\u00e5de for lesing og skriving. Eksterne datakilder er tilgjengelige b\u00e5de p\u00e5 Windows og Linux.<\/p>\n<h4>Datadeling mekanisme<\/h4>\n<p>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000269.htm\">Datadeling mekanisme<\/a><\/noindex> er ment for \u00e5 b\u00e5de lage territorielt distribuerte systemer basert p\u00e5 1C:Enterprise og for \u00e5 organisere datadeling med andre informasjonssystemer som ikke er basert p\u00e5 1C:Enterprise.<\/p>\n<p>Denne mekanismen brukes aktivt i implementeringene av 1C, og spekteret av oppgaver som l\u00f8ses med den er ganske bredt. Det inkluderer datadeling mellom 1C-applikasjoner installert i filialene til organisasjonen, samt deling mellom en 1C-applikasjon og nettbutikkens nettsted, og datadeling mellom serverapplikasjonen i 1C og den mobile klienten (laget med den mobile plattformen for 1C:Enterprise), og mye mer.<\/p>\n<p>Et av n\u00f8kkelbegrepene i datadeling mekanismen er utvekslingsplanen. Utvekslingsplanen er en spesiell type objekt i 1C-plattformen som definerer, blant annet, hvilket datainnhold som skal delta i utvekslingen (hvilke spesifikke referanser, dokumenter, registre osv.). Utvekslingsplanen inneholder ogs\u00e5 informasjon om deltakerne i utvekslingen (de s\u00e5kalte utvekslingsnodene).<br \/>\nDen andre komponenten i datadeling mekanismen er mekanismen for registrering av endringer. Denne mekanismen sporer automatisk endringer i systemet som m\u00e5 overf\u00f8res til sluttbrukere i samsvar med utvekslingsplanen. Med denne mekanismen overv\u00e5ker plattformen endringer som har skjedd siden forrige synkronisering, og gj\u00f8r det mulig \u00e5 minimere st\u00f8rrelsen p\u00e5 dataene som overf\u00f8res i l\u00f8pet av neste synkroniserings\u00f8kt.<\/p>\n<p>Data exchange occurs through XML messages of a specific structure. The message contains data that has changed since the last synchronization with the node, along with certain service information. The structure of messages supports message numbering and allows for receiving confirmations from the receiving node regarding the acceptance of messages. Such a confirmation is contained in each message coming from the receiving node, in the form of the number of the last accepted message. The message numbering allows the platform to understand which data has already been successfully transmitted to the receiving node and to avoid retransmission, sending only the data that has changed since the sender node received the last message with the receipt of data received by the receiving node. This scheme ensures guaranteed delivery even in unreliable transmission channels and in the event of message loss.<\/p>\n<h4>External components<\/h4>\n<p>\nIn certain cases, when addressing integration tasks, one may encounter specific requirements, such as interaction protocols, data formats not accounted for in the 1C:Enterprise platform. For this kind of tasks, the platform provides for <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/overview\/Term_000000545.htm\">the technology of external components<\/a><\/noindex>, which allows for the creation of dynamically connectable modules that expand the functionality of 1C:Enterprise. <\/p>\n<p>A typical example of a task with such requirements could be the integration of the 1C application solution with trading equipment, ranging from scales to cash registers and barcode scanners. External components can be connected both on the server side of 1C:Enterprise and on the client side (including, but not limited to, the web client, as well as <noindex><a rel=\"nofollow\" href=\"https:\/\/wonderland.v8.1c.ru\/blog\/vneshnie-komponenty-v-mobilnom-prilozhenii\/\">the next version of the mobile platform<\/a><\/noindex> 1C:Enterprise). The technology of external components provides a relatively simple and understandable programming (C++) interface for interaction between the component and the 1C:Enterprise platform, which must be implemented by the developer.<\/p>\n<p>The possibilities opened up by using external components are quite broad. Interaction can be implemented via specific data exchange protocols with external devices and systems, specific data processing algorithms and formats can be integrated, and so on.<\/p>\n<h4>Utdaterte integrasjonsmekanismer<\/h4>\n<p>\nPlattformen tilbyr integrasjonsmekanismer som ikke anbefales for bruk i nye l\u00f8sninger; de er bevart av hensyn til bakoverkompatibilitet, samt i tilfelle den andre siden ikke kan arbeide med mer moderne protokoller. En av dem er arbeidet med filer i DBF-format (st\u00f8ttes i innebygd spr\u00e5k ved hjelp av objektet XBase).<\/p>\n<p>En annen utdaterte integrasjonsmekanisme er bruken av COM-teknologi (tilgjengelig bare p\u00e5 Windows-plattformen). 1C:Enterprise-plattformen gir to integrasjonsmetoder for Windows som bruker COM-teknologi: Automation-server og Eksternt tilkobling. De ligner mye p\u00e5 hverandre, men en av de viktigste forskjellene er at i tilfelle av Automation-server kj\u00f8res et fullt klientprogram for 1C:Enterprise 8, mens i tilfelle av eksternt tilkobling kj\u00f8res en relativt liten intra-prosess COM-server. Det vil si at ved \u00e5 bruke Automation-server kan man bruke funksjonaliteten til klientprogrammet og utf\u00f8re handlinger som ligner interaktive handlinger fra brukeren. Ved \u00e5 bruke eksternt tilkobling kan man bare bruke funksjoner for forretningslogikk, som kan utf\u00f8res b\u00e5de p\u00e5 klientsiden av forbindelsen, hvor den intra-prosess COM-serveren opprettes, og ved \u00e5 kalle forretningslogikk p\u00e5 1C:Enterprise-serveren.<\/p>\n<p>COM-teknologien kan ogs\u00e5 brukes til \u00e5 kontakte eksterne systemer fra koden til applikasjonen p\u00e5 1C:Enterprise-plattformen. I dette tilfellet fungerte 1C-applikasjonen som COM-klient. Men det b\u00f8r huskes at disse mekanismene kun vil fungere hvis 1C-serveren opererer i Windows-milj\u00f8et.<\/p>\n<h3>Integrasjonsmekanismer implementert i standardkonfigurasjoner<\/h3>\n<p><\/p>\n<h4>EnterpriseData-format<\/h4>\n<p>\n<img decoding=\"async\" alt=\"M\u00e5ter \u00e5 integrere med 1C\" src=\"\/wp-content\/uploads\/2019\/08\/8930091e53309b9b808a719b747a6226.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nI flere 1C-konfigurasjoner (listen nedenfor) er det implementert en klar mekanisme for datasutveksling med eksterne applikasjoner, basert p\u00e5 den beskrevne plattformens datadeling, og som ikke krever endring av kildeteksten til konfigurasjonene (forberedelse til datautveksling skjer i innstillingene til de applikative l\u00f8sningene):<\/p>\n<ul>\n<li>\u00ab1C:ERP Ledelse av virksomheten 2.0\u00bb <\/li>\n<li>\u00abKompleks automatisering 2\u00bb <\/li>\n<li>\u00abBokf\u00f8ringen til virksomheten\u00bb, revisjon 3.0 <\/li>\n<li>\u00abBokf\u00f8ring av virksomheten KORP\u00bb, revisjon 3.0 <\/li>\n<li>\u00abDetaljhandel\u00bb, revisjon 2.0 <\/li>\n<li>\u00abBasis for Trade Management\u00bb, edition 11 <\/li>\n<li>\u00abTrade Management\u00bb, edition 11<\/li>\n<li>\u00abPayroll and Personnel Management CORP\u00bb, edition 3<\/li>\n<\/ul>\n<p>\nThe data exchange uses the format <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_app\/enterprisedata\/\">EnterpriseData<\/a><\/noindex>, based on XML. The format is business-oriented\u2014the data structures described correspond to business entities (documents and directory elements) represented in 1C programs, for example: act of completed work, incoming cash order, counterparty, nomenclature, etc.<\/p>\n<p>Data exchange between the 1C application and a third-party application can occur:<\/p>\n<ul>\n<li>through a dedicated file directory <\/li>\n<li>through an FTP directory <\/li>\n<li>through a web service deployed on the 1C application side. The file with data is passed as a parameter of the web methods<\/li>\n<li>through email<\/li>\n<\/ul>\n<p>\nIn the case of exchange via a web service, the third-party application will initiate the data exchange session by calling the corresponding web methods of the 1C application. In other cases, the initiator of the exchange session will be the 1C application (by placing the data file in the corresponding directory or sending the data file to the configured email address).<br \/>\nAlso, on the 1C side, the frequency of synchronization will be configured (for options with file exchange via directory and email):<\/p>\n<ul>\n<li>according to a schedule (with a specified frequency) <\/li>\n<li>manually; the user will have to manually start the synchronization each time it is needed<\/li>\n<\/ul>\n<p><\/p>\n<h5>Acknowledgment of messages<\/h5>\n<p>\n1C applications keep track of the sent and received synchronization messages and expect the same from third-party applications. This allows for the use of the message numbering mechanism described above in the section 'Data Exchange Mechanism.'<\/p>\n<p>1C-applikasjoner overf\u00f8rer under synkronisering kun informasjon om endringer som har skjedd med forretningsenhetene siden forrige synkronisering (for \u00e5 minimere mengden data som overf\u00f8res). Ved f\u00f8rste synkronisering vil 1C-applikasjonen eksportere alle forretningsenheter (for eksempel elementer fra nomenklaturregisteret) i formatet EnterpriseData til en XML-fil (siden alle er \"nye\" for den eksterne applikasjonen). Den eksterne applikasjonen m\u00e5 behandle informasjonen fra den mottatte XML-filen fra 1C og ved neste synkronisering plassere en spesialseksjon i XML-filen sendt til 1C, med informasjon om at meldingen fra 1C med et bestemt nummer er mottatt. Bekreftelsen p\u00e5 meldingen fungerer som et signal for 1C-applikasjonen om at alle forretningsenhetene er behandlet av den eksterne applikasjonen, og informasjon om dem trenger ikke \u00e5 overf\u00f8res mer. I tillegg til bekreftelsen kan XML-filen fra den eksterne applikasjonen ogs\u00e5 inneholde data for synkronisering fra applikasjonens side (for eksempel dokumenter for salg av varer og tjenester).<\/p>\n<p>Etter \u00e5 ha mottatt bekreftelsesmeldingen vil 1C-applikasjonen merke alle endringer sendt i forrige melding som vellykket synkronisert. Bare usynkroniserte endringer i forretningsenheter (opprettelse av nye enheter, endringer og sletting av eksisterende) vil bli sendt til den eksterne applikasjonen ved neste synkronisering.<\/p>\n<p><img decoding=\"async\" alt=\"M\u00e5ter \u00e5 integrere med 1C\" src=\"\/wp-content\/uploads\/2019\/08\/b0d5509a53909e38886a15c2e03e7131.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nN\u00e5r data overf\u00f8res fra den eksterne applikasjonen til 1C-applikasjonen, skjer det en omvendt prosess. Den eksterne applikasjonen m\u00e5 fylle ut bekreftelsesseksjonen i XML-filen p\u00e5 passende m\u00e5te og plassere forretningsdata for synkronisering fra sin side i formatet EnterpriseData.<\/p>\n<p><img decoding=\"async\" alt=\"M\u00e5ter \u00e5 integrere med 1C\" src=\"\/wp-content\/uploads\/2019\/08\/d34b96efb7591770133b363b369c0019.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h5>Forenklet datadelingsprosess uten bekreftelse<\/h5>\n<p>\nFor enkle integrasjons scenarier der det kun er n\u00f8dvendig \u00e5 overf\u00f8re informasjon fra den eksterne applikasjonen til 1C-applikasjonen, og det ikke er behov for \u00e5 sende data tilbake fra 1C-applikasjonen til den eksterne applikasjonen (for eksempel integrering av en nettbutikk som sender salgsinformasjon til \"1C:Regnskap\"), er det en forenklet variant for drift via webtjeneste (uten bekreftelse) som ikke krever oppsett p\u00e5 1C-applikasjonen.<\/p>\n<h4>Spesialiserte integrasjonsl\u00f8sninger<\/h4>\n<p>\nDet finnes en standard l\u00f8sning \u00ab1C:Datakonvertering\u00bb, som bruker plattformens mekanismer for konvertering og datadeling mellom standardkonfigurasjoner av 1C, men den kan ogs\u00e5 brukes for integrasjon med tredjepartsapplikasjoner.<\/p>\n<h5>Integrasjon med bankl\u00f8sninger<\/h5>\n<p>\nStandard <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/100\/index.htm\">\u00abKlientbank\u00bb<\/a><\/noindex>, utviklet av spesialister i 1C for over 10 \u00e5r siden, har i praksis blitt industristandarden i Russland. Neste skritt i denne retningen er teknologien <noindex><a rel=\"nofollow\" href=\"http:\/\/directbank.1c.ru\/\">DirectBank<\/a><\/noindex>, som gj\u00f8r det mulig \u00e5 sende betalingsdokumenter til banken og motta kontoutskrifter direkte fra programmet \u00ab1C:Entreprise\u00bb med et enkelt klikk i \u00ab1C\u00bb; dette krever ikke installasjon og oppstart av ekstra programmer p\u00e5 klientdatamaskinen. <\/p>\n<p>Det finnes ogs\u00e5 <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/109\/\">standarder for datadeling i l\u00f8nnprosjekter<\/a><\/noindex>.<\/p>\n<h5>Annet<\/h5>\n<p>\nDet er verdt \u00e5 nevne <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/131\/\">protokollen for utveksling mellom systemet 1C:Enterprise og nettstedet<\/a><\/noindex>, standarden for utveksling av kommersiell informasjon <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/90\/\">CommerceML<\/a><\/noindex> (utviklet i samarbeid med Microsoft, Intel, Price.ru og andre selskaper), <noindex><a rel=\"nofollow\" href=\"http:\/\/v8.1c.ru\/edi\/edi_stnd\/111\/\">standarden for datadeling ved kortbetalingstransaksjoner<\/a><\/noindex>.<br \/>\n<br \/>Kilde: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1c\/blog\/308420\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a\u0430\u043a\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0438\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u0435\u0434\u044a\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043a \u0431\u0438\u0437\u043d\u0435\u0441-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c? \u041e\u0434\u043d\u0438\u043c\u0438 \u0438\u0437 \u0441\u0430\u043c\u044b\u0445 \u0433\u043b\u0430\u0432\u043d\u044b\u0445 \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0437\u0430\u0434\u0430\u0447\u0438: \u041b\u0435\u0433\u043a\u043e\u0441\u0442\u044c \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f\/\u0430\u0434\u0430\u043f\u0442\u0430\u0446\u0438\u0438 \u043b\u043e\u0433\u0438\u043a\u0438 \u0440\u0430\u0431\u043e\u0442\u044b \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f \u043a \u043c\u0435\u043d\u044f\u044e\u0449\u0438\u043c\u0441\u044f \u0431\u0438\u0437\u043d\u0435\u0441-\u0437\u0430\u0434\u0430\u0447\u0430\u043c. \u041b\u0435\u0433\u043a\u043e\u0441\u0442\u044c \u0438\u043d\u0442\u0435\u0433\u0440\u0430\u0446\u0438\u0438 \u0441 \u0434\u0440\u0443\u0433\u0438\u043c\u0438 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c\u0438. \u0422\u043e, \u043a\u0430\u043a \u0440\u0435\u0448\u0430\u0435\u0442\u0441\u044f \u0432 1\u0421 \u043f\u0435\u0440\u0432\u0430\u044f \u0437\u0430\u0434\u0430\u0447\u0430, \u0431\u044b\u043b\u043e \u043a\u0440\u0430\u0442\u043a\u043e \u043e\u043f\u0438\u0441\u0430\u043d\u043e \u0432 \u0440\u0430\u0437\u0434\u0435\u043b\u0435 \u00ab\u041a\u0430\u0441\u0442\u043e\u043c\u0438\u0437\u0430\u0446\u0438\u044f \u0438 \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u043a\u0430\u00bb \u044d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438; \u043c\u044b \u0435\u0449\u0435 \u0432\u0435\u0440\u043d\u0435\u043c\u0441\u044f \u043a \u044d\u0442\u043e\u0439 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u043e\u0439 \u0442\u0435\u043c\u0435 \u0432 \u043e\u0434\u043d\u043e\u0439 \u0438\u0437 \u0431\u0443\u0434\u0443\u0449\u0438\u0445 \u0441\u0442\u0430\u0442\u0435\u0439. [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":27703,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-36968","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a\u0430\u043a\u0438\u0435 \u0432\u0430\u0436\u043d\u0435\u0439\u0448\u0438\u0435 \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f \u043f\u0440\u0435\u0434\u044a\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043a \u0431\u0438\u0437\u043d\u0435\u0441-\u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u044f\u043c?\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/sposoby-integratsii-s-1s\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"nn_NO\" \/>\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\/no\/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\u00e5ter \u00e5 integrere med 1C | ProHoster","description":"Hvilke viktigste krav stilles til forretningsapplikasjoner?","canonical_url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/sposoby-integratsii-s-1s","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"nn_NO","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\/no\/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\/no\/wp-json\/wp\/v2\/posts\/36968","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/comments?post=36968"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/36968\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media\/27703"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media?parent=36968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/categories?post=36968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/tags?post=36968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}