---
title: "Legacy - LiveDesign on-premise"
slug: "connector-ld-pp-admin-guides-ld-onprem"
updated: 2026-04-21T09:44:57Z
published: 2026-04-21T09:44:57Z
canonical: "docs.discngine.com/connector-ld-pp-admin-guides-ld-onprem"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.discngine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Legacy - LiveDesign on-premise

The following installation procedures to **deploy the Pipeline Pilot Connector Gadget application** are based on a legacy LiveDesign on-premise installation using nginx as application server. For the following steps, we assume you have SSH access to your LiveDesign server. Note that you might need sudo rights on the LiveDesign server.

## Single gadget (main use case)

1. Create a ldconn.conf file in nginx's endpoints.d folder:

```
cd /etc/nginx/endpoints.d
touch ldconn.conf
```

1. Fill the ldconn.conf file.

Copy the files in the folder **web** of the downloaded zip package into the `/home/seurat/custom_gadgets/ldpp/` folder (or any other folder you wish to use). Then, paste the following lines in the ldconn.conf file:

```
location /discngine/ldconn/ {
    alias /home/seurat/custom_gadgets/ldpp/;
    index index.htm;
}
```

1. Add the following endpoint at the end of the ldconn.conf file:

```
location = /discngine/ldconn/session/ {
    default_type text/plain;

    if ( $http_cookie ~ "JSESSIONID=(?<token>[^;]*)" ) {
        return 200 $1;
    }
    return 401;
}
```

1. Restart nginx:

```
sudo service nginx restart
```

## Several gadgets

Let's assume our LiveDesign server is hosted on `livedesign.discngine.com` and we have two Pipeline Pilot servers: `pp.dev.discngine.com` and `pp.prod.discngine.com`. We want to have two gadgets on LiveDesign:

- `PP Connector`, which will point to `pp.prod.discngine.com` and be defined on LiveDesign under `/discngine/ldconn`
- `PP Connector DEV`, which will point to `pp.dev.discngine.com` and be defined on LiveDesign under `/discngine/ldconn-dev`

### Nginx configuration

The nginx configuration located at `/etc/nginx/endpoints.d/ldconn.conf` should look like:

```
# Location for the first gadget (proxy calls to PP prod)
location /discngine/ldconn/ {
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_pass https://pp.prod.discngine.com:9943/discngine/ldconn/;
        proxy_read_timeout 600;
}

# Location for the second gadget (proxy calls to PP dev)
location /discngine/ldconn-dev/ {
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_pass https://pp.dev.discngine.com:9943/discngine/ldconn$path_remainder;
        proxy_read_timeout 600;
}

#Mutualisation of the session endpoint as it will be the same for both gadgets
location /discngine/ldconn/session/ {
    default_type text/plain;

    if ( $http_cookie ~ "JSESSIONID=(?<token>[^;]*)" ) {
        return 200 $1;
    }
    return 401;        
}
```

### Admin panel

The declaration of the gadget in the admin panel should look like:

```
[
  // ... other gadgets
  {
    "categoryName": "Discngine",
    "gadgets": [
        {
            "name": "PP Connector",
            "location": "/discngine/ldconn/index.htm?pipelinePilotServerUrl=https://pp.prod.discngine.com:9943"
        },
        {
            "name": "PP Connector DEV",
            "location": "/discngine/ldconn-dev/index.htm?pipelinePilotServerUrl=https://pp.dev.discngine.com:9943"
        }
    ]
  }
]
```