- 5 minutes to read

Step 12: Install Pickup Log Events Service

Install the new Nodinite 7 Pickup Log Events Service. There is no in-place update—you must install v7 using the Portal.

Prerequisites

  • Step 11 completed – TLS configured
  • Log API endpoint changed (now includes environment name in path)
  • Configuration Database renamed: NodiniteConfig_<ENV> → Nodinite_<ENV>_Config
  • PowerShell 7 with administrator privileges

Steps

Tip

If you already configured the Pickup Log Events Service settings in the Portal during Step 11 (Configure TLS), skip steps 1–5 and go directly to Download (step 6).

  1. Go to Portal → your Environment
  2. Click Agents tab
  3. Locate Pickup Log Events Service
  4. Configure settings:
    • Service Account: Verify or update account name
    • Service Account Password: Enter password
    • Port: Verify port (default or custom)
    • Log API Endpoint: Auto-configured with new v7 address
    • Database Name: Verify Nodinite_<ENV>_Config
  5. Click Save
  6. Click Download

Preparing Download
Wait for the Portal to generate your ZIP package before downloading.

  1. Extract ZIP to Application Server

  2. Open PowerShell 7 as Administrator
    Open Start Menu → Search "PowerShell 7" → Right-click → Run as administrator

  3. Navigate to extracted folder

  4. Run installation script:

    dir -r | unblock-file
.\Nodinite7-DEMO-Installation.ps1

    If your service account passwords contain special characters, pass them as SecureString values to avoid parsing errors.

    # If all service accounts share the same password
$pwd = ConvertTo-SecureString 'P@ssw0rd!' -AsPlainText -Force
.\Nodinite7-DEMO-Installation.ps1 `
    -WebClientServiceAccountPassword          $pwd `
    -WebApiServiceAccountPassword             $pwd `
    -LogApiServiceAccountPassword             $pwd `
    -LoggingServiceServiceAccountPassword     $pwd `
    -MonitoringServiceServiceAccountPassword  $pwd `
    -AzureAgentServiceAccountPassword         $pwd `
    -AzureLogicAppsAgentServiceAccountPassword $pwd `
    -BizTalkAgentServiceAccountPassword       $pwd `
    -BoomiAgentServiceAccountPassword         $pwd `
    -DatabaseAgentServiceAccountPassword      $pwd `
    -FileFolderAgentServiceAccountPassword    $pwd `
    -IBMMQAgentServiceAccountPassword         $pwd `
    -LogFileParserAgentServiceAccountPassword $pwd `
    -MessageQueueAgentServiceAccountPassword  $pwd `
    -MuleAgentServiceAccountPassword          $pwd `
    -NonEventsAgentServiceAccountPassword     $pwd `
    -PickupServiceAgentServiceAccountPassword $pwd `
    -RabbitMQAgentServiceAccountPassword      $pwd `
    -WebServiceAgentServiceAccountPassword    $pwd `
    -WindowsServerAgentServiceAccountPassword $pwd

    # If each service account has a different password
