Installing Sage X3

Pre-requisites

This document describes how to install a Sage X3 solution on a Windows or Linux server.

Note: This procedure only applies to the first installation of a Sage X3 platform technology V12 product on new servers and workstations. It is important that a prior version of Sage X3 has never been installed on the server.

Before the installation, you need to:

1. Define the architecture of the servers that make up the SAFE X3 solution.
2. Check the minimum requirements of your system environment.
3. Make sure Java Runtime Environment or JDK version 8 or higher is installed. It can be downloaded from the Oracle website. Oracle Java Runtime Environment (JRE) or Java Development Kit (JDK) latest versions require commercial licensing to be used on production systems. You can download the open-source Zulu JRE or JDK 8 provided by Azul Systems instead. Make sure you download and install the Windows x86 Java version for your 64-bit Windows operating system.

You can then follow the installation procedure available on the official support (DVD-ROM or network location containing the installation files).

Installation overview

The main installation steps are listed below. Additional information is available in the corresponding paragraphs.

Installing and configuring the SAFE X3 solution (Linux or Windows)

1. Install the AdxAdmin administration runtime.
2. Install the components to configure a Sage X3 solution.
3. Install the Console on a Windows workstation.
4. Create a Sage X3 solution using the Console.

Installing Sage X3 Syracuse Server components (Linux or Windows)

1. Install MongoDB.
2. Install Elasticsearch.
3. Install Sage X3 Syracuse Server.

Completing the installation for Sage X3 Syracuse Server and the Sage X3 solution

1. On the Syracuse Server:
1. Update MongoDB and the Syracuse Server.
2. You need to update the Syracuse Server and MongoDB with the latest patch.
3. Make sure that you have the latest available version of MongoDB Community Edition installed with the corresponding prerequisites for the Syracuse Server.
2. On the Sage X3 solution:
1. Install the Seed folder.
2. Apply the list of patches.
3. Update the search index.

Installing the Production Scheduler

Caution: This feature is only available on-premise. If you are using the Cloud solution, this step is not relevant.

1. Install the Production Scheduler.

1. Install a Print Server component.

Installing additional and optional servers

1. Installing a Documentation server component (Linux or Windows).
2. Installing an additional Process server component:
   1. Install an additional Process server component (Linux or Windows).
3. Installing a Java Bridge component:
   1. Install a Java Bridge component (Linux or Windows)
4. Installing Web Services and ADC server component:
   1. Install the Web Services and ADC server component (Linux or Windows).

Installing and configuring the SAFE X3 solution (Linux or Windows)

Installing the AdxAdmin administration runtime

You have to install an administration runtime on each Process, Application, Database, Print, Java, and Webservice and ADC servers. However, it is not required on the client workstations or on the workstation that runs the management console.

Double-click adxadmin-91.3.5.1248.jar in the AdxAdmin folder.
The default AdxAdmin service port is 1818. Make sure this port is not blocked by existing firewalls or antivirus software as it is used to communicate with the Console.

Caution:

1. For Windows servers, run the installer as a user with administrator rights and rights to log on as a service.
2. For Linux servers, run the installer as root to create the AdxAdmin service. You can then run the AdxAdmin service as root and use the proprietary account of the SGBD Oracle installation to configure the database component in the SAFE X3 Console. Refer to our console documentation (AdxAdmin process rights) for more information.

Installing the components to configure a Sage X3 solution

1. On the database server only:
   Depending on the database used for SAFE X3, double-click db-sql-2.0.0-win.jar or db-ora-2.0.0.jar in the DbSQL or DbORA folder.
   Make sure the appropriate database engine was installed with the required settings before attempting this installation.
2. On the application server that hosts the Runtime component only:
   Double-click x3-application-12.0.19.jar in the Application folder.
   Select New installation.
3. On the process server only:
   Double-click runtime-91.3.5.12.jar in the Runtime folder.
   Select New installation.

Installing the Console on a Windows workstation

Double-click console-2.41.0.86-win.jar in the X3Installs\Console folder to launch the installation.

Creating a Sage X3 solution using the Console

Note: Before configuring a Sage X3 Solution, make sure that:

• Apache HTTP Server 2.2 or higher is installed on the Application Server. It can be downloaded from the Apache website. For Windows distribution, select the no_ssl MSI Installer Package in binaries/win32.
• The user account you use for the steps below has administrative rights and rights to log on as a service.

To create a basic solution, consult our console documentation.

Installing Sage X3 Syracuse Server components (Linux or Windows)

Installing MongoDB

MongoDB is an open source document database. Follow the detailed procedure to install it.

