M3coretech 13.4.0 M3coreig Windows En-Us

M3 Core Installation Guide -
Windows
Release 13.4.0
Copyright © 2023 Infor
Important Notices
The material contained in this publication (including any supplementary information) constitutes and contains
confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any modification,
translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest
therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including
any modification, translation or adaptation of the material) by virtue of your review thereof other than the
non-exclusive right to use the material solely in connection with and the furtherance of your license and use
of software made available to your company from Infor pursuant to a separate agreement, the terms of which
separate agreement shall govern your use of this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain
such material in strict confidence and that your use of such material is limited to the Purpose described above.
Although Infor has taken due care to ensure that the material included in this publication is accurate and
complete, Infor cannot warrant that the information contained in this publication is complete, does not
contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume
and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity
which is caused by or relates to errors or omissions in this publication (including any supplementary
information), whether such errors or omissions result from negligence, accident or any other cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern your use of
this material and you will neither export or re-export, directly or indirectly, this material nor any related
materials or supplemental information in violation of such laws, or use such materials for any purpose
prohibited by such laws.
Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor and/or
related affiliates and subsidiaries. All rights reserved. All other company, product, trade or service names
referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Release: Infor M3 Core Technology 13.4.0
Publication Date: November 27, 2023
Document code: m3coretech_13.4.0_m3coreig_windows_en-us
Contents
Contents
Chapter 1: Introduction and overview...........................................................................................9

What is M3 Core?................................................................................................................................................9
Knowledge Prerequisites.................................................................................................................................10
Prerequisites.....................................................................................................................................................10
Handover from installation planning..............................................................................................................10
Chapter 2: Installing and preparing LifeCycle Manager..................................................................12
Installing a LifeCycle Manager Server.............................................................................................................12
Preparing for installation.............................................................................................................................12
Installing a LifeCycle Manager Server..........................................................................................................12
Completing the installation using a manual LDAP.....................................................................................14
Completing the installation using a pre-configured AD LDS instance.......................................................16
Installing LifeCycle Manager Services.............................................................................................................17
LifeCycle Manager Service installation considerations..............................................................................17
Installing a LifeCycle Manager Service on Windows...................................................................................18
Installing a LifeCycle Manager Client..............................................................................................................19
Logging on to the LifeCycle Manager Client...................................................................................................20
Attaching middleware to LifeCycle Manager..................................................................................................21
Attaching middleware to LifeCycle Manager Java......................................................................................22
Attaching middleware to LifeCycle Manager SQL Server...........................................................................22
Setting up a space............................................................................................................................................23
Chapter 3: Uploading M3 Core to LifeCycle Manager......................................................................24
Downloading and updating LifeCycle Manager Server with product package.............................................24
Applying update...........................................................................................................................................24
Retrieving fixes.................................................................................................................................................25
Chapter 4: Verify M3 Documentation URLs...................................................................................26
Verify the M3 BE User Documentation Infocenter..........................................................................................26
M3 Core Installation Guide - Windows | 3

Contents
Obtaining an SSL certificate........................................................................................................................26

Installing a Self-Signed SSL Certificate.......................................................................................................27
Chapter 5: Install Infor ION Grid and M3 Core................................................................................29
Install ION Grid.................................................................................................................................................29
Installing Infor ION Grid...............................................................................................................................29
Verifying the Grid..........................................................................................................................................33
Configuring host SSL certificate..................................................................................................................33
Preparing users................................................................................................................................................33
User management in Infor Ming.le..................................................................................................................34
Enable editing of the property IFS Person ID..............................................................................................34
Importing M3 users in Infor Ming.le 12........................................................................................................35
Manual configuration of the property IFS Person ID..................................................................................35
Automatic configuration of the property IFS Person ID - latest.................................................................35
SAML Session Provider.....................................................................................................................................36
Installing and configuring the SAML Session Provider...............................................................................36
Install the SAML Session Provider using LifeCycle Manager......................................................................36
Verify the SAML configuration.....................................................................................................................40
Configuring Login and Logout Endpoints...................................................................................................40
Grid Database Connectivity (GDBC)................................................................................................................41
Installing the Grid Database Connectivity (GDBC)......................................................................................41
Managing Database Drivers for GDBC.........................................................................................................42
Viewing Grid Database Connectivity Application (GDBC) Configuration Information..............................44
Event Hub and Event Analytics........................................................................................................................45
Installing Event Hub.....................................................................................................................................45
Installing Event Analytics.............................................................................................................................45
Install M3 UI Adapter........................................................................................................................................46
Installing M3 UI Adapter...............................................................................................................................46
Attaching an M3 UI Adapter Database.........................................................................................................48
Changing M3 UI Adapter Database connection..........................................................................................48
Install M3 H5.....................................................................................................................................................48
Installing M3 H5 Enterprise..........................................................................................................................48
Install M3 Business Engine...............................................................................................................................49
Installing M3 Business Engine release 15.1.................................................................................................49
Attaching an M3 Business Engine Database...............................................................................................50
Installing an environment............................................................................................................................51

Contents
Install M3 Business Engine layouts..................................................................................................................55

Attaching middleware - OpenText StreamServe/Exstream.......................................................................55
Connect OpenText StreamServe/Exstream to M3 Business Engine Environment....................................56
Overview.......................................................................................................................................................56
Install base to an additional component........................................................................................................57
Creating a system configuration in M3 BE...................................................................................................57
Creating a database schema........................................................................................................................59
Creating new language tables.....................................................................................................................60
Importing a database data for additional component...............................................................................60
Uploading and installing additional M3 BE packages................................................................................63
Uploading and installing additional M3 BE packages....................................................................................64
Additional M3 BE Package Types.................................................................................................................65
Uploading M3 BE Packages..........................................................................................................................65
Installing M3 BE packages............................................................................................................................66
Install additional languages............................................................................................................................66
Create language tables................................................................................................................................67
Import database data..................................................................................................................................67
Create system language...............................................................................................................................70
Generate M3 BE Menu for Infor Smart Office..............................................................................................70
Install document languages............................................................................................................................70
Install document languages........................................................................................................................70
Install feature packs.........................................................................................................................................71
What is a Feature Pack?...............................................................................................................................71
Installing Modifications for a New Market After Installing a Feature Pack................................................72
Apply feature pack.......................................................................................................................................72
Update Environment with Delta Languages...............................................................................................73
Applying MI metadata..................................................................................................................................74
Run Fix Programs..........................................................................................................................................75
Install fixes........................................................................................................................................................76
HFix – Hot Fix................................................................................................................................................77
VFix – Verified Fix..........................................................................................................................................77
How to Download and Install in CCSS Mode...............................................................................................78
MCE - Maintenance Correction Entity..........................................................................................................78
MCP - Maintenance Correction Pack...........................................................................................................78
Upload Fixes Package..................................................................................................................................79

Contents
Apply Fixes....................................................................................................................................................80
Update Environment with Delta Languages...............................................................................................82
Applying MI metadata..................................................................................................................................83
Run Fix Programs..........................................................................................................................................84
Install M3 Foundation Information Reader.....................................................................................................85
Install M3 Web Services....................................................................................................................................85
Install the M3 Web Services application......................................................................................................85
Verify that the MWS Grid application is running.........................................................................................86
Install Infor Enterprise Collaborator...............................................................................................................86
Setting the Central File folder......................................................................................................................86
Installing IEC Database................................................................................................................................87
Attaching IEC Database................................................................................................................................88
Installing IEC in Infor ION Grid.....................................................................................................................88
Verifying IEC Server installation..................................................................................................................91
Adding full control access to the Central File folder...................................................................................92
Installing IEC Client tools.................................................................................................................................92
Installing Partner Admin tool.......................................................................................................................93
Verifying Partner Admin tool installation....................................................................................................93
Troubleshooting...........................................................................................................................................94
Installing Business Document Mapper........................................................................................................94
Starting and verifying Business Document Mapper installation...............................................................96
Installing Flat File Definition tool................................................................................................................96
Verifying Flat File Definition tool installation.............................................................................................96
Install M3 Financial Business Messages..........................................................................................................97
Installing Financial Business Messages.......................................................................................................97
Install M3 BOD Processor.................................................................................................................................98
Installing M3 BOD Processor........................................................................................................................98
Install Workflow Executor................................................................................................................................98
Installing Workflow Executor.......................................................................................................................98
Install M3 Adaptation Kit..................................................................................................................................99
Installing M3 Adaptation Kit through LifeCycle Manager...........................................................................99
Install M3 Metadata Publisher.......................................................................................................................100
Installing M3 Metadata Publisher..............................................................................................................100
Selecting a database for MDP installation................................................................................................101
Chapter 6: Post M3 SW Component installation...........................................................................103

Contents
Post M3 SW Component installation.............................................................................................................103

Appendix A: AD LDS in LifeCycle Manager...................................................................................104
AD LDS users and groups...............................................................................................................................104
Adding a user to LCMAdmins group..........................................................................................................105
Creating a new user group in AD LDS........................................................................................................105
Creating a new user and adding the user to an existing user group in AD LDS.......................................105
Changing password using ADAM ADSI tool...............................................................................................105
Adding user management permissions to the LCMADAM instance.............................................................106
Configuring LCM Server to use SSL for AD LDS.............................................................................................107
Enabling SSL on AD LDS.............................................................................................................................107
Validating LDAPs to access AD LDS............................................................................................................107
Importing CA certificate to a LifeCycle Manager keystore.......................................................................107
Validating LDAPs to access AD LDS instance............................................................................................108
Appendix B: Security................................................................................................................109
Securing Access to M3 BE...............................................................................................................................109
Setting up Trust Between External Applications and M3 BE........................................................................109
Securing M3 BE Installation Folder...............................................................................................................110
Security issues................................................................................................................................................111
Restrict physical access.............................................................................................................................111
Backup........................................................................................................................................................111
Passwords...................................................................................................................................................111
Perimeter defense......................................................................................................................................112
Antivirus program considerations.............................................................................................................113

Version Log
Version Log
The version log describes the changes between versions of this document.
Part Number Release Date Description

1.0 2015-05 First release of this document
2.0 2015-11 Republished for 13.3.0
3.0 2016-09 Updated for 13.4.0
4.0 2016-09 Corrections
Contacting Infor
If you have questions about Infor products, go to Infor Concierge at https://
mingle-portal.us2.prd3.inforcloudsuite.com/v2/CONCIERGE_PRD and create a support incident.
For the latest documentation, go to Documentation Central at docs.infor.com. We recommend that you check
this website periodically for updated documentation. If you have comments about Infor documentation,
contact documentation@infor.com.

Introduction and overview
Chapter 1: Introduction and overview
What is M3 Core?
For companies in the business to Make, Move and Maintain products, Infor M3 provides the tools they need
to manage their operations. With the full system, they can monitor transactions throughout their organization,
including manufacturing operations, supply chain activities, customer and supplier relationships, warehouse
and distribution processes and, of course, financial management. Infor M3 consolidates these into one
coherent view of operations.
While the complete M3 Solution is made up of several different Software Components, where some are unique
for just a certain industry or micro vertical, there are a number of components that will be common for all
M3 installations no matter for what industry. These components are gathered under the Product Family
named M3 Core.
This guide will be covering the necessary steps to install these components, M3 Core.
M3 Core
M3 Business Engine
M3 Financial Business Messages
M3 Core Infrastructure and Technology
LifeCycle Manager
ION Grid
Session Providers
M3 Core Technology
Grid Database Connectivity (GDBC)
Event Hub
Event Analytics
M3 UI Adapter
H5 Enterprise
M3 Foundation
Web Services Runtime
Infor Enterprise Collaborator (IEC)

BOD Processor
Workflow Executor
M3 Adaptation Kit
M3 Metadata Publisher
The Installation guide is the second in a set of three guides:

• Planning in the guide, "M3 Core Installation Planning Guide"
• Software installation in the guide "M3 Core Installation Guide"
• Post-installation, upgrade and administration in the guide "M3 Core Administration Guide"
These guides cover all necessary aspects and steps to establish the installation of the components above and
can be found on docs.infor.com.
Knowledge Prerequisites
To install M3 Core, you must have:
• Experience installing and administering operating systems.
• Experience installing and administering databases.
• Experience working with user authentication management.
• Experience installing and administering networks.
• Experience installing and configuring applications
Prerequisites
M3 Core requires certain hardware and software components to run properly.
• Ensure that all necessary preparatory steps that are outlined in the M3 Core Installation Planning Guide
have been carried out.
Handover from installation planning

Use the Excel worksheet published with the M3 Core guides. It serves as a handover document containing
the server set-up performed using the Installation Planning Guide. The document contains information about
server IP addresses and other details, and the required SW installations to be performed on each server.

Use the handover document to install M3 Core using this M3 Core Installation Guide.

Installing and preparing LifeCycle Manager
Chapter 2: Installing and preparing LifeCycle Manager
This chapter contains information on installing LifeCycle Manager and its components.
Installing a LifeCycle Manager Server

Note: Before installing a LifeCycle Manager Server, verify that all the requirements are met. Refer to the
chapter Install M3 Home Server in the M3 Core Installation Planning Guide.
Preparing for installation

1 Create a temporary directory for the installation file.
2 Download the required file LifeCycleManagerServer_<version>.jar from the Infor Download Center to a
temporary directory.
Installing a LifeCycle Manager Server

1 Open a command prompt.
If you are not using the Windows built-in local Administrator account and UAC is enabled, then you must
start the command prompt with the option to Run as Administrator. Right-click the cmd shortcut and
select Run as Administrator.
2 Navigate to the directory where the .jar file is located.
3 Run the command to start the installation of the LCM Server.
If no default Java is installed, specify the full path to Java in the bin directory of the Java JDK installation.
For example, run this command "C:\<path to jdk>\bin\java" -jar LifeCycleManagerServer_10.1.x.x.jar
and press Enter.
4 Click Next.
5 Select to Install a new server.
6 Click Next.

7 Select the destination folder or browse to another location. Ensure that the selected destination folder
does not contain any folder named LCM-Server.
8 Click Next.
9 Select the path or browse to another location for the Java JDK installation to use for the LifeCycle Manager
Server.
10 Click Next.
11 Specify this information:
Server host:
Select the server IP address or hostname.
If you select to install the LifeCycle Manager Server using the server's hostname instead of IP address,
ensure that name resolution is working on your network. The server hosting LifeCycle Manager Server
must be accessible from both the hosts where LCM Services will be installed and from the LifeCycle
Manager Client computers using the LifeCycle Manager Server hostname or FQDN.
Base port:
Accept the default value (4060) if not in use, or specify a base port number for a range of four ports that
will be used for LifeCycle Manager Server communication.
12 Click Next.
13 Specify this information to set up the backup strategy for the LifeCycle Manager Server:
Note: Ensure that a backup of the LifeCycle Manager Server installation directory is frequently created
and verified in case of a crash of the server where LifeCycle Manager Server is installed.
Configure backup routines
If you select No, all the backup routine parameters are disabled. If you select to configure backup routines
later, you must configure the backup routines directly in the lcm.properties file located in the folder of
the LifeCycle Manager Server installation. For more information about the backup settings in lcm.prop
erties, see LifeCycle Manager Administration Guide.
Backup path
Specify the destination where the backup should be placed. Specify the IP address or name of the remote
server and folder name. The folder name must already exist because it will not be automatically created.
Note: Ensure that the server used for backup of LifeCycle Manager Server is frequently backed up. We
recommend that you use a server that is frequently backed up, for example the M3 Home server or the
M3 Database server if applicable.
Backup user
Specify the user who has necessary privileges to access and create files on the server where the backup
will be created.
If the backup server is a member of a domain, specify Domain\User. If the backup server is not a member
of a domain, then specify Server\User.
Backup user password

Specify the password of the backup user.
Note: The backup user password cannot end with @.

Day of week to run backup

Select what day of the week the backup will be run or select everyday.
Time to start backup

Select what time the backup will be started. A backup of the database will not take more than a minute
or two.
Remove backup after following number of days

Select this option backups must be deleted after the number of days you have specified (default is to
never remove the backup).
14 Click Next to display the LDAP Configuration window and select whether to use Manual configure for a
central LDAP server or a pre-configured AD LDS instance.
15 Consider these options:
• If you plan to install LifeCycle Manager using your existing LDAP server, perform the task Completing
the installation using a manual LDAP. For more information, see LifeCycle Manager LDAP
considerations in the M3 Core Installation Planning Guide.
• If you want to install a pre-configured AD LDS instance, perform the task Completing the installation
using a pre-configured AD LDS instance. For more information, see AD LDS in LifeCycle Manager.
Completing the installation using a manual LDAP

Note: Ensure that you have the LDAP installation values from the M3 Core Installation Planning Guide available
as you complete this portion of the installation. Refer to the LDAP Settings in the M3 Core Installation Planning
Guide.
1 Select the option to Manually configure settings for a central LDAP server.
LDAP server
Specify the host ID, either an IP address or domain name service (DNS) name of the LDAP server. For
example, specify ldap.company.com or 10.20.30.40.
LDAP port
Specify the host port of the LDAP server.
Bind user (distinguished name)

Specify the distinguished name for the LifeCycle Manager Server that will be used when binding to the
directory service.
Bind user password

Specify the bind user password.
Note: The bind user password cannot end with @.

SSL enabled
Optionally, select Yes or No depending on whether a secure socket communication is enabled in the
LDAP server.
Trust store password

Optional. This setting is needed only if SSL is enabled. Specify the password for the keystore.
Note: The trust store password cannot end with @.
Retype Trust store password

Specify the Trust store password for the keystore.
3 Click Next.
User prefix
Specify the attribute that LifeCycle Manager will use to display the user name of users in the directory
service.
Group prefix
Specify the attribute that LifeCycle Manager will use to display the group name of groups in the directory
service.
User suffix
Specify the base distinguished name which indicates the starting point for LDAP searches of users in the
directory service.
Group suffix
Specify the base distinguished name which indicates the starting point for LDAP searches of groups in
the directory service.
Group member attribute

Specify the attribute for groups in the directory service that LifeCycle Manager will use to determine
which users are members of that group.
User search filter

Specify the LDAP user filter that searches the user registry for users.
Note: With this search filter, a user can log on with either the value found in cn or the value found in
sAMAccountName. The user name used in LifeCycle Manager is determined by the User prefix setting.
Group search filter

Specify the LDAP user filter that searches the user registry for groups.
LCM admin group

Specify a group name in the user registry that points to the LifeCycle Manager Administrators group.
Members of this group are allowed to perform all tasks in LifeCycle Manager.
Note: LifeCycle Manager must be able to find this group with an LDAP search using the group search
filter.

LCM user group

Specify a group name in the user registry that point out the LifeCycle Manager user group. Members of
this group are allowed to log on to LifeCycle Manager but are not trusted to manage applications.
Note: If this field is left blank, all users that are found with an LDAP search using the user search filter
Are allowed to log on to LifeCycle Manager. LifeCycle Manager must be able to find this group with an
LDAP search using the group search filter.
These values are written in the LCMInstallDir\LCM-Server\lcm.properties file. You can use a text editor
to change values if you make a mistake during the installation, or want to change values later. The server
must be restarted after the values in the lcm.properties file have been changed.
5 Click Next. The Service Account window is displayed prompting you to select whether to create a new
service account user or to use an already existing user.
6 Perform one of these options:
• Click Yes to create a new service account user, go to step a.
• Click No to select an existing user, go to step b.
a Specify this information:
Service account user
Specify the name of the user.
Service account password

Specify the password for the user.
Retype password
Specify the password.
b Specify this information:

Select a local administrator user from the list.

Specify the password for the local administrator user.
7 Click Next twice to initialize the installation.

