Preparing a property file

For the vendors who are tested with ION, example property files are provided as part of the downloaded JMSBundlewrapper zip file in this folder: \JMSClientBundleWrapper\examples\[Vendor Name]. For example, C:\temp\JMSClientBundleWrapper\examples\IBMWMQ.

For other vendors, you must create a property file based on the template that is provided in: \JMSClientBundleWrapper\examples\Others. For example, C:\temp\JMSClientBundleWrapper\examples\Others.

Specify these properties in the properties.txt file:

InstallPath

Specify the absolute path where the zip file is unzipped. The default value is C:\temp\JMSClientBundleWrapper.

Note: If you change this path, you must also change the localRepository property in this file: \JMSBundleWrapper\build\settings.xml

Example:

InstallPath=C:\mylocation\JMSBundleWrapper

OriginalJar

Specify the file name of the jar that was copied to the OriginalJar folder.

Example:

OriginalJar= com.infor.ion.ibmmq-7.1.0 jar

BundleSymbolicName

Specify a unique identifier for a bundle, based on the reverse domain name convention. This convention is also used by the Java packages.

Example:

BundleSymbolicName= com.infor.ion.ibmmq

BundleVersion

Specify the version to be used for the OSGi bundle.

A version must be of this format:

positiveInteger (.positiveInteger (.positiveInteger))-(buildNr|qualifier)

The first three positions must be a positive integer.

We recommend that you use the JMS server version.

Example:

BundleVersion=7.1.0

BundleName

Specify any short human-readable name for the OSGi bundle to be created for the JMS Client.

Example:

BundleName= com.infor.ion.ibmmq

BundleDescription

Specify a description for the OSGi bundle to be created for the JMS Client.

Example:

BundleDescription=IBM MQ

JMSProviderCode

This name is displayed together with the version in ION.

Example:

JMSProviderCode = IBMWMQ

SpringBeanId

Specify a unique identifier accross all custom wrapper (JMS & Dynamic JDBC) projects.

Example: SpringBeanId = jmsTibcoClientImpl