GeneXus M Installation Steps

Official Content
This documentation is valid for:

GeneXus M has several components that allow software development using a distributed architecture.

The following image shows four components and how they interact. Note that they can be installed in three different machines.

GeneXusMArchitecture_png

So these are the Setups to install

  • On Server 1
    • GeneXus Server: For authentication & authorization, SCM, etc
  • On Server 2 
    • GeneXus M Services: This is the services layer that the IDE interacts with 
    • GeneXus: Its business layer (BL) does tasks like build, run, among others, that the GeneXus M Services require
  • By each Developer
    • The IDE: This is lightweight and multi-platform, it has to be installed on the developer's machine

Note that Server 1 and Server 2 could be the same machine. They are handled separated in this article just for remarking the possibility to distribute those components and how to do so if you need.

Installation Steps

Installation Steps for the Server-Side

On Server 1

  1. Check GeneXus Server Requirements
  2. Download "GeneXus Server" from https://www.genexus.com/betatesters
  3. Install GeneXus Server (ref: GeneXus Server Installation Manual
  4. Authorize it with Beta keys
  5. Create a user for each developer (IDE)

On Server 2

  1. Check GeneXus 16 hardware and software requirements
  2. Download "GeneXus Setup" or "GeneXus Zip File" from https://www.genexus.com/betatesters
  3. Install GeneXus and get (Beta) keys
  4. Download "GeneXus M Services" from https://www.genexus.com/betatesters
  5. Unzip it
  6. Create or Edit LocalSettings.json of the "GeneXus M Services" installation (Follow instructions from below)
  7. Open the TCP and UDP Port set in the ServicesPort field of the LocalSettings.json so that GeneXus M Services can communicate with the IDEs and Server 1
  8. Open the TCP Port 30100 so that the IDEs can access it for Live Editing (ref.:Live Editing - under the hood )
  9. Start run.bat of the "GeneXus M Services" installation (from a privileged command prompt)

Installation Steps for the Client-Side (IDE)

  1. Download the "GeneXus M" for your platform (Linux, Mac or Windows) from https://www.genexus.com/betatesters
  2. Check Software and Hardware Requirements
    1. Supported operating systems
      • OS X 10.8 or later
      • Windows 7 or later (64bits)
      • Ubuntu Linux (64bits)
    2. Hard disk: Minimum of 400MB of space for the installation
    3. Memory: Minimum of 4GB required
  3. Unzip it to a specific folder
  4. Start GeneXus M and set the following
    1. Server URI: The URL of the GeneXus Server
    2. User & Password: Credentials to log in to that GeneXus Server

LocalSettings.json

Fields specification

  • GenexusBLBasePath: Absolute path of GeneXus installation (ie: "C:\\Program Files (x86)\\GeneXus\\GeneXusBeta")
  • ProjectsFolder: Absolute path where KBs are stored
  • SqlServerDefaultInstance: Name of the SQL Server instance where the KBs are stored. It also sets the default Environment's Data Store Server Name Property
  • SqlUserName and SqlUserPassword: Credentials to create and access the databases associated with the KBs. They also set the default Environment's Data Store User Name property and User Password Property
  • ProvisioningEndpoint: URL of GeneXus Server Installation (You must use the trailing slash, ie: "http://server1/GeneXusServerBeta/" instead of "http://server1/GeneXusServerBeta")
  • CustomPrivateAddress: IP Address or server name as seen from the Server where GeneXus Server is installed. If it is installed on the same server, 127.0.0.1 or localhost can be used
  • CustomPublicAddress: IP Address or server name as seen from the IDEs


Optional Configuration:

  • ServicesPort: GXM-Services will listen on this port
  • ServerID: GUID that identifies this GeneXus M Services installation
  • MaxConcurrentBuildProcess: <n process> default=1: Maximum concurrent build processes to be executed in parallel
  • TeamID: Not supported yet
  • BuildMode: For internal use. Do not touch!

Attention: You need to escape the backslash ('\') character!

Sample LocalSettings.json

Sample for the case that Server 2 <> Server 1

{
    "BuilMode":0,
    "ServicesPort":8001,
    "ServerID":"ce3641f4-2b2b-4895-b1a6-fc6463d0b1fd",
    "GenexusBLBasePath":"C:\\Program Files (x86)\\GeneXus\\GeneXusBeta",
    "ProjectsFolder":"d:\\GXMProjects\\",
    "SqlServerDefaultInstance":"localhost",
    "SqlUserName":"sa",
    "SqlUserPassword":"sapwd",
    "ProvisioningEndpoint":"http://server1/genexusserverbeta/",
    "WebServerRoot": "http://server2",
    "ProvisioningPlatform": 1,
    "CustomPrivateAddress":"server2",
    "CustomPublicAddress": "server2",
    "TeamID": ""
}

Sample for the case that Server 2 = Server 1

{
    "BuilMode":0,
    "ServicesPort":8001,
    "ServerID":"ce3641f4-2b2b-4895-b1a6-fc6463d0b1fd",
    "GenexusBLBasePath":"C:\\Program Files (x86)\\GeneXus\\GeneXusBeta",
    "ProjectsFolder":"d:\\GXMProjects\\",
    "SqlServerDefaultInstance":"localhost",
    "SqlUserName":"sa",
    "SqlUserPassword":"sapwd",
    "ProvisioningEndpoint":"http://localhost/genexusserverbeta/",
    "WebServerRoot": "http://myserver",
    "ProvisioningPlatform": 1,
    "CustomPrivateAddress":"127.0.0.1",
    "CustomPublicAddress": "myserver",
    "TeamID": ""
}

Note that http is used to declare GXserver's endpoint. If you need to use https, you must set up a certificate. See HowTo: Setting up an SSL Certificate in IIS for GeneXus Server for more information.

 

Was this page helpful?
What Is This?
Your feedback about this content is important. Let us know what you think.