f)b @5L

HP TP Web Connector V5.0A

Release Notes - July 2006

This document provides the release notes for the HPD TP Desktop Connector Version 5.0A product. TheseC release notes describe known problems with thisF product, and include hints and suggestions to help) you use this product.

Preface

E
Kit Updates
P
Associated Documentation

Installation Notes

Problems Fixed

S
Problems Fixed in Version 5.0A
Q
Problems Fixed in Version 5.0
V
Problems Fixed in Version 4.5A
i
Problems Fixed in Previous Kits and ECO Releases

Known Problems

Restrictions

General Information

E
General Notes
I
Programming C Clients
U
Programming Automation Clients
O
Programming Java Clients
X
Controlling Client Connections
U
Using the ACMS Gateway Adapter
f
Using the HP TP Web Connector Gateway for ACMS
]
Using the TPware Management Utility
W
Using the Client Build Utility
=
Samples

Troubleshooting Tips

e
Registering and Unregistering Automation DLLs
W
Interpreting Runtime Error Codes

X
Location of Runtime Error Code Information
T
Interpreting Automation Errors

Z
Running Oracle Web Request Broker

Preface

Kit Updates

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.@

Associated Documentation

C In addition to these release notes, also refer to the3 following TP Web Connector documents:

Online Guides:

HP TP Web Connector Installation GuideG
HP TP Web Connector Getting Started

Online help:

TPware Management Utility online help
TPware STDL online help
H TPware Client Build Utility Online help

;

Installation Notes

D The following sections describe installation notes. IfG the release note reflects a problem logged in the ProblemI Tracking and Reporting System (PTR), then the PTR number is( listed in the description.

When installing this TPware kit the install procedureC will detect the presence of a previously installedF TPware kit and install the kit in the same directory.
K
If you are upgrading from a previously installed TPwareI kit, all information stored by the TPware management GUI" will be retained.
J
You must shutdown all TPware processes and applicationsG that use TPware prior to the installation of this kit.
J
When upgrading from a previously installed TPware kit,C you will not be asked for product license keys for5 products that are already installed.
K
With this release the TPware management information willG be migrated from HKEY_LOCAL_MACHINE\SOFTWARE\HP\TPwareP to HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware. Once theG migration is complete the TPware key under HKEY_LOCAL_5 MACHINE\SOFTWARE\HP will be removed.
H
If TPware files are lost or damaged once the kit hasI been installed, reinstall the latest TPware kit in order& to restore the files.
L
When installing both the HP TP Desktop Connector VersionF 5.0A and TP Web Connector on the same system, cautionB must be used. Both products allow connectivity toE HP ACMS. With both products installed, HP TP Desktop@ Connector applications that use HP ACMS GatewayB Connector interface will not work. However, HP TPI Desktop Connector applications using the Client ServicesD Interface (formerly known as ACMS Desktop Portable API)" will not be affected.
B
On rare occasions, a TPware product uninstall doesC not delete the TPware program folder and/or associated files.
A Workaround: Delete the program folder and/or product. files using the Windows Explorer.
G
'Error 115' during the installation of a TPware product? indicates that a file is locked and will cause the0 installation to fail. (PTR 64-4-95)
? Workaround: Prior to installing any TPware ECOs or@ additional TPware products, all TPware applicationsC and TPware product processes must be shutdown. If thisC error continues, then reboot the system and repeat the installation.
A
The regsvr32.exe image which is referenced in theB product documentation is not supplied with the TPware@ kit. This is a Microsoft image and must be obtained@ from Microsoft. This file is typically found in the& WinNT\system32 directory.
G
There is only one uninstall procedure. When you run theC uninstall procedure, all the TPware products currently# installed are removed.G
When installing the TPware products in a directory thatC differs from a previous installation, check any of theC user-defined environment variables to ensure that they< are referencing the new installation directory.
>
The installation procedure may run out of disk= space while copying files due to customized disk) configurations. (PTR 64-9-7)
? Workaround: Correct the problem and then perform a reinstall.
A
If you need to uninstall or re-install the TPwareD product and want to save settings defined in the TPwareA Management Utility, perform the following before youD uninstall. Note, this does not have to be done in order% to install a TPware ECO.
1. Click on Start -> Run...1
2. Enter regedit at the Open prompt.4
3. Click Registry on the menu bar.H
4. Select Export Registry File... on the Registry Menu.G
5. Enter a separate file name in the File Name prompt9 for each of the settings to be saved.J
6. In Export range, click on the Selected branch button,< then enter the appropriate registry key:+
  G
  X HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\ACMSDA Settings- (for the ACMS settings)0
  W HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\Group Settings0 (for the Threads settings)W HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\Share Settings0 (for the Sharing settings)
  /