Note: Make sure you install MongoDB before installing Sage X3 Syracuse Server.

Installing Elasticsearch

Elasticsearch is an open source, distributed real-time search and analytics engine. Sage X3 is now compatible with Elasticsearch version 6.8. You can download it from the Elasticsearch website.

Note: It is important to click the links given inside version 6.8 procedures. If you go directly on Elastic's download center you will only be able to download their latest release that is not yet certified with Sage X3.

Although Sage X3 is still compatible with previous releases, it is strongly recommended to install version 6.8 as Elasticsearch 2.4.4 is no longer maintained by Elastic. It is highly recommended to host Elasticsearch on a dedicated server.

Make sure you write down the Elasticsearch host name and its corresponding http service port number. These two parameters are defined in the elasticsearch.yml file. You will need to set these hostname and port parameters in the nodelocal configuration file. These parameters are equivalent to network.host and http.port in the elasticsearch.yml file.

Note: For network.host, 0.0.0.0 will bind to all network interfaces. The value 0 has the same effect as 0.0.0.0. For further information, consult Elasticsearch's network settings documentation.

For further information on Elasticsearch set up, consult the installation guide available in their online documentation.

Installing the Sage X3 Syracuse Server component

Note: Make sure you install MongoDB and Elasticsearch before installing the Sage X3 Syracuse Server component.

Double-click syracuse-server-M.m.P.jar in the SyracuseServer folder to launch the installation:

• For Windows servers, run the installer as a user with administrator rights.
• For Linux servers, run the installer as root.

For more information on Sage X3 Syracuse Server installation, refer to the installation procedure.

Completing the installation for the Sage X3 Syracuse Server and the Sage X3 solution

On Sage X3 Syracuse Server

1. Make sure the certificates were generated during the installation.
   If not, generate the public key corresponding to the server (server_name.pwd). Refer to the certificate installation documentation for more information.