8 Click Finish. The Windows service LCM-Server is automatically started. You can view the service in
Computer Management > Services and Applications > Services.
Completing the installation using a pre-configured AD LDS

instance
1 Select the option to use a Preconfigured AD LDS (Active Directory Lightweight Directory Services).
2 Click Next. Service Account window is displayed prompting you to select whether to create a new service
account user or to use an already existing user.

3 Perform one of these options:

• Click Yes to create a new service account user, go to step a.
• Click No to select an existing user, go to step b.
a Specify this information:
Specify the name of the user.

Specify the password for the user.
Retype password
b Specify this information:

Select a local administrator user in the list.

Specify the password for the local administrator user.

5 Click Finish. Two Windows services, LCMADAM and LCM-Server are started. You can view these services
inComputer Management > Services and Applications > Services.
Installing LifeCycle Manager Services

Use these procedures to install the LifeCycle Manager Services.
LifeCycle Manager Service installation considerations

A LifeCycle Manager Service must be installed on each server hosting an Infor product that is managed in
LifeCycle Manager.
Before installing a LifeCycle Manager Service, verify that all the requirements are met. Refer to the chapters
Install M3 Home Server and Install M3 Application and M3 Database Servers in the M3 Core Installation Planning
Guide.
Note: If you cannot, for some reason, have a LifeCycle Manager Service installed on the M3 server that holds
a SQL Server installation (M3 Home Server or M3 Database Server), you must add the database server as an
external host in the LifeCycle Manager Client Hosts tab. For more information, see Managing hosts in LifeCycle
Manager Administration Guide.

Installing a LifeCycle Manager Service on Windows

1 Go to http://LifeCycle_Manager_Server_IP_address:Port# where Port# is the number you specified for the
LifeCycle Manager Server port, plus 2.
• If you used the default value (4060), the Port# is 4062.
• If you do not know the value, look in the LCMInstallDir\LCM-Server\lcm.properties file for the value
of http.server.port.
2 Click Download LifeCycle Manager Service Installation.
3 Click Save. The installLcmService.jar file is saved to a temporary folder on the Windows server.
4 Open a command prompt (Admin).
If you are not using the Windows built-in local Administrator account and UA) is enabled, then you must
start the command prompt with the option to Run as Administrator. Right-click the cmd file and select
Run as Administrator.
5 Navigate to the directory where the jar file is located.
6 Run the command to start the installation of the LCM service. You must specify the full path to java in
the bin-directory in the Java JDK installation. You must install JDK directly in the root. Ensure that there
are no spaces in the directory name. For example, run this command "C:\<path to jdk>\bin\java" -jar
installLcmService.jar and press Enter.
Note: If the currently available Java 8 update does not have support for the Windows OS version you are
using, an additional parameter is required during the installation of LCM service. If installing on, for
example, Windows 2019 run this command C:\<path to jdk>\bin\java -jar -Dos.name="Windows
Server 2019" installLcmService.jar and press Enter.

LCM Server IP
Specify the LifeCycle Manager Server IP address or FQDN, and press Enter.
LCM Server port

Press Enter to accept the default port (4060), or specify a different port number matching the setting
made when installing the server, and press Enter.
LCM Server Admin

Specify the name of a user who is a member of the LifeCycle Manager Administrators group, and press
Enter.
LCM Server Admin Password

Specify the password for the user, and press Enter.
LCM Server HTTP update port

This port is used to fetch the LifeCycle Manager Service installation program. Press Enter to accept the
default port (4062) or tspecify the correct port number, and press Enter.
Note: This question is only shown if the property http.server.port in the lcm.properties file has been
edited.
LCM Service name

Specify a name for the LifeCycle Manager Service, and press Enter.

We recommend that you use the host name of the application server.
LCM Service IP
Specify the computer IP address where the LifeCycle Manager Service must be installed. If the computer
is set up to use Dynamic Host Configuration Protocol (DHCP), specify the FQDN instead. Ensure that you
specify an external IP number.
LCM Service installation path

Press Enter to accept the default value, or type the desired path where the LifeCycle Manager Service
will be installed and then press Enter. Ensure that this directory does not yet exist on your system.
LCM Service port

Press Enter to accept the default value 4065 or specify a desired port number, and press Enter.
A message is displayed if the port you are trying to access is already in use.
Port interval (from port - to port)

Select the range of ports that will be used when Job executing nodes are started by the LifeCycle Manager
Service. New nodes are started either by requests from the system or a product handled by LifeCycle
Manager that needs a specific execution node to run its job in. If the default ports 4066 - 4075 are occupied,
another range must be selected.
Trust this certificate chain (Y/N)

Specify Y if you trust the certificate chain.
8 Press Enter to finish the installation and start the LifeCycle Manager Service.
9 Check the Windows Services to ensure that the LifeCycle Manager Service you installed is started.
Note: Perform these actions to start and stop the LifeCycle Manager Service:
Start: Start the Windows Service LCM-Service:service_name.
Stop: Stop the Windows Service LCM-Service:service_name.
Installing a LifeCycle Manager Client

Use this procedure to install a LifeCycle Manager Client. This version of LifeCycle Manager Client is not
compatible with LifeCycle Manager Server 10.1.1.0 or earlier versions.
Before installing a LifeCycle Manager Client, verify that all the requirements are met. Refer to the chapter
Install M3 Project Admin Client/Server in the M3 Core Installation Planning Guide.
Note: Installing the new LifeCycle Manager Server requires that an LCM Client 10.1.x is installed. In LifeCycle
Manager version 10.1.4.0, it is possible to update your LCM Client 10.1.X to a newer version of the LCM Server.
However, once updated, you cannot use it against earlier versions of LCM Server (10.1.1.0 or earlier). It is
possible to have both old and new versions of the LifeCycle Manager Client installed on the same computer.
1 Go to http://LifeCycle_Manager_Server_IP_address:Port# where Port# is the number you specified for the
LifeCycle Manager Server port, plus 2.


• If you do not know the value, look in the LCMInstallDir\LCM-Server\lcm.properties file for the value
of http.server.port.
2 Click Download LifeCycle Manager Client.
3 Click Save to save the LifeCycleManagerClient.jar file to a temporary folder on your local machine.
4 Open a command prompt.
If you are not using the Windows built-in local Administrator account and UAC is enabled, then you must
start the command prompt with the option to Run as Administrator. Right-click the cmd file and select
Run as Administrator.
5 Navigate to the directory where the .jar file is located.
6 Run the command to start the installation of the LCM Client.
If no default Java JDK is installed, you must specify the full path to Java in the bin directory in the Java
JDK installation. For example, run this command "C:\<path to jdk or jre>\bin\java" -jar LifeCycle
ManagerClient.jar and press Enter.
7 Click Next.
8 Select to Install a new client.
9 Specify a name for the new client. This name will be the name of the shortcut created and the name of
the folder where this client will be installed.
10 Click Next.
11 Select the destination folder or browse to another location. Ensure that the selected destination folder
does not contain any folder with the same name as your LCM Client (for example, LCM-Client).
12 Consider these scenarios before selecting the Installation Directory:
• If you install the LifeCycle Manager Client in the Program Files directory and UAC is enabled, it is
required that you start the LifeCycle Manager Client using an Administrator account. We recommend
that you change the compatibility level first before starting the application. For more information,
see Changing the Compatibility Level in the M3 Core Administration Guide.
• If you install the LifeCycle Manager Client in the Program Files directory and UAC is enabled, but you
do not want to change the compatibility level, you must start the LifeCycle Manager Client by selecting
the Run as administrator option. For more information, see Logging on to the LifeCycle Manager
Client on page 20.
• If you install the LifeCycle Manager Client in a folder that does not require administrative rights, no
further steps are needed to start and run the LifeCycle Manager Client.

14 Click Finish.
Logging on to the LifeCycle Manager Client

1 On the Start menu, click the LCM-Client shortcut. It will have the name provided during the installation.
If you installed the LifeCycle Manager Client under the Program Files folder and have UAC enabled and
did not change the compatibility level for the LifeCycle Manager.exe file, then you must right-click the

LifeCycle Manager Client shortcut (for example, LCM-Client) and select Run as administrator from the
menu.
User
Specify your LifeCycle Manager user name.
Note: The next steps required that the user is a member of the LCMAdmins group.
Password
Specify the corresponding password for the user.
Server
Specify the IP address or domain name of the LifeCycle Manager Server.
Port
Specify the LifeCycle Server port number. The default value is 4060.
Workspace
Accept default path to the workspace, or click Browse to select a different workspace location.
3 Click Log On. The server certification information window is displayed when the LifeCycle Manager Client
connects to a server for the first time.
4 Click Yes to accept the certificate.
5 Click Yes to update the client then click OK to restart LifeCycle Manager.
6 Specify the required information and click Log On. LifeCycle Manager is now started. A dialog box is
displayed if a new Java configuration file for Grid applications is available on the CCSS server.
7 Click Yes to review the changes. A compare window is displayed.
8 Click Apply New Version to apply the new configuration file.
For more information regarding Retrieving Grid Java Configuration, see LifeCycle Manager Administration
Guide.
Note: If you attempt to log on to a version of LifeCycle Manager Server earlier than 10.1.2.0 using your
newly installed client, a message is displayed informing you that an earlier version of LifeCycle Manager
Client is required to connect to that server.
Attaching middleware to LifeCycle Manager

Attach these middleware to the M3 Database Server and the M3 Home Server:
For Windows server, attach SQL Server and Java.

Attaching middleware to LifeCycle Manager Java

On the Windows servers, we recommend that both 32-bit and 64-bit java are installed. Ensure that both are
attached to LifeCycle Manager on all the hosts used by Infor ION Grid.
1 Click Actions > Attach Product.
2 Select Jave from the list and click Next.
3 Select the host where Java is installed. Click Next.
Name
Specify the name of the java version. For example, Java 1.8.0_202 32-bit.
Description
Specify a description.
Installation Path
Select the path to your JDK installation. For example, E:\jdk1.8.0_202_32.
5 Click Next.
6 On the Summary screen, verify the property values and click Finish to start the task.
7 Click OK.
To view the log file, either click View log or go to the Logs view.
Attaching middleware to LifeCycle Manager SQL Server

The SQL Server middleware must be attached to all servers that will be hosting M3 databases.
Verify that the SQL Server instances are configured to use a static port.
2 Select the Microsoft SQL Server from the list and click Next.
3 Select the Location (the LifeCycle Manager Service) where the middleware is installed. Click Next.
Name
Specify a name for your middleware.
Description
Specify a description for your middleware.
SQL Server version

Select Microsoft SQL Server version to attach.
Default log directory

Specify a folder for the system transaction logs.
For example X:\SQLLogs

Note: This field is optional and is only applicable if installing M3 Business Engine database on this server.
If you have selected to attach the middleware on an external host, then this field will be disabled.
Default table directory

Specify a folder for the tables.
For example Y:\SQLData
Default index directory

Specify a folder for the indexes.
For example Z:\SQLIndexes
Note: For more information about logs, tables, and indexes, see M3 Business Engine and Microsoft SQL
Server - Best Practices on KB 2212202.
5 Click Next.
6 On the Summary screen, verify the property values, and click Finish to start the task.
7 Click OK.
To view the log file, either click View log or go to the Logs view.
Note: To change the default folders for the database files for a M3 BE environment before you install the
environment: Right-click the SQL Server instance and select Change default root directory for database
files.
Setting up a space
The ION Grid installation must be installed into a LifeCycle Manager space.
Verify that an appropriate space is displayed in the Applications tab of the LifeCycle Manager.
The LifeCycle Manager installation has three pre-defined spaces:
• Production
• Test
• Development
These spaces correspond to a default set of environments in a M3 Core installation. If your M3 Core installation
requires additional environments, you must create a corresponding space in the LifeCycle Manager Client
before you create the new environment.
To create a new space, go to the Applications tab in LifeCycle Manager Client and click the Manage Spaces
icon. Note that the space abbreviation name is used in both the Infor ION Grid and the M3 Business Engine
environment installation.
For more information, see Managing spaces in the LifeCycle Manager Administration Guide.

Uploading M3 Core to LifeCycle Manager
Chapter 3: Uploading M3 Core to LifeCycle Manager
All installation files for M3 Core must be downloaded before installation can start.
Downloading and updating LifeCycle Manager Server with

product package
You must update the LifeCycle Manager Server with product packages to enable remote installations and
management of your servers. A product package can contain LifeCycle Manager Client updates, installation
scripts, and components to install.
Note: This action should be performed each time a new product package to be installed is received.
Applying update
1 Download the installation files for M3 Business Engine, M3 Financial Business Messages, Infor ION Grid,
Session Providers, and M3 Core Technology from the Infor Download Center.
We recommend that you store all the downloads on the M3 Home Server where LifeCycle Manager Server
is installed.
2 Log on to LifeCycle Manager with a user that is a member of the LifeCycle Manager administrator's group.
3 In LifeCycle Manager Client, click Admin > Upload Products.
4 On the Manage Products page, click Upload and select these packages to upload:
• Grid_Installer_11.1.13.x.x.lcm
• Session_Providers_11.1.13.x.lcm
• SAML Session Provider 1.14.x.zip
• M3Core_Technology_13.x.x.lcm
• M3BusinessEngine_x.x.zip
• help_m3beud_E361_15.1.x.x.zip
Replace x.x with the available version to be installed.
5 Click Open.
6 In the Verifying package window, click Yes to accept to register the packages on the LifeCycle Manager
Server.

Uploading M3 Core to LifeCycle Manager
7 Click OK.
8 When the dialog appears asking you if you want to update your client, click Yes.
9 When the update is done, a dialog that shows the need to restart the client is displayed. Click OK.
10 Log on again.
Retrieving fixes
Use this procedure to retrieve and install available fixes handled by LifeCycle Manager from a Customer
Correction Self Service (CCSS) channel.
For more information about the types of fixes, see Types of fixes in the LifeCycle Manager User Guide available
in the LCM Client (Help > Help Contents) and in the M3 Core Infrastructure and Technology online
documentation available at docs.infor.com.
You may need to set up access to the CCSS server before you can retrieve fixes.
For example, if your organization uses a proxy server to access the internet, you must first set up LifeCycle
Manager to recognize the proxy. Review the guidelines and procedures in Managing access to the CCSS server
in the LifeCycle Manager User Guide.
1 Log on to LifeCycle Manager.
2 Select Actions > Retrieve Fixes. The Retrieve Fixes tab is displayed.
3 Click Retrieve and apply all available fixes.
4 Click Yes to confirm.
5 Specify a valid user name and password. Use your Infor Support Portal credentials.
6 Click OK.
7 A notification will be displayed informing that the LCM Client needs to be updated. Select to update and
restart the LCM Client.

Verify M3 Documentation URLs
Chapter 4: Verify M3 Documentation URLs
M3 BE User Documentation is delivered in infocenters.
Verify the M3 BE User Documentation Infocenter

The https URL for the M3 BE User Documentation is needed when installing the M3 UI Adapter. You can obtain
the URL after you have uploaded the Infocenter to LifeCycle Manager, see Upload M3 Core to LifeCycle Manager.
1 The URL to the Infocenter must be in https. Ensure that the Infocenter has a valid SSL certificate, or that
the certificate is added properly to the Trusted Root Certification Authorities of the browser.
2 After you have obtained and installed the SSL certificate, in the address line of a web browser, specify
the URL to the LifeCycle Manager Portal Documentation page.
http://LifeCycle_Manager_Server_IP_address:Port#/documentation
where Port# is the number you specified for the LifeCycle Manager Server port, plus 3 (with SSL) or plus
2 (without SSL).
• If you do not know the value, look in the LCMInstallDir\Server\lcm.properties file for the value of
http.server.port.
3 On the Documentation page, click the link to launch the M3 BE User Documentation infocenter.
4 Save the URL.
5 Provide the URL to the Infocenter when prompted during the installation of M3 UI Adapter, or when
configuring the Infocenter in Smart Office.
Obtaining an SSL certificate

Running Infocenter inside an application (for example, Infor Ming.le®or M3 H5) that runs in HTTPS also requires
the Infocenter to run in HTTPS. To run Infocenter properly in HTTPS, you must obtain a digital certificate,
which is an electronic document used to verify server identification and to encrypt communication between
server and client. There are three ways to obtain a certificate:
1 Purchase one from a Certification Authority (CA)
2 Generate one from the internal certificate server (comes with Windows Server)

3 Create a self-signed certificate.

Note:
Observe the following guidelines when you determine how to implement security certificates at your
site.
• When you order an SSL certificate, always specify the server name as a fully qualified domain name,
for example, server.corp.com. All automated configuration and tooling in your application will assume
that your certificate contains the fully qualified server name.
• An SSL certificate is created for a specific URL and HTTP server. It can not be reused on any other
server.
The table below illustrates the advantages and disadvantages of each mode of acquiring a certificate:
Mode of acquisition Advantages Disadvantages

Issued by a third-party Applicable to clients from any Additional expense; delivery time gap.
vendor domain.
Issued by an in-house Inexpensive; automatically Configuration and maintenance of certifi-
certificate authority. applies to all clients in the in- cation server is needed; applies only to
ternal network. domain clients.
Self-signed certificate Inexpensive and easy to use, Not recommended because it is not as se-
especially for test environ- cure as certificates issued by a root certifi-
ments. cate. The certificate must also be installed
on every client machine in advance in order
for Infor Smart Office to start.
Installing a Self-Signed SSL Certificate

The following step-by-step instructions describe how to install a self-signed SSL certificate manually on a
client machine. It is however also possible to push out certificates using Active Directory. For more information,
see the Active Directory documentation.
Note: These instructions only work with self-signed SSL certificates. They will not work with SSL certificates
created by a certificate authority.
It is not recommended to install self-signed SSL certificates in a production environment. In a production
environment, an SSL certificate issued by an in-house certificate authority or issued by a third party vendor
should be used.
To install a self signed certification, follow these steps:
1 Open your web browser as an administrator.
2 In your browser, specify the URL over https, for example https:// server.company.com:19006. Press Enter.
Note: It is important to type the first part of the URL exactly the same way as specified in the SSL certificate,
for example server.company.com
3 The Certificate Error page is displayed. Click Continue to this website (not recommended).
4 Click Certificate Error in the address bar and then click View Certificate.

5 The Certificate dialog box is displayed. Click Install Certificate.

6 The Certificate Import Wizard is displayed. Click Next.
7 Select the Place all certificates in the following store and click Browse.
8 The Select Certificate Store dialog box is displayed. Select the Trusted Root Certification Authorities
and check the Show Physical Stores and select Local Computer under Trusted Root Certification
Authorities (if this is not done the certificate will only be installed for the user currently logged on).
In the Select Certificate Store dialog box, press OK.
9 Click Finish.
10 In the Security Warning dialog box, click Yes to import the certificate.
11 Close the existing web browser and open a new one to specify the URL over HTTPS.

Install Infor ION Grid and M3 Core
Chapter 5: Install Infor ION Grid and M3 Core
Install ION Grid
Installing Infor ION Grid

Use this procedure to install the Infor ION Grid for the first time.
1 In LifeCycle Manager, select Actions > Install Product.
2 Select the product Infor ION Grid version from the list.
Click Next.
3 Select a space for the installation and click Next.
4 On the Install window, specify this information:
Grid Name
Specify a name for the grid.
Description
Specify a description for the grid.
LCM Admin Group

Select the LifeCycle Manager administrator's group from the list of administrator groups.
Database server
Specify the hostname for the database.
Create new database

Select this option to create a new database on the selected database server (see Create database below)
Note: This option is not available for Oracle.
Create schema in existing database

Select this option if you wish to create a schema in a database previously created through Lifecycle
Manager (see Create schema in existing database below)
Manual configuration of existing database

Select this option to specify the location of an existing database manually (see Use existing database
below)

