All
Accepted answers
Ben Spead · Jan 2, 2024 go to post

@Alan Watts - to clarify, can you please confirm that you are trying to use Embedded (aka Server-side) source control using the git-source-control package from OEM?  

Ben Spead · Dec 27, 2023 go to post

Thank you for all of the ideas which make all of our products and online offerings better :-)

Ben Spead · Dec 20, 2023 go to post

Wait ... is that a "reCAP" on the logo?  ;)

Love it - thanks for all you do!

Ben Spead · Dec 20, 2023 go to post

Please remember to vote in the poll once you read the article!  Feel free to ask questions here about apps that may be new to you.

Ben Spead · Dec 19, 2023 go to post

Thanks for the recap - it's great to see everything accomplished this year :)  Thank you to everyone to added to our Community this year!!

Ben Spead · Dec 19, 2023 go to post

A great resource for the Community - thank you for taking the time to write this!

Ben Spead · Nov 30, 2023 go to post

I have just learned that there are issues with "eu-central-1" and they are looking to remove it.  Could you please try another deployment using "us-east-1" and see if that fixes it?

Ben Spead · Nov 22, 2023 go to post

@Mathew Rimmington - this is an open source package which is written and maintained by InterSystems employees for the good of the Community, but doesn't have official support in the same way that customers have official support for InterSystems IRIS or HealthShare.  

This package is very much still strongly recommended for use and new sites are coming on board all the time.  We continue to invest in it and see it as a valuable tool for developers using a shared-dev model on InterSystems products.

In terms of the issue you are seeing, what InterSystems product are you using, and what specific version?  We will definitely help you work through the issues as much as we can.

CC: @Timothy Leavitt , @Pravin Barton 
 

Ben Spead · Nov 21, 2023 go to post

I strongly recommend that you reach out to Support with these questions

Ben Spead · Nov 20, 2023 go to post

I strongly suggest you contact InterSystems Support to ask about this.  

Ben Spead · Nov 14, 2023 go to post

thanks for taking the time to post your solution to others can benefit!!

Ben Spead · Nov 14, 2023 go to post

my understanding is that there will be no changes made to those APIs, nor plans to deprecate them.  That is what Bob was referring to when he said most orgs use their own monitoring solutions to consume the IRIS data (via those APIs) ... so the APIs will stay, but SAM as an out of the box consumer of the metrics will be deprecated

Ben Spead · Nov 14, 2023 go to post

this is only the SAM container.  the APIs it consumes will stay and there are no plans to deprecated those.

Ben Spead · Nov 14, 2023 go to post

Colin ... I hope you're successful in that effort!!  happy kicking ;)

Ben Spead · Nov 13, 2023 go to post

@Colin Brough - this was recently discussed on a thread internal to InterSystems, and I credit @Eduard Lebedyuk 
for the following options, which were suggested within the context of Enabled/Disabled Business Hosts on different environments using the same Production (some don't apply to your question about logging and testing, but I include them all for completeness):

1. Track a separate production class for each environment.
2. Use SDS to effectively disable Business Hosts (for example, by setting the Port property to an empty string).
3. Create a custom adapter/business host that has SDS configurable setting "RealEnable", which would be checked in OnInit or OnProcess input.
4. Use Interoperability Schedules, with Business Host always off/on.

I think (1) and (3) would be most likely to work for you here.

Also, it's not going to help you in the immediate term, but be aware that TestingEnabled (along with some other fields) is supported for SDS starting in InterSystems IRIS 2023.3 (I am very excited about that!!)

Ben Spead · Nov 2, 2023 go to post

Sounds like you are using client-side source control in a shared development environment ... this is just a formula for frustration.  Either use private dev instances with client-side source control, or use server-side source control with a shared dev instance.  This was the theme of a presentation we did at G.S. a couple of times.  See https://community.intersystems.com/post/new-video-shared-development-21…
NOTE - This was given a 2nd time where we used VSCode and not Atelier but I can't find that posting for some reason.   However the principles are identical whether you're using Atelier or VSCode ... they use the same APIs to manage source with the server.