SlickEdit
SlickEdit is a cross-platform, multi-language source code and text editor. It provides various coding tools and time-saving programming features. SlickEdit 2014 supports over 40 languages across 9 different platforms.
A proprietary license manager licenses and manages SlickEdit usage. To monitor the SlickEdit license manager in OpenLM Platform, track license usage, and collect license statistics, configure OpenLM Broker as follows.
Before you begin
Confirm these prerequisites:
- An OpenLM Platform account
- OpenLM Broker v25.x or higher, installed on the same machine as SlickEdit and approved in Broker Hub.
Configure OpenLM Broker
To configure OpenLM Broker for SlickEdit:
-
Open the Broker UI at
http://localhost:5090/. -
Select License Managers, then Add License Manager.
-
Download and install the latest OpenLM Broker version from the Downloads page.
-
In the Broker, select the license manager node.
-
If Auto-Detect did not find SlickEdit, select Add Port.
-
Configure the Broker to monitor the SlickEdit license server (for example,
slickedit_license_server) on port27100. -
Set the vendor name to
SlickEdit. -
In the Commands node, enter the full path to the
selicutil.exeexecutable, then select Update and Apply. -
Set the SlickEdit commands for Status and Data_inquiry as shown in the following image, replacing
<fullpath>with the actual path toselicutil.exe.
Configuring SlickEdit in the Broker UI -
Select Restart Broker.
You can also configure the Broker through the Broker UI.
Approve SlickEdit in OpenLM Platform
To approve SlickEdit in OpenLM Platform:
- Sign in to OpenLM Platform with the URL your administrator gave you.
- From the menu, select License Servers, then Pending Server.
- Select the SlickEdit license manager, then select Approve and Merge.
Verify the integration
To verify that OpenLM Platform receives data from SlickEdit:
- In OpenLM Platform, select License Servers Live, then Server Statistics.
- Confirm SlickEdit appears with a green status indicator.
It can take up to 3 minutes for the status to update for a connection.
The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.