binding.messaging.access_point.physical.wizard_text
<p>The "Specify AMQP Details" screen allows you to configure transport information for the current Access Point definition. Transport configuration options are derived from the service binding.<p><i>Service Details</i><p>Displays the "Service Type" and "Service Name" of the service associated with the current Access Point definition. These fields are Policy Manager-specific.<p><i>Binding Details</i><p>Displays the "Binding Type" and "Binding" associated with the service access point definition. The "Binding Type" is a Policy Manager-specific field. The "Binding" represents the wsdl:binding element in the Service Descriptor Document.<p><i>Access Point Details</i><p>Displays the "WSDL Port Name" and "Description." The "WSDL Port Name" represents the wsdl:port element in the WSDL. The "Description" represents the wsdl:documentation element in the Service Descriptor Document. The "Description" field is optional.<p><p>If the binding includes an AMQP transport the following sections display:<p><i>AMQP Details</i><p>Virtual Host Name - Allows you to specify the virtual host name of the AMQP broker.<p>Authentication Required - This section is used if the AMQP binding will be used to authenticate an AMQP registry where AMQP destinations or targets are located, or to authenticate the AMQP system itself, authentication may be required. To enable authentication, select the checkbox and specify the username and password credentials.<p><p>If the binding includes a JMS transport the following sections display:<p><i>JMS Details</i><p>Allows you to enter JMS properties assigned to the Access Point. In the "JNDI URL" field, enter the URL of the Java Naming and Directory Interface where the server can be accessed. A "jms:/" prefix is added to the field. In the "JNDI Initial Context" field enter the starting point for resolution of names for naming directory operations. In the "JMS Factory Name" field, enter the connection factory for the Java Message Service. In the "JMS Queue Name" enter the name of the JMS Queue where a Queue object reference can be found in the JNDI server.<p>The "Add Connection Property" link allows you to add JMS Connection Properties which are user-defined additional properties that allow you to specify the messaging engine that an application will connect to. Only "String" type message properties are supported. Connection Properties are configured by entering a "Property Name" and "Property Value. Entering a Connection Property is optional. Click the "Add Connection Property" link for each Connection Property you would like to add. To remove a Connection Property, click the "Remove" link.<p>After completing your entries, click "Finish".
binding.messaging.access_point.physical.wizard_title
Specify AMQP Details
binding.messaging.access_point.virtual.wizard_text
<p>The "Specify AMQP Details" screen allows you to configure transport information for the current Access Point definition. Transport configuration options are derived from the service binding.<p><i>Service Details</i><p>Displays the "Service Type" and "Service Name" of the service associated with the current Access Point definition. These fields are Policy Manager-specific.<p><i>Binding Details</i><p>Displays the "Binding Type" and "Binding" associated with the service access point definition. The "Binding Type" is a Policy Manager-specific field. The "Binding" represents the wsdl:binding element in the Service Descriptor Document.<p><i>Access Point Details</i><p>Displays the "WSDL Port Name" and "Description." The "WSDL Port Name" represents the wsdl:port element in the WSDL. The "Description" represents the wsdl:documentation element in the Service Descriptor Document. The "Description" field is optional.<p><p>If the binding includes an AMQP transport the following sections display:<p><i>AMQP Details</i><p>This section displays the authentication details (true/false), and Username. If true, the AMQP binding will be used to authenticate an AMQP registry where AMQP destinations or targets are located, or will authenticate the AMQP system itself.<p><p>If the binding includes a JMS transport the following sections display:<p><i>JMS Details</i><p>Allows you to enter JMS properties assigned to the Access Point. In the "JNDI URL" field, enter the URL of the Java Naming and Directory Interface where the server can be accessed. A "jms:/" prefix is added to the field. In the "JNDI Initial Context" field enter the starting point for resolution of names for naming directory operations. In the "JMS Factory Name" field, enter the connection factory for the Java Message Service. In the "JMS Queue Name" enter the name of the JMS Queue where a Queue object reference can be found in the JNDI server.<p>The "Add Connection Property" link allows you to add JMS Connection Properties which are user-defined additional properties that allow you to specify the messaging engine that an application will connect to. Only "String" type message properties are supported. Connection Properties are configured by entering a "Property Name" and "Property Value. Entering a Connection Property is optional. Click the "Add Connection Property" link for each Connection Property you would like to add. To remove a Connection Property, click the "Remove" link.<p>After completing your entries, click "Finish".
binding.messaging.access_point.virtual.wizard_title
Specify AMQP Details
binding.messaging.binding.wizard_text
<p>The "Configure Messaging Binding Properties" screen provides options for configuring the properties of the current Messaging binding definition.<p><i>Binding Details:</i><p>Displays Interface QName, Binding QName, and Binding Type elements for the current binding definition.<p><i>Binding Properties:</i><p>Transport - Select AMQP or JMS messaging protocols.<p>Transport URI - Specify the Transport URI for connecting to the AMQP or JMS server.<p><i>Operations:</i><p>Configure each operation in the binding as follows:<p>Operation Label - Displays the read only label of the operation.<p>Destination Type Pull-Down - Select whether you would like messages routed to a Topic exchange or a Queue.<p>Destination Name - Enter the name of the Topic exchange (e.g., example.topic) or Queue.<p>Input Content Type - Describe type of content of the Request Message.<p>Output Content Type - Describe the type of content of the response message when it is not a fault.<p>Fault Content Type - Describe the type of content of the response message when it is a fault.<p>Reply To - Specify the name of the queue that the replies (i.e., responses to the requests) will be inserted into.<p>Note: Type of content can be described using a media type (i.e., application/xml, text/html, and application/json).<p><i>Parts:</i><p>Define the following elements for the parts of the input message as defined in the interface (WSDL portType).<p>Part - Read-only label that displays part name as defined in the interface.<p>Name - Enter a binding specific name for the part. The value of the Part is used as the default.<p>Type - Select how the part is transported in the protocol. Options include Body or Property.<p>Value - Enter a value if the Type field has a Property as its choice. The text box is only enabled if Property has been chosen.<p>Use Selector - Enable use of a selector filter and specify filter.<p>After completing your entries, click "Next" to continue. If the current operation is the last in the sequence, the "Finish" button displays.
binding.messaging.binding.wizard_title
Configure Messaging Binding Properties
binding.messaging.name
Messaging
com.soa.binding.messaging.transport.uri.required
Transport URI Required
com.soa.binding.messaging.ui.amqp.amqpplusssl
AMQP+SSL
com.soa.binding.messaging.ui.amqp.amqpssl
AMQPS
com.soa.binding.messaging.ui.amqp.exchange
Exchange Name
com.soa.binding.messaging.ui.amqp.helpid
32
com.soa.binding.messaging.ui.amqp.nossl
AMQP
com.soa.binding.messaging.ui.amqp.queue
Queue Name
com.soa.binding.messaging.ui.amqp.routingkey
Routing Key
com.soa.binding.messaging.ui.amqp.title
AMQP Information
com.soa.binding.messaging.ui.amqp.url
AMQP URL
com.soa.binding.messaging.ui.context.path.must.start.with.slash
Context Path must start with '/'
com.soa.binding.messaging.ui.context.path.required
Context Path is required
com.soa.binding.messaging.ui.destination.required
Destination Required
com.soa.binding.messaging.ui.fault.content.label
Fault Content Type
com.soa.binding.messaging.ui.information
Information
com.soa.binding.messaging.ui.input.content.label
Input Content Type
com.soa.binding.messaging.ui.invalid.reply.queue
Invalid Reply To queue
com.soa.binding.messaging.ui.invalid.reply.topic
Invalid Reply To topic
com.soa.binding.messaging.ui.invalid.url
Invalid URL: {0}. {1}
com.soa.binding.messaging.ui.invalid.url.jms
Invalid URL: URL must start with 'jms:/'
com.soa.binding.messaging.ui.jms.connection.property
Add Connection Property
com.soa.binding.messaging.ui.jms.factory.name
JMS Factory Name
com.soa.binding.messaging.ui.jms.factory.name.required
JMS Factory Name required
com.soa.binding.messaging.ui.jms.jndi.initial.context
JNDI Initial Context
com.soa.binding.messaging.ui.jms.jndi.url
JNDI URL
com.soa.binding.messaging.ui.jms.queue.name
JMS Queue Name
com.soa.binding.messaging.ui.jms.queue.name.required
JMS Queue Name required
com.soa.binding.messaging.ui.jms.title
JMS Information
com.soa.binding.messaging.ui.jndi.initial.context.required
JNDI Initial Context required
com.soa.binding.messaging.ui.jndi.url.required
JNDI URL required
com.soa.binding.messaging.ui.location
Transport
com.soa.binding.messaging.ui.location.uri
Transport URI
com.soa.binding.messaging.ui.message.namespace.required
Message Namespace required
com.soa.binding.messaging.ui.output.content.label
Output Content Type
com.soa.binding.messaging.ui.part.type.not.selected
Select an option for part type
com.soa.binding.messaging.ui.topicString.required
TopicString Required
com.soa.binding.messaging.ui.tranposrt.uri.not.found.for.binding
TransportURI not found for binding: {0}
com.soa.binding.messaging.ui.unsupported.protocol.type
Unsupported protocol Type {0}
com.soa.binding.messaging.ui.unsupported.transport
Unsupported transport: {0}