Software environments

This section describes the software that you need to have installed to be able to create and run WebSphere MQ Everyplace applications.

Supported platforms

You can install WebSphere MQ Everyplace on certain server platforms only. To transfer programs and Java classes to other platforms, you must use an appropriate download or file transfer program (not supplied).

Note:
You can install the C Bindings, the Native C Client, and Palm support only on platforms marked * in the following lists.

Directly supported platforms with installation support

You can install the product using the built-in tools on the following supported platforms:

Directly supported platforms without installation support

The following platforms are supported for the testing and deployment of WebSphere MQ Everyplace, but only support installation by file transfer from another platform:

Indirectly supported platforms
You can use the following platforms, but IBM will only investigate problems if the problem can be reproduced on one of the directly supported platforms listed above:

Java environment

Running the Java APIs requires one of the following Java runtime environments:

* These items are duscussed in more detail below.

WebSphere MQ bridge operation requires WebSphere MQ Everyplace Classes for Java. You can download the WebSphere MQ Everyplace Classes for Java as SupportPac ma88 from the IBM WebSphere MQ Web site at http://www.ibm.com/software/mqseries/everyplace/. You should check the level of Java that is required to run the version of MQSeries Classes for Java that you are using.

PersonalJava

You can use PersonalJava instead of other Java runtimes on device platforms.

Using WebSphere MQ Everyplace requires the following optional classes of PersonalJava:

The WebSphere MQ Everyplace examples require some of the optional classes in packages java.io and java.awt.

J2ME

WebSphere MQ Everyplace is compliant with the J2ME technologies, Connected Limited Device Configuration (CLDC) and Connected Device Configuration (CDC), or more explicitly their most popular profiles, CDC/Foundation and CLDC/Midp.

Using CDC/Foundation enableS the full functionality of WebSphere MQ Everyplace, excluding any example code requiring the awt gui package. The use of CLDC/Midp, however, restricts the application to solely 'client' side behaviour and a limited range of built-in compressors and encryptors.

Note:
Devices that are CLDC/Midp enabled might have severe memory limitations that can preclude the direct use of the WebSphere MQ Everyplace core package.

Websphere Studio Device Developer

Websphere Studio Device Developer (WSDD) provides a Java IDE together with runtime environments for many different device platforms. WSDD includes WebSphere Micro Environment for developing J2ME applications and supports WebSphere Custom Environment for developing applications for realtime control systems and other devices in closed systems.

You can develop applications using WebSphere MQ Everyplace in the Websphere Studio Device Developer .IDE and deploy those applications using the runtime environments. WebSphere MQ Everyplace requires the use of the jclMidp class library, or higher.

C Bindings Environment

The C Bindings APIs require:

The C Bindings cannot be used with Personal Java or VisualAge Micro Edition.

Storage requirements

The following table shows the storage you need to perform the installation of all the available options of WebSphere MQ Everyplace:

Table 1. Storage required to perform installation

Operating system Storage required
Windows NT (file system = NTFS) 40Mb
AIX 27Mb
Solaris 27Mb
Linux 27Mb
HP-UX 27Mb


© IBM Corporation 2002. All Rights Reserved