© Copyright 2006 Hewlett-Packard Development Company, L.P.
This document provides the release notes for the HP
TP Desktop Connector Version 5.0 product. These
release notes describe known problems with this
product, and include hints and suggestions to help
you use this product.
Programming Automation Clients Controlling Client Connections Using the ACMS Gateway Adapter Using the HP TP Web Connector Gateway for ACMS Using the TPware Management Utility Registering and Unregistering Automation DLLs Interpreting Runtime Error Codes
For notifications on future updates or changes to the HP TP Desktop Connector product kits, refer to the following website:
http://h71000.www7.hp.com/commercial/tpwebconnector.
In addition to these release notes, also refer to the
following TP Web Connector documents:
Online Guides:
Online help:
The following sections describe installation notes. If
the release note reflects a problem logged in the Problem
Tracking and Reporting System (PTR), then the PTR number is
listed in the description.
Workaround: Delete the program folder and/or product
files using the Windows Explorer.
Workaround: Prior to installing any TPware ECOs or
additional TPware products, all TPware applications
and TPware product processes must be shutdown. If this
error continues, then reboot the system and repeat the
installation.
Workaround: Correct the problem and then perform a
reinstall.
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\ACMSDA Settings
(for the ACMS settings)
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\Group Settings
(for the Threads settings)
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\Share Settings
(for the Sharing settings)
To restore the registry settings after you re-install,
do the following:
Note:
For more information on pre-requisites and installation instructions, refer to the README file.
There are no problems fixed in this release.
Following are the problems fixed in this release:
The following problems were fixed in releases prior to
Release 1.2A:
Following are the known Problems with this release:
The TPWARE installation has been overhauled and many
currently unsupported products have been removed
from the kit (a notable example is ACMSxp, which
is now retired). Still there may be some traces
of these products in the installation tree, which
are not functional, but still get copied during the
Installation.
There is no new restriction in this release.
The following general notes apply to this release:
Workaround: Do not mix ISAPI and Automation DLLs in the
same process.
For example, if a group named "add_task_group" has a
limit of 10 threads, and there are two processes that
call add_task_group, then each process creates up to
10 worker threads (20 total), but only 10 threads are
allowed access to add_task_group's server.
Workaround: Upgrade to Internet Explorer V5.5 or V6.0.
Workaround: Issue a NET STOP IISADMIN or alternatively,
reboot your system.
In a user program, if einfo.h is included before windows.h
and a message header file is then included, compilation
errors occur. (PTR 64-4-4)
Workaround: Include windows.h before einfo.h.
The following notes apply to Automation clients:
Workaround: For X/Open or MIA Syntax: Make sure embedded
records in the same task or processing group have
unique field names. For X/Open Syntax only: Declare the
embedded records as separate datatype, then reference
the user-defined type in the field definition.
For example, the following is invalid syntax for Automation adapter:
The following is valid X/Open syntax for Automation adapter:
The following notes apply to Java clients:
When building a Java input adapter from the command
console under the Microsoft environment, the environment
variable STDL_JAVA_MS has to be defined to be a non-
null value. When STDL_JAVA_MS is defined the STDL
compiler will use ,code_example>(jvc.exe) instead of
the normal javac.exe to compile the Java source files.
Microsoft does not provide the Jar utility. The STDL
compiler needs the Jar utility to be available in order
to archive the class files. The Jar.exe utility can be
obtained from the normal Java distribution or one of the
IDEs and made available in the executable path.
To run the Microsoft virtual machine from the command
console, execute jview.exe instead of java.exe.
It is possible to elect to run the Microsoft virtual
machine at runtime while using the normal JDK for
development.
You must ensure that the working directory and a sub
directory used when STDL compiles the Java files matches
the naming of the Java package. For the purpose of
this description, assume that the package is to be
named emp.tpw, the name of the working directory is
C:\dev\emp and the name of the directory that will hold
the Java files during compilation is called tpw. The
Java compilation directory is created under the working
directory, C:\dev\emp\tpw. There will be an additional
temporary directory automatically created by the STDL
compiler alongside the Java compilation directory.
C:\dev\emp // Normal development work directory for the make, stdl
and result files
C:\dev\emp\tpw // Java compilation temporary directory
C:\dev\emp\temp // Automatically generated temporary directory
STDL_JAVA_PACKAGE=emp.tpw
SET CLASSPATH=%classpath%;C:\dev
SET INCLUDE=%include%;C:\dev\emp\tpw
After the Jar file has been created, client programs
can reference the class files in the package by
including the Jar file in the class path and
importing the package. For example, assume the jar
file is named employee.jar:
SET CLASSPATH=%classpath%;C:\dev\emp\employee.jar
Workaround: For X/Open or MIA Syntax: Make sure embedded
records in the same task or processing group have
unique field names. For X/Open Syntax only: Declare the
embedded records as separate datatype, then reference
the user-defined type in the field definition.
For example, the following code is invalid syntax for
Java adapter:
The following is valid X/Open syntax for Java adapter:
When a client uses the ACMS Gateway adapter the connection
established by the client is cached. By default, the
connection is cached for up to 20 minutes of inactivity.
If after 20 minutes the client has not used the connection,
the connection will timeout due to inactivity. This value
can be modified by entering a value in the Windows registry
by using the registry editor. The registry value that needs
to be added is located in the path:
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\Cache Settings
The value that needs to be added is Binding Timeout the
value represents the lifetime in minutes of the connection
following a period of inactivity. If the value is set to
zero the connection is never removed due to inactivity. To
set the Binding Timeout value, do the following:
The following notes apply to the ACMS Gateway adapter:
Workaround: Use the Management Utility and set either
the "Execute call on a separate thread" or "Execute
call on a separate thread, but limit maximum threads to"
execution semantics for the group.
The release notes for the TP Web Connector Gateway for
ACMS component (Version 5.0) are contained in a separate
document within the TP Web Connector Gateway for ACMS
installation procedure and are installed in the following
OpenVMS system directory:
The following note applies to the TPware Management
Utility:
Workaround: Use the Computer tab only at the beginning
of a TPware Management Utility session, make registry
changes, then exit. If you want to use the Computer tab
to connect to and make changes to multiple nodes, it is
required that you exit the utility with "Close" or "OK"
after managing each node.
The following notes apply to the Client Build Utility:
Workaround: Delete the existing DLL before rebuilding.
The following notes apply to the samples provided in the
kit:
There are certain times when the user must unregister and
re-register an Automation server. If you are adding or
removing methods, changing the number or type of arguments,
or changing the fields in a record associated with an
argument, you should unregister the existing Automation
DLL using the regsvr32 -u command before you build the
new DLL. Failure to issue the unregister command using the
exact same DLL that was used when registering can cause the
following problems:
If you forgot to unregister before you built the new DLL
and receive errors when unregistering, then select to
continue if prompted. Next re-register the new DLL. If the
Automation DLL registers successfully the new Automation
interface should be available. If not try unregistering and
registering again.
If you don't re-register an Automation DLL and have
changed any of the information mentioned above, then the
Automation server will not work correctly because the
registered Automation interface will be out of sync with
the Automation interface in the DLL.
If you receive the following error messages when
registering or unregistering an Automation DLL, then check
that the STDL_SYS_DIR environment variable is defined and
in the current path. If you did not reboot after installing
the kit you should do so.
Other than Automation errors as described below, the TP
Web Connector returns error information in einfo.ecode.
These error codes and their descriptions can be found in
the following files:
The stdlrt_msg.h file contains error codes for TPware
runtime exceptions. The range of these errors is 01 to
255 (0x01 to 0xFF).
The acmsda_client_messages.txt text files, found in the
TPWARE\stdl\include directory, document client error codes.
The range of these errors is -3000 to -3199 (0xFFFFF448 to
0xFFFFF381).
Please examine these files to evaluate and respond to
client and/or gateway errors as logged in the ACMS Software
Error log (SWLUP). Also see SYS$HELP:ACMSDA$GATEWAY_
MESSAGES.TXT on the TP Web Connector Gateway system for
ACMS (on OpenVMS) for evaluating gateway error information.
Runtime Automation error values are returned using a 32-
bit number known as a result handle (i.e. HRESULT). The
structure of a HRESULT value is defined by Microsoft.
Automation errors returned by the TP Web Connector start
at 214774989 (0x80041001). These values can be translated
to error codes found in stdlrt_msg.h using the following
formula:
When running the Oracle Web Request Broker samples, the
error "The requested access method is not allowed for
that object" is returned if the virtual path to the web
cartridge does not match the requested path. (Note that the
virtual path for web cartridges is case sensitive.)
© Copyright 2006 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use, or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S.Government
under vendor’s standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additonal warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Microsoft and Windows are US registered trademarks of Microsoft Corporation.
Java is a US trademark of Sun Microsystems, Inc.
Printed in the US
Contents
Preface
Kit Updates
Associated Documentation
Installation Notes
Problems Fixed
Problems Fixed in Version 5.0
Problems Fixed in Version 4.5A
Existing...
Replaced By...
EMPLOYEE_INFO_TASK_GROUP.GDF
EMPLOYEE_WEB_GROUP.GDF
TPWARE_ADD_EMPL_INFO.TDF
EMPLOYEE_WEB_ADD.TDF
TPWARE_GET_EMPL_INFO.TDF
EMPLOYEE_WEB_GET.TDF
TPWARE_PUT_EMPL_INFO.TDF
EMPLOYEE_WEB_PUT.TDF
Problems Fixed in Previous Kits and ECO Releases
Known Problems
Restrictions
General Information
General Notes
Programming C Clients
Programming Automation Clients
TYPE MOVE_REC1 IS RECORD
FLD_1 IS INTEGER;
FLD_2 IS OCTET;
FLD_3 IS RECORD
FLD3_1 TEXT SIZE 7;
FLD3_2 INTEGER;
END RECORD;
END RECORD;
TYPE MOVE_REC2 IS RECORD
FLD_1 TEXT SIZE 8;
FLD_2 DECIMAL STRING SIZE 3;
FLD_3 IS RECORD
FLD3_1 TEXT SIZE 7;
FLD3_2 INTEGER;
END RECORD;
END RECORD;
TYPE USER_TYPE IS RECORD
FLD3_1 TEXT SIZE 7;
FLD3_2 INTEGER;
END RECORD;
TYPE MOVE_REC1 IS RECORD
FLD_1 INTEGER;
FLD_2 OCTET;
FLD_3 USER_TYPE;
END RECORD;
TYPE MOVE_REC2 IS RECORD
FLD_1 TEXT SIZE 8;
FLD_2 DECIMAL STRING SIZE 3;
FLD_3 USER_TYPE;
END RECORD;
Programming Java Clients
import emp.tpw.*; // In client application source file
TYPE MOVE_REC1 IS RECORD
FLD_1 IS INTEGER;
FLD_2 IS OCTET;
FLD_3 IS RECORD
FLD3_1 TEXT SIZE 7;
FLD3_2 INTEGER;
END RECORD;
END RECORD;
TYPE MOVE_REC2 IS RECORD
FLD_1 TEXT SIZE 8;
FLD_2 DECIMAL STRING SIZE 3;
FLD_3 IS RECORD
FLD3_1 TEXT SIZE 7;
FLD3_2 INTEGER;
END RECORD;
END RECORD;
TYPE USER_TYPE IS RECORD
FLD3_1 TEXT SIZE 7;
FLD3_2 INTEGER;
END RECORD;
TYPE MOVE_REC1 IS RECORD
FLD_1 INTEGER;
FLD_2 OCTET;
FLD_3 USER_TYPE;
END RECORD;
TYPE MOVE_REC2 IS RECORD
FLD_1 TEXT SIZE 8;
FLD_2 DECIMAL STRING SIZE 3;
FLD_3 USER_TYPE;
END RECORD;
Controlling Client Connections
Using the ACMS Gateway Adapter
Using the HP TP Web Connector Gateway for ACMS
SYS$HELP:ACMSDA050.RELEASE_NOTES - text version
Using the TPware Management Utility
Using the Client Build Utility
Cannot create a file when that file already exists.
NMAKE: fatal error U1077: 'move'": return code '0x1'
Samples
Troubleshooting Tips
Registering and Unregistering Automation DLLs
LoadLibrary ("
Interpreting Runtime Error Codes
Location of Runtime Error Code Information
<installed-kit>\stdl\include\stdlrt_msg.h
<installed-kit>\stdl\include\acmsda_client_messages.txt
Interpreting Automation Errors
STDL error code = <Automation-error-code-value> - 0x80041000
Running Oracle Web Request Broker