...
The figure below depicts an HTTP endpoint.
Figure 1: HTTP Target
| Attribute | Description |
| Target ID | ID provided while creating a target. |
| Target URI | URI of the Target endpoint. |
| Method | Choose method from Get, Post, Put and Delete. |
| Failover ID | The ID of the target which needs to be invoked if invocation fails on this server. |
...
| Attribute | Description |
|---|---|
| Key Manager Factory Type | Algorithm for the Key Manager Factory. |
| Key Store Type | Type of the Key Store whose location is specified by Key Store Location should be specified in the field. |
| Key Store Location | Location of the key store file can be provided using the file dialog box that opens up on clicking the ellipsis The KeyStore is used by the component for client authentication. |
| Key Store Password | Password of the specified key store can be specified in the field. |
| Key Store Client Key | Determines Key Store Client Key |
...
| Attribute | Description |
|---|---|
| Is Transacted | A session can be either transacted or non-transacted. Enable this if the session is transacted. When enabled, the acknowledge mode property disappears. |
Acknowledgement Mode | The type of Acknowledgement can be specified here. A session retains messages it consumes until they have been acknowledged.
Auto AcknowledgeThe session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or the receive call or when the message listener, which has been called by the session has called to process the message, successfully returns. Client AcknowledgeWith this acknowledgment mode, the client acknowledges a consumed message. Dups OK AcknowledgeThis acknowledgment mode instructs the session to lazily acknowledge the delivery of messages. |
...
Overview
Content Tools
ThemeBuilder