OAuth server to be deployed on the IRIS learning cloud platform. Clients - one on the other instance of the learning IRIS server, the other client locally on my computer in the container docker.
Both clients get a seemingly correct link (through ##class(%SYS.OAuth2.Authorization).GetAuthorizationCodeEndpoint()) to the login request form:
A very common problem of our users is to use an external database as data source in an IRIS production. As many of you already know, we have two ways to connect directly to an external database, the first one is using an ODBC connection, the second is using JDBC.
In our example we are going to create a connection using JDBC, and we are going to build a simple Docker's project, in this way you will be able to modify the example as you wish.
https://www.youtube.com/embed/bowj02anRM8 [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
What’s the contest about?
In the last year, InterSystems added and expanded Native APIs for Java, .NET, Python, and Node.js. The Native API provides high speed access to globals, the ability to instantiate and use ObjectScript objects, and fine-grained control over transactions.
We are developing some containarized cloud application level iris instances and using CPF Merge to do a lot of the initial buildout for the iris instance (i.e. create databases, namespaces, map globals/routines, ecp setup, etc...)
I am trying to figure out how to get package mappings into a namespace config, via cpf merge if possible... ?
This is the document I am working from to develop the cpf merge file -
Very recently Docker showed a very new feature added to their Docker Desktop tool. It was a good way to start using Docker on macOS and Windows, and they also released the same tool for Linux as well. And new feature Extensions add an ability to extend this GUI application with some extra abilities from extensions.
We have a bunch of templates on OEX that provide a handy foundation for building a particular application with IRIS. And the basic principle of each and every template is that we take vanilla IRIS images, load code, and files into the image using Dockerfile, and create a new docker image as a solution. And then we develop running this image and rebuilding it when returning to development.
Some developers ask me why we need to build the docker image to work with the code. Indeed, if at the end of the day I need to develop a ZPM package and not a docker image why don't run the vanilla image and load the code and everything in it?
The problem I have with the building image approach is that often I can wait a lot to build an image and it fails on some Objectscript problem in the source that I cannot fix as the image is not building. and
https://www.youtube.com/embed/G93HBywyaSY [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
Watch this video to explore how to use the passwordless ipm module to turn on and off entering login-password during docker build with your InterSystems IRIS:
https://www.youtube.com/embed/ygIJsTMO0Gw?controls=0 [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
https://www.youtube.com/embed/PvlDp6xLQ5U [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
https://www.youtube.com/embed/gaZfBdQYnVE [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
I recently had to diagnose a networking problem I was having when attached to our corporate network. I was seeing an unknown bridge network being defined that shared the same IP address space as the company network thus blocking access to company resources. This bridge network was separate from the Docker0 bridge network which the docker engine sets up. Docker was configured with a bip (bridge ip) address to prevent docker form using an address space that create a conflict.
The title says it all. I’m building an IRIS image with docker-compose using a separate Dockerfile. Pretty straightforward procedure: I import a Installer script inside the container containing a Installer Manifest I defined. Within the manifest, I create a namespace with code and data databases in separate locations. My intention is to keep the code database inside the container, so whenever I build the container, the imported code is replaced. The data, however, should be persistent.
I found a package on OEX for a Sharding Demo If Sharding is NOT included in the Community License I can not use the Community Distribution but require a different one. And have to add ZPM manually.
When deploying IRIS in a container, what are recommendations for permitting users terminal access? There is docker exec -it, but that does not work from a user's workstation where - in the old deployment model - they would connect to the server over ssh using Putty and open a terminal session from there.
https://www.youtube.com/embed/gil-H8TQqLg [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
When creating a service with DOCKER SERVICE CREATE we cannot pull from the intranet/local image repository. Both PULL and PUSH can be handled from the intranet repository.
I think there have been articles published here before but I'm struggling to find them:
I'd like to be able to create my own customised version of the official IRIS Community Edition Container, eg with Node.js and a number of modules pre-installed. So, for example, can I create my own Dockerfile that begins with something like:
FROM containers.intersystems.com/intersystems/iris-community-arm64:2023.2.0.227.0
For example, let's use this template repo. If you build this container A using docker-compose and then run the container it exposes REST-API which is available on:
localhost:52773/person/all
The question is how to make this REST-API accessible from another docker container B running on the same machine? E.g. with IRIS 2019.4 Community from this repo?
The problem is that for the second container localhost it's something which belongs to container B.
I think I need to set up a network between containers somehow. E.g. using docker-compose. But is there any simpler way?
I'm trying to build my project on a Linux machine using Docker.
In my development environment, I use Windows 10 Pro with Docker Desktop version 2.3.0.5. Everything works fine, and the docker-compose build runs flawlessly.
But, when I tried to run the same project in a Linux. Ubuntu 18.04.5 LTS (GNU/Linux 5.4.0-1025-azure x86_64), docker --version Docker version 19.03.6, build 369ce74a3c
By likes
Open Exchange app.png)
