Sage X3 installation procedure_7.0

Introduction

This document describes the installation procedure for the Sage X3 solution on Windows and Linux servers.

Warning: This process is only valid for the first installation of SAFE X3 technology version 7 product on new servers that do not host a prior version of the product.

There is no specific recommendation, the user must:

• Define the architecture of the servers that make up the SAFE X3 solution.
• Check the compatibility of the system environment with the hardware and software prerequisites of each component, and follow the installation process available on the official support supplied (product DVD-ROM or network location where all the installation files have been placed).

Installation steps

The installation steps are described below. Additional information about the detail process will be found in the corresponding paragraphs.

Installation and configuration of the SAFE X3 solution (Linux or Windows):

• Install the AdxAdmin administration runtime.
• Install the components to configure a Sage X3 solution.
• Install the Console on a Windows workstation.
• Create a Sage X3 solution using the Console.

Install the SAFE X3 administration components (Linux or Windows):

• Install the components for the SAFE X3 node.js server.

Complete the installation for a SAFE X3 administration server and Sage X3 solution (Linux or Windows):

• On the SAFE X3 node.js administration server.
• On the Sage X3 solution.

Installation of the Print server component on a Windows server:

• Install a Print Server component.
• Configure the print server using the Console.
• Publish the SAFE X3 folders for the print server using the Console.

Further installation of Print servers, Process servers, and Java servers:

• Install an additional Print Server component.
• Configure the Print server using the Console.
• Publish the Sage X3 solution folders on the Print Server using the Console.
  
• Install an additional Process server component.
• Configure the process server using the Console.
  
• Install a Java server component.
• Configure the Java server using the Console.
• Publish the Sage X3 solution on the Java server using the Console.
  

  ---

Installation of AdxAdmin administration runtime

Installing an administration runtime on each server is mandatory for all Process, Application, Database, Print, and Java servers. It is not necessary to install the administration runtime on the client workstations or on the workstation that will run the configuration console.

• Administration runtime: AdxAdmin

To launch the installation, double-click the '.jar' file in the AdxAdmin folder.

For Windows servers, it is mandatory to launch the installer as a user with administrator rights.

For Linux servers, it is recommended to launch the installer as root; otherwise, the corresponding service will not be created (adxadmin). It is then recommended to launch the adxadmin service as root and to use, in the Console, the proprietary account of the SGBD Oracle installation to configure the database component. For more information on this topic, refer to the console documentation, paragraph 'AdxAdmin process rights' on page 'Component loading - dialogue box'.

Install the components to configure a solution in SAFE X3 technology

Install the required components from the installation support on the corresponding destination server(s):

• Database: DbSQL or DbORA depending on the database to be used for SAFE X3 (Oracle or SQLServer).
• Application: Application
• Process server: Runtime

To launch the installation, double-click the '.jar' file in the folder of each component.

Install the components for node.js administration server

Install the required components from the installation support on the corresponding destination server(s):

• Elasticsearch server: Elasticsearch
• Node.js administration server: Syracuse Server

To launch the installation, double-click the '.jar' file in the folder of each component.

For Windows servers, it is mandatory to launch the installer as a user with administrator rights.

For Linux servers, it is recommended to launch the installer as root; otherwise, the corresponding service will not be created.

Reminder: as a prerequisite, it is necessary to install the MongoDb database onto the server for the Version 7 web server component.

For more information about the node.js administration server installation, see the node server installation procedure.

Installation of the Console

Install the required component from the installation support on the corresponding destination server:

• Configuration console: Console

To launch the installation, double-click the '.jar' file in the Console folder.

Creation of a Sage X3 solution

Using the SAFE X3 configuration console:

• Create a new solution in the console.
• Search for the components database, application and main runtime in the 'Data - Application' tab. For the database, you can share an existing database already active in another solution, only if the product code is different.
• Enter the parameters for each component.
• Configure the database using the "Data" button. To use the default scripts, choose the "Total configuration" option.
• Configure the application and the main runtime using the "Application" button.
• The solution exists on the server when the application and runtime configuration is completed.

Complete the installation

On the SAFE X3 node.js administration server:

• If the generation of certificates did not occur during the installation of the administration server component, you need to generate the public key corresponding to the server. This file must be generated with the name of the server ('hostname'.pwd - in which hostname matches the name of the SAFE X3 administration server).
  Please refer to the corresponding Certificate installation documentation.

• Check that the following services have been started:

  • Agent Sage Syracuse Server
  • Elasticsearch for Syracuse
  • MongoDB for Syracuse
  • Sage X3 Syracuse Server

Note: You can set a dependency between services to ensure services are started in the order they are needed. First, you must start the Elasticsearch for Syracuse service and MongoDB service, and then the Agent Sage Syracuse Server service. The Sage X3 Syracuse Server service must not be set to start automatically.

On the SAFE X3 Solution server:

• If the copy of certificates did not occur after the installation of the node.js administration server component, add the public key (file [ServerName].pem) in the keys folder of the solution runtime.

• Check that the following services have been started:

  • Sage X3 solution service (in function of the name of the X3 solution).
  • Database services (in function of the Sage X3 database is installed under Oracle or SQLServer).

• From a Version 7 web server connection (as an administrator):

  • Log on to the following URL "http://[ServerName:port]" (for example: http://aysyrqav7:8124), using an Internet browser, and the user/password: admin/admin.
  • Define the X3 server: a server and a service are identified to access the Sage X3 files (matches a Sage X3 solution).
  • Click the X3 Servers link in the administration menu and then click “+Creation”. Enter the exact name of the server and the port number of the service logged on to the solution. Click “+Save”.
  • Declare the endpoint (Endpoints), for the root folder of the Sage X3 solution. Click the link Endpoints in the administration menu and then click “+Creation”. Enter the fields and grant access to the 'Super Administrators group’. Click “+Save”.
  • Associate an endpoint (Endpoints) to a user. Click the link User in the administration menu and then click “+Creation”. Enter the information and add the endpoint to the "Endpoint login" list. Click “+Save”.
  • Log out from the Version 7 web server (Logout button), and then log in.
  • Select the endpoint of the root folder (of the product) by selecting the Login button.
  • Finalize the Supervisor installation: Select the view "ADMX3 user portal', and then launch a function from the menu (for example: Setup > General parameters > Folders, GESADS function).
  • Apply any patches delivered with the version in the folders: Copy the .dat files from the Patch folder of the installation support (corresponding to the patch list) into the PATCH folder on the root folder of the created solution. Using the PATCH function ( Development > Utilities > Patch integration ), integrate the patches by selecting “destination type = Server”, and choose the PATCH volume ([PATCH]/).

Install a SAFE X3 Print server component

Install the required component(s) from the installation support on the corresponding destination server(s):

• Print server : Print Server

To launch the installation, double-click the '.jar' file in the folder of the component.

Configure this component with the configuration console.

Install an additional SAFE X3 Process server component

Install the required component from the DVD-ROM on its destination server.

• Additional process server : Runtime

To Launch the installation, double-click the '.jar' file in the folder of the component.

Configure this component with the configuration console.

Install JavaBridge component

Install the required component from the DVD-ROM on its destination server.

• Java Bridge server : JavaBridge

To launch the installation, double-click the '.jar' file in the folder of the component.

Configure this component with the configuration console.