ProductArtifactsPath - System Parameter
Store installation paths for Nodinite Core Services components. This parameter contains JSON configuration that maps component names to their URIs and API keys.
What you need to know about this parameter:
- Legacy - Used by Nodinite v6 Install and Update Tool
- Do NOT modify manually - Automatically managed by installation processes
- Nodinite v7 - Configuration comes from Environment entry in portal
- Internal use only - Not intended for manual administration
Warning
DO NOT MODIFY THIS PARAMETER
Nodinite administrators should NOT change this parameter manually.
- Nodinite v6 (Legacy): Automatically set by the Install and Update Tool
- Nodinite v7: Configuration comes from the Environment entry in the Nodinite portal
Manual changes may break quick-access buttons, automation, and internal component communication.
The ProductArtifactsPath System Parameter provides installation path information for Nodinite Core Services components. This JSON-formatted parameter is used internally by:
- Install and Update Tool (v6) — Quick-access buttons to web applications
- Internal automation — Component discovery and validation
- Troubleshooting tools — Verifying component locations
How It Works
Nodinite v6 (Legacy)
The Install and Update Tool provides quick-access buttons to web applications:
- Web Client — Perform a search in the Admin Log View and verify that Log Events are present in the results
- Web API — Use the Swagger feature to test Get operations for Roles. All roles should be returned in the response JSON
- Log API — If possible, post a minimal JSON Log Event example and confirm it appears in the Admin Log View
Nodinite v6 Install and Update Tool with quick-access buttons to web applications.
Nodinite v7
Configuration is automatically created and maintained based on the Environment entry in the Nodinite portal. Do not modify this parameter manually.
JSON Structure
The parameter stores a JSON array with objects for each component:
[
{"Name":"WebAPI","Uri":"http://localhost/Nodinite/Dev/WebAPI/","XApiKey":""},
{"Name":"WebClient","Uri":"http://localhost/Nodinite/Dev/WebClient/","XApiKey":""},
{"Name":"LogAPI","Uri":"http://localhost/Nodinite/Dev/LogAPI/","XApiKey":""},
{"Name":"LoggingService","Uri":"http://localhost:8000/Nodinite/Dev/Service/Logging/","XApiKey":"1234d170-1921-48d6-abcf-c93ff2888344"},
{"Name":"MonitoringService","Uri":"http://localhost:8000/Nodinite/Dev/Service/Monitoring/","XApiKey":"1234d170-ed36-479c-ba1b-6c189a3eb418"}
]
## JSON Structure
The parameter stores a JSON array with objects for each component:
```json
[
{"Name":"WebAPI","Uri":"http://localhost/Nodinite/Dev/WebAPI/","XApiKey":""},
{"Name":"WebClient","Uri":"http://localhost/Nodinite/Dev/WebClient/","XApiKey":""},
{"Name":"LogAPI","Uri":"http://localhost/Nodinite/Dev/LogAPI/","XApiKey":""},
{"Name":"LoggingService","Uri":"http://localhost:8000/Nodinite/Dev/Service/Logging/","XApiKey":"1234d170-1921-48d6-abcf-c93ff2888344"},
{"Name":"MonitoringService","Uri":"http://localhost:8000/Nodinite/Dev/Service/Monitoring/","XApiKey":"1234d170-ed36-479c-ba1b-6c189a3eb418"}
]
Field Definitions:
| Field | Description | Example |
|---|---|---|
| Name | Component identifier | WebAPI, WebClient, LogAPI, LoggingService, MonitoringService |
| Uri | HTTP/HTTPS endpoint URL | http://localhost/Nodinite/WebAPI/ |
| XApiKey | API key for authentication (if required) | 1234d170-1921-48d6-abcf-c93ff2888344 |
Note
API keys in the example above are for demonstration only and do not reflect real-world values.
Version Information
Available From: Nodinite version 4
Current Status:
- Nodinite v6: Used by Install and Update Tool for quick-access buttons
- Nodinite v7: Automatically configured from portal Environment entry
FAQ
How is this parameter created?
Nodinite v6: Automatically set during installation by the Install and Update Tool.
Nodinite v7: Automatically created based on the Environment entry configured in the Nodinite portal.
Can I modify this parameter?
NO. This parameter is for internal use only and should not be modified manually.
- Manual changes may break quick-access buttons
- Changes may disrupt internal component communication
- Updates will be overwritten during version upgrades
What if my component URLs change?
Nodinite v6: Run the Install and Update Tool to update the configuration.
Nodinite v7: Update the Environment entry in the Nodinite portal. The parameter will update automatically.
What are the XApiKey values used for?
API keys provide authentication for internal service-to-service communication, particularly for the Logging Service and Monitoring Service. These are automatically generated during installation.
Does this affect post-installation hardening?
The actual addresses used depend on post-installation steps performed as described in the Nodinite Hardening user guide. However, you should not manually modify this parameter—use the appropriate installation tool or portal configuration instead.
Next Step
Install and Update Tool — Installation and update procedures portal — Nodinite portal for v7 configuration Administration — System administration
Related Topics
Installation & Configuration:
Core Services:
System Parameters:
Access Management: