Device Manager 1.8.0.1 Fix Pack 1 README

Last updated: November 28, 2005

This document contains information for Device Manager Version 1.8.0.1 Fix Pack 1.

This Readme includes the following information:

Updates included with this Fix Pack
Installing the Product Update tool
Installing Device Manager 1.8.0.1 Fix Pack 1
Verifying the version of Device Manager
Removing the Device Manager 1.8.0.1 Fix Pack 1
Trademarks

Updates included with this Fix Pack

This Fix Pack includes corrections for the following problems:

Device Manager Information Center updated (in English) at

http://publib.boulder.ibm.com/infocenter/wedmInfo/v6r0/index.jsp

Multiple submitted job entries in job progress table when a device enrolls and Device Manager is creating thousands of devices
Event messages containing spaces cannot be received
Additional tracing messages added to the message log
Multiple event messages sent on registerForJobCompletion Administration API method
In some cases when the following sequence of jobs occurs in the same session:
1. Successful software distribution job.
2. Successful software removel job.
3. Unsucessful software removal job because the Application URL within the package file does not exist on the server.
you may receive the following misleading Job Progress message after the unsucessful software removal job:
```
Error, not enough space on the device to accept a job size 
of zero.
```
Solution: Run the second software removel job in a separate session and you will receive a "missing Application URL" message .
Add %OWNER% keyword substitution support for Symbian OS devices
Device Manager Administration API samples will not compile
Device Manager API error when creating a job that contains a list of thousands of devices
Enrollment URL now uses instHostName configuration parameter value
InteractiveJobs queue connection fails during start-up; messaging engine now started first
Software removal jobs on Windows Mobile Version 5.0 not working
Remove the batch deletion for expired jobs; perform the deletion one at a time
Device Manager Administration commands not working on computers with Solaris operating system
Device Manager Administration command cannot create an SMSGateway device
Device Manager Administration commands on AIX do not return a non-zero return code when there is an error
Queries that use 3 or more registry parameters do not work
Query strings that are longer than device value should fail, but are recorded as a successful query match
A connection query using NOT EXISTS with a registry parameter fails on Windows CE devices
Connection queries using APPLICATION_VIEW_WINCE with Windows Mobile 2003 for Smartphone fail
Registry data values not compared correctly for a connection query against the registry data
Update stress agent and internal HTTP notification handler
Out of Memory and notification failure during job with thousands of devices
Notification processing could stop completely during an error condition
For Nokia devices, the URL to the SIS file is built incorrectly

Return to top

Installing the Product Update tool

Device Manager Fix Pack 1 requires the Product Update tool, which is included with the Device Manager Fix Pack.

The Product Update tool creates a backup of your configuration in case you need to remove the Fix Pack later. Before you install this Fix Pack, verify that you installed IBM® WebSphere® Everyplace® Device Management, Version 6.0.

To install the Product Update tool, complete the following steps:

Open a command prompt and create a new directory (update_home) for the Product Update tool. Use the following directory locations for the update_home directory:
Windows:
```
C:\Program Files\IBM\Updatertool
```
AIX or Linux:
```
/usr/IBM/Updatertool
```
Solaris:
```
/opt/IBM/Updatertool
```
Copy the Product Update tool ZIP file, ProductUpdateInstaller60.zip, to the directory (update_home) you just created.
Unzip the ProductUpdateInstaller60.zip file.

Return to top

Installing Device Manager 1.8.0.1 Fix Pack 1

Fix Pack 1 requires that you install the Product Update tool.

The Fix Pack should be applied where the Device Manager product root was installed and configured. If Device Manager was installed to the Deployment Manager, then you install the Fix Pack at the Deployment Manager.

Before you install this Fix Pack, verify you have enough disk space:

100 MB disk space for the ZIP file and the extracted files.

4 MB of disk space in the dms_home directory, such as

/usr/IBM/DeviceManager

/opt/IBM/DeviceManager

C:\Program Files\IBM\DeviceManager

Installing the Fix Pack

To install the Fix Pack, complete the following steps:

