Topic Index
Click on one of the letters below to jump immediately to that section of the index.
- | . | A | B | C | D | E | F | G | H | I | J | L | M | N | P | R | S | T | U | W | X
-
-sourcepro option [in 1.4 Software Requirements].
.h++ productsusing with HydraExpress [in 1.4.1 SourcePro C++ Compatibility]
A
Agent ports, default [in 3.2.5 Agent Ports]Agent URL, setting [in 3.2.5 Agent Ports]
Agent
running multiple [in 4.4 Running Multiple Agents]
startup and shutdown [in 3.2 Configuring the Agent]
AgentContext [in 5.2 Creating a Custom Connector]
accessing Agent resources [in 5.2 Creating a Custom Connector]
AJP13 connector [in 3.2.2 Connectors]
Apache, configuring [in 3.4 Configuring an External Web Server]
B
Bobcatnow Agent servlet container [in 1.6 HydraExpress Mappings to LEIF Legacy Directory Structure]
was LEIF server [in 1.3 The HydraExpress Libraries]
C
classesnaming conventions for [in A.1.2 Naming Conventions]
clients
WSDL-defined client faults [in 8.3 Faults]
WSDL-defined faults [in 8.3 Faults]
code generator [in 1.2 HydraExpress Components]
code samples
client-side, for WSDL-defined faults [in 8.3.2 Generated Client-Side Code]
throwing WSDL-defined faults [in 8.3.3 Throwing Faults in the Server-Side Code]
Config [in 5.2 Creating a Custom Connector]
connector properties [in 5.2 Creating a Custom Connector]
connector layer [in 3.2.2 Connectors]
ConnectorImp [in 5.2 Creating a Custom Connector]
creating custom connectors [in 5.2 Creating a Custom Connector]
connectors [in 3.2.1 Agent Startup and Shutdown]
AJP13 [in 3.2.2 Connectors]
custom, creating [in 5.2 Creating a Custom Connector]
HTTP [in 3.2.2 Connectors]
HTTPS [in 3.2.2 Connectors]
consulting services [in B.1 Consulting Services and Training]
Core Library
location of header files [in 1.3 The HydraExpress Libraries]
D
directoryinstallation [in 2.4 The HydraExpress Directory Structure]
documentation, conventions [in A.1.1 Typographic Conventions]
documentation, list of [in 1.7 Documentation]
E
environment, settingfor HydraExpress [in 2.3 Configuring Your Environment]
error handling [in 8.3.1 WSDL-Defined Faults]
servers [in 8.3 Faults]
examples
client faults [in 8.3 Faults]
server error handling [in 8.3 Faults]
shipped with HydraExpress [in 1.5 Shipped Examples]
Exception [in 8.1 Overview]
[in 8.1 Overview]
[in 8.2 Exceptions]
[in 8.2 Exceptions]
exceptions
general [in 8.1 Overview]
to catch in generated samples [in 8.2.3 Standard Library Exceptions]
F
faultshow implemented on clients and servers [in 8.3 Faults]
implementation [in 8.3 Faults]
SOAP [in 8.1 Overview]
WSDL-defined faults [in 8.3 Faults]
WSDL-defined, in server code [in 8.3.2 Generated Client-Side Code]
G
general exceptions [in 8.1 Overview]H
handler chainshttp [in 3.2.3 Handler Chains]
header files, location of in installation [in 1.3 The HydraExpress Libraries]
HTTP connector [in 3.2.2 Connectors]
HTTPS connector [in 3.2.2 Connectors]
HTTPS
configuring security [in 3.5 Configuring Security]
Hydra Suite
HydraExpress a part of [in 1.1 Welcome]
HydraExpress
setting environment [in 2.3 Configuring Your Environment]
I
installationlocation of Core header files [in 1.3 The HydraExpress Libraries]
J
Java software requirements [in 1.4 Software Requirements]L
libraries12d [in 2.4 The HydraExpress Directory Structure]
15d [in 2.4 The HydraExpress Directory Structure]
primary libraries in HydraExpress [in 1.3 The HydraExpress Libraries]
load balancing
sample configuration [in 3.4.2.5 Sample Configuration for Load Balancing]
logger
custom [in 6.4 Creating and Using Custom Loggers]
custom, using [in 6.4.2 Using Your Logger]
default [in 6.2 Logging Fundamentals]
defining custom [in 6.4.1 Defining Your Logger]
global [in 6.1 Overview]
levels, definitions of [in 6.2 Logging Fundamentals]
[in 6.4.3 Creating a Rotating Log File]
separating messages [in 6.4.2.2 Separating Your Log Messages from the Agent Messages]
M
MessageInfo [in 5.2 Creating a Custom Connector][in 5.2 Creating a Custom Connector]
data structures [in 5.2 Creating a Custom Connector]
messages
client code for WSDL-defined fault messages [in 8.3.1 WSDL-Defined Faults]
example code for defining faults in WSDL [in 8.3.2 Generated Client-Side Code]
fault messages defined in WSDL [in 8.3.1 WSDL-Defined Faults]
separating log from Agent [in 6.4.2.2 Separating Your Log Messages from the Agent Messages]
throwing WSDL-defined faults [in 8.3.2 Generated Client-Side Code]
multiple Agents
issues with [in 4.4 Running Multiple Agents]
multithreading
servlet execution engine [in 3.3.3.1 Configuring Multiple Single Thread Servlet Engines]
N
naming conventions for classes and methods [in A.1.2 Naming Conventions]P
patchesapplying at runtime [in 4.5 Updating a Running Agent]
ports
Agent [in 3.2.5 Agent Ports]
issues with [in 3.2.5 Agent Ports]
project file
used in shipped examples [in 1.5.1 The Use of the HydraExpress Project File in Shipped Examples]
R
Rogue Wave Web sitetechnology access [in B.3 Web Access to Rogue Wave Technology]
runtime
applying patches [in 4.5 Updating a Running Agent]
rwagent.xml
defined [in 3.2 Configuring the Agent]
rwsfgen
code generator [in 1.2 HydraExpress Components]
rwsfserver startup script
overview and options [in 4.3 Starting and Stopping the Agent]
RWxmsg SourcePro exception class [in 8.2.4 SourcePro Exceptions]
S
securitycustomizing and configuring [in 3.5 Configuring Security]
server faults [in 8.3 Faults]
servers
error handling [in 8.3 Faults]
faults [in 8.3 Faults]
throwing WSDL-defined faults [in 8.3.2 Generated Client-Side Code]
servlet development in HydraExpress [in 1.2 HydraExpress Components]
servlet execution engine
multithread and single thread issues [in 3.3.3.1 Configuring Multiple Single Thread Servlet Engines]
servlets
configuring in web.xml [in 3.3 Configuring the Servlet Execution Engine]
[in 3.3.2 Configuring Individual Servlets in the Context-Level web.xml File]
single thread => See single-thread.
single-thread
accessing servlets [in 3.3 Configuring the Servlet Execution Engine]
[in 3.3.2 Configuring Individual Servlets in the Context-Level web.xml File]
attribute [in 3.3.3 Single-Thread and Multithread Issues]
SOAP
faults [in 8.1 Overview]
SoapFaultException [in 8.1 Overview]
[in 8.1 Overview]
[in 8.3 Faults]
[in 8.3 Faults]
SOAPworX
now Web Services in HydraExpress [in 1.6 HydraExpress Mappings to LEIF Legacy Directory Structure]
SourcePro
compatibility [in 1.4 Software Requirements]
using older versions [in 1.4.1 SourcePro C++ Compatibility]
std
:exception [in 8.2.4 SourcePro Exceptions]
T
technical support [in B.2 Technical Support]threading
single-thread access to servlets [in 3.3 Configuring the Servlet Execution Engine]
[in 3.3.2 Configuring Individual Servlets in the Context-Level web.xml File]
training [in B.1 Consulting Services and Training]
U
URLsetting Agent [in 3.2.5 Agent Ports]
W
Web serverconfiguring external [in 3.4 Configuring an External Web Server]
Web services
library in HydraExpess [in 1.3 The HydraExpress Libraries]
web.xml file, context [in 3.3.3.1 Configuring Multiple Single Thread Servlet Engines]
web.xml
global file [in 3.3.1 Configuring the Global web.xml File]
[in 3.3 Configuring the Servlet Execution Engine]
worker configuration
ajp13 [in 3.4.2.2 Configuring AJP13 Workers]
worker.properties [in 3.4.2 Configuring the Apache Web Server]
[in 3.4.2.5 Sample Configuration for Load Balancing]
configuring for single thread container [in 3.3.3.1 Configuring Multiple Single Thread Servlet Engines]
WSDL
client code for WSDL-defined faults [in 8.3.1 WSDL-Defined Faults]
defining of fault messages [in 8.3.1 WSDL-Defined Faults]
example code for defining faults [in 8.3.2 Generated Client-Side Code]
throwing faults defined in WSDL [in 8.3.3 Throwing Faults in the Server-Side Code]
X
XML bindingin HydraExpress [in 1.2 HydraExpress Components]
XML Object Link
now XML Binding in HydraExpress [in 1.6 HydraExpress Mappings to LEIF Legacy Directory Structure]
XmlName [in 8.3.3 Throwing Faults in the Server-Side Code]
[in 8.3.3 Throwing Faults in the Server-Side Code]
©2004-2007 Copyright Quovadx, Inc. All Rights Reserved.
Quovadx and Rogue Wave are registered trademarks of Quovadx, Inc. in the United States and other countries. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.