Transfer a IDM Document from one IDM System to another

Question

Hi

I have to transfer a IDM Document from one system (LTR 2025.06) to an other one (CE).

My consideration;

* activate ION Integration
* create a Data Flow from the source IDM to the destination IDM with the Sync.ContentDocument BOD and a mapping from sync to process on the way …

Do far so good:

* BOD is triggerd
* Data Flow works - Document will be created on the destination side …

But:

In the Sync.ContentDocument BOD there is only the (not direct useable - KB2231342) url to the document himself.

For the process BOD I'll need the Base64Binary string … Therfore only the Document Header without contend will be created on the destination side.

Does anyone have experience with a scenario like this? How can it be solved?

I would have expected it to be possible to transfer data between two Infor systems.

I'd really like to avoid programming an application that selects the document via API, downloads the content, base64-encodes it, and then transfers it back to the target system via API. Surely there's an easier way?

T'x

Christoph

Christiaan Rentier · Answer

Christoph,

Sounds a good idea.

The URL in the Sync.ContentDocument BOD can be used indeed. Just one remark the Bearer Token present in the file is for obvious reasons only valid a very limited time (15 mins AFAIK). In case your script runs for whatever reason later on a file downloaded way earlier, then the token won't work. Preferably Authenticate using the IONAPI file created for Authorized App.

BTW doesn't the On-Premises Infor OS has the option to start a script as part of a Document flow?

Rgds Christiaan

Christoph Madlener · Answer

ok, not that straightforward as expected/hoped but somehow working.

my current solution:

ION integration activated for IDM1

DataFlow which stores the Sync.ContentDocument BOD from IDM1 in a FileShare

a scheduled Powershell script (t'x to ai) which downloads the document based on the included url also to the file system

the same powershell script also creates the metadata txt file with the attribute and acl values and the acl value (also extracted from the BOD)

then the StreamServeAdatper takes both files and performes the upload to the IDM2 (there of course the same dok type has to be already configured)

t'x for your help

Christoph

Brandon Watson · Answer

You could probably write the file on-prem to a folder share, then pick up the file with Cloud and insert. The biggest problem will be the filename and attributes being written properly. You would want to use the binary stream api to get the document form on-prem, triggering off the Sync.ContentDocument, but that would only get you the filename and not the attributes.

You could also try and use the IDM Utilities JAR and do an Export from on-prem with that JAR and then use the cloud JAR to upload to cloud.

I guess another option is the StreamServe Adapter. You could possibly have a parrallel flow that drops the Sync.ConentDoc to the xml/txt file that matches the binary file and drop both in the StreamServe Directory.

The last option I can think of is the Network Connection Point, depending on the on-prem InforOS version. That can connect on-prem to cloud with BODs, you could send the Sync.ContentDoc to cloud and have Cloud get the document with an API and then use Merge Script to merge the binary and ContentDoc to get the filename and all attribute files written.

Copyright © 2025 Infor. All rights reserved.