Installing a M3BE 15.1.2 Test Lab

This post is to run through the installation of a basic M3 15.1.2 environment. As with my previous documentation of the 10.1 installation – this is about achieving a few things

  1. Create a completely isolated environment that I can test updates with. Even though I have access to production, test and development environments – if something goes wrong then we potentially have an expensive prospect of getting it fixed.
  2. As it is completely isolated, I can do dumb stuff. The things that make sense in the wee hours of the morning, but once they blow up in your face you reflect and think “That was never going to work”
  3. Provides a better understanding of how the newer versions of M3 hang together.

In this post I wanted to minimise the number of servers I needed to spin up – so the entire M3 environment is running off a single virtualised server. Needless to say, shortcuts have been taken – especially around security and some of the configuration. Likewise no consideration has been given to tuning or performance implications.

In general I’ve followed the instructions, but in some instances needed to take a bit of a leap of faith. Where I followed the manual in a section I’ve included the document I was referencing. For convenience I have also included the files that I used for installation.

Following these instructions should give you a basic running test environment, with the M3BE, M3 UI Adapter, Smart Office, LDAP Session Provider and H5 Enterprise client.

Even though the M3 environment is on a single server, I do have Active Directory and DNS set up on another server which acts as another part of my test network.

Please excuse some of the highlighting – occasionally it shoots across the screen which appears to be a bug in the beta version of Windows I’m using and it got rather tedious trying to correct all of the screen captures.


Below is a list of the files that I grabbed to do this installation.







M3 Business Engine

Name:    M3BE152

Active Directory Server

A user, m3auth has been set up in AD for LCM to authenticate against
A group called LCMAdmin has been set up, and m3auth and Administrator have been added to it.
LDAP Port: 389

Users set up in Active Directory:

Install MS Server Standard 2012r2

C: 40 gig
D: 40 gig

Install MS SQL Server 2012 Standard 64bit

This is installed for convenience rather than tuning or good security.



