Migrating MDRest4i Instance to Another IBM i Server or LPAR

Published: 2026-02-05

Applies to Version: 14 only

The easiest approach is to install a new version on the new server, including the Product lib, the SDK (if applicable) and any API servers.

Here is a step-by-step guide:

Step 1-Save MDRST Library

Save the current instance of MDRest4i library to a suitable media that can be used on the new server.

Note

THe library name will be either MDRST or MDRST plus the instance name. The instance name will have been assigned by whoever installed MDRest4i in the first instance, and is a 4 digit suffix added to MDRST.

For example MDRSTV14

Step 2-Install MDRest4i

Install a new version of MDRest4i on the new server.

If you still have the original SAVE feels from the original installation, use those to avoid any potential regression issues. Otherwise download the latest version from this link:

https://wiki.midrangedynamics.com/downloads/mdrest4i/

Remember to install new License Key

Step 3-Restore SDK Data

The following files can be restored from the current system backup made in Step 1 above.

Table	Description
MDRDAUTH	MDRest4i Object Authorities
MDRDCFG	MDRest4i API Configuration
MDRDCRED	MDRest4i - Credential Store
MDRDHTTP	MDRest4i - HTTP Instances
MDRDILOG	MDRest4i Installation Log
MDRDOAPI	Open API Documents
MDRDPAGE	MDRest4i Documenter Pages
MDRDSCHM	MDRest4i Saved Schemas
MDRDUSER	MDRest4i SDK User Data

Here is a suggested command for this:

RSTOBJ  OBJ((MDRDAUTH) (MDRDCFG) (MDRDCRED) (MDRDHTTP) (MDRDILOG) (MDRDOAPI) (MDRDPAGE) (MDRDSCHM) (MDRDUSER)) 
        SAVLIB(MDRST) DEV(*SAVF) SAVF(QGPL/MDRST) OBJTYPE(*FILE) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(MDRST)

Warning

update the values for:

SAVLIB(MDRST) SAVF(QGPL/MDRST) RSTLIB(MDRST)

as per your new and existing installation, where SAVF(QGPL/MDRST) is the backup from the old server created in Step 1 above.

Step 4-Restart All Servers

Using command MDRHTTP start/restart your SDK and API server/s on the new IBM i server.