It's tough to say without knowing your config and what exactly was done. For the second error at least it seems reasonably clear what could be causing it, maybe that will help to resolve the first error as well? I'm not an Apache expert so take my personal advice with a grain of salt, I just know that many people have found Mark's article to be helpful.
 

https://stackoverflow.com/questions/24060620/error-starting-apache-httpd-configuration-error-more-than-one-mpm-loaded

Hi Scott,

Did you look at Web Servers for UNIX, Linux, and macOS? That page explains how to configure Apache to serve CSP files.

I'm not sure what you mean by calls to the management portal. If you have the standalone Apache / gateway set up appropriately, you can serve the portal through (presumably default) port 80, ex. go to http://<hostname>:80/csp/sys/UtilHome.csp, rather than attempting to use your private web server port.

Really the independent Apache is the main piece, you can consider the standalone web gateway to be a module on that Apache web server.

Hope that helps.

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."

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.

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.

This isn't a topic I'm super familiar with, it probably depends on what you plan on doing with the messages. The following docs might be helpful?

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=PAGE_interop_vdoc

If you're having throughput issues and suspect it is related to the service you're using (is there a particular reason you think that's the problem?), do you have a test environment where you can compare the 2 services?

Michael,

What's the use case? You might be able to design something with SQL triggers but that feels ripe for complications. You can find people discussing this kind of solution (using triggers) for other databases online, and from what I can tell people generally agree this is a messy option.

If the idea is that people are accidentally executing improper SQL commands, perhaps I would tackle this from a training perspective, or by restricting SQL commands to a more limited audience.

Hello Michael,

If the Ensemble log reports an arbiter loss of connection, Ensemble doesn't really have more logs that can explain why that happened. These messages are just reporting the underlying condition that Ensemble experiences.

Confirming the cause of connection losses is really more a matter of reviewing network/other logging in the environment.