2. Make sure the following services have been started:
   1. Agent Sage Syracuse
   2. Elasticsearch for Syracuse
   3. MongoDB for Syracuse
   4. Sage Syracuse

   On the Sage X3 solution

   1. Make sure the certificates were copied during the installation.
      If not, copy the public key corresponding to the server (server_name.pem) in the keys folder of the solution runtime.
      If there are any periods (.) in the server name, replace them with underscores in the file name.
   2. Make sure the following services have been started:
      1. Sage X3 solution service
      2. Database services
   3. From a Sage X3 Syracuse Server connection:
      1. Open an Internet browser and log on as admin/admin to http://ServerName:port.
      2. Go to Administration > Endpoints > X3 solutions.
         When prompted to, click +New X3 solution. Enter a code, a description, an application, and the exact name of the Sage X3 solution, the main server host and the main server port. Click Save.
      3. Click Create endpoints in this new X3 solution and select the root folder.
      4. Click Administration > Endpoints > Endpoints and select the endpoint you created.
         Add the Super administrator group in the Administration section and click Save.
      5. From the root folder endpoint, click Personalizations and Menus intialization in the right-hand panel.
         Wait until the end of the import.
      6. Log out from the web server and log back in as admin.
      7. Click the endpoint name in the header and select the endpoint of the Sage X3 root folder.
      8. Click Setup > Users > Users (GESAUS function).
         Wait until the Supervisor installation is complete.

   Installing the Seed folder

   The Seed folder is the demonstration folder supplied with Sage X3. Aside from root folder X3, the Seed folder is the first endpoint you can connect to. After completing the installation, you can use the Seed folder as a sandbox.

   To install it:

   1. Navigate to the Seed directory in the product DVD-ROM.
   2. Double-click the x3-seed-12.0.19.zip file to launch the self-extracting archive.
   3. Copy the extracted Seed folder to where the Sage X3 application folders are installed.
   4. Copy the extracted X3_PUB\Seed subfolder to where the Sage X3 application X3_PUB directory is located.
   5. Open the Console, select the Sage X3 solution from the Solutions tab and click the folders icon.
   6. Click Import, select the Seed folder from the drop-down list and make sure that SVG is set as the data directory.
      Make sure Import of the table structure only is not selected and click OK.
   For more detail, consult our console documentation.
   7. Define an endpoint for the Seed folder before using it.

   Applying the list of patches

   For a first installation, use the applicative setup installation support available from your local Sage download center. You should also do the applicative setup using folder validation if you have not installed several monthly patches on your existing installation.

   If you only have one patch to add, in all folders, apply the latest patch available from your local Sage download center. You can contact your local support for further information about the patches to download.

   Mandatory if a zip file exists under the directory Patch:

   1. Go to Administration > Utilities > Update > Updates and click Add an update.
   2. Upload the zip file located in the Patch directory.For more details, refer to the Administration reference updates documentation.

   Updating the search index

   You have to update the search index in order to use the data search feature for an endpoint.

   1. Log in to Sage X3 as admin.
   2. Go to Administration > Usage > Search Index Management.
   3. Select the data source endpoint to index.
      Leave Entities blank.
   4. Select the locale for which the index must be updated.
   5. Select Delete index before update.
   6. Click Update index.
      Refer to Search Indexes Administration for more information.

   Installing the Production Scheduler

   The Production Scheduler is an option of the Manufacturing module.

   Double-click production-scheduler-6.0.1842-win.jar in the ProductionScheduler folder to launch the installation.
   
   Refer to Installing the Production Scheduler for more information.

   Installing a PrintServer component

   1. Double-click print-server-2.16.0.26-win.jar in the PrintServer folder.
   2. To implement a print server, consult our console documentation.

   Installing additional and optional servers

   Installing a Sage X3 Documentation server component

   By default, Sage X3 tries to access the online documentation server through the internet, but an optional local server can be installed. This allows customers to manage custom help pages or to access the help when the internet is unavailable.

   1. Double-click x3-documentation-12.0.19.jar in the Documentation folder.
   2. Enter a name for the local documentation server, as well as an available port number.
      This port will be used for the help base URL.
   3. When prompted to select the installation packages, select Sage X3 V12 documentation files if you want to copy the standard help pages locally.
      If you only want to manage custom pages on the local documentation server, do not check this option.
   4. Finish the installation process.
   5. For each endpoint from where you want to access the local documentation server, enter the help base URL (http://server_name:documentation_server_port/).

   Installing an additional SAFE X3 Process server component

   Double-click runtime-91.3.5.12.jar in the Runtime folder to launch the installation.

   Caution:

   • For Windows servers, run the installer as a user with administrator rights and rights to log on as a service.
   • For Linux servers, run the installer as root to create the AdxAdmin service. You can then run the adxadmin service as root and use the proprietary account of the SGBD Oracle installation to configure the database component in the Console. Refer to our console documentation (AdxAdmin process rights) for more information.

   To implement an additional SAFE X3 Process server component, consult our console documentation.

   Installing a Java Bridge component

   1. Double-click java-bridge-2.23.2.jar in the JavaBridge folder.
   2. To implement a Java Bridge server, consult our console documentation.

   Installing Web Services and ADC server component

   Installing Web Services and ADC server component

   This component provides a web-service SOAP server (for the Sage X3 HR portal) and VT connection.

   1. Make sure all system requirements (on Windows or on Linux) are met.
   2. Double-click vt-web-server-2.36.1.jar in the VTWebServer folder.
   3. Select New installation.
   4. Enter the installation path.
   5. Enter the server name, the path for all temporary files and logs, and the passphrase to use to encrypt the private key that will be generated at the end of the installation.
      Make sure you write down the passphrase, and keep it at hand when launching the configuration of the component.
   6. For Linux installations, set the user and group who will own the folder where the component will be located.
   7. Configure the component with the management console.
      

   Configuring the Web Services and ADC server using the Console

   From the Console:

   1. Define the port to use and enter the passphrase you have set during the installation.
      Enter specific parameters, if required.
   2. Link the folders that will be used for web-service or VT connection to the component, and complete the required setup.
      The webservice component public key that was generated during the installation is automatically copied in the appropriate folder of the runtime server. This is done in order to establish an operational connection between the two components.
   3. Define web-service pools to enable SOAP clients call X3 Objects and sub-programs using the SOAP protocol.
      Configure a pool per folder.
      Note: The web-server uses the passphrase you configured to encrypt the private key. This allows a secure connection between the runtime and the webservice server. The passphrase is also encrypted.
   4. If you connect to the management console from another user account, re-enter the passphrase.
   5. If you update a webservice ADC server 231 to a newer product update, and if you have already published the solution, make sure that the public key of the webservice ADC server is in the keys sub-directory of each runtime directory of the linked solutions.

   Caution: If you have installed a Sage X3 Syracuse Server before installing the webservice ADC server component, make sure you copy the public key of the Sage X3 Syracuse Server to \data\KEYSTORE\WEBSERVER\ for a secure connection between Sage X3 Syracuse Server and the ADC server webservice for the HRM portal.

   Installing Business Intelligence

   Refer to the Business Intelligence installation procedure for more information.

   
   
   Index  Home