Pre-Install Configuration

Some additional configuration steps are required once the software components have been installed.

Installation Setup

The installation of 1SMS on Wildfly requires, at a minimum, the set-up of a configuration file. In order to facilitate the ease of installation a minimum requirements template file is supplied. A number of parameters will need to be defined in order to install the full 1SMS suite.

During initial configuration refer to the template and this document. Configuration should be carried out in a single config.json file, but for clarity of documentation has been split into the individual sections:

  • Master Domain Configuration
  • LDAP Configuration
  • Clustering Configuration (Optional)
  • Product Configuration
    • 1Exchange
    • 1Workflow
    • 1Transact
    • 1Plan
    • 1Integrate
    • 1Integrate Engines

Access Through a Proxy or Load Balancer

If you are going to access 1SMS through a proxy or load balancer, then the download URL for 1Exchange packages will need to be adjusted to use the proxy or load balancer URL.

     Example: 1Exchange is installed on machine1.myCompany.local/1exchange, but proxy access is via 1sms.myCompany.com/1exchange.

To ensure the connection will work as expected, use the restBaseURL parameter to specify the external service address to be used by clients for the download of job packages.

Template File

The template file supplied includes the Elements required for minimum installation. These can be configured alone for a basic installation of 1SMS. If further customisation is desired then there are a number of additional optional parameters that can be implemented.

The file is called example-configuration.json and is supplied with the release notes.

     Note: Once you have edited this file, it must be renamed to config.json

Upon completion of configuration, place the file next to the installer JAR.