5 On the Create database windows, specify this information:

Database
The name of the database to create
Schema
The name of the database schema to create (optional)
Database administrator user

The user with privileges to create the database
Database administrator password

The password for the administrator user
New database user

The user that will be created to run the grid database
New database password

The password you want to set for the grid database user
- or -
6 On the Create schema in existing database window, specify this information:
Existing database
The database, previously created through Lifecycle Manager, that the new schema should reside in
Schema
The name of the database schema to create

The user with privileges to create the schema

The password for the administrator user
JDBC user
Existing user that will run the grid database
JDBC password
The JDBC user's password
- or -
7 On the Use existing database window, specify this information:
Existing database
The name of the database instance
Schema
The name of the database schema, if used

JDBC user
The JDBC user name
JDBC password
The JDBC user's password
JDBC URL
Enter the URL to connect to the database.
Examples:
• SQL Server – jdbc:sqlserver:// host_fqdn:port; databaseName= yourDBname,instance= instanceName
Oracle – jdbc:oracle:thin:@// host_fqdn:port/ service
DB2 on IBM i - jdbc:as400:// host_fqdn/ relationalDatabaseName;errors=full;prompt=false For
example: jdbc:as400://abc008.
8 On the Initial Host window, specify the values for these fields and click Next:
Host
Select the initial host in your grid. This is the name the grid will use to identify this host.
Host Description
Type a description for this host.
Internal Address
Select the IP address of the host. This address will be used by the grid to connect this host to the rest of
the grid.
External Address
Select the FQDN of the host.
JDK
Initial installation of a host on the Windows platform require two JVMs to be installed; One 32 bit and
one 64 bit. The other platforms only require a 64 bit JVM.
Select the JDK to be used to run this grid. Java 8 is required when SAML Session Provider 1.14.x is used.
When installing the Grid Host on the M3 Business Engine Application Server, this Grid Host must be
installed with a 32-bit JVM.
9 On the Assign Ports window, specify or accept values for the following and click Next:
Assign ports manually
Select this check box if you want to enter the port numbers manually rather than going with the
pre-assigned values. You will not be able to edit the other port fields unless you select this check box.
Starting Port
Select the base for a range of ports to be used by the grid.

Internal Ports section:
Address
This read-only field shows the internal IP address for the grid.
Grid Agent Port

Accept the default port number or enter another port number for the grid agent. This is the port the grid
uses for configuration purposes. It must be accessible from the LifeCycle Manager server.
Registry Port
Accept the default port number or type another port number for the registry. It needs to be accessible
from all hosts in the grid.
Administrative Router Ports section:
Address
This read-only field shows the FQDN for the grid host.
Router Port
Accept the default port number or enter another port number for the administrative router. The
administrative router is the default way to access the grid from the outside, and so this port must be
accessible from outside the grid.
HTTPS Port
The HTTPS port to use for the administrative router.
Web Start Port

Type a port number to be used in order to use the Java web start entry point to the Grid Administrative
Pages from outside LifeCycle Manager.
Default Router Ports section:
Address
This read-only field shows the external IP address for the grid. It is the default router address, which is
the main entry point for external clients. It is used for external HTTP/HTTPS traffic, and the default SSL
certificate for this host is based on this.
HTTP Port
The HTTP port to use.
HTTPS Port
The HTTPS port to use.
Add default router to all hosts

Select this check box if you want to add a default router to all hosts the grid is on.
If you chose to select the ports manually, a check will verify that the ports are available and you will be
notified if a port conflict is detected.
10 On the Summary window, verify the properties provided.

Click Finish.
Verifying the Grid

After installation, the grid is automatically started. Perform the steps below in order to verify the installation
of the grid.
1 In LifeCycle Manager, locate the grid on the Applications tab of the left pane and double-click it.
2 In the Tasks tab of the right pane, click Grid Management Pages.
If the Infor ION Grid Management pages are shown, the grid is properly started and running.
Configuring host SSL certificate

As a prerequisite before installing the SAML Session Provider, configure the SSL certificate for the host where
the SAML router will be installed.
Consider trust for the CA (certificate authority) signing this SSL certificate: client browsers targeting grid
applications and authenticating with SAML need to trust the CA. Furthermore, the AD FS host needs to trust
it to retrieve metadata for the SAML Session Provider.
In order to enable trust from clients efficiently, it is recommended to use SSL certificates that are either
created by an internal company CA, or purchased from a public CA.
To create a certificate signing request to be signed by an external CA, refer to section "Creating Certificate
Signing Requests and Importing Certificates" in the Infor ION Grid Security Administration Guide.
Preparing users
To provide a seamless user handling, IFS, AD FS and SAML Session Provider must be configured consistently.
See "Users in M3" in M3 Core Installation Planning Guide.
When ION is installed, the user property IFS Person ID is added to IFS. This property must be populated with
a unique value for each user, corresponding to the M3 user.
Important: A user that has the Person property set to MVXSECOFR must be configured and able to log on, in
order to configure M3 BE.
On a high level, these steps must be completed for users to get the correct names for accessing M3 BE. Detailed
instructions for each step are found in subsequent chapters.
Preparing users

1 The property IFS Person ID must be configured in IFS for each user. This value must correspond to the
field User in 'User.Open' (MNS150) in M3 BE, and can have a maximum length of 10 characters. See User
management in Infor Ming.le on page 34.
2 Configure AD FS to forward Person as a claim as described in Install the SAML Session Provider using
LifeCycle Manager on page 36.
3 Configure the SAML Session Provider to use Person claim: http://schemas.infor.com/claims/Person as
identity, as described in Install the SAML Session Provider using LifeCycle Manager on page 36.
User management in Infor Ming.le

IFS is accessed via "User Management" in Infor Ming.le®. This option is available to users with sufficient
privileges.
All users that should access M3 need to be set up in IFS. Use one of these methods:
• Import a CSV or XML file.
• Synchronize users from the AD.
• Configure each user manually.
To add users manually or to import users, see section "Manage Users" in the Infor Operating Service
Administration Guide. For importing users, also consider Importing M3 users in Infor Ming.le 12 on page 35.
To configure synchronization of users from the AD, see section "AD Parameters" in the Infor Operating Service
Administration Guide.
When considering how to add users, you must take into account how to set up the IFS Person ID. The IFS
Person ID property must be set for each user that should access M3. This can be done in three different ways:
• Manually during user import, as described in Importing M3 users in Infor Ming.le 12 on page 35
• Manually as described in Manual configuration of the property IFS Person ID on page 35
• Automatically as described in Automatic configuration of the property IFS Person ID on page 35
Note: The IFS Person ID property must be set with a unique value for each user. There is no functionality in
IFS that guarantees uniqueness. This must be validated before setting the property values.
Enable editing of the property IFS Person ID

1 Access Infor Ming.le as a user with the IFSApplicationAdmin role.
2 Click the user icon, and select User Management.
3 Click Security Administration> IFS Person ID.
4 Select No Automatic Setting. Click the save icon to save the configuration.

Importing M3 users in Infor Ming.le 12

In Infor Ming.le 12, you can import user definitions in CSV or XML files. For M3, the IFS Person ID property value
must correspond to the M3 user name.
Note: Before importing users, ensure that the IFS Person ID configuration in Infor Ming.le is set to No Automatic
Setting. Otherwise, the configured IFS Person ID values are overwritten with the UPN values when synchronizing
from the AD. For instructions, see Enable editing of the property IFS Person ID.
Note: Optionally, you can create a template file that provides support for the specified format. To create a
template file for import:
1 Export the IFS bootstrap user in the desired format.
2 Edit the result file with values for your real users.
Use this procedure to import M3 users:
1 Prepare the user information in the required format, for example in CSV or XML, based on the exported
information from the AD.
2 Specify the PersonId field with the unique M3 user value for each user.
3 Import the file.
For details on this procedure, see Importing Users in the Infor Operating Services Administration Guide.
Manual configuration of the property IFS Person ID

Note: Before configuring the property IFS person ID, ensure that the IFS Person ID configuration in Infor
Ming.le is set to "No Automatic Setting". Otherwise, the configured IFS Person ID values are overwritten with
the UPN values when synchronizing from the AD. For instructions, see "Enable editing of the property IFS
Person ID".
Use this procedure to specify the IFS Person ID:
1 Access Infor Ming.le as a user with the UserAdmin or IFSApplicationAdmin role.
2 Click the user icon, and select User Management.
3 Click Manage, and then Users.
4 Select the user to configure. Click the arrow icon next to that user in order to configure values.
5 Click Additional Properties.
6 On the IFS Person ID row, specify the M3 user value for that user.
7 Click the save icon to save the configuration.
Automatic configuration of the property IFS Person ID

In some environments, there may already be an AD attribute that meets the criteria for the M3 user name –
unique values for all users and at most 10 characters long. If this is the case, this attribute can be used to
populate the property IFS Person ID when automatically syncing users from the AD.
1 Optional: Override the AD attribute for MVXSECOFR.

If there is an AD attribute that is suitable for the IFS Person ID values, but needs to be overridden with
the value MVXSECOFR for a user, that is possible. If this scenario applies, you must configure this user
before configuring the custom AD attribute and synchronizing the other users.
a Enable editing of the IFS Person ID field.
b Add the user manually as described in Manual configuration of the property IFS Person ID on page
35.
2 Map the property IFS Person ID to a custom AD attribute
a Access Infor Ming.le as a user with the IFSApplicationAdmin role.
b Click the user icon, and select User Management.
c Click Security Administration> IFS Person ID.
d Click No Automatic Setting to enable configuration of the AD attribute to use.
e In External Name, select the AD attribute to use for the M3 user name.
f Click the save icon to save the configuration.
Note:
The configuration will only take effect for users that are added after this procedure.
3 Synchronize the rest of the users from the AD.

To synchronize users from the AD automatically, see section AD Parameters in the Infor Operating Service
Administration Guide.
SAML Session Provider

The SAML Session Provider is the preferred session provider for M3 Core. See M3 Core Installation Planning
Guide for an overview of the SAML protocol in an M3 context.
Installing and configuring the SAML Session Provider

Use this procedure to install the SAML Session Provider. The SAML Session Provider can be deployed to
multiple hosts and started in multiple nodes.
The only recommended Session Provider for the M3 Core installation is the SAML Session Provider 1.14. For
information about alternative session providers, refer to ION Grid Security Administration Guide available in
the M3 Core I&T documentation on docs.infor.com.
Install the SAML Session Provider using LifeCycle Manager

The SAML Session Provider is installed in grid using LifeCycle Manager. This procedure describes the required
configuration for an M3 installation.

Note: Before you start the installation, retrieve the latest version of the SAML Session Provider 1.14 from
CCSS. The JDK on the hosts where SAML Session Provider should run must be Java 8 for integration with Infor
OS to work properly.
Installing the SAML Session Provider using LifeCycle Manager

2 From the list, select the product Infor SAML Session Provider <version>. Click Next.
3 On the Host selection window, select the grid host you want to deploy the SAML Session Provider to.
Select ADFS as the installation profile, and click Next.
4 If a SAML router already exists, you will be asked if you want to reuse that router. If no SAML router exists,
on the Router properties window, define the properties for the router to be used by the session provider
and for any additional endpoint addresses and click Next:
External Router Address
The external address for the router.
Router IP Address
The external IP address of the router.
Router HTTPS port

The HTTPS port for the router.
Restrict SYSTEM access

Select this check box to publish all applications except the Grid Management Pages via the SAML Router.
Select this option if management of the grid is authenticated with a client certificate.
Additional ACS endpoints

If load balancers or proxies are placed in front of the Grid, the SAML Session Provider needs to publish
endpoints for those addresses, as described in Configuring Login and Logout Endpoints on page 40.
Write one entry per row in the format fqdn:port. The first entry will be configured as the Logout Endpoint,
and will be used to form the Entity ID for the SAML Session Provider (to be used in IFS and AD FS). If
nothing is added here, all login and logout endpoints are based on the SAML router properties defined
above.
Exclude Router ACS

Select this check box to create Assertion Consumer Services for the Additional ACS endpoints only. No
ACS value will be created based on the SAML Router properties. Select this option if all SAML
authentication should pass via the load balancer - that is, no direct access to grid routers by end users.
5 On the Session Provider Properties window, specify the information and click Next:
IdP FQDN
The fully qualified domain name of the AD FS server.
IdP https port

The SSL port of the AD FS endpoint.

Metadata URI
Provide the URI to the federation metadata. The default AD FS value is /FederationMetadata/2007-06/
FederationMetadata.xml. The URI can found in the AD FS management console:expand
"Service">"Endpoints". In the Metadata section, find the URL Path for the FederationMetadata.
The Secondary Identity Provider properties are only applicable in cloud scenarios.
After you click Next, the installer will get the SSL certificates from the AD FS server and you will have to
confirm them before continuing. The installer will retrieve the AD FS metadata and parse it for suggested
values for a later installation step.
6 On the IFS Properties window, specify the information and click Next:
IFS FQDN
Specify the FQDN for IFS.
IFS HTTPS port

Specify the HTTPS port for reaching IFS.
IFS admin user

Provide the name for a domain user that has the IFSApplicationAdmin and AttributeServiceCaller IFS
Security Roles. The username must be in the domain\uid format. This should be a service user with a
password that does not expire; otherwise, the password must be kept up-to-date. This user is used for
authenticating IFS web service calls, both during installation and at runtime.
IFS admin password

Provide the password for the domain user from the previous field.
OAuth 1.0a Consumer Key

If OAuth 1.0a is used to authenticate to IFS, specify the consumer key. If both Oauth credentials and IFS
admin credentials are provided, the OAuth credentials will be used.
OAuth 1.0a Secret Key

If OAuth 1.0a is used to authenticate to IFS, specify the secret key.
Farm name
The name of the farm for the used InforOS installation.
Platform ID
The platform ID of the farm for the used InforOS installation.
Purpose
A very short (4-10 characters) description of the purpose of the setup. This will be part of the application
name in IFS and the Relaying Party Trust in AD FS for easier identification.
After you click Next, the connection to IFS web services is validated and the credentials tested.
7 In the SAML Properties window, configure Identity Claim name, and click Next.
Identity Claim name
Change the value to http://schemas.infor.com/claims/Person
8 Review the values on the Summary window and click Finish to start the installation.

9 The application must now be activated manually in the Infor OS Manager. To do this, follow these steps.
For more information, see Completing claims-based authentication configuration in Infor Operating
Service Installation Guide.
a Open Infor OS Manager for the correct farm.
b Select Applications.
c Identify the application corresponding to your SAML Session Provider installation, in the format
Grid-<Purpose> where <Purpose> is the value provided for the Purpose field in the IFS properties
window.
d Click the download link for this application to save a powershell script.
e Run the script on the AD FS server.
See AD FS server configuration in Infor Operating Service Installation Guide.
10 Continue with the procedure Adding Assertion Consumer Service endpoint to AD FS on page 39.
Adding Assertion Consumer Service endpoint to AD FS

1 To retrieve the metadata for the SAML Session Provider, the AD FS server must trust the SSL certificate
used by the SAML Router. The root certificate used to sign this SSL certificate must be present in the
Trusted Root Certificates store on the AD FS server.
If an external CA has been used to sign the grid SSL certificate, it may already be present in the Trusted
Root Certificates store. See Configuring host SSL certificate on page 33.
2 Find the federation metadata URL for the SAML Session Provider:
a From the Grid Management Pages, open the management pages of the SAMLSessionProvider
application.
b Click Metadata.
c Copy the federation metadata URL displayed on the page for use in step 7.
3 Log on to the AD FS server, and start the AD FS Management console.
4 Expand Trust Relationships in the left side menu and select Relying Party Trusts.
5 Select the application that corresponds to your SAML Session Provider installation, with the display name
on the format Infor_Grid-<gridPurpose>_<InforOSFarmName>_<InforOSID> and the Identifier on the format
urn:Infor_<InforOSFarmName>_<InforOSID>:Grid_<gridPurpose>.
6 Right-click and select Properties.
7 On the Monitoring tab, enter the federation metadata URL for your SAML Session Provider (see step 2c
for the value).
8 Click Test URL to ensure that the address is reachable and trusted by AD FS. If you get an error message,
see the Microsoft Windows Server documentation on troubleshooting trust management problems with
AD FS.
9 When you get a message saying that the URL was validated successfully, click OK and then OK again.
10 Select again the application that corresponds to your SAML Session Provider installation.
11 Right-click and select Update from Federation Metadata.
12 On the Endpoints tab, verify the SAML Assertion Consumer Endpoints, and then select Update.

Verify the SAML configuration

After finishing the configuration of the SAML Session Provider, validate the configuration by signing in to the
grid.
1 In a browser, access the endpoint https://<SAML Router FQDN>:<SAML Router https port>/saml/authen
ticate. If a load balancer or proxy server is used, use the FQDN and port from the proxy server address
instead.
2 When redirected to AD FS, provide the credentials for a user that has been configured in Infor Ming.le.
3 Verify that the UserID is set to the expected value based on the IFS Person ID.
4 Repeat the test for a router that has basic authentication enabled, for example the Default Router. This
will mimic SAML authentication for active clients.
Configuring Login and Logout Endpoints

To authenticate a given user, the SAML Session Provider creates an authentication request which is provided
to the identity provider (IdP). The response (assertion) is returned to one of a set of pre-configured login
endpoints also known as assertion consumer service locations. These are endpoints where the SAML Session
Provider receives and handles assertions from the IdP.
Note: When a web application in the grid requires a session, this session is set as a cookie on the HTTP
response. The assertion from the IdP must be returned to the same host address as the one used in the original
request from the client. Otherwise, the session will be set on the wrong context, and the client will not be
able to access the desired resources. Both the SAML Session Provider and the IdP must be configured to use
the correct assertion consumer services.
If you access secured web applications in the grid via a proxy server or load balancer, you must add assertion
consumer services representing the proxy host.
The SAML protocol also supports single logout among all configured SAML service providers. In order for
SAML Session Provider to participate in the logout process, it must have a logout endpoint configured and
the identity provider which initiates the logout requests must know about the endpoint.
Initial Configuration
By default, the installation will set up one or two assertion consumer service endpoints in the configuration:
one for the FQDN of the SAML router for the HTTP-POST binding and optionally one for the IP address of the
SAML router if an IP address was provided during installation. Unfortunately, only one of these can be
automatically set up in the IdP. The installation must therefore be completed with a manual step, as described
in the installation procedure for the SAML Session Provider. See Adding Assertion Consumer Service endpoint
to AD FS on page 39.

Updating Assertion Consumer Services

This section describes how to add more assertion consumer services to the configuration of the SAML Session
Provider and the IdP. This is needed if you access secured web applications running in the grid via a host and
port other than those already specified as assertion consumer service endpoints, for example, via a router
different from the SAML router, or if you have a proxy in front of the grid.
This procedure assumes that the initial configuration of assertion consumer service endpoints has already
been performed.
1 Add an assertion consumer service endpoint to the SAML Session Provider:
a From the Grid Management Pages, open the Management Pages of the SAMLSessionProvider
application.
b Select Login and Logout endpoints.
c Type the desired host address and port, and then click on Create Endpoints.
d Click on the disk button to save your changes.
2 Add the assertion consumer service endpoint to the AD FS configuration. See section Updating Login
and Logout Endpoints in AD FS.
Updating Login and Logout Endpoints in AD FS

After adding new assertion consumer endpoints or logout endpoints, the AD FS configuration must be updated
to match.
To update Login and Logout Endpoints in AD FS:
1 Log on to the AD FS server, and start the AD FS management console.
2 In the left side menu, expand Trust Relationships and select Relying Party Trusts.
3 Select the application that corresponds to your SAML Session Provider installation, on the format urn:
<SAML router FQDN>_<SAML router https port>. Right-click and select "Update from Federation Metadata."
4 On the Endpoints tab, verify the SAML Assertion Consumer Endpoints. Then select Update.
Grid Database Connectivity (GDBC)
Installing the Grid Database Connectivity (GDBC)

