M3 H5 SDK version 2 is now available on GitHub and npm

Legacy Contributor

M3 H5 SDK version 2 is now available on GitHub and npm.

Simply visit https://github.com/infor-cloud/m3-h5-sdk to get started!

 

For anyone received the beta or pre-release of the SDK please read the instructions below.

 

 

Migration instructions

These instructions only applies to those who started using the M3 Odin SDK 2.x before it was migrated to GitHub & npm.

 

Since we did not get access to the npm organization scope "@infor" we chose to use the scope "@infor-up" instead. This means that any existing projects must be updated to use the new scope. The changes includes all relevant import statements in TypeScript files and relevant dependencies in package.json files. We hope that the benefit of public GitHub & npm access outweighs the hazzle of migrating any existing projects.

 

Migrate TypeScript files

Edit all TypeScript files in each project that should be migrated. Change any occurrences similar to the value in the "Before" column in the table below to the value in the "After" column. You can also just search and replace "@infor/" with "@infor-up/". In Visual Studio code you can do this for all TypeScript files using Ctrl+Shift+H (replace in files) with a filter for "*.ts" files.

 

Before	After
import { } from '@infor/m3-odin';;	import { } from '@infor-up/m3-odin';;
import { } from '@infor/m3-odin-angular';;	import { } from '@infor-up/m3-odin-angular';;

 

 

Migrate package.json files

Edit the package.json file for each project that should be migrated. Change any occurrences of the value in the "Before" column in the table below to the value in the "After" column. You can also just search and replace "@infor/" with "@infor-up/".

 

Depending on how much control you want over updates you may also choose to change the version to either "~2.0.0" or "^2.0.0". See https://docs.npmjs.com/about-semantic-versioning for more information.

 

Before	After
"@infor/m3-odin": "2.0.0"	"@infor-up/m3-odin": "2.0.0"
"@infor/m3-odin-angular": "2.0.0"	"@infor-up/m3-odin-angular": "2.0.0"
"@infor/m3-odin-cli": "2.0.0"	"@infor-up/m3-odin-cli": "2.0.0"

Legacy Contributor

Hi,



Do you have any documentation on how to connect the SDK to a Multi-tenant environment?

I have been able to connect it to a single-tenant by assigning the M3-proxy and ION-proxy.



Is there an address in a MT environment that can be used against the M3-proxy or is it only ION API that is available?

I have tried to assigning our MT tenant address to both proxys but it doesn't seem to work.



I also see that there are parameters for both multi-tenant and ion-api in odin serve but I'm unsure how to configure this.