Skip Headers
Oracle® Application Server Integration InterConnect Adapter for HTTP Installation and User's Guide
10g Release 2 (10.1.2)
B14074-02
  Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents

Previous
Previous
 

Index

A  B  C  D  E  H  I  L  M  O  P  R  S  T  U  W  X 

A

adapter.ini file
bridge_class parameter, 2.3.1.2
cannot be changed, A.5
configuring D3L, 3.1.2
configuring XML, 3.1.1
directory path location, 2.1.2
encrypted_http.sender.password parameter, 2.3.1.2
encrypted_http.sender.wallet_password parameter, 2.3.1.2
http.receiver.customized_class parameter, 2.3.1.2
http.receiver.instance_name parameter, 2.3.1.2
http.receiver.registry_port parameter, 2.3.1.2
http.sender.authtype parameter, 2.3.1.2
http.sender.cipher_suites parameter, 2.3.1.2
http.sender.password parameter, 2.3.1.2
http.sender.proxy_host parameter, 2.3.1.2
http.sender.proxy_port parameter, 2.3.1.2
http.sender.realm parameter, 2.3.1.2
http.sender.timeout parameter, 2.3.1.2
http.sender.username parameter, 2.3.1.2
http.sender.wallet_location parameter, 2.3.1.2
http.sender.wallet_password parameter, 2.3.1.2
ota.d3ls parameter, 2.3.1.2
ota.receive.endpoint parameter, 2.3.1.2
ota.send.endpoint parameter, 2.3.1.2
ota.type parameter, 2.3.1.2
adapters
multiple adapters in same Oracle home, 2.2
agent
configuration parameters, 2.3.1.2

B

bridge
detecting messages, 3.2.1
bridge_class parameter
cannot be changed, A.5
definition, 2.3.1.2

C

configuration
HTTP adapter, 2.3
copyAdapter script, 2.2

D

D3L payload
message delivery, 3.2.3.1
data definition description language (D3L)
file contents, 3.1.2
importing in iStudio, 3.1.2
sending messages using D3L as the payload data type, 3.2.3
setting the ota.d3ls parameter, 2.3.1.2
setting the ota.type parameter, 2.3.1.2
supported, 1.1
used by bridge to parse formats, 3.2.1
design time concepts
HTTP adapter, 3.1
diagnostics
on received messages, 3.2.5
directories
logs, 2.3
persistence, 2.3
directory path
of HTTP adapter, 2.1.2
document type definition (DTD)
features, 3.1.1
importing in iStudio, 3.1.1

E

.EAR file
manually deploying, 2.1.3.7
encrypted_http.sender.password parameter
definition, 2.3.1.2
encrypted_http.sender.wallet_password parameter
definition, 2.3.1.2
encryption
of the HTTP adapter password parameter, A.7
endpoints
send and receive endpoints are restricted to HTTP endpoints, 1.4
support for receiving from a single endpoint, 1.4
error messages
HTTP adapter startup problems, A.2
executable files
stop, 2.3
stop.bat, 2.3

H

HTTP adapter
configuration, 2.3
customizing, 3.3
D3L support, 1.1
design time concepts, 3.1
diagnosing received messages, 3.2.5
directory path location, 2.1.2
hardware requirements, 1.2.1
installation, 2.1
installation tasks, 2.1.2
installing multiple adapters, 2.2
JRE requirements, 1.2.2.2
limitations, 1.4
log of successfully started adapter, 3.4.1
logging information, 2.3
message persistence, 2.3
operating system requirements, 1.2.2.1
overview, 1.1
preinstallation tasks, 2.1.1
receiving messages, 3.2.1
runtime concepts, 3.2
sending messages, 3.2.3
software requirements, 1.2.2
starting, 3.4
startup error, A.3
startup errors, A.2
stopping, 2.3, 3.5
support for publish/subscribe model, 1.4
supported HTTP versions, 1.1
XML payload, 3.1.1
XML payload support, 1.1
HTTP Adapter-specific Parameters, 2.3.1.2
HTTP protocol
message headers, 3.2.4
supported versions, 1.1
http.receiver. instance_name parameter
definition, 2.3.1.2
http.receiver.customized_class parameter
definition, 2.3.1.2
http.receiver.registry_port parameter
customizing after installation, 2.1.3.6
definition, 2.3.1.2
HTTPS
functionality available, 1.1, 2.1.3.5, 2.3.1.2
http.sender.authtype parameter
customizing after installation, 2.1.3.3
definition, 2.3.1.2
http.sender.cipher_suites parameter
customizing after installation, 2.1.3.5
definition, 2.3.1.2
HTTPSenderCustomizer Interface, 3.3.2, 3.3.2.2
http.sender.password parameter
customizing after installation, 2.1.3.3
definition, 2.3.1.2
http.sender.proxy_host parameter
customizing after installation, 2.1.3.4
definition, 2.3.1.2
http.sender.proxy_port parameter
customizing after installation, 2.1.3.4
definition, 2.3.1.2
http.sender.realm parameter
customizing after installation, 2.1.3.3
definition, 2.3.1.2
http.sender.timeout parameter
customizing after installation, 2.1.3.2
definition, 2.3.1.2
http.sender.username parameter
customizing after installation, 2.1.3.3
definition, 2.3.1.2
http.sender.wallet_location parameter
customizing after installation, 2.1.3.5
definition, 2.3.1.2
http.sender.wallet_password parameter
customizing after installation, 2.1.3.5
definition, 2.3.1.2

