Test system Build Diary: 2021 R3 (V12 patch 27) Multi-Main (Application Cluster) installation

2 minute read time.

Last Updated: 19th August 2021

Return to Index page: Test system Build Diary index

What is a "Build Diary"

A Build Diary simply describes the steps taken by Sage Support to perform a task or tasks on our internal test systems.  Build diaries could be created for major multi-node installations, but may also just be describing the steps taken when installing a small hotfix, or anything in-between.

Why is this being shared

It may be useful for you to see the steps we have taken to create or implement some feature or installation, as this may highlight "gotcha’s", issues encountered or just give you some guidance if you are planning something similar yourself.

You could potentially use these documents as the base for your own "Workplan document" (Described in "Overview of patching X3 and supporting technologies") when you are planning your own activities

Target Audience

This document is aimed at Sage X3 Certified Technical consultants.  Sage prescribe that X3 system installation, maintenance, migrations, etc. should be performed by suitably qualified Sage X3 consultants.  The prerequisite consideration would be for them to have the latest "Sage X3 Certified Technical Consultant" certification.  You can read more about the Sage X3 qualifications and requirements in Sage University

Additional things to note

•    This document does NOT purport to illustrate "best practice" for the task being described
•    The steps described will not necessarily be for a "perfect" task, as there may have been issues that needed to be overcome, worked around, or ignored
•    The Sage internal test system has network and hardware configuration specific to Sage
•    The Sage internal test system does not necessarily include a Windows Domain and has Sage sandbox specific Windows security setup, so operating system permissions are generally not discussed
•    If you intend to use these notes as a guide for your own activities, use with caution and perform your own testing to ensure the described steps are suitable and identify any additional considerations that apply to your own situation
•    Ensure you only install and use software you are licensed for

What does this Build Diary describe?

This build diary primarily describes the creation of a three-node new installation, with installation and configuration of three node Multi-Main (Application Cluster) for use as an internal TEST system, using software versions:
•    Windows Server 2019
•    SQL Server 2019
•    X3 version 2021 R3

See the attached PDF document "BuildDiary_2021R3_MultiMain_Install.pdf"


If you find this document useful, or even if you don’t, we would be happy to hear your feedback.

BuildDiary_2021R3_MultiMain_Install.pdf
Parents
  • Hi Mike,

    On Application server setup, I am a bit confused on this part. A explanation would be appreciated as the Network button always confused me during Application setup test runs.

    Suppose I have a separated dedicated SAN with a UNC path to the shared path of the SAN, what should I put on both Network target and Destination path?

    Assume I cannot access the SAN normally as it is using own proprietary OS and not Windows. I also did not map it to a drive letter in advance for Destination path (had an issue with it).

  • Seems like Network is for when the current application server is the main base.

    The UNC Path in Network will be used to point to current application server.

    If planning to use SAN/NAS/Amazon FSx/Dedicated File Server to store `folders`, make a `Standard` installation at C:\ drive (or any physically installed disk drive letter; don't use any outside server's disk first) and then after a full solution configuration, follow this guide to complete the transition to UNC path: https://www.sagecity.com/gb/sage-x3/b/sage-x3-uk-support-insights/posts/test-system-build-diary-v12-patch-27-convert-runtime-to-multi-main

    Note: The instruction for moving means cut and paste `folders` to the UNC Path. A directory symbolic link (SYMLINKD) will be created by Sage X3 Console at the C:\ drive to point to UNC Path.

    Sage X3 Console requires Sage X3 AdxAdmin to function and symbolic link will tell Sage X3 Console to use current Application Server's AdxAdmin rather than accessing to the UNC Path and ask its server's AdxAdmin.

    Had to resolve an emergency and learned the hard way since I am confused at the `Network` explanation in Sage X3 Application installer.

  • Hello Chunheng,
    Sorry the instructions were unclear.  From reading your last comment, I think you have solved your problem?

Comment Children