Sage X3 solutions
| Administration Page | Application/Contract | Syracuse/Collaboration | Class | x3solutions | Representation | x3solutionr |
|---|
A Sage X3 solution entity describes a connection to a Sage X3 solution. Associated with a Sage X3 server, there are several Endpoints that correspond to Sage X3 folders.
The following information must be entered for a Sage X3 server:
A unique code that identifies the solution
Description of the Sage X3 server that displays when the Sage X3 server is referenced in another page, for example an Endpoints definition
Indicates the name of the solution
Provides the main process server address, which can be the network server name or the IP address
The port used by the Sage X3 connection service to the solution
The location of the host in which the Apache Web server delivering the Sage X3 resources for Classic pages. The host is usually the same as the application server and does not need to be entered. The address can be the network server name or the IP address.
The port used by the Apache Web server delivering the Sage X3 resources for Classic pages. The port is usually 80, but it can be changed.
A check box that indicates if the proxy must be used for HTTP access
Defines the BO server, if there is one, that is associated with the X3 server to deliver Business Intelligence data.
Selects the Endpoints the solution is connected to. Endpoints can be added in multiple selections.
Indicates the Certificate used by Syracuse to authenticate against the servers
A solution can be accessed by several runtimes that are described in this array. If several runtimes exist, the load balancer will, by default, use a round-robin algorithm that selects a runtime at connection time; this algorithm can be changed according to the parameters associated with the runtimes:
Server on which the runtime is installed. It can be a network name or an IP address.
The port associated with the runtime.
Represents an affinity list of tags, separated by commas, that allows you to assign the preferred runtime at connection time (see the corresponding paragraph). On the other hand the same tags can be set either on a group for the user connection, or on a SOAP Pool for a SOAP web service connection or on a batch server for the tasks launched by the batch controller.
The application server has by default a "MAIN" tag.
This check box can be selected only if a tag has been entered. When selected, the runtime can only be accessed if the tags are found in the context of a runtime execution (ie defined in groups, SOAP Pool or batch server).
When a runtime server is not available for connection (if it doesn't answer to the connection request), the server is blacklisted and is no longer used to connect during a period in minutes defined by this value. Note that once the banishment has been triggered, the task that will cancel the blacklisting that is launched in the server instance. If in the meantime the server is stopped, the blacklist will not be automatically canceled after the time-out. For this reason, it is possible manually to clear the Blacklisted check box.
When a runtime server is blacklisted, this check box is selected. It can also be manually selected (for the ban time-out period) and reset. The reset link is particularly interesting if the server was stopped after the banishment because there is no other way to delete it from the blacklist.
When the runtime server has been automatically configured by the synchronization service based on solution.json file, this check box is selected. Additional runtimes can be added manually, then this check box needs to be cleared.
Select this check box to disable a runtime that is being used.
Indicates the number of jobs that can run in parallel during the update process. The 0 default value indicates that there is no limitation.
Runtime servers are assigned based on a round-robin algorithm on the eligible runtimes. A runtime is eligible if is not disabled or blacklisted.
The runtime assignment is done in priority on the runtimes that have the same tag as the context runtime execution, (i.e., defined in groups, SOAP Pool or batch server).
If no tag matches, or if the runtime with the same tag is not eligible, the connection is established on the next available runtime according to the round robin rule, except for those runtimes that have a tag with the “exclusive” check box selected.
In a non multi main runtime architecture, meaning that the eanable application cluster is not set on the Sage X3 solution, certain functions will automatically run only on the main server because of applicative needs. This is an automatic assignment that does not require any configuration.
Several services available from the right panel:
This service accesses the main server associated with the solution and checks if the connection is possible. It displays the result on the upper panel.
This service is available directly on the line of the server array. It checks if the connection is possible and displays the result on the upper panel.
This service connects on the main server associated to the solution and checks if the connection is possible on all available servers. It displays the result on the upper panel.
This service displays a dialog box with all the available endpoints for the solution. Select the check box at the beginning of each line to create the endpoint definition with the right parameters.