Yes, the GenericService will send an EnsLib.HTTP.GenericMessage object to your business process. The GenericMessage includes the headers and content of the inbound HTTP request. Your DTL can use these fields to transform to another format.

Similarly, the GenericOperation accepts the same GenericMessage type and uses the values in it to issue an HTTP request to the downstream system.

So all together, this allows you to create a REST web service and/or call out to external REST services using only the GUI.

https://docs.intersystems.com/irisforhealth20221/csp/docbook/DocBook.UI…

Here's a sample class to Base64 encode a stream:

Class Example.B64.Util Extends %RegisteredObject
{

/// Be cautious if changing CHUNKSIZE. Incorrect values could cause the resulting encoded data to be invalid.
/// It should always be a multiple of 57 and needs to be less than ~2.4MB when MAXSTRING is 3641144
Parameter CHUNKSIZE = 2097144;

ClassMethod B64EncodeStream(pStream As %Stream.Object, pAddCRLF As %Boolean = 0) As %Stream.Object
{
    set tEncodedStream=##class(%Stream.GlobalCharacter).%New()
    
    do pStream.Rewind()
    
    while ('pStream.AtEnd) {
        set tReadLen=..#CHUNKSIZE
        set tChunk=pStream.Read(.tReadLen)
        
        do tEncodedStream.Write($System.Encryption.Base64Encode(tChunk,'pAddCRLF))
        if (pAddCRLF && 'pStream.AtEnd) {
            do tEncodedStream.Write($c(13,10))
        }
    }
    
    do tEncodedStream.Rewind()
    
    quit tEncodedStream
}
}

Fortunately it's a simple issue. In your CALL action, you need to add a "Request Action" and set callrequest to the object you want to send to the BO. It looks like you're just modifying the inbound request so you could just set callrequest to request.

Try removing the JsonArayOBJ argument from your call to SendFormDataURL.

set st = ..Adapter.SendFormDataURL(..Adapter.URL,.callResponsePat,"POST",HTTPRequestPat)

Can you give some more details on what's happening? Is there an error message?

Can you clarify a bit?

Do you want to use curl to make an HTTP request to a web service running in Ensemble? Or do you want Ensemble to launch curl to make an HTTP request to an external web service?

You can put something similar to Jeffrey's logic directly in the Value of the Set action. Instead of using $E ($EXTRACT) you would use DTL's built-in SubString function:

..SubString("123456789",1,3)_"-"_..SubString("123456789",4,5)_"-"_..SubString("123456789",6,9)

All persistent classes will save their data in globals automatically. It will save using the standard structures of the IRIS SQL layer.

If you have an existing global structure that you need to maintain you'll need to map your classes to your global structure. See this series of articles on how to do that.

Have a look at this previous thread.

And there's a built-in capability in IRIS to see ports in use by different components.

If you try this what does it return?

&sql(select count(*) INTO :tCount from GMECC_DocmanConnect_Tables.ParisConnecMessagetSettings Where  MessageName = :tMessageName and Identifier = :tIdentifier)

write SQLCODE, ":", tCount,!

What Response From does is control which responses from a call to an operation (or another component) are returned to the business service that called the router. By default the router won't return the response to the service, but setting Response From will enable responses to be returned from specific operations (or * for all operations). This is how you can control which response gets sent back to the service in a case when a router calls multiple operations. If multiple responses match the Response From setting, then only the first response will be returned to the service.

Response Target Config Names allows you to specify additional components (beyond the service that called the router) that should receive a copy of the response that came back from the operation. So you could send a copy of an ACK or other response to another operation for some reason.

All of this is probably moot, because I'm guessing your service doesn't need to receive a response.

In terms of the NULL responses, these shouldn't become orphans -- the fact that they appear in the message trace tells us that the production knows which session they belong to so they should get deleted along with the rest of the session.

A few questions that will help us to understand better:
- Which business service are you using? Is it custom or out-of-the-box?
- If the service is custom, what type of object is it sending to the Business Process?
- What type of Business Process are you using? Is it BPL, ObjectScript, or a router using routing rules?

Have a look at the Structured Logging capabilities as well.

Since you don't need to modify the request/response maybe pass-through services and operations will meet your needs?

This section in the docs discusses business processes and routers. You could use either one -- routing rules tend to be faster/easier to create.

Basically, your business process or routing rule would create a notification message and send it to a business operation. The process/router could construct the notification message directly or could call a data transformation that would create the notification message.

The operation would send the notification to an external system. One example would be to use an email operation to send the notification to an email server.

Our online learning portal also has some courses that cover these topics:

Integration Architecture
https://learning.intersystems.com/course/view.php?id=908

Building a Message Router
https://learning.intersystems.com/enrol/index.php?id=1745

Building BPL Business Processes
https://learning.intersystems.com/enrol/index.php?id=1290

Data Transformations Basics
https://learning.intersystems.com/course/view.php?id=1170

Can you elaborate on the limitations you see in DocumentType that are leading you to think about using Custom Pairs?

DocumentType is of type HS.SDA3.CodeTableDetail.DocumentType, which can store a code, description, and the code system. Seems like that's what you need, and it already maps to DocumentReference:type in FHIR.

After the service reads the file it will send a message containing the file contents to whatever Business Process you've set as it's target. Your business process or router could send a notification message wherever needed.