Resource Bundle com.soa.binding.soap11.ui / Soap11BindingApplicationResources Information

binding.soap11.access_point.physical.wizard_text

The "Specify SOAP 1.1 Details" screen allows you to configure transport information for the current Access Point definition. Transport configuration options are derived from the service binding.The "Service Details" section displays the "Service Type" and "Service Name" of the service associated with the current Access Point definition. These fields are Policy Manager-specific.The "Binding Details" section 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 WSDL.The "Access Point Details" section 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 WSDL. The "Description" field is optional.If your binding includes an HTTP transport a custom HTTP configuration section (HTTP Details) displays. This section allows you to enter Host Name or IP, Port, and Path for the URL you would like assigned to the Access Point. In the "URL" text box enter the Host Name or IP, Port, and Path for the HTTP or HTTPS protocol type. Then, click the radio button of the "Protocol Version" you would like assigned to the Access Point. Options include HTTP 1.1 (default) or HTTP 1.0). If your binding includes a JMS transport a custom JMS configuration section displays. The "JMS Details" section 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.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.After completing your entries, click "Finish."

binding.soap11.access_point.physical.wizard_title

Specify SOAP 1.1 Details

binding.soap11.access_point.virtual.wizard_text

The "Specify SOAP 1.1 Details" screen allows you to configure transport information for the current Access Point definition. Transport configuration options are derived from the service binding.The "Service Details" section displays the "Service Type" and "Service Name" of the service associated with the current Access Point definition. These fields are Policy Manager-specific.The "Binding Details" section 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 WSDL.The "Access Point Details" section displays the "WSDL Port Name." The "WSDL Port Name" represents the wsdl:port element in the WSDL.If your binding includes an HTTP transport a custom HTTP configuration section (HTTP Details) displays. This section displays the Listener Address, Virtual Host, and Context Path. The Virtual Host field allows you to specify an additional domain name that is used for accessing the service endpoint. This field is optional. The Context Path field allows you to specify a unique location used to access the current virtual service in the container. The "Context Path" is combined with the Listener Address to form an Access Point URL. It is recommended not to use the default Context Path to avoid potential location resolution conflicts. If your binding includes a JMS transport, a custom JMS configuration section displays. The "JMS Details" section displays the "JNDI URL," "JNDI Initial Context," and "JMS Factory Name" properties defined in your container JMS Listener configuration and a "JMS Queue" field that allows you to enter the name of the JMS Queue where a Queue object reference can be found in the JNDI server.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.After completing your entries, click "Next" to continue. If the current operation is the last in the sequence, the "Finish" button displays.

binding.soap11.access_point.virtual.wizard_title

Specify SOAP 1.1 Details

binding.soap11.binding.wizard_text

The "Configure SOAP 1.1 Binding Properties" screen provides options for configuring the properties of the current SOAP 1.1 binding definition.The "Binding Details" section provides a summary of the "Interface QName," "Binding QName," and "Binding Type" elements for the current binding definition.The "Binding Properties" section allows you to select a binding "Transport" (HTTP, JMS, WebSphere MQ, Other), "Transport URI" (JMS, Other), a binding "Style" (Document/Literal, RPC Literal, or RPC Encoded), "SOAP Action," and "Namespace." Refer to the screen descriptions for "SOAP Action" and "Namespace" for additional details.Each SOAP binding requires a "Transport URI" which is an address that points to the message transport mechanism used to communicate information required to deliver a message appropriately to an endpoint. The "Transport URI" option displays for "JMS" and "Other" options. JMS supports four "Transport URI" options (WebSphere, WebLogic, WSIF, and Tibco) that are selectable from a drop-down list box. The "Other" transport option displays a "Transport URI" text box that allows you to enter a custom Transport URI (e.g., TCP). Note: The Transport URI for HTTP is a known value and is processed by Policy Manager.After completing your entries, click "Next" to continue. If the current operation is the last in the sequence, the "Finish" button displays.

binding.soap11.binding.wizard_title

Configure SOAP 1.1 Binding Properties

binding.soap11.name

SOAP 1.1

com.soa.binding.soap11.transport.uri.required

Transport URI Required

com.soa.binding.soap11.ui.context.path.must.start.with.slash

Context Path must start with '/'

com.soa.binding.soap11.ui.context.path.required

Context Path is required

com.soa.binding.soap11.ui.destination.required

Destination Required

com.soa.binding.soap11.ui.http.client.certificate.option

Client Certificate

com.soa.binding.soap11.ui.http.client.certificate.option.accept

Accept

com.soa.binding.soap11.ui.http.client.certificate.option.require

Require

com.soa.binding.soap11.ui.http.helpid

32

com.soa.binding.soap11.ui.http.protocol.version

Protocol Version

com.soa.binding.soap11.ui.http.title

HTTP Information

com.soa.binding.soap11.ui.http.url

URL

com.soa.binding.soap11.ui.information

Information

com.soa.binding.soap11.ui.invalid.reply.queue

Invalid Reply To queue

com.soa.binding.soap11.ui.invalid.reply.topic

Invalid Reply To topic

com.soa.binding.soap11.ui.invalid.url

Invalid URL: {0}. {1}

com.soa.binding.soap11.ui.invalid.url.http

Invalid URL. URL must start with 'http://' or 'https://'

com.soa.binding.soap11.ui.invalid.url.jms

Invalid URL: URL must start with 'jms:/'

com.soa.binding.soap11.ui.jms.connection.property

Add Connection Property

com.soa.binding.soap11.ui.jms.factory.name

JMS Factory Name

com.soa.binding.soap11.ui.jms.factory.name.required

JMS Factory Name required

com.soa.binding.soap11.ui.jms.helpid

32

com.soa.binding.soap11.ui.jms.jndi.initial.context

JNDI Initial Context

com.soa.binding.soap11.ui.jms.jndi.url

JNDI URL

com.soa.binding.soap11.ui.jms.queue.name

JMS Queue Name

com.soa.binding.soap11.ui.jms.queue.name.required

JMS Queue Name required

com.soa.binding.soap11.ui.jms.title

JMS Information

com.soa.binding.soap11.ui.jndi.initial.context.required

JNDI Initial Context required

com.soa.binding.soap11.ui.jndi.url.required

JNDI URL required

com.soa.binding.soap11.ui.message.namespace.required

Message Namespace required

com.soa.binding.soap11.ui.nonwsdl

This is a non-WSDL access point.

com.soa.binding.soap11.ui.only.http.transport.supported

Only HTTP Transport supported at present

com.soa.binding.soap11.ui.other.helpid

32

com.soa.binding.soap11.ui.other.title

Information

com.soa.binding.soap11.ui.other.url

URL

com.soa.binding.soap11.ui.soapaction.required

SOAPAction required

com.soa.binding.soap11.ui.topicString.required

TopicString Required

com.soa.binding.soap11.ui.tranposrt.uri.not.found.for.binding

TransportURI not found for binding: {0}

com.soa.binding.soap11.ui.unsupported.protocol.type

Unsupported protocol Type {0}

com.soa.binding.soap11.ui.unsupported.transport

Unsupported transport: {0}

com.soa.binding.soap11.ui.useServicePkiForInboundHttps

Use Service PKI for inbound HTTPS

com.soa.binding.soap11.ui.wmq.helpid

32

com.soa.binding.soap11.ui.wmq.title

WMQ Information

com.soa.binding.soap11.ui.wmq.url

URL