A Rules Service item lets you install, start, configure, stop, and uninstall a USoft Rules Service.
A USoft Rules Service enables a client to connect to a USoft Rules Engine server.
A Java client application can connect using the JDBC protocol. For more information about JDBC Rules Engine Connectivity, refer to the USoft Definer Guide or the USoft Definer Help.
A Rules Service item has the following properties and options:
This is the name of the Rules Service as it is shown on the Services tab page in the Control Panel of the Windows operating system. By default the name RulesService is used but it is strongly suggested that you use a name appropriate to the application served, e.g. OrdersService. Note that the Service Name and its port number must be unique. As a consequence, a running service has to be stopped and removed before its name can be changed.
|
This is the port number that the Rules Service uses to communicate with client applications. This port number must be included in a client connection string. By default, the port number is 7777. It is strongly suggested to choose a unique port number since a port number can only be used by one RulesService on a machine.
|
This check box can be selected to start the Rules Service automatically every time your computer is started.
IMPORTANT: When you uninstall USoft Series, you must clear this check box, otherwise you will get an Event Log error message the next time the computer is started.
|
If this Rules Service is intended for use in a secure connection, check the Use TLS check box. Otherwise, leave it unchecked. TLS stands for Transport Layer Security, and it makes use of the Secure Sockets Layer.
NOTE: You must install an appropriate digital certificate before you can use TLS/SSL. See your USoft Authorizer help for more details.
|
This is the port number that the Rules Service uses to communicate with client applications. This parameter is used to specify the port number if you are importing data from another rules service.
|
You can specify the host name and port number of another (Peer) Rules Service that is already started. The new, to be started, Rules Service will take its configuration parameters from this Peer Rules Service. If you click the Configure button, an overview of all running Rules Engines is shown.
|
For security reasons, only the localhost (i.e. the host where the service runs) can be used to configure the Rules Service. To allow remote configuration of the Rules Service, the Hostname field can be used to specify a name, or list of names of remote computers that are trusted to configure the Rules Service. The list of controlling hosts can be extended by supplying new hostnames.
|
Click the Add button to add the name of a remote computer to the Controlling hosts list.
|
Click the Remove button to remove the name of a remote computer from the Controlling hosts list.
|
Click the Install button to install the Rules Service as a Windows Service.
After installation of the Rules Service, all fields above the Install button are greyed out. Removing the Rules Service enables these fields again.
|
Click the Remove button to remove the Rules Service from the Windows Services.
|
If this Rules Service is running on the same machine that is running the database service that the Rules Service uses, select the name of the database service from the drop down list. This ensures that following a restart of both services, or the machine, for example, Windows will check that the database service is running before it attempts to start the Rules Service.
This is not necessary if the services are running on different machines.
|
After completion of all Rules Service properties, click the Start button to start the Rules Service.
|
Click the Stop button to stop a running Rules Service.
|
Click the Configure button to view the first configuration page for this Rules Service. In these configuration pages:
•Specify the USoft application to serve, and the database account. •Specify the number of Rules Engines to run. •Monitor the Rules Engines that are currently running and the client computers that are currently connected. Refer to the help provided with these configuration pages.
|
|