Open a command prompt and change to the update_home directory, such as:
Windows:
```
C:\Program Files\IBM\Updatertool
```
AIX or Linux:
```
/usr/IBM/Updatertool
```
Solaris:
```
/opt/IBM/Updatertool
```
AIX, Linux, or Solaris only: Use the following command to change the file permissions of the scripts:
```
chmod +x update*.sh
```
Copy the Fix Pack JAR file, DMS_PTF_1801.jar, to the directory that contains the Product Update tool (update_home).
Set the JAVA_HOME environment variable.
Each time you open a new command prompt, you need to set the JAVA_HOME environment, so if you are performing these steps on multiple computers, make sure to set the JAVA_HOME variable.
1. Open a command prompt window.
2. Change directory to the was_home/bin directory, where was_home is the installation directory of the WebSphere Application Server on the computer.
3. Issue the appropriate command:
  Windows:
```
setupCmdLine.bat
```
  AIX, Linux, or Solaris:
```
. ./setupCmdLine.sh
```
  Note: When running this command in a AIX, Linux, or Solaris shell, be sure to use the syntax " . ./setupCmdLine.sh ". If you do not precede the command with the period and space, the Java environment will not be properly set for the active shell.
Stop the Device Manager servers.
Change to the was_home /bin directory, where was_home is the installation directory of the WebSphere Application Server is running.

Windows:
```
stopServer.bat DMS_AppServer -user was_admin_userid -password was_admin_password
```
AIX, Linux, or Solaris:
```
./stopServer.sh DMS_AppServer -user was_admin_userid -password was_admin_password
```
Run the preUpdate command.
Navigate to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

Windows:
```
preUpdate -user was_username -password was_password
```
AIX, Linux, or Solaris:
```
./preUpdate.sh -user was_username -password was_password
```
Open a command prompt and change to the update_home directory, such as:
Windows:
```
C:\Program Files\IBM\Updatertool
```
AIX or Linux:
```
/usr/IBM/Updatertool
```
Solaris:
```
/opt/IBM/Updatertool
```

Install the Fix Pack files using the Product Update tool.

Note: The commands shown below spans multiple lines for clarity, but the command begins with updateProduct and must be entered on a single line.

For example:

updateProduct -fixpack -installDir "dms_home"
-fixpackDir "update_home"
-install -fixpackID DMS_PTF_1801
-productID DMS -productVersion 1.8.0.0

Where dms_home represents the full path to the installation directory of Device Manager server.

Windows example:

updateProduct -fixpack -installDir "C:\Program Files\IBM\DeviceManager" 
-fixpackDir "C:\Program Files\IBM\Updatertool" 
-install -fixpackID DMS_PTF_1801
-productID DMS -productVersion 1.8.0.0

AIX or Linux example:

./updateProduct.sh -fixpack -installDir "/usr/IBM/DeviceManager" 
-fixpackDir "/usr/IBM/Updatertool" 
-install -fixpackID DMS_PTF_1801
-productID DMS -productVersion 1.8.0.0

Solaris example:

./updateProduct.sh -fixpack -installDir "/opt/IBM/DeviceManager" 
-fixpackDir "/opt/IBM/Updatertool" 
-install -fixpackID DMS_PTF_1801
-productID DMS -productVersion 1.8.0.0

Run the postUpdate command.
Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

Windows:
```
postUpdate -user was_username -password was_password
```
AIX, Linux, or Solaris:
```
./postUpdate.sh -user was_username -password was_password
```
Start the Device Manager servers.
Change to the was_home /bin directory, where was_home is the installation directory of the WebSphere Application Server is running, then use the startServer command file.

Windows:
```
startServer.bat DMS_AppServer -user was_admin_userid -password was_admin_password
```
AIX, Linux, or Solaris:
```
./startServer.sh DMS_AppServer -user was_admin_userid -password was_admin_password
```
Navigate to the dms_home/config directory. Run the following DMSconfig command.
Note: If your configuration file is not named DMSconfig.properties, use the -file your_config_file_name parameter in place of the -file DMSconfig.properties parameter in the examples below.

Windows example:
```
DMSconfig.bat -target dms-console-repackage -file DMSconfig.properties
```
For Windows, make sure the properties file identified by the -file parameter exists. If the properties file does not exist, no error message is displayed.

