Business services are AquaLogic Service Bus definitions of the enterprise services with which you want to exchange messages. You define business services using WSDLs (Web Services Definition Language) just as you would define a proxy service. However, the configuration of business services differs from that of proxy services in that a business service does not have a pipeline. Therefore, a business service is any service not implemented by the BEA AquaLogic Service Bus pipelines.
Note:
If a business service requires Web service security, make sure the WSDL you specify has the necessary WS-Policies attached when you create the business service. Furthermore, if the WS-Policy of the business service requires encryption, make sure the public certificate of the business service is embedded in the WSDL. If the business service is a WebLogic Server 9.0 Web service, you can retrieve its WSDL using the http://<host>:<port>/<service url>?WSDL URL, the public certificate will be automatically embedded for you if necessary.
The following table lists the Business Services pages you can access from the Resource Browser and the Project Explorer modules.
Table 15-1 Pages Accessed from Project Explorer and Resource Browser Modules
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 15-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)
Transport Configuration
You can configure the following parameters for each business service:
List of <string URI, integer weight> pairs—for example, <http://www.bea.com, 100>. For a random-weighted list, the list should contain at least one element.
Load-balancing algorithm—enumeration, one of round-robin, random, or random-weighted. If you select random-weighted, the weights are applicable for each URI.
Retry Count
Retry Interval
The transport you select must be able to support the transport mode (that is, 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 so that it can choose the transport mode accordingly. 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 use the routing options action in the message flow to set the mode for a route or publish.
Based on the transport and WSDL or interface, the transport mode is automatically selected, but you can overwrite it using the routing options action for a route or publish
Each service type must define the following configurations:
Binding definition
Run-time configuration
Run- ($operation, $body, $header, $attachments)
Table 15-3 Service Type Configuration
Property
Description
WSDL Port
You can base SOAP and XML services on an existing WSDL resource. A WSDL resource may be used for business services for HTTP, HTTPS, and JMS transports. This WSDL is used as the base for the final WSDL document.
When you create a business 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. For HTTP(S) business services, this is used as the default URL that can be overridden.
You can base SOAP and XML services on an existing WSDL resource. A WSDL resource may be used for business services, for any transport. This WSDL is used as the base for the final WSDL document.
When you create a business 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 binding describes the structure of the interface and how it is packaged. The transport address is separately specified in the service definition.
You may change the transport protocol of a service and override separately in the service definition what is specified in the transport attribute of the <soap:binding> element, in the <wsdl:binding> referenced by the service.
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.
Run-Time Variables:
The $body and $header variables respectively hold the <soap:Body>and<soap:Header>of the SOAP message to the business service being routed to or published.
Note:
For SOAP 1.2 service, 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.
To learn more about the message context variables, see Message-Related Variables in the AquaLogic Service Bus User Guide.
Transport-Typed
Transport typed services have an empty binding definition and only applies to EJB business services. A WSDL is not specified. Instead the transport automatically defines the WSDL for the service. A zip containing this WSDL can be exported from the console. This WSDL however will not have a port defined.
The EJB Transport-Typed Service is an outbound transport to access EJBs from AquaLogic Service Bus. It is a self-described transport that generates a WSDL to describe its service interface. The EJB transport features transaction and security context propagation.
Business services built using an EJB transport can be used for publish, service call out, and service invocation.
Any XML Services
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.
Run-Time Variables:
The $body variable holds the incoming XML message wrapped in a <soap:Body> element.
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.
Note:
For SOAP 1.2 service, the $body and $header are SOAP 1.2 namespace Body and namespace, not SOAP 1.1 namespace Body and namespace.
To learn more about the message context variables, see Message-Related Variables in the AquaLogic Service Bus User Guide.
Messaging Services
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).
By definition, messaging-based services do not have any WSDL definition. It is not possible to request a WSDL document for those services.
The following content types are available to choose from for the request (and response):
Binary
Text
XML
MFL
None
Run-Time Variables:
This service type is message based.
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 service, the $body and $header are SOAP 1.2 namespace Body and namespace, not SOAP 1.1 namespace Body and namespace.
To learn more about the message context variables, see Message-Related Variables in the AquaLogic Service Bus User Guide.
Business Service Types and Transport
The Business service types and transports supported by AquaLogic Service Bus are listed below.
Table 15-4 Business Service Types and Transports Supported by AquaLogic Service Bus
The Create a Business Service pages enable you to add a new business service. Business services are AquaLogic Service Bus definitions of the enterprise services with which you want to exchange messages. To learn more, see Overview of Business Services.
To add a business service, you must first configure general information for the service, then configure general and protocol-dependent transport information for the service. If this is a messaging service, you must also configure the message types. You can review the configuration before you create the new business service.
To Add a Business - Service - General Configuration
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 business service. You can add a business service directly under the project, or you can add the business 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 Business Service from under Service. The Edit a Business Service - General Configuration page is displayed.
In the Service Name field, enter a unique name. This is a required field.
In the Description field, enter a description for this business service.
In the Service Type field, do one of the tasks described in the following table.
Note:
A service type defines the types and packaging of the messages exchanged by the service. This is a required field.
Table 15-5 Service Type Field
To...
Complete These Steps...
Create a service from a WSDL
Select WSDL Web Service fromunder Create a New Service.
Click Browse. The WSDL Browser is displayed.
In the WSDL Browser, select a WSDL resource, then select a port or a binding in the Select a WSDL page.
Click Submit to close the dialog box and return to the General Configuration page.
Note:
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.
Select Messaging Service to create a service that exchanges messages of very different content-type. These exchanges can be either request/response or one-way. It can also just have a response with no request when used with the HTTP ‘GET’ option for the HTTP transport. Unlike Web services, the content-type of the request and response need not be the same.
To Add a Business Service - Message Type Configuration
If you selected Messaging Service in the Service Type field, the Edit a Business Service - Message Type Configuration page is displayed when you click Next on the Edit a Business 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 15-6 Request Message Type Field
Message Type
Description
None
Select None if there is no request message (HTTP GET example)
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 an 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.
In the Response Message Type field, select a message type for the response message.
Table 15-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 an 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.
To Add a Business Service - Transport Configuration
The Transport Configuration page is displayed when you click Next on the Edit a Business Service - General Configuration page. It is displayed for messaging services when you click Next on the Edit a Business Service - Message Type Configuration page.
Note:
This page allows you to configure transport information for the business service. Outbound transport-level security applies to the connections between AquaLogic Service Bus proxy services and business services. For more information 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:
DSP
E-mail
File
FTP
HTTP
HTTPS
JMS
Tuxedo
EJB (only for Transport Typed Service)
In the Load Balancing Algorithm field, select one of these load-balancing algorithms.
Table 15-8 Load Balancing Algorithm Field
Load-Balancing Algorithm
Description
Round-robin
Dynamically orders the URLs that you enter in the Endpoint URI field for this business service. If the first one fails, it tries the next one, and so on until the retry count is exhausted.
For every new message, there is a new order of URLs.
Random
Randomly orders the list of URLs that you enter in the Endpoint URI field for this business service. If the first one fails, it tries the next one, and so on until the retry count is exhausted.
Random-weighted
Randomly orders the list of URLs that you enter in the Endpoint URI field for this business service, but some are retried more than others based on the value you enter in the Weight field.
None
Orders the list of URLs that you enter in the Endpoint URI field for this business service from top to bottom.
In the Endpoint URI field, enter an endpoint URI in the format based on the transport protocol you selected in the Protocol field, then click Add.
Table 15-9 Endpoint URI Field
Transport Protocol
Format
DSP
t3://host:port/dsp-app-name
E-mail
mailto:java-net@java.sun.com
File
file:///drivename:/somename
FTP
ftp://host:port/directory
HTTP
http://host:port/someService
HTTPS
https://host:port/someService
JMS
jms://host:port/factoryJndiName/destJndiName
To target a JMS destination to multiple servers, use the following URI format: jms://host1:port,host2:port/QueueConnectionFactory/DestName
Tuxedo
tuxedo:resourcename[/remotename]
In the URI, resourcename corresponds to a WTC Import name and the remotename corresponds to the service name exported by the remote Tuxedo domain. The URI resourcename is required, and the remotename is optional.
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 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.
EJB
ejb:provider:jndiname
In the URI, provider is the name of the JNDI provider resource, and JNDIname is the JNDI name in the JNDI server for the EJB.
Note:
If the JNDI provider is located on the same server, the JNDI provider need not be specified. The URI then would be ejb::jndiname
Note:
You can configure multiple URIs. You can click the Delete icon in the Options column to delete them at any time. At run time, the URLs are selected based on the load balancing algorithm you selected in the Load Balancing Algorithm field.
Note:
If you selected Random-weighted in the Load Balancing Algorithm field, you can also enter a weight in the Endpoint URI field. The default is 1.
Note:
If you have multiple endpoint defined, and you selected None in the Load Balancing Algorithm field, the order of endpoints is significant. You can re-order the endpoints using the Up and Down arrows in the Options column.
In the Retry Count field, specify the number of times the list is retried. The number in this field indicates the number of times the list of URIs is retried (not the number of URIs in the list). If the number of retries is set to 0, each URI in the list is tried once. If the number of retries is set to 3, each URI is cycled through four times.
In the Retry Interval field, specify the number of seconds the system must pause between retries.
To Add a Business Service - Protocol-Dependent Transport Configuration
The [Protocol] Transport Configuration page is displayed when you click Next on the Edit a Business Service - Transport Configuration page. This page allows you to configure additional transport information for the business service, based on the transport protocol you selected in the Protocol field.
Based on the transport protocol you selected in the Protocol field, do one of the following:
Table 15-10 Protocol Field
Transport Protocol...
Complete These Steps...
HTTP
In the Timeout field, enter the timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout.
In the HTTP Request Method field, select POST or GET as the HTTP request method header for sending a message.
The GET method can include as part of the request some of its own information that better describes what to get. This information is passed as a sequence of characters appended to the request URL in a query string. The POST method passes all its data, of unlimited length, directly over the socket connection as part of its HTTP request body. The exchange is invisible to the client, and the URL doesn't change at all.
Select the Basic Authentication Required check box 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. If you select this field, you must also enter a service account in the Service Account field.
Note:
Basic authentication over HTTP is strongly discouraged because the password is sent in clear text. However, it is safe to send passwords over HTTPS because HTTPS provides an encrypted channel.
In the Service Account field, enter a service account. A service account is an alias resource for a username and password. This is a required field if you selected the Basic Authentication Required field. To learn more about service accounts, see Overview of Service Accounts. You can create service accounts in the Project Explorer module. To learn more, see Adding a Service Account.
HTTP continued
Make sure the Follow HTTP Redirects check box is selected if HTTP redirects, which are requests with a response code 3xx, should be automatically followed. A re-direct occurs when you send an outbound request to the URL of a business service, and that service returns a response code (for example, 302) that says the URL is no longer valid and this request needs to be sent to another URL. If the Follow HTTP Redirects check box is selected, AquaLogic Service Bus automatically re-sends the request to the new URL without any action on your part. Uncheck this check box if you do not want the HTTP redirects to be automatically followed.
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 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 HTTP 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 responses in HTTP transports, or enter a different character set encoding.
HTTPS
In the Timeout field, enter the timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout.
In the HTTP Request Method field, select POST or GET as the HTTP request method header for sending a message.
The GET method can include as part of the request some of its own information that better describes what to get. This information is passed as a sequence of characters appended to the request URL in a query string. The POST method passes all its data, of unlimited length, directly over the socket connection as part of its HTTP request body. The exchange is invisible to the client, and the URL doesn't change at all.
In the Business Service Authentication field, select None, Basic, or Client Certificates as the business service authentication method. If you select Basic, you must also enter a service account in the Service Account field.
In the Service Account field, click Browse to select a static service account. A service account is an alias resource for a username and password. This is a required field if you selected Basic in the Business Service Authentication field.To learn more about service accounts, see Overview of Service Accounts. You can create service accounts in the Project Explorer module. To learn more, see Adding a Service Account.
Make sure the Follow HTTP Redirects check box is selected if HTTP redirects, which are requests with a response code 3xx, should be automatically followed. A re-direct occurs when you send an outbound request to the URL of a business service, and that service returns a response code (for example, 302) that says the URL is no longer valid and this request needs to be sent to another URL. If the Follow HTTP Redirects check box is selected, AquaLogic Service Bus automatically re-sends the request to the new URL without any action on your part. Uncheck this check box if you do not want the HTTP redirects to be automatically followed.
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 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.
JMS
In the Destination Type field, select Queue or Topic.
In the Message Type field, select Bytes or Text.
If you selected Queue in the Destination Type field, either select the Is Response Required check box or leave it blank. This check box 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 8. If you select the check box, continue with step 4.
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 4, 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 4, then enter a response connection factory URI in the Response Connection Factory field, and a list of JNDI destination names under JNDI Destination Names.
In the Response Timeout field, enter the amount of time to wait for the response, in seconds. This field is required if you selected Is Response Required.
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 Dispatch Policy field, select a dispatch policy for this endpoint. Default signifies the default dispatch policy. Dispatch policy refers to the instance of WLS 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.
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 Expiration field, enter the expiration or time-to-live value for a message, in seconds. If you enter 0, the message never expires.
JMS continued
In the Unit of Order field, enter a message unit-of-order. Message Unit-of-Order is a WebLogic Server value-added feature that enables message producers to group messages into a single unit with respect to the processing order. This single unit is called a Unit-of-Order and requires that all messages from that unit be processed sequentially in the order they were created.
In the JNDI service account field, click Browse to select a service account to use for JNDI lookups. To learn more about service accounts, see Overview of Service Accounts.
In the JMS service account field, click Browse to select a service account (only static service accounts will be displayed) to use for the JMS resource managed by the JMS server. To learn more, see Overview of Service Accounts.
E-mail
In the SMTP Server field, select an SMTP server. NOTE: This is a required field if you do not select a JNDI name in the Mail Session field.
In the Mail Session field, select the JNDI name of a configured session. NOTE: This is a required field if you do not enter an SMTP server name in the Mail Server address field.
In the From Name field, enter a display name for the originating E-mail account for this service.
In the From Address field, enter the originating E-mail account for this service.
In the Reply To Name field, enter a display name for the reply to E-mail account.
In the Reply To Address field, enter an E-mail address to reply to.
In the Connection Timeout field, enter the timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout.
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 Prefix field, enter a prefix that is prepended to the file name. This is a required field.
Note:
Do not enter * in this field. This character causes a run-time exception.
In the Suffix field, enter a suffix that is appended to the file name. This is a required field.
Note:
Do not enter * in this field. This character causes a run-time exception.
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. To learn more about service accounts, see Overview of Service Accounts. You can create service accounts in the Project Explorer module. To learn more, see Adding a Service Account.
In the Timeout field, enter the socket timeout, in seconds. The default is 60 seconds.
In the Prefix for destination File Name field, enter a prefix for the file name under which the file is stored on the remote server. This is a required field.
Note:
Do not enter * in this field. This character causes a run-time exception.
In the Suffix for destination File Name field, enter a suffix for the file name under which the file is stored on the remote server. This is a required field.
Note:
Do not enter * in this field. This character causes a run-time exception.
In the Transfer Node field, select ascii or binary as the transfer mode.
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.
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.
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 Remote Access Point from the drop down list that is associated with the Import. The drop down list contains remote access points configured in WTC. A Business Service cannot be created if there is no associated remote access point.
If more than one URI has been specified, there will be one remote access point field per URI and the URI displays for informative purposes. If more than one URI exists, each requires a different remote access point. If the URI specified already corresponds to an existing WTC resource, the corresponding remote access point displays, but cannot be modified.
Request Buffer Type – Select from the drop-down list the type of buffer that the remote Tuxedo service will receive.
The Request Buffer Subtype is enabled if the previous Request Buffer Type value is VIEW or VIEW32. Enter the buffer subtype with which to associate the request buffer.
Select the check box for Response Required? to indicate a bidirectional call. If not checked, the underlying tpcall is invoked with TPNOREPLY flag, and a null response is posted asynchronously.
Select the check box Suspend Transaction to suspend the transaction, if it exists. This is useful when the remote service does not support transactions.
In the Dispatch Policy drop-downlist, select a WLS Work Manager, if available. The default Work Manager is presented and used if no other WLS Work Manager exists. This Work Manager is used to asynchronously post a null reply in the case of a one-way invocation.
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.
EJB
In the optional field, Service Account, click the Browse button and select a service account from the list displayed. If no service account is specified, AquaLogic Service Bus uses an anonymous subject.
Select the Supports Transaction check box to specify transaction support.
In the Client Jar field, click the Browse button and select an EJB client JAR resource from the list displayed. To learn about creating JAR resources, see Overview of JARs. This is a required field.
In the Converter Jar field, click the Browse button and select an EJB converter class JAR resource from the list displayed. To learn more about EJB client JAR resources and converter classes, see EJB Transport in the AquaLogic Service Bus User Guide.
In the Home Interface drop-down list, select the required EJBHome interface from the options populated by the JAR. The JNDI name in this URI sample must be associated with the EJBHome interface you select here. If the EJB is not of the required type or an EJBHome interface is not specified in the client-jar, a warning will be displayed.
The Remote Interface field will be automatically populated depending on the configuration of the Home Interface.
The Target Namespace field is populated by information picked up from the JAR.
Select Document Wrapped or RPC Style according to your requirements. If two or more methods of your stateless session EJB have the same number and data type of parameters, and you want the operations to be document-oriented, you must specify that they be document-wrapped.
Note:
The style is important because when routing or publishing to the EJB, $body needs to have content that matches the style. Also when calling out to an EJB, the style impacts the parameter contents, especially for document wrapped. Secondly one usage pattern is to define an EJB business service and then create a proxy service with the same WSDL that routes to the EJB. In this case care must be taken on the style of the WSDL because the client tool used to invoke the proxy might have limitations on the style of the WSDL.
Select Encoded or Literal Encoding.
In Methods, select the required methods (you can select multiple methods). Click + to expand the method and: edit the default parameter values and select a converter if provided (or required).
DSP
In the Debug Level field, specify 0 for no debug information, or a higher value to output debug information. Specify 1 to output information on the request message, or 3 to output information on the request and the response message.
In the optional field, Service Account, click the Browse button and select a service account from the list displayed. If no service account is specified, AquaLogic Service Bus uses an anonymous subject.
In the Dispatch Policy drop-down list, select a WLS Work Manager, if available. The default Work Manager is used if no other WLS Work Manager exists. The Work Manager is used to post the reply message for response processing.
If a business service is created from a WSDL that includes WS-Policy attachments, the policies (read-only) are displayed on the [Protocol] Transport Configuration page. If any of the service's WS-Policies specifies authentication, then you must select a service account. A proxy service that routes to this business service will use this service account to authenticate to the business service.
To Add a Business Service - General Configuration Review
The General Configuration Review page is displayed when you click Next on the Protocol Transport Configuration page. This page allows you to review the configuration data that you have entered for this business service. If necessary, you can click Edit to make changes to the configuration before you save the business 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 business service, click Save. The Business Service is created.
The Project View or Folder View page is displayed. The new business service is included in the list of resources.
To disregard changes, click Cancel.
Note:
The new business 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 configuration is deployed to run time. 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 Business Services page allows you to view a list of business services. Business services are AquaLogic Service Bus definitions of the enterprise services with which you want to exchange messages. To learn more, see Overview of Business Services.
To List and Locate Business Services
From the left navigation pane, select Business Services from under Resource Browser. The Summary of Business Services page is displayed, which displays the following information for each business service. For a more detailed description of the properties, see Viewing and Changing Business Services.
The path is the project name and the name of the folder in which the business service resides. It is a link to the project or folder that contains this resource. To learn more, see Viewing Project Details.
Actions
For business services, the Actions column displays the following:
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. For business services, you can only use the Test Console at run time; that is, when the session is activated. To learn more, see Testing Services.
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 Business 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 business service, do one of the following:
Filter by business 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 business 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 allows you to view and change details of a specific business service. Business services are AquaLogic Service Bus definitions of the enterprise services with which you want to exchange messages. To learn more, see Overview of Business Services.
The View Details page displays the following information.
Table 15-12 View Details Page
Property
Description
Resource Name
The name of this business service.
Last Modified By
The user who created this business service or imported it into the configuration.
Last Modified On
The date and time that the user created this business service or imported it into the configuration.
References
The number of objects that this business 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 business 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 business service, if one exists.
The View Details page displays the following General Configuration information.
Table 15-13 General Configuration Information
Property
Description
Service Type
The service type
If the service type for this business service is Messaging Service, the page displays the following Message Type Configuration information.
Table 15-14 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 15-15 Transport Configuration Information
Property
Description
Protocol
The transport protocol
Load Balancing Algorithm
The load balancing algorithm
Endpoint URI
The endpoint URI
Retry Count
The retry count
Retry Interval
The retry interval
If the transport protocol is E-mail, the page displays the following E-mail Transport Configuration information:
Table 15-16 E-mail Transport Configuration Information
Property
Description
Mail Server Address
The SMTP server for this service
Service Account
The service account for this mail server
Mail Session
The mail session for this service
From Name
The originating display name for this service
From Address
The originating address for this service
Reply to Name
The reply to display name for this service
Reply to Address
The reply to address for this service
Request Encoding
The character set encoding for requests in E-mail transports.
If the transport protocol is File, the page displays the following File Transport Configuration information:
Table 15-17 File Transport Configuration Information
Property
Description
Prefix
A prefix that is prepended to the file name.
Suffix
A suffix that is appended to the file.
Request Encoding
The character set encoding for requests in File transports.
If the transport protocol is FTP, the page displays the following FTP Transport Configuration information.
Table 15-18 FTP Transport Configuration Information
Property
Description
User Authentication
The user authentication method: anonymous or externally configured account.
Identity (E-mail id) or Service Account
The mail ID for an anonymous user or service account for an externally configured account.
Timeout
The socket timeout, in seconds.
Prefix for destination File Name
The prefix for the file name under which the file is stored on the remote server.
Suffix for destination File Name
The suffix for the file name under which the file is stored on the remote server.
Transfer Mode
The transfer mode: Binary or ASCII.
Request Encoding
The character set encoding for requests in FTP transports.
If the transport protocol is HTTP, the page displays the following HTTP Transport Configuration information.
Table 15-19 HTTP Transport Configuration Information
Property
Description
Timeout
The amount of time in seconds it takes the service to time out.
HTTP Request Method
The HTTP request method.
Basic Authentication Required
Whether or not basic authentication is required: displays Enabled if it is required.
Follow HTTP Redirects
Whether or not a re-direct occurs when you send an outbound request to the URL of a business service, and that service returns a response code (for example, 302) that says the URL is no longer valid and this request needs to be sent to another URL. Displays Enabled if AquaLogic Service Bus automatically re-sends the request to the new URL without any action on your part.
Service Account
If you selected one, a service account for this transport.
Request Encoding
The character set encoding for requests in HTTP transports.
Response Encoding
The character set encoding for responses in HTTP transports.
If the transport protocol is HTTPS, the page displays the following HTTPS Transport Configuration information.
Table 15-20 HTTPS Transport Configuration Information
Property
Description
Timeout
The amount of time in seconds it takes the service to time out.
HTTP Request Method
The HTTP request method: POST or GET.
Business Service Authentication
The authentication method for the business service: None, Basic, or Client Certificates.
Follow HTTP Redirects
Whether or not a re-direct occurs when you send an outbound request to the URL of a business service, and that service returns a response code (for example, 302) that says the URL is no longer valid and this request needs to be sent to another URL. Displays Enabled if AquaLogic Service Bus automatically re-sends the request to the new URL without any action on your part.
Service Account
If you selected one, a service account for this transport.
Request Encoding
The character set encoding for requests in HTTPS transports.
Response Encoding
The character set encoding for responses in HTTPS transports.
If the transport protocol is JMS, the page displays the following JMS Transport Configuration information.
Table 15-21 JMS Transport Configuration Information
Property
Description
Destination Type
The destination type: Queue or Topic.
Use SSL
Displays Enabled if the requests are made over a TLS/SSL connection.
Message Type
The message type: Text or Bytes.
Expiration
The expiration or time-to-live value for a message, in seconds. If it is 0, the message never expires.
Is Response Required
Whether or not a response is expected after an outbound message is sent.
Response URI
A response URI in the format jms://host:port/factoryJndiName/destJndiName.
To target multiple servers, use the following URI format: jms://host1:port,host2:port/QueueConnectionFactory/DestName
Response Timeout
The amount of time to wait for the response, in seconds.
Unit of Order
The Message Unit-of-Order that enables message producers to group messages into a single unit with respect to the processing order. This single unit requires that all messages from that unit be processed sequentially in the order they were created.
JNDI service account
The service account to use for JNDI lookups.
Request Encoding
The character set encoding for requests in JMS transports.
Response Encoding
The character set encoding for responses in JMS transports.
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 15-22 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.
Remote Access Point for URI
The remote access point for the URI Endpoint associated with the WTC Import Service.
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.
Suspend Transaction
Selecting the check box indicates Yes. If a transaction exists, it will be suspended. Otherwise the transaction will run.
Dispatch Policy
Refers to the instance of WLS Work Manager that you want to use for the service endpoint.
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.
If the transport protocol is EJB, the page displays the following EJB Transport Configuration information.
Table 15-23 EJB TRansport Configuration Information
Property
Description
Service Account
The service account selected for this business service.
Supports Transaction
Selecting the check box indicates Yes. Transactions will be supported.
Client Jar*
The name of the client JAR that this EJB transport service invokes.
Converter Jar
The name of the converter class JAR that this EJB transport service requires.
Home Interface*
The Home interface URI selected for this service.
Remote Interface*
The Remote Interface URI for the service.
Target Namespace*
The target namespace picked from the JAR information.
Style
Whether the service uses Document Wrapped or RPC Style.
Encoding
Whether the coding for the outbound message should be encoded or literal.
Methods
A list of methods to be invoked by this service.
If the transport protocol is DSP, the page displays the following DSP Transport Configuration information.
Table 15-24 DSP transport Configuration Information
Property
Description
Debug Level
Specifies the output of debug information.
Service Account
If you selected one, a service account for this transport.
Dispatch Policy
Refers to the instance of WLS Work Manager that you want to use for the service endpoint.
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. To learn more, 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 Business 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 return to the previous page, click Back.
To update the business service, click Finish. The Business Service is updated.
The Summary of Business Services page is displayed.
To disregard changes, click Cancel.
Note:
The business 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 configuration is deployed to run time. 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 Business Services page allows you to delete a business service. Business services are AquaLogic Service Bus definitions of the enterprise services with which you want to exchange messages. To learn more, see Overview of Business 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.
To Delete a Business 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 Business Services from under Resource Browser. The Summary of Business Services page is displayed.
In the Options field of the business service you want to delete, click the Delete icon.
The business 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 business 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 configuration is deployed to run time. Alternatively, click Discard at any time during the session to discard the changes you have made so far in the current session.
