Prerequisites
Common settings are defined.
The Automation Data Pool is configured.
Set the Drawing Generation Service parameters
In the Drawing Generation Service Configuration section of LDAWP Administrator, review and configure:
Clean result path (min).
The interval, in minutes, at which output data in the Result Path is automatically deleted.Minimum free space on Result Disk (MB).
Minimum required disk space on the drive hosting the Result Path.Result Url.
The public URL used to access drawing files on the server. Must be adapted and must not use "localhost".Max Services.
The maximum number of parallel LDOOP processes — typically scaled to the server's CPU core count.Service timeout (s).
Timeout for the entire LDAWP drawing generation process. Should be ≥ the LDOOP timeout, to avoid terminating an instance prematurely.File Count.
The maximum number of unique XML filenames kept in the session list; this also decrements the SERVICECOUNTER value in the LDAWP contract. If exceeded, the oldest XML entry is removed (FIFO) to make room for the new one.Http Runtime Execution Timeout (s).
The maximum time an HTTP request can stay active on the web service. Should be ≥ the LDOOP timeout.Number of processes in LDOOP.
The number of preloaded LDOOP instances for the LDAWP Service.0= no preloaded instances;1–n= that many preloaded instances. Instances are initialized on the first request, so preloading reduces latency for subsequent requests.Default LDOOP process initialization project.
The default Liftdesigner project used to initialize LDOOP processes — typically your customer implementation's prototype project. Using a pre-initialized project significantly improves generation performance.
NOTE:
Configuration path is the directory where the configuration file currently being edited is stored.
Prototype path is created relative to the active data pool to save the model prototype ld3 file set in the DigiPara Liftdesigner Datamanager.
Result path is the local server directory where drawings generated from client requests are stored.
How the preloaded LDOOP pool behaves
With Number of processes in LDOOP set to, for example, 3:
Idle state — all three preloaded LDOOP processes are active and waiting for a request.
Job assignment — when a request comes in, one of the preloaded processes is immediately assigned to it.
Job completion — once the drawing generation finishes, that LDOOP process is terminated.
Re-initialization — after a few seconds, a new preloaded process automatically starts to keep the pool at its configured count.
High load — if concurrent jobs exceed the number of preloaded instances, an additional LDOOP process is started for the extra job — this takes longer than using an already-preloaded process.
Result: The Drawing Generation Service is configured with the correct paths, timeouts, and LDOOP pool size for your server's expected load.