7. Click on the Save button.J
8. Repeat steps 5 through 7 for each of the settings to be saved.

G To restore the registry settings after you re-install," do the following:

Click on Start -> Run...6
Enter regedit at the Open prompt.5
Click Registry on the menu bar.J
Select Import Registry File... on the Registry Menu.G
Enter the file name in the File Name prompt. ThisC should be the same file used in step 5 when the1 registry settings were saved.H
Click on the Open button. You should see a messageA box telling you that the information has been9 successfully entered in the registry.J
Repeat steps 5 through 6 for each of the settings to be restored.

Note:_For more information on pre-requisites and installation instructions, refer to the README file.

Problems Fixed

Problems Fixed in Version 5.0A

There are no problems fixed in this release.

Problems Fixed in Version 5.0

There are no problems fixed in this release.

Problems Fixed in Version 4.5A

? Following are the problems fixed in this release:

Problems while registering EMPLOYEE_ACMS_AUTO.DLL. ThereH were problems in registering the EMPLOYEE_ACMS_AUTO.DLLE due to discrepancies in the .asp files. Due to this,C the .asp files are modified in the employee sample application.K
The name of the EMPLOYEE_INFO_APPL_XXX sample is changed- to EMPLOYEE_WEB_APPL sample.Q

The following table lists the files that are replaced by new & files in the ACMSDA045A.D saveset:

& )
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

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

D The following problems were fixed in releases prior to Release 1.2A:

The ACMS Gateway output adapter would sometimesF incorrectly return the error message -3103 when -3020A should have been returned instead. (PTR 64-8-13)H
If the length of a text field in a record definitionC equaled 1024 and the Java input adapter was being usedE then the compilation of the task group and corresponding; record definition(s) would fail. (PTR 64-8-14)C
The Java adapter was incorrectly converting UnicodeB characters to UTF-8 instead of multibyte format. (PTR 64-9-24)G
The TPware Add sample server code was not the same code> that was in the ACMSxp V3.1 NT kit. (PTR 64-4-20)H
The STDL compiler returned an error if the full pathname? of the STDL file to be compiled contained embedded" spaces. (PTR 64-4-29)E
When interfacing with HP ACMS, floating point numbers? with a high degree of precision were not correctly@ converted from OpenVMS format to Windows NT format. (PTR 64-8-01)E
The Output Adapter drop down list for the client buildB utility did not list the HP ACMS output adapter type. (PTR 64-8-03)G
A client using the HP ACMS Gateway output adapter wouldA spin if the TP Web Connector Gateway was shutdown orB crashed while the client was connected. (PTR 64-8-04)@
The STDL compiler did not properly compile record= definitions that contained embedded records when5 building the Java adapter. (PTR 64-8-11)D
A memory corruption problem has been fixed in the HP7 ACMS Gateway output adapter. (PTR 64-8-12)F
Failure to define RPC_DEFAULT_ENTRY via an environmentE variable or the TPware Management Utility caused the DCE1 NSID process to crash. (PTR 64-9-14)E
If a user was a member of many Windows NT groups, theE TPware management GUI would fail to start. (PTR 64-9-15)D
The MSRPC output adapter did not correctly handle theE selection of multiple servers with the same interface if7 one of the servers was down. (PTR 64-9-16)H
Binding Timeout, if enabled, did not work. (PTR 64-9-17)G
The STDL compiler truncated array names within recordsE that exceeded 25 characters in length. (PTR 64-9-18)G
The STDL compiler allowed numeric characters as theB first character in a STDL '#include' preprocessor4 directive statement. (PTR 64-11-15)