Use this procedure to install the Grid Database Connectivity in a grid.
2 From the list, select the product GDBC <version>.
Click Next.

3 On the Install window, select the location for the Grid Database Connectivity:
Name
Select the grid on which the grid extension should be installed.
Click Next.
4 On the Install Grid Database Connectivity window, enter values for the following:
Host
The host for the grid extension.
H2 port
The port for the H2 database used by GDBC.
Click Next.
5 On the Summary window, verify the properties provided.
Click Finish.
Managing Database Drivers for GDBC

It is possible to select H2 or SQL Server for GDBC.
Note: For M3 Core, any production environment must use SQL Server.
Add a database driver for the Grid Database Connectivity (GDBC)

The Grid Database Connectivity supports the uploading of new database drivers (type 4 JDBC only). If you
have type 4 JDBC drivers you want to use, you can upload them to the GDBC broker.
1 Access the management pages for the Grid Database Connectivity. You can access these pages via the
grid's Grid Management Pages, which can be accessed through the LifeCycle Manager, Java Web Start,
or HTML. For more information, see the Infor ION Grid Administration Guide.
2 In the Grid Management Pages, click the Management Pages link for the Grid Database Connectivity.
3 On the Grid DB Broker page, click Manage Drivers.
4 On the Drivers page, click Add New.
5 Enter a driver name and click Create.
6 On the Driver Details page, click Add file(s).
7 Enter the path and name of the drivers files, or click Browse to navigate to each driver file.
8 Click Add when you have entered or selected all driver files you want to add.

Change the GDBC database driver for an application

Note: This procedure must be carried out for each application that should be using GDBC.
1 Access the management pages for the Grid Database Connectivity grid extension. You can access these
pages through the grid's Grid Management Pages, which can be accessed through the LifeCycle Manager,
Java Web Start, or HTML. For more information, see the Infor ION Grid Administration Guide.
2 In the Grid Management Pages, click the GDBC application link at the bottom of the page.
3 On the Application GDBC page, click Configuration.
4 On the Application: GDBC (GDBC) page, click Edit Properties.
5 Edit the broker.connectionUrl property:
a Click on the Value link for the broker.connectionUrl property and click Add New Entry.
b Enter the Grid application name into the Application column, for example, EventHub, CLM or
MangoServer (Smart Office server).
c Enter the JDBC driver URL connection string into the Value column.
For example, for a JTDS driver connecting to SQL server, you would use the construct:
jdbc:jtds:sqlserver://hostname:port/database_name
d Select the Merge radio button.

e Click Save.
6 Edit the broker.driverClassName property.
a Click on the Value link for the broker.driverClassName property and click Add New Entry.
c Enter the driver class name into the Value column.
For example, for a JTDS driver, you would use:
net.sourceforge.jtds.jdbc.Driver

e Click Save.
7 Edit the broker.userName property.
a Click on the Value link for the broker.userName property and click Add New Entry.
c Enter the database user name that should be used for the connection.
e Click Save.
8 Edit the broker.password property.
a Click on the Value link for the broker.password property and click Add New Entry.
c Enter the database user's password that should be used for the connection.
e Click Save.
9 Edit the broker.driverDirName property.

a Click on the Value link for the broker.driverDirName property and click Add New Entry.
c Enter the driver directory name. This is the Driver Name and can be retrieved from the Drivers page
in the GDBC management pages.
e Click Save.
10 When you have entered values for the properties, click Save at the top of the Application Properties page
and then click Save again on the confirmation dialog box.
11 Restart the application to put the changes into effect.
Viewing Grid Database Connectivity Application (GDBC)

Configuration Information
Use this procedure to view information on the applications using GDBC to make a database connection. The
information available includes:
• Application - name of the application using the driver
• Driver - GDBC driver in use for that connection
• Driver Class - class file used to implement the JDBC connection
• User - database connection user name
• URL - database connection URL
• Version - database version
• H2 Web Console - direct link to the web console for embedded H2 database connections only
1 Access the management pages for the Grid Database Connectivity grid extension. You can access these
pages via the grid's Grid Management Pages, which can be accessed through the LifeCycle Manager, Java
Web Start, or HTML. See the Infor ION Grid Administration Guide available in the M3 Core I&T documentation
on docs.infor.com.
2 In the Grid Management Pages, click the Management Pages link for the Grid Database Connectivity grid
extension.
3 On the Grid DB Broker page, click View application configuration.

Event Hub and Event Analytics
Installing Event Hub

Note: The Grid Database Connectivity Grid Extension (GDBC) must be configured on the Grid which the
application Event Hub uses. GDBC is mandatory which means Event Hub is dependent on GDBC for backend
storage. See Installing the Grid Database Connectivity (GDBC) topic for the configuration of GDBC.
Use this procedure to install Event Hub.
2 On the Install step, select Event Hub <version>, then click Next.
3 On the Location step, select the Grid instance where to install Event Hub, then click Next.
4 On the Select Host step, specify this information:
Deploy hosts
Select the host(s) where to install Event Hub. Each host selected will run one Event Hub node.
Recorder host
Select a host where to start the event recorder.
The event recorder is started on demand when a recoding session is created.
5 On the Select posts step, specify this information:

Port
Accept the default or specify a unique port.
SSL Port
Accept the default or specify a unique port.
6 On the Summary step, review the information and click Finish.
Installing Event Analytics

Use this procedure to install Event Analytics.
Install Event Analytics

2 On the Install step, select Event Analytics <version>, then click Next.
3 On the Location step, select the Grid instance where to install Event Analytics, then click Next.
4 On the Install Event Analytics step, specify this information:

Host
Select the host where to install Event Analytics.
Analytics Persistence Folder

Browse to an absolute path on the file system, or specify a relative path (relative to the grid application
root directory).
Note that in this directory the application stores rules and analytics data that may occupy several
gigabytes of disk space.
5 On the Summary step, review the information and click Finish.
Install M3 UI Adapter
Ensure that your Infor ION Grid is started.
Installing M3 UI Adapter
Use this procedure to install M3 UI Adapter. To use the installation wizards, the user must be a member of
the LifeCycle Manager administrator group.
Note: See Installation considerations for M3 UI Adapter in M3 Core Administration Guide. There is no upgrade
path from the previous 10.2.x versions of M3 UI Adapter to versions 10.3.x. The only possible upgrade is from
version 10.3.0.0 to version 10.3.1.0.
1 In LifeCycle Manager, locate the Grid instance where you want to install M3 UI Adapter.
2 Right-click the Grid instance > Install Product.
3 On the Install window, select M3 UI Adapter <version> and click Next.
4 Specify a description for the M3 UI Adapter installation and click Next.
5 Select the host(s) where M3 UI Adapter will be installed and click Next.
Database server
Select MS SQL.
Create database/Attach database

Select Create database if you are installing M3 UI Adapter for the first time. User should select this option
if they want to start with a new database. This option also creates a new user to access the database,
and requires a database administrator and password.
Select Attach database if you are reinstalling M3 UI Adapter or if you have an existing database. This
option only requires a database user and password to allow M3 UI Adapter to connect.
7 Click Next.

Database Location
Select the location where the MUA database files will be created.
Note:
This field is disabled when Attach database is selected.
Database Admin Logon

Specify username and password of database administrator.
These fields are disabled when Attach database is selected.
Database User Logon

Specify username and password of database user.
9 Click Next.
M3 BE User Documentation URL
Specify the URL of the M3 Business Engine User Documentation Infocenter.
Note: The URL to the Infocenter must be in https. Make sure that the Infocenter has a valid SSL certificate,
or that the certificate is added properly to the Trusted Root Certification Authorities of the browser.
See Verify the M3 BE User Documentation Infocenter on page 26.
Logical ID/Base URL

Specify the entire URL to, and including, the search jsp.
If Document Management is accessed from Ming.le, an example of the URL would be lid://infor.daf.1
If using standalone Document Management, however, the URL must point to the standalone installation.
The URL in this case must have this format: https://hostname:port/ca/client/index. html?$query=
Entities URL
Specify the entire URL.
This URL is used to retrieve the list of IDM entities and must have this format
https://hostname:port/ca/api/datamodel/entities.
For example, https://172.30.162.87:10080/ca/api/datamodel/entities
Note: H5 Mashups and SDK Applications need to use a proxy to connect to IDM. For more information
about the installation of IDM proxy, see instructions in the M3 Core Administration Guide.
11 Click Next.
12 On the Summary page, review information and click Finish. When a notification appears stating that
installation has finished successfully, click OK or click View log.
When the installation is completed, M3 UI Adapter appears in the list of Grid applications. The M3 UI
Adapter and the M3 BE environment installations will be automatically connected after they are installed
in the same Grid.
Refresh the client and verify that the application is already started.
Note: After the installation, you must configure the role first in order to log in to M3 UI Adapter. See
instructions in Setting M3 UI Adapter users in the M3 Core Administration Guide.

Attaching an M3 UI Adapter Database

1 Right-click the database server instance, and select Attach MUA Database.
2 Specify user and password for the database administrator. Click Next.
3 Select the MUA database to attach, and then click Next.
4 On the Summary screen, verify the property values, and click Finish.
5 When the task is finished, a dialog is displayed. Click OK. To view the log file, either click View log or go
to the Logs view.
Changing M3 UI Adapter Database connection

1 In LifeCycle Manager, locate and select the M3 UI Adapter <version> in Grid.
2 Right-click the M3 UI Adapater > Change Database.
3 The Change Database dialog is displayed. Click Next.
Database server
Select MS SQL.
Database
Select the required database, and then click Next.
5 Specify user and password for the database user. Click Next.
6 On the Summary page, review information and click Finish.
Install M3 H5
Ensure that your Infor ION Grid is started.
Installing M3 H5 Enterprise
Use this procedure to install M3 H5 Enterprise.
1 In LifeCycle Manager, locate the Grid instance where the latest version of M3 UI Adapter is installed.
2 Right-click the Grid instance > Install Product.
3 On the Install window, select M3 H5 Client Enterprise <version> and click Next.
4 Select the host(s) where M3 H5 will be installed and click Next.
5 On the Summary page, review information and click Finish. When a dialog box is displayed, click OK or
click View log.

After the installation is completed, M3 H5 appears in the list of Grid applications. Refresh the client and
verify if the application is already started.
Install M3 Business Engine

Note: To use the installation wizards, the user running LifeCycle Manager Client must be a member of the
LifeCycle Manager administrator’s group.
Installing M3 Business Engine release 15.1

1 In the LifeCycle Manager, select Actions > Install Product to start the installation wizard.
2 Select the product M3 Business Engine 15.1. Click Next.
3 Select the Location (the LifeCycle Manager Service) where you wish to install the M3 Business Engine.
Click Next.
4 Perform one of the following actions depending on if you want to install M3 Business Engine on a SMB
share or not:
• If you do not want to install M3 Business Engine on an SMB share, click Next, and continue to step
6.
• To install M3 Business Engine on an SMB share:
a Select the check box Install M3 BE on a SMB share.
b Enter the following values:
Remote Host:
Enter the hostname of the server, which must belong to the same domain as the server where
the LCM Service is installed.
Remote Host User

Enter the domain user name
Remote Host Password

Enter the password for the remote host user.
Click Next.
5 Select one of these options:
• Select Existing Share:
Share Name
Select an existing share.
• Create New Share:

Share Name
Specify a name for your share, for example: M3BEShare.
Installation Path
Specify a local path on the remote host for your M3 BE installation. For example: D:\M3BE.
Click Next.
6 Enter the values for the installation of M3 BE Release: M3BE_15.1:
Installation Path
Click Select ... and then choose the location where to install M3 Business Engine. Make sure that the
selected folder has appropriate permissions. See Securing M3 BE Installation Folder on page 110 for
details.
Note:
If you installed on a SMB share, the installation path is already defined, and the Select option is disabled.
Description
Enter a description for the installation.
Click Next.
7 Select the check box and specify your search criteria if you want to use a filter when searching for groups
in LDAP.
Click Next.
8 Select an Admin Group for the M3 Business Engine installation. If no Admin Group is selected, only users
that belong to the LifeCycle Manager administrators group (LCMAdmins) are allowed to administer the
M3 Business Engine installation. Click Next.
9 On the Summary screen, verify the property values, and click Finish to start the installation.
Note:
The installation of M3 Business Engine files may take several minutes to complete.
10 The Install M3 Business Engine task is displayed in the Progress view. When the installation is completed,
a dialog appears. Click OK. To view the log file, either click View log or go to the Logs view.
The M3 Business Engine installation M3BE_15.1 can now be found in the Hosts tab in the LifeCycle Manager
Client under the Host where you did the installation.
Note:
An M3 Business Engine installation can have one environment, or be shared by many M3 Business Engine
environments.
Attaching an M3 Business Engine Database

If you have an M3 Business Engine database that you want to attach to your environment, you must first
attach a database middleware to the node hosting the database. Then the task Attach M3 BE Database can

be run on this node. This method can be useful when upgrading from an older M3 Business Engine version,
or if you want to attach a backup of a database to your environment.
Attach database
1 Right-click your M3 Business Engine application middleware database instance node, and select Attach
M3 BE Database.
2 Enter user and password for the database administrator. Click Next.
3 Select an existing database to attach. Click Next.
5 When the task is finished a dialog appears. Click OK. To view the log file, either click View log or go to the
Logs view.
Installing an environment
1 In the LifeCycle Manager, navigate to your space, right-click your Grid and select Install Product to start
the installation wizard.
2 Select the product M3 BE 15.1 - Environment <10.x.x>, and click Next.
Note: Ensure to select the correct M3 Foundation version. This is reflected by the <10.x.x> version.
3 Select the M3 Business Engine installation to install the M3 BE environment in. An M3 Business Engine
installation can have one environment, or be shared by many M3 Business Engine environments. Click
Next.
4 If your Grid is set up to run on multiple hosts, the Additional Grid Hosts window is displayed.
Select the additional Grid Hosts to run M3 BE on.
Click Next.
5 Verify and specify the environment information:
Name
The environment name is the abbreviation set for your space.
Type
This is the type set for your space.
Description
Specify a description for your environment.
M3 Foundation
Select the latest M3 Foundation version available.
M3 Router
Accept the default base port number, or enter a unique base port for a range of ports to be used by the
environment.

Note: Firewalls and some Antivirus programs may block access to ports that M3 Business Engine requires
to successfully start up and run. The install environment wizard will create firewall inbound rules for the
M3 BE application server ports to allow client applications to connect to M3 BE.
For more information, see Security issues.
Click Next.
6 Select the check box and specify your search criteria if you want to use a filter when searching for groups
in LDAP.
Click Next.
7 Select an Admin Group for the M3 Business Engine environment installation.
The default value displayed here is the group used for the M3 Business Engine installation. If no Admin
Group is selected, only users that belong to the LifeCycle Manager administrators group (LCMAdmins)
are allowed to administer the M3 Business Engine environment installation.
Click Next.
8 Specify the values needed for the M3 Business Engine database.
Database server
Select the database server for M3 Business Engine.
Create database
Accept the default name or specify a new name for the M3 Business Engine database.
Note: Required length is 8 characters or less.
Attach database
Select an M3 Business Engine database if you want to attach an existing database to your environment.
Insert delivery data

Select Insert delivery data to install the delivery data included in the installation of M3 Business Engine.
Note: If you do not want to fill the database with data during the environment setup clear the Insert
delivery data check box. This copy must then be done manually by using the Import Data to Database
task in LifeCycle Manager.
For information about how to use these administration tools, see the M3 BE LifeCycle Manager User Guide
available in the M3 Core I&T documentation on docs.infor.com.
Click Next.
9 Enter the following MS SQL Server information:
User
Specify the database system administrator login sa
Password
Enter the database system administrator password
Transaction log
Accept the default path or specify a new path for the system logs.

Note: If using an SQL Server attached to an external host it is not possible to specify the path by using
the Select button. You must manually enter the path to the already existing folders in the edit field. For
example: X:\SQLLogs\M3FDB<Space abbreviation name>
Tables
Accept the default path or specify a new path for the tables.
example: X:\SQLTables\M3FDB<Space abbreviation name>
Indexes
Accept the default path or specify a new path for the indexes.
example: X:\SQLIndexes\M3FDB<Space abbreviation name>
Initial size
Specify the initial size of the database (large or small)
Table
Select the compression type for tables.
Note: If you have selected to attach a database then you should select the same compression type as
the database you attach is using.
Index
Select the compression type for indexes.
Note: If you have selected to attach a database then you should select the same compression type as
the database you attach is using.
Click Next.
Note: Support for compression is only available for SQL Server Enterprise Edition and SQL Server Developer
Edition.
Row level compression dramatically reduces the metadata needed for variable length columns. Page
level compression reduces the data size by sharing common data across rows. When Page level
compression occurs, there are three operations that happen in the following order: row compression,
prefix compression, and dictionary compression.
Data compression can improve query performance, but there are performance trade-offs for using row
and page compression. CPU utilization will go up, but I/O utilization and memory utilization will go down.
Data compression is a CPU intensive operation and if your environment is already facing CPU crunch
then this is not the best solution.
For more information about logs, tables, indexes and compression, see M3 Business Engine and Microsoft
SQL Server - Best Practices" (SQL Server BPG) on KB 2212202.
10 Enter database and license information.
M3 BE admin
MDBADM

M3 BE admin password
The user is created with the password supplied here. Retype the password.
If the user already exists, the valid password for this user must be entered.
Note: The password must contain a minimum of 8 characters. Also, it must be a combination of
alphanumeric and special characters.
M3 BE user
MDBUSR
M3 BE user password
The user is created with the password supplied here. Retype the password.
If the user already exists, the valid password for this user must be entered.
Note: The password must contain a minimum of 8 characters. Also, it must be a combination of
alphanumeric and special characters.
License key
Specify license key for M3 Business Engine.
Note: If you require a License Key, send an email to APAC.Keys@Infor.com, EMEA.Keys@Infor.com or
AMER.Keys@Infor.com with the following information:
• Requested Product and Version
• Client Name and Client ID #
• Client Contact Name and Email address
The default key is valid for ten users and has no limit date, but a new license key should be ordered as
soon as possible.
For information on how to set up the license key, see M3 Business Engine Foundation Administration
Guide available in the M3 Core Infrastructure and Technology online documentation on docs.infor.com.
License mail sender

Specify a sender address, for example License.<M3BE environment name>@infor.com
License mail receiver

Specify a mail address to the person responsible for the license key at your company.
SMTP mail server

Enter the IP address or Host name (FQDN) for the SMTP server
Note: To verify the settings, click Send test mail.
The database logins and users MDBADM and MDBUSR are created while running this wizard. For more
information, see M3 Business Engine and Microsoft SQL Server - Best Practices" (SQL Server BPG) on KB
2212202.
Click Next.
11 A page with information that the Grid Agent will be restarted when installing the environment is displayed.
Click Next.
12 On the Summary screen, verify the property values and click Finish.