AIX, Linux, or Solaris example:
```
DMSconfig.sh -target dms-console-repackage -file DMSconfig.properties
```
Result from the DMS config command:

If the HTTP server is on a remote computer, then the DMconsole.zip file is copied to the dms_home/www/dms/console directory.

If the HTTP server is on the local computer, then the DMSconfig command creates the DMconsole.zip file in the IBM_Http_Server\htdocs\language_code\dms\console directory, such as:
Windows example:
```
C:\Program Files\IBMHttpServer\htdocs\en_US\dms\console
```
AIX or Linux example:
```
/usr/IBMHttpServer/htdocs/en_US/dms/console
```
Solaris example:
```
/opt/IBMHttpServer/htdocs/en_US/dms/console
```
You must reinstall the Device Manager console on all computers where the console is installed. Go to
```
http://server_host_name/dmserver/DMconsole
```
and follow the instructions.

Return to top

Verifying the version of Device Manager

After you have applied the Device Manager Fix Pack, you can verify the version using the update tool.

Set the JAVA_HOME environment variable.
1. Open a command prompt window.
2. Change directory to the was_home/bin directory,
  where was_home is the installation directory of the WebSphere Application Server, such as:
  
  Windows:
```
C:\Program Files\WebSphere\AppServer\bin
```
  AIX or Linux:
```
/usr/IBM/WebSphere/AppServer/bin
```
  Solaris:
```
/opt/IBM/WebSphere/AppServer/bin
```
3. Issue the appropriate command:
  Windows:
```
setupCmdLine.bat
```
  AIX, Linux, or Solaris:
```
. ./setupCmdLine.sh
```
  Note: When running this command in a AIX, Linux, or Solaris shell, be sure to use the syntax " . ./setupCmdLine.sh ". If you do not precede the command with the period and space, the Java environment will not be properly set for the active shell.
Change to the update_home/puibin directory, where update_home is the installation directory of the WebSphere Everyplace Device Management update tool, such as:
Windows:
```
C:\Program Files\IBM\Updatertool\puibin
```
AIX or Linux:
```
/usr/IBM/Updatertool/puibin
```
Solaris:
```
/opt/IBM/Updatertool/puibin
```
Set the PUI_PRODUCT_HOME environment variable using the following command, where dms_home is the installation directory of Device Manager server:
Note: When providing the path for the PUI_PRODUCT_HOME environment variable, you must not place quotes around the path.

Windows:
```
set PUI_PRODUCT_HOME=dms_home
```
Windows example:
```
set PUI_PRODUCT_HOME=C:\Program Files\IBM\DeviceManager
```
AIX or Linux:
```
export PUI_PRODUCT_HOME=/dms_home
```
AIX or Linux example:
```
export PUI_PRODUCT_HOME=/usr/IBM/DeviceManager
```
Solaris:
```
export PUI_PRODUCT_HOME=/dms_home
```
Solaris example:
```
export PUI_PRODUCT_HOME=/opt/IBM/DeviceManager
```
Run the following command from the update_home/puibin directory to display the current version for the Device Manager server:
Windows:
```
puiVersionInfo.bat
```
AIX, Linux, or Solaris:
```
chmod +x pui*.sh
./puiVersionInfo.sh
```
Look for the Installed Product topic of the information that is printed to the screen. Verify the Device Manager version as 1.8.0.1.

Return to top

Removing the Device Manager 1.8.0.1 Fix Pack 1

To remove Device Manager 1.8.0.1 Fix Pack 1, do the following steps:

Set the JAVA_HOME environment variable.
Each time you open a new command prompt, you need to set the JAVA_HOME environment, so if you are performing these steps on multiple computers, make sure to set the JAVA_HOME variable.
1. Open a command prompt window.
2. Change directory to the was_home/bin directory, where was_home is the installation directory of the WebSphere Application Server on the computer.
3. Issue the appropriate command:
  Windows:
```
setupCmdLine.bat
```
  AIX, Linux, or Solaris:
```
. ./setupCmdLine.sh
```
  Note: When running this command in a AIX, Linux, or Solaris shell, be sure to use the syntax " . ./setupCmdLine.sh ". If you do not precede the command with the period and space, the Java environment will not be properly set for the active shell.
