Release Notes
Managing the Nodinite Install and Update Tool
Use the latest Nodinite Install and Update Tool to perform installations and updates; see the release notes for details about the specific version.
What is the address of the Nodinite Install and Update Tool?
The installer can opt to change the default installation paths; the actual address in use may vary between different installations.
Try any of the following first (replace %hostname% accordingly):
- HTTPS -
https://%hostname/%/NodiniteUpdate/UpdateClient/ - HTTP -
http://%hostname/%/NodiniteUpdate/UpdateClient/
If you don't know the address (URI) to the Nodinite Install and Update Tool, log on locally on the Nodinite Application Server with administrative privileges. Then, you can try to use the default address http://localhost/NodiniteUpdate/UpdateClient/.
But, of course, you can always find and access the address using the IIS MMC (%windir%\system32\inetsrv\InetMgr.exe).
Features
You can manage the following features using the Nodinite Install and Update Tool:
- Assign access rights - Manage who should be allowed to install and update Nodinite
- Download package - Download a Nodinite Core Services package.
- Install and Update Monitoring Agents
- Install and Update Logging Agents
- Install a new instance of Nodinite
- Update an existing instance of Nodinite
- Manage BizTalk Server Logging for each instance.
- Manage System Parameters for each instance.
- Manage License for each instance.
Assign Access rights
The initial installer can configure, thus limiting the set of users (or Windows AD Groups) with a grant to access and use the Nodinite Install and Update Tool.
The users and groups differ in the Nodinite Install and Update Tool, and the Nodinite Core Service instances.
The Nodinite Install and Update Tool complains with a yellow warning bar that you still need to apply the access restrictions, encouraging you to perform the configuration. But beware, access to the tool is otherwise fully open and accessible for everyone on the network with access to the host.
How do I restrict access?
Make sure to comply to your security policies and limit access to this tool.
You can Add and Remove users and groups from the Settings tab/page You must know the exact name from the Active Directory. Use the following format (you can see the current account name at the top right):
- Domain\User Name
- Domain\Group Name
Settings tab, where an authenticated and assigned user can add and remove users and groups to allow/prevent access to this tool.
NOTE: The changes are immediately effective when you click on the Add/Remove buttons.
The settings are instantly applied; if you do not add your own account first, you will be locked out of the tool.
Remove User
You can remove a user by clicking on the Remove button.
Remove Active Directory Group
You can remove an Active Directory Group by clicking on the Remove button.
Configuration file
You should only edit this file if you lock yourself out of the tool or try to perform an advanced update/reconfiguration. Make sure to first create a backup of this file.
Users and groups may be edited in the underlying Settings.json file.
You need to be an administrator with access to the file system to read and change the content of this file. Remember to open an elevated Notepad, or even better, use Notepad++
ActiveDirectoryUsers": [
{
"Name": "DOMAIN\\JohnDoe"
},
{
"Name": "DOMAIN\\JaneDoe"
}
],
"ActiveDirectoryGroups": [
{
"Name": "DOMAIN\\administrators"
}
]
Package Management
The package management feature allows you to:
You can download and remove previously downloaded packages that are no longer in use from within the Nodinite Install and Update Tool. First, click on the Package Management button from the page loaded from the Instances main menu item.
Remove Package
You can list and remove previously downloaded Packages from within the Packages tab:
List of previously downloaded Packages with versioning information.
Manage Files
At the bottom of the page, there is a list of backup files that the Nodinite Update Service keeps (the last 2 are kept automatically). If your installation/update is successful, you can opt to clean up these files.
- Manage files - displays the files and size in total
- Refresh - Click this button to refresh the list
- Remove All - Click this button to remove all backup files
- Restore backup - Click this button to stop the IIS App Pool, remove the current installation, then replace the files, then restart the IIS App pool
- Download - Click this button to download the zip file
- Remove - Click this button to remove the specific zip file
Download package
You must first download a package to either Install or Update.
The Nodinite Core Services comes as a single zip file. There are two ways to download a version of Nodinite into the Nodinite Install and Update Tool:
- This option requires Internet access from the server hosting the Nodinite Install and Update Tool.
- Add Manually - Download to the local file system (including external media like USB...).
- Once manually downloaded, you then need to Upload the ZIP file.
The currently installed version of Nodinite is printed in the Web Client; read more in the Nodinite Version user guide.
1. Download from the Internet
The selected version and its accompanying Release Notes forNodinite are displayed in the panel to the right.
- Click the Download package button to download from the Internet.
Download a new Nodinite version directly from the Internet.
To download from the Internet, the following addresses must be whitelisted in your firewall (TCP port 443):
Also, it would be handy if you could access the Nodinite portal:
Step 2: Continue with either Install or Update
2. Add Manually
For Nodinite instances without any access to the Internet, you must manually download a Nodinite release from another host with access to the Internet. This option is standard for installing a Preview or Release Candidate for a POC.
Example of the 'Add Manually' tab.
- Make sure you have a Nodinite ZIP file, or download it from the Nodinite Portal.
- Click the Browse button and select the Nodinite package to Upload.
- Select the file to upload from the local file system.
- Click the Upload button to start the upload.
- This operation may take a few seconds because the content of the ZIP file is first validated and then extracted.
- When the download completes, you should see the following alert on the screen:
Now, you can continue with either an Installation or an Update:
Install a new instance of Nodinite
You can install new instances of Nodinite using the Nodinite Install and Update Tool. Follow the steps in the Installing and Configuring - Nodinite user guide to get Nodinite installed and configured for first use.
If all prerequisites are met, you should now only be 15-30 minutes away from running your Nodinite instance.
Update an existing instance of Nodinite
Before executing the Update, ensure you have downloaded the latest version of the Nodinite Core Services.
Always use the latest version of the Nodinite Install and Update Tool; see Release Notes for more information.
Existing instances of Nodinite are updated using the Nodinite Install and Update Tool. An Update operation always uses the highest version from the list of uploaded packages. It's only possible to perform an Update to a higher version; you can not downgrade.
You can change the name of the Customer in the list of instances if you click the Edit button.
Use the Action button to perform operations on the Environment.
- Details - Navigate to the details page
- License - Manage the license
- Manage System Parameters
- Manage BizTalk Server Logging
- Remove - Remove this instance from the update tool. NOTE: This operation merely removes the entry, you still need to Uninstall!
Step 1: Select Environment
Begin with selecting the instance to Update:
- Click the environment name to update
- Or Click the Action button and select the Update menu item
List of available instances to update
There can be multiple instances to manage from the list of installed Nodinite instances. There is one table for each Customer.
Step 2: Review Update
Next, a summary of installed components eligible for an update is present in the table.
We aim hard to only release an update of the Log Databases for major releases (features), never to minor builds (bugs). If you need to update the Log Databases; please follow step 3.
| Application Update | Database and Application Update |
|---|---|
 |
 |