13 The Install Environment task is displayed in the Progress view. When the step is completed, a message
box is displayed. Click OK. To view the log file, either click View log or go to the Logs view.
You can manage the new environment from LifeCycle Manager, either in the Applications view for the
Space used for your environment, or in the Hosts view under the Host where your M3 Business Engine
was installed.
Note: If the Grid is running on a private network, you need to add an external address to the M3Router
in Grid after installing the M3 BE Environment. Go to Grid Configuration Manager > Communications >
Routers > M3Router to enable the communication. For more information about managing external
addresses of routers, refer to the Infor ION Grid Security Administration Guide available in the M3 Core
Infrastructure and Technology online documentation on docs.infor.com.
The M3RemoteClassProvider enables reading and writing files that reside on the base M3 BE host only.
To increase performance for individual hosts, you can override the M3RemoteClassProvider and let the
M3 nodes access the filesystem directly, see M3 Core Administration Guide, chapter Overriding the use of
the M3 RemoteClassProvider node.
Note: The M3 BE database is set in recovery model simple during installation. Before a production
environment goes live, it is recommended to use recovery model full. For more information, see KB
2212202:
• M3 Business Engine and Microsoft SQL Server - Best Practices, version for M3 BE 15.1 and Microsoft
SQL Server 2016, topic # 51422, or
SQL Server 2014, topic # 44834, or
SQL Server 2012, topic #37304
Install M3 Business Engine layouts
Attaching middleware - OpenText StreamServe/Exstream

2 Select OpenText StreamServe/Exstream from the list. Click Next.
3 Select the location (the LifeCycle Manager Service) where the middleware is installed. Click Next.
Name
Specify the name of your OpenText StreamServe/Exstream server.
Description
Specify a description for your server.

Installation path
Select the path to where the layouts are to be installed.
Click Next.
6 When the task is finished, a dialog is displayed. Click OK. To view the log file, either click View log or go
to the Logs view.
Connect OpenText StreamServe/Exstream to M3 Business Engine

Environment
All the appropriate layouts and language files are uploaded to the LifeCycle Manager Server when M3 Business
Engine is installed and are now available to be added to the OpenText StreamServe/Exstream server.
To install the layouts and language files for the installation of M3 Business Engine on the OpenText
StreamServe/Exstream server, you need to connect the middleware OpenText StreamServe/Exstream to your
M3 Business Engine environment.
Connect to environment
1 Right-click your OpenText StreamServe/Exstream middleware, and select M3 BE Integration Tasks >
Connect OpenText StreamServe/Exstream to M3 BE Environment.
2 Select your M3 Business Engine environment in the list. Click Next.
4 When the task is finished a dialog is displayed. Click OK. To view the log file, either click View log or go
to the Logs view.
Overview
For Exstream 16.x (Streamserve v5), Infor delivers the following:
• Main projects to create runtime environment for all standard programs and market modifications in M3
Business Engine
• All projects, source files, for the layouts, test data and example reports to be used for customer
modifications.
The StreamServe/Exstream Layout Files are included in the base package for M3 Business Engine.
After uploading the base package for M3 Business Engine and configuring the StreamServe/Exstream location
in LifeCycle Manager, all layout files are available on the StreamServe/Exstream server.

Install base to an additional component

This section describes the procedures on how to install a base to an additional component for M3 Business
Engine.
When installing the base of an additional component, you must also update the system configuration in M3
Business Engine, create the component schema, create new language tables, and copy data before the
component can be used in the M3 Business Engine system.
For information on how to upload and install additional M3 BE Packages, see Uploading M3 BE Packages on
page 64 and Installing M3 BE packages on page 64.
Creating a system configuration in M3 BE

This section describes the procedures about how to create system configurations in M3 Business Engine.
A system configuration is specified through up to five system components. The definitions made to system
component and system configuration define the classpath to be used by the server to access M3 Business
Engine.
The LifeCycle Manager Environment Configurator is used to set up the system configuration for a M3 Business
Engine environment. The two tabs, Configuration and Components, are equivalent to the M3 Business Engine
programs ‘System Configuration. Open’ (MNS102) and ‘Configuration Component. Open’ (MNS104)
There are icons or buttons located at the upper right hand part of the Environment Configurator window,
allowing you to add, delete, save, undo, refresh, and use horizontal or vertical orientation in viewing.
Note: The System Configurations pane is displayed by default. However, set the component first before the
system configurations.
Create system component

This section describes the steps to take in order to create a system component including a service pack, fixes,
database/schema and view paths.
1 Right-click the environment and select Environment Configurator.
2 Click on the Components pane located in the lower left hand part of the window.
3 Click the plus icon in the upper right hand part of the Environment Configurator window. The New
Component window is displayed.
4 Enter the component name and click OK.
In the right hand part of the window, the Component details, a default schema is entered. If this is not
the correct schema or if the default schema is already in use, please change.
Note:
When LifeCycle Manager installs the component, all files that belong to the component will be placed in
this component’s folder under the M3 BE installation root. The name of the component defined in the
Environment Configurator must correspond to the name of the component folder.

5 If you plan to install fixes for the component, remember to also tick the fix check boxes.
The fixes and service pack information will be added to the server's classpath in order of priority, that is
in the order they are defined in the Component Details, the highest priority being hot fix at the top.
6 Click the save icon in the upper right hand part of the Environment Configurator window.
7 Depending on the environment status:
• If the environment is running, the message "Set M3 BE in maintenance mode" is displayed. Click OK
to save the new component.
• If the environment is stopped, the environment is started in maintenance mode and the new
component is saved.
Note:
The environment is in maintenance mode until the application is started, or set online.
Create system configuration

This section describes the steps to take in order to create a system configuration and connect it to up to four
system components.
1 Right-click the environment and select Environment Configurator.
2 Click on the Configurations pane located in the lower left hand part of the window.
3 Click the plus icon in the upper right hand part of the window Environment Configurator. The window
New System Configuration window is displayed.
4 Enter a name for the System configuration and click OK.
5 Enter a description for the configuration in the Description field.
6 Select the newly created component from the Components drop-down list.
Note:
The components must be defined in the order (from top to bottom): customer modification, market
modification, standard base (MVX).
7 Click the save icon in the upper right hand part of the Environment Configurator window.
• If the environment is running, the message "Set M3 BE in maintenance mode" is displayed. Click OK
to save the new configuration.
• If the environment is stopped, the environment is started in maintenance mode and the new
configuration is saved.
Note:

Connect the system configuration

Before you connect your system configuration to a Company and Division, ensure that your environment is
started. Start a session towards the M3 Business Engine in an M3 UI product, and open ‘Company. Connect
Division’ (MNS100) to attach the component.
When a job is started on this particular company and division, the server creates a classpath to access the
system, based on the information defined in the system configuration and system components.
Creating a database schema
Create database
1 Right-click your environment and select Database > Create Database.
• If the environment is running, the message "Set M3 BE in maintenance mode" is displayed. Click
Next.
• If the environment is stopped, the environment is started in maintenance mode.
Note
The environment is in maintenance mode until the application is stopped, started, or set online.
3 Enter the database user login information:

User
MDBADM
Password
Enter a password for the user.
Click Next.
4 Select component and system configuration.
Component
The component specified in the Environment Configurator Components pane (or in MNS104).
System configuration
The system configuration specified in the Environment Configurator Configurations pane (or in MNS102)
Note
The database schemas for the new component will be created automatically according to the specification
in Environment Configurator Components pane (MNS104).
Click Next.

6 When the task is finished, a dialog appears. Click OK. To view the log file, either click View log or go to
the Logs view.
Creating new language tables
Create language tables

1 Right-click your environment, and select Database > Create Database Language Tables.
2 Enter database user login information:
User
MDBADM
Password
Enter the password for user.
Click Next.
3 Select Create language tables for uploaded languages, and click Next.
4 Select the component specified in the Environment Configurator (MNS104) for which to create language
tables, and click Next.
5 Select the component and language code, and click Next.
Note:
An additional component can contain several languages. Note that only the uploaded languages are
displayed in this list.
the Logs view.
Importing a database data for additional component
Import database data

Use the task Import Database Data to copy delivery data to the database.
1 Right-click your environment, and select Database > Import Database Data.
• If the environment is running, the message "Set M3BE environment in maintenance mode" is
displayed. Click Next.


Note:
The environment is in maintenance mode until the application is stopped, started, or set online.
3 Specify the database user login information:

User
MDBADM
Password
Enter the password for the user.
Click Next.
4 Select the default mode Import Database Data.
The different configuration options works as follows:
Import Database Data
Select this option to import specific data.
Import Database data using saved configuration

Select this option to import specific data using a saved configuration.
Note:
It is recommended to save the settings or configuration related to data that you frequently use, such as
tables, to save you from providing the data again.
Delete configuration
Select this option to remove a saved configuration.
When the second and third options are selected, the Load Configuration field is enabled. It allows you
to use or delete a saved configuration. The configuration is stored in the LCM client workspace that you
selected when you logged in. If you can not find your saved configuration, consider if you saved the
configuration in another workspace, or in a workspace for another LCM Client.
5 Select data zip files to import.
Source zip files uploaded to LCM server
Select the zip files to be added by selecting the check box to the left of the zip file name. It is possible to
select several files at a time.
Source zip files stored in local M3BE installation path

Select the zip files to be added by selecting the check box to the left of the zip file name. It is possible to
Example for a market:
/M3BE/_db_data/<Mxx>/15.1/delivery_data.zip
Click Next.
6 Select tables to import to database.

Component
Select the component specified in the Environment Configurator Components pane (MNS104).
Database schema
Depending on your selection of component, the correct schema is presented.
7 Select the default mode Import all tables.

The different table selections work as follows:
Import all tables
All tables will be imported
Enter table name

One specific table will be imported, enter the name in the text field.
Select tables
A selection of tables are presented in the box at the bottom of the dialog.
Click Next.
8 Select the import strategy "Copy tables without checking for duplicate keys".
The different strategies work as follows:
Replace existing records
The records in target that have a duplicate in the source are replaced by the ones imported.
Keep existing records

The existing records in both source and target are left unchanged in the target.
Copy tables without checking for duplicate keys

All records will be inserted without checking for duplicate keys. This may cause an exception if records
already exists.
Note:
This option is recommended when the target database is empty, and in other situations when there is
no risk of duplicate keys. This option increases the copy data performance significantly.
Clear target tables before import

For tables that exist in both source and target, data are cleared in target tables before import.
Allow data mismatch

Select this option to allow the format of the existing table and the imported tables to differ without
causing any errors.
9 Click Next.
10 To save this configuration, specify a unique name, and click Next.
the Logs view.

Uploading and installing additional M3 BE packages

This chapter describes the procedures on how to upload and install additional M3 BE Packages after the base
installation, and also details the naming standards for the available package types.
Additional M3 BE Package Types

Package Types File Name Format Description
Market Modifications M3BE_15.1_[Mxx].zip Mxx is the two-letter abbreviation for
a market, pre-fixed by M, for example
MSE for the Swedish market.
Customer Modifications M3BE_15.1_[XXX].zip XXX is a three letter abbreviation for a
customer, for example EXC for the
customer Example Company.
Standard Languages languageS_[<language_code>]_MVX_15. <language_code> is the two-letter ab-
1_n.zip breviation for a language (for example,
SE for Swedish).
n is the order number of the language
file package.
Language Market Modifi- languageM_[<language_code>]_[Mxx]_ <language_code> is the two-letter ab-
cation 15.1_n.zip breviation for a language (for example,
SE for Swedish).
Mxx is a two-letter abbreviation for a
country code (for example, MSE for
Sweden).
file package.
Document Languages languageO_XX_15.1_n.zip XX is the language code.
n is the order number of the document
language file package.
Feature Packs FPn_15.1_[MVX][Mxx].zip n is the order number for the feature
pack.
MVX indicates the standard M3 installa-
tion.
Mxx is the two letter abbreviation for
a country code (for example MSE for
Sweden).
For information on fixes, see Install fixes on page 76 .

Upload M3 BE Packages
This procedure describes how to upload additional packages to install on M3 Business Engine.
Uploading M3 BE Packages
1 Right-click M3BE_15.1, and select Upload M3BE packages.
2 Click Select… and choose the directory that contains the M3 Business Engine packages. You can select
several packages at a time.
Note:
To select all packages, right-click in the list and select the option Select all.
Select your packages and click Next.
3 On the Summary screen, verify the property values, and click Finish
the Logs view.
Install M3 BE packages
Installing M3 BE packages
1 Right-click M3BE_15.1, and select Install M3BE Packages.
2 Select the M3 Business Engine packages to install in the list. You can select several packages at a time.
Note:
Click Next.
The appropriate Viewdefinitions, language files and help files and OUT layouts are installed at the same
time.
the Logs view.
Uploading and installing additional M3 BE packages

This chapter describes the procedures on how to upload and install additional M3 BE Packages after the base
installation, and also details the naming standards for the available package types.

Additional M3 BE Package Types

Package Types File Name Format Description
Market Modifications M3BE_15.1_[Mxx].zip Mxx is the two-letter abbreviation for
a market, pre-fixed by M, for example
MSE for the Swedish market.
Customer Modifications M3BE_15.1_[XXX].zip XXX is a three letter abbreviation for a
customer, for example EXC for the
customer Example Company.
Standard Languages languageS_[<language_code>]_MVX_15. <language_code> is the two-letter ab-
1_n.zip breviation for a language (for example,
SE for Swedish).
file package.
Language Market Modifi- languageM_[<language_code>]_[Mxx]_ <language_code> is the two-letter ab-
cation 15.1_n.zip breviation for a language (for example,
SE for Swedish).
Mxx is a two-letter abbreviation for a
country code (for example, MSE for
Sweden).
file package.
Document Languages languageO_XX_15.1_n.zip XX is the language code.
n is the order number of the document
language file package.
Feature Packs FPn_15.1_[MVX][Mxx].zip n is the order number for the feature
pack.
MVX indicates the standard M3 installa-
tion.
Mxx is the two letter abbreviation for
a country code (for example MSE for
Sweden).
For information on fixes, see Install fixes on page 76 .
Uploading M3 BE Packages
1 Right-click M3BE_15.1, and select Upload M3BE packages.
2 Click Select… and choose the directory that contains the M3 Business Engine packages. You can select
several packages at a time.

Note:
Select your packages and click Next.
3 On the Summary screen, verify the property values, and click Finish
the Logs view.
Installing M3 BE packages
1 Right-click M3BE_15.1, and select Install M3BE Packages.
2 Select the M3 Business Engine packages to install in the list. You can select several packages at a time.
Note:
Click Next.
The appropriate Viewdefinitions, language files and help files and OUT layouts are installed at the same
time.
the Logs view.
Install additional languages

This section describes the procedures on how to install an additional language to the standard M3 Business
Engine.
When you install an additional language, you must create language tables and import database data before
the language can be used in the M3 Business Engine system.
If a new language is installed after several feature packs, MCPs or MCEs are installed, the installation step
automatically updates the language (.lng) file with all delta language packs found for the new language. When
you import the delivered database data, ensure that you also import the data for the language from the latest
feature pack or MCP.
For information on how to upload and install additional M3 BE packages, see Uploading M3 BE Packages on

Create language tables
Create tables
1 Right-click your environment, and select Database > Create Database Language Tables.
User
MDBADM
Password
Enter the password for the user.
Click Next.
3 Select Create language tables for uploaded languages, and click Next.
4 For an additional component, select the component specified in the Environment Configurator (MNS104).
For standard, select the MVX component and click Next.
5 Select the component and language code, and click Next.
Note:
Note that only the uploaded languages are displayed in this list.
the Logs view.

Use the task Import Database Data to copy delivery data to the database.

1 Right-click your environment, and select Database > Import Database Data.
• If the environment is running, the message "Set M3 BE in maintenance mode" is displayed. Click
Next.
Note:

User
MDBADM
Password
Enter the password for user.
Click Next.
4 Select the default mode Import Database Data.
The different configuration options works as follows:
Select this option to import specific data.
Import Database data using saved configuration

Select this option to import specific data using a saved configuration.
Note:
It is recommended to save the settings or configuration related to data that you frequently use, such as
tables, to save you from providing the data again.
Delete configuration
Select this option to remove a saved configuration.
When the second and third options are selected, the Load Configuration field is enabled. It allows you
to use or delete a saved configuration. The configuration is stored in the LCM client workspace that you
selected when you logged in. If you can not find your saved configuration, consider if you saved the
configuration in another workspace, or in a workspace for another LCM Client.
5 Select the source data zip files to import.
Source zip files uploaded to LCM Server
Select the zip files to be added by selecting the checkbox to the left of the zip file name. It is possible to
select several files at a time
Source zip files stored locally on server

Select the zip files to be added by selecting the checkbox to the left of the zip file name. It is possible to
Example:
/M3BE/_db_data/MVX/15.1/languageS/delivery_data_SE_1.zip
Click Next.
6 Select tables to import to database.
Component
For an additional component select the component specified in the Environment Configurator. For
standard select the MVX component.
Database schema
Depending on your selection of component, the correct schema is presented.

7 Select the default mode Import all tables.

The different table selections work as follows:
Import all tables
All tables will be imported
Table name
One specific table will be imported, enter the name in the text field
Select table names

A selection of tables are presented in the box at the bottom of the dialog
Click Next.
8 Select the default import strategy Replace existing records.
The different strategies work as follows:
Replace existing records
The records in target that have a duplicate in the source are replaced by the ones imported.
Keep existing records

The existing records in both source and target are left unchanged in the target.
Copy tables without checking for duplicate keys

All records will be inserted without checking for duplicate keys. This may cause an exception if records
already exists.
Note:
This option is recommended when the target database is empty, and in other situations when there is
no risk of duplicate keys. This option increases the copy data performance significantly.
Clear target tables before import

For tables that exist in both source and target, data are cleared in target tables before import.
Allow data mismatch

Select this option to allow the format of the existing table and the imported tables to differ without
causing any errors.
9 Click Next.
10 To save this configuration, type a unique name, and click Next.
12 When the task is finished a dialog appears. Click OK. To view the log file, either click View log or go to the
Logs view.
Note:
If you already have applied a feature pack or an MCP that contains a delta delivery of the languages, you
must repeat this task from step 1 for the delta delivery zip files to complete the installation. For a feature
pack or MCP, you will find the data ZIP files in the following folder:
M3BE\_db_data\[component]\15.1\[H][T][V]Fix_deltalanguages\

Create system language

It is possible to install M3 Business Engine with several different system languages in the same installation.
The system language is connected to an M3 user determining what language should be used.
The M3 Business Engine environment must be started before you run the procedure. See the procedure Start
Environment located in the M3 Core Administration Guide which is available in the M3 Core I&T documentation
on docs.infor.com.
Add system language

1 Log on to the applicable M3 UI product as a user with access rights to 'System Language. Open' (MNS105)
and 'User. Open' (MNS150).
2 Start the program 'System Language. Open' (MNS105) and specify the code for a new system language
from the list.
Click Options > Create.
3 Start the program 'User. Open' (MNS150) and connect the new language to an appropriate user.
Click Options > Change.
4 Log off.
Generate M3 BE Menu for Infor Smart Office

Generate M3 BE menu
The M3 Business Engine menu in Infor Smart Office is retrieved directly from M3 Business Engine when started.
The M3 Business Engine menu needs to be generated for all different languages available and regenerated
each time the language tables is updated with new data. Before you can generate the menu for a specific
language, make sure that the language exists in the M3 Business Engine program ‘System Language. Open’
(MNS105). Start ‘Menu System. Mass Update’ (MNS910) and use option 1 to generate the menu for the language.
Install document languages
Install document languages

This section describes the procedure of installing document languages to M3 Business Engine.

A document language delivery contains only the .lng files to be installed on the OpenText
StreamServe/Exstream server. If you have already installed an Additional Language all necessary language
files are already available on the connected OpenText StreamServe/Exstream server.
For information on how to upload and install additional M3 BE Packages, see Uploading M3 BE Packages on
Install feature packs

This section describes the procedures for installing feature packs to M3 Business Engine.
If your installation includes market modifications, you must install the corresponding feature pack for the
market modifications too.
The feature packs will be installed in the VFix folder in the specified environment under the corresponding
component. For standard M3 BE and market modifications, the VFix folder is reserved for feature packs,
corresponding to how the TFix folder is reserved for MCEs.
What is a Feature Pack?