Installation Document


  1. Run Setup
  2. Select Installation
  3. Select New SQL Server stand-alone installation or add features to an existing installation
  4. Click OK
  5. Enter Product Key, click Next
  6. Accept license terms and click Next
  7. Click Next
  8. Click Next
  9. Select Database Engine Services, client tools, management tools, click Next
  10. Click Next
  11. Click Next
  12. Click Next
  13. Click Collation

    (It is recommended to use a specific account, but I’m just running with the default)
  14. Click Customize
  15. Select Latin1_General, tick Binary, click OK
  16. Click Next
  17. Set authentication to Mixed Mode, set a password, assign the current user as an administrator. Click Data directories.
  18. I’m storing my database in D:\Data
  19. Click Next
  20. Click Next
  21. Click Install
  22. Click Close
  23. Open SQL Server Configuration Manager
  24. Select SQL Server Services and ensure that both SQL Server, and SQL Server Agent are set to automatic and are running. With my install I needed to adjust SQL Server Agent
  25. Check that the port for the SQL Server is set to static (SQL Server Network Configuration -> Protocols for MSSQLSERVER -> TCP/IP Properties

    (my IP on my server is
  26. We should set up specific ports in the firewall, but as this is an isolated environment I am just going to disable the firewall altogether.
  27. Turn Windows Firewall On or off
  28. Turn off Windows Firewall
  29. Click OK

Install Java

Note that with our Java install we deviate from the standard install process.





  1. Run the install
  2. Next
  3. Change the path as per the recommendations from the Infor install document (Click Change)
  4. Change the path to remove spaces, click OK
  5. Click Next
  6. Click Change to Change the path again
  7. Remove the spaces from the path again, click OK
  8. Click Next
  9. Click Close

Install LifeCycle Manager Server



Installation Document


  1. Double click on LifeCycleManagerServer_10.1.2.1.jar
  2. Click Next
  3. Click Next
  4. Set a path and click Next
  5. Specify the path to the JDK we installed earlier, click Next
  6. Set the server host to the current server and click Next
  7. Click No for backup routines, next
  8. I have my own LDAP Server – it is an AD server (unlike my previous article). I’m not using SSL as it is a test next network
  9. Change the configuration settings – you’ll need the user and group suffix to tell LCM where to look for your users, and also point to a group that you’ve set up for the LCM admins
  10. I’m going to let LCM create a user to run the LCM server service
  11. Click Next
  12. Click Finish
  13. Check that the LCM service is running from Task Manager

Install LCM Service

  1. Browse to

  2. Tools -> Internet Options
  3. Click Security, Trusted Sites -> Sites
  4. Add
  5. Click Download LifeCycle Manager Service Installation
  6. Click Save
  7. Click Open
  8. Key in the details of the LCM Server
  9. Using the default Name
  10. It’s detected the main IPv4 address, so I’ll press enter
  11. Default path with me is ok
  12. Default Port is OK
  13. Defaults are OK
  14. Select Y to trust the cert

Install LCM Client

  1. Browse to

  2. Click Download LifeCycle Manager Client
  3. Save
  4. Click Open
  5. Click Next
  6. Click Next
  7. Click Next
  8. Click Next
  9. Click Finish
  10. Click Click on the LCM-Client Icon
  11. Key in the username and password (as this is on the same server as the LCM Server, I am just using localhost). This is a user that MUST be in the LCMAdmin group we created in AD
  12. Accept the cert
  13. Click Yes
  14. Click OK
  15. Log in again
  16. Recently Infor have released an update to the default JVM settings for grid applications, click yes to accept them
  17. Apply new version
  18. Click OK
  19. Done

Add M3BE and Foundation to LCM


Installation Document


  1. In LCM Click Admin -> Upload Products
  2. Click Upload
  3. Locate and select the and M3Foundation_10.1.2.0.lcm

    We have the FPs to take us up to .2
  4. Click OK
  5. We can see the two packages have been added, click on Yes to restart LCM
  6. Click OK
  7. Log in to LCM

Install the M3 BE

Installation Document


  1. In LCM select Actions -> Install Product
  2. Click Next
  3. Click Next
  4. Click Next
  5. Click Select
  6. Assign new path
  7. Click Next
  8. Click Next
  9. Select the Admin group we set up in LDAP, click Next
  10. Click Finish – this will take a while
  11. Click OK

Attach Database

Installation Document


  1. In LCM -> Actions -> Attach Product
  2. Select Microsoft SQL Server and click Next
  3. Select where LCM Server is installed, click Next
  4. I’m just dropping all of the files in to the one directory
  5. Click Finish
  6. Click OK
  7. We can now see our SQL Server entry in LCM

Create a database for our Grid

We need to create a database for our Grid

  1. Open Microsoft SQL Management Studio
  2. Right Click on Databases -> Select New Database
  3. Give it a name

Install the ION Grid


Installation Document


  1. In LCM -> Admin -> Products -> Manage Products
  2. Click Upload
  3. Select grid-lcm-installer-
  4. Accept the cert
  5. Click on OK
  6. Click Yes
  7. Click OK
  8. Log back in to LCM
  9. Actions -> Install Product
  10. Select Infor ION Grid, Click Next
  11. Install in to Test, click Next
  12. Enter the database details for our grid
  13. Click Next
  14. We’ll accept the default ports
  15. Click on Finish
  16. Click OK

Install our Environment

Installation Document


  1. In LCM Right click on our TST Grid we set up earlier -> Install Product
  2. Select the Grid we installed earlier and click Next
  3. Click Next
  4. Click Next
  5. Click Next
  6. Click Next
  7. Click Next
  8. Enter our sa password for the database, click Next
  9. Enter some passwords for MDBADM and MDBUSR, I’ve dropped some garbage in to the sender/receiver and mail server
  10. Click Next
  11. Click Finish
  12. Click on OK
  13. And we have our M3BE Environment installed

Install the other BE Packages

This will take us up to version 15.1.2


This includes fixpacks, and market mods

Installation Document


  1. In LCM -> M3BE -> Right Click and Upload M3BE Packages
  2. Tick the packages we want to install and click Next
  3. Click Finish
  4. Right Click our M3BE and select Install M3BE Pacakges
  5. Select the components to install and click Next
  6. Click Finish
  7. Click OK

Create the System Component

Installation Document


  1. In LCM and on M3BE Environment, right click and select Environment Configurator
  2. Click Components -> Click the + icon
  3. I’m installing the AU/NZ Regional mods, typically MAU, so enter MAU
  4. Click Save
  5. Click on OK
  6. Click Configurations, click the + icon
  7. Enter MAU for the regional modification
  8. Give our entry a name and click Save

Create the Database Schema

Installation Document


  1. LCM -> Right Click on the new environment -> Database -> Create Database
  2. Enter the password we provided earlier for MDBADM
  3. M3FDBTST is the schema for a Windows install
  4. Click Finish
  5. Click OK

Create Language Tables

Installation Document


  1. LCM -> Right Click on the new environment -> Database
  2. Enter your MDBADM password, click Next
  3. Select Create language tables for uploaded languages and click Next
  4. Select the two components MVX, MAU and click Next
  5. Select MAU and then click Next
  6. Click Finish
  7. Click OK
  8. Enter in the MDBADM password
  9. Import Database Data and click Next
  10. Select the MAU file to import and click Next
  11. Change the Component so it is our regional modification and click Next
  12. We will replace the existing records, click Next
  13. Click Next

Install Grid Extensions

– this is for the LDAP Session Provider, GDBC, Event Hub

  1. In LCM -> Admin -> Upload Products. Click Upload
  2. Accept the cert
  3. Click OK
  4. Click Yes
  5. Click OK

Install GDBC

  1. LCM -> Right Click Test Grid -> Install Product
  2. Select GDBC and click Next
  3. Click Next
  4. Click Finish
  5. Click OK

  6. Refresh LCM and we should see GDBC and it should be running

Install the LDAP Session Provider

  1. LCM -> Right Click Test Grid -> Install Product
  2. Select Infor LDAP Session Provider
  3. Click Next
  4. Click Next
  5. Click Finish
  6. Click OK
  7. Right Click LDAP Session Provider and select Configure Session Provider
  8. Point to our LDAP server – as this is a test network, I’m not encrypting our connection – but in anything outside of a close test network we should.
  9. Click on Validate to test our connection
  10. Click Next
  11. Enter the username/password and search base
  12. Click Validate to test the authentication details
  13. Click OK
  14. Click Next
  15. Add the base location where we have our users
  16. Click Validate – we should see the users in that context
  17. Click Next
  18. Add the location for our groups
  19. Click Validate
  20. We should see a group from the context. Click Close
  21. Click Next
  22. For the display name, we will use the default attribute of displayName
  23. Click Validate
  24. Enter the name of a user in the context you pointed the LDAP Session Provider at and click Validate
  25. We should get a result. Click Close
  26. Click Finish
  27. Click On Save, to save our settings
  28. Refresh our Test hierarchy and you should see that the LDAP Session Provider is green aswell as the M3BE

Upload our Client Tools


  1. Unzip
  2. LCM -> Admin -> Upload Products, Click Upload
  3. Select our two packages:,
    and Click OK
  4. LCM -> Admin -> Upload Products, Click Upload
  5. Browse to the extracted InforSmartOffice_1020_LCM10 -> Server ->
  6. Click Yes to accept the certs
  7. Click OK
  8. Click Yes
  9. Click OK

Install the M3UI Adapter

  1. LCM -> righ click on our grid -> Install Product
  2. Select M3 UI Adapter and click Next
  3. Click Next
  4. Click Next
  5. Enter a directory for the fileroot
  6. Click Finish
  7. Click OK
  8. Click on Refresh and we should have the M3 UI Adapter and it should be running

Install the Enterprise Client

Note in some versions of Enterprise search, you’ll need to edit the M3_H5_Client_Enterprise/app-user so it is set to authenticated

  1. LCM -> righ click on our grid -> Install Product
  2. Select M3 H5 Client Enterprise and click Next
  3. Select a path for the Mashups and click Next
  4. Click Finish
  5. Click OK
  6. Click Refresh and we should see the M3 H5 Client Enterprise running

Install Mango Server

We should set Internet Explorers security to medium low before we start and add our server to IEs trusted list.

  1. LCM -> righ click on our grid -> Install Product
  2. Select Infor Smart Office and then click Next
  3. Click Next
  4. Select the server we want to install it on and click Next
  5. Set the Default System Profile, and Suffix and click Next
  6. Click Finish
  7. Click OK
  8. Refresh our LCM tree and we should see MangoServer running
  9. Right Click on the MangoServer and select Sign Installation Point
  10. Click Sign Installation Point
  11. Click on Export
  12. Save the installation point
  13. Click Save
  14. Go to where you extracted the, go to the SignTool and unzip it
  15. Go in to the SignTool folder and run SignTool.exe
  16. Click Next
  17. Browse to the location where you exported the MangoServer to
  18. Click Next
  19. Click Create a new self-signed certificate
  20. Specify a name, password and location to create the cert
  21. Click Next
  22. Click Finish

    Note the directory it’s exported to
  23. In LCM right Click on the MangoServer and select Sign Installation Point
  24. Click Sign Installation Point
  25. Click on Sign Installation Point
  26. Click on Browse
  27. Locate the export directory
  28. Click on Import
  29. Click on OK
  30. And you should see the Installation Point was imported message
  31. Right Click on the MangoServer application and select Configure Application
  32. Click Edit Role Mappings
  33. Click on Edit beside Administrator
  34. Click Add
  35. Add users as Administrators to Smart Office (Administrator and m3srvadm)
  36. Click OK
  37. Click Save
  38. Click Save
  39. Repeat for app-admin

Install the Smart Office Client

  1. Browse to our install location
  2. Click Install
  3. Log in to Smart Office with one of the users that you added to the Administrator role above
  4. Administration Tools -> Profile Editor
  5. Click on Advanced
  6. Go down to M3 and enable the M3 Configuration
  7. Scroll down to the MForms section
    1. The Application Server can be determined by going. Right click on the M3BE and select Configure Application

      Scroll down to Connection Dispatchers

      So we will use ( is the IP of our address)
    2. RuntimeURLLogon can be determined by going to the default router.
      Right click on the MangoServer and select Monitor Application

      Click on Web Components

      In the Web Routers section make note of the HTTP Port.

      In IE, enter our servers IP Address and port

      which will redirect you to /grid/info.html
      Scroll down to the mne section

      The highlighted section is our RuntimeUrlLogon and RuntimeUrl
      It should look something like this:

    3. Click Save
    4. Click Next
    5. Close Smart Office

Testing M3 Login

Now we should run Smart Office to test our setup. Note, in your authentication source you must have mvxsecofr set up with a username/password.

  1. Login to Smart Office as mvxsecofr (this is one of the automatically deployed users)
  2. We should see the menus / M3 Transactions in Navigator
  3. We can now create other users

Install the Feature Packs

We’ve already uploaded them to LCM, now we will install them

  1. Right click on the M3BE_15.1_TST -> Fixes -> Apply Feature Pack
  2. We have feature pack 2 to install, so select 2, and put a tick in our regional mods (MAU), click Next
  3. Click Next
  4. Click Next
  5. Click Next
  6. Click Next
  7. Click Finish
  8. Click OK
  9. Click Details
  10. Run through the fixes that are required in the details
  11. Run the Upgrade Database
    1. Right Click on our BE, Select Database -> Upgrade Database with Fix/Feature Pack
    2. Click Next
    3. Enter your mdbadm password and click Next
    4. Click Next
    5. Click Finish
    6. Because we have market mods, we need to repeat the steps with the market mods
      Right Click on our BE, Select Database -> Upgrade Database with Fix/Feature Pack
    7. Click Next
    8. Enter your mdbadm password and click Next
    9. Change the component to MAU – the system configuration will change to MAU automatically. Click Next
    10. Click Finish
  12. Import Database Data
    1. Right Click our M3BE -> Database -> Import Database Data
    2. Enter our database password and click Next
    3. Click Next
    4. Select the fixes listed in the details section from earlier
    5. There was no MAU, so we are only going to be doing the MVX
    6. Click Next

      The names of what we are deploying implies we could just do a clear tables, but I’ll stick with a replace
    7. Click Next
    8. Click Finish
    9. Click OK
      Note, I did originally try importing the FP1 data aswell which resulted in CMNFNG layout mismatches. So on the second attempt I only did the FP2 data which succeeded.
  1. Apply MI metadata
    1. Right click on the M3BE -> Fixes -> Apply MI metadata
    2. Click Next
    3. Enter a M3 username/password
    4. Click Finish
    5. Click on OK

And there we have it – a basic M3 environment up and running.

And if we start Smart Office and run a quick script:

We can see our BE is version 15.1.2

Going to a 15.1.3 install is as simple as applying the and which I will document soon.

This entry was posted in M3 / MoveX, Misc. Bookmark the permalink.

17 Responses to Installing a M3BE 15.1.2 Test Lab

  1. Vikas Sharma says:

    Great detailed explanation.

    We are new to M3. Though we have worked on SAP and JDA. We tried installing M3 Followed the steps as mentioned in “M3 Core Installation PlanningGuide – Windows.pdf” and “M3 Core Installation Guide -Windows.pdf” But were unsuccessful. On 2 separate installation we got 2 different errors. 1. “Application Server is not available though on webapplication page we can see all services are running and up with OK.

    The other instance we got error “User profile not found.”
    We did not install LDAP but using LCM configured AD LDAP and install Windows session manager.
    Version used : M3-13.2 and M-13.3

    Many thanks in advance.
    Vikas Sharma

    • potatoit says:

      Hi Vikas,

      one of the reasons that I have documented the steps in this way is because there are quick a few steps. Missing one or two can result in oddities.

      Without knowing the specifics, I’d struggle to even guess what could be wrong or what parts of your install aren’t working correctly.

      Specifically where do you see the errors?

      • Vikas Sharma says:

        Thanks for reply,
        We get this error when we try to access H5 in browser. Also if integrate the same instance in the ming.le the error is same.

        We try to run a fresh installation as per your documentation except we did not use LDAP. but no luck looks like we are missing some point.


      • potatoit says:

        If I log in to the H5 client with a user that isn’t set up within M3 (MNS150) then I get: “The application server is currently not available”

        So you need to set that user up.

        Initial logins on a clean new environment, you need to log in as mvxsecofr (this user needs to be set up in your authentication source). With mvxsecofr you will be able to run programs and be able to create other users.

        You can see the users that are delivered by looking in the table CMNUSR


      • Vikas Sharma says:

        Great Scott. Many thanks. My problem mentioned above “App server Not found” is solved now by the solution you gave.

        It is bit strange, none of the documentation says one needs to setup mvxsecofr User in AD. and use it to login.

        Thanks again.

        Vikas Sharma

      • potatoit says:

        Hi Vikas,

        I’m glad I wasn’t the only one that didn’t see it (but I am prone to skipping boring parts of documentation :-)).

        The documentation I have found has been getting better but there are still holes.


  2. Hi Scott, great many screenshots, I miss those from the Infor docs. Have you explored installing M3 on AWS, or on Linux?

  3. Magnus Tallqvist says:

    Looking forward to your experience in updating this environment to 13.3. Please read the documentation prior that since there are numerous changes to product to be downloaded as well as the process in doing it.

  4. Nikhil Sood says:

    Hi Scott,

    Thanks for great documentation. I was able to create my test lab using steps mentioned by you.
    I have some questions:
    1. Is there any way to create M3 login for user whose AD ID is more than 10 characters?
    2. Right now after installation i can see all options but all data is empty companies, customers etc. I can see which is due to no company present.Is there a way to get some test data loaded in M3 for practice?

    Thanks in advance

    • potatoit says:

      Hi Nikhil,

      1. unfortunately not as far as I am aware. The only thing that I can think of that you could do to allow staff with usernames that are longer than 10 characters is to use a different attribute from the cn in the LDAP setup. So you could use the comments field for example and have the users truncated username. This unfortunately means that your user will have a different username than that that use to log in to their computer and it means that you will need to populate this field for everyone. I am actually looking at using this technique for IFL as I transition them from their existing usernaming convention to something more consistent.
      2. If you have access to Quick Step (?) then that will populate some base data, or depending on where your lab is set up you can import a copy of your companies database. As far as I am aware, Infor don’t provide a generic testing configuration – it’d be nice but…


  5. Paul Grooby says:

    Scott — this makes me want to come back to M3 World 🙂 — Awesome documentation and examples

    • potatoit says:

      Perhaps you should! I feel that M3 has come a long way in recent years. It’s not perfect, but it doesn’t feel like the BE is stagnating. And there are some pretty kewl technologies that sit around M3 now too…

  6. hi ,

    What is the minimum Server requirement to install M3 Lab ?
    CPU , RAM

    Thank you

    • potatoit says:

      It depends on what you want to achieve.

      For this proof of concept, if memory serves I had about 30gig of RAM in total in my physical server. But I wouldn’t do serious testing on that.

      The installation documents in InforXtreme have minimum requirements – you should use them as a guide. Also, there is no tuning or best practices applied to my install – there are guides available on InforXtreme.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s