Install a LifeCycle Manager Server

Open a command prompt.

If you are not using the Windows built-in local Administrator account and User Account Control (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.

Navigate to the directory where the .jar file is located.

Run the command to start the installation of the LCM Server.

If no default Java is installed, you must enter the full path to Java in the bin directory of the Java JDK installation. For example, run the following command and press Enter:

"C:\<path to jdk>\bin\java" -jar LifeCycleManagerServer_10.1.x.x.jar

The LifeCycle Manager Server Setup window is displayed.

Click Next.

Select to Install a new server.

Click Next. The Destination Folder window is displayed.

Select the destination folder or browse to another location. Make sure that the selected destination folder does not contain
any folder named LCM-Server.

Click Next. The Java Virtual Machine window is displayed.

Select the path or browse to another location for the Java JDK installation to use for the LifeCycle Manager Server.

Click Next. The Server Settings window is displayed.

Provide the necessary information. Consider the following fields:

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, be sure 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 type a base port number for a range of four ports that will be used for
LifeCycle Manager Server communication.

Click Next. The Backup Routines window is displayed.

Provide necessary information to set up the backup
strategy for the LifeCycle Manager Server. Consider the following
fields:

Note:

It is extremely vital that 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.properties, see LifeCycle Manager Administration Guide available on the Infor Xtreme Download record for LifeCycle Manager.

Backup path

Type the destination where the backup should be placed. Type
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:

Make sure that the server used for backup of LifeCycle Manager Server is frequently backed up. Infor recommends to use a server
that is frequently backed up, for example the M3 Home server or the M3 Database server (if applicable).

Backup user

Type 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, then you must
type Domain\User. If the backup server is not
a member of a domain, then you must type Server\User .

Backup user password

Type 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 if you want backups to be deleted after the
number of days you have typed (default is to never remove the backup).

Click Next. The LDAP Configuration window
is displayed prompting you to select whether to use Manual configure
for a central LDAP server or a Preconfigured Active Directory Lightweight Directory Services (AD LDS) instance.