A feature pack contains all updates since the previously delivered feature pack, or in the case of the first
feature pack version, the updates made since the base delivery of M3 Business Engine 15.1.0.
A feature pack includes:
• New functionality and features
• Regulatory and statuatory updates
• All Maintenance Correction Entities (MCE - Maintenance Correction Entity on page 78) made since the
previously delivered feature pack, or in the case of the first feature pack, the base version.
Note:
When you install a feature pack, all the previously installed MCEs are removed from the M3 BE environment.
When you install a feature pack, the M3 BE version information in LifeCycle Manager is updated, and a new
CCSS channel for this M3 BE version is created. The base delivery of M3 Business Engine is version 15.1.0.
When you install a feature pack, the third digit is updated (e.g FP1 = 15.1.1, FP2 = 15.1.2 etc).
Note:
Only the MCEs retrieved for this M3 BE version will displayed in Manage Fixes. Ensure that all market
modifications installed on your M3 Business Engine environment are on the same feature pack version as the
standard M3 BE in your installation.

Installing Modifications for a New Market After Installing a

Feature Pack
If you decide to install modifications for a new market after you have installed a feature pack for the standard
M3 BE and existing market modifications, follow these steps:
Install a Modification for a New Market after Installing a Feature Pack
1 Install the base delivery of the market modification.
2 Install the feature pack, MCP and MCE corresponding to the standard M3 BE version of your installation.
3 Create the database for the new market.
Apply feature pack

Apply a feature pack to an M3 Business Engine environment.
Ensure that all required feature packs for standard M3 Business Engine and all configured market components
are uploaded to the LifeCycle Manager server. Upload M3 BE Packages on page 64
Apply feature pack

1 Right-click your environment and select Fixes > Apply Feature Pack.
2 Select the feature pack version for standard M3 Business Engine to upgrade your environment to.
Current version
Verify the current version.
Upgrade to
All feature pack versions for standard M3 Business Engine that are uploaded to the LifeCycle Manager
Server are displayed here.
Markets that will be upgraded

Displays a list of all market components configured in a system configuration in your environment. All
available markets in this list will be upgraded.
Markets that can not be upgraded

All markets that are installed and configured on this environment and do not have a corresponding
feature pack version uploaded to the LifeCycle Manager Server are displayed here.
Note: Infor requires you to always install the same feature pack version for both standard M3 Business
Engine and all installed markets at the same time.
Click Next.
3 A list of the installed standard or market modification fixes that are in conflict with the feature pack is
displayed. Select to remove all these conflicting files.

Click Next.
4 A list of the installed standard or market modification fixes that do not conflict with the feature pack is
displayed. These files might be affected by the files to be installed. Select the files to be removed by
selecting the check box in front of the file name.
Click Next.
5 A list of the installed customer modifications on this environment is displayed. These files might be
affected by the files to be installed. Select the files to be removed by selecting the check box in front of
the file name.
Click Next.
6 Select if you want to save the information provided in the previous steps, and information about all MCEs
that will be removed to a spread sheet.
8 When the task is finished, a dialog is displayed. Click OK. To view the log file, either click View log, or go
to the Logs view.
9 If the feature pack you applied contains database interface changes, changes to database delivery data,
MI transactions or fix programs, a new window informs you to perform one or more of the following tasks:
• If the feature pack contains DB Interface: run the Upgrade Database with Fix/Feature Pack task.
Note: If archiving is used on your installation, run the Upgrade Archiving Schema task. See M3 BE
LifeCycle Manager User Guide.
• If the feature pack contains a DB data zip file: run the Import Database Data task.
• If the feature pack contains MI transactions: run the Apply MI metadata task.
• If the feature pack contains fix programs: run the Run Fix Programs task.
Click Details. A Notepad window with information about for which fix(es) the different tasks must be run
is displayed.
Note:
For more information regarding fix programs to run for this feature pack, read the applicable net change
report (NCR). The NCR is available on Infor Support Portal.
Note:
The appropriate Viewdefinitions, language files, help files, and OUT layouts are installed at the same
time.
Update Environment with Delta Languages

This chapter describes how to update the already installed languages after you have applied a feature pack
that includes delta language updates.
A delta delivery is not a complete delivery of language files, it requires that the base language package has
been installed in your environment before you can update it with the delta delivery in this fix.
The language files (.lng files) and field help files are automatically updated when you apply a feature pack,
but there are still steps needed before a complete update of the language installation is done.


The task Import Database Data with merge mode Replace existing records must be executed to merge the
updated language data into the database. You can find the XML data ZIP files in the following folder:
M3BE\_db_data\[component]\[BE version]\VFix_deltalanguages
You can also go to the Select data zip files page, select the Sort and filter source zip files check box to filter
the list of available files depending on installed fixes.
Primarily , the sort order will be:
1 Data zip files that are uploaded through Upload M3BE Packages, for example, IA_DIS_1512_XML.zip
2 Data zip files that are exported, for example, exported_data/cpm900.zip
3 Components in alphabetical order
Then, the sort order of source zip files per component will be:
• Base delivery data, for example, MVX/15.1/delivery_data.zip
• Base language data for all languages, for example, MVX/15.1/languageS/delivery_data_SE_1.zip, sorted
by language in alphabetical order.
• FP delivery data, for example, MVX/15.1/VFix/delivery_data_FP1.zip, sorted by FP order such as FP1,
FP2, FP3, and so on.
• FP language data for all languages, for example, MVX/15.1/VFix_deltalanguages/delivery_data_FP1_GB.zip,
sorted by FP order and language in alphabetical order.
• MCE and MCP language data for all languages, for example, MVX/15.1/TFix_deltalanguages/TFix_MVXCON
GB_JT-826579.zip, sorted by the order in which the MCEs were applied. When filtering is enabled, the
view shows only the applied MCEs data.

Applying MI metadata
Use this procedure to apply MI metadata to your M3 BE environment.
To apply MI metadata
1 Right-click the environment and select Fixes > Apply MI metadata. The window Apply MI metadata is
displayed.
Note:

You can also open the task by clicking Apply MI metadata on the Dashboard tab Fixes.
2 The Start Environment in restricted mode information dialog is displayed. This means that the environment
will be shutdown and when re-started in restricted mode, only the LCM Client can run M3 Business Engine
jobs. An M3 BE user cannot login to an M3 UI or run M3 BE programs during the time it takes to run this
task.
Note:
Do not perform any other tasks that affect this M3 Business Engine environment while running Apply MI
metadata.
When the task is finished the environment status is changed to running mode. Click Next.
3 Provide information in these fields:
Select program
Select MI programs to apply. Right-click in the list and select all.
View All
• Select View All to display all available MI programs, or,
• Clear View All to display only the MI programs that can be applied.
Hide not applied but overridden

If View All is selected then this option will hide all programs that are overridden by another fix.
M3 user
Specify a M3 BE user
M3 user password
Specify the password
Click Next.
to the Logs view.
Run Fix Programs

Use this procedure to run fix programs for your M3 BE environment.
Note:
It is important that this task is executed each time after you have applied a feature pack for standard and or
for markets. Also in cases where not much data exists in the database the task needs to be run to set the
correct status for all fix programs in the M3 BE program (CMS950).
Note:
The run fix programs task is only applicable for environments running M3 Foundation 10.1.3.0 or newer
versions and when applying feature pack 3 (M3 BE 15.1.3) or newer versions.

To run fix programs:

1 Right-click the environment and select Fixes > Run Fix Programs. The window Run Fix Programs is
displayed.
Note:
You can also open the task by clicking Run Fix Programs on the Dashboard tab Fixes.
task.
Note:
Do not perform any other tasks that affect this M3 Business Engine environment while running Run Fix
programs.
M3 user:
Note:
The M3 BE user specified must be a user that is enabled to run at least one company/division for each
available system configuration that exists for this specific environment (Update User in MNS150).
M3 user password:
Click Next.
to the Logs view.
Status of fix programs can be viewed in the M3 BE program CMS950.
Note:
Some fix programs are delivered in status 03 (=optional) and will not be run when running the task 'Run
Fix Programs' from LifeCycle Manager. These fix programs are delivered in status optional since they are
not required to be run immediately after an upgrade. They can be scheduled to be run during a weekend
or in a nightly run. More information regarding the new fix program handling can be found in the NCR
for M3 BE 15.1.3.
Install fixes
A fix can be a single or a bundle of individual corrections to M3 Business Engine. It is delivered in a zip file.
The different types of fixes are as follows:
• HFix – Hot fix

• VFix – Verified fix

• MCE - Maintenance Correction Entity
• MCP - Maintenance Correction Pack
The following sections are included:
HFix – Hot Fix

A hot fix is made by using the M3 Adaptation Kit (MAK) and can also be deployed from the MAK tool by personnel
from Infor at customer site or through remote access.
For more information about how to create and deploy hot fixes, see M3 Adaptation Kit User Guide available
in the M3 Core I&T documentation on docs.infor.com.
The naming standard for the zip file is:
HFix_<hotfix info>_<component>.zip.
The component name can be any of the following:

• MVX for standard (M3 Business Engine)
• Mxx for a market modification, where xx stands for market, such as SE for the Swedish market.
• ppp for a customer modification, where ppp stands for CUS or a customer unique ID, such as TWI for the
Twilfit customer.
• MI[n] where [n] is a digit 1-9 for an industry component
A hot fix applied for an Additional Component need to have its corresponding fix level activated in the
Environment Configurator to become active.
VFix – Verified Fix

The VFix folder can be used by the project as an internal way of verifying hot fixes.
The naming standard for the zip file is: VFix_<verifiedfix info>_<ppp>.zip ppp is a component name that
refers to a customer modification. It stands for CUS or a customer unique ID, such as TWI for the Twilfit
customer.
A verified fix is created by exporting a deployed hot fix using the M3 Adaptation Kit tool by personnel from
Infor at customer site or via remote access.
For more information about how to export hot fixes to the VFix folder, see M3 Adaptation Kit User Guide.
A verified fix applied for a customer component needs to have its corresponding fix level activated in the
Environment Configurator to become active.

How to Download and Install in CCSS Mode

Customer Correction Self Service (CCSS) is a process and a set of tooling that support and simplify download,
analysis and installation of single fixes and country functionality into an M3 Business Engine environment.
For more information, see M3 BE 15.1- How to Download and Install in CCSS mode, topic #29229 in Infor Support
Portal Documentation.
MCE - Maintenance Correction Entity

A Maintenance Correction Entity (MCE) is an individual solution made to solve a reported issue for a particular
version of M3 Business Engine and the MCE is provided for download from a central server at Infor as a part
of the Customer Correction Self Service (CCSS) solution. The MCE is packaged as a zip file in the Temporary
Fix (TFix) format and the naming standard for the zip file is:
TFix_<solution_no>_<component>.zip
The component name can be any of the following:

• MVX for standard (M3 Business Engine)
• Mxx for a market modification where xx stands for market, such as SE for the Swedish market.
An MCE applied for a market modification need to have its corresponding fix level activated in the Environment
Configurator to become active.
MCP - Maintenance Correction Pack

Maintenance Correction Pack (MCP) is the preferred method for installing fixes.
An MCP is a manually packaged MCE which has relations to a number of MCEs. Each MCP also contains
accumulated delivery units for Language components, and API metadata for the related MCEs. Individual
MCPs are delivered for each country (Mxx) and the standard component (MVX). Installing an MCP will install
all related MCEs.
The MCP is created at a certain point in time, and includes references to all MCEs available for the component
at that time. Each MCP is cumulative, therefore it is only necessary to download and install the latest. An MCP
(and all related MCEs) cannot be deactivated.
The MCP is packaged as a zip file in the Temporary Fix (TFix) format, and the naming standard for the zip file
is: TFix_MCP<mm>-<BE version>- <nn>_<component>.zip
<mm> is a sequence number, <BE version> is the M3 BE version, and <nn> is a build number starting with 01.
Note:
To see which MCPs that are installed, open the management pages for the BE environment, and click the
About link.

Upload Fixes Package

Before starting the installation, the zip file must be uploaded to the LifeCycle Manager Server.
Fixes are uploaded using the procedure Upload M3 BE Packages on page 64, while MCEs are uploaded using
the procedure Retrieve MCE.
You may need to set up access to the CCSS server before you can retrieve MCE packages. For example, if your
organization uses a proxy server to access the internet, you must first set up LifeCycle Manager to recognize
the proxy. Review the guidelines and procedures in Managing Access to the Customer Correction Self
Service (CCSS) Server in the M3 LifeCycle Manager User Guide.
Retrieve MCE
1 Right-click M3BE_xx.x and select Retrieve MCE.
The notation xx.x refers to the current version of the M3 Business Engine.
2 The Logon to CCSS Sever dialog appears. Enter the User and Password used for logging on to the Infor
Support Portal site, and click OK.
3 In the Solution overview pane, search a solution from the list of available MCEs using these filter options:
Solution
Specify the ID number of the solution.
Description
Specify a description of the solution.
Component
Select the component to which the solution belongs, or select ALL to show all components.
Show
Select to view all solutions or view only those that have been retrieved or not retrieved already.
View
Select to view 100, 500 or ALL MCEs
4 Click Search. The search results are displayed. The following table lists the status that might be displayed
in the Retrieved column of the results list:
Status Description
The solution is retrieved and is available on the LifeCycle Manager Server.
The solution is not yet retrieved.
5 Select one solution in the list. The details and possible dependencies of the selected MCE solution are
displayed.
6 Select the check box of one or more solutions, or right-click and select Select All MCE's. Click Retrieve.
7 Click OK. The MCE solution and all dependencies that are not yet retrieved are retrieved and uploaded
to the LifeCycle Manager Server.

Apply Fixes
Use this procedure to install a fix, or one or more MCEs, to any environment using the Apply Fix function.
Apply Fixes
1 Right-click your environment and select Fixes > Manage Fixes.
2 In the Fix(es) overview pane, search for a fix using the following filter options:
Name
Type the name of the fix.
Solution
Type the ID number of the solution.
Description
Type a description of the fix.
Component
Select the component to which the solution belongs or select ALL to show all solutions.
Show
Select to view all solutions or view only those that have been applied or not applied already.
Applied By
Type the name or ID of the user who installed the fix.
Applied Date
Type the date when the fix was applied.
3 Click Search. The search results are displayed. The following table lists the different statuses that might
be displayed in the results list:
Status Icon Description

Applied The fix is fully applied
Superseded The MCE is fully replaced by a later MCE (only valid

for MCEs).
Partially superseded One or more of the files included in the MCE is re-
placed by a later MCE (only valid for MCEs)
Not Applied The fix is not applied
Partially Applied One or more of the files included in the fix is ap-
plied, but not all of them (only valid for fixes that
are not MCEs)

4 Select a fix in the list. Complete information about the fix and each file that is included in the fix is
displayed. For MCEs, possible dependencies are also shown.
Depending on the filter you use, a list with search results is displayed. Note that the search results include
only all MCEs and fixes that were found based on the filter criteria. In the results window, you can right-click
to select or deselect all the MCEs found by the search.
Note:
The selected fix will be displayed in bold font in Fix(es) Details. All fixes that also contain changes to the
database are displayed in blue. MCEs containing database changes cannot be removed once applied.
Click Apply.
5 If the fix to apply is an MCE package, LifeCycle Manager will scan the M3 Business Engine environment
for conflicts.
If no conflicts are found a message box appears, click OK to apply the fix.
If conflicts are found, the Apply Fix wizard is started, continue below.
Apply Fix Wizard

Fixes that are in conflict with the current M3 Business Engine environment are applied using the Apply Fix
wizard. It is automatically started when the type of the fix, or conflict, is determined.
1 The Apply Fix wizard is started.
The appropriate Viewdefinitions, language files, help files and OUT layouts are installed at the same time.
Click Next.
2 Select a Fix type in the list and type a description for the fix. Click Next.
3 A list of already existing files in the target folder is presented. These files will be replaced by the files to
be installed. Click Next.
4 A list of files that exist in another fix type folder or as a fix for an additional component is displayed. These
files might be affected by the files to be installed. Select the files to be removed by selecting the check
box in front of the file name. Click Next. The files that are not selected will remain in the specific
environment.
5 A list of files that might affect the behavior of the fix to be installed are presented. If there are no conflicting
files found, click Next.
the Logs view.
8 If the fix you applied contains database interface changes, changes to database delivery data, MI
transactions or fix programs, a new window informs you to perform one or more of the following tasks:
• If the fix contains DB Interface: run the Upgrade Database with Fix/Feature Pack task.
Note:
If archiving is used on your installation, run the Upgrade Archiving Schema task. For more information,
see M3 BE LifeCycle Manager User Guide.
• If the fix contains a DB data zip file: run the Import Database Data task.
• If the fix contains MI transactions: run the Apply MI metadata task.

• If the fix contains fix programs: run the Run Fix Programs task.
Note:
The run fix programs task is only applicable for environments running M3 Foundation 10.1.3.0 or
newer versions and when applying a fix on the M3 BE 15.1.3 or newer versions.
Click Details. A Notepad window with information about for which fix(es) the different tasks must be run
is displayed.
Update Environment with Delta Languages

This chapter describes how to update the already installed languages after you have applied a Fix that includes
delta language updates.
A delta delivery is not a complete delivery of language files, it requires that the base language package has
been installed in your environment before you can update it with the delta delivery in this fix.
The language files (.lng files) and field help files are automatically updated when applying a fix but there are
still steps needed before a complete update of the language installation is done.

The task Import Database Data with merge mode Replace existing records must be executed to merge the
updated language data into the database. You can find the XML data ZIP files in the following folder:
M3BE\_db_data\[component]\[BE version]\[H][T][V]Fix_deltalanguages
You can also go to the Select data zip file page, select the Sort and filter source zip files check box to filter the
list of available files depending on installed fixes.
Primarily , the sort order will be:
1 Data zip files that are uploaded via Upload M3BE Packages, for example, IA_DIS_1512_XML.zip
2 Data zip files that are exported, for example, exported_data/cmp900.zip
3 Components in alphabetical order.
Then, the sort order of source zip files per component will be:
• Base delivery data, for example, MVX/15.1/delivery_data.zip
• Base language data for all languages for example, MVX/15.1/languageS/delivery_data_SE_1.zip, sorted
by language in alphabetical order.
• FP delivery data, for example MVX/15.1/VFix/delivery_data_FP1.zip, sorted by FP order such as FP1,
FP2, FP3 and so on.
• FP language data for all languages, for example, MVX/15.1/VFix_deltalanguages/delivery_data_FP1_GB.zip,
sorted by FP order and language in alphabetical order.

• MCE and MCP language data for all languages, for example, MVX/15.1/TFix_deltalanguages/TFix_MVXCON
GB_JT-826579.zip, sorted by the order in which the MCEs were applied. When filtering is enabled, the
view shows only the applied MCEs data.

Applying MI metadata
Use this procedure to apply MI metadata to your M3 BE environment.
To apply MI metadata
1 Right-click the environment and select Fixes > Apply MI metadata. The window Apply MI metadata is
displayed.
Note:
You can also open the task by clicking Apply MI metadata on the Dashboard tab Fixes.
will be shutdown and when re-started in restricted mode, only a the LCM Client can run M3 Business
Engine jobs. An M3 BE user cannot login to an M3 UI or run M3 BE programs during the time it takes to
run this task.
Select program
Select MI programs to apply. Right-click in the list and select all.
View All
• Select View All to display all available MI programs, or,
• Clear View All to display only the MI programs that can be applied.
Hide not applied but overridden

If View All is selected then this option will hide all programs that are overridden by another fix.
M3 user
M3 user password
Specify the password

Click Next.
to the Logs view.
Run Fix Programs

