Configure the Server to Pre-load Services

Overview

The following sections describe how to use pre-load configuration settings when you start your DataFlux Data Management Server. This is helpful if you typically use the same services each time you run DataFlux Data Management Server.

Use the following options to configure pre-load:

DMSERVER/SOAP/DATA_SVC/PRELOAD_ALL = count
DMSERVER/SOAP/DATA_SVC/PRELOAD = count:name-of-servicecount:name-of-service ...

The value count specifies the number of pre-load instances. The value name-of-service indicates the name of the service element. This can include the directory where the service is located.
DMSERVER/SOAP/DATA_SVC/PRELOAD_DURING_RUN = yes|no

By default, the Data Management Server pre-loads all configured services before accepting SOAP requests. When the value is yes, the DataFlux Data Management Server starts a separate thread to pre-load all configured services at run time, while accepting SOAP requests at the same time. If DataFlux Data Management Server is stopped while the pre-load thread is still running, that thread will be terminated.

Pre-load All Services

The configuration option DMSERVER/SOAP/DATA_SVC/PRELOAD_ALL = count causes the DataFlux Data Management Server to find and pre-load a specified number of all services. This includes services found in subdirectories. The number of instances of each service (count) must be an integer greater than 0, or the directive is ignored.

For example, DMSERVER/SOAP/DATA_SVC/PRELOAD_ALL = 2 causes DataFlux Data Management Server to preload two instances of each service that is available, including those found in subdirectories.

Pre-load One or More Specific Services

The configuration option DMSERVER/SOAP/DATA_SVC/PRELOAD =count:name-of-service designates the specific services, as well as the count for each service, that the DataFlux Data Management Server is to pre-load at start-up. Use additional count and service elements for each service. Separate each count and service element by one or more blank spaces. The service element itself cannot include blank spaces. Also, all elements must be listed on a single line. Using this format, you can configure a directive that starts a number of services, each with a different count.

The following example loads two counts of the abc service and one count of the xyz service. The xyz service is located in the subdir2 subdirectory:

DMSERVER/SOAP/DATA_SVC/PRELOAD = 2:abc.ddf 1:subdir1\xyz.ddf

Configure Complex Pre-loads

By combining options, you can configure more complex pre-loads. The two options add the counts arithmetically to determine how many services are actually loaded. Internally, the DataFlux Data Management Server builds a list of all of the services that it needs to pre-load and, for each service, sets the total count.

The following two example options illustrate the logic of how this works:

DMSERVER/SOAP/DATA_SVC/PRELOAD_ALL = 2
DMSERVER/SOAP/DATA_SVC/PRELOAD = 2:svc1.ddf -1:subdir1\svc2.ddf -2:svc3.ddf

The first option instructs the DataFlux Data Management Server to pre-load a total of two instances of all existing services. The second options modify the first as follows:

Two additional counts of svc1.ddf are added, for a total of four instances. The counts are added together, and the total is the number of instances that DataFlux Data Management Server tries to preload.
The svc2.ddf file, which is found in the subdir1 subdirectory, has a -1 count. This produces a total count of one for svc2.ddf.
For the svc3.ddf file, there is a combined total count of zero, so this service is not loaded at all. The count value must be greater than zero for a service to be pre-loaded.

Some important points to remember:

DataFlux Data Management Server attempts to pre-load a single instance of all requested services before trying to pre-load more instances, if more than one instance is specified.
The service element can include the path to the service, relative to the root of the services directory. For example, 1:subdir1\svc2.ddf specifies one instance of service svc2.ddf, which is located in the subdir1 subdirectory.
The count value can be a negative value. This is meaningful only when both configuration options are used together.
Pre-loading stops when the Data Management Server has attempted to pre-load all required instances (successfully or not), or if the limit on the number of services has been reached. Depending on whether a SOAP or WLP server is used, the limit can be specified by using one of the following configuration options: DMSERVER/SOAP/DATA_SVC/MAX_NUM , or DMSERVER/WLP/DATA_SVC/MAX_NUM . These configurations will default to 10 if a number is not specified.