### Proxy Service Transport Configuration page

Use the AquaLogic Proxy Service Transport Configuration page to select a transport protocol for the proxy service and to set other general transport configuration settings.

This page appears both in the New AquaLogic Proxy Service wizard and in the AquaLogic Proxy Service editor:

Note: | Inbound transport-level security applies to the client applications and ALSB proxy services. Outbound transport-level security applies to the connections between ALSB proxy services and business services. To learn more about transport-level security, see Configuring Transport-Level Security in the AquaLogic Service Bus Security Guide.

Option | Description
--- | ---
Protocol | Select a transport protocol from the list. The protocols available differ, depending on the service type you are creating: WSDL Web Service: HTTP, JMS, Local, SB, WS Messaging Service: E-mail, File, FTP, HTTP, JMS, Local, MQ (if available), SFTP, Tuxedo Any SOAP Service: HTTP, JMS, Local, SB Any XML Service: E-mail, File, FTP, HTTP, JMS, Local, MQ (if available), SB, SFTP, Tuxedo
Endpoint URI | Enter an endpoint URI in the format based on the transport protocol you selected in the Protocol field, above: The formats are: E-mail - `mailfrom:mail-server-host:port` File - `file:///root-dir/dir1` FTP - `ftp://hostname:port/directory` HTTP - /`someName` The HTTP transport supports both `HTTP` and `HTTPS` endpoints. JMS - `jms://host:port[,host:port]*/factoryJndiName/destJndiName` To target a target a JMS destination to multiple servers, use the following URI format: `jms://host1:port,host2:port/QueueConnectionFactory/DestName` Note that when you create a proxy service, you can configure a JMS endpoint URI even if the server at that endpoint if not available. However, in the case of JMS, when you activate the session, the endpoint must be available. Local This transport does not require an endpoint URI. MQ - `mq://local-queue-name?conn=mq-connection-resource-ref` `local-queue-name` is the name of the MQ queue from which the proxy service reads messages. `mq-connection-resource-ref` is the path (`project/folder`) and name of the MQ connection resource; for example, `default/my_MQconnection`. To make the MQ transport available in ALSB, see MQ Connections in Using the AquaLogic Service Bus Console. SB - `service_name` `service_name` is the unique identifier for the proxy service. By default, this name will be the proxy service name. `service_name` must only contain characters permitted in URIs (as described in RFC2396), except it cannot contain forward slash (/) or colon (:) characters. SFTP - `sftp://hostname:port/directory`
Endpoint URI (continued) | Tuxedo - `servicename` The URI `servicename` corresponds to a WTC Export that the remote Tuxedo domain identifies as a Tuxedo service. If more than one URI is specified, you must have unique resource names for the endpoints. If no remote name is specified, its value is the value of the resource name. If no remote name is entered or if remote and resource name are the same, only one URI is allowed. In this case resource name and remote name will have the same value. This allows users using already defined WTC Imports to make use of WTC load-balancing and failover. Note: If you configure two identical URIs, an error indicates that the service name already exists. WS - `/contextPath` `contextPath` must be unique for proxy services that use either HTTP or WS transport.
Get All Headers | Select Yes to retrieve all the headers from the transport. Select No to retrieve a defined set of headers. If you select No, enter a set of headers in the Header field, then click Add. (This step does not apply to Local transport.)
Note: | ALSB does not pass the HTTP Authorization header from the request to the pipeline because it opens a security vulnerability. You could inadvertently create a log action that writes the user name and unencrypted password to a log file. If your design pattern requires the HTTP Authorization header to be in the pipeline, do the following: a. In the startup command for ALSB, set the following system property to true: `com.bea.wli.sb.transports.http.GetHttpAuthorizationHeaderAllowed` b. In Eclipse, on the Transport Configuration page, select Yes for Get All Headers or select No and specify Authorization. c. Restart ALSB. ALSB will pass the Authorization header to the pipeline.