Use this procedure to run fix programs for your M3 BE environment.
Note:
The run fix programs task is only applicable for environments running M3 Foundation 10.1.3.0 and M3 BE
15.1.3 or newer versions.
To run fix programs:
1 Right-click the environment and select Fixes > Run Fix Programs. The window Run Fix Programs is
displayed.
Note:
You can also open the task by clicking Run Fix Programs on the Dashboard tab Fixes.
task.
Note:
Do not perform any other tasks that affect this M3 Business Engine environment while running Run Fix
programs.
M3 user:
Note:
The M3 BE user specified must be a user that is enabled to run at least one company/division for each
available system configuration that exists for this specific environment (Update User in MNS150).
M3 user password:
Click Next.
to the Logs view.

Install M3 Foundation Information Reader

Use the procedure below to install the optional Infor M3 Foundation Information Reader, This tool will do the
following:
• Consume XML files from an arbitrary number of LCM servers (as specified in the configuration); process
them and present information to the users.
• Monitor executing auto jobs and warn if any critical jobs stops running. The monitoring is configurable.
• Monitor the remaining range of a number series, which is configurable.
• Monitor batch queues and warn if they never shrink.
• Monitor the News flow and warn for dump logs.
Install the InfoReader

1 In the LifeCycle Manager, navigate to your space, right-click your Grid and select Install Product to start
the installation wizard.
2 Select the product M3 Foundation Information Reader, and click Next.
Session Provider User:
Enter a session provider authenticated user name that will be used for this application
Session Provider Password:

Specify the password for the user
Click Next.
5 The Install task is displayed in the Progress view. When the step is completed, a message box is displayed.
Click OK. To view the log file, either click View log or go to the Logs view.
Install M3 Web Services

Use these steps to make a first-time installation of M3 Web Services.
Make sure that your Infor ION Grid is started.
Install the M3 Web Services application

1 In LifeCycle Manager, choose Actions> Install Products.
2 Select Infor M3 Web Services, and click Next.
3 On the Location window, select the Grid where you want to install M3 Web Services. Click Next.
4 In the Add Application to Hosts window:

a Enter an application name and description, for example MWS.

Note:
The application name is used to identify the M3 Web Services grid application.
b Select a host to install to.
5 Click Next, and click Finish.
A dialog displays where the installation is completed.
Verify that the MWS Grid application is running

1 In the Application tab, right-click the grid where MWS is installed. Select Grid Management Pages.
2 Click the MWS link next to Application.
The running MWS grid application is identified with the status OK RUNNING.
Install Infor Enterprise Collaborator

Use these instructions to install the EC Server.
Infor ION Grid must be started.
Setting the Central File folder

The Central File folder is a local folder in the domain accessible to the Grid Agent of the EC_Central node, for
example, e:/EC_Central_Folder.
The Grid Agent must have full control access to the Central File folder. The Host machine containing the
Central File folder must have a running LCM Service and the users must have read/write access to the Central
File folder location.
When you install EC Server, LCM Service extracts the default files to the CF folder upon installation.
1 Prepare the host machine to contain the Central File folder.
• Domain is accessible to the Grid Agent of the EC_Central node
• Has a running LCM Service
2 Access the host machine and create the central file folder.
For example, create e:/EC_Central_Folder
3 Set the user access rights to the Central File folder. Allow user read/write access.

Installing IEC Database

Use these guidelines to install a new EC database:
• If you will install the EC application for the first time, you must install the corresponding EC database in
LCM.
• If you are using a previous version of the EC application, you can proceed to upgrade to the latest version.
Before you can upgrade the installed EC application, you must first upgrade the EC database.
Use this procedure to install a new EC database:
Installing a new EC database - SQL Server

1 In the LCM Applications tab, select the Host > Database and expand the view of Microsoft SQL Server
where your <MSSQL instance> is installed.
2 Right-click <MSSQL instance> where to install EC database.
3 Select <MSSQL instance> > Install EC Database.
The Database server information window is displayed.
4 Specify the admin user and password to access the database server.
5 Click Next.
The EC Database Information window is displayed.
6 In the Database name field, specify a name for this installation.
7 In the Database user section, specify this information:
MEC Database user
Specify a database user name.
MEC Database user password

Specify a database user password. Retype to verify the password.
Note:
• Save the EC DB user information. Use the information when you install EC in Grid, upgrade EC
database, and to access this database.
• Do not use an already existing user account, you must create a new user account.
8 Click Next.
The Summary window is displayed. Review and verify the completeness of the information.
9 Click Finish to complete the installation.
When the task is finished, a message is displayed.
10 Click OK.
11 Optionally, access the log view to show the installation details.

Attaching IEC Database

This procedure applies only to previously installed EC Database. You must check the EC database version
before you attach an EC database.
Use these guidelines to attach EC Database:
• If you are installing the EC application for the first time, you must install the corresponding EC database,
see Installing IEC Database on page 87
• If you are using the classic version of EC and need to upgrade to a version that runs in Grid, you must first
attach the classic EC database, then upgrade the database in LCM.
Use the database set up in the new EC application in grid. Then, run Republish All and (Re)activate
mapping in the same way as you would apply a CCSS fix.
Use this procedure to attach EC Database:

1 In the LCM Applications tab, select and expand the view of Microsoft SQL Server where your <EC MSSQL
instance> is installed.
2 Right-click <MSSQL instance> where you need to attach your EC DB.
3 Select <MSSQL instance> > Infor Enterprise Collaborator <version> > Attach MEC Database > MEC<version>.
The EC Database server information window is displayed.
4 Specify the admin user and password to access the database server.
5 Click Next.
The EC Database server information window is displayed.
6 In the Database name list, select the EC Database that you want to attach.
7 Specify the EC database user and password to access the database server.
The view shows the Database Version to attach.
8 Click Next.
The Summary window is displayed. Review and verify the completeness of the information such as Admin
user, Database name, EC database user, and the database version to attach.
9 Click Finish to complete the installation.
When the task is finished, a message is displayed.
10 Click OK.
11 Optionally, access the log view to show the installation details.
Installing IEC in Infor ION Grid

Use this procedure to install Infor Enterprise Collaborator application in a grid for the first time. If you have
already installed a previous version of EC application in grid, proceed to upgrade to the latest available EC
version.
Note:
Install only one EC Server instance for every grid environment to avoid errors on duplicate installation.

Before you can install EC in a grid, you must complete these prerequisites:
• Set up Central File folder
• Install EC Database
• Provide the LCM service and Grid Agent users full access to the Central File folder.
• Select the latest version release of Infor ION Grid.
• Select a grid instance that contains the host to run MapGen and CentralFileSystem.
To verify, see the (Registry) list underneath Grid Host.
• Start and run the Grid. If not already started, EC deployment will wait for until Grid is started.
Use this procedure:

Installing IEC in Infor ION Grid
1 In LCM, select Actions > Install Product.
The Install window is displayed.
2 Select Infor Enterprise Collaborator <version> and click Next.
3 Select the grid instance where to install IEC.
4 Click Next.
The Application Name window is displayed.
Application Name
Specify a descriptive name for this grid application.
For example: EC Server
Description
Specify an optional brief description for this installation.
6 Click Next.
The Grid Host window is displayed. The grid default hosts are selected by default based on your installation
set up.
Note:
By default, EC_Process node will run on all Grid hosts.
7 On Grid Host window, specify this information:
MapGen Host
Select a host machine for the EC_MapGen Node.
By default, this hosts is automatically derived from your EC Server Host selection earlier.
EC_UI Host
Select a host machine for the EC_UI Host Node.

Central File Location Host

Select a host machine for the EC_Central Node.
Central File Path

Click Select to specify the complete path to the Central File folder location. The Central File is a local
folder in the Central File Location host machine.
Use the Central File folder remote file chooser.
a Select the location where you want to browse for the CF folder.
b Navigate to the CF folder path.
c Click OK to continue.
8 Click Next.
The Database information window is displayed.
Note:
Refer to your EC database set-up details.
9 On the Server information group, select the Database server that you defined earlier.
10 On the Database User Information group, type the database user and password that you defined earlier.
11 Click Next.
The M3 API Information window is displayed.
12 On Select M3 BE Environment, specify this information:
You can select to install the BE now or configure to use BE later.
BE Installation
Select the BE installation to use.
- Or -
Select Manual Configuration to perform BE configuration later.
BE Environment
Select the BE environment to use.
13 On the API Information group, specify this information:

Note:
If you are not prepared with the details to indicate in these fields, select Manual Configuration in the
previous step, then configure the BE and API later. Refer to movex.properties located in the actual BE
environment for the API details.
API Ref Name
Specify the API reference name.
API Port
By default, this field is auto-filled based on your selected BE Installation.

Host Name
Specify the host name of the BE Environment.
Note:
If you selected a BE Environment to use, this field will be auto-filled with a value corresponding to your
selected BE Environment.
User
Specify the username to access the BE Environment.
Password
Specify the password to access the BE Environment.
Encoding IANA
This is auto-filled.
Use Proxy
Select this to specify the proxy connection to use. You may need to use a proxy connection because of
firewalls and NATed networks settings.
Note:
This information specified in this API is the same as with the information in the Partner Admin M3 API
Communication fields. If changed, the values specified here will replace the values in the Partner Admin
M3 API Communication fields. The corresponding <APIMapper.mi.*properties>(application) is also
populated.
14 Click Next.
The Summary page is displayed.
15 Review the information and click Finish to complete the installation.
After you click Finish, LCM copies the EC Config files to the Central File Folder.
16 When the task is finished, successful installation dialog appears. Click OK or View log.
EC application is now installed in your selected grid node.
Verifying IEC Server installation

Use this procedure to verify the completeness of the EC installation.
Verifying IEC Server installation
1 In the Applications tab, select and expand the view of Space > Grid Application <version> where EC is
installed.
2 Right-click <Grid_Name> Grid Management Pages.
The Infor ION Grid Management Page window is displayed in the right pane.
3 Click the Topology view link.
If the view shows the Management pages tab, grid is properly started and running.

4 Verify that the status of these EC nodes are set to "OK".

When the installation tasks are completed and the Grid is running, EC Server is started along with these
components:
• EC_Central
• EC_MapGen
• EC_UI
• EC_Process
5 Close the Grid Management Pages.
Adding full control access to the Central File folder

After you install the EC application, you must set full access rights to the Central File folder for the Grid Agent
user.
Note:
EC does not control the logon for GridAgent. EC_ Central uses the Security context of the Grid Agent (By default
the user account is lcm) to access or modify the files under the CF folder.
Adding full control access to the Central File folder - SQL Server
1 Check that the LCM Service user on the Central File Location Host has read/write access to the Central
File folder.
2 Check the GridAgent logon where EC_Central Node must run.
Note:
To find the GridAgent Services, run services.msc from the command prompt.
GridAgent uses the format: Infor ION Grid Bootstrap - <Grid Name>
where <Grid Name> is the grid node where EC is installed.

3 Set the logon account access rights to the Central File folder.
For example:
Logon = Infor ION Grid Bootstrap - <Grid Name>
Access rights to "Infor ION Grid Bootstrap - <Grid Name> " enable full control.
Installing IEC Client tools

Download the Partner Admin, Flat File Definitions, and Business Document Mapper tools from M3 Core Options
or from M3 Core Infrastructure and Technology. For Business Document Mapper with restricted features, you
can only download from M3 Core Infrastructure and Technology.

Infor Enterprise Collaborator tools include a design studio where the mapping of business messages from
and to the M3 system is defined and maintained. The mapping of the business is a description of how an
arbitrary input XML schema is transformed into an output target XML schema, but with the graphical mapping
tool, developers can connect inbound with outbound messages and make integration simple.
Infor Enterprise Collaborator Tools - CCSS package

Immediately after installation of the IEC Tools package, retrieve the latest CCSS and upgrade the IEC Tools
installation through CCSS.
Installing Partner Admin tool

Use this procedure to install Partner Administration tool on a machine within the EC Server and EC Database
network.
1 Launch the PartnerAdmin<version> .msi file.
The setup window is displayed.
2 Select to install the Partner Admin tool. Click Next.
3 Click Next to accept the default destination folder installation.
4 Optionally, you can browse to another folder location for PA tool installation. Click OK.
5 Click Next to start the installation wizard.
6 Click Finish to complete the installation and close the Setup program.
Verifying Partner Admin tool installation

Use this procedure to verify the completeness of PA tool installation. You must have administrator rights to
be able to launch the PA tool.
1 Access Windows and select All Programs > Infor Enterprise Collaborator.
2 Launch Partner Administrator.
The Partner Administration Tool Security Login window is displayed.
3 Specify a username and password.
4 Click OK.
When you specify a username and password for the first time, a message shows that no key store file
exists.
Click OK to continue. The Partner Administration Tool Security Login window is displayed.
5 Specify a password for this username.
Confirm your password.
A key store file is created for this username and password. A message shows that you need to set up a
database connection.

6 Click OK.
If the Database settings window is displayed, PA tool is properly installed. You can now proceed to set
up a database connection. You find the jdbc url in EC administration in EC Application properties page.
Troubleshooting
You can experience issues and errors during the installation and setup of IEC client and server tools. Consult
these topics to solve these common issues.
MSMQ Error
The MSMQ error is an issue that develops if you do not have the correct MSMQ version installed. This error
will stop a channel from working and shows an error message:
An error occurred when opening queue: nlbavwm3e238\pubtqueuerec Channel will stop.
The stack text will show: com.intential.ec.communication.msmq.MSMQException: Make sure that a MSMQ is
installed in the host it will execute.
To address this issue, you must install the MSMQ Windows component. You can find the installation steps in
the MSMQIn topic under Polling type channel properties in the Infor Enterprise Collaborator Partner
Administration Tool User Guide.
Installing Business Document Mapper

The Business Document Mapper delivery includes these:
• The <mapper-base*win*>. zip file (32-bit or 64-bit)
This package includes an Eclipse environment and a JRE.

• The Mapper feature software
This package is included in the M3 Core Technology package.
Use these procedures to install Mapper.
Unzip Eclipse for Mapper

1 Copy the appropriate <mapper-base*win*>.zip file to the machine where Mapper should be installed.
2 Unpack the base zip file to a local folder on the machine.
This will be referred to as <MAPPER_ROOT> in the instructions here.

Install Mapper plugins through the LifeCycle Manager update site

1 Go to the LifeCycle Manager Server site, http://<LCMServer>:<LCMServer_http_port>
For example, http://10.20.30.40:4062
2 Click the link to "Update site for Eclipse based Infor products".
These are the information contained:
• Eclipse plugin site location
• Eclipse product repositories uploaded in LCM
3 Go to the <MAPPER_ROOT> folder and run mapper.exe

4 Select Help > Install new Software to display the Available Software window.
5 To install Mapper for the first time, click Add.
The Add Site window is displayed.
Name
Specify the tool name, for example, MAPPER_INSTALL
Location
Specify the Eclipse plugin site location obtained from step 2.
7 Click OK.
8 Select Infor Business Document Mapper and click Next.
The Install Details window is displayed.
9 Review the items to install and click Next.
10 On the Review License window, accept the license agreement and click Finish.
A progress window is displayed.
11 On the Software Update window, click Yes.
The Mapper files are now uploaded to Eclipse and the workbench is restarted. You can now proceed to
verify the installation.
To update an existing Mapper installation

1 Go to the <MAPPER_ROOT> folder and run mapper.exe
2 Select Help > Install new Software to display the Available Software window.
3 Click the "What is already installed" link.
The view shows the Installed Software tab by default.
4 Select all the Infor Business Document Mapper Features. Click Update.
The Update Details window is displayed.
5 Review and confirm the updates. Click Next.

Starting and verifying Business Document Mapper installation

Use this procedure to verify the completeness of Mapper installation.
Perform this verification procedure when Eclipse has restarted right after installation.
Starting and verifying Business Document Mapper installation
1 Start mapper.exe from the <MAPPER_ROOT> folder.
2 Verify that the "Mapping Development" perspective is displayed.
a Select Window > Open Perspective > Other.
b Double- click Mapping Development.
The user password window is displayed.
3 Specify a user password.
Installing Flat File Definition tool

1 Launch the FlatFileDefTool<version> .msi file.
The setup window is displayed.
2 Click Next.
3 Click Next to accept the default destination folder installation.
4 Optionally, you can browse to another FFD tool installation folder location.
5 Click Next to start the installation wizard.
6 Click Finish to complete the installation and close the Setup program.
Verifying Flat File Definition tool installation

Use this procedure to verify the completeness of Flat File Repository Manager tool installation. You must have
administrator rights to be able to launch FFD tool.
Note:
You can use the FFD tool offline and without a database connection. To be able to verify the completeness
of FFD installation, you must have a DB connection.
Verifying Flat File Definition tool installation
1 Access Windows and select All Programs > Infor Enterprise Collaborator.
2 Launch Flat File Repository Manager.
The Flat File Definition Tool Security Login window is displayed.
3 Specify a user name and password.
4 Click OK.

When you specify a username and password for the first time, a message shows that no key store file
exists for <username>.
Click OK to continue. The Flat File Definition Tool Security Login window is displayed.
5 Specify a password for this username. Confirm your password.
A key store file is created for this username and password.
6 Click OK.
7 Select Flat File Repository Manager.
The Flat File Repository Manager window is displayed.
The user interface of the Flat File Repository Manager has three panes providing three different views.
These panes are the Definitions in repository, Definitions from repository being edited, and the Local
definitions. The icon displayed in each pane indicates the status of the environment in which the user is
currently working.
Install M3 Financial Business Messages
Installing Financial Business Messages

Use the this procedure to install the M3 Financial Business Messages.
1 Extract the FBM zip file.
2 Open Eclipse mapper and select a workspace, and click OK.
3 Specify the Business Document Mapper Security Password.
4 Import mapping.
5 Publish the mapping.
6 Activate the mapping.
7 Connect the mapping to its corresponding Partner Agreement.
Note:
After FBM installation is completed, you must Deploy the mapping to the Mapper Server runtime environment.
Deployment is the process of publishing a mapping to a Mapper Server. The mappings are loaded into the
Mapper Sever and are ready to run after they have been activated or reactivated. Then, connect the published
mapping to its corresponding Partner agreement using the Partner Agreement Tool.
For more information, see these topics:
"Importing mappings", see Infor Document Mapper User Guide.
"Publishing mappings", see Infor Enterprise Collaborator Administration Guide.

Install M3 BOD Processor
Installing M3 BOD Processor

The M3 BOD Processor subscribes to events from Event Analytics, enhances, and publishes them through
Event Hub to IEC. The M3 BOD Processor processes BOD content based on rulespack archives that filter events
that are valid as BODs.
1 In LifeCycle Manager, select Actions> Install Product.
2 On the Install window, select the "M3 BODs 15.x.x" product and click Next.
3 On the Location window:
a Select the Grid instance where you want to install M3 BOD Processor.
Note:
You must install the product on the same Grid instance as M3 Core Infrastructure and Technology.
b Select an unoccupied HTTPS port number on the host.
c Select Validate SVCM3BOD user, and specify the name and the password for any MNS150 user to
complete the validation.
d If the M3 BE is not started, select the "Start M3 BE Environment" check box.
4 Click Next.
After installation, verify that the product is displayed in "Started" status in the list of Grid applications.
Install Workflow Executor

Use these instructions to install Workflow Executor.
Installing Workflow Executor

1 In LifeCycle Manager, select Actions> Install Product.
2 On the Install window, select the product version and click Next.
3 On the Grid Host window, select a grid host.
4 On the Summary dialog, click Finish.
After installation, verify that the product is displayed in status Started in the list of Grid applications.

Install M3 Adaptation Kit

Use these instructions to install M3 Adaptation Kit.
Installing M3 Adaptation Kit through LifeCycle Manager

