Console Online Help

Business Services

This section includes the following topics:

• Overview of Business Services
• Adding a Business Service
• Listing and Locating Business Services
• Viewing and Changing Business Services
• Deleting Business Services

 

---

Overview of Business Services

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:

 

Service Types

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:

• Binding definition
• Run-time configuration
• Run-time variables ($operation, $body, $header, $attachments)

Property	Description
WSDL Port	You can base SOAP and XML services on an existing WSDL resource. A WSDL document is available for proxy and 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 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. For a definition of a WSDL port, see http://www.w3.org/TR/wsdl#_ports.
WSDL Binding	You can base SOAP and XML services on an existing WSDL resource. A WSDL document is available for proxy and business services for any transport. This WSDL is used as the base for the final WSDL document. 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 binding describes the structure of the interface and how it is packaged. You use it to map the transport address. For a definition of a WSDL Binding, see http://www.w3.org/TR/wsdl#_bindings. You may change the transport protocol of a service to another compatible one. The transport attribute of the <soap:binding> element, in the <wsdl:binding> referenced by the service, must reflect the value for the selected transport. For SOAP services, any existing <wsdl:service> definition is removed and a new one containing a single <wsdl:port> is created. This <wsdl:port> is configured based on the <wsdl:binding> referenced by the service and its SOAP address contains the address or the service (as defined by its transport). For XML services, the only standard WSDL binding definition available is the one defined for HTTP. However, BEA has added its own standard definition for JMS. So, except in the case of the JMS transport protocol, the standard HTTP binding is used. As for SOAP, any existing <wsdl:service> is removed and a new one is created to reflect the service address. As only HTTP and JMS one-way are supported as standards, the <wsdl:service> is not generated for any other configuration.
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. The $attachments variable contains the SOAP message attachments if any. The $operation variable is not applicable to this service type if the business or proxy service is not created from a WSDL. To learn more about the message context variables, see Message-Related Variables.
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. 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. 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. To learn more about the message context variables, see Message-Related Variables.
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. 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. To learn more about the message context variables, see Message-Related Variables.


 

 

---

Adding a Business Service

The Edit 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:

• To Add a Business - Service - General Configuration
• To Add a Business Service - Message Type Configuration
• To Add a Business Service - Transport Configuration
• To Add a Business Service - Protocol-Dependent Transport Configuration
• To Add a Business Service - General Configuration Review

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. 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 following:

Note: A service type defines the types and packaging of the messages exchanged by the service. This is a required field.

To...	Complete These Steps...
Create a service from WSDL port	1. Select WSDL port from under Create a New Service. 2. Click Browse. The WSDL Browser is displayed. 3. In the WSDL Browser, select a WSDL resource, then select a port in the Definitions pane. 4. 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. To learn more about this service type, see Service Types in Overview of Business Services.
Create a service from WSDL binding	1. Select WSDL binding from under Create a New Service. 2. Click Browse. The WSDL Browser is displayed. 3. In the WSDL Browser, select a WSDL resource, then select a binding in the Definitions pane. 4. 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 binding describes the structure of the interface and how it is packaged. You use it to map the transport address. To learn more about this service type, see Service Types in Overview of Business Services.
Create a messaging service	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. Unlike Web services, the content-type of the request and response need not be the same. To learn more about this service type, see Service Types in Overview of Business Services.
Create a SOAP service that does not have an explicitly defined, concrete interface	Select Any SOAP Service to create a SOAP service that does not have an explicitly defined, concrete interface. To learn more about this service type, see Service Types in Overview of Business Services.
Create an XML service that does not have an explicitly defined, concrete interface	Select Any XML Service to create an XML service that does not have an explicitly defined, concrete interface. Note: HTTP GET is only supported in the Any XML Service service type. To learn more about this service type, see Service Types in Overview of Business Services.
Create a service from an existing business service	1. Select Business Service from under Create from Existing Service. 2. Click Browse. The Service Browser is displayed. 3. In the Service Browser, select a business service. 4. Click Submit to close the dialog box and return to the General Configuration page.
Create a service from an existing proxy service	1. Select Proxy Service from under Create from Existing Service. 2. Click Browse. The Service Browser is displayed. 3. In the Service Browser, select a proxy service. 4. Click Submit to close the dialog box and return to the General Configuration page. To learn more about proxy services, see Overview of Proxy Services.


 
Click Next.

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.

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:

Message Type	Description
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.


 
In the Response Message Type field, select a message type for the response message:

Message Type	Description
None	Select if there no content-type for the 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.


 
Click Next.

The Transport Configuration page is displayed. Continue in To Add a Business Service - Transport Configuration.

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 enables you to configure transport information for the business service. 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. For more information about transport-level security, see "Transport-Level Security" in Securing Inbound and Outbound Messages in the BEA AquaLogic Service Bus User Guide.

In the Protocol field, select one of these transport protocols:
• HTTP
• JMS
• HTTPS
• FTP
• Email
• File

 
In the Load Balancing Algorithm field, select one of these load-balancing algorithms:

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 URL in the format based on the transport protocol you selected in the Protocol field, then click Add:

Transport Protocol	Format
Email	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


 

Note: You can configure multiple URLs. You can click Delete in the Action 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.

In the Retry Count field, specify the number of times the list is retried. The number of retries is for the list of URIs, not the URIs themselves. For example, if you specify 3 in this field, the list is cycled through 3 times.
In the Retry Interval field, specify the number of seconds' wait time between retries.
Click Next.

