go to post Vic Sun · Jan 14, 2022 Connor, I'm not sure I understand what you're describing. Are you familiar with InterSystems mirroring? In short, it is a method of keeping two separate instances' data in sync, and can be used for reporting purposes. Do you really need just the deltas, and if so in what way would you be using them?
go to post Vic Sun · Jan 14, 2022 Hi Connor - is there a reason you can't use mirroring? I can imagine it would be possible to implement something custom where you capture the built-in online backup with Veeam snapshots, but it feels like there would be a lot more moving pieces.
go to post Vic Sun · Jan 10, 2022 Hello Scott, I think the following doc section "Deploying a Production" is relevant: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=EGDV_deploying#EGDV_exporting_production "If a production uses XSD schemas for XML documents or uses an old format schema for X12 documents, the schemas are not included in the XML deployment file and have to be deployed through another mechanism. InterSystems IRIS can store X12 schemas in the current format, in an old format, or in both formats. When you create a deployment file, it can contain X12 schemas in the current format, but it does not contain any X12 schemas in the old format or any XSD schemas for XML documents. If your production uses an old format X12 schema or uses any XSD XML schema, you must deploy the schemas independently of deploying the production. For the schemas that are not included in the deployment file, they can be deployed to a target system by either of the following means: If the XML or X12 schema was originally imported from an XSD or SEF file and that file is still available, import the schema on the target system by importing that file. XSD files can be used to import XML schemas and SEF files can be used to import X12 schemas. Export the underlying InterSystems IRIS global that contains the schema and then import this on the target system. To export a global, select System Explorer > Globals, select the desired globals and then select Export. The X12 schemas are stored in the EnsEDI.Description, EnsEDI.Schema, EnsEDI.X12.Description, and EnsEDI.X12.Schema globals. The XML schemas are stored in the EnsEDI.XML.Schema global. See “Exporting Globals” in the Using Globals guide for details on exporting globals."
go to post Vic Sun · Dec 13, 2021 Please see the following page for official InterSystems guidance! https://community.intersystems.com/post/december-13-2021-advisory-vulnerability-apache-log4j2-library-affecting-intersystems-products
go to post Vic Sun · Dec 13, 2021 Please see the following page for official InterSystems guidance!https://community.intersystems.com/post/december-13-2021-advisory-vulnerability-apache-log4j2-library-affecting-intersystems-products
go to post Vic Sun · Nov 30, 2021 The fact that there is a TCP error implies that there's a problem below IRIS , at the networking level. Opening the firewall was a good first step, but can you check other network logs or check the connectivity between the machines in other ways?
go to post Vic Sun · Nov 24, 2021 I'm not sure why this many month old question appeared at the top of the community queue, but can this problem be described more clearly? You can monitor multiple namespaces. How is the monitor incorrect?
go to post Vic Sun · Nov 11, 2021 If you debug the class and go through it can you try to identify which line is throwing the error?
go to post Vic Sun · Nov 10, 2021 Omar, What schemas do you need? The ASTM schema structure page is the place to start for existing functionality and importing. https://cedocs.intersystems.com/ens20141/csp/docbook/DocBook.UI.Page.cls?KEY=EAST_tools#EAST_tools_schema_structures edit: I think you edited your comment to add the message you are seeing. I can see on modern ISC products that E1394 is built-in, not sure about on 2014.1.
go to post Vic Sun · Nov 9, 2021 Hello Omar, What problem exactly are you having? It sounds like you have a reasonable configuration. "The Ensemble architecture prohibits a business service from initiating transmissions outside Ensemble. Replies to received documents are fine, but there is no provision for a business service to initiate an exchange with an entity outside Ensemble. To adapt this restriction to ASTM conventions, Ensemble provides a special-purpose business operation for use with ASTM business services. This business operation identifies the incoming ASTM business service as its partner service. Whenever any member of the Ensemble production needs to initiate communication to the external device, it invokes this business operation, which sends the transmission out via its partner service. This preserves the Ensemble conventions for internal messaging (a business service may send messages to a business process or business operation only) while leaving room for ASTM conventions (there is only one TCP socket available on the device, and at the other end of this TCP connection is an Ensemble business service)." Basically, you configure the operation with a connection to your ASTM TCP service and then the operation will be able to "use" the same port.
go to post Vic Sun · Nov 9, 2021 Ah - I think you might get more help with this from Avaya directly, as probably most people on this forum don't know how their application is set up.
go to post Vic Sun · Nov 9, 2021 Cathy, What do you mean by skillset data? Do you have an idea of what tables you are working with (other than the waiting time)?
go to post Vic Sun · Nov 9, 2021 Hello Nicola, Pretty open ended question, but perhaps the shortcut reference would be of use to you? Maybe you can elaborate on what you're looking for. https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSTD_Commands#GSTD_Commands_Accel Also, I'm sure somebody would mention VS Code if I didn't. That may be a more cozy programming experience for you depending on your background.
go to post Vic Sun · Nov 5, 2021 I think the Ens.Util.Statistics EnumerateHostStatus query may be what you're looking for: https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic.cls?&LIBRARY=ENSLIB&PRIVATE=1&CLASSNAME=Ens.Util.Statistics For a TCP component, the AdapterState will tell you if there is a connection or not.
go to post Vic Sun · Nov 3, 2021 I'd look at the other logs on the system. That error indicates that a job can't be spawned, so the question would be why? Maybe the performance problem is rooted in that same reason. edit: you may want to consider opening a WRC case for this if you can't find evidence of a problem.
go to post Vic Sun · Nov 1, 2021 Hello Mikhail, It looks like on IRIS 2021.1, global exports don't support wildcard exclusions, but they do work for class exports (as the class reference example suggests). $SYSTEM.OBJ.Export can handle many different item types - I'll put in a request that we narrow the documentation.
