bottrap

MIB Smithy SDK for Application Developers

March 8th, 2010 by Michael Kirkham

Wanted to use MIB Smithy SDK to develop Tcl/Tk based SNMP applications you can distribute to your customers but User-Based and Host-Based Licensing made that infeasible? There’s an option for that now with the MIB Smithy SDK Developer License (or MIB Smithy SDK “Embedded Edition”).

MIB Smithy SDK Embedded provides all the same features as a regular license for MIB Smithy SDK, but is a special build and Developer License Agreement. Each Developer License grants a single developer a royalty-free license to embed the SDK and distribute it as an integral component of the developer’s applications, and includes a Single User or Single Host License for the normal SDK to use for development and internal use.

When you purchase online or by purchase order, a license and download permissions for both will be added to your account. The Developer License Redistributables available from the Downloads page contains only the files necessary for redistribution so you don’t have the overhead of downloading MIB modules and documentation bundled with the SDK twice.

User-Based Licensing Now Online

March 8th, 2010 by Michael Kirkham

As previously (but quietly) announced, User-Based Licensing was introduced in MIB Smithy SDK 4.0, and subsequently in MIB Smithy 4.2 and MIB Views 1.5. Earlier versions of these products supported only Host-Based Licensing.

Host-Based Licensing permits any user to use the software on a single specified computer, provided it’s used by only one person at a time. This scheme is useful in multi-user environments where use is less frequent, as licenses can be shared in this manner, with the trade-off being limits on how often the license can be transferred to another computer.

User-Based Licensing, on the other hand, permits a single specified user to use the software on any computer, provided it’s used on only one computer at a time. This scheme is useful in environments where a user uses multiple computers or changes computers frequently (such as on a desktop and laptop), with the trade-off being that each user needs their own license.

The User-Based Licensing feature was implemented in these releases, but until now the systems on the web site weren’t set up to handle it. From now on, when initially configuring their license key, new customers can choose whether to designate it as a User-Based or Host-Based License, and whether to use the old license key format (compatible with all versions) or new license key format (compatible with these versions and later) for Host-Based Licenses. The new format includes a couple of freely editable plaintext fields (usually filled in with the product name and serial number) that make it easier for customers with multiple license keys to distinguish them from one another, and gets rid of those BEGIN/END lines people often don’t realize are required parts of the old key format.

Customers who initially purchased their license prior to December 31, 2010 (through end of this year) who are using Host-Based Licenses can elect to permanently convert their keys to User-Based Licenses, provided their support is current, and can now do so online by following link at the bottom of the License Detail page, accessible via serial number link at Manage Licenses. This future cutoff date was chosen to allow for transition time, as some current MIB Smithy SDK users may want to switch to User-Based Licenses, and may wish to acquire additional licenses, but need time to port their scripts or hardware from SDK 3.x to 4.x API and Platform Changes.

After conversion to a User-Based License, you’ll be permitted to continue to use your old Host-Based license key as necessary for migration and script porting, but it may no longer be shared (it must be used only by the newly assigned user) and no further Host ID transfers will be permitted.

The new format looks approximately like this, with the two fields in ||’s editable in any way that helps you keep track of your licenses (except by inserting | characters):

|MIB Smithy Professional - Windows|XXXXXX-XXXXXX-XXXXXX|dcPkYQW
hJeSOYzDPDYvWprYQoaQd9zsoDihw25qLweMriJBDksDQbRuwbHfdprYfIKQdQQ
YjY42AzazjkeNn30s8ygPiOOChK2UveIM4BWNmF2Vg=lyma9fS60Ah9k0JZ02ja

If you’d like to convert your license to the new format, but stay with Host-Based Licensing, please contact support. As with conversion to User-Based, your support must be current (it’s only supported by the above versions of the software).

P.S. No, that’s not a valid license key, so don’t even try. :)

MIB Smithy 4.2 and MIB Views 1.5 Released

March 5th, 2010 by Michael Kirkham

MIB Smithy 4.2 and MIB Views 1.5 are now available. These releases are based on MIB Smithy SDK 4.0, adding IPv6 support, Linux x86_64 support, a username-based licensing option, and many MIB compiler improvements (a full list can be found in the MIB Smithy SDK 4.0 Release Announcement, which also describes changes to supported platforms that apply to these releases as well).

The format used specify OCTET STRING values in hex in the SNMP Query Tool and Agent Settings dialog has changed, in keeping with SDK 4.0’s changes to binary data handling. Instead of prefixing the value with 0x, as in 0x:12:ab:cd, you surround the value in single quotes, as in '12:ab:cd'. However, you can now suppress conversion from hex, treating the value as a literal string (with quotes) by surrounding the value in another pair of single quotes, as in ''12:ab:cd''. Essentially, any string value with surrounding single quotes will have one set of quotes stripped off; if, after stripping, the value looks like colon-delimited hex (without quotes), hex conversion will occur.

Although these releases don’t do much beyond what SDK 4.0 brings, it’s still a significant milestone. Now that MIB Smithy and MIB Views are up to the new SDK version, the holds on new features are lifted, so I can get back to tackling my sizable wish list for these products. First, though, I’ll be working on getting the web site updated to support generating the new username-based license keys and providing access to the Linux x86_64 platform (x86_64 won’t be treated as a unique platform from x86 as far as purchasing and license keys are concerned, but it is a different build/distribution, and the systems aren’t set up yet to handle two different files for a single platform+version).

MIB Smithy SDK 4.0.2 Released

March 3rd, 2010 by Michael Kirkham

This release fixes a minor bug that was introduced in 4.0 that I discovered while getting MIB Smithy ported to the 4.0 SDK, in an API primarily used by MIB Smithy to list the topmost nodes in a module within the Project Tree. It also has one minor new feature to simplify the porting of MIB Smithy and MIB Views. MIB Smithy 4.2 and MIB Views 1.5, based on SDK 4.0, will be available as soon as a few remaining build issues are resolved.

Changes in this release:

2453: smilib get -rootnodes returning no results

The smilib get -rootnodes property for modules was inadvertently broken in SDK 4.0’s rearchitecture such that orphaned records (those with missing or undefined dependencies) were no longer returned in the result.

2458: Add smilib get -format option for OBJECT-TYPEs

smilib get -format can now be used on OBJECT-TYPEs to return the DISPLAY-HINT for the TEXTUAL-CONVENTION referenced by the OBJECT-TYPE’s SYNTAX. This saves the step of having to first look up the SYNTAX.

MIB Smithy SDK 4.0.1 Released

February 25th, 2010 by Michael Kirkham

This release fixes a couple of assertion failures that could occur in some of the new validation rules introduced in the 4.0 release and some licensing issues with Windows, and introduces a new edition of the SDK available for general release soon.

2419: New SDK edition for application developers

A new SDK edition (the MIB Smithy SDK Developer License) was implemented to accommodate developers who which to use the SDK to develop distributable applications.

2412: Error upon redisplaying license dialog

Upon adding a license key to the license dialog that was not accepted, the dialog should be redisplayed. A bug was introduced in 4.0 that cause an “unknown command name” error instead.

2421: Demo license key crashes on Windows

An issue was identified in the new licensing engine for 4.0 that could cause the SDK to crash when given an evaluation license key on Windows.

2282: Assertion failure checking for duplicate members

The SDK could abort during validation with an assertion failure when checking for duplicate members (such as OBJECTS in OBJECT-GROUP) if multiple members were undefined.

2407: Assertion failure validating orphaned read-write OBJECT-TYPE

The SDK could abort during validation with an assertion failure when checking for a mix of read-write and read-create columnar objects when the OBJECT-TYPE’s OID was not fully defined or known.

2409: License key location on Windows Vista/Windows 7

On Windows Vista and Windows 7, the license dialog could fail write license keys to the correct location due to changes in structure and permissions of %ALLUSERSPROFILE%. The default location is now based on %APPDATA%, which is user-specific and more appropriate for user-based licenses.