Home Applications pex-demo
This application is not supported by InterSystems Corporation. Please be notified that you use it at your own risk.
2 reviews
IPM installs
Pull requests
Demo showcasing InterSystems IRIS integration with Kafka via PEX (java, .net)

What's new in this version

Initial Release

PEX demo

Demo showcasing InterSystems IRIS integration with Kafka via PEX.


The Production EXtension (PEX) framework provides you with a choice of implementation languages when you are developing interoperability productions. Interoperability productions enable you to integrate systems with different message formats and communication protocols. If you are not familiar with interoperability productions, see Introduction to Productions.

As of January 2022, PEX supports Python, Java, and .NET (C#) languages. PEX provides flexible connections between business services, processes, and operations that are implemented in PEX-supported languages or in InterSystems ObjectScript. In addition, you can use PEX to develop, inbound and outbound adapters. The PEX framework allows you to create an entire production in Pytohn or Java or .NET or to create a production that has a mix of Python, Java, .NET, or ObjectScript components. Once integrated, the production components written in Pytohn, Java, and .NET are called at runtime and use the PEX framework to send messages to other components in the production.

Running the demo

  1. Install:
  2. Execute:
git clone https://github.com/intersystems-community/pex-demo.git
cd pex-demo
docker compose pull
docker compose up -d

Demo Production

  1. (Optional) Disable KafkaConsumer service to catch a message on Kafka side (otherwise it would be processed too quickly).
  2. Open Production and test KafkaProducer operation by sending a dc.KafkaRequest message (topic: test, with any text, if text is a positive integer it would start a cycling message interchange). It would send a message to Kafka via Java Gateway.
  3. Open Kafka Manager and Navigate to Resources > Topics > test > Browse Data > Fetch to see that your message is enqueued.
  4. Open Message Viewer on KafkaConsumer service
  5. Start KafkaConsumer service. It would start receiving messages from test topic via .Net Gateway. If you want to receive messages from another topic, modify Remote Settings value for the Service.
  6. Refresh Message Viewer to see new messages.
  7. Send Ens.StringContainer request to KafkaProcess with a small integer value. Check emergent cycle session counting down to zero in a Message Viewer on KafkaConsumer service.

Demo Dynamic Gateway

Example of working with dynamic proxy objects:

docker-compose exec iris iris session iris
set GW = ##class(%Net.Remote.Gateway).%New()
set sc = GW.%Connect("netgw", 55556)
set random = ##class(%Net.Remote.Object).%New(GW,"System.Random")
write random.Next(100)
set sc = GW.%Disconnect()

What’s inside


  • InterSystems IRIS: http://localhost:52773/csp/user/EnsPortal.ProductionConfig.zen
  • Eco Kafka Manager: http://localhost:8082

Other ports

  • SuperServer: 51773
  • Java Gateway: 55555
  • .Net gateway: 55556
  • Python gateway: 55557
  • Zookeeper: 2181
  • Kafka: 9092
Read more
Made with
1.0.016 Jul, 2020
Technology Example
Works with
InterSystems IRIS
First published
16 Jul, 2020
Last checked by moderator
12 Mar, 2024Doesn't work