Stop the Device Manager servers.
Change to the was_home /bin directory, where was_home is the installation directory of the WebSphere Application Server is running.

Windows:
```
stopServer.bat DMS_AppServer -user was_admin_userid -password was_admin_password
```
AIX, Linux, or Solaris:
```
./stopServer.sh DMS_AppServer -user was_admin_userid -password was_admin_password
```
Run the preUpdate command.
Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

Windows:
```
preUpdate -user was_username -password was_password
```
AIX, Linux, or Solaris:
```
./preUpdate.sh -user was_username -password was_password
```
Open a command prompt and change to the update_home directory, such as:
Windows:
```
C:\Program Files\IBM\Updatertool
```
AIX or Linux:
```
/usr/IBM/Updatertool
```
Solaris:
```
/opt/IBM/Updatertool
```
AIX, Linux, or Solaris only: Use the following command to change the file permissions of the scripts:
```
chmod +x update*.sh
```

Remove the Fix Pack 1 files using the Product Update tool.

Note: The command shown below spans multiple lines for clarity, but the command begins with updateProduct and must be entered on a single line.

For example:

updateProduct -installDir "dms_home"
-fixpack -uninstall -fixpackID DMS_PTF_1801 
-fixpackDetails

Where dms_home represents the full path to the installation directory of Device Manager server.

Windows example:

updateProduct -installDir "C:\Program Files\IBM\DeviceManager" 
-fixpack -uninstall -fixpackID DMS_PTF_1801 
-fixpackDetails

AIX or Linux example:

./updateProduct.sh -installDir "/usr/IBM/DeviceManager" 
-fixpack -uninstall -fixpackID DMS_PTF_1801
-fixpackDetails

Solaris example:

./updateProduct.sh -installDir "/opt/IBM/DeviceManager" 
-fixpack -uninstall -fixpackID DMS_PTF_1801
-fixpackDetails

Run the postUpdate command.
Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

Windows:
```
postUpdate -user was_username -password was_password
```
AIX, Linux, or Solaris:
```
./postUpdate.sh -user was_username -password was_password
```
Start the Device Manager servers.
Change to the was_home /bin directory, where was_home is the installation directory of the WebSphere Application Server is running.

Windows:
```
startServer.bat DMS_AppServer -user was_admin_userid -password was_admin_password
```
AIX, Linux, or Solaris:
```
./startServer.sh DMS_AppServer -user was_admin_userid -password was_admin_password
```
Navigate to the dms_home/config directory. Run the following DMSconfig command.
Note: If your configuration file is not named DMSconfig.properties, use the -file your_config_file_name parameter in place of the -file DMSconfig.properties parameter in the examples below.

Windows example:
```
DMSconfig.bat -target dms-console-repackage -file DMSconfig.properties
```
For Windows, make sure the properties file identified by the -file parameter exists. If the properties file does not exist, no error message is displayed.

AIX, Linux, or Solaris example:
```
DMSconfig.sh -target dms-console-repackage -file DMSconfig.properties
```
Result from the DMS config command:

If the HTTP server is on a remote computer, then the DMconsole.zip file is copied to the dms_home/www/dms/console directory.

If the HTTP server is on the local computer, then the DMSconfig command creates the DMconsole.zip file in the IBM_Http_Server\htdocs\language_code\dms\console directory, such as:
Windows example:
```
C:\Program Files\IBMHttpServer\htdocs\en_US\dms\console
```
AIX or Linux example:
```
/usr/IBMHttpServer/htdocs/en_US/dms/console
```
Solaris example:
```
/opt/IBMHttpServer/htdocs/en_US/dms/console
```
You must reinstall the Device Manager console on all computers where the console is installed. Go to
```
http://server_host_name/dmserver/DMconsole
```
and follow the instructions.

Return to top

Trademarks

IBM, WebSphere, and Everyplace are registered trademarks of the IBM Corporation in the United States, other countries, or both.

Microsoft, Active Directory, Exchange, Pocket PC, Internet Explorer, Windows, Windows 2003, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

Return to top

(c) Copyright International Business Machines Corporation 1994, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.