I

initialization parameters
bridge_class, 2.3.1.2
cannot be changed, A.5
encrypted_http.sender.password, 2.3.1.2
encrypted_http.sender.wallet_password, 2.3.1.2
http.receiver.customized_class, 2.3.1.2
http.receiver.instance_name, 2.3.1.2
http.receiver.registry_port, 2.3.1.2
http.sender.authtype, 2.3.1.2
http.sender.cipher_suites, 2.3.1.2
http.sender.password, 2.3.1.2
http.sender.proxy_host, 2.3.1.2
http.sender.proxy_port, 2.3.1.2
http.sender.realm, 2.3.1.2
http.sender.timeout, 2.3.1.2
http.sender.username, 2.3.1.2
http.sender.wallet_location, 2.3.1.2
http.sender.wallet_password, 2.3.1.2
making the password parameter secure, A.7
ota.d3ls, 2.3.1.2
ota.receive.endpoint, 2.3.1.2
ota.send.endpoint, 2.3.1.2
ota.type, 2.3.1.2
installation
changing or correcting settings after installation, A.5
hardware requirements, 1.2.1
HTTP adapter, 2.1, 2.1.2
installing HTTP adapter into same Oracle home as spoke database, 2.1
JRE requirements, 1.2.2.2
operating system requirements, 1.2.2.1
preinstallation tasks, 2.1.1
software requirements, 1.2.2
iStudio
importing D3L, 3.1.2

L

log files
log.xml, 2.3
of successfully started HTTP adapter, 3.4.1
viewing HTTP adapter startup problems, A.2
logs directory
definition, 2.3
log.xml file
logging information, 2.3

M

messages
diagnosing received messages, 3.2.5
example of sending message to HTTP adapter, 3.2.3
HTTP headers, 3.2.4
logging HTTP adapter activity, 2.3
persisting, 2.3
receiving from a single endpoint, 3.2.1

O

oai.ear file
manually deploying, 2.1.3.7
sample file, 2.1.3.7
ota.d3ls parameter
definition, 2.3.1.2
ota.receive.endpoint parameter
definition, 2.3.1.2
ota.send.endpoint parameter
definition, 2.3.1.2
ota.type parameter
definition, 2.3.1.2

P

password
encryption, A.7
payload data type
sending messages, 3.2.3
persistence directory
definition, 2.3
POST method
supported by the HTTP adapter's servlet for receiving messages, 1.4
postinstallation
configuration
customizing a proxy host, 2.1.3.4
customizing a Secure Socket Layer environment, 2.1.3.5
customizing the authentication scheme, 2.1.3.3
customizing the receiving endpoints, 2.1.3.6
customizing the sending endpoints, 2.1.3.2
manually deploying an EAR file, 2.1.3.7
publish/subscribe model
supported, 1.4

R

Real Application Clusters, 2.3.1.1
ReceiverCustomizer Interface, 3.3.1
requirements
hardware, 1.2.1
JRE, 1.2.2.2
operating system, 1.2.2.1
software, 1.2.2
runtime concepts
HTTP adapter, 3.2

S

Secure Socket Layer (SSL)
functionality available, 1.1, 2.1.3.5, 2.3.1.2
security
making the adapter.ini password parameter secure, A.7
start (UNIX), 2.3
starting
HTTP adapter, 3.4
stop file
definition, 2.3
stop.bat file
definition, 2.3
stopping
HTTP adapter, 3.5

T

troubleshooting
changing or correcting information set during installation, A.5
delivering a message to a specific partition of the publishing adapter, A.8
HTTP adapter not publishing or subscribing to the messages, A.6
HTTP adapter not starting, A.3
HTTP adapter startup errors, A.2
HTTP adapter uses old information in run-time environment, A.4
making the adapter.ini password parameter secure, A.7

U

uninstalling the HTTP adapter, 2.4

W

web.xml file
editing the setting in the EAR file, 2.1.3.7

X

XML payload
configuring the ota.type parameter in adapter.ini file, 3.1.1
HTTP adapter, 3.1.1
message delivery, 3.2.3.2