Use these procedures to install M3 Adaptation Kit through the LifeCycle Manager.
Install M3 Adaptation Kit through the LifeCycle Manager update site
1 Go to the LifeCycle Manager Server site, http://<LCMServer>:<LCMServer_http_port>
For example, http://10.20.30.40:4062
2 Click the link to "Update site for Eclipse based Infor products".
You will be directed to http://<LCMServer>:<LCMServer_http_port>/eclipseproducts
The page contains the following information:
• Eclipse plugin site location
• Eclipse product repositories uploaded in LCM
3 Start Eclipse and select Help > Install New Software.

4 On the Available Software window, click Add.
5 On the Add Site window, provide the following details:
Name
Type the tool name, for example, MAK
Location
Type the Eclipse plugin site location obtained from step 2
Click OK.
6 On the Available Software window, do either of the following:
If you are doing a first-time installation: If you are updating an existing MAK installation:
a Select MAK Feature, MAK Help, and MAK SVN a Click the link to "What is already installed".
Team Support. Click Next. The Installed Software tab appears by default.
b On the Install Details window, review the b Select MAK Feature, MAK Help, and MAK SVN
items to be installed. Click Next. Team Support. Click Update.
c On the Update Details window, review and
confirm the updates. Click Next.
7 On the Review Licenses window, accept the license agreement and click Finish. A progress window
appears.
8 On the Certificate Selection window, select the Infor software certificate. Click OK.
9 On the Software Update window, click Yes.

The MAK files are now uploaded to Eclipse and the workbench is restarted. You can now proceed to verify
the installation.
Install M3 Metadata Publisher

Use these instructions to install M3 Metadata Publisher.
Installing M3 Metadata Publisher

Use this procedure to install the M3 Metadata Publisher application in a grid for the first time.
Note:
To use the installation wizards, the user running LCM Client must be a member of the LCM administrator’s
group.
1 Log on to LifeCycle Manager as administrator.
2 Select Actions > Install. The Install window is displayed.
3 From the list, select the M3 Metadata Publisher<version> and click Next.
4 On the Install window, select the grid on which MDP will be installed.
5 Click Next.
6 In the Install M3 Metadata Publisher Grid Host window, do this:
a Select an MDP Server Host to use, if not already selected.
b In the drop down lists, select an MDP Client Host and an MDP Index Host.
7 Click Next.
8 Select a database server. Your selection here must correspond to the platform where to install MDP.
9 Select a database task to perform. Depending on whether to use a new or an existing database, select
the appropriate task, see Selecting a database for MDP installation on page 101.
• Select Create new database to create a new database on your selected database server.
• Select Create schema in existing database if you need to create a schema in a database previously
created through Lifecycle Manager.
• Select Manual configuration of existing database to manually specify the location of an existing
database.
10 Click Next.
11 On the MDP database information window, confirm the MDP database information and specify login
credentials for the database admin.
12 In the Summary page, review and verify the completeness of the information. Click Finish to complete
the installation.
13 When the task is finished, a window indicating the successful installation is displayed. Click OK or click
View log.

The MDP application is now installed in grid. You can find it under the Space > Grid Applications node in the
Applications tab.
Selecting a database for MDP installation

Here are the available tasks to perform when you select a database to use for your MDP installation.
Creating a database
Use this procedure to create a new database on your selected database server.
1 Select Create new database and click Next.
Database
Specify the name of the database to create.
Schema
Optionally, specify the name of the database schema to create.

Specify the user with privileges to create the database.

specify the password for the administrator user.
New database user

Specify the user that will be created to run the grid database.
New database password

Specify the password you want to set for the grid database user.
Database location
Optionally, specify the path for the database.
Note: This field is available only if you selected an SQL Server, and if the database location for the API
setting is available in LCM, for example, latest LCM version. If left blank, the database is created in the
default path.
3 Confirm the new password and click Next.

4 On the summary page, review the information and click Finish to complete.

Creating a schema in an existing database

Use this procedure if you need to create a schema in a database previously created through Lifecycle Manager.
1 Select Create schema in existing database and click Next.
Existing database
Specify the database, previously created through Lifecycle Manager, where the new schema should
reside.
Schema
Specify the name of the database schema to create.

Specify the user with privileges to create the schema.

Specify the password for the administrator user.
JDBC user
Specify the JBDC user that will run the grid database.
JDBC password
Specify the password for the JDBC user.
Manually configuring an existing database

Use this procedure to manually specify the location of an existing database.
1 Select Manual configuration of existing database and click Next.
2 On the Use existing database window, specify this information:
Existing database
Specify the name of the database instance.
Schema
Specify the name of the database schema, if used.
JDBC user
Specify the JDBC user.
JDBC password
Specify the JDBC user's password.
JDBC URL
Specify the URL to connect to the database.
For example, for an SQL Server: jdbc:sqlserver:// host_fqdn:port; databaseName= yourDBname,instance=
instanceName.

Post M3 SW Component installation
Chapter 6: Post M3 SW Component installation
Post M3 SW Component installation

Before you continue with the Post M3 SW Component Installation tasks, you must update the M3 Core
Installation worksheet with applicable information from the installation phase.
Continue with the post-installation procedures outlined in the M3 Core Administration Guide.

AD LDS in LifeCycle Manager
Appendix A: AD LDS in LifeCycle Manager
This appendix contains information about AD LDS users and groups, user management permissions to the
LCMADAM instance, and configuration of the LCM server to use SSL.
AD LDS users and groups

LifeCycle Manager delivers a pre-configured AD LDS (Active Directory Lightweight Directory Services) solution
in the LifeCycle Manager Server installation to simplify the LDAP setup.
Five user accounts and two groups are created during LifeCycle Manager Server installation if AD LDS is chosen
as the LDAP strategy. After the LifeCycle Manager Server installation is finished, use Windows Services console
to verify that the LCMADAM service is running.
These users and groups are created:
Users
admin Has all permissions to administer the LCMADAM instance
binduser Use this account to bind to the LCMADAM instance
LCMAdmin Use this account to administer LifeCycle Manager
LCMProduser Use this account to administer a product in LifeCycle Manager (Product User)
LCMViewer Use this account to view status of products installed in LifeCycle Manager
Groups
LCMAdmins Consists of one user account - LCMAdmin
LCMProd Consists of one user account - LCMProduser
The users created during the AD LDS instance installation have the default password ChangeMe123. This
password should be reset.

Adding a user to LCMAdmins group

1 Start a command prompt console.
2 Navigate to this directory: LCMInstallDir\LCM-Server\adam\manage.
3 Run the script new_lcmadmin.cmd name_of_new_user.
The user created will have the default password ChangeMe123. This password should be reset.
Creating a new user group in AD LDS

2 Navigate to the following directory: LCMInstallDir\LCM-Server\adam\manage.
3 Run the script new_group.cmd name_of_new_group.
Creating a new user and adding the user to an existing user group
in AD LDS
2 Navigate to the following directory: LCMInstallDir\LCM-Server\adam\manage.
3 Run the script new_lcmuser.cmd name_of_new_user name_of_LCMgroup.
Changing password using ADAM ADSI tool

1 Select Start > Run and specify adsiedit.msc to start the ADSI Edit tool.
Note: The ADSI Edit tool is included when installing the AD LDS Snap-Ins and Command-Line Tools
feature.
2 Select Action > Connect to....
3 Specify a name for the connection.
4 Select the Select or type a Distinguished Name or Naming Context radio button and specify
dc=lcmadam,dc=net.
5 Select the Select or type a domain or server radio button and specify the Server IP address.
6 Click OK.
7 In the left pane, expand The connection name > dc=lcmadam,dc=net.
8 Click OU=LCM.
9 Right-click on a user and select Reset Password. Ensure to use complex passwords.
Note: The password cannot end with @. The password for binduser in the file lcm.properties must be
updated when password is changed (ldap.bind.password.0=). The password will be encrypted the next
time the LifeCycle Manager Server is restarted.

Adding user management permissions to the LCMADAM

instance
Full access to all AD LDS partitions created during LifeCycle Manager server installation is by default restricted
to the user who installed the LifeCycle Manager server. Therefore, by default, only this user has permissions
to create new users and groups in the LCMADAM instance.
If for some reason the original install user cannot log into the server, the LCMADAM instance cannot be
managed. We recommend that you grant this permission to other users.
1 Log in to the LifeCycle Manager server machine using the same account which installed LifeCycle Manager.
2 Run ADSI Edit.
3 Click Action > Cconnect to.
4 Connect to Configuration Naming Context.
5 In the left pane, expand Configuration->CN=Configuration,CN=…->CN=Roles.

6 In the right pane, double click CN=Administrators.
7 Scroll down to the member attribute and click Edit.
8 Click Add Windows Account.
9 Specify the groups or users you want to have permissions to manage the LCMADAM instance.
10 Click OK twice.
11 Exit ADSI Edit tool.
12 Restart the LCMADAM Windows service.
13 Restart the LCM Server service.

Configuring LCM Server to use SSL for AD LDS

Use this procedure to configure SSL for AD LDS. This procedure is an example of requesting and installing a
server certificate from a Certificate Authority configured on MS Windows 2008.
Ensure that the CA website is configured to use SSL.
You have to obtain a certificate for the server hosting an AD LDS instance before configuring the instance to
use LDAPs. The certificate must be issued for server authentication.
Enabling SSL on AD LDS

Follow the steps described in http://technet.microsoft.com/en-us/library/cc725767(WS.10).aspx to enable
SSL on AD LDS.
Validating LDAPs to access AD LDS

1 Use a LDAP browser, for example ldp.exe.
Note: You have to enable the AD LDS Snap-Ins and Command-Line Tools feature to be able to run ldp.
2 Connect and bind to AD LDS using port 636 and SSL.
Importing CA certificate to a LifeCycle Manager keystore

The CA certificate must be imported before LDAPs are enabled for communication between AD LDS and the
LifeCycle Manager Server and AD LDS.
1 Verify that the folder for the keystore exists.
2 Create the keystore and import the CA certificate.
For example, use this commend: D:\<path to jdk>\bin>keytool -import -file c:/dc5.cer -keystore
"D:\Infor\LifeCycle Manager\LCM-Server\adam\ADAM_SSL/dc5" - storepass ChangeMe123 -storetype
jks.
You must replace ChangeMe123 with your password.

Note: The Trust store password cannot end with @.
3 Edit these parameters in the lcm.properties file. The passwords for bind user and trust store will be
encrypted the next time the LifeCycle Manager Server is restarted.
# LDAP configurations
ldap.validation=true
ldap.server.0=seliw031.infor.com
ldap.port.0=636
ldap.bind.user.0=cn=binduser,ou=lcm,dc=lcmadam,dc=net
ldap.bind.password.0=##01WQ8/QAEA0iSnuVPKMIpkRQ==
ldap.ssl.enabled.0=true

ldap.trust.store=D:/Infor/LifeCycle Manager/LCM-Server/adam/ADAM_SSL/dc5
ldap.trust.store.password=
Validating LDAPs to access AD LDS instance

1 Run an LDAP browser. For example, ldp installed with AD LDS.
2 Connect and bind to AD LDS using port 636 and SSL.

Security
Appendix B: Security
This appendix presents some important security notes regarding hardware and operating environment
security. The appendix does not, by far, provide a full coverage of all security issues that might be considered.
Caution:
It is highly recommended to disable the Windows Guest account, if this has not already been done.
Securing Access to M3 BE
M3 BE can be accessed and managed by a variety of applications. Some of them like Infor Smart Office provide
user authentication but some like MI or BCI (Business Component Interface) do not include this functionality.
M3BE is installed as a Grid-enabled application, which means that the application uses Grid Session Providers
to authenticate users.
Setting up Trust Between External Applications and M3

BE
M3 Business Engine and its client applications can be set up to run trusted connections over the MI socket
protocol. When a trusted connection is used, the client is responsible for authenticating users, and no user
credentials need be transmitted to M3 BE. The connection must be configured for client-authenticated SSL,
and the certificate in the client keystore must be generated with the role run-as-m3user.
Configuring client-authenticated SSL MI ports

By default, M3 BE is configured with a secure MI port on the grid M3Router. This is a secured connection
dispatcher, denoted by a padlock symbol in the grid Management UI. If you add your own connection
dispatchers to use for trusted connections, these must be set up with one of these authentication types:
• Clients may authenticate with certificate
or
• Clients must authenticate with certificate

Security
Generating a client keystore

How to generate a client keystore for connections to a specific grid is described in Infor ION Grid Security
Administration Guide, section "Creating an SSL Client Keystore in ION Grid for LifeCycle Manager".
Note:
To set up a trusted connection, the role list entered in the Create Client Keystore window must include the
role <M3 BE deployed application name>/run-as-m3user.
Securing M3 BE Installation Folder

The folder containing M3 Business Engine files should be additionally secured by changing the default NTFs
permissions. In case M3 Adaptation Kit (MAK) is used to perform changes and to troubleshoot M3 BE, some
additional changes to NTFS permissions are required, unless MAK users are members of the local administrators
group.
Infor provides a group M3_MAK_Group which is automatically created. Make sure that M3 Adaptation Kit
users are included in this group.
Infor also provides a group M3_Grid_Group which is automatically created. When installing an M3 BE
environment, the Infor ION Grid user is automatically included in this group.
Securing M3 BE Installation Folder
1 NTFS permissions on the M3 Business Engine installation folder are inherited from the M3 BE installation
drive.
During the installation of an M3 BE Environment, these permissions are added to the specified folders:
Folder M3_MAK_Group M3_Grid_Group

<M3BE_inst_folder> Read Modify
<M3BE_inst_folder>\_db_data Modify Inherited from parent
object
<M3BE_inst_folder>\env\<env_name>\Fix Modify Inherited from parent
object
2 If applicable, ensure that M3 Adaptation Kit users are included in the group M3_MAK_Group.

Security
Security issues
Restrict physical access

One of the risks of unauthorized physical access is the ability by an intruder to start the server from a memory
stick, CD/DVD or floppy disk and gain access to the Windows file system. Your mission-critical production
application and database servers should be physically secured.
Recommendation:
As with any Windows based server, it is recommended to restrict physical access whenever possible.
Backup
Backup means not only backing up data on disks. Backup also means verifying that backup media contains
valid data that can be used to restore the system, as well as providing replacement parts for disks, power
supplies, software disk media etc.
Note: Do not schedule any batch jobs in M3 Business Engine during the backup of the entire database!
Recommendations:
Backup of disk data is utterly important. Make sure you have understood the backup needs of SQL Server
databases, for more information, see M3 Business Engine and Microsoft SQL Server - Best Practices (SQL Server
BPG) on KB 2212202. You must also define a backup and recovery plan, and practice recovery from backed
up files.
Also ensure that you have fast access to spare parts like disks.
Passwords
All passwords in Windows and SQL Server must be hard to crack.
Suggestions for stronger passwords in Windows and SQL Server:
• Do not use known words or user names in your password
• Include special characters (!@#$%*) and numbers in your password
• To really increase password strength, use a non-printable ASCII character. I.e. within the password,
'secret' embed an alt character secret where you hold down the ALT key while pressing the 1,2 and 9 keys
on the numeric keypad.
Note:
For laptop users, you will have to activate NUMLOCK and use the j, k, l, u, i, o keys that correspond to the
numeric keypad.

Security
Note:
If you have an account called 'test' and it is an administrator level account, do not use the password 'test'.
For more details read: http://technet.microsoft.com/en-us/library/cc783860.aspx
Perimeter defense
Recommendations
Place the M3 Business Engine Application server and SQL Server machine behind a firewall to reduce security
vulnerability.
Open the following ports on the firewall

M3BE application server
When installing an M3 Business Engine environment, the following Firewall Inbound Rules are automatically
created for that environment:
• <BE_env_name> BCI
• <BE_env_name> EXT
• <BE_env_name> HTTP
• <BE_env_name> HTTPs
• <BE_env_name> ME
• <BE_env_name> MEs
• <BE_env_name> MI
• <BE_env_name> MIs
• <BE_env_name> PROXY
SQL server network ports – TCP

• Default instance: 1433 -1434
• Named instance: the port number selected when creating the instance.
Windows firewall
The latest MS Windows OS versions are delivered with enabled Firewall. There are two ways to handle this
situation; either disable Windows Firewall or create Inbound Rules that allow client applications to connect
to M3BE. When Windows built-in firewall is enabled on your M3 Business Engine application server, you must
create exceptions that allow access to ports listed above.

Security
Firewall rules can be created in two ways, by allowing access to ports opened by a process or by opening
explicit network ports. To create a firewall rule that allows network access to explicit ports use the following
command (this example is valid for Windows 2008 R2):
netsh advfirewall firewall add rule name="<name>"

dir=in action=allow protocol=TCP localport=<port>
For considerations about firewall installed on SQL Server, see M3 Business Engine and Microsoft SQL Server -
Best Practices" (SQL Server BPG) on KB 2212202.
Antivirus program considerations

Some Antivirus programs block access to ports known to be used by some applications to compromise your
system. For example MacAfee has a rule called "Prevent IRC communication" that blocks access to ports
6666-6669. If this rule is enabled, and if M3 Business Engine environment uses any of these ports, either disable
the rule or exclude the following processes from the rule:
On the M3 BE server: java.exe
On the administrative client: java.exe and Lifecycle Manager.exe.
For considerations regarding antivirus program installed on SQL Server, see M3 Business Engine and Microsoft
SQL Server - Best Practices" (SQL Server BPG) on KB 2212202.

M3coretech 13.4.0 M3coreig Windows En-Us

Uploaded by

Copyright:

Available Formats

M3coretech 13.4.0 M3coreig Windows En-Us

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M3coretech 13.4.0 M3coreig Windows En-Us

Uploaded by

Copyright:

Available Formats

M3 Core Installation Guide -

Chapter 1: Introduction and overview...........................................................................................9

M3 Core Installation Guide - Windows | 3

Obtaining an SSL certificate........................................................................................................................26

M3 Core Installation Guide - Windows | 4

Install M3 Business Engine layouts..................................................................................................................55

M3 Core Installation Guide - Windows | 5

M3 Core Installation Guide - Windows | 6

Post M3 SW Component installation.............................................................................................................103

M3 Core Installation Guide - Windows | 7

Part Number Release Date Description

M3 Core Installation Guide - Windows | 8

Chapter 1: Introduction and overview

M3 Core Installation Guide - Windows | 9

The Installation guide is the second in a set of three guides:

Handover from installation planning

M3 Core Installation Guide - Windows | 10

M3 Core Installation Guide - Windows | 11

Chapter 2: Installing and preparing LifeCycle Manager

Installing a LifeCycle Manager Server

Preparing for installation

Installing a LifeCycle Manager Server

M3 Core Installation Guide - Windows | 12

Backup user password

M3 Core Installation Guide - Windows | 13

Day of week to run backup

Time to start backup

Remove backup after following number of days

Completing the installation using a manual LDAP

Bind user (distinguished name)

Bind user password

M3 Core Installation Guide - Windows | 14

Trust store password

Retype Trust store password

Group member attribute

User search filter

Group search filter

LCM admin group

M3 Core Installation Guide - Windows | 15

LCM user group

Service account password

b Specify this information:

Service account password

7 Click Next twice to initialize the installation.

Completing the installation using a pre-configured AD LDS

M3 Core Installation Guide - Windows | 16

3 Perform one of these options:

Service account password

b Specify this information:

Service account password

4 Click Next twice to initialize the installation.

Installing LifeCycle Manager Services

LifeCycle Manager Service installation considerations

M3 Core Installation Guide - Windows | 17

Installing a LifeCycle Manager Service on Windows

7 Specify this information:

LCM Server port

LCM Server Admin

LCM Server Admin Password