- There is an Update available for the Configuration Database. In step 4 the database is automatically updated by the system. Usually, you should not need to perform a manual update.
If there is a problem updating the database or you want to update it manually, follow the How to manually update database user guide.
- No update is available for the Log database since the Manual Update button does not exist. The '...' button is available to help you get the script if you need it.
If there is an update available, please review step 3.
- There is an Update available for the Nodinite Log API.
- Click the Update All button to open the update modal.
The Update all button is only enabled when and if a higher package version exists; please review the Download Package step.
Step 3: Manage Log Databases
If there is an update to the Log databases; then, you must always first update these manually using the provided scripts. There is also more to read in the How to manually update database user guide.
If there is an update to the Log databases; click on the Manage Log Databases Log Databases button:
Follow the steps in the guide to manually update the Log databases.
You can also verify if there is a need to update the Log databases in step 3. If there is nothing to update, please close this page and return to step 4.
New 6.0.0.65 From time to time, we change the indexing scheme and apply this as an optional update. You can apply this update by clicking on the Ignore Version Differences checkbox. Run the scripts to make sure you are using the latest definitions. Doing so may drastically improve the performance and reduce IO for SQL Server.
TIP: If the database is in FULL recovery mode You can temporarily change to SIMPLE recovery mode to speed up the update process.
Step 1: Stop Logging/Monitoring Services
Turning the services off before starting is recommended to make sure they aren't writing to the databases.
Click the Stop button to stop the Logging- and the Monitoring Service.
Example with stopped Services.
Click the Next button to proceed to the next step.
Step 2: Put all archive databases into read-only mode
Click the Read-Only button to put all Archive Log databases into read-only mode.
Click the Next button to proceed to the next step.
Step 3: Command line scripts
There are scripts available to update all the Log databases.
- Active - the panel to the left. This is always just one database.
- Archive - the panel to the right. There can be many archive databases.
Copy the script(s) and run in a CMD-prompt using the same account as the Logging Service. Then, repeat the operation using the scripts for both the Active and Archive Log Databases.
Click the Next button to proceed to the next step.
Step 4: Set archive databases back from read-only mode
When all Log Databases are up to date, click on the Unset read-only mode button.
Click the Next button to proceed to the next step.
Step 5: Restart services
Click the Start button to start the Logging- and the Monitoring Service.
The services should promptly start and display with green icons.
Click the Next button to proceed to the next step.
Step 6: Continue updating Nodinite
Click the back to the previous page link to return to the instance view from where you can continue the update by clicking on the Update all button.
Step 4: Perform Update
Now that all your Log Databases are up to date, you can initialize the update process. For each account in use for the Core Services, you must provide its password.
Advanced tab
Different versions of the SqlPackage (DacFX) use different parameters to connect to the SQL Server. Please review the SqlPackageParams System Parameter for additional details on this topic.
SSL Options for connecting with the SQL Server instance.
NOTE: Any changes are stored in the SqlPackageParams System Parameter upon a successful update.
Update steps
- Select the version to update to (by default, the highest available version is pre-selected)
If you perform manual updates to any of the databases in the previous steps, then make sure to select and verify the SAME version in this dialogue is selected
Enter the password for the installation/service account(s) and click on the Validate Account button.
Example: Enter the 'Password' for the account in use to perform the installation.When all accounts are validated, you can initialize the Update process by clicking on the Update Nodinite button
Example: All fields validatedA progress bar will be displayed; wait for the Update to finish (usually takes between 15 seconds and 3-5 minutes, depending on current workload, often the longest time for the update is to gracefully stop processes with work in progress).
When completed successfully, click the Close button
Congratulations, Nodinite is now up to date.
You can subscribe to new releases using the Nodinite Portal
Manage BizTalk Server Logging
Add and Remove Microsoft BizTalk Server Logging Agents is detailed in the 'Configure Microsoft BizTalk Server Logging Agent' user guide.
Manage System Parameters
Each instance of Nodinite has its own set of System Parameters. Please read the 'How do I change the System Parameters' user guide to change these.
Manage License
To manage the License, click on the Manage License button:
From within this page, you can edit the following properties:
- Customer Name
- Product Key
When you click the Save button, the page's heading information is updated, and the License gets validated. This feature helps you visually detect when the product key is about to expire.
The ability to modify the license, as documented in this section, was introduced with the 5.2 release. For example, if your list of Nodinite instances has the following icon displayed, simply open the manage license page and click on the Save button.
Example of license as displayed after updating to 5.2.
Next Step
- Install a new instance of Nodinite
- Install and Update Log Agents
- Install and Update Monitoring Agents
- Administration