$pwdWebClient    = ConvertTo-SecureString 'WebClientP@ss'    -AsPlainText -Force
$pwdWebApi       = ConvertTo-SecureString 'WebApiP@ss'       -AsPlainText -Force
$pwdLogApi       = ConvertTo-SecureString 'LogApiP@ss'       -AsPlainText -Force
$pwdLogging      = ConvertTo-SecureString 'LoggingP@ss'      -AsPlainText -Force
$pwdMonitoring   = ConvertTo-SecureString 'MonitoringP@ss'   -AsPlainText -Force
$pwdAzure        = ConvertTo-SecureString 'AzureP@ss'        -AsPlainText -Force
$pwdAzureLA      = ConvertTo-SecureString 'AzureLAP@ss'      -AsPlainText -Force
$pwdBizTalk      = ConvertTo-SecureString 'BizTalkP@ss'      -AsPlainText -Force
$pwdBoomi        = ConvertTo-SecureString 'BoomiP@ss'        -AsPlainText -Force
$pwdDatabase     = ConvertTo-SecureString 'DatabaseP@ss'     -AsPlainText -Force
$pwdFileFolder   = ConvertTo-SecureString 'FileFolderP@ss'   -AsPlainText -Force
$pwdIBMMQ        = ConvertTo-SecureString 'IBMMQP@ss'        -AsPlainText -Force
$pwdLogFileParser = ConvertTo-SecureString 'LogFileParserP@ss' -AsPlainText -Force
$pwdMsgQueue     = ConvertTo-SecureString 'MsgQueueP@ss'     -AsPlainText -Force
$pwdMule         = ConvertTo-SecureString 'MuleP@ss'         -AsPlainText -Force
$pwdNonEvents    = ConvertTo-SecureString 'NonEventsP@ss'    -AsPlainText -Force
$pwdPickup       = ConvertTo-SecureString 'PickupP@ss'       -AsPlainText -Force
$pwdRabbitMQ     = ConvertTo-SecureString 'RabbitMQP@ss'     -AsPlainText -Force
$pwdWebService   = ConvertTo-SecureString 'WebServiceP@ss'   -AsPlainText -Force
$pwdWinServer    = ConvertTo-SecureString 'WinServerP@ss'    -AsPlainText -Force
.\Nodinite7-DEMO-Installation.ps1 `
    -WebClientServiceAccountPassword           $pwdWebClient    `
    -WebApiServiceAccountPassword              $pwdWebApi       `
    -LogApiServiceAccountPassword              $pwdLogApi       `
    -LoggingServiceServiceAccountPassword      $pwdLogging      `
    -MonitoringServiceServiceAccountPassword   $pwdMonitoring   `
    -AzureAgentServiceAccountPassword          $pwdAzure        `
    -AzureLogicAppsAgentServiceAccountPassword $pwdAzureLA      `
    -BizTalkAgentServiceAccountPassword        $pwdBizTalk      `
    -BoomiAgentServiceAccountPassword          $pwdBoomi        `
    -DatabaseAgentServiceAccountPassword       $pwdDatabase     `
    -FileFolderAgentServiceAccountPassword     $pwdFileFolder   `
    -IBMMQAgentServiceAccountPassword          $pwdIBMMQ        `
    -LogFileParserAgentServiceAccountPassword  $pwdLogFileParser `
    -MessageQueueAgentServiceAccountPassword   $pwdMsgQueue     `
    -MuleAgentServiceAccountPassword           $pwdMule         `
    -NonEventsAgentServiceAccountPassword      $pwdNonEvents    `
    -PickupServiceAgentServiceAccountPassword  $pwdPickup       `
    -RabbitMQAgentServiceAccountPassword       $pwdRabbitMQ     `
    -WebServiceAgentServiceAccountPassword     $pwdWebService   `
    -WindowsServerAgentServiceAccountPassword  $pwdWinServer

  5. Verify the Pickup Service application pool is running in IIS Manager

  6. Open Web Client → Administration → Monitoring Agents and confirm the Pickup Service agent appears with a green status

Migrate Configuration from v6 Settings.json

In v6, the Pickup Log Events Service was configured via a local Settings.json file on the Application Server. In v7 this configuration is managed remotely through the Web Client.

After installation, transfer the relevant settings from the old Settings.json into the Monitoring Agent configuration in the Web Client:

  1. Open Web Client → Administration → Monitoring Agents
  2. Locate the Pickup Log Events Service agent and click Edit
  3. On the Configuration tab, review and update each field against the values from your v6 Settings.json:
Settings.json field (v6) Web Client field (v7) Notes
LogApiUrl Log API Endpoint URL structure changed in v7 — now includes environment name in path. Verify the auto-configured value is correct.
DatabaseName / connection string Database Name Renamed from NodiniteConfig_<ENV> to Nodinite_<ENV>_Config
PollingIntervalSeconds Polling Interval Carry over your v6 value if it was customised
BatchSize Batch Size Carry over your v6 value if it was customised
  1. Save the configuration
  2. Check Web Client after a polling interval to confirm log events are being retrieved

Note

The Settings.json file is no longer used. Do not edit it — all configuration is now managed through the Web Client GUI.

Completion Checklist

  • Pickup Service configured in Portal
  • Installation script completed successfully
  • Pickup Service agent visible in Web Client Monitoring Agents with green status
  • Settings migrated from v6 Settings.json into Web Client
  • Log API Endpoint verified (v7 path format)
  • Database name verified (Nodinite_<ENV>_Config)
  • Log events visible in Web Client
  • No errors in IIS application pool or Event Viewer

Troubleshooting

IIS Application Pool Not Running

Problem: Pickup Service agent shows red/offline status in Web Client.

Solution:

  • Open IIS Manager → Application Pools
  • Find the Pickup Service pool and start it if stopped
  • Verify the service account identity has the correct permissions
  • Review Event Viewer for detailed errors

No Log Events Appearing

Problem: Agent is running but logs are not being picked up.

Solution:

  • Verify Log API Endpoint in the Web Client agent configuration — v7 URL includes the environment name in the path (e.g. http://server:40002/DEMO/api/...)
  • Verify Database Name is Nodinite_<ENV>_Config (renamed from v6)
  • Check network connectivity from the Application Server to the Log API port
  • Review IIS logs and Event Viewer for errors

Next Step