...
The target configuration encapsulates different back end/third party services which need to be invoked by the proxy to fulfil requests. The endpoint URL specified when creating a project is saved as the default target configuration. New targets can be added by clicking the Add button. The targets Targets can be either HTTP or JMS endpoints.
HTTP
...
| Attribute | Description |
|---|---|
| User Name | User Name to connect to the web server. |
| Password | Password for the username mentioned. |
| Hostname | Host that needed to be authenticated with. |
| Port | Port of the host that needed to be authenticated with. |
| DOMAIN | Domain name needed by NT Credentials for NT Domain. |
...
Select this option to enable SSL Settings. Rest of the Other properties in this editor are enabled and configurable only when this property is checked.
...
Protocol Handler Packages
Protocol handlers organized are organized in a package hierarchy similar to content handlers.
...
| 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 |
...
This configuration helps to connect with a provider, and administer JMS.
| Attribute | Description |
|---|---|
| Server URL | IP address of the JMS server. |
| Backup URLs | The backup URLs to which the component tries to connect if the server specified by the property "server URL" is down. Multiple backup URLs can be specified by separating them with a ';'. |
| CF lookup name | Connection Factory Lookup Name. |
| JMS username | Username with which the connection to the server is established. |
| JMS password | Password for the username mentioned. |
...
| Attribute | Description |
|---|---|
| JNDI Username | The name with which the user connects to the JNDI server to perform lookup operations. |
| JNDI Password | The password for the JNDI username. |
Initial Context Factory | The name of the initial context factory. The initial context is typically used as a starting point. |
Properties (for Initial Context) | Properties can be used for creating an initial context by providing specific values by clicking clicking the Add An initial context must be created using the specific implementation and extra parameters required by the implementation. The initial context will be used to look up for a name. It is analogous to the root, or top of a directory tree for a file system. |
button....
| 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 mode 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 when the message listener 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. |
...
| Attribute | Description |
|---|---|
| Destination Name | JNDI name of the topic/queue to be subscribed to. |
Destination Type | Specifies whether the destination for the port is a 'Queue' or a 'Topic':
|
| Lookup Destination | Enable this property if the destination is already present and needs to be looked up using JNDI. |
| Autocreate Destination | Enable this property to create a destination if it is not set. |
...
| Attribute | Description | ||
|---|---|---|---|
| Delivery Mode | Delivery mode defines whether the message can be is persistent or non-persistent; choose either of these as per requirement:.
| ||
| Priority | The priority of the message to be sent to the destination. | ||
| Time to Live in ms | The time to live (in milliseconds) of the message to be sent to the destination. After the specified timeout, the message will be discarded. |
...
Destination on which response is expected.
| Note |
|---|
Refer to the Request Destination Configuration section above for the descriptions. |
...
Destination on which error is expected.
| Note |
|---|
Refer to the Request Destination Configuration section above for the descriptions. |
...
| Attribute | Description |
|---|---|
| Execution Timeout in ms | Maximum time in milliseconds the component should wait for a message. The default value is '0' which specifies infinite wait time , that is, waits which signifies waiting until a message is received. |
| Message Selector | Value for a JMS message property to route the message depending on that. |