On Boarding Overview - Revision history

Olibouban at 17:22, 20 March 2024

2024-03-20T17:22:35Z

← Older revision		Revision as of 17:22, 20 March 2024
Line 1:		Line 1:
			= OBSOLETE =

	== Introduction ==		== Introduction ==

Rdaly: /* Configuring the E-mail notification */

2019-12-23T22:53:50Z

Configuring the E-mail notification

← Older revision		Revision as of 22:53, 23 December 2019
Line 21:		Line 21:
	# Scroll down to '''E-mail Notification'''. Here is a sample configuration for guidance.		# Scroll down to '''E-mail Notification'''. Here is a sample configuration for guidance.

	[[File:Correct-~~mail~~-config-1.png\|700px]]		[[File:Correct-email-config-1.png\|700px]]

	== Groups ==		== Groups ==

Rdaly: /* Introduction */

2019-12-23T22:52:11Z

Introduction

← Older revision		Revision as of 22:52, 23 December 2019
Line 21:		Line 21:
	# Scroll down to '''E-mail Notification'''. Here is a sample configuration for guidance.		# Scroll down to '''E-mail Notification'''. Here is a sample configuration for guidance.

	[[File:~~correct~~-mail-config-1.png\|700px]]		[[File:Correct-mail-config-1.png\|700px]]

	== Groups ==		== Groups ==

Rdaly: /* Configuring the E-mail notification */

2019-12-23T22:51:07Z

Configuring the E-mail notification

← Older revision		Revision as of 22:51, 23 December 2019
Line 18:		Line 18:
	To avoid an error message in the LicenseExpiration job, set up the E-mail notification in Jenkins.		To avoid an error message in the LicenseExpiration job, set up the E-mail notification in Jenkins.

	In Jenkins select '''Manage Jenkins''' and '''Configure System'''.		# In Jenkins select '''Manage Jenkins''' and '''Configure System'''.
	Scroll down to E-mail Notification.		# Scroll down to '''E-mail Notification'''. Here is a sample configuration for guidance.


			[[File:correct-mail-config-1.png\|700px]]

	== Groups ==		== Groups ==

Rdaly at 22:49, 23 December 2019

2019-12-23T22:49:35Z

← Older revision		Revision as of 22:49, 23 December 2019
Line 13:		Line 13:

	In Jenkins and on the Dashboard, the Lingoport project will be referred to as '''<group name>.<project name>'''. For example given a group called "Acme" and a software project called "Weather", Jenkins and Dashboard will refer to it as '''Acme.Weather'''		In Jenkins and on the Dashboard, the Lingoport project will be referred to as '''<group name>.<project name>'''. For example given a group called "Acme" and a software project called "Weather", Jenkins and Dashboard will refer to it as '''Acme.Weather'''

			=== Configuring the E-mail notification ===

			To avoid an error message in the LicenseExpiration job, set up the E-mail notification in Jenkins.

			In Jenkins select '''Manage Jenkins''' and '''Configure System'''.
			Scroll down to E-mail Notification.



	== Groups ==		== Groups ==

Rdaly: /* Groups */

2019-12-13T18:41:29Z

Groups

← Older revision		Revision as of 18:41, 13 December 2019
Line 34:		Line 34:
	[[File:ManageLicenses.PNG\|700px]]		[[File:ManageLicenses.PNG\|700px]]


	~~==== Command Line Equivalent ====~~
	~~'''Using the command line is not recommended. Work with Jenkins and its jobs, whenever possible.'''~~
	If you'd rather use the command line instead of the Jenkins ManageLicenses job, for instance in a script, use the <code>--create-group</code> command on lrm-cli.jar command line. Using the command line is not recommende. The ManageLicenses Jenkins job is more reliable. You need to have requested a license key for the new group from Lingoport before creating the group. For instance:

	~~> java -jar $LRM_HOME/lrm-cli.jar --create-group --group-name group1 --date "2016-06-01" --number-of-licenses 10 --license-key <license-key>~~

	To update the license of an existing group, used the <code>--update-license</code> command on lrm-cli.jar command line. You need to have requested a license key for the new group from Lingoport before updating the group.For instance:

	~~> java -jar $LRM_HOME/lrm-cli.jar --update-license --group-name group1 --date "2016-06-01" -number-of-licenses 10 --license-key <license-key>~~

	~~Once a group has been created, the database and the file structure are updated. The Jenkins LicenseExpiration job should show the change to the license.~~

	=== Creating a new LicenseExpiration job for a new group ===		=== Creating a new LicenseExpiration job for a new group ===

Rdaly at 18:40, 13 December 2019

2019-12-13T18:40:54Z

← Older revision		Revision as of 18:40, 13 December 2019
Line 120:		Line 120:

	== Next Step ==		== Next Step ==
	[[~~Before~~ On-Boarding]]
			The next step is to do the actual on boarding. Select the link below that describes your situation.

			*[[On Boarding an LRM Project]]
			*[[On Boarding a Globalyzer Project]]
			*[[On Boarding a project with both LRM and Globalyzer]]

Rdaly: /* Command Line Equivalent */

2019-12-10T21:39:01Z

Command Line Equivalent

← Older revision		Revision as of 21:39, 10 December 2019
Line 36:		Line 36:

	==== Command Line Equivalent ====		==== Command Line Equivalent ====
			'''Using the command line is not recommended. Work with Jenkins and its jobs, whenever possible.'''
	If you'd rather use the command line instead of the Jenkins ManageLicenses job, for instance in a script, use the <code>--create-group</code> command on lrm-cli.jar command line. Using the command line is not recommende. The ManageLicenses Jenkins job is more reliable. You need to have requested a license key for the new group from Lingoport before creating the group. For instance:		If you'd rather use the command line instead of the Jenkins ManageLicenses job, for instance in a script, use the <code>--create-group</code> command on lrm-cli.jar command line. Using the command line is not recommende. The ManageLicenses Jenkins job is more reliable. You need to have requested a license key for the new group from Lingoport before creating the group. For instance:

Rdaly: /* Adding a new LRM License/Group */

2019-12-10T21:37:12Z

Adding a new LRM License/Group

← Older revision		Revision as of 21:37, 10 December 2019
Line 29:		Line 29:
	LRM projects are associated with a group. If LRM is installed without the Stack Installer (not recommended), the installer requires at least one group and its license. The license for a group is obtained from support@lingoport.com based on the commercial agreement between the client and Lingoport. Each project within a group must have a unique name.		LRM projects are associated with a group. If LRM is installed without the Stack Installer (not recommended), the installer requires at least one group and its license. The license for a group is obtained from support@lingoport.com based on the commercial agreement between the client and Lingoport. Each project within a group must have a unique name.

	=== Adding a new LRM License/Group ===		=== Adding or updating a new LRM License/Group ===
	To add new groups after installing the system, contact Lingoport and arrange for a new group. Lingoport will provide a license key for a given number of projects. The ManageLicenses job can also be used to update an existing or expired license. With the new license information, execute the ManageLicenses Jenkins job:		To add new groups after installing the system, contact Lingoport and arrange for a new group. Lingoport will provide a license key for a given number of projects. The '''ManageLicenses''' job can also be used to update an existing or expired license. With the new license information, execute the ManageLicenses Jenkins job:

	[[File:ManageLicenses.PNG\|700px]]		[[File:ManageLicenses.PNG\|700px]]

Rdaly: /* LicenseExpiration Jenkins jobs */

2019-12-10T21:36:02Z

LicenseExpiration Jenkins jobs

← Older revision		Revision as of 21:36, 10 December 2019
Line 25:		Line 25:
	In the illustration above, the group is '''Acme'''. Select the job (Acme.LicenseExpiration). Select '''Build Now''' from the left side menu to run the Jenkins job. Once it has built, select the top sphere under Build History. If the sphere is red, there is a problem with the license. This will bring you to Console Output. The console output shows when the license expires for group Acme as well as the versions of the Lingoport components and other system information.		In the illustration above, the group is '''Acme'''. Select the job (Acme.LicenseExpiration). Select '''Build Now''' from the left side menu to run the Jenkins job. Once it has built, select the top sphere under Build History. If the sphere is red, there is a problem with the license. This will bring you to Console Output. The console output shows when the license expires for group Acme as well as the versions of the Lingoport components and other system information.

	The [[Terms_and_Definitions#LRMProject\|projects]] under one group get the group's defaults for the associated translation system. So if a group's configuration is set up for an SFTP communication with a TMS for instance, all projects under that group will by default use the same mechanisms (that SFTP) with the same settings unless explicitly changed.		The [[Terms_and_Definitions#LRMProject\|projects]] under one group can get the group's defaults for the associated translation system. So if a group's configuration is set up for an SFTP communication with a TMS for instance, all projects under that group will by default use the same mechanisms (that SFTP) with the same settings unless explicitly changed. This can be changed to a project by project basis if desired.

	LRM projects are associated with a group. If LRM is installed without the Stack Installer (not recommended), the installer requires at least one group and its license. The license for a group is obtained from support@lingoport.com based on the commercial agreement between the client and Lingoport. Each project within a group must have a unique name.		LRM projects are associated with a group. If LRM is installed without the Stack Installer (not recommended), the installer requires at least one group and its license. The license for a group is obtained from support@lingoport.com based on the commercial agreement between the client and Lingoport. Each project within a group must have a unique name.