An additional Transport Configuration page is displayed. This page enables you to configure protocol-dependent transport information for the business service. Continue in To Add a Business Service - Protocol-Dependent Transport Configuration.

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 enables 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:

Transport Protocol...	Complete These Steps...
HTTP	1. In the Timeout field, enter the timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout. 2. 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. 3. Select the Basic Authentication Required checkbox 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. 4. 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. 5. 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. 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. 6. In the Request encoding field, accept the default iso-8859-1 as the char set encoding for requests in HTTP transports, or enter a different char set encoding. 7. In the Response encoding field, accept the default iso-8859-1 as the char set encoding for responses in HTTP transports, or enter a different char set encoding.
HTTPS	1. In the Timeout field, enter the timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout. 2. 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. 3. 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. 4. In the Service Account field, click Browse to select a 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. 5. 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. 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. 6. In the Request encoding field, accept the default iso-8859-1 as the char set encoding for requests in HTTPS transports, or enter a different char set encoding. 7. In the Response encoding field, accept the default iso-8859-1 as the char set encoding for requests in HTTPS transports, or enter a different char set encoding.
JMS	1. In the Destination Type field, select Queue or Topic. 2. Select the Use SSL checkbox 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. 3. In the Message Type field, select Bytes or Text. 4. 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. 5. If you selected Queue in the Destination Type field, select the Is Response Required checkbox or leave it blank. This checkbox determines whether or not a response is expected after an outbound message is sent. When you select the checkbox, you must enter data in two additional fields: Response URI and Response Timeout. 6. 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 7. 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. 8. 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. 9. 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. 10. In the Request encoding field, accept the default utf-8 as the char set encoding for requests in JMS transports, or enter a different char set encoding. 11. In the Response encoding field, accept the default utf-8 as the char set encoding for requests in JMS transports, or enter a different char set encoding. 12. In the JMS service account field, click Browse to select a service account to use for the JMS server connection.To learn more, see Overview of Service Accounts.
JMS continued	13. 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. 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.
Email	1. In the Mail Server address field, enter an existing SMTP server in the format host:port. This is a required field if you do not select a JNDI name in the Mail Session field. 2. In the Service Account field, click Browse to select a service account. This is a required field if the SMTP Server used requires authentication. A service account is an alias resource for a username and password. 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. 3. In the Mail Session field, select the JNDI name of a configured session. This is a required field if you do not enter an SMTP server name in the Mail Server address field. 4. In the From Name field, enter a display name for the originating email account for this service. 5. In the From Address field, enter the originating email account for this service. 6. In the Reply To Name field, enter a display name for the reply to email account. 7. In the Reply To Address field, enter an email address to reply to. 8. In the Request encoding field, accept the default iso-8859-1 as the char set encoding for requests in Email transports, or enter a different char set encoding.
File	1. 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. 2. 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. 3. In the Request encoding field, accept the default utf-8 as the char set encoding for requests in File transports, or enter a different char set encoding.
FTP	1. 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. 2. In the 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. 3. In the Timeout field, enter the socket timeout, in seconds. The default is 60 seconds. 4. 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. 5. 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. 6. In the Transfer Node field, select ascii or binary as the transfer mode. 7. In the Request encoding field, accept the default utf-8 as the char set encoding for requests in File transports, or enter a different char set encoding.


 

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.

Click Next.

The General Configuration Review page is displayed. Continue in To Add a Business Service - General Configuration Review.

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 enables 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 delete the changes you have made so far in the current session.

Related Topics

Listing and Locating Business Services

Viewing and Changing Business Services

Deleting Business Services

 

---

Listing and Locating Business Services

The Summary of Business Services page enables 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:

Property	Description
Name	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.
Path	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 or Viewing Folder Details.
Options	The Options column displays the following: A Manage Monitoring icon. The icon is a link to the Manage Monitoring page, which enables you to view alerts for a specific service. To learn more, see Listing and Locating Alert Rules. 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. Ascending and descending arrow buttons indicate sortable columns—in this case, the Name and Path columns. Click the button to change the sort order.
• Scroll through the pages. Use the controls in the lower right corner. 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.

Note: Click View All to display all business services.

Related Topics

Adding a Business Service

 

---

Viewing and Changing Business Services

The View Details page enables 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.

To View and Change Business Service Details

Locate the business service. To learn more, see Listing and Locating Business Services.
Click the business service name.

The View Details page displays the following information

Property	Description
Resource Name	The name of this business service.
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:

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:

Property	Description
Request Message Type	A message type for the request message: 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:

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 Email, the page displays the following Email 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


 


 

If the transport protocol is File, the page displays the following 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


 


 

If the transport protocol is FTP, the page displays the following FTP Transport Configuration information:

Property	Description
User Authentication	The user authentication method: anonymous or externally configured account
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


 


 

If the transport protocol is HTTP, the page displays the following 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.
Service Account	A service account for this transport.


 


 

If the transport protocol is HTTPS, the page displays the following 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.
Service Account	A service account for this transport.


 


 

If the transport protocol is JMS, the page displays the following JMS Transport Configuration information:

Property	Description
Destination Type	The destination type: Queue or Topic.
Use SSL	Whether or not 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.
JMS service account	The service account to use for the JMS server connection.


 

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 delete the changes you have made so far in the current session.

Related Topics

Overview of Business Services

Listing and Locating Business Services

Adding a Business Service

Deleting Business Services

 

---

Deleting Business Services

The Summary of Business Services page enables 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 delete the changes you have made so far in the current session.

Related Topics

Listing and Locating Business Services

Adding a Business Service

Viewing and Changing Business Services

Contact BEA |  Feedback |  Privacy  |