Known Problems

A Following are the known Problems with this release:

Unsupported Product traces
E The TPWARE installation has been overhauled and manyA currently unsupported products have been removedA from the kit (a notable example is ACMSxp, which@ is now retired). Still there may be some tracesB of these products in the installation tree, whichD are not functional, but still get copied during the Installation.

Restrictions

: There is no new restriction in this release.;

General Information

General Notes

@ The following general notes apply to this release:

If you try to use an ISAPI DLL and an Automation DLLH in the same process, the second DLL used for task callsH returns an error code of 0xFFFFF4444 and an error class of -4.
H Workaround: Do not mix ISAPI and Automation DLLs in the same process.G
The number of concurrent connections for the TP WebF Connector Gateway for ACMS should be limited in orderF to reduce the possibility of excessive runtime systemE resource usage. Set the maximum number of threads onG the Threads tab in the Management Utility to limit the: number of concurrent gateway connections.C
If you use the Default group to specify threadsG settings, then any changes made to the Default threadsB settings do not take effect dynamically. You mustG restart any application that uses the Default settings9 in order for the changes to take effect.J
When threads settings are specified for a named group,A all processes accessing the group share a commonE throttle. If a group has "Execute call on a separateC thread, but limit maximum threads" semantics, eachF process that accesses the group will create up to theI specified number of worker threads, but only the maximumD number of threads are allowed through the throttle.
E For example, if a group named "add_task_group" has aF limit of 10 threads, and there are two processes thatE call add_task_group, then each process creates up toF 10 worker threads (20 total), but only 10 threads are; allowed access to add_task_group's server.B
The error log reporting stdlog -b (before) and -s@ (since) switches are not working properly. (PTR 64- 11-17)H
Error logging message to the NT event viewer erroneouslyB display binary characters and may not contain all theD information returned to the client and information thatB is reported via the stdlog error logging utility when@ the STDL_LOG_FILE environment variable is set. (PTR 64-11-18)H
When reading the online version of the product documents? with Microsoft Internet Explorer V3.x, some of the$ hyperlinks do not work.
C Workaround: Upgrade to Internet Explorer V5.5 or V6.0.G
The STDL compiler does not report an error when invalidA communications adapters are used with the -C switch. (PTR 64-4-37)C
A thread leak can occur whenever the WWW service is@ stopped and restarted without stopping the INETINFO process.
D Workaround: Issue a NET STOP IISADMIN or alternatively, reboot your system.

;

Programming C Clients

D In a user program, if einfo.h is included before windows.hA and a message header file is then included, compilation$ errors occur. (PTR 64-4-4)

7 Workaround: Include windows.h before einfo.h.G

Programming Automation Clients

: The following notes apply to Automation clients:

There are certain times when you must unregister andB register an Automation server. Please see the section@ "Registering and Unregistering Automation DLLs" for! further information.C
This version has limited Automation error reporting.B Please see the section on "Interpreting Runtime Error) Codes" for more information.3
Arrays are base 0 in Automation.G
Automation does not support user-defined datatypes.C To handle user-defined datatypes, such as records,F each record must be defined as a separate object. ForI embedded records the software creates an object with theI name _RECORD. If two embedded records in theG same task or processing group file have the same fieldF name, then the software will declare two objects withC the same name. This causes an error. (PTR 64-4-19)
I Workaround: For X/Open or MIA Syntax: Make sure embeddedB records in the same task or processing group haveH unique field names. For X/Open Syntax only: Declare theF 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:

    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;

The following is valid X/Open syntax for Automation adapter:

   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

4 The following notes apply to Java clients:

The Java adapter has been tested using Sun Microsystems' J2SE 1.4.2 SDK.H
Visual J++ Version 6.0 is required to run the Visual J++# Automation Add Sample.;
There is no support for bean serialization.D
Arrays (primitives, strings and objects) in the Java8 adapter are restricted to three dimensions.F
The STDL data type UUID is now converted to and from aC Java String. This change to support the UUID data typeD requires that the Microsoft Visual C library RPCRT4.LIB> is included in the link line when building a JavaB adapter DLL. The RPCRT4.LIB library is needed whetherB or not UUID types are used in the client application.E
The Java input adapter did not work with the Microsoft? virtual machine. With the release of Microsoft SDK= for Java, Version 3.1 there is now the option ofB using the Microsoft compiler and virtual machine. Usew http:\\www.microsoft.com\java\download.htm build 3167? 2/18/99 or later. When installed this version willC provide a development SDK and virtual machine. It willE also update the virtual machine for Visual Studio J++ ifC that product is installed. After the SDK installation,A ensure that the executable path is set to locate theE new jvc.exe and jview.exe images in preference to imagesD from any earlier Microsoft development environment. TheF classpath might also need adjusting to locate the new" classes.zip file.
D When building a Java input adapter from the commandI console under the Microsoft environment, the environmentE variable STDL_JAVA_MS has to be defined to be a non-B null value. When STDL_JAVA_MS is defined the STDLE compiler will use ,code_example>(jvc.exe) instead ofG the normal javac.exe to compile the Java source files.E Microsoft does not provide the Jar utility. The STDLH compiler needs the Jar utility to be available in orderG to archive the class files. The Jar.exe utility can beI obtained from the normal Java distribution or one of the@ IDEs and made available in the executable path.
F To run the Microsoft virtual machine from the command@ console, execute jview.exe instead of java.exe.
E It is possible to elect to run the Microsoft virtualB machine at runtime while using the normal JDK for development.H
This kit supports a workaround to allow the generatedH Java classes to be placed into a package. The followingG is a description of the steps to be taken to allow theI STDL compiler to include the classes in a package. TheseE steps are in addition to the directions for buildingE Java clients provided in the HP TP Desktop Connector' Getting Started guide.
E You must ensure that the working directory and a subI directory used when STDL compiles the Java files matchesC the naming of the Java package. For the purpose ofC this description, assume that the package is to beD named emp.tpw, the name of the working directory isH C:\dev\emp and the name of the directory that will holdE the Java files during compilation is called tpw. TheH Java compilation directory is created under the workingG directory, C:\dev\emp\tpw. There will be an additionalF temporary directory automatically created by the STDLC compiler alongside the Java compilation directory.
1. Manually create the directories. The terminalG directory names in the path have to match the names@ used in the package definition. For example:
  W C:\dev\emp // Normal development work directory for the make, stdl3 and result filesK C:\dev\emp\tpw // Java compilation temporary directoryS C:\dev\emp\temp // Automatically generated temporary directory
  <
2. Define the environment variable STDL_JAVA_@ PACKAGE= in a way that matches the6 Java package directories. For example:
  . STDL_JAVA_PACKAGE=emp.tpw
  G
3. When the java classes are generated they will includeD the named package. In order for the Java compiler toE locate the classes in the package at STDL build time,D the working directory's parent needs to be specified. in the classpath. For example:
  5 SET CLASSPATH=%classpath%;C:\dev
  @
4. In addition to generating class files the STDLA compiler will also generate C include files to be@ used when building the adapter DLL. Add the Java@ compilation directory to the INCLUDE environment> variable to allow the C compiler to locate theB generated include files during the STDL build. For example:
  9 SET INCLUDE=%include%;C:\dev\emp\tpw
  F
5. When the STDL build completes, the generated DLL andD JAR files that are required for the application willB have been moved up into the working directory. TheE normal temporary directory is cleaned up after a STDLE build. This is not the case with the Java compilationD directory. The directory can be cleaned up by addingB to the make file cleanup, a delete of the files in/ the Java compilation directory.
  D 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 andB importing the package. For example, assume the jar+ file is named employee.jar:
  J SET CLASSPATH=%classpath%;C:\dev\emp\employee.jar
  K import emp.tpw.*; // In client application source file
  H
6. Records are defined as separate objects. For embeddedE records the software creates an object with the nameG . If two embedded records in the same taskH or processing group file have the same field name, thenD the software will declare two objects with the same: name. This causes an error. (PTR 64-4-19)
  I Workaround: For X/Open or MIA Syntax: Make sure embeddedB records in the same task or processing group haveH unique field names. For X/Open Syntax only: Declare theF embedded records as separate datatype, then referenceE the user-defined type in the field definition.

F For example, the following code is invalid syntax for Java adapter:

   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;

The following is valid X/Open syntax for Java adapter:

   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

D When a client uses the ACMS Gateway adapter the connection> established by the client is cached. By default, theB connection is cached for up to 20 minutes of inactivity.E If after 20 minutes the client has not used the connection,C the connection will timeout due to inactivity. This valueE can be modified by entering a value in the Windows registryE by using the registry editor. The registry value that needs- to be added is located in the path:

K HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\TPware\Cache Settings

A The value that needs to be added is Binding Timeout theD value represents the lifetime in minutes of the connectionB following a period of inactivity. If the value is set toD zero the connection is never removed due to inactivity. To: set the Binding Timeout value, do the following:

In the registry editor, highlight "Cache Settings".C
Go to the Edit drop down tab and select "add value".G
For the value name, enter Binding Timeout (note space in name).E
For the datatype, select DWORD click on OK and enter a value.A
Restart the client in order for the change to take affect.

Using the ACMS Gateway Adapter

@ The following notes apply to the ACMS Gateway adapter:

The ACMS Gateway adapter does not support the following features:
1. Exchange Steps$
2. Data Compression6
3. SHOW_DESKTOP_USERS Utility Program%
4. Nonblocking Calls,
5. Forced Nonblocking Calls0
6. Client Task Cancel Calls4
7. non-Windows Client Platforms-
8. non-TCP/IP transports*
9. variant data types
G
A stack overflow may occur when accessing ACMS fromH clients within web servers. If this happens, einfo willF contain the following: eclass = -4, ecode = FFFFF444./ (PTR 14) (HP TP Web Connector)
F Workaround: Use the Management Utility and set eitherD the "Execute call on a separate thread" or "ExecuteI call on a separate thread, but limit maximum threads to"3 execution semantics for the group.
I
EINFO is not being cleared after an error occurs. (PTR

Using the HP TP Web Connector Gateway for ACMS

D The release notes for the TP Web Connector Gateway forG ACMS component (Version 5.0A) are contained in a separateC document within the TP Web Connector Gateway for ACMSG installation procedure and are installed in the following' OpenVMS system directory:

2   SYS$HELP:ACMSDA050.RELEASE_NOTES - text version

Using the TPware Management Utility

A The following note applies to the TPware Management Utility:

The TPware Management Utility does not save all changesF before connecting to the next registry. (PTR 64-4-44)
G Workaround: Use the Computer tab only at the beginningF of a TPware Management Utility session, make registryH changes, then exit. If you want to use the Computer tabH to connect to and make changes to multiple nodes, it isH required that you exit the utility with "Close" or "OK"* after managing each node.

# I

Using the Client Build Utility

@ The following notes apply to the Client Build Utility:

The Client Build Utility creates a process that runs> nmake to create the client files. This process is? visible on the desktop as a minimized window icon.@ If nmake runs for 10 minutes without returning, theB Client Build Utility will timeout and return a CreateC Process error. However, the created process will stillC be running. If the application is unusually complex it@ may be a legitimately long build, in which case the? process can be allowed to complete. Otherwise, the@ minimized window should be closed, which terminates the process.
F
Rebuilding an existing Automation client generates the3 following error message. (PTR 64-9-13)
```
6   Cannot create a file when that file already exists.7   NMAKE: fatal error U1077: 'move'": return code '0x1'
```
C Workaround: Delete the existing DLL before rebuilding.

Samples

B The following notes apply to the samples provided in the kit:

The Samples provided in this kit can be found under theB "TPware Products" menu item under the "Programs" menu& item on the "Start" menu.

Troubleshooting Tips

Registering and Unregistering Automation DLLs

G There are certain times when the user must unregister andD re-register an Automation server. If you are adding orI removing methods, changing the number or type of arguments,C or changing the fields in a record associated with anE argument, you should unregister the existing AutomationD DLL using the regsvr32 -u command before you build theH new DLL. Failure to issue the unregister command using theI exact same DLL that was used when registering can cause the! following problems:

The unregister command will not be able to remove all5 associated Windows Registry entries.<
The unregister command will signal errors.

F If you forgot to unregister before you built the new DLLC and receive errors when unregistering, then select toH continue if prompted. Next re-register the new DLL. If theF Automation DLL registers successfully the new AutomationI interface should be available. If not try unregistering and registering again.

A If you don't re-register an Automation DLL and haveF changed any of the information mentioned above, then theC Automation server will not work correctly because theF registered Automation interface will be out of sync with2 the Automation interface in the DLL.

> If you receive the following error messages whenH registering or unregistering an Automation DLL, then checkG that the STDL_SYS_DIR environment variable is defined andI in the current path. If you did not reboot after installing' the kit you should do so.

The dynamic link library stdl_rtm.dll could not be found& in the specified path
```
1LoadLibrary ("") failed!Get Last Error returns 0x0000007e
```
F
Please 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.

Interpreting Runtime Error Codes

Location of Runtime Error Code Information

A Other than Automation errors as described below, the TPA Web Connector returns error information in einfo.ecode.B These error codes and their descriptions can be found in the following files:

2   <installed-kit>\stdl\include\stdlrt_msg.h@   <installed-kit>\stdl\include\acmsda_client_messages.txt

? The stdlrt_msg.h file contains error codes for TPware@ runtime exceptions. The range of these errors is 01 to 255 (0x01 to 0xFF).

A The acmsda_client_messages.txt text files, found in theE TPWARE\stdl\include directory, document client error codes.D The range of these errors is -3000 to -3199 (0xFFFFF448 to 0xFFFFF381).

? Please examine these files to evaluate and respond toE client and/or gateway errors as logged in the ACMS Software> Error log (SWLUP). Also see SYS$HELP:ACMSDA$GATEWAY_A MESSAGES.TXT on the TP Web Connector Gateway system forE ACMS (on OpenVMS) for evaluating gateway error information.D

Interpreting Automation Errors

B Runtime Automation error values are returned using a 32-A bit number known as a result handle (i.e. HRESULT). The? structure of a HRESULT value is defined by Microsoft.B Automation errors returned by the TP Web Connector startC at 214774989 (0x80041001). These values can be translatedB to error codes found in stdlrt_msg.h using the following formula:

F    STDL error code = <Automation-error-code-value> - 0x80041000

Running Oracle Web Request Broker

E When running the Oracle Web Request Broker samples, theC error "The requested access method is not allowed forE that object" is returned if the virtual path to the webI cartridge does not match the requested path. (Note that theA virtual path for web cartridges is case sensitive.)

_Confidential computer software. Valid license from HP required for possession, use, or copying.VConsistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer SoftwareYDocumentation, 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 HPaproducts and services are set forth in the express warranty statements accompanying such productsaand services. Nothing herein should be construed as constituting an additional warranty. HP shallOnot be liable for technical or editorial errors or omissions contained herein.

MMicrosoft and Windows are US registered trademarks of Microsoft Corporation.

0Java is a US trademark of Sun Microsystems, Inc.

Printed in the US#

6˙˙

HP TP Web Connector V5.0A

Release Notes - July 2006

Contents