![]() ![]() ![]() ![]() ![]() ![]() |
This section includes the following topics:
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.
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.
Each service type must define the following configurations:
$operation
, $body
, $header
, $attachments
)
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.
For a definition of a WSDL port, see
http://www.w3.org/TR/wsdl#_ports.
|
|||
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.
For a definition of a WSDL Binding, see
http://www.w3.org/TR/wsdl#_bindings.
|
|||
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.
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.
To learn more about the message context variables, see
Message-Related Variables in the AquaLogic Service Bus User Guide.
|
|||
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.
|
|||
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.
To learn more about the message context variables, see
Message-Related Variables in the AquaLogic Service Bus User Guide.
|
|||
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.
To learn more about the message context variables, see
Message-Related Variables in the AquaLogic Service Bus User Guide.
|
The Business service types and transports supported by AquaLogic Service Bus are listed below.
XML (no WSDL)1
|
|
1HTTP GET is only supported for XML with no WSDL. |
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.
The tasks in this procedure include:
Note: | Click the name of a folder to select it. The Folder View page is displayed. |
Note: | A service type defines the types and packaging of the messages exchanged by the service. This is a required field. |
|
|||
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.
|
|||
Select Any XML Service to create an XML service that does not have an explicitly defined, concrete interface.
|
|||
To learn more about proxy services, see Overview of Proxy Services.
|
If you selected Messaging Service in the Service Type field, the Edit a Business Service - Message Type Configuration page is displayed. Continue in To Add a Business Service - Message Type Configuration.
For all other service types, the Edit a Business Service - Transport Configuration page is displayed. Continue in To Add a Business Service - Transport 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).
Note: | File, FTP, or SFTP transport business services whose type is Messaging Service support one-way messaging only; the Response Message Type should be none . If you select an option other than none , the file, ftp, or sftp protocol will not be available on the Transport Configuration page. |
The Transport Configuration page is displayed. Continue in 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 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.
|
|||
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.
|
|||
mq-connection-resource-ref is the path (project/folder ) and name of the MQ connection resource; for example, default/my_MQconnection .
To make the MQ transport available in ALSB, see MQ Connections
|
|||
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. |
An additional Transport Configuration page is displayed. This page allows you to configure protocol-dependent transport information for the business service. Continue in 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.
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. 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. |
|
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. |
|
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. 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. |
|
|
|
|
|
|
|
NOTE: Do not enter * in this field. This character causes a run-time exception. NOTE: Do not enter * in this field. This character causes a run-time exception. |
|
NOTE: Do not enter * in this field. This character causes a run-time exception. NOTE: Do not enter * in this field. This character causes a run-time exception. |
|
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. |
|
|
|
Bytes (for a stream of uninterpreted bytes) For more detailed information, see the Native MQ Transport User Guide. Dispatch policy refers to the instance of WLS Work Manager that you want to use for the service endpoint. |
|
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. |
|
For more information on accessing AquaLogic Data Services Platform from AquaLogic Service Bus, see
http://download.oracle.com/docs/cd/E13171_01/alsb/docs26/aldsp_transport_for_alsb2_6.pdf
|
|
Username Password Authentication - Specifies that a static service account is associated with this authentication method and the client is authenticated using the provided credentials. Host Based Authentication - Specifies that a user name and proxy service provider is required to use this authentication method. Any user connecting from a known host is authenticated using the private key of the host. Public Key Authentication - Specifies that a user name and proxy service provider is required to use this authentication method. Every user has their own private key. |
Note: | 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. |
The General Configuration Review page is displayed. Continue in 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.
The Project View or Folder View page is displayed. The new business service is included in the list of resources.
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. |
Listing and Locating Business Services
Viewing and Changing Business Services
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.
A unique name for the business service. The name is a link to the View Details page. To learn more, 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.
|
|
|
|
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: | Click View All to display all business services. |
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.
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.
|
|
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.
|
|
The View Details page displays the following General Configuration information.
If the service type for this business service is Messaging Service, the page displays the following Message Type Configuration information.
The page displays the following Transport Configuration information:
If the transport protocol is E-mail, the page displays the following E-mail Transport Configuration information:
If the transport protocol is File, the page displays the following File Transport Configuration information:
If the transport protocol is FTP, the page displays the following FTP Transport Configuration information.
If the transport protocol is HTTP, the page displays the following HTTP Transport Configuration information.
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.
|
|
If the transport protocol is HTTPS, the page displays the following HTTPS Transport Configuration information.
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.
|
|
If the transport protocol is JMS, the page displays the following JMS Transport Configuration information.
If the transport protocol is Tuxedo, the page displays the following Tuxedo Transport Configuration information.
If the transport protocol is EJB, the page displays the following EJB Transport Configuration information.
If the transport protocol is DSP, the page displays the following DSP Transport Configuration information.
If the transport protocol is MQ, the page displays the following MQ Transport Configuration information.
If the transport protocol is SFTP, the page displays the following STP Transport Configuration information.
Note: | You cannot change the Service Name or Service Type fields. |
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. |
Listing and Locating Business Services
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. |
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.
Listing and Locating Business Services
Viewing and Changing Business Services
![]() ![]() ![]() |