The Edit Service Properties (EDTJSMSRV) command uses the EDTF command to edit the service.properties file in the system subdirectory.
It is recommend you use Studio to maintain this file.
The service.properties file configures the JSM services. It is a registry for the services used by the JSM. It is also used for controlling tracing and resources.
The service.properties file is loaded when the JSM starts. If the service properties change, you must refresh in order for the changes to take effect.
When you select the option to Edit JSM Service Properties, you will be prompted to enter the following:
The instance defaults to a value of *DEFAULT. This is the recommended value. The default instance is defined in the JSMMGRDTA data area. This value can be changed using 184.108.40.206 Change Default Instance (CHGJSMDFT).
Following is an example of the service.properties file:
Edit File: /jsm/instance/system/service.properties
************Beginning of data**************
# Java Service Manager services
************End of Data********************
When the LANSA client requests that the JSM to load a service, only the name of the service is specified.
USE BUILTIN(JSM_COMMAND) WITH_ARGS('SERVICE_LOAD SERVICE(SMTPMailService)') TO_GET(#JSMSTS #JSMMSG)
When the JSM instance receives the SERVICE_LOAD command, the SMTPMailService servicename is prefixed with "service." The JSM searches the service.properties files. It uses the keyword SERVICE.SMTPMAILSERVICE to locate the class named com.lansa.jsm.service.SMTPMailService.
It is possible to associate a resource with this service by adding an entry with a "resource." prefix.
If a resource entry is present and the named resource file exists in the properties subdirectory, then this resource is passed to the service program via the JSMContainer getServiceResource() method.
If no resource entry exists then the service name is used as the resource file name.
If no resource file exists then an empty resource object is returned.