Obviously the class keywords and source could diverge and become incompatible.

That said, take a look at the header in the export file.  Should be as simple as changing IRIS to cache

I think I may have it.  Basically I. Base64.encoding the file on the client side and will need to decide it on the server.  

I need to do a little more testing and debugging in the morning and will post the solution.


Check %SYSTEM.INetInfo.   I think it probably contains a method to serve your purpose 


Even in a http POST, url variables are found in %request.Data.  The content stream will contain the body of your post.

If  you want to q global search and replace you can use the %RCHANGE utility from a terminal session.

Hi David

SSL for a web service hosted by ISC back-end is handled through the web server.   You  need to configure the web server to handle the SSL.

This procedure involves generating a certificate and setting up the ssl connection inside the web server software.  That process varies based on the web server you are running.

I would do something like this.

if pVersion?1"v"1n.n {

     // Parameter is well formed vnnn

} else {

     // Parameter is not well formed


Hi Jimmy

The short answer is that the EnsLib.File.PassthroughOperation is a special operation that can take a stream and write it out to a file.  The operation expects you to pass in an instance of Ens.StreamContainer and you need to populate the Stream property which is what the PassthroughOperation is looking for.

An example might be:

set sc=##class(Ens.StreamContainer).%New()

set stream = ##class(%Stream.GlobalCharacter).%New()

do stream.Write("This is my text to go into the file")

set sc.Stream=stream

Once you have done this, you can send sc as the input to your operation using ..SendRequestAsync or ..SendRequestSync, or from a BP if that is where the message is coming from

My question is given your request message you created, what are you hoping the output in the file will look like?