ION - Network Connector

This repository contains a demo of the ION Network Connector, the documentation can be found on https://docs.infor.com/ion/latest/en-us/iondeskceug_cloud_osm/default.html, go to Connect Modeling > ION Network connection point. Below procedure partly applies to accessing the ION API Gateway for other API calls.

Infor OS - ION Network Connectors:

Connecting two different Infor OS environments to each other via ION Network Connector.

In the example we combine two different Multi Tenants of Infor OS, similar can be done for Single Tenant or On-Premises.

The Network Connector can be used to connect:

• To replace the ION CC (CloudConnector)
  • upgrade to ION CE and start using the Network Connector
• Multi Tenant environments running in different regions
• Multi Tenant environments from different customers
• Multi Tenant to On-Premises, when receiving messages in On-Premises
  • In case the Infor OS On-Premises was installed with Alias which is registered on the Internet and with a CA signed public certificate:
    • open port 7443 and 443 for traffic from that Tenant to the Infor OS On-Premises
  • In case the Infor OS On-Premises was installed with customer internal Alias which is NOT registered on the Internet and with a internal certificate:
    • create a public alias and corresponding certificate which can be used via the Internet publicly
    • replace the internal names in the *.ionapi file with public names
    • in the network device translate the public URL to the local URL for inbound traffic and the other way round for outgoing messages
    • open port 7443 and 443 for traffic from that Tenant to the Infor OS On-Premises
• Remark: the Infor OS server running On-Premises should be exposed to the internet in a professional way only, using WAP, a gateway or any other network device
  • ensure to have the right IP-addresses of the MT tenant in your region or the client calling the API whitelisted
  • additionally keep the traffic for acceptedDocuments URL encoded!! Check the LID of your Network Connector in the On-Premises server, for example:
  • The Multi Tenant server will send a GET message using the URL encoded Logical ID.
  • e.g. https://inforos.acme.com/InforIntSTS/IONSERVICES/api/ion/messaging/service/v3/lid%3A%2F%2Finfor.iondesk.iondesk%2Fnetworkconnector/acceptedDocuments
  • having a body like

    {
      "logicalId": "lid://infor.iondesk.iondesk/networkconnector"
    }
    

• Multi Tenant to Single Tenant, when receiving messages in Single Tenant
  • this requires Cloud Ops to open port 7443 and 443 for traffic from that Tenant.

Check https://docs.infor.com for documentation, search for "Enterprise Connector prerequisites"

Support for Network connectors in ION:

• 2020-12 introduction of the network connection point
• 2021-06 support pausing of network connection points

For Infor Employees:

• Create Incident to open Single Tenant for traffic from that specific Multi-Tenant only.
• Specify the relevant IP-addresses to be put on the Whitelist found at: https://inforwiki.atlassian.net/wiki/spaces/MTIOS/pages/152732588/MT+Application+NAT+List
• If Single Tenant is not opened correctly for traffic from that MT the testing the Network Connector will result: Error occurred while generating Oauth access token for 'https://dev.cloud.infor.com:7443'. Reason: Unable to get Oauth20 token due to : Connection timed out
• The Network Connection Point is using the ION API for connectivity and authentication
• The Network Connection Point is based on using the IMS messages
  • IONSERVICES/api/ion/messaging/service/ping (to check if the remote ION API is up and running)
  • IONSERVICES/api/ion/messaging/service/versions (to check the version remotely)
  • IONSERVICES/api/ion/messaging/service/v3/lid://infor.iondesk.iondesk/<your Backend Service Name>/acceptedDocuments (to check the acceptedDocuments, what else.. )
  • IONSERVICES/api/ion/messaging/service/v3/multipartMessage (to send the BOD finally )

Connecting Infor OS deployments, Multi Tenant & On-Premises

• Bidirectional or Unidirectional (Receive from/ Send to Partner) integration
• Using ION API as proxy (authorized app)
• On-Premises and Single Tenant:
  • Authentication via port 443: "pu": "https://inforos.acme.com/InforIntSTS/"
  • ION API via port 7443: "iu": "https://inforos.acme.com:7443"
• On Multi Tenant:
  • Authentication via port 443: "pu": "https://mingle-sso.yourinforcloudsuite.com:443/{TenantName}/as/",
  • ION API via port 7443: "iu": "https://mingle-ionapi.yourinforcloudsuite.com"

DEMO: using ION Network connection point (Unidirectional)

• Connecting Infor OS deployments, Two Multi Tenants
• First Unidirectional
  • Send to Partner MingleTest1 & Receive from EDUGDENA031

Summary

On Receiving Tenant

• Create Authorized App of type Backend Service,
• Download Credentials, Create Service Account,
• Download *.ionapi file
• Create Network Connection Point, import local *ionapi file
• Create Data Flow to process received documents

On Sending Tenant

• Create Network Connection Point, import remote *ionapi file
• Create Data Flow to generate documents to be sent

BiDirectional

• Same steps to be repeated vice versa

ION API – Authorized App (Backend Service)

On Receiving Tenant

• Create Authorized App of type Backend Service
• Download Credentials
• Create Service Account (use a Service User)
• Download *.ionapi file

ION Desk - Network Connector (receiving)

On Receiving Tenant:

• Create Connection Point (ION Network)
• Direction: Receive from Partner
• Import Local *.ionapi
• Documents to be received from Partner (LN_Enum & LN_tcibd001)

ION Desk - Data Lake Flow (receiving)

On Receiving Tenant:

• Create Data Lake Flow (demo only)
• Select Documents (LN_Enum & LN_tcibd001)

ION Desk - Network Connector (sending)

On Sending Tenant:

• Create Connection Point (ION Network)
• Direction: Send to Partner
• Import Remote *.ionapi
• Documents to be sent to Partner (LN_Enum & LN_tcibd001)
• Testing connection is possible now

ION Desk - Document Flow (sending)

On Sending Tenant:

• Create Document Flow
• Select Documents (LN_Enum & LN_tcibd001)

ION Desk - OneView (testing)

• Trigger Documents in sending Application and check OneView
• Check OneView and receiving Application

DEMO: using ION Network connection point (Bidirectional)

• Connecting Infor OS deployments, Two Multi Tenants
• BiDirectional =
  • Send to Partner MingleTest1 & Receive from EDUGDENA031
  • Send to EDUGDENA031 & Receive from Partner MingleTest1

ION API - Authorized App (Backend Service)

On Receiving Tenant:

• Create Authorized App of type Backend Service
• Download Credentials
• Create Service Account (use a Service User)
• Download *.ionapi file

ION Desk - Network Connector ( BiDirectional

On the Receiving Tenant:

• Change Connection Point (Network Connector)
• Direction: BiDirectional was “Send to Partner”
• Import Local *.ionapi
• Documents to be received from Partner (Process.ItemMaster)

ION Desk - Document Flow (receiving)

On the Receiving Tenant:

• Create Document Flow
• Select Documents (Process.ItemMaster)

ION Desk - Network Connector (sending)

On the Sending Tenant:

• Change Connection Point (Network Connector)
• Direction: BiDirectional was “Receive from Partner”
• Import Remote *.ionapi
• Select Documents (Process.ItemMaster Send To Partner)
• Testing connection is possible now

ION Desk - Document Flow (sending)

On the Sending Tenant:

• Create Document Flow (IMS via ION API is used to publish documents to the Connection Point)
• Select Documents (Process.ItemMaster)

ION Desk - OneView (testing)

• Trigger Documents in sending Application
• Check OneView on both Tenants and receiving Application if document is received