Alberto Fuentes · Feb 19, 2016 go to post

Hi Timur,

I have many examples that we have been using during ad-hoc sessions with customers in Spain.

Those sessions were called IAT (you know we tend to pick up tricky names smiley)

And at this moment they are not in our github repository, so I'm just sharing some of them here.

We could upload some of these examples to github and use proper names if you are interested.

Alberto Fuentes · Oct 28, 2019 go to post

Hi Alex,

It really sounds very interesting having a "row driven" unit test methodology with the messages contained in XData blocks.

It would be great also having Object to Object support. 

You should definitely share it to community :)

Alberto Fuentes · Mar 12, 2017 go to post

Hi Sameera,

Make sure that workdir is configured in ^GITConfig with a trailing slash.

set ^GITConfig($username,"workdir")="c:\GitCode\"

Also make sure that your workdir c:\GitCode\ is a proper initilized git repository.

Alberto Fuentes · Dec 23, 2015 go to post

Hi Mario,

I guess you need to run some routine to export/import your classes from a Linux shell.
You can use operating system authentication when opening a terminal session:

- Allow "Operating System authentication" in System > Security Management > Authentication/CSP Session Options

- Allow "Operating System authentication" System > Security Management > Services > Terminal
- Create a user in cache with the same username as the user in Linux that will run the bash script.

Then you can just invoke a routine / classmethod from your linux shell and use $system.OBJ.Export / Import to export or import classes, include files, etc.

You should also think about using Ens.Director to stop / start production or business hosts as needed.
For instance:

[cacheowner@demo tmp]$ whoami
cacheowner
[cacheowner@demo tmp]$ ccontrol session HSEX15 "##class(Test.MyClass).Run()"
Run!
Exporting to XML started on 12/23/2015 16:25:57
Exporting routine: Test.MyInclude.inc
Export finished successfully.

Where:
Class Test.MyClass Extends %RegisteredObject
{
ClassMethod Run() As %Status
{
set ret = $$$OK
try {
write "Run!",!
do $system.OBJ.Export("Test.MyInclude.inc","/tmp/include.xml")
} catch ex {
set ret = ex.AsStatus()
do $system.Status.DisplayError(ret)
}
quit ret
}
}

Anyway, you can check out the Ensemble production deployment capabilities:
http://docs.intersystems.com/ens20152/csp/docbook/DocBook.UI.Page.cls?KEY=EGDV_deploying

Alberto Fuentes · Mar 5, 2020 go to post

Hi,

Try using ..%Process to access the actual business process instance (BPL).

Set SourceConfigName = ..%Process.%PrimaryRequestHeader.SourceConfigName 

Alberto Fuentes · Mar 8, 2021 go to post

Hi,

It seems the code was using a deprecated image name. I've just updated it to use intersystemsdc/jgw.

Please, try again.

Alberto Fuentes · Apr 15, 2021 go to post

Hi Tirthankar, You probably need to set up the Object Gateway classpath correctly.

I've just got it working as follows:

  1. Get the proper .jar files

I've copied them from the jgw container:

docker cp jgw:/jgw/FirstDemo.jar shared/ 
docker cp jgw:/jgw/gson-2.8.5.jar shared/     
docker cp jgw:/jgw/intersystems-gateway-3.1.0.jar shared/
docker cp jgw:/jgw/intersystems-jdbc-3.1.0.jar shared/    
docker cp jgw:/jgw/intersystems-utils-3.1.0.jar shared/

You can also generate your .jar files, just make sure it contains all the required dependencies.

  1. Set up your local Object Gateway:
  • IP address: 127.0.0.1
  • Port: 4444
  • ClassPath: /shared/FirstDemo.jar:/shared/gson-2.8.5.jar:/shared/intersystems-utils-3.1.0.jar

After that, start your Object Gateway, you should see something like: Executing O.S. command: java -Xrs -classpath /shared/FirstDemo.jar:/shared/gson-2.8.5.jar:/shared/intersystems-utils-3.1.0.jar:/usr/irissys/dev/java/lib/JDK18/intersystems-gateway-3.1.0.jar:/usr/irissys/dev/java/lib/JDK18/intersystems-jdbc-3.1.0.jar com.intersystems.gateway.JavaGateway 4444 "" "" 127.0.0.1 ""

  1. Modify some of the PEX components in the production, e.g. FirstOperation:
  • Gateway Host: localhost
  • Gateway Port: 4444

That should work.

Alberto Fuentes · Feb 23, 2023 go to post

Hi Eduard!

It's something custom. We have implemented some solutions (e.g. notifications system) using the feature you mentioned in the past but we always ended up creating new classes to handle the complexity we needed.

Anyway are still experimenting with this one :)

Alberto Fuentes · Mar 27, 2023 go to post

It simply calls the subscriber endpoint via $classmethod and passing the message payload as parameter :)

It could be improved adding way more types of endpoints such as remote HTTP endpoints (REST), etc.

Alberto Fuentes · Dec 24, 2024 go to post

Thanks so much for all your kind words and support! It’s awesome to be part of such a great community. I really appreciate every message.
Looking forward for next chance to have a coffee or beer together , whichever happens first 😀

Let’s keep doing amazing things together!