Proxy services are AquaLogic Service Bus definitions of services implemented locally on WebLogic Server. You can define a proxy service in terms of WSDLs, pipelines, and policies. If the proxy service requires security certificates, you can create a proxy service provider to manage these security certificate mappings to key store entries from the AquaLogic Service Bus Console. For information on how to configure a proxy service provider, see Adding a Proxy Service Provider. You can configure access control policies on proxy services. To learn more, see Listing and Locating Access Control Policies, Editing Transport-Level Access Policies, and Editing Message-Level Access Policies.
You implement a proxy service through configuring its Message Flow. Message Flows can include the following nodes: Start, Pipeline Pair, Branch, and Route. To learn more, see Overview of Proxy Services and Viewing and Changing Message Flow.
The following table lists the pages you can access from the Project Explorer and Resource Browser modules. The tasks and help topics associated with each are provided.
Table 16-1 Pages Accessed from Project Explorer and Resource Browser Modules
Page
Associated Tasks
Help Topics
Summary of Proxy Services
View a list of proxy services. The service name and alerts are displayed.
Each service type is modeled following the same pattern. Their configuration is composed of a common part and a service type specific part.
The common configuration consists of the following properties.
Table 16-2 Service Type Configuration
Property
Description
Resource Definition
The resource definition consists of:
The service name (that is, project, path, and local name)
An optional description for the service
The service type (read only)
Miscellaneous Configuration
This configuration consists of:
The service provider for proxy services
Note:
A service provider is only required if the proxy service routes messages to HTTPS services that require client-certificate authentication, or in some message-level security scenarios.
Transport Configuration
You can configure the following parameters for each proxy service:
Endpoint URI—string, for example: /proxy1 or jms://localhost:7001/QueueConnectionFactory/DestName. (This is required.)
To target a JMS destination to multiple servers, use the following URI format: jms://host1:port,host2:port/QueueConnectionFactory/DestName
Get all headers except the HTTP Authorization header from the request1. This is a Boolean value; the default is true.
User-specified Headers—a list of string header names, which is only applicable if you select False for the Get all headers option. Does not get the HTTP Authorization header even if you specify it.
The transport you select should support the transport mode (request/response, one-way, or both) required by the binding definition, and be configured accordingly.
For services exchanging messages in both modes, you must configure the binding layer to choose the transport mode accordingly (for any transport implementing the request/response as two asynchronous calls, for example, JMS). This occurs automatically when the service is a concrete type, as it is described in the binding definition. When it is not a concrete type, to configure the binding layer, you must set the mode in the $outbound variable.
Transport Configuration Continued
Based on the transport and WSDL, or interface, the transport mode is automatically selected, but you can overwrite it in $inbound or $outbound.
1AquaLogic Service Bus 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, see To Add a Proxy Service - Transport Configuration.
Each service type must define the following configurations:
You can base SOAP and XML services on an existing WSDL resource. A WSDL resource can be used for proxy services using HTTP, HTTPS and JMS transports. This WSDL is used as the base for the final WSDL document for the service.
When you create a proxy service based on a WSDL, you can select only a WSDL port or a WSDL binding, as a WSDL may or may not have a port defined. The WSDL port describes what the actual transport address is. This, however, is not used for proxy services. The URL is specified in the transport configuration for the service.
When you create a proxy service based on a WSDL Binding, AquaLogic Service Bus sets the new service and port definitions in the WSDL generated for the proxy service. Regardless of whether you define a proxy service based on a WSDL port or a WSDL binding, the WSDL generated for the proxy service defines only a single port. If the service is generated from port X in the template WSDL, then port X is also defined in the generated WSDL.
However the URL defined in the transport configuration for the service is used for HTTP(S) services and not the URL in the WSDL. For other transports (only JMS applies), the service and port is not defined in the generated WSDL.
Furthermore, if you base the proxy service on a WSDL port, the generated WSDL uses that port name and preserves any WS-Policies associated with that port. The binding is determined from the port, and in turn, the port type is determined from the binding.
If the service is generated from binding Y in the template WSDL, the generated WSDL defines a new service and port (<service-name>QSService and <port-name>QSPort). None of the ports defined in the template WSDL are included in the generated WSDL.
If you base the service on a WSDL binding template, there may be multiple ports in that WSDL associated with that binding. Each port can use a different URL and have a different WS-Policy attached to it. Therefore, the generated WSDL uses the binding but generates an artificial port for that binding with no WS-Policy. For all WSDL-based services, the transport type and transport URL are specified in the transport section of the service definition.
Note:
You can get the WSDL for an HTTP(S)-based proxy service by entering the URL for the service appended with ?WSDL in your browser's Address field.
WSDL Web Services (Binding)
You can base SOAP and XML services on an existing WSDL resource. A WSDL resource can be used for proxy services using HTTP, HTTPS and JMS transports. This WSDL is used as the base for the final WSDL document.
When you create a proxy service based on a WSDL, you can select only a WSDL port or a WSDL binding, as a WSDL may or may not have a port defined. The WSDL port describes what the actual transport address is. This, however, is not used for proxy services. The URL is specified in the transport configuration for the service.
You may change the transport protocol of a service to another compatible one in the transport configuration for the service.
A service and port will be in the generated WSDL only for HTTP and HTTPS (not for JMS; other transports are not supported). For SOAP services, any existing <wsdl:service> definition is removed and a new one containing a single <wsdl:port> is created.
For XML services, the only standard WSDL binding definition available is the one defined for HTTP. This is used for JMS as well, in the generated WSDL.
If the WSDL is SOAP-based, then the variables are similar to AnySOAP except that $operation will be initialized based on the Operation Selection algorithm (See To Add a Proxy Service - Operation Selection Configuration. Likewise, if the WSDL is XML-based, then the variables are similar to AnyXML except that the $operation will be initialized based on the Operation Selection algorithm.
Any SOAP Service
Binding Definition: The only information this service type defines is that the service is receiving or sending SOAP messages—regardless of their WSDL binding definition. Therefore the binding configuration for this type is empty.
In addition, as there is no binding configuration, the combination of this type and the content-type of the message is sufficient to determine whether or not there are attachments to the message.
As per their definition, “any” services (SOAP or XML) do not have any WSDL definition. It is not possible to request a WSDL document for those services.
Run-Time Variables:
The $body and $header variables respectively hold the <soap:Body> and <soap:Header> of the incoming SOAP message.
Note:
For SOAP 1.2 proxies, the $body and $header are SOAP 1.2 namespace Body and namespace, not SOAP 1.1 namespace Body and namespace.
The $attachments variable contains the SOAP message attachments, if any.
The $operation variable is not applicable to this service type as you do not define a port type.
Binding Definition: The only information this service type defines is that the service is receiving/sending XML messages—regardless of their WSDL binding definition. Therefore, the binding configuration for this type is empty.
In addition, as there is no binding configuration, the combination of this type and the content-type of the message is sufficient to determine whether or not there are attachments to the message.
As per their definition, “any” services (SOAP or XML) do not have any WSDL definition. It is not possible to request a WSDL document for those services.
Run-Time Variables:
The $body variable holds the incoming XML message wrapped in a <soap:Body> element.
Note:
For SOAP 1.2 proxies, the $body and $header are SOAP 1.2 namespace Body and namespace, not SOAP 1.1 namespace Body and namespace.
The $attachments variable contains message attachments, if there are any.
The $header variable is not applicable to this service type and is set to its default value.
The $operation variable is not applicable to this service type as you do not define a port type.
Binding Definition: The binding definition for messaging services consists of configuring the content-type of the messages that are exchanged. The content-type for the response does not need to be the same as for the request; therefore, the response is configured separately (for example, the service could accept an MFL message and return an XML acknowledgment receipt) and could also be set to None.
As per their definition, messaging-based services do not have any WSDL definition. It is not possible to request a WSDL document for those services.
There are four available content types to choose from for the request (and response):
Binary
Text
XML
MFL
Run-Time Variables:
This service type is message based. There is no concept of multiple “operations” as for Web services. Therefore, the $operation variable is left empty.
The $body variable holds the incoming message wrapped in a <soap:Body> element.
The $header variable is not applicable to this service type, and is set to its default value.
The $attachments variable contains message attachments if there are any.
Note:
For SOAP 1.2 proxies, the $body and $header are SOAP 1.2 namespace Body and namespace, not SOAP 1.1 namespace Body and namespace.
The Proxy service types and transports are supported by AquaLogic Service Bus are listed in the following table.
Table 16-4 Proxy Service Types and Transports Supported by AquaLogic Service Bus
Service Type
Transport Protocols
SOAP WSDL
JMS
HTTP(S)
Local
SOAP (no WSDL)
JMS
HTTP(S)
Local
XML
HTTP(S)
JMS
E-mail
File
FTP
Tuxedo
Local
Messaging Type (Binary, Text, MFL, XML)
HTTP(S)
JMS
E-mail
File
FTP
Tuxedo
Local
Security-Related Validation
When you activate a session that contains changes to an active-intermediary proxy service, AquaLogic Service Bus validates the changes to ensure that you have created all of the credentials that the proxy service’s static endpoints require. For example, if you configured a proxy service to have a Web service as a static endpoint and the Web service requires a digital signature, AquaLogic Service Bus verifies that you have associated a proxy service provider with the proxy service and that the proxy service provider contains a key-pair binding that can be used as a digital signature.
If a session contains a change to the key-pair bindings of a proxy service provider, AquaLogic Service Bus validates the change against all of the proxy services that use the proxy service provider. For example, if you remove the encryption key-pair, AquaLogic Service Bus reports a validation error for any proxy service that references the proxy service provider and whose endpoint requires encryption.
The following criteria determine when AquaLogic Service Bus performs this security-related validation and the actions that it takes during validation:
If a proxy service specifies a static route and operation, AquaLogic Service Bus determines which credentials the static route and operation require. If the proxy service is missing the required credentials, AquaLogic Service Bus will not commit the session until you add the missing credentials.
If a proxy service specifies a static route but the operation is passed through from the inbound request, AquaLogic Service Bus determines which credentials the static route and each of the route’s operations require. If the proxy service is missing the required credentials, AquaLogic Service Bus issues a validation warning, but allows you to commit the session.
If a proxy service specifies a dynamic route and operation, AquaLogic Service Bus cannot validate the security requirements and you risk the possibility of runtime errors. For information about dynamic routing, see “Dynamic Routing” in Modeling Message Flow in AquaLogic Service Bus in the AquaLogic Service Bus User Guide.
The Edit a Proxy Service - General Configuration page allows you to add a proxy service.
Proxy services are AquaLogic Service Bus definitions of services implemented locally on WebLogic Server. You define a proxy service in terms of WSDLs, pipelines, and policies. To learn more, see Overview of Proxy Services.
To add a proxy service, you must first configure general information for the service, configure general and protocol-dependent transport information for the service, then configure operation selection algorithms for the service if it includes operations. If this is a messaging service, you must also configure the message types. You can review the configuration before you create the proxy service.
If you have not already done so, from the left navigation pane, under Change Center, click Create to create a new session for making changes to the current configuration. To learn more, see Using the Change Center.
From the left navigation pane, select Project Explorer. The Project View page is displayed.
Select the project to which you want to add the proxy service. You can add a proxy service directly under the project, or you can add the proxy service under a selected folder.
Note:
Click the name of a folder to select it. The Folder View page is displayed.
From the Project View or Folder View page, in the Create Resource field, select Proxy Service from under Service. The Create a Proxy Service - General Configuration page is displayed.
In the Service Name field, enter a unique name for the proxy service.
In the Description field, enter a description for the proxy service.
In the Service Type field, do one of the following.
Note:
A service type defines the types and packaging of the messages exchanged by the service. This is a required field.
Select WSDL port and click Browse. The Select a WSDL page is displayed.
Click a WSDL resource from the list to select it, the Select a WSDL definition page is displayed, showing the port and binding information for that WSDL.
From Select WSDL Definitions, select a port or binding definition.
NOTE: port and binding options are mutually exclusive. You can only select one or the other.
Click Submit to close the dialog box and return to the General Configuration page.
Note:
If you are going to use the SOAP Body Type selection for operations, ensure that the WSDL does not have two operations with the same input message. The SOAP Body Type operation cannot be uniquely identified by inspecting the input message.
Select Messaging Service to create a service that can receive messages of one data type and respond with messages of a different data type. These exchanges can be either request/response or one-way. Unlike Web services, the content-type of the request and response need not be the same.
Note:
HTTP GET is only supported in the Any XML Service and Messaging Service service types.
Create a proxy service from an existing business service
Select Business Service fromunder Create from Existing Service.
Click Browse. The Service Browser is displayed.
In the Service Browser, select a business service.
Click Submit to close the dialog box and return to the General Configuration page.
This enables you to create a proxy service with a route node that routes to the business service you select. To learn more about business services, see Overview of Business Services.
Note:
You cannot create a proxy service from a transport typed business service.
Note:
If you create a proxy service from a DSP transport business service, ALSB will switch the transport type of the proxy service to HTTP. This is because the DSP transport cannot be used for proxy services. You can then change the transport type of the proxy service to any other available transport.
Create a proxy service from an existing proxy service
Select Proxy Service fromunder Create from Existing Service.
Click Browse. The Service Browser is displayed.
In the Service Browser, select a proxy service.
Click Submit to close the dialog box and return to the General Configuration page.
This enables you to clone a new proxy service from the proxy service you select.
Since AquaLogic Service Bus does not accept the same URI for multiple services, you must change the URI for the cloned service.
Note:
1Note: When you create a business service or proxy service based on a WSDL, you can select only a WSDL port or a WSDL binding, as a WSDL may only have one of these entities defined. The WSDL port describes what the actual transport address is. You use it for a concrete interface.
In the Proxy Service Provider field, select the name of a proxy service provider:
Click Browse. The Service Provider Browser is displayed.
In the Service Provider Browser, select a proxy service provider.
Click Submit to close the dialog box and return to the General Configuration page.
A proxy service provider is only required in certain cases: Outbound 2-way TLS/SSL, where the proxy service routes messages to HTTPS services that require client-certificate authentication, or in some Web service security scenarios; for example, if the proxy service requires messages to be encrypted. To learn more about proxy service providers, see Overview of Proxy Service Providers. To learn how to create a proxy service provider, see Adding a Proxy Service Provider.
Note:
To add a Web service security-enabled proxy service, you must create the proxy service from a WSDL (port or binding) with WS-Policy attachments.
To Add a Proxy Service - Messaging Type Configuration
If you selected Messaging Service in the Service Type field, the Edit a Proxy Service - Message Type Configuration page is displayed when you click Next on the Edit a Proxy Service - General Configuration page.
The binding definition for messaging services consists of configuring the content-type of the messages that are exchanged. The content-type for the response does not need to be the same as for the request; therefore, the response is configured separately (for example, the service could accept an MFL message and return an XML acknowledgment receipt).
Select a message type for the request and response messages:
In the Request Message Type field, select a message type for the request message.
Table 16-6 Request Message Type Field
Message Type
Description
None
Select None if there is no request message.
Binary
Select Binary if the content-type of the message is unknown or not important.
Text
Select Text if the message can be restricted to text.
MFL
Select MFL if the message is a binary document conforming to an MFL definition. You can configure only one MFL file.
Note:
For MFLs, you can click Browse to select a MFL from the MFL Browser, then click Submit.
Note:
To support multiple MFL files, define the content as binary or text and use the MFL action in the message flow to convert to XML.
XML
Select XML if the message is an XML document. To provide some type information, you can choose to declare the XML schema type of the XML document exchanged.
In the Response Message Type field, select a message type for the response message.
Table 16-7 Response Message Type Field
Message Type
Description
None
Select None if there is no response message.
Binary
Select Binary if the content-type of the message is unknown or not important.
Text
Select Text if the message can be restricted to text.
MFL
Select MFL if the message is a binary document conforming to an MFL definition. You can configure only one MFL file.
Note:
For MFLs, you can click Browse to select a MFL from the MFL Browser, then click Submit.
XML
Select XML if the message is an XML document. To provide some type information, you can choose to declare the XML schema type of the XML document exchanged.
The Transport Configuration page is displayed when you click Next on the Edit a Proxy Service - General Configuration page. It is displayed for messaging services when you click Next on the Edit a Proxy Service - Message Type Configuration page.
This page allows you to configure transport information for the proxy service. To learn more about the types of service types and transports supported by AquaLogic Service Bus, see Proxy Service Types and Transports.
Note:
Inbound transport-level security applies to the client applications and AquaLogic Service Bus proxy services. Outbound transport-level security applies to the connections between AquaLogic Service Bus proxy services and business services. To learn more about transport-level security, see Configuring Transport-Level Security in the AquaLogic Service Bus Security Guide.
In the Protocol field, select one of these transport protocols:
E-mail
File
FTP
HTTP
HTTPS
JMS
Tuxedo
Local
In the Endpoint URI field, enter an endpoint URL in the format based on the transport protocol you selected in the Protocol field, then click Add.
Table 16-8 Endpoint URI Field
Transport Protocol
Format
E-mail
mailfrom:mail-server-hostname:mail-server-port
File
file:///drivename:/somename
FTP
ftp://hostname:port/directory
HTTP
/someName
HTTPS
/someName
JMS
jms://host:port/factoryJndiName/destJndiName
To target a target a JMS destination to multiple servers, use the following URI format:
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. To learn more, see JMS Endpoint URIs Must be Available To Activate a Session.
Tuxedo
exportname
The URI exportname 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 displays notifying you that service name already exists.
Local
This transport does not require an endpoint URI.
In the Get All Headers field, select Yes if you want to retrieve all the headers from the transport or select No if you want 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:
AquaLogic Service Bus 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:
Note:
a. In the startup command for AquaLogic Service Bus, set the following system property to true: com.bea.wli.sb.transports.http.GetHttpAuthorizationHeaderAllowed
Note:
b. In the AquaLogic Service Bus Console, on the Transport Configuration page, select Get All Headers or select User-specified Headers and specify Authorization.
Note:
c. Restart AquaLogic Service Bus.
Note:
AquaLogic Service Bus will pass the Authorization header to the pipeline.
To Add a Proxy Service - Protocol-Dependent Transport Configuration
The [Protocol] Transport Configuration page is displayed when you click Next on the Edit a Proxy Service - Transport Configuration page. This page allows you to configure additional transport information for the proxy service, based on the transport protocol you selected in the Protocol field. This step is not required for local transport.
Based on the transport protocol you selected in the Protocol field, do one of the following.
Table 16-9 Protocol Field
Transport Protocol...
Complete These Steps...
HTTP
Select the Basic Authentication Required field to specify that basic authentication is required to access this service, or leave it blank to specify that basic authentication is not required. Basic authentication instructs WebLogic Server to authenticate the client using a username and password against the authentication providers configured in the security realm, such as a Lightweight Directory Access Protocol (LDAP) directory service and Windows Active Directory. The client must send its username and password on the HTTP request header.
NOTE: Basic authentication is strongly discouraged over HTTP because the password is sent in clear text. However, it is safe to send passwords over HTTPS because HTTPS provides an encrypted channel.
WARNING: By default, all users (authorized and anonymous) can access a proxy service. To limit the users who can access a proxy service, create a transport-level authorization policy. See Editing Transport-Level Access Control Policies.
Select the Custom Authentication field to indicate that an authentication token is contained in an HTTP header. The client's identity is established through the use of this client-supplied token. You must configure an Identity Assertion provider that maps the token to an AquaLogic Service Bus user.
The custom authentication token can be of any active token type supported by a configured WebLogic Server Identity Assertion provider.
The Advanced Settings are automatically displayed.
HTTP continued
In the Dispatch Policy field, select a dispatch policy for this endpoint. Leave blank to use the default dispatch policy.
Dispatch policy refers to the instance of WLS 9.0 Work Manager that you want to use for the service endpoint. For example, if the proxy service has a JMS transport protocol, the service endpoint is an MDB (message-driven bean) JAR file that you can associate with the specific dispatch policy.
In the Request encoding field, do the following:
For HTTP inbound transports, if the character set encoding parameter of the Content-Type header is not specified in Client Request, enter a character set encoding parameter in this field. If you do not enter a value, the field defaults to iso-8859-1.
For HTTP outbound transports, if you have not configured a request encoding, the AquaLogic Service Bus run time decides the most appropriate encoding while it makes a request to the business service. In the case of a non-passthrough scenario, the default character encoding is utf-8 at run time. However if it is a passthrough scenario, the run time will pass through the encoding received with the outbound response.
In the Response encoding field, do the following:
For HTTP inbound transports, if you do not enter a response encoding, the binding layer decides the most appropriate encoding while it sends back the response to client. In the case of a non-passthrough scenario, the default character set encoding is utf-8 at run time. However, in the case of a passthrough scenario, the run time will pass through the encoding received with the outbound response.
For HTTP outbound transports, if the character set encoding parameter of the Content-Type header is not specified in the Back End Service response, enter a character set encoding parameter in this field. If you do not enter a value, the field defaults to iso-8859-1.
In the Authentication Header field of the Advanced Settings, enter the HTTP header (any except Authorization) from which AquaLogic Service Bus is to extract the token. This field is available only if you selected the Custom Authentication check box.
For example, client-xyz-token.
Select an Authentication Token Type from the drop-down list in the Advanced Settings. Only the active token types configured for an Identity Assertion provider are available. (See Configuring Identity Assertion Providers for Custom Tokens for more information.) This field is available only if you selected the Custom Authentication check box.
HTTPS
In the Client Authentication field, select the client authentication method: None, Basic, Client certificate, or Custom Authentication.
WARNING: By default, all users (authorized and anonymous) can access a proxy service. To limit the users who can access a proxy service, create a transport-level authorization policy. See Editing Transport-Level Access Control Policies.
If you select the Custom Authentication check box, it indicates that an authentication token is contained in an HTTP header. The client's identity is established through the use of this client-supplied token. You must configure an Identity Assertion provider that maps the token to an AquaLogic Service Bus user.
The Advanced Settings are automatically displayed.
In the Dispatch Policy field, select a dispatch policy for this endpoint. Leave blank to use the default dispatch policy. Dispatch policy refers to the instance of WLS 9.0 Work Manager that you want to use for the service endpoint. For example, if the proxy service has a JMS transport protocol, the service endpoint is an MDB (message-driven bean) JAR file that you can associate with the specific dispatch policy.
In the Request encoding field, accept the default iso-8859-1 as the character set encoding for requests in HTTPS transports, or enter a different character set encoding.
In the Response encoding field, accept the default iso-8859-1 as the character set encoding for requests in HTTPS transports, or enter a different character set encoding.
In the Authentication Header field in the Advanced Settings, enter the HTTP header (any except Authorization) from which AquaLogic Service Bus is to extract the token. This field is available only if you selected the Custom Authentication check box.
For example, client-xyz-token.
Select an Authentication Token Type from the drop-down list in the Advanced Settings. Only the active token types configured for an Identity Assertion provider are available. (See Configuring Identity Assertion Providers for Custom Tokens for more information.) This field is available only if you selected the Custom Authentication check box.
JMS
In the Destination Type field, select Queue or Topic.
If you selected Queue in the Destination Type field, you can optionally select Is Response Required. This option determines whether or not a response is expected after an outbound message is sent. If you do not select the check box, skip to step 6. If you select the check box, continue with step 3.
If you expect a response, you must select a Response Correlation Pattern. For JAX-RPC services running on WebLogic Server 9.2, select JMSMessageID. For all other services, select JMSCorrelationID.
If you selected JMSCorrelationID in step 3, then in the Response URI field, enter a response URI in the format jms://host:port/factoryJndiName/destJndiName. This field is required if you selected Is Response Required. To target multiple servers, use the following URI format: jms://host1:port,host2:port/QueueConnectionFactory/DestName
If you selected JMSMessageID in step 3, then enter a response connection factory URI in the Response Connection Factory field, if a connection factory is not specified, the connection factory for the request is used for the response.
In the Response Message Type field, select Bytes or Text. if you selected the Is Response Required field.
In the Request encoding field, accept the default utf-8 as the character set encoding for requests in JMS transports, or enter a different character set encoding.
In the Response encoding field, accept the default utf-8 as the character set encoding for requests in JMS transports, or enter a different character set encoding.
In the Client Response Timeout field, enter the number of seconds to wait for a server response before dropping the connection. This only applies if the client is another proxy service in the same domain.
In the Dispatch Policy field, select a dispatch policy for this endpoint. Default signifies the default dispatch policy.
Dispatch policy refers to the instance of WLS 9.0 Work Manager that you want to use for the service endpoint to process the request. For example, if the proxy service has a JMS transport protocol, the proxy service endpoint is an MDB (message-driven bean) JAR file that you can associate with the specific dispatch policy.
JMS continued
Click Advanced Settings to display additional fields.
Select the Use SSL check box if the requests are made over a TLS/SSL connection or leave blank if they are not. TLS/SSL (Secure Sockets Layer) provides secure connections by allowing two applications connecting over a network to authenticate the other's identity and by encrypting the data exchanged between the applications. Authentication allows a server, and optionally a client, to verify the identity of the application on the other end of a network connection. Additionally, if the administrator has restricted access to individual JMS destinations (queues or topics) by setting access control on the JNDI entry for the destination, the Business Service must authenticate when looking up the entry in the JNDI tree with a username and password.
In the Message Selector field, enter a message selector expression. Only messages with properties matching the expression are processed.
Select the Durable Subscription check box if the subscription is durable or leave this check box blank if the subscription is not durable.
In the Retry Count field, enter the number of delivery retries a message can have before it is moved to the error destination. This field only applies to WebLogic Server JMS destinations.
In the Retry Interval field, enter the amount of time, in milliseconds, before rolled back or recovered messages are redelivered. This field only applies to WebLogic Server JMS destinations.
In the Error Destination field, enter the name of the target destination for messages that have reached their redelivery limit. This field only applies to WebLogic Server JMS destinations.
In the Expiration Policy field select an Expiration Policy to use when an expired message is encountered on a destination.
NOTE: This applies only to WLS JMS destinations.
In the JMS service account field, select a service account to use for the JMS resource managed by the JMS server. A service account is an alias resource for a User ID and its associated password. To learn more about service accounts, see Overview of Service Accounts.
E-mail
In the Service Account field, enter a service account. You can click Browse to select service accounts from a browser. This is a required field.
In the Polling Interval field, enter a polling interval, in seconds. This is a required field.
In the E-mail Protocol field, select POP3 or IMAP as the server type for the E-mail account. This is a required field.
In the Read Limit field, specify the maximum number of messages to read per polling sweep. Enter 0 to specify no limit. This is a required field.
Select the Pass By Reference field to stage the file in the archive directory and pass it as a reference in the headers, or leave the field blank not to do this.
In the Post Read Action field, select what happens to a message after it has been read (This is a required field):
Archive - the message is archived
Delete - the message is deleted
Move - the message is moved. Move is only available with the IMAP protocol.
In the Attachments field, select how attachments are handled:
Archive - Attachments are saved to the Archive Directory
Ignore - Attachments are ignored
This is a required field.
In the IMAP Move Folder field, enter the folder to which the message is moved if the Post Read Action field is set to Move.
In the Download Directory field, enter a temporary location for downloading the E-mails. This is a required field.
In the Archive Directory field, specify the path to the archive location if the Post Read Action field is set to Archive. The Archive Directory field is also a required field if you have selected the Pass By Reference field.
In the Error Directory field, enter the file system directory path to write the message and any attachments if there is a problem. This is a required field.
In the Request encoding field, accept the default iso-8859-1 as the character set encoding for requests in E-mail transports, or enter a different character set encoding.
File
In the File Mask field, enter the regular expression for the files to be picked. The default is *.*.This is a required field.
In the Polling Interval field, enter a polling interval, in seconds. The default is 60. This is a required field.
In the Read Limit field, specify the maximum number of messages to read per polling sweep. Enter 0 to specify no limit. The default is 10. This is a required field.
Select Sort By Arrival to specify that events are delivered in the order of arrival, or leave blank not to do this.
Note that when the Sort By Arrival option is selected for a proxy service that is executed in a clustered environment, messages are always sent to the same server. In other words, load balancing across servers is ignored when this option is selected.
Select the Scan SubDirectories check box to recursively scan all the directories or leave blank not to do this.
Select the Pass By Reference check box to stage the file in the archive directory and pass it as a reference in the headers, or leave the field blank not to do this.
In the Post Read Action field, select what happens to a message after it has been read (This is a required field):
Archive - the message is archived
Delete - the message is deleted
In the Stage Directory field, enter an intermediate directory to temporarily stage the files while processing them. This is a required field.
In the Archive Directory field, specify the path to the archive location if the Post Read Action field is set to Archive. The Archive Directory field is also a required field if you have selected the Pass By Reference field.
In the Error Directory field, enter the location where messages and attachments are posted if there is a problem. This is a required field.
In the Request encoding field, accept the default utf-8 as the character set encoding for requests in File transports, or enter a different character set encoding.
FTP
In the User Authentication field, select anonymous if the user of the FTP server is anonymous or select external_user if the user of the FTP server is an externally configured account.
In the Identity (E-mail id) or Service Account field, enter the mail ID for the anonymous user if you selected anonymous in the User Authentication field, or enter the service account if you selected external_user in the User Authentication field. This is a required field if you selected external_user.
Select the Pass By Reference check box to stage the file in the archive directory and pass it as a reference in the headers.
Select the Remote Streaming check box to directly stream the FTP files from the remote server at the time of processing or leave blank not to do this. When you select Remote Streaming, the archive directory is the remote directory on the remote FTP server machine. Therefore, you should specify the archive directory as relative to the FTP user directory.
In the File Mask field, enter the regular expression for the files to be picked. The default is *.*.This is a required field.
In the Polling Interval field, enter a polling interval, in seconds. The default is 60. This is a required field.
In the Read Limit field, specify the maximum number of messages to read per polling sweep. Enter 0 to specify no limit. The default is 10. This is a required field.
In the Post Read Action field, select what happens to a message after it has been read. (This is a required field):
Archive - the message is archived
Delete - the message is deleted
In the Transfer Node field, select ascii or binary as the transfer mode.
In the Download Directory field, enter the directory on your local machine where files are downloaded during the file transfer. This is a required field.
In the Archive Directory field, specify the path to the archive location if the Post Read Action field is set to Archive. The Archive Directory field is also a required field if you have selected the Pass By Reference field.
In the Error Directory field, enter the location where messages are posted if there is a problem. This is a required field.
NOTE: The archive, download, and error directories are absolute path, and they are automatically created. If you specify the relative path, the files are created relative to the Java process that starts the WebLogic Server.
In the Request encoding field, accept the default utf-8 as the character set encoding for requests in FTP transports, or enter a different character set encoding.
FTP continued
Click Advanced Settings to display additional fields.
Select the Scan SubDirectories check box to recursively scan all the directories or leave blank not to do this.
Select the Sort By Arrival check box to deliver events in the order of arrival.
In the Timeout field, enter the socket timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout.
In the Retry Count field, specify the number of retries for FTP connection failures.
Tuxedo
In the optional field, Field Table Classes, enter the name of the class or classes describing the FML/FML32 buffer received. These are used for the FML/FML32-to-XML conversion routines to map field names to element names. This is a space separated list of fully qualified class names.
In the optional field, View Classes, enter the name of the class or classes describing the VIEW/VIEW32 buffer received or sent. These are used for the VIEW-to-XML or VIEW32-to-XML conversion routines to map field names to element names. This is a space separated list of fully qualified class names.
NOTE:X_C_TYPE and X_COMMON Tuxedo buffer types are handles in the same manner as VIEW/VIEW32 buffers.
If an incoming request contains a VIEW, then the corresponding VIEW class should be specified in the AquaLogic Service Bus CLASSPATH.
In the Classes Jar field, select a JAR Resource that contains a JAR file with the FML/FML32 or VIEW/VIEW32 classes necessary for this endpoint operation.
Select a Local Access Point from the drop-down list that is associated with the Export. The drop-down list contains local access points configured in WTC. A Proxy Service cannot be created if there is not an associated local access point.
Select the Reply Buffer Type from the drop-down list the type of buffer that the remote Tuxedo client will receive. This field is enabled if the Response Required field is selected.
The Reply Buffer Subtype is enabled if the previous Reply Buffer Type value is VIEW or VIEW32. Enter the buffer subtype with which to associate the reply buffer. This field is enabled if the Response Required field is selected.
Select the check box for Response Required? if this service is expected to send a response. The default status is selected, and deselected if the service type is Messaging Service and the response message type is None. In this case, the field is not enabled.
Tuxedo continued
In the Request Encoding field, specify a character set encoding for requests in Tuxedo transports.
In the Response Encoding field, specify a character set encoding for responses in Tuxedo transports.
In the Transformation Style field, select one of the following choices:
None—(default) The order of fields may not be respected.
Ordered—The fields will be presented with all their occurrences in the correct order.
Ordered and Grouped—If the fields are logically structured as records, the fields will be ordered by occurrence and also grouped by record.
To Add a Proxy Service - Message Level Security Configuration
If this service is of a type that supports message level security, the Create a Proxy Service - Message Level Security Configuration page is displayed. This page allows you to use both custom message-level authentication and WS-Security policies. To learn more about custom message-level authentication and WS-Security policies, see the AquaLogic Service Bus Security Guide.
Message-level custom tokens and message-level username and password are supported on proxy services of the following binding types:
WSDL-SOAP
WSDL-XML
Abstract SOAP
Abstract XML
Mixed – XML (in the request)
Mixed – MFL (in the request)
The configuration for both custom username/password and custom token is similar. In both cases, you specify XPath expressions that enable AquaLogic Service Bus to locate the necessary information. The root of these XPath expressions is as follows:
Use soap-env:Envelope/soap-env:Header if the service binding is AnySOAP or WSDL-SOAP.
Use soap-env:Body if the service binding is not SOAP based.
Note:
All XPath expressions must be in a valid XPath 2.0 format. The XPath expressions must use the XPath “declare namespace” syntax to declare any namespaces used, as follows:
In the Use Custom Authentication field, do one of the following:
Table 16-10 Message Level Security Configuration - Use Custom Authentication
If You Choose...
Complete These Steps...
No
If the proxy service is created from a WSDL (port or binding) that has WS-Policies attached, the Process WS-Security and Effective Request/ResponsePolicy fields are also displayed on the Message Level Security Configuration page. Continue with step 2.
If the proxy service was not created from a WSDL (port or binding) that has WS-Policies attached, Click Next. The page displayed depends on whether the service has operations:
The Advanced Settings are automatically displayed.
In the Custom Authentication Settings field, you must choose either Custom User Name and Password, or Custom Token. (This is a required field.)
Depending on whether you choose Custom User Name and Password, or Custom Token, additional advanced settings are displayed.
If you choose Custom User Name and Password, you must specify both the User Name XPath and the User Password XPath. The XPath expressions are evaluated against the message headers or payload, as appropriate, which allows AquaLogic Service Bus to obtain the username and password values for custom authentication.
If you choose Custom Token, you must specify both the Token Type and the Token XPath.
Select the Token Type from the drop-down list. Only the active token types configured for a WebLogic Server Identity Assertion provider are available. See Configuring Identity Assertion Providers for Custom Tokens for more information.
Enter an XPath expression in the Token XPath field. This is the path to the custom token. AquaLogic Service Bus evaluates the Token XPath expression against the message headers or payload, as appropriate, to obtain the token for custom authentication.
Optionally, specify zero or more Context Properties to pass additional context information to the Authentication (Custom User Name and Password) or Identity Assertion (Custom Token) security provider. Context Properties provides a way (the ContextHandler interface) to pass additional information to the WebLogic Security Framework so that a security provider can obtain contextual information. See Additional Context Properties for Message Level Authentication for more information.
Enter the Property Name as a literal string, and the Value Selector as a valid XPath expression. (XPath expressions can also be literal strings.)
The XPath expressions are evaluated against the same message-part that is used for the custom token or custom username/password. That is, the Value Selector XPath expressions for SOAP-based proxy services evaluate against the header and against the payload for non-SOAP-based proxy services.
The XPath expression is evaluated at runtime to produce the property’s value. A ContextHandler is essentially a name/value list and, as such, it requires that a security provider know what names to look for. Therefore, the XPath expressions are evaluated only if a security provider asks for the value of one of these user-defined properties.
Click Add Property to add this context property. You can add multiple Context Properties.
If the proxy service is created from a WSDL (port or binding) that has WS-Policies attached, the Process WS-Security and Effective Request/ResponsePolicy fields are also displayed on the Message Level Security Configuration page.
The Effective Request/ResponsePolicy field displays read-only views of the effective request/response WS-Policy for all operations.
Do one of the following:
Select Yes in the Process WS-Security Header field if you want the proxy service to behave as an active intermediary, which means it performs decryption, signature verification and so on.
Select No in the Process WS-Security Header field if you want the proxy service to behave as pass-through, which means the proxy service does not decrypt the message or verify the digital signature.
To Add a Proxy Service - Operation Selection Configuration
If this service has operations, the Operation Selection Configuration page is displayed when you click Next on the Protocol Transport Configuration page. This page allows you to enforce WS-I compliance (for SOAP 1.1 services only) and select the selection algorithm to use to determine the operation called by this proxy service. This option is only available for SOAP or XML services defined from a WSDL.
The WSDL specification defines a default algorithm to compute which operation is called based on the type of the SOAP message received. However, there are cases (for example, performance issues, signature/encryption issues, or the default algorithm is not applicable) when you may need to select the operation based on other means.
AquaLogic Service Bus provides additional algorithms. Each of them follows the same pattern and are based on the evaluation of an expression to get a value that is then used to lookup the corresponding operation in a static table.
Note:
AquaLogic Service Bus is generally very forgiving if an inbound message is either missing data such that the operation cannot be determined, or has data that does not correspond to a valid operation. Both of these conditions result in $operation being empty. Rather than reject all such messages, AquaLogic Service Bus does not initialize the operation variable in the context but otherwise continues to process the message.
Note:
However, security requirements are enforced if the proxy service is WSDL-based and at least one of the following conditions is true:
The WSDL has a WS-Security policy and the proxy is an active intermediary.
The proxy has message-level custom authentication (either custom token or username/password).
Note:
If these conditions are met, then there is a runtime check to make sure the operation selection algorithm returns a valid operation name. If the operation selection returns null or an operation that is not in the WSDL, then the message is rejected and an error is raised.
For SOAP 1.1 services only: Select Enforce WS-I Compliance if you want to specify whether or not the service is to conform to the Basic Profile defined by the Web Services Interoperability Organization.
When a service is marked WS-I compliant, checks are performed against the messages sent to and from that service. For Proxies, checks are performed against request messages received by the Proxy. For invoked services (i.e. services invoked by a Proxy via Service Callout action or Route Node), checks are performed against the response messages received from those services. Note that it is the WS-I compliance property of the invoked service and no the proxy that determines whether or not checks are performed against messages received from the invoked service. If you specify WS-I compliance testing for an invoked service, the message flow generates a fault for response errors.
In the Selection Algorithm field, select one of the following.
Table 16-11 Selection Algorithm Field
Selection Algorithm
Description
Transport Header
If you select this selection algorithm, you can define the transport header that contains the lookup value.
SOAPAction Header
If you select this selection algorithm, operation mapping is done automatically from the WSDL associated with this proxy service.
WS-Addressing
If you select this selection algorithm, the lookup value is contained by the WS-Addressing Action tag located in the SOAP headers of the SOAP message.
SOAP Headers
If you select this selection algorithm, you can define an XPath expression evaluated against the SOAP headers, which allows you to get the lookup value.
SOAP Body Type
This is the default algorithm defined by the WSDL specification to compute which operation is called based on the type of the SOAP message received.
Note:
If the proxy service is configured for a Web service security pass-through scenario with an encrypted body, you cannot select the SOAP Body Type selection algorithm. A similar caveat applies to pass-through encrypted SOAP headers.
If you have a WSDL that has two operations with the same input message, do not choose the SOAP Body Type selection algorithm for operations, because the operation cannot be uniquely identified by inspecting the input message.
Note:
If you are creating an XML service type based on a WSDL port or binding, the following selection algorithms are displayed on this page: Transport Header and Payload Type.
Additional fields are displayed depending on the selection algorithm you select.
Based on the algorithm you selected in the Selection Algorithm field, do one of the following.
Table 16-12 Selection Algorithm Field
Selection Algorithm...
Complete These Steps...
Transport Header
In the Header Name field, enter the transport header that extracts the value used as a key to select the operation being invoked.
Under the Operation Mapping field, specify the value for each operation in the Value field. The value is used as the key of the operation. This is a required field.
SOAPAction Header
There are no additional fields displayed for this selection algorithm.
WS-Addressing
Under the Operation Mapping field, specify the value for each operation in the Value field. The value is used as the key of the operation. This is a required field.
SOAP Headers
In the XPath Expression field, specify the XPath expression that extracts the value used as a key to select the operation being invoked.
Under the Operation Mapping field, specify the value for each operation in the Value field. The value is used as the key of the operation. This is a required field.
SOAP Body Type
There are no additional fields displayed for this selection algorithm.
Payload Type
There are no additional fields displayed for this selection algorithm.
To Add a Proxy Service - General Configuration Review
The General Configuration Review page is displayed when you click Next on the Operation Selection Configuration page. This page allows you to review the configuration data that you have entered for this proxy service. If necessary, you can click Edit to make changes to the configuration before you save the proxy service.
Do one of the following:
To make a change to one of the configuration pages, click Edit for the appropriate page.
To return to the previous page, click Back.
To create the proxy service, click Save. The proxy service is created.
The Project View or Folder View page is displayed. The new proxy service is included in the list of resources.
To disregard changes, click Cancel.
Note:
After you create a proxy service, the next step is to configure its Message Flow. Message Flow defines the implementation of a proxy service. Message Flows can include pipeline pairs and the following nodes: Start, Route, and Branch. To learn more, see Overview of Message Flow and Viewing and Changing Message Flow.
Note:
The new proxy service is saved in the current session. When you have finished making changes to this configuration, from the left navigation pane, click Activate under Change Center. The session ends and the core configuration is updated. Alternatively, click Discard at any time during the session to discard the changes you have made so far in the current session.
Generating WSDLs from a Proxy Service
When you create a proxy service based on a WSDL Binding, AquaLogic Service Bus sets the new service and port definitions in the WSDL generated for the proxy service. Regardless of whether you define a proxy service based on a WSDL port or a WSDL binding, the WSDL generated for the proxy service defines only a single port. If the service is generated from port X in the template WSDL, then port X is also defined in the generated WSDL. Any other ports defined in the template WSDL are not included in the generated WSDL. Furthermore, if you base the proxy service on a WSDL port, the generated WSDL uses that port name and preserves any WS-Policies associated with that port. The binding is determined from the port, and in turn, the port type is determined from the binding.
If the service is generated from binding Y in the template WSDL, the generated WSDL defines a new service and port (<service-name>QSService and <port-name>QSPort). None of the ports defined in the template WSDL are included in the generated WSDL.
If you base the service on a WSDL binding template, there may be multiple ports in that WSDL associated with that binding. Each port can use a different URL and have a different WS-Policy attached to it. Therefore, the generated WSDL uses the binding but generates an artificial port for that binding with no WS-Policy. For all WSDL-based services, the transport type and transport URL can be overwritten in the transport section of the service definition.
In a clustered domain, when generating the dynamic WSDL, AquaLogic Service Bus rewrites the endpoint URL based on the server or cluster configuration. If a front-end HTTP host/port (or a front-end HTTPS host/port for HTTPS endpoints) has been specified, it will be used; otherwise, the managed server host or port will be used. It is strongly advised that a front-end HTTP or HTTPS host/port is assigned in clustered domains.
You can get the WSDL for an HTTP(S)-based proxy service by entering the URL for the service appended with ?WSDL in your browser’s Address field.
The Summary of Proxy Services page allows you to view a list of proxy services. Proxy services are AquaLogic Service Bus definitions of services implemented locally on WebLogic Server. To learn more, see Overview of Proxy Services.
To List and Locate Proxy Services
From the left navigation pane, select Proxy Services from under Resource Browser. The Summary of Proxy Services page is displayed. It displays the following information for each proxy service. For a more detailed description of the properties, see Viewing and Changing Proxy Services.
The path is the project name and the name of the folder in which the proxy service resides. It is a link to the project or folder that contains this resource. To learn more, see Viewing Project Details or Viewing Folder Details.
Actions
For proxy services, the Actions column displays up to three icons:
A Launch Test Console icon, which you can click to invoke the Test Console, which you use to validate and test the design of your services and transformations. To learn more, see Testing Services.
An Edit Message Flow icon, which is a link that enables you to edit pipelines for a specific service. To learn more, see Viewing and Changing Message Flow.
An Export WSDL icon displays for any WSDL-based proxy services. You use the Export WSDL functionality to quickly make a WSDL available for consumption by external tools such as IDEs. Note that this is different than the Export Resources functionality in the System Administration module, which you use to move and stage resources between two domains. Click the Export WSDL icon to export the WSDL. To learn more, see Exporting a WSDL.
Options
The Options column displays the following:
A Delete icon that enables you to delete a specific service. To learn more, see Deleting Proxy Services.
You cannot delete a resource if it is referenced by other resources in AquaLogic Service Bus. Instead of the Delete icon, a Delete icon with a red X is displayed for these resources.
To locate a specific proxy service, do one of the following:
Filter by proxy service name. In the Name and Path fields, enter the name and path of the search target, then click Search. The path is the project name and the name of the folder in which the proxy service resides. The services matching the search criteria are displayed.
Resort the list. Click on an underlined column name. Ascending and descending arrows indicate the sort order. Click the column name to change the sort order.
Scroll through the pages. Use the page controls above or below the table. Go to a page by selecting the page number or by using the arrow buttons to go to the next, previous, first, or last page.
The View Details page displays the following information
Table 16-14 View Details Page
Property
Description
Resource Name
The name of this proxy service.
Last Modified By
The user who created this proxy service or imported it into the configuration.
Last Modified On
The date and time that the user created this proxy service or imported it into the configuration.
References
The number of objects that this proxy service references. If such references exist, click the link to view a list of the objects. To learn more, see Viewing References.
Referenced by
The number of objects that reference this proxy service. If such references exist, click the link to view a list of the objects. To learn more, see Viewing References.
Description
A description of this proxy service, if one exists.
The View Details page displays the following General Configuration information.
Table 16-15 General Configuration Information
Property
Description
Service Type
The service type
Proxy Service Provider
The name of the proxy service provider
If the service type for this proxy service is Messaging Service, the page displays the following Message Type Configuration information.
Table 16-16 Message Type Configuration Information
Property
Description
Request Message Type
A message type for the request message: None, Binary, Text, MFL, or XML.
Response Message Type
A message type for the response message: None, Binary, Text, MFL, or XML.
The page displays the following Transport Configuration information.
Table 16-17 Transport Configuration Information
Property
Description
Protocol
The transport protocol
Endpoint URI
The endpoint URI
Get All Headers
Whether all the headers or a defined set of headers are retrieved from the transport
If the transport protocol is E-mail, the page displays the following E-mail Transport Configuration information.
Table 16-18 E-mail Transport Configuration Information
Property
Description
E-mail Protocol
A server type for the E-mail account:
pop3
imap
Service Account
The service account for this mail server
Polling Interval
A polling interval, in seconds.
Read Limit
The maximum number of messages read per polling sweep. 0 signifies no limit.
Pass By Reference
Whether or not the file is staged in the archive directory and passed as a reference in the headers
Post Read Action
Whether or not a message is archived, deleted or moved after it has been read:
Archive - the message is archived
Delete - the message is deleted
Move - the message is moved
Note:
Move is only available with the IMAP protocol.
Attachments
Whether or not attachments are archived or ignored:
Archive - Attachments are saved to the Archive Directory
Ignore - Attachments are ignored
IMAP Move Folder
The folder to which the message is moved if the Post Read Action field is set to Move.
Download Directory
The temporary location for downloading E-mails.
Archive Directory
The path to the archive location if the Post Read Action field is set to Archive. The Archive Directory field is also a required field if you have selected the Pass By Reference field.
Error Directory
The file system directory path to write the message and any attachments if there is a problem.
Request encoding
Displays the character set encoding for requests in E-mail transports. The default is iso-8859-1.
If the transport protocol is File, the page displays the following File Transport Configuration information.
Table 16-19 File Transport Configuration Information
Property
Description
File Mask
The regular expression applied for this file to be picked.
Polling Interval
The polling interval, in seconds.
Read Limit
The maximum number of messages to read per polling sweep. 0 signifiesno limit.
Sort by Arrival
Whether or not events are delivered in the order of arrival.
Scan Subdirectories
Whether or not all the directories are recursively scanned.
Pass By Reference
Whether or not the file is staged in the archive directory and passed as a reference in the headers.
Remote Streaming
Whether or not the ftp files are directly streamed from the remote server at the time of processing.
Post Read Action
Whether or not a message is archived or deleted after it has been read:
Archive - the message is archived
Delete - the message is deleted
Stage Directory
The intermediate directory where files are temporarily staged while they are processed.
Error Directory
The file system directory path to write the message and any attachments if there is a problem.
Archive Directory
The path to the archive location if the Post Read Action field is set to Archive. The Archive Directory field is also a required field if you have selected the Pass By Reference field.
Request encoding
Displays the character set encoding for requests in File transports. The default is utf-8.
If the transport protocol is FTP, the page displays the following FTP Transport Configuration information.
Table 16-20 FTP Transport Configuration Information
Property
Description
Identity (E-mail id)/ Service Account
The mail ID for an anonymous user or service account for an externally configured user.
Timeout
The socket timeout, in seconds
File Mask
The regular expression applied for this file to be picked.
Scan Subdirectories
Whether or not all the directories are recursively scanned.
Pass By Reference
Whether or not the file is staged in the archive directory and passed as a reference in the headers.
Post Read Action
Whether or not a message is archived or deleted after it has been read:
Archive - the message is archived
Delete - the message is deleted
Archive Directory
The path to the archive location if the Post Read Action field is set to Archive. The Archive Directory field is also a required field if you have selected the Pass By Reference field.
Download Directory
The temporary location for downloading FTP files.
Error Directory
The file system directory path to write the message and any attachments if there is a problem.
Retry Count
The number of retries for FTP connection failures.
Polling Interval
The polling interval, in seconds.
Read Limit
The maximum number of messages to read per polling sweep. 0 signifiesno limit.
Sort By Arrival
Whether or not events are delivered in the order of arrival
Transfer Mode
The transfer mode: Binary or ASCII
Request encoding
Displays the character set encoding for requests in FTP transports. The default is utf-8.
If the transport protocol is HTTP, the page displays the following HTTP Transport Configuration information.
Table 16-21 HTTP Transport Configuration Information
Property
Description
Authentication
The client authentication method: None, Basic, or Custom Authentication
Request encoding
Displays the character set encoding for requests in HTTP transports. The default is iso-8859-1.
Response encoding
Displays the character set encoding for responses in HTTP transports. The default iso-8859-1.
If the transport protocol is HTTPS, the page displays the following HTTPS Transport Configuration information.
Table 16-22 HTTPS Transport Configuration Information
Property
Description
Authentication
The client authentication method: None, Basic, Client Certificate, or Custom Authentication
Request encoding
Displays the character set encoding for requests in HTTPS transports. The default is iso-8859-1.
Response encoding
Displays the character set encoding for responses in HTTPS transports. The default iso-8859-1.
If the transport protocol is JMS, the page displays the following JMS Transport Configuration information.
Table 16-23 JMS Transport Configuration Information
Property
Description
Destination Type
The destination type: Queue or Topic.
Is Response Required
Whether or not a response is expected after an outbound message is sent.
Response Correlation Pattern
Correlation pattern options:
JMSCorrelationID
JMSMessageID
Response URI
The Response URI for the JMSCorrelationID
Response Connection Factory
The Response Connection Factory URI for MessageID
Response Message Type
Format for response message
Request Encoding
The character set encoding for requests in JMS transports. The default is utf-8.
Response Encoding
The character set encoding for responses in JMS transports. The default is utf-8.
Client Response Timeout
The number of seconds to wait for a client response before timing out.
Dispatch Policy
The Dispatch policy for this endpoint.
Use SSL
Whether or not the requests are made over a TLS/SSL connection.
Message Selector
The Message selector pattern
Durable Subscription
Whether the subscription is durable or not.
Retry Count
The number of delivery retries configured. before the message is sent to the error destination.
Retry interval
The retry interval in seconds.
Error Destination
The name of the target destination for messages that have reached their delivery limit.
Expiration Policy
The expiration policy used when an expired message is encountered on a destination.
JMS service account
The service account to use for the JMS resource managed by the JMS server.
If the transport protocol is Tuxedo, the page displays the following Tuxedo Transport Configuration information.
Table 16-24 Tuxedo Transport Configuration Information
Property
Description
Field Table Classes
The space separated list of fully qualified FML Files class names for buffer mapping.
View Classes
The space separated list of fully qualified View class names for buffer mapping.
Classes Jar
A JAR Resource that contains a JAR file with the FML/FML32 or VIEW/VIEW32 classes necessary for the endpoint operation.
Local Access Point for URI
The local access point for the URI Endpoint associated with the WTC Export Service.
Reply Buffer Type
The buffer type buffer that the remote Tuxedo client will receive. This field is enabled if the Response Required field is selected.
The buffer subtype with which to associate the reply buffer if the buffer type is VIEW or VIEW32.
Response Required
Selecting the check box indicates Yes. A response is required. Otherwise, no response is required.
The default status is selected, and deselected if the service type is Messaging Service and the response message type is None. In this case, the field is not enabled.
Request Encoding
The character set encoding for requests in Tuxedo transports.
Response Encoding
The character set encoding for responses in Tuxedo transports.
Transformation Style
The ordering or grouping of elements when FML or FML32 buffers are transformed into XML.
The page displays the following Message Level Security Configuration information.
Table 16-25 Message Level Security Configuration Information
Property
Description
Custom Authentication
The client message-level authentication method: None, Custom Username and Password, or Custom Token.
Process WS-Security
Indicates whether the proxy service behaves as an active intermediary.
The page displays the following Operation Selection Configuration information.
Table 16-26 Operation Selection Configuration Information
Property
Description
Enforce WS-I Compliance
For SOAP 1.1 services only: Displays Yes if you selected this option to specify whether or not the service is WS-I compliant, and displays No if you did not want to specify this.
Selection Algorithm
The selection algorithm that determines the operation called by this proxy service.
Header Name
If you selected Transport Header in the Selection Algorithm field for this proxy service, this field displays the transport header that extracts the value used as a key to select the operation being invoked.
XPath Expression
If you selected SOAP Headers in the Selection Algorithm field for this proxy service, this field displays the XPath expression that extracts the value used as a key to select the operation being invoked.
Operation Mapping
If you selected Transport Headers, WS-Addressing or SOAP Headers in the Selection Algorithm field for this proxy service, this field displays the value for each operation. The value is used as the key of the operation.
If you have not already done so, from the left navigation pane, under Change Center, click Create to create a new session or click Edit to enter an existing session to make changes to the current configuration. For more information, see Using the Change Center.
To make a change to the fields on the configuration pages, click Edit for the appropriate page. See Adding a Proxy Service for a description of the pages and fields.
Note:
You cannot change the Service Name or Service Type fields.
Do one of the following:
To update the proxy service, click Finish. The Edit a Proxy Service– Summary page is displayed. Click Save to commit the updates.
To return to the previous page, click <<Prev.
To disregard changes and return to the Summary of Proxy Services page, click Cancel.
Note:
The proxy service is updated in the current session. When you have finished making changes to this configuration, from the left navigation pane, click Activate under Change Center. The session ends and the core configuration is updated. Alternatively, click Discard at any time during the session to discard the changes you have made so far in the current session.
The Summary of Proxy Services page allows you to delete a proxy service. To learn more, see Overview of Proxy Services.
Note:
You cannot delete a resource if it is referenced by other resources in AquaLogic Service Bus. Instead of the Delete icon, a Delete icon with a red X is displayed for these resources.
Note:
You must delete all service-level access control policies and transport-level access control policies associated with a proxy service before you delete that service from AquaLogic Service Bus.
To Delete a Proxy Service
If you have not already done so, from the left navigation pane, under Change Center, click Create to create a new session for making changes to the current configuration. To learn more, see Using the Change Center.
From the left navigation pane, select Proxy Services from under Resource Browser. The Summary of Proxy Services page is displayed.
In the Options field of the proxy service you want to delete, click the Delete icon.
The proxy service is removed from the list.
Note:
If necessary, you can undo the deletion of this resource. To learn more, see Undoing a Task.
The proxy service is deleted in the current session. When you have finished making changes to this configuration, from the left navigation pane, click Activate under Change Center. The session ends and the core configuration is updated. Alternatively, click Discard at any time during the session to discard the changes you have made so far in the current session.
