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.
For more information, see "Configuring Proxy Services and Business Services" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus.
This section describes how to create and configure business services.
For JCA services, you can generate business services from JCA Bindings, as described in Section 19.1.1, "Generating a Business Service from a JCA Binding Resource", or from Oracle Enterprise Repository, as described in Section 19.1.2, "Generating a Business Service from Oracle Enterprise Repository."
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "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 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.
Follow the Section 2.3, "Resource Naming Restrictions" for naming guidance.
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.
You can generate a JCA business service from an outbound JCA Binding resource in Oracle Service Bus. For more information on JCA Binding resources, see Chapter 13, "JCA Bindings."
To generate a JCA business service from a JCA Binding:
In the Oracle Service Bus Administration Console, click Create or Edit in the Change Center if you area not already in Create or Edit mode.
In the Resource Browser, click JCA Bindings.
Locate the JCA Binding from which you want to generate a service, and click the Action icon.
In the window that appears, confirm the name of the WSDL and the service you want to generate, select the location for these new resources, and click Generate.
Oracle Service Bus generates the service and its corresponding WSDL.
Modify any other configuration details on the generated service as appropriate, such as the Endpoint URI.
You can generate a business service from Oracle Enterprise Repository using the Oracle Service Bus development environment. For more information, see "Generating a Business Service from Oracle Enterprise Repository" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Create a business service by selecting Business Service from the Create Resource 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:
The Create/Edit a Business Service - General Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
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 19-1 describes how to use the page.
Table 19-1 Create/Edit a Business Service - General Configuration Page
| Option | To create or edit... |
|---|---|
|
Service Name |
Enter a unique name for the business service. Follow the Section 2.3, "Resource Naming Restrictions" for naming guidance. |
|
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:
Note: When a service is created from another service, alert rules are maintained in the following way:
|
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.
The Create/Edit a Business Service - Message Type Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
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 benone. If you select an option other than none, the file, ftp, or sftp protocol will not be available on the Transport Configuration page.Table 19-2 describes how to use Create/Edit a Business Service - Message Type Configuration page.
Table 19-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:
|
|
Response Message Type |
Select a message type for the response message:
|
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.
The Create/Edit a Business Service - Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
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 Fusion Middleware Developer's Guide for Oracle Service Bus.
Table 19-3 describes how to use this page.
Table 19-3 Create/Edit a Business Service - Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
Protocol |
Select a transport protocol from the list. The protocols available differ, depending on the service type you are creating:
|
|
Load Balancing Algorithm |
Select one of these load-balancing algorithms:
|
|
Endpoint URI |
Enter an endpoint URL in the format based on the transport protocol you selected in the Protocol field. Following are descriptions of the URI formats for each transport. Optional URI elements are shown in brackets []. For more information on transport URIs, see the respective transport chapters in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
|
|
Endpoint URI (continued) |
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 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, Tuxedo, SB, and WS. |
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.
The Create/Edit a Business Service - Protocol-Specific Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
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 "Oracle BPEL Process Manager Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Table 19-4 Create/Edit a Business Service - BPEL-10g Transport Configuration Page
| 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:
|
|
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 "Advanced Use Cases (Asynchronous)" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
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:
The BPEL transport ignores the Suspend Transaction option in the following situations:
For a description of transaction propagation, see "Transaction Propagation" in the at Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
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 Create/Edit a Business Service - DSP Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
For more information, see "DSP and Oracle Data Service Integrator Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Use this page to configure transport settings for a business service using the DSP (Oracle Data Service Integrator) transport protocol. Table 19-5 describes how to use this page.
Table 19-5 Create/Edit a Business Service - DSP Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
Debug Level |
Specify one of the following
|
|
Service Account |
Click Browse and select a service account from the list displayed. If no service account is specified, an anonymous subject is used. For more information: |
|
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. The Work Manager is used to post the reply message for response processing. For information about Work Managers, see:
|
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.
The Create/Edit a Business Service - EJB Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
Use this page to configure transport settings for a business service using the EJB transport protocol. Table 19-6 describes how to use the page.
Table 19-6 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. This option is not available if you use the Pass Caller's Subject option. For more information: |
|
Supports Transaction |
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 Section 8, "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 Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
Home Interface |
EJB 2.1 only – 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, Oracle Service Bus displays a warning. |
|
Remote Interface |
EJB 2.1 only – This field is automatically populated depending on the configuration of the Home Interface. |
|
Business Interface |
EJB 3.0 only – Select the business interface in the client JAR you want to use. |
|
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, |
|
Encoding |
Select Encoded or Literal. |
|
Methods |
The methods displayed are those of the EJB remote or business interface you selected. Select the required methods (you can select multiple methods). Click + to expand the method. Edit the default parameter values and select a converter if provided (or required). You must exclude the methods with parameters or return types that are not supported by the JAX-RPC stack, or you must associate such arguments with converter classes. You can change the default operation name for a given method. (By default, the operation name is the method name.) If an EJB contains methods with same name, you must change the operation names so that they are unique—WSDLs require unique operation names. Note: If the credentials or transaction settings are different between the methods for a given EJB, you can customize the methods for a given business service and create a business service per method. This gives you fine-grained control over transactions and credentials. |
|
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. For more information, see "EJB Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
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.
The Create/Edit a Business Service - E-Mail Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
Use this page to configure transport settings for a business service using the e-mail transport protocol. Table 19-7 describes how to use the page.
Table 19-7 Create/Edit a Business Service - E-Mail Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
SMTP Server |
Select the default SMTP Server to use for endpoint URI entries of name@domain_name.com. If you provide SMTP server parameters in the endpoint URI, as described in Table 19-3, those server resources are used instead of this SMTP Server setting. Do not select an SMTP server if you use the Mail Session option. For more information on creating SMTP resources, see Section 31.7, "Adding SMTP Servers" |
|
Mail Session |
Enter the JNDI name of the configured mail session to use for endpoint URI entries of name@domain_name.com. If you provide JNDI mail session parameters in the endpoint URI, as described in Table 19-3, those mail sessions are used instead of this Mail Session setting. Do not enter a Mail Session if you use the SMTP Server option. |
|
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 |
|
Request Encoding |
Accept the default |
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.
The Create/Edit a Business Service - File Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
Use this page to configure transport settings for a business service using the file transport protocol. Table 19-8 describes how to use this page.
Table 19-8 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 |
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.
The Create/Edit a Business Service - Flow Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
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 Fusion Middleware Developer's Guide for Oracle Service Bus.
Use this page to configure transport settings for a business service using the Flow transport protocol. Table 19-9 describes how to use this page.
Table 19-9 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.
The Create/Edit a Business Service - FTP Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
Use this page to configure transport settings for a business service using the ftp transport protocol. Table 19-10 describes how to use this page.
Table 19-10 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 service account for the external user. For more information: |
|
Timeout |
Enter the socket timeout interval, in seconds, before the connection is dropped. The default is 60 seconds. |
|
Prefix for destination File Name |
Enter an optional prefix that the transport prepends to the file name on the remote server. Do not enter * in this field. This character causes a run-time exception. |
|
Suffix for the destination File Name |
Enter an optional suffix that the transport appends to the file name 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 |
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.
The HTTP transport supports both HTTP and HTTPS endpoints.
The Create/Edit a Business Service - HTTP Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
Use this page to configure transport settings for a business service using the HTTP transport protocol. Table 19-11 describes how to use the page.
Table 19-11 Create/Edit a Business Service - HTTP Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
Read Timeout |
Enter the read timeout interval in seconds. A zero (0) value indicates no timeout. |
|
Connection Timeout |
Enter the connection timeout interval in seconds. If the timeout expires before the connection can be established, Oracle Service Bus raises a connection error. A zero (0) value indicates no timeout. |
|
HTTP Request Method |
This parameter lets you to use one of the following HTTP methods in a 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:
|
|
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. For more information: |
|
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:
|
|
Request Encoding |
Accept the default |
|
Response Encoding |
Accept the default |
|
Proxy Server |
Enter a proxy server resource or click Browse to choose an entry from the list of configured proxy server resources. |
|
Follow HTTP redirects |
Select this check box to specify that HTTP redirects (which are requests with a response code If you select the Follow HTTP Redirects check box, 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. |
|
Use Chunked Streaming Mode |
Select this option if you want to use HTTP chunked transfer encoding to send messages. Note: Do not use chunked streaming with if you use the Follow HTTP Redirects option. Redirection and authentication cannot be handled automatically in chunked mode. |
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 using the JCA transport protocol. For more information on using the JCA transport, see "JCA Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus and Section 19.1.1, "Generating a Business Service from a JCA Binding Resource."
Table 19-12 JCA Transport Configuration Page
| Option | Description |
|---|---|
|
JCA File |
Click Browse to select a JCA Binding. The JCA Binding defines different aspects of the service, such as details about the adapter used, a binding to the WSDL and TopLink or EclipseLink mapping file, and the activation/interaction spec properties required by the service. Once you select a valid JCA Binding, the remaining transport configuration fields become available. For more information on JCA Bindings, see Chapter 13, "JCA Bindings." |
|
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:
|
|
JNDI Service Account |
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. For more information on JNDI service accounts, see "Security" in the "JCA Transport" chapter of the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
EndPoint Properties |
This field lets you assign values to endpoint properties such as retries for the type of adapter the service uses. For a list of supported JCA endpoint properties, see "Endpoint Properties" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
Dynamic EndPoint Properties |
This option lets you pass request parameters to JCA-compliant services. For example, you can use a dynamic endpoint property to pass database query parameters to the Oracle JCA Adapter for Database. For more information on querying with parameters, see "Oracle JCA Adapter for Database" in the Oracle Fusion Middleware User's Guide for Technology Adapters. Enter a name/value pair for each dynamic endpoint property you want to provide. The endpoint property key matches the query parameter name. |
|
Always use configuration from JCA file |
This option determines whether or not Activation Spec Properties (proxy services) and Interaction Spec Properties (business services) are always used from the JCA file. If this option is selected (default), the JCA transport interacts with the JCA framework using the activation/interaction spec properties in the JCA file. If this option is deselected, you can override the Activation/Interaction Spec Properties. For the redeployment impact of using this option, see "Endpoint Redeployment" in the "JCA Transport" chapter of the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
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 file. 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. |
|
Connection properties (legacy) |
For legacy JCA services that use non-managed mode connection properties (deprecated in this release), see the connection configuration options at |
For more information on endpoint and activation/interaction spec properties, see the Oracle Fusion Middleware User's Guide for Technology Adapters.
Use this page to configure transport settings using the JEJB transport protocol. For more information on using the JEJB transport, see "JEJB Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Table 19-13 JEJB Transport Configuration Page
| Option | Description |
|---|---|
|
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:
|
|
EJB Spec Version |
Select the EJB version of the remote EJB interface. |
|
Pass XMLBeans by value |
Select this option if you want the transport to generate an "inlined" XML representation of POJO arguments (an XMLObject) whose parameters you can access and manipulate with XQuery expressions. Note: Type information is not available inline for XMLObjects passed by value. If you use this option, you cannot pass the typed XMLObject as the argument in a Java Callout in a proxy service pipeline. Do not select this option if you want to pass the POJO by reference, which also results in better performance. |
|
Pass Caller's Subject |
As an alternative to selecting a Service Account, select this option to have Oracle Service Bus pass the authenticated subject from the proxy service when invoking the EJB. |
|
Service Account |
Click Browse and select a JNDI service account from the list displayed. If no service account is specified, an anonymous subject is used. For more information, see Chapter 17, "Service Accounts." |
|
Client JAR |
Click Browse and select an EJB client JAR resource from the list displayed. The client JAR contains the remote or business interface for the remote service. The Client JAR is registered as a generic Archive Resource. |
|
Home Interface |
EJB 2.1 only – Select the required EJBHome interface from the options populated by the JAR. |
|
Remote Interface |
EJB 2.1 only – This field is automatically populated based on the configuration of the Home Interface. |
|
Business Interface |
EJB 3.0 only – Select the business interface from the client JAR that you want to invoke. |
|
Target Namespace |
This field is populated by information picked up from the JAR. |
|
Methods |
Select the required methods. Click + to expand the method, which lets you edit the default parameter values. You can change the default operation name for a given method. By default, the operation name is the method name. If an EJB contains methods with same name (overloaded), you must change the operation names so that they are unique. WSDLs require unique operation names. |
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.
The Create/Edit a Business Service - JMS Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
For more information, see "JMS Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Use this page to configure transport settings for a business service using the JMS transport protocol. Table 19-14 describes how to use the page.
Table 19-14 Create/Edit a Business Service - JMS Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
Destination Type |
Select a type for the JMS bridge destination:
|
|
Message Type |
Select one of the following:
This option is disabled if you select a Message Type of Java for the response. |
|
Response Queues |
This option is available only when Queue is selected for the Destination Type. Select one of the following response options:
You can optionally select a service account for JMS/JNDI credentials on each request/response pairing. |
|
Response Pattern |
This option is available only when you select a response option in the Response Queue field. Select one of the following:
For more information, see "Message ID and Correlation ID Patterns for JMS Request/Response" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
Dispatch Policy |
Select the instance of Oracle 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. For information about Work Managers, see:
|
|
Request Encoding |
Enter the character set for encoding requests. The default is UTF-8. |
|
Response Encoding |
This option is available only when one of the response options is selected in the Response Queues field. Enter the character set for encoding responses. The default is UTF-8. |
|
Response Timeout |
This option is available only when one of the response options is selected in the Response Queues field. Enter the amount of time, in seconds, to wait for the response before dropping the connection. The default, zero (0), means the response never times out. |
|
Client Jar |
This option is available when the service is a Messaging Service with a response type of Java. Select the client JAR to be used for dequeueing messages that contain Java Objects. Selecting the client JAR ensures it is on the classpath. For more information, see "Sending and Receiving Java Objects in Messages" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
Response URI |
This option is available when you select the One for all Request URIs response option and the JMSCorrelationID response pattern. Enter a response URI in the format: jms://host:port/connection_factory/jndi_destination To target multiple servers, use the following format: jms://host1:port,host2:port/connection_factory/jndi_destination You can also omit the host and port in the response URI. For example: jms:///connection_factory/jndi_destination When you omit host and port, the connection factory/destination lookup occurs on the local server. This is useful, for example, if the request URI goes to a foreign connection factory/destination, but you want the response sent to the local server. |
|
Request Responses |
This option is available when you select the One per Request URI response option for the JMSCorrelationID pattern to provide response failover. For each request URI entered on the generic Transport page, enter a Response URI, as described in the previous Response URI field. You can select an optional Service Account for JMS/JNDI credentials that the service uses for both the request and response queues. |
|
Target - Responses |
This option is available when you select the One for all Request URIs response option for the JMSMessageID pattern. Enter the name of the Target server that is to receive responses, and enter a Response URI, as described in the Response URI field. |
|
Request Connections |
This option is available when you select the One per Request URI response option for the JMSMessageID pattern to provide response failover. For each request URI, identified sequentially by number in the Seq.No field, optionally enter a JMS Connection Factory name. If you do not enter a name, the JMS transport uses the connection factory from the request URI. You can select an optional Service Account for JMS/JNDI credentials that the service uses for both the request and response queues. |
|
Target - Destinations |
This option is available when you select the One per Request URI response option for the JMSMessageID pattern to provide response failover. Use this field in conjunction with Request Connections. Each Target server listed (determined by the servers in the current domain), such as Managed Servers in a cluster, lists the request URIs by Seq.No, which correspond to those in the Request Connections field. For each request URI on each target, enter the Destination queue on that target server that receives responses. Note: Because the Oracle Service Bus development environment supports only a one-server environment, only one Target is listed. To configure this field in a multi-server environment, deploy this service to the run-time environment and complete the service configuration in the Oracle Service Bus Administration Console. |
|
JMS Service Account |
This option is available when you use the None or One for all Request URIs options in the Response Queues field. Select a service account to use for the JMS resource managed by the JMS server. A service account is an alias resource for a user ID and password, used for both the request and response. The same service account is used for both JMS and JNDI purposes. This field is mutually exclusive with the Pass Caller's Subject option. Use one or the other for JMS/JNDI authentication. For more information, see Section 17, "Service Accounts." |
|
Use SSL |
Select this option 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 service must authenticate when looking up the entry in the JNDI tree. Authenticate using a Service Account or the Pass Caller's Subject option. |
|
Expiration |
The time interval in milliseconds after which the message expires. Default value is 0, which means that the message never expires. |
|
Enable Message Persistence |
The JMS delivery mode the service uses, which lets you balance reliability with throughput. Select this option (default) for guaranteed message delivery. Deselect this option to improve throughput if an occasional lost message is tolerable. |
|
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 Oracle WebLogic Server. This field is mutually exclusive with the Service Account option. Use one or the other for JMS/JNDI authentication. 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 Oracle Fusion Middleware Securing Oracle WebLogic Server. |
|
JNDI Timeout |
The JNDI connection timeout (in seconds) used while looking up the destination or connection factory in the JNDI tree. The default, zero (0), means the connection never times out. |
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.
The Create/Edit a Business Service - MQ Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
For more information, see "MQ Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Before you begin
Configure a MQ Connection resource. See Section 9, "MQ Connections."
To configure the MQ transport
Use this page to configure transport settings for a business service using the native MQ transport protocol. Table 19-15 describes how to use the page.
Table 19-15 Create/Edit a Business Service - MQ Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
Message Type |
Select one of the following:
|
|
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 |
|
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:
|
|
Auto-generate Correlation Value |
This option is available only when the Is Response Required check box is selected. Select this check box to automatically generate a CorrelationID or MessageID. |
|
Model Queue |
For Dynamic Queue Response Correlation Pattern only. Enter the name of the model queue used to generate the dynamic queue. |
|
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 or, if you are using dynamic queues: mq://dynamic_queue_prefix?conn=mq_connection_resource The dynamic_queue_prefix, which is limited to 32 characters, is used to create the dynamic queue on the MQ server. The queue name becomes the prefix plus a unique ID. For example, if the dynamic_queue_prefix is example, the dynamic queue would be named something like example123129083821. You can also use an asterisk (*) as a wildcard in the dynamic queue response URI. For example: mq://dynamic_queue_prefix*?conn=mq_connection_resource mq://dynamic_queue_prefix* mq://* If you do not provide a dynamic_queue_prefix in the URI, the transport uses the dynamic queue name generated by the MQ server. If you do not provide an explicit mq_connection_resource in the URI (best practice), the transport uses the mq_connection_resource from the endpoint URI. For more detailed information, see "MQ Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
Response Timeout |
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 |
Dispatch policy refers to the instance of Oracle WebLogic Server Work Manager that you want to use for the service endpoint. For information about Work Managers, see:
|
|
Dynamic Queue Pooling |
For Dynamic Queue Response Correlation Pattern only. Select this option if you want the service to use pooled connections to dynamic queues. If you want to use a separate connection pool for dynamic queues, consider configuring a dedicated MQ Connection resource for the dynamic queues. Do not select this option if you want to create a new dynamic queue instance on each request (and destroy the queue after the response). |
|
Endpoint URI 'PUT' options |
Enter the MQ PUT message options from among the following:
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. For information about how the MQ transport handles RFH2 headers, see "About RFH2 Headers" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
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.
The Create/Edit a Business Service - SB Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
For more information, see "SB Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Use this page to configure transport settings for a business service using the SB (Service Bus) transport protocol. Table 19-16 describes how to use the page.
Table 19-16 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:
|
|
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. For more information: |
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.
The Create/Edit a Business Service - SFTP Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
For more information, see "HTTP and Poller Transports" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Use this page to configure transport settings for a business service using the sftp transport protocol. Table 19-17 describes how to use this page.
Table 19-17 Create/Edit a Business Service - SFTP Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
User Authentication |
Select one of the following:
|
|
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 |
|
Prefix for destination File Name |
Enter an optional prefix that the transport prepends to the file name on the remote server. Do not enter * in this field. This character causes a run-time exception. |
|
Suffix for the destination File Name |
Enter an optional suffix that the transport appends to the file name on the remote server. Do not enter * in this field. This character causes a run-time exception. |
|
Request Encoding |
Accept the default |
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.
Table 19-18 describes the transport-specific configuration options for the SOA-DIRECT transport.
For more information on the SOA-DIRECT transport, see "SOA-DIRECT Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Table 19-18 Create/Edit a Business Service – SOA-DIRECT Transport Configuration
| Property | Description |
|---|---|
|
JNDI Service Account |
Optional. Specifies the security credentials for the JNDI lookup of the target SOA service. The service account must be static. Click Browse and select a service account. If you do not specify a service account, an anonymous subject is used. |
|
Role |
Required. Identifies the communication pattern the service uses. Select one of the following options:
|
|
Callback Proxy |
Optional. Enabled only for the Asynchronous Client role. This option lets you specify the proxy service that receives callbacks. When you select a callback proxy, if no WS-Addressing is provided by the request or the proxy service pipeline, Oracle Service Bus automatically populates the ReplyTo property in the SOAP header. You must select a WSDL proxy service that uses the SB transport (for RMI), and the callback proxy service must understand WS-Addressing. WS-Addressing properties that are sent in the request or set in the proxy service pipeline are used instead of the callback proxy you set in this option. If you do not specify a Callback Proxy, and the request does not contain ReplyTo properties, you must provide ReplyTo properties in the SOAP header through the proxy service pipeline. |
|
Fault Proxy |
This option is not currently supported. You must configure your callback services to handle faults in an asynchronous pattern. |
|
WS-Addressing Version |
Required. Enabled only for the Asynchronous Client role. Specify the default WS-Addressing version to use when no WS-Addressing is provided in the request or the proxy service pipeline. WS-Addressing properties that are sent in the request or set in the proxy service pipeline are used instead of the WS-Addressing version you set in this option. For WS-Addressing version mismatches between environments, perform any necessary transformations in the proxy service pipeline. For more information, see the "Transformation Examples" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
|
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:
|
|
Pass Caller's Subject |
Optional. Select this option to have Oracle Service Bus pass the authenticated subject from the proxy service when invoking the SOA service. The Invocation Service Account option, an alternative to Pass Caller's Subject, is disabled when you select this option. Note: Make sure that domain trust is enabled between client and target server if they are in different domains. For more information, see "Important Information Regarding Cross-Domain Security Support" in Oracle Fusion Middleware Securing Oracle WebLogic Server. |
|
Invocation Service Account |
Optional. Alternative to Pass Caller's Subject, which lets you specify custom security credentials by selecting a service account for RMI invocation. You can specify any type of service account (Pass Through, Static, Mapping). Click Browse and select a service account. If you do not specify a service account, an anonymous subject is used. |
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.
The Create/Edit a Business Service - Tuxedo Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
For more information, see "Tuxedo Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Use this page to configure transport settings for a business service using the Tuxedo transport protocol. Table 19-19 describes how to use the page.
Table 19-19 Create/Edit a Business Service - Tuxedo Transport Configuration Page
| Option | To create or edit... |
|---|---|
|
Field Table Classes |
Enter the name of the class or classes describing the |
|
View Classes |
Enter the name of the class or classes describing the |
|
Classes Jar |
Select a JAR Resource that contains a JAR file with the |
|
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 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 |
|
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. This Work Manager is used to asynchronously post a null reply in the case of a one-way invocation. For information about Work Managers, see:
|
|
Request Encoding |
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:
|
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.
The Create/Edit a Business Service - WS Transport Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
For more information, see "WS Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
Use this page to configure transport settings for a business service using the WS transport protocol. Table 19-20 describes how to use the page.
Table 19-20 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 ( |
|
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. |
|
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 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.
The Create/Edit a Business Service - SOAP Binding Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
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.
The Create/Edit a Business Service - Message Handling Configuration page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
Use this page to specify how Oracle Service Bus handles message content. Table 19-21 describes the message handling options for business services. Different options are available for different transport types.
Table 19-21 Create/Edit a Business Service - Message Handling Configuration Page
| Option | To create or edit... |
|---|---|
|
XOP/MTOM Support |
This feature lets you 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. Oracle Service Bus supports XOP/MTOM using the following transports:
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:
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. This feature lets you 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. 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). |
|
Result Caching |
If you invoke business services whose results seldom change, result caching improves business service performance by returning cached results to the client instead of invoking an external service directly. To use result caching for business services, you must first enable it globally, as described in Section 27.2.11, "Enabling Result Caching Globally." Configure result caching in the Advanced Settings section using the following guidelines:
|
|
Result Caching (continued) |
For a more detailed description of result caching, see "Improving Performance by Caching Business Service Results" in the Oracle Fusion Middleware Administrator's Guide for Oracle Service Bus. |
After you finish
Click Next to review and save this configuration on the Create/Edit a Business Service-Summary page.
The Create/Edit a Business Service - Summary page is one in a series of pages for creating and editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5, "Editing Business Service Configurations."
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:
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 Section 29.2, "Exporting Resources."
Before you begin
You can only export a WSDL when you are outside a session. See Section 3.1, "Using the Change Center."
To export a WSDL
Do either of the following:
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.
To locate business services:
Do either of the following:
Select Project Explorer to display the Projects View page or the Project/Folder View page. Then navigate through projects and folders to find the business service.
Select Resource Browser > Business Services. The Summary of Business Services page displays the information shown in Table 19-22. For a more detailed description of the properties, see Section 19.5, "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.
Table 19-22 Summary of Business Services Page
| Property | Description |
|---|---|
|
Name |
A unique name for the business service. Click the name to display the View a Business Service - Configuration Details age. See Section 19.5, "Editing Business Service Configurations." |
|
Path |
The path is the project name and the name of the folder in which the business service resides, for example, Click the path of a business service to display the Project/Folder View page that contains it. |
|
Actions |
Do any of the following:
|
|
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 Section 19.6, "Deleting Business Services." |
To edit a business service configuration:
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "Using the Change Center."
You don't have to enter a session if you only want to view details.
Locate the business service you want to view or edit, as explained in Section 19.4, "Locating Business Services."
Click the business service name. The View a Business Service - Configuration Details page displays configuration information for the selected business service.
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.
For a list of all those pages, see Section 19.5.1, "View a Business Service - Configuration Details Page."
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.
Continue to view or edit, as described in Section 19.1, "Creating and Configuring Business Services."
On the Create/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.
The View Business Service - Configuration Details page displays the configuration details of a business service. Table 19-23 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 Section 19.2, "Create/Edit a Business Service - Page Reference."
Click the Edit link next to any category name to display the associated configuration page.
Table 19-23 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 Section 4.23, "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 Section 4.22, "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 Section 4.22, "Viewing References to Resources." |
|
Description |
A description of this business service, if one exists. |
|
General Configuration |
Shows properties configured on the General Configuration page. |
|
Message Type Configuration |
Shows properties configured on the Section 19.2.2, "Message Type Configuration Page." |
|
Transport Configuration |
Shows properties configured on the Section 19.2.3, "Transport Configuration Page." |
|
BPEL-10g Transport Configuration |
Shows properties configured on the Section 19.2.5, "BPEL-10g Transport Configuration Page." |
|
DSP Transport Configuration |
Shows properties configured on the Section 19.2.6, "DSP Transport Configuration Page." |
|
EJB Transport Configuration |
Shows properties configured on the Section 19.2.7, "EJB Transport Configuration Page." |
|
E-Mail Transport Configuration |
Shows properties configured on the Section 19.2.8, "E-Mail Transport Configuration Page." |
|
File Transport Configuration |
Shows properties configured on the Section 19.2.9, "File Transport Configuration Page." |
|
Flow Transport Configuration |
Shows properties configured on the Section 19.2.10, "Flow Transport Configuration Page." |
|
FTP Transport Configuration |
Shows properties configured on the Section 19.2.11, "FTP Transport Configuration Page" |
|
HTTP Transport Configuration |
Shows properties configured on the Section 19.2.12, "HTTP Transport Configuration Page." |
|
JCA Transport Configuration |
Shows properties configured on the Section 19.2.13, "JCA Transport Configuration Page." |
|
JEJB Transport Configuration |
Shows properties configured on the Section 19.2.14, "JEJB Transport Configuration Page." |
|
JMS Transport Configuration |
Shows properties configured on the Section 19.2.15, "JMS Transport Configuration Page." |
|
MQ Transport Configuration |
Shows properties configured on the Section 19.2.16, "MQ Transport Configuration Page." |
|
SB Transport Configuration |
Shows properties configured on the Section 19.2.17, "SB Transport Configuration Page." |
|
SFTP Transport Configuration |
Shows properties configured on the Section 19.2.18, "SFTP Transport Configuration Page." |
|
SOA-DIRECT Transport Configuration |
Shows properties configured on the Section 19.2.19, "SOA-DIRECT Transport Configuration Page." |
|
Tuxedo Transport Configuration |
Shows properties configured on the Section 19.2.20, "Tuxedo Transport Configuration Page." |
|
WS Transport Configuration |
Shows properties configured on the Section 19.2.21, "WS Transport Configuration Page." |
|
Message Handling Configuration |
Shows properties configured on the Section 19.2.23, "Message Handling Configuration Page." |
The View a Business Service - Policies Configuration page is one in a series of pages for editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5.1, "View a Business Service - Configuration Details Page."
Use this page to configure policy settings for WSDL-based and Any SOAP business services. Table 19-24 describes how to use the page.
Note that for WSDL-based services, WLS 9.2 policies bound to the service are exposed (inlined) in the effective WSDL. Abstract policies are pre-processed before they are inlined. OWSM policies are bound by reference, not inlined in the effective WSDL.
Table 19-24 View a Business Service - Policies Page
| Option | To edit... |
|---|---|
|
Service Policy Configuration |
Following are the options in the Service Policy Configuration field: OWSM Policies
WLS 9 Policies
Note: The policy binding models are mutually exclusive. You must use only one type of policy in a service. If you bind policies directly to the service, all WSDL-based policies are ignored. After adding policies, you can provide overrides on the Security page. |
After you finish
Click Update to save this configuration; or click Reset to undo your changes.
The View a Business Service - Security Configuration page is one in a series of pages for editing business services, as described in Section 19.1, "Creating and Configuring Business Services" and Section 19.5.1, "View a Business Service - Configuration Details Page."
The fields available on this page depend on the use of policies in the business service. For example, if the service uses OWSM policies (recommended), Policy Overrides appear on the Security page. For more information, see "Securing Oracle Service Bus with Oracle Web Services Manager" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus.
WLS 9.2 policies bound to the service are exposed (inlined) in the effective WSDL. Abstract policies are pre-processed before they are inlined. OWSM policies are bound by reference, not inlined in the effective WSDL.
Use this page to configure security settings for a business service that has a WSDL-based policy or that uses pre-defined policy bindings. Table 19-25 describes how to use the page.
Table 19-25 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. Note: This option is not available for services that use Oracle Web Services Manager Policies, because user credentials are provided by override keys. For more information: |
|
Policy Overrides |
For OWSM policies, provide any desired overrides that are allowed. For more information, see Table 19-24 and "Securing Oracle Service Bus with Oracle Web Services Manager" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus. |
After you finish
Click Update to save this configuration; or click Reset to undo your changes.
To delete a business service:
If you have not already done so, click Create to create a new session or click Edit to enter an existing session. See Section 3.1, "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.