© 2026 InterSystems Corporation. All rights reserved.Privacy & TermsGuaranteeSection 508Contest TermsCode of ConductModeration PolicyCookies Settings
Initial Release
This repository contains the materials and some examples you can use to learn the basic concepts of PEX (Production EXtension) in IRIS Interoperability.
You can find more in-depth information in https://learning.intersystems.com.
New to IRIS Interoperability framework? Have a look at IRIS Interoperability Intro Workshop.
Build the image we will use during the workshop:
$ git clone https://github.com/intersystems-ib/workshop-pex
$ cd workshop-pex
$ docker compose build
docker compose up
superuser/ SYS account.FirstOperation Business Operation.Class Name and Remote Business Operation section. What is the Java Gateway server that is being used?MessageRouter Business Process.Ens.StringRequest and enter some text in the StringValue field. Send the test message.Message Router transforms a Ens.StringRequest to a EnsLib.PEX.Message. You can see the data transform here Workshop.PEX.FirstDemo.DT.StringRequest2PEX.FirstOperation is a very simple Business Operation that is implemented on Java. We will go through it in the next section.FirstOperation implementation.FirstMessage request?FirstDemo.jar).PEXJavaServer in IRIS, which starts and manages the Java Gateway processjgw is no longer needed: the Java Gateway is handled by IRIS through an External Language Server (ELS). The IRIS image already includes a JDK 11 and the InterSystems Java libraries (/usr/irissys/dev/java/lib/1.8/, e.g. intersystems-utils-4.2.2.jar, which contains the PEX classes), so no builder stage or local jars are needed.FirstService and FirstProcess. Go through their implementation and Settings tab in the production, and finally enable them and check what happens.LOGINFO).docker-compose build and run again.Have a look at those great examples on using PEX with InterSystems IRIS: