M.App Enterprise Tutorials

Not sure on how to get started or looking for a workflow to get M.App Enterprise up and running. Tutorials provide step by instruction on some of the most common configurations and workflows to get M.App Enterprise configured up and running quickly.
Showing results for 
Search instead for 
Do you mean 

Installing Luciad Fusion for M.App Enterprise

by Technical Evangelist ‎10-02-2019 03:50 AM - edited ‎10-21-2019 03:22 AM (3,414 Views)

This article gives you some information about the installation of Luciad Fusion, which is integrated with the release of M.App Enterprise 2019. 

 

 

Note: We strongly recommend to install Luciad Fusion on a seperate server. 

 

Note: For the storage of the metadata you will need to create an empty database before installing Luciad Fusion. The database providers are the same as they are in M.App Enterprise (Oracle, SQLServer and PostgreSQL). 

 

Note: A Warehouse user must be created before installing Luciad Fusion. It is the same procedure as it is for M.App Enterprise. If there is a shared Warehouse between Luciad Fusion and MAE, please ensure that this Warehouse user is allowed to write to the folder. 

 

 

Step 1: Defining a Server Port on the Luciad Fusion server

 

 luciad_1.png

 

Because you have to use Luciad Fusion with a valid SSL certificate you have to put in 443 as a Server Port.

 

 

 

Step 2: Defining the connection to the M.App Enterprise server

 

luciad_2.png

 

Because the Public Server Name and the Server Name respectively IP Adress can be different at your configuration.

 

Note: As the Warehouse Location we strongly recommend the same as you had for M.App Enterprise.

 

 

Step 3: Warehouse User

luciad_3.png

Note: The Warehouse user must be same on the M.App Enterprise application server and the Luciad Fusion Server, if the Warehouse of Luciad Fusion is in the MAE Warehouse (= what we strongly recommend).

 

 

Step 4: Database connections for metadata tables

 

Three database providers are available for Luciad Fusion. Oracle, Microsoft SQLServer and PostgreSQL.

 

Note: Please don't combine any M.App Enterprise DB (Master or Tenant) with the Luciad Fusion database.

 

luciad_4_oracle.png

luciad_4_postgres.png

luciad_4_sqlserver.png

 

 

Note: If you want to use SQLServer as your Luciad Fusion database, you have to create a new user there.

 

# Example SQL Server SQL for creating a database named luciad and user luciad:
## Create database
CREATE DATABASE [luciad]
ALTER DATABASE [luciad] SET READ_COMMITTED_SNAPSHOT ON

## Create user
USE [master]
CREATE LOGIN [luciad] WITH PASSWORD=N'luciad', DEFAULT_DATABASE=[luciad], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
ALTER SERVER ROLE [dbcreator] ADD MEMBER [luciad]
USE [luciad]
CREATE USER [luciad] FOR LOGIN [luciad]
ALTER ROLE [db_owner] ADD MEMBER [luciad]

 

 

Configuration of a valid SSL certificate on the Fusion Server:

 

You have to copy the following code snippet into application-fusion.production.yml (there is a section called server. already in there):

 

# SSL (https) can be enabled by setting the following properties:

# server.ssl.key-store: classpath:keystore.p12

# server.ssl.key-store-password: <password>

# server.ssl.keyStoreType: <type>

# server.ssl.keyAlias: <alias>

 

 

Fusion & MAE on the same server:

 

We can not outline it often enough. THIS IS NOT THE WAY IT IS MEANT TO BE, but here are some tips / checks if there is no other way than installing Luciad Fusion on the same server than MAE. 

 

Note: Don't be suprised if the performance drops if you are using Luciad Fusion & MAE on the same server.

 

  1. Fusion Studio must run on another port than MAE (e.g. 444 for https:// or 81 for http://)
  2. Define the correct URL in the MAE installation process (http(s)://SERVERNAME:PORT)
  3. Fusion is basically up and running (e.g. check if a logs folder and the log file gets created in INSTALLDIR\logs\fusion.log or check if the Luciad Fusion DB gets created)
  4. If you change the URL of the Fusion Server after installing MAE, please restart the M.App service
  5. If you are using the self-signed certificate of MAE, you have to change in application-fusion.production.yml the authServiceUrl from https://servernamen/api/v1/oauth2 to http://localhost/api/v1/oauth2

 

 

Fusion already installed and want to be used in MAE 

NOTE: At your own risk, you can try inserting the following snippet

 

 

1.) Backup application-fusion-production.yml file

2.) Put in the following code snippet:

 authenticationTypes:

- mappent

mappEnterprise:

authServiceUrl: http://MAE_SERVERNAME/api/v1/oauth2

clientId: Studio

secret:

 

 

 

Comments
by
‎10-11-2019 02:21 AM - edited ‎10-11-2019 03:10 AM

Hi Stefan,

I have followed the instructions and luciad Fusion has been installed successfully (almost). However, I can't start the LuciadFusionServer (under Services or via StartFusionPlatformServer.bat) and receive the error in the eventviewer saying 'Child process [6376 - C:\Program Files\Hexagon\LuciadFusion\StartFusionPlatformServer.bat -Dlcd.license.server=148.53.0.193:42000] finished with 1'.

 

So it seems like there is something wrong with the configured license server. There I have put the IP-adress of the computer that is shown within the error message (MAE and Fusion running on the same machine). also I have checked the bindings in IIS for 443.

We are using a self signed certificate - as with MAE. The MAE-pro license has been uploaded in the management.

 

Do you got some inputs what could be wrong?

 

Thanks and regards,

Hella

by Technical Evangelist
on ‎10-15-2019 12:27 AM

As it turned out the heap size was wrongly set in the Java environment. An update was done to OpenJDK 13 and now it is working without any issues. 

by
on ‎11-01-2019 04:52 AM

Hi Stefan, do you know, if there is any documentation for Luciad Fusion for M.App installation? What all Prerequisites is need? (eg. java is not mentioned in the M.App enterprise download page.... ).

Many thanks

Jan

by
on ‎11-05-2019 02:10 PM

Hola

 

He intentado seguir los pasos pero no termina la instalación debido a un error

Overview
Contributors