Home Applications sscp

sscp

This application is not supported by InterSystems Corporation. Please be notified that you use it at your own risk.
4.5
2 reviews
0
Awards
402
Views
4
IPM installs
0
0
Details
Releases
Reviews  (2)
Issues
File Transfer over the InterSystems IRIS SuperServer

What's new in this version

Initial Release

InterSystems SuperServer Copy

File Transfer over the InterSystems IRIS SuperServer.

Why

Dropping to $ZF, the shell, or automation tooling like Ansible is proving to cause more problems sometimes than its worth when automating systems for post configuration for things like MIRRORING setup, certificates, and libraries across systems. As a common practice, it would be nice to rule out “ObjectScript Native” mechanisms before resorting to doing those things outside the instance… this solution allows you to rule it out for file transfer and keep the file copy operations across instances “ObjectScript Native”.

Example Copy

Setup

You need install the ipm package on all instances and in selected namespaces you wish to connect to. The namespace is not directly important to enabling the file copy operation, but just note it does not have to be in %SYS to work.

zn <Your Favorite Namespace>  
zpm "install sscp"  

Usage

For the initial version, a full connection string is required, and is in the form of username:password@host:port@namespace:file.

So, to transfer an IRIS.DAT file from host fhirwatch-pop-os (laptop) to remote server target-host you could use the following:

Set tSC = ##class(ZMSP.SuperServer).Copy("_SYSTEM:SYS@fhirwatch-pop-os:1972@%SYS:/tmp/source.dat","kmitnick:12345@target-host:1972@SDOH:/tmp/destination.dat")
Server to Server Transfer

Do I have to be on the instances I am transferring files across? Nope.

Let’s say you’ve loaded the ipm package on your laptop, container, or toaster running IRIS, and you have two targets you want to do a file transfer across:

Set tSC = ##class(ZMSP.SuperServer).Copy("_SYSTEM:SYS@remote-host:1972@%SYS:/tmp/source.dat","kmitnick:12345@target-host:1972@SDOH:/tmp/destination.dat")
Third Party Initiator

Use Cases

Establishing HealthShare Mirroring with HSSYS.
Automated provisioning of MIRRORS.
Transfer and update of Globals or Classes for those things outside of mirroring (%SYS).
Getting Files into your Health Connect Cloud instance to the file system interoperability target /connect.

Configuring Auditing

One of the benefits here of keeping this operation in house is it is now auditable, to enable auditing you can create a source and log the operation. Programmatically:

zn "%SYS"
set sc = ##class(Security.Events).Create("sscp","File Transfer", "ConfigurationChange","File Transfer Initiated",1)

Through the UI:

  1. Go to Management Portal -> System Administration -> Security -> Auditing -> Configure User Events
  2. Press button Create New Event
  3. Set Event Source: sscp
  4. Set Event Type: File Transfer
  5. Set Event Name: SSCP
  6. Press Save
Create Audit Event

Then, after your $$$OK, you can do:

Set tSC = $SYSTEM.Security.Audit("sscp","File Transfer", "ConfigurationChange","Transferred IRIS.DAT", "Setup of HealthShare Mirroring")

Which results in something like:

Logged Audit Event

Credit:
@Yuri.Gomes - Leveraging Audit Database

Is it fast?

Yeah I dunno… Most of the transfers in production use are under 100MB at the moment (HSSYS out of the box is around 22MB), but the only other benchmark I can share is some stuff that was around 800MB and took about a minute and a half traversing the internet.

Troubleshooting

The app logs to messages.log on both sides loosely.

Definitive RoadMap

  • Use stored connections instead to avoid secrets all over the place and ridiculous connection strings.
  • Investigate impact of the use private SSL Certificates wuth the connections.

DOCKER Support

Prerequisites

Make sure you have git and Docker desktop installed.

Installation

Clone/git pull the repo into any local directory

$ git clone https://github.com/sween/sscp.git

Open the terminal in this directory and run:

$ docker-compose build

Run IRIS container with your project:

$ docker-compose up -d

Test from docker console

$ docker-compose exec iris1 iris session iris
USER>

Now copy /iris1/TESTA from container iris1 to /iris2/copyTESTA.txt of container iris2
and watch the result in the related subdirectory or your installation

Set tSC=##class(ZMSP.SuperServer).Copy("_SYSTEM:SYS@iris1:1972@USER:/iris1/TESTA.txt","_SYSTEM:SYS@iris2:1972@USER:/iris2/copyTESTA.txt")

or using WebTerminal

http://localhost:42773/terminal/

Authors

@Ron.Sweeney1582
@Eduard.Lebedyuk
@Robert.Cemper1003

Made with
Install
zpm install sscp download archive
Version
1.0.028 Jul, 2023
ObjectScript quality test
Category
Solutions
Works with
InterSystems IRISInterSystems IRIS for HealthHealthShare
First published
28 Jul, 2023
Last checked by moderator
22 Aug, 2023Works