What schemas do you need? The ASTM schema structure page is the place to start for existing functionality and importing.

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

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.

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.

Agreed with the other comments. You can find documents discussing how to migrate to IRIS on the WRC distributions site (which covers that you can rename .DATs, among other things). I'd also recommend contacting your InterSystems account rep, they'll be happy to work with you.

Depending on what version you're on, you may be able to in-place migrate (if that's a desirable option for you).

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?

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?


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.

Hello Herb,

Have you checked the connectivity since the error is a timeout?

Can you make an SFTP connection outside of IRIS using a third party application or the command line?

You can debug the SSH portion of the connection via:

Hope that helps.

On top of Robert's answer, I would add - why are you copying from another namespace at all? If you just need the standard interoperability mappings, those get generated from the "enable namespace for Interoperability productions" checkbox.

You can't run 2 productions (even if you assign 2 namespaces) from the same databases simultaneously, so I would probably avoid "copy from" in general, particularly because you are trying to use EnsLib code.

There are probably specific cases where you might want to copy a namespace from another one, but I'd be cautious and make sure that copying is what you actually want.

edit: I am unsure whether using "copy from" on HSSYS is a good idea. Personally, I haven't done that, but I would be concerned that you might have similar issues to copying from %SYS, as HSSYS is a shipped database.