Business services are Oracle 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 Oracle Service Bus pipelines.
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Using the Change Center.
Select Project Explorer, then select the project or folder to which you want to add the business service.
On the Project/Folder View page, select Business Service from the Create Resource drop-down list.
On the Create/Edit a Business Service - General Configuration page, provide a name for the service and select the type of service to create.
Click Next. The pages that follow depend on the choices you made on the first page. Enter the appropriate information on each of the subsequent pages, until you reach the summary page, then click Save to save the service in the current session.
For detailed instructions on completing each page, see the following:
If a business service is created from a WSDL that includes WS-Policy attachments, the policies (read-only) are displayed on the Protocol-Specific 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.
Create/Edit a Business Service - Page Reference
Create a business service by selecting Business Service from the Create Resource drop-down list on the Project/Folder View page. When you select that option, it displays the first in a series of pages for configuring and adding business services. The pages displayed vary, depending on the options you choose along the way. The pages are:
Use this page to modify general configuration settings for a business service.
When you create a business service, this is the first page displayed in a series of pages for configuring the service. The pages displayed after this one differ depending on the choices you make on this page.
Table 16-1 Create/Edit a Business Service - General Configuration Page
Option
To create or edit...
Service Name
Enter a unique name for the business service.
Description
Enter a description.
Service Type
A service type defines the types and packaging of the messages exchanged by the service. Select the type of business service to create:
WSDL Web Service - Select this option to create a business service based on a WSDL. Then, enter the WSDL name, qualified by its path (for example, myProject/myFolder/myWSDL). Alternatively, click Browse to select a WSDL from the Select a WSDL page.
(port or binding) - Enter the name of a port (defined in the WSDL) to describe an actual transport address, or enter the name of a binding (defined in the WSDL) to map to a transport address. If you use Browse to select a WSDL, as described above, the Select a WSDL Definition page lists any ports and bindings defined in the WSDL. When you choose a port or a binding on that page, the (port or binding) field is filled with the selected name.
Transport Typed Service - Select this option to create a service that uses the EJB or Flow transport.
Messaging Service - Select this option 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.
Any SOAP Service - Select this option to create a SOAP service that does not have an explicitly defined, concrete interface.
Keep the default SOAP 1.1, or select SOAP 1.2 from the drop-down list.
Any XML Service - Select this option to create an XML service that does not have an explicitly defined, concrete interface.
HTTP GET is only supported for messaging services and this service type.
Business Service - Select this option to clone an existing business service.
Enter the path (project/folder) and the name of the business service; or click Browse to select the business service from the Summary of Business Services page.
Since Oracle Service Bus does not accept the same URI for multiple services, you must change the URI for the cloned service.
Proxy Service - Select this option to create a business service based on an existing proxy service.
Service Type (continued)
Note:
When a service is created from another service, alert rules are maintained in the following way:
When a proxy service is created from a business service or a business service is created from a proxy service, the alert rules, if any, are removed.
When a proxy service is created from another proxy service or a business service is created from another business service, the alert rules, if any, are retained.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure message types for a business service whose type is Messaging Service.
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:
E-mail, 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.
Table 16-2 describes how to use Create/Edit a Business Service - Message Type Configuration page.
Table 16-2 Create/Edit a Business Service - Message Type Configuration Page
Option
To create or edit...
Request Message Type
Select a message type for the request message:
None - Select this option if there is no request message (HTTP GET example)
Binary - Select this option if the content-type of the message is unknown or not important.
Text - Select this option if the message can be restricted to text.
MFL - Select this option if the message is a binary document conforming to an MFL definition. You can configure only one MFL file.
For MFLs, you can click Browse to select an MFL from the MFL Browser, then click Submit.
XML - Select this option 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.
Response Message Type
Select a message type for the response message:
None - Select this option if there is no response message.
Binary - Select this option if the content-type of the message is unknown or not important.
Text - Select this option if the message can be restricted to text.
MFL - Select this option if the message is a binary document conforming to an MFL definition. You can configure only one MFL file.
For MFLs, you can click Browse to select an MFL from the MFL Browser, then click Submit.
XML - Select this option 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.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to select a transport protocol for the business service and to set other general transport configuration settings.
Outbound transport-level security applies to the connections between Oracle Service Bus proxy services and business services. For more information about transport-level security, see Configuring Transport-Level Security in the Oracle Service Bus Security Guide.
Any XML Service: dsp, email, file, ftp, http, jms, jpd, mq (if available), sb, sftp, tuxedo
Load Balancing Algorithm
Select one of these load-balancing algorithms:
Round-robin - This algorithm 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 - This algorithm 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 - This algorithm 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 - This algorithm orders the list of URLs that you enter in the Endpoint URI field for this business service from top to bottom.
Endpoint URI
Enter an endpoint URL in the format based on the transport protocol you selected in the Protocol field, above: The formats are:
To target a JMS destination to multiple servers, use the following URI format: jms://host1:port,host2:port/QueueConnectionFactory/DestName
In a cluster: The host names in the JMS URI must exactly match the host names of the cluster servers as they are configured in WebLogic Server.
jpd - jpd:[<jndi_provider_name>]:<jpd_uri>
jndi_provider_name (optional) is the name of the JNDI provider which corresponds to the WLI JNDI Provider resource. When omitted, the JNDI provider on the local server is used.
<jpd uri> is the relative URL of the JPD on the WLI server. For example, if processes.Process.jpd is in the SampleApp Web project, then the relative URL of the JPD is /SampleApp/processes/Process.jpd.
local-queue-name is the name of the MQ queue from which the business service reads messages.
mq-connection-resource-ref is the path (project/folder) and name of the MQ connection resource; for example, default/my_MQconnection.
Note:
The Endpoint URI cannot contain spaces, so do not create MQ Connection resources or projects/folders with spaces in the names.
To make the MQ transport available in Oracle Service Bus, see MQ Connections.
sb - sb://[<jndi_provider_name/>]service_name
jndi_provider_name (optional) is the name of the Oracle Service Bus JNDI Provider resource. When omitted, the default context is used.
service_name is a target service and corresponds to the remote proxy service URI.
sftp - sftp://hostname:port/directory
tuxedo - tuxedo:resourcename[/remotename]
In the URI, resourcename corresponds to a WTC Import name and 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 have the same value. This allows already defined WTC Imports to make use of WTC load-balancing and failover. For more information, see Oracle Service Bus Interoperability Solution for Tuxedo.
ws - http://host:port/somename or https://host:port/somename
Click Add to add one or more additional URIs. At run time, the URLs are selected based on the load balancing algorithm you selected in the Load Balancing Algorithm field.
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.
If you have multiple endpoint defined, and you selected None in the Load Balancing Algorithm field, the order of endpoints is significant. You can reorder the endpoints using the Up and Down arrows in the Options column.
Oracle Service Bus does not support duplicate endpoint URIs within the same business service.
Retry Count
In case of delivery failure when sending outbound requests, specify the number of times to retry individual URL endpoints; in other words, the number of failover attempts.
For example, a business service has one configured URI (U1) and the number of retries is set to 3. If U1 fails on the first attempt, the system retries the U1 endpoint 3 more times.
If a business service has 2 configured URIs (U1 and U2) and a retry count of 3, if the first attempt (for example, to U1) fails, the system tries (fails over to) the next URI (U2). If that also fails, the system makes two more attempts, once to U1 and once to U2.
Retry Iteration Interval
Specify the number of seconds the system pauses before iterating over all the endpoint URIs in the list again.
For example, a business service has two configured URIs (U1 and U2) and a retry count of 2 with a retry iteration interval of 5 seconds. If the first attempt (to U1) fails, the system tries U2 right away. But if U2 also fails, the system waits for 5 seconds and retries U1 once more.
Retry Application Errors
Select Yes or No.
In case of delivery failure when sending outbound requests, specify whether or not to retry endpoint URIs based on application errors (for example, a SOAP fault).
This field is available only for these transports, HTTP, EJB, JMS, DSP, JPD, Tuxedo, SB, and WS. For more information, see How to Suppress Retries in Case of Application Errors in Oracle Service Bus Operations Guide.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the BPEL-10g (Oracle BPEL Process Manager) transport protocol. For more information on using Oracle Service Bus with Oracle BPEL Process Manager, see the Oracle BPEL Process Manager Transport User Guide.
Property
Description
Role
The BPEL transport is used to send request messages from Oracle Service Bus to Oracle BPEL Process Manager. The business service can serve one of the following roles:
Synchronous Client For synchronous communication with an Oracle Service Bus client, the only location information that is required is the BPEL address. This address is captured statically as the endpoint URI and/or dynamically through URI rewriting.
Asynchronous Client For asynchronous communication with an Oracle Service Bus client, a callback from Oracle BPEL Process Manager to Oracle Service Bus is sent on a different connection than the request, and you must configure Oracle Service Bus to provide the correct callback address. For more information, see “Creating a Callback Proxy for Asynchronous Communication” in the Oracle BPEL Process Manager Transport User Guide.
Service Callback If the business service is designed to be a service callback to Oracle BPEL Process Manager (where Oracle BPEL Process Manager is calling an external service through Oracle Service Bus), the callback address is known only at run time. Use an Endpoint URI of bpel://callback.
If you configure the business service with the marker URI, configure your pipeline logic to dynamically set the URI on $outbound; for example, using the TransportHeader action.
Note:
A Service Callback business service does not support load balancing or failover.
Callback Proxy
This optional field is available only for the Asynchronous Client role. This field lets you select the proxy service (must be either an SB or HTTP proxy of type Any SOAP) that will be used to route callbacks to the Oracle Service Bus client that made the request. For more information, see “Creating a Callback Proxy for Asynchronous Communication” in the Oracle BPEL Process Manager Transport User Guide.
Service Account
For JNDI context security, used to access the Oracle BPEL Process Manager delivery service. Click Browse and select a service account. If no service account is specified, an anonymous subject is used.
There is no restriction on the type of service account that can be configured, such as static or pass-through, but the run time must be able to access a user name and password.
Suspend Transaction
Selecting Suspend Transaction makes the business service non-transactional even if the business service is invoked by a transaction.
If you do not select Suspend Transaction:
If the protocol indicates a WebLogic Server-supported protocol (t3, iiop, http), the transaction is propagated.
If the protocol indicates an OC4J server (ormi, opmn), the BPEL transport throws an exception, since OC4J does not support transaction propagation.
The BPEL transport ignores the Suspend Transaction option in the following situations:
The business service is called with quality of service (QoS) “best-effort.” The BPEL transport automatically suspends any transaction that does not support QoS.
The business service is called with QoS set to “exactly-once” and there is no transaction.
Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists.
For information about Work Managers, see the following WebLogic Server Administration Console Online Help topics:
Use this page to configure transport settings for a business service using the DSP (Oracle Data Service Integrator) transport protocol. Table 16-4 describes how to use this page.
Table 16-4 Create/Edit a Business Service - DSP Transport Configuration Page
Option
To create or edit...
Debug Level
Specify one of the following
0 - for no debug information
1 - to output information on the request message
3 - to output information on the request and the response message
Service Account
Click Browse and select a service account from the list displayed. If no service account is specified, an anonymous subject is used.
Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists.
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the EJB transport protocol. Table 16-5 describes how to use the page.
Table 16-5 Create/Edit a Business Service - EJB Transport Configuration Page
Option
To create or edit...
Pass Caller’s Subject
Select this check box to have Oracle Service Bus pass the authenticated subject from the proxy service when invoking the EJB and no service accounts are configured. Note that the Service Account field is disabled when this option is selected.
Service Account
Click Browse and select a service account from the list displayed. If no service account is specified, an anonymous subject is used.
Select this check box to specify transaction support.
Client Jar
Click Browse and select an EJB client JAR resource from the list displayed. To learn about creating JAR resources, see JARs. This is a required field.
Converter Jar
Click Browse 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 Oracle Service Bus User Guide.
Home Interface
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.
Remote Interface
This field is automatically populated depending on the configuration of the Home Interface.
Target Namespace
This field is populated by information picked up from the JAR.
Style
Select Document Wrapped or RPC 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.
The style is important because when routing or publishing to the EJB, $body must have content that matches the style. Also when calling out to an EJB, the style affects 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.
Encoding
Select Encoded or Literal.
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).
Exceptions
This field appears if a method throws a business exception. If an EJB method throws an exception that has data types not supported by Java Web Services (JWS), such as an ArrayList, use the Exceptions field to select a converter class that converts the exception to a type supported by JWS.
Your converter class must implement com.bea.wli.sb.transports.ejb.ITypeConverter. Converter classes can only be configured for checked exceptions and not for run-time exceptions.
Package the converter class and the converted exception class in the client or converter JAR.
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the e-mail transport protocol. Table 16-6 describes how to use the page.
Table 16-6 Create/Edit a Business Service - E-Mail Transport Configuration Page
Option
To create or edit...
SMTP Server
Select an SMTP server.
This is a required field if you do not select a JNDI name in the Mail Session field.
Mail Session
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.
From Name
Enter a display name for the originating e-mail account for this service.
From Address
Enter the originating e-mail account for this service.
Reply To Name
Enter a display name for the reply to e-mail account.
Reply To Address
Enter an e-mail address to reply to.
Connection Timeout
Enter the timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout.
Request Encoding
Accept the default ISO-8859-1 as the character set encoding for requests in e-mail transports, or enter a different character set encoding.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the file transport protocol. Table 16-7 describes how to use this page.
Table 16-7 Create/Edit a Business Service - File Transport Configuration Page
Option
To create or edit...
Prefix
Enter a prefix to be prepended to the file name.
Do not enter * in this field. This character causes a run-time exception.
Suffix
Enter a suffix to be appended to the file name. This is a required field.
Do not enter * in this field. This character causes a run-time exception.
Request Encoding
Accept the default utf-8 as the character set encoding for requests in File transports, or enter a different character set encoding.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
You use Flow transport-typed business services to access Split-Joins. To learn more about Split-Joins, see Improving Service Performance with Split-Join in the Oracle Service Bus User Guide.
Use this page to configure transport settings for a business service using the Flow transport protocol. Table 16-8 describes how to use this page.
Table 16-8 Create/Edit a Business Service - Flow Transport Configuration Page
Option
To create or edit...
Timeout
Enter the number of seconds to wait for a response. This value is ignored for a request-only (one-way) operation.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the ftp transport protocol. Table 16-9 describes how to use this page.
Table 16-9 Create/Edit a Business Service - FTP Transport Configuration Page
Option
To create or edit...
User Authentication
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.
Identity (E-mail id)
This field is available only if the User Authentication option is set to anonymous.
Enter the mail ID for the anonymous user.
Service Account
This field is available only if the User Authentication option is set to external user.
Enter the socket timeout interval, in seconds, before the connection is dropped. The default is 60 seconds.
Prefix for destination File Name
Enter a prefix for the file name under which the file is stored on the remote server.
Do not enter * in this field. This character causes a run-time exception.
Suffix for destination File Name
Enter a suffix for the file name under which the file is stored on the remote server.
Do not enter * in this field. This character causes a run-time exception.
Transfer Mode
Select ASCII or binary as the transfer mode.
Request Encoding
Accept the default UTF-8 as the character set encoding for requests in ftp transports, or enter a different character set encoding.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
HTTP Transport Configuration Page
The HTTP transport supports both HTTP and HTTPS endpoints.
Use this page to configure transport settings for a business service using the HTTP transport protocol. Table 16-10 describes how to use the page.
Table 16-10 Create/Edit a Business Service - HTTP Transport Configuration Page (Continued)
Option
To create or edit...
Timeout
Enter the response timeout interval in seconds. If you enter 0, there is no timeout.
HTTP Request Method
This parameter lets you to use one of the following HTTP methods in a request:
POST – 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 does not change. For REST-based requests, POST tells the transport to perform a create/replace operation or perform an action with the request.
GET – You 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. You can use GET in a business service with a Service Type of “Any XML Service,” or with a Service Type of “Messaging Service” when the Request Message Type is set to “None.” For REST-based requests, GET retrieves a representation of a remote resource.
PUT – You can use PUT in a business service with a Service Type of “Any XML Service” or “Messaging Service.” PUT tells the transport to perform a create/replace operation with a REST-based request, such as uploading a file to a known location.
HEAD – You can use HEAD in a business service with a Service Type of “Any XML Service,” or with a Service Type of “Messaging Service” when the Response Message Type is set to “None.” HEAD tells the transport to get header information for a remote resource rather than getting a full representation of the resource in a REST-based request.
DELETE – You can use PUT in a business service with a Service Type of “Any XML Service” or “Messaging Service.” DELETE tells the transport to perform a delete operation with a REST-based request.
Note:
If a method is already set in the $outbound/transport/request/http:http-method variable, that value takes precedence over any method you select for HTTP Request Method.
Authentication
Select one of the following:
None - Specifies that authentication is not required to access this service.
Basic - Specifies that basic authentication is required to access this service.
Basic authentication instructs WebLogic Server to authenticate the client using a user name 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 user name and password on the HTTP request header.
Basic authentication is strongly discouraged over HTTP because the password is sent in clear text. However, it is safe to send passwords over HTTPS because HTTPS provides an encrypted channel.
Warning: By default, all users (authorized and anonymous) can access a business service. To limit the users who can access a business service, create a transport-level authorization policy. See Editing Transport-Level Access Policies.
Client Certificate - Specifies encrypted communication and strong client authentication (two-way SSL). To learn more, see Configuring Transport-Level Security in the Oracle Service Bus Security Guide.
Service Account
Enter a service account. A service account is an alias resource for a user name and password. This is a required field if you selected the Basic Authentication Required field.
Select this check box to specify that 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, Oracle Service Bus automatically re-sends the request to the new URL without any action on your part. Deselect this check box if you do not want the HTTP redirects to be automatically followed.
Dispatch Policy
Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists. For information about Work Managers, see Using Work Managers to Optimize Scheduled Work and Create Global Work Managers in the WebLogic Server Administration Console Online Help.
Request Encoding
Accept the default iso-8859-1 as the character set encoding for requests in HTTP transports, or enter a different character set encoding.
Response Encoding
Accept the default iso-8859-1 as the character set encoding for responses in HTTP transports, or enter a different character set encoding.
Proxy Server
Enter a proxy server resource or click Browse to choose an entry from the list of configured proxy server resources.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
JCA Transport Configuration Page
Use this page to configure transport settings using the JCA transport protocol. For more information on using the JCA transport, see the JCA Transport User Guide.
Table 16-11 JCA transport configuration
Option
Description
Adapter Name
A read-only value showing the name of the adapter that the JCA service will use.
Adapter Type
A read-only value showing the adapter type.
Dispatch Policy
Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists.
For information about Work Managers, see the following WebLogic Server Administration Console Online Help topics:
JNDI Service Account is for JNDI context security, used to access the EIS adapter managed connection factory. Click Browse and select a service account. If no service account is specified, an anonymous subject is used.
For JCA business services, there is no restriction on the type of JNDI service account that can be configured, such as static or pass-through, but the run time must be able to access a user name and password. JCA proxy services can use only static JNDI service accounts.
This option determines whether or not connection factory properties, activation spec properties (proxy services), and interaction spec properties (business services) are always used from the WSDL.
If this option is selected (default), the JCA transport interacts with the JCA framework in the following ways, depending on whether you are using managed or non-managed mode:
Managed mode – The activation/interaction spec defined in the JCA WSDL. The Activation/Interaction Spec Properties field is read-only; and if Connection Mode is set to Managed, the Connection Factory Properties field is read-only.
Non-managed mode – Connection factory properties defined in the JCA WSDL. The Activation/Interaction Spec Properties field is read-only.
If this option is deselected, you can override the Activation/Interaction Spec Properties of the WSDL; and in non-managed mode you can override the Connection Factory Properties of the WSDL. At run time the JCA transport interacts with the JCA framework using the JCA WSDL and any activation/interaction spec or connection factory overrides you have provided.
For more information on using this option, see “Endpoint Redeployment” in the JCA Transport User Guide.
Connection Mode
This option determines how the service connects to the associated JCA adapter for the EIS system.
Managed – Recommended for production. The JCA transport connects to the JCA adapter through the JCA adapter-managed connection factory configured in WebLogic Server. For authentication, specify a JNDI service account. If no JNDI service account is specified, an anonymous subject is used. In managed mode, Connection Factory Authentication Properties are read-only.
Non-Managed – The JCA transport connects to the JCA adapter through the JCA adapter framework, which acts as a container for the JCA adapter. For authentication, specify a JNDI service account. If no JNDI service account is specified, an anonymous subject is used. In non- managed mode, Connection Factory Authentication Properties are editable for overrides.
Note:
If you want to change from Non-Managed mode to Managed mode, be sure to deselect the Overwrite Connection Authentication Properties option before changing modes.
Overwrite Connection Authentication Properties
This option indicates whether or not the user name/password in the adapter connection factory is overwritten by the Connection Authentication Service Account credentials. If no JNDI Service Account is specified, an anonymous subject is used.
This option, which is displayed only if the connection factory properties contain user name/password properties, is available in non-managed mode with “Always use configuration from JCA WSDL” deselected.
Connection Authentication Service Account
This field is enabled if “Overwrite Connection Authentication Properties” is enabled and selected. This service account browser displays available service accounts. If the “Overwrite Connection Authentication Properties” option is selected, you must select a service account. For proxy services, only static service accounts are available.
This field if displayed only if the connection factory properties contain user name password properties.
Connection Factory Authentication Properties
This field is displayed only if the Connection Factory Properties contain a user name and password. This field is always read-only.
Connection Factory Properties
This field shows the connection factory properties from the WSDL’s <jca:address> element.
Development and Testing: You can override this value if you deselect “Always use configuration from JCA WSDL” and make the Connection Mode Non-Managed. In production environments, use managed mode, which makes the JCA transport connect to the adapter connection factory configured in WebLogic Server.
Operation Name
Displays a read-only name of the selected WSDL operation. An operation can have its own activation/interaction spec properties, shown in the Activation/Interaction Spec Properties field.
Activation/Interaction Spec Properties
“Activation Spec Properties” is the field name for proxy services; “Interaction Spec Properties” is the field name for business services.
If this service is an inbound service invoked by an EIS application, this field displays the activation spec properties for the JCA inbound operation shown in Operation Name field.
You can override the activation/interaction spec properties if you deselect “Always use configuration from JCA WSDL.”
Note:
For Oracle Adapter Suite adapters, activation/interaction spec properties are displayed as read-only. The Oracle Adapter Suite adapters store their own configurations, which you must change in the Oracle Adapter Suite management tools.
TopLink File Browser
For Oracle Database or Oracle Applications adapters that depend on a database, use this field to select a TopLink mapping file from the file system. The content of the TopLink mapping file is displayed in an editable text box.
Generate a TopLink mapping file in Oracle JDeveloper and import it into Oracle Service Bus.
This option is available only when JMSMessageID is selected for the Response Correlation Pattern.
Enter a response connection factory URI.
If a connection factory is not specified, the connection factory for the request is used for the response.
Response JNDI Names
This option is available only when JMSMessageID is selected for the Response Correlation Pattern.
Enter a list of JNDI destination names
Response Timeout
Enter the amount of time to wait for the response, in seconds. This field is required if you selected Is Response Required.
Request Encoding
Accept the default UTF-8 as the character set encoding for requests in JMS transports, or enter a different character set encoding.
Response Encoding
This option is available only when the Is Response Required check box is selected.
Accept the default UTF-8 as the character set encoding for responses in JMS transports, or enter a different character set encoding.
Dispatch Policy
Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists.
For example, if the business service has a JMS transport protocol, the business service endpoint is an MDB (message-driven bean) JAR file that you can associate with the specific dispatch policy.
Advanced Settings
Use SSL
Select only if the requests are made over a TLS/SSL connection.
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 user name and password.
Expiration
The time interval in milliseconds after which the message will expire. Default value is 0, which means that the message never expires.
Unit of Order
Enter a message unit-of-order. Message unit-of-order enables message producers to group messages into a single unit with respect to the processing order. This single unit-of-order requires that all messages in that unit be processed sequentially in the order they were created.
Pass Caller’s Subject
Select this check box to have Oracle Service Bus pass the authenticated subject when sending a message.
When you enable this field and the business service targets JMS resources in a different domain, enable global trust on both domains. See Configuring Security for a WebLogic Domain in Securing WebLogic Server.
JMS Service Account
Select a service account to use for the JMS resource managed by the JMS server. A service account is an alias resource for a User ID and its associated password. The same service account is used for both JNDI and JMS purposes.
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the JPD transport protocol. Table 16-13 describes how to use the page.
Table 16-13 Create/Edit a Business Service - JPD Transport Configuration Page (Continued)
Option
To create or edit...
System Service Account
Enter the service account for the user, or click Browse to select one from the list displayed.
The system service account specifies the user credentials for the invocation of the WLI stateless session bean that the JPD transport uses to send incoming messages.
If no service account is specified, the inbound request subject is used. If there is no inbound request subject, an anonymous subject is used.
Process Service Account
Enter the service account for the user, or click Browse to select one from the list displayed.
The process service account specifies the user credentials for the invocation of the JPD.
If no service account is specified, the inbound request subject is used. If there is no inbound request subject, an anonymous subject is used
Callback Proxy Location
Enter the location of the proxy service for receiving callbacks from the JPD, specified in the following format:
jms://[host:port[,host:port]*]/MyFactory/MyQueue
Where:
host: (optional) Host name of the Oracle Service Bus server where the callback proxy service is configured
port: (optional) Port number on which Oracle Service Bus is listening for incoming requests
MyFactory: JNDI name of the Queue connection factory
MyQueue: JNDI name of the Queue where the Oracle Service Bus proxy service is waiting for callback requests
In a clustered environment, specify the host name and port numbers of the Managed Servers, separated by a comma (,).
The Callback Proxy Location will be ignored if the JPD being invoked is a synchronous JPD or an asynchronous JPD without callbacks.
Select the check box to propagate the existing transaction within Oracle Service Bus to the JPD.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the native MQ transport protocol. Table 16-14 describes how to use the page.
Table 16-14 Create/Edit a Business Service - MQ Transport Configuration Page
Option
To create or edit...
Message Type
This option is available only when the Is Response Required check box is selected.
Select one of the following:
Bytes (for a stream of uninterpreted bytes)
Text (for text messages)
Is Response Required
Select this option to specify that a response is expected after an outbound message is sent.
Polling Interval
This option is available only when the Is Response Required check box is selected.
Enter a polling interval, in milliseconds. The default is 1000.
Response Correlation Pattern
This option is available only when the Is Response Required check box is selected.
Specify whether the response correlation pattern should be based on MessageID or CorrelationID.
Auto-generate Correlation Value
Select this check box to automatically generate a CorrelationID or MessageID.
MQ Response URI
This option is available only when the Is Response Required check box is selected.
The destination to which the response should be published. Enter a response URI in the same format as the endpoint URI: mq://<local-queue-name>?conn=<mq-connection-resource-ref>
This option is available only when the Is Response Required check box is selected.
Enter the number of seconds to wait for a response before dropping the connection.
Dispatch Policy
This option is available only when the Is Response Required check box is selected.
Select a dispatch policy for this endpoint.
Dispatch policy refers to the instance of WLS Work Manager that you want to use for the service endpoint. For information about work managers, see Using Work Managers to Optimize Scheduled Work and Create Work Manager in the WebLogic Server Administration Console Online Help.
Endpoint URI ‘PUT’ options
Enter the MQ PUT message options from among the following:
MQC.MQPMO_ALTERNATE_USER_AUTHORITY
MQC.MQPMO_DEFAULT_CONTEXT
MQC.MQPMO_FAIL_IF_QUIESCING
MQC.MQPMO_LOGICAL_ORDER
MQC.MQPMO_NEW_CORREL_ID
MQC.MQPMO_NEW_MSG_ID
MQC.MQPMO_NO_CONTEXT
MQC.MQPMO_NO_SYNCPOINT
MQC.MQPMO_NONE
MQC.MQPMO_PASS_ALL_CONTEXT
MQC.MQPMO_PASS_IDENTITY_CONTEXT
MQC.MQPMO_RESOLVE_LOCAL_Q
MQC.MQPMO_SET_ALL_CONTEXT
MQC.MQPMO_SET_IDENTITY_CONTEXT
MQC.MQPMO_SYNCPOINT
MQC.MQPMO_VERSION_1
MQC.MQPMO_VERSION_2
You can use either “|” or “+” to separate multiple options. For example, you can specify the following:
MQC.MQPMO_LOGICAL_ORDER | MQC.MQPMO_NEW_MSG_ID
The MQ PUT message options are applied when the message is placed in the outbound queue.
MQ Unrecognized Response URI
Enter the URI representing the queue to which unrecognized response messages should be sent. Note that this setting is enabled only when the Auto-generate Correlation Value check box is selected.
If you do not specify a value for this field, unrecognized response messages are deleted.
Process RFH2 Headers
Select this option to parse WebSphere MQ RFH2 headers from a message payload and automatically generate an RFH2Headers transport header containing the RFH2 data.
If you do not select this option, the payload is passed through as received.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the SB (Service Bus) transport protocol. Table 16-15 describes how to use the page.
Table 16-15 Create/Edit a Business Service - SB Configuration Page
Option
To create or edit...
Dispatch policy
Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists. For information about Work Managers, see Using Work Managers to Optimize Scheduled Work and Create Global Work Managers in the WebLogic Server Administration Console Online Help.
Timeout
The amount of time in seconds it takes the service to time out.
Note:
The timeout will be ignored when the quality of service is Exactly-Once.
Service Account
Click Browse and select a service account from the list displayed. If no service account is specified, an anonymous subject is used.
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the sftp transport protocol. Table 16-16 describes how to use this page.
Table 16-16 Create/Edit a Business Service - SFTP Transport Configuration Page
Option
To create or edit...
User Authentication
Select one of the following:
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 service key 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 service key provider is required to use this authentication method. Every user has their own private key.
Service Account
Enter the service account for the user, or click Browse to select service accounts from a browser.
Service Key Provider
This option is available only when Host Based or Public Key Authentication is selected.
Enter a service key provider in the Service Key Provider field. You can click Browse to select service key providers from a browser. This is a required field.
Username
This option is available only when Host Based or Public Key Authentication is selected.
Enter the user name.
Timeout
Enter the socket timeout interval, in seconds, before the connection is dropped. If you enter 0, there is no timeout. The default value is 60.
Prefix for destination File Name
Enter the prefix for the file name under which the file is stored on the remote server.
Suffix for destination File Name
Enter the suffix for the file name under which the file is stored on the remote server.
Request Encoding
Accept the default UTF-8 as the character set encoding for requests in SFTP transports.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the Tuxedo transport protocol. Table 16-17 describes how to use the page.
Table 16-17 Create/Edit a Business Service - Tuxedo Transport Configuration Page (Continued)
Option
To create or edit...
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.
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.
Classes Jar
Select a JAR Resource that contains a JAR file with the FML/FML32 or VIEW/VIEW32 classes necessary for this endpoint operation.
Remote Access Point(s)
Select a remote access point from the drop down list that is associated with the Import. The list contains remote access points configured in WTC. A business service cannot be created if there is no associated remote access point.
If no remote access points exist or to create a new one, select New. Enter the corresponding Access Point Name and Network Address in the adjacent fields. Upon validation of the endpoint, the access point is added to the WTC configuration for each WTC server. If no WTC server exists, one is created.
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.
Local Access Point(s)
This field appears only when you select New in the Remote Access Point field.
From the drop-down list, select a local access point to be associated with the newly created remote access point. If none exist or to create a new one, select New. Enter the corresponding Local Access Point Name and Local Network Address in the adjacent fields.
Request Buffer Type
Select the type of buffer that the remote Tuxedo service will receive.
Request Buffer Subtype
This option is enabled if the previous Request Buffer Type value is VIEW or VIEW32. Enter the buffer subtype with which to associate the request buffer.
Response Required?
Select this check box to indicate a bidirectional call. If not checked, the underlying tpcall is invoked with TPNOREPLY flag, and a null response is posted asynchronously.
Suspend Transaction?
Select this check box to suspend the transaction, if it exists. This is useful when the remote service does not support transactions.
Dispatch Policy
Select the instance of WebLogic Server Work Manager that you want to use for the dispatch policy for this endpoint. The default Work Manager is used if no other Work Manager exists.
Specify a character set encoding for requests in Tuxedo transports.
Response Encoding
Specify a character set encoding for responses in Tuxedo transports.
Timeout
Specify the maximum amount of time (in seconds) that the transport run time waits for replies; an integer value that is greater than or equal to 0. If not specified or set to zero (default), replies will time out at BLOCKTIME, the maximum number of seconds that the local WTC access point allows for a blocking call.
Transformation Style
Select one of the following:
None - (default) The order of fields may not be respected.
Ordered - The fields are presented with all their occurrences in the correct order.
Ordered and Grouped - If the fields are logically structured as records, the fields are ordered by occurrence and grouped by record.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure transport settings for a business service using the WS transport protocol. Table 16-18 describes how to use the page.
Table 16-18 Create/Edit a Business Service - WS Transport Configuration Page
Option
To create or edit...
Response Timeout
Enter the number of seconds to wait for a response.
Leaving this field blank indicates that there is no response timeout. The business service will wait for the duration of the sequence timeout configured in the RM policy.
If you enter a zero (0) value, there is no timeout; as such, it will never time out.
Service Account
Enter a service account or click Browse to select one from the list displayed.
The service account specifies the credentials to use when there is an HTTP basic authentication policy on this service.
Advanced Settings
Queue Error Messages
Select the check box to enable sending error messages to the configured error queue.
Error Queue URI
This option is available only when the Queue Error Messages check box is selected.
Enter the URI of the JMS queue for storing error messages, in the following format:
jms://host:port/connFactoryJndiName/queueJndiName
JMS Error Queue Service Account
This option is available only when the Queue Error Messages check box is selected.
Enter a service account or click Browse to select one from the list displayed.
The service account specifies the credentials to use for JNDI lookups and sending error messages to the error queue.
Use SSL for Error Queue
This option is available only when the Queue Error Messages check box is selected.
Select the check box to use SSL for connecting to the error queue.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to configure the SOAP Binding for a business service based on a WSDL.
Select Enforce WS-I Compliance to specify whether or not the service is to conform to the Basic Profile defined by the Web Services Interoperability Organization. This option is available for or SOAP 1.1 services only
When a service is marked WS-I compliant, checks are performed against the messages sent to and from that service.
After you finish
Click Next to continue configuring this service on the next page; or click Last to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to specify how Oracle Service Bus is to encode outbound messages sent by business services and whether Oracle Service Bus should stream attachments in outbound response messages instead of buffering the attachment contents in memory.
Using this page, you can enable the business service to encode outbound messages in MTOM/XOP format. SOAP Message Transmission Optimization Mechanism (MTOM) is a method of sending binary data to and from Web services. MTOM uses XML-binary Optimized Packaging (XOP) to transfer the binary data.
Using this page, you can also enable the business service to store attachments in outbound response messages to a disk file and then process the data in a streaming fashion without buffering the attachment contents in memory. This enables the business service to process large attachments robustly and efficiently.
Table 16-19 Create/Edit a Business Service - Message Content Handling Configuration Page
Option
To create or edit...
XOP/MTOM Support
Oracle Service Bus supports XOP/MTOM using the following transports:
HTTP/S
Local
SB
Select the Enabled check box to enable the business service to encode outbound messages in MTOM/XOP format. Note that this option is disabled for imported business services that are based on previous release configurations.
If XOP/MTOM Support is enabled, select how to handle binary data in the $header and $body message context variables from among the following options:
Include Binary Data by Reference: (Default) In an outbound response message, replace xop:Include elements with ctx:binary-content elements when setting up the $body message context variable.
Include Binary Data by Value: In an outbound response message, replace xop:Include elements with Base64-encoded text versions of corresponding binary data when setting up the $body message context variable.
Note that if XOP/MTOM Support is enabled for a business service, it is not required that every outbound message be in the MTOM format. Instead, this setting specifies that the business service is capable of handling an MTOM payload.
Since Oracle Service Bus does not support a combination of MTOM and SwA, the system issues a runtime error when Oracle Service Bus attempts to dispatch an outbound request to a business service and the business service is both MTOM/XOP-enabled and the $attachments message context variable is not null.
Attachments
Oracle Service Bus supports streaming MIME attachments using the HTTP/S transport.
Select the Page Attachments to Disk check box to enable the business service to stream attachments in outbound response messages.
Note that if you enable XOP/MTOM Support, the Attachments option is only available if you choose the Include Binary Data by Reference option under XOP/MTOM Support. Note also that payloads that contain attachments must conform to RFC 822. Specifically, lines containing Internet headers need to be terminated with CRLF (carriage return line feed).
After you finish
Click Next to review and save this configuration on the Create/Edit a Business Service - Summary page.
Use this page to view or modify the configuration settings for a business service before saving it.
To view or modify settings, click Edit in the row of the appropriate category (for example, General Configuration, Transport Configuration, etc.). The pages you can edit depend on what pages you configured when creating the business service. The following list shows all pages:
Exporting a WSDL Associated with a Business Service
You can export the WSDL of a WSDL-based business service, so you can view or modify the WSDL in an external tool such as an IDE. The WSDL is exported as a JAR file.
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. See Exporting Resources.
Select Resource Browser > Business Services to display the Summary of Business Services page.
Select Project Explorer, then select the project or folder containing the business service you want to export as a WSDL. The Project/Folder View page is displayed.
Click the Export WSDL icon in the row of the business service whose WSDL you want to export. A dialog box prompts you to open or save the exported JAR file.
In the dialog box, click Open to open the file, or click Save to save it.
Select Resource Browser > Business Services. The Summary of Business Services page displays the information shown in Table 16-20. For a more detailed description of the properties, see Editing Business Service Configurations.
To restrict the number of items in the list, you can filter by name, path, or both. In the Name and Path fields, under Search, enter the name and/or path of the target(s), then click the Search button.
The path is the project name and the name of the folder in which the business service resides.
Wildcard characters * and ? are allowed. Search is case-sensitive.
Click View All to display all business services in the domain. This clears the search parameters from the previous search.
Click the Launch Test Console icon 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. For transformations, you can use the Test Console whether you are inside or outside a session. See Testing Services and Testing Transformations.
The Export WSDL icon is displayed for WSDL-based business services. Click this icon to export a WSDL, which you can then view or modify in an external tools such as an IDE. See
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. See Exporting a WSDL.
The Generate WSDL icon is displayed for transport-typed business services, such as EJB and Flow. Click this icon to generate a WSDL, which you can then view or modify. See Generating a WSDL
Options
Click the Delete icon to delete the service. A Deletion Warning icon is displayed when other resources reference this resource. You can delete the resource with a warning confirmation. This might result in conflicts due to unresolved references to the deleted resource. For more information, see Deleting Business Services.
Editing Business Service Configurations
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Using the Change Center.
You don’t have to enter a session if you only want to view details.
To view or modify settings, do either of the following:
Click the Edit icon next to the name of the category whose properties you want to view or edit (for example, General Configuration, Transport Configuration, etc.). The pages you can edit depend on what pages you configured when creating the business service.
Click Edit at the bottom of the page to display the Create/Edit a Business Service - General Configuration page, which is the first page in the sequence of pages for configuring this business service.
On the Edit a Business Service - Summary page, click Save to commit the updates in the current session.
To end the session and deploy the configuration to the run time, click Activate under Change Center.
View a Business Service - Configuration Details page
The View Business Service - Configuration Details page displays the configuration details of a business service. Table 16-21 describes all the properties that can appear on this page. (Properties vary depending on the details of the business service.)
The categories listed on this page correspond to the Create/Edit a Business Service pages used for creating and editing business service configurations, as described in Create/Edit a Business Service - Page Reference.
Click the Edit link next to any category name to display the associated configuration page.
Table 16-21 View a Business Service: Configuration Details Page
Properties
Description
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. Click the date and time link to view the change history of this resource. See View Change History page.
References
The number of objects that this business service references. If such references exist, click the numeric link to view a list of the objects. To learn more, see Viewing References to Resources.
Referenced by
The number of objects that reference this business service. If such references exist, click the numeric link to view a list of the objects. To learn more, see Viewing References to Resources.
Description
A description of this business service, if one exists.
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 Oracle 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.
Proxy Server
The proxy server resource configured for the business service.
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.
Pass Caller’s Subject
Whether Oracle Service Bus is to pass the authenticated subject when sending a message.
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.
Use this page to configure policy settings for a business service that has a WSDL-based policy or that uses custom policy bindings (both WSDL-based and Any SOAP services). Table 16-22 describes how to use the page.
Note that for WSDL-based services, all policies bound to the service are exposed (inlined) in the effective WSDL, regardless of which binding model is used. Abstract policies are pre-processed before they are inlined.
Table 16-22 View a Business Service - Policies Page
Option
To edit...
Service Policy Configuration
There are two options in the Service Policy Configuration field:
WSDL-Based Policy, in which one or more Web Services Policy (WS-Policy) statements in a WSDL document express the business service's message-level security requirements.
Custom Policy Bindings, in which you add service-level policies, operation-level policies (in which case the policy applies to both the request and response messages), request policies, and response policies from the console.
Note:
The two policy binding models are mutually exclusive. If you bind policies directly to the service, all WSDL-based policies are ignored.
Service Level Policies (Custom Policy Bindings Only)
To specify policies that apply to the entire service, expand the service name entry. Click Add to search for and select your policies.
You can select from your own existing WS-Policy resources, or from predefined policies.
You can bind multiple policies to the service.
Update the policy binding.
Operation Level Policies (WSDL-Based Policy Only)
Provides a read-only view of the request and response policies from the WSDL.
To specify policies that apply to an operation, the request/response of that operation, or any request or any response in the case of Any SOAP services, expand the operation name entry. Click Add to search for and select your policies.
You can select from your own existing WS-Policy resources, or from predefined policies.
You can bind multiple policies to the service.
Update the policy binding.
After you finish
Click Update to save this configuration; or click Reset to undo your changes.
All policies bound to the service are exposed (inlined) in the effective WSDL, regardless of which binding model is used. Abstract policies are pre-processed before they are inlined.
Use this page to configure security settings for a business service that has a WSDL-based policy or that uses custom policy bindings. Table 16-23 describes how to use the page.
Table 16-23 View a Business Service - Security Page
Option
To edit...
Service Account
Click Browse and select a service account from the list displayed. If no service account is specified, an anonymous subject is used.
Click Update to save this configuration; or click Reset to undo your changes.
Deleting Business Services
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Using the Change Center.
Select Resource Browser > Business Services to display the Summary of Business Services page.
Click the Delete icon in the row of the business service you want to delete. The business service is deleted in the current session. A Deletion Warning icon is displayed when other resources reference this resource. You can delete the resource with a warning confirmation. This might result in conflicts due to unresolved references to the deleted resource.
To end the session and deploy the configuration to the run time, click Activate under Change Center.
Export WSDL icon in the row of the business service whose WSDL you want to export. A dialog box prompts you to open or save the exported JAR file.
Edit icon next to the name of the category whose properties you want to view or edit (for example, General Configuration, Transport Configuration, etc.). The pages you can edit depend on what pages you configured when creating the business service. 
Delete icon in the row of the business service you want to delete. The business service is deleted in the current session. A 
Deletion Warning icon is displayed when other resources reference this resource. You can delete the resource with a warning confirmation. This might result in conflicts due to unresolved references to the deleted resource.
Launch Test Console icon 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. For transformations, you can use the Test Console whether you are inside or outside a session. See 
Generate WSDL icon is displayed for transport-typed business services, such as EJB and Flow. Click this icon to generate a WSDL, which you can then view or modify. See 
Delete icon to delete the service. A