Developer Products - ObjectQ - Release Notes 6.0.5

...... Return to "Release Notes" page ......

1. Introduction

Release 6.0.5 implements one additional feature to Release 6.0.4b - the ability to retrieve MIB files via a URL rather than a file name, so that some or all can be centrally located.

2. New feature

MIB files have previously been stored in a local directory. This carries the inherent danger of similarly named files becoming out of synch at the client and server. It is now possible to retrieve MIB files via a URL, rather than a filename, so that they may be stored in a central repository.

MIB files are specified potentially in two places: using a parameter to the cpInit() function, and in the REGDOMAIN environment variable.

The parameter to the cpInit() function is a directory (or a colon-separated list of directories) which will be searched for appropriately named MIB files (files ending .adf, .edf, .cdf, .sdf, .mdf and .snr). In this release, if the parameter is a URL, it specifies a file that contains a list of URLs of MIB files to be loaded.

If the REGDOMAIN environment variable is set, it specifies a filename from which the Domain Table is populated; if it is not set, the domain data is loaded from a file named regdomain in the current directory. In this release the REGDOMAIN environment variable may also specify a URL from which the domain information is obtained.

For example, the REGDOMAIN environment variable could be set to s or file://localhost/MIBdata/regdomain.

If the parameter passed to cpInit() is file://home/oq-user/files.txt, then the file files.txt could contain:

# Local file
# sftp with username/password
# sftp with public key authentication
# sftp with public key authentication
# Local file
# Anonymous ftp
# Local file

To use sftp, either the username/password must be included in the URL, or, more usually, public/private keys must be created and populated appropriately. Currently supported protocols include file:, ftp:, sftp: and http:. The servers need to be configured to support the authentication method used.

The tarballs contain both the libraries, and two header files that should be installed in the ObjectQ include directory, to replace the ones from Release 6.0.4b. When building applications, libcurl should be included in the list of dependent libraries. If it is not available, substitute the supplied libfcurl to avoid unresolved references.

The man pages, etc. are essentially the same as for Release 6.0.1a - only the libraries have changed. There are libraries for 64-bit Linux, enabled for WebSphere MQ only (since there is no 64-bit library for BEA messageQ) and 32-bit Linux, enabled for both WebSphere MQ and DMQ. For other systems, please contact us.

The ObjectQ log file will indicate the version of ObjectQ against which the application was built. This may also be determined using: strings myapp | grep Version.

3. Questions or Inquiries about this release

As always we welcome your inquiries, comments, suggestions and insight, so please contact us. The engineer responsible for this release is Brian Meekings and can be contacted at:

Information Design, Inc.
Office: (203) 245-0772

For other inquiries: or
Cell: (203) 589-1192 Office: (203) 245-0772 Ext 6212