Skip to main content

Install LDAWP

Run the LDAWP setup package on the prepared server, providing the credentials for the service account LDAWP will run under.

Written by Sabine Bunese

Prerequisites

  • The server has been prepared: the Web Server (IIS) role and .NET Framework 4.8 features are enabled, and the LDAWPServiceUser account exists.

  • The DigiPara Liftdesigner Suite is already installed on the server.

  • Access to the DigiPara Download Portal (a login is required to access the download files).

Download and start the installer

  1. Download the DigiPara LDAWP Setup.
    Log in to the Download Portal and download the file.

  2. Run the downloaded file.
    If a Windows UAC prompt appears, click Yes to proceed.
    ​

Enter the service account credentials

When the installation wizard launches, click Next, then:

  1. Locate the service account.
    Click Browse to select the account.

  2. Enter the domain and username.
    Search the domain directly into the Domain/Server field, or use the browse function to select it, and enter the username LDAWPServiceUser (the account created while preparing the server).

  3. Confirm the user definition.
    Click OK to confirm. This may take a moment.

  4. Enter the password.
    Type the password for LDAWPServiceUser and click Next.
    ​

Complete the installation

  1. Review and confirm the license agreement.
    Click Next.

  2. Begin the server-side installation.
    Click Install to start.

  3. Once complete, a success message appears.
    Optionally, view the Windows Installer log for details.
    ​

What the installer sets up

The setup performs the following actions automatically — useful to know when verifying the installation or troubleshooting later:

Directory operations — copies the following directories to the IIS root (e.g. C:\inetpub\wwwroot\) and sets the necessary user permissions:

  • LDAWP_DrawingGenerationApp

  • LDAWP_DrawingGenerationService

  • LDAWP_WebAdmin

  • LDAWP_Inbound

  • LDAWP_Outbound

IIS setup — creates two application pools and registers the applications and virtual directories below under them. Two pools exist because the classic stack runs on .NET Framework (LDAWP_AppPool), while the newer API and web app run on .NET 8 (LDAWPCore_AppPool):

IIS application

Application pool

Role

LDAWP_DrawingGenerationAPI

LDAWPCore_AppPool

New ASP.NET Core 8 REST API

LDAWP_DrawingGenerationApp

LDAWPCore_AppPool

Web frontend (URL-parameter interface + viewer)

LDAWP_DrawingGenerationService

LDAWP_AppPool

Classic WCF/SOAP service (existing integrations)

LDAWP_WebAdmin

LDAWP_AppPool

Web admin tool

LDAWP_Inbound / LDAWP_Outbound

(virtual directories)

Client model XMLs in / generated files out

The installer also configures Anonymous Authentication and adds the MIME types each application needs (e.g. .dwg, .svg).

Registry operations — adds specific values under the Liftdesigner LDOOP registry node (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\DigiPara\LIFTdesigner\LDOOP).

Result: LDAWP is installed on the server, with its IIS applications, virtual directories, and registry entries in place, running under the LDAWPServiceUser account. The LDAWP Administrator application is ready for the next configuration steps.

Related Articles
Did this answer your question?