M3 Cloud Connectivity

M3 Cloud Connectivity

Introduction

Connecting Comflow to M3 in the cloud has two big differences compared to on prem M3 - Database and API.

The runtime database in M3 cloud is not normally accessible. Though there is a customer Data Lake, to which tables can be mirrored. The mirroring takes often less than a second, so this data base can be used for most of Comflow data access. It is just in specific transactional access, where the data base access must be switched to an API-call instead. This means that most of old Comflow M3 applications will work also for M3 Cloud.

M3 API's are accessed via a connection framework - ION. Apart from having a different authentication and transport, the layout of the API-transactions are basically the same as for on-prem, why the conversion from on-prem to cloud is straight forward.

Connecting Database

Connecting the database, the Data Lake, is the same as setting up an SQL Server connection. See example below:

                      <Server name="SERVER1">
                                 <Services>
                                            <Service name="M3" type="jdbcpool" class="" port="">
                                                      <Parameters>
                                                                 <parameter name="driver" value="net.sourceforge.jtds.jdbc.Driver" />
                                                                 <parameter name="url" value="jdbc:jtds:sqlserver://1.2.3.4:1433/M3Data;domain=DOMAIN;useNTLMv2=TRUE" />
                                                                 <parameter name="user" value="USER" />
                                                                 <parameter name="password" value="xxx" />
                                                                 <parameter name="schema" value="dbo" />
                                                                 <parameter name="validationQuery" value="select 1" />
                                                                 <parameter name="charset" value="UTF-8" />
                                                                 <parameter name="useCaseingOnTable" value="false" />
                                                      </Parameters>
                                            </Service>
                                 </Services>
                      </Server>