Oracle® Fusion Middleware Developer's Guide for Oracle Service Bus 11g Release 1 (11.1.1.5.0) Part Number E15866-03 |
|
|
View PDF |
When you configure a business service or a proxy service, you must configure the transport used by the service. Each transport is configured on its own configuration page.
Each transport available for business services and proxy services has its own configuration page. Oracle Service Bus provides the following transports:
Section 3.1.1, "BPEL-10g Transport Configuration Page (Business Services)"
Section 3.1.2, "DSP Transport Configuration Page (Business Services)"
Section 3.1.3, "EJB Transport Configuration Page (Business Services)"
Section 3.1.4, "E-Mail Transport Configuration Page (Business Services)"
Section 3.1.5, "E-Mail Transport Configuration Page (Proxy Services)"
Section 3.1.6, "File Transport Configuration Page (Business Services)"
Section 3.1.7, "File Transport Configuration Page (Proxy Services)"
Section 3.1.8, "FTP Transport Configuration Page (Business Services)"
Section 3.1.9, "FTP Transport Configuration Page (Proxy Services)"
Section 3.1.10, "HTTP Transport Configuration Page (Business Services)"
Section 3.1.11, "HTTP Transport Configuration Page (Proxy Services)"
Section 3.1.12, "JCA Transport Configuration Page (Proxy and Business Services)"
Section 3.1.13, "JEJB Transport Configuration Page (Business Services)"
Section 3.1.14, "JEJB Transport Configuration Page (Proxy Services)"
Section 3.1.15, "JMS Transport Configuration Page (Business Services)"
Section 3.1.16, "JMS Transport Configuration Page (Proxy Services)"
Section 3.1.17, "MQ Transport Configuration Page (Business Services)"
Section 3.1.18, "MQ Transport Configuration Page (Proxy Services)"
Section 3.1.19, "SB Transport Configuration Page (Business Services)"
Section 3.1.20, "SB Transport Configuration Page (Proxy Services)"
Section 3.1.21, "SFTP Transport Configuration Page (Business Services)"
Section 3.1.22, "SFTP Transport Configuration Page (Proxy Services)"
Section 3.1.23, "SOA-DIRECT Transport Configuration Page (Business Services)"
Section 3.1.24, "Tuxedo Transport Configuration Page (Business Services)"
Section 3.1.25, "Tuxedo Transport Configuration Page (Proxy Services)"
Section 3.1.26, "WS Transport Configuration Page (Business Services)"
Section 3.1.27, "WS Transport Configuration Page (Proxy Services)"
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" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1147
.
Table 3-1 BPEL-10g Transport Configuration Options for Business Services
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:
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. |
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:
|
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 information about Work Managers, see:
|
Note:
The DSP transport is being deprecated and will be removed from future releases.Use this page to configure transport settings for a business service using the DSP (Oracle Data Service Integrator) transport protocol. For more information on accessing Oracle Data Service Integrator from Oracle Service Bus, see "DSP and Oracle Data Service Integrator Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1229
.
Table 3-2 DSP Transport Configuration Options for Business Services
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. |
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. The Work Manager is used to post the reply message for response processing. For information about Work Managers, see:
|
Use this page to configure transport settings for a business service using the EJB transport protocol.
For more information on the EJB transport, see "EJB Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1009
.
Table 3-3 EJB Transport Configuration Options for Business Services
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. |
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. |
Converter Jar |
Click Browse and select an EJB converter class JAR resource from the list displayed. |
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 that you want to invoke. |
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 at |
Use this page to configure transport settings for a business service using the e-mail transport protocol.
Table 3-4 E-Mail Transport Configuration Options for Business Services
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 4-6, those server resources are used instead of this SMTP Server setting. Do not select an SMTP server if you use the Mail Session option. You must first create the SMTP Server resource. For more information, see Section 2.1.17, "Creating SMTP Server Resources." |
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 4-6, 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 |
Use this page to configure transport settings for a proxy service using the e-mail transport protocol.
Table 3-5 E-Mail Transport Configuration Options for Proxy Services
Option | To create or edit... |
---|---|
Service Account |
Enter a service account name, or click Browse to select service accounts from a browser. |
Managed Server |
Select the Managed Server for polling in a clustered domain. This field is available only in a clustered domain. |
Polling Interval |
Enter a polling interval, in seconds. |
E-Mail Protocol |
Select POP3 or IMAP as the server type for the e-mail account. |
Read Limit |
Specify the maximum number of messages to read per polling sweep. Enter 0 to specify no limit. |
Pass By Reference |
Select this check box to stage the file in the archive directory and pass it as a reference in the headers. By default when you create a new service, the Pass By Reference option is selected and you must specify the archive directory location. |
Pass Attachments by Reference |
Select this check box to stage the attachments in the archive directory and pass them as a reference in the headers. By default, when the Pass By Reference option is selected, the Pass Attachments By Reference option is implicitly true and you must specify the archive directory location. |
Post Read Action |
Select what happens to a message after it has been read:
|
Attachments |
Select how attachments are handled:
|
IMAP Move Folder |
Enter the folder to which the message is moved if the Post Read Action field is set to Move. |
Download Directory |
Enter a temporary location for downloading e-mails. |
Archive Directory |
Specify the path to the archive location if the Post Read Action field is set to Archive. This field is required if the Pass By Reference or Pass Attachments By Reference option is selected. |
Error Directory |
Enter the file system directory path to write the message and any attachments if there is a problem. |
Request Encoding |
Accept the default |
Use this page to configure transport settings for a business service using the file transport protocol.
Table 3-6 File Transport Configuration Options for Business Services
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 |
Use this page to configure transport settings for a proxy service using the file transport protocol.
Table 3-7 File Transport Configuration Options for Proxy Services
Option | To create or edit... |
---|---|
File Mask |
Specify the files that the proxy service should poll. If the URI is a directory and you specify |
Managed Server |
Select the Managed Server for polling in a clustered domain. This field is available only in a clustered domain. |
Polling Interval |
Enter a polling interval, in seconds. The default is 60. |
Read Limit |
Specify the maximum number of messages to read per polling sweep. Enter |
Sort By Arrival |
Select this check box to specify that events are delivered in the order of arrival. Note that when this option is selected for a proxy service that is executed in a clustered environment, messages are always sent to the same server. In other words, load balancing across servers is ignored when this option is selected. |
Scan Subdirectories |
Select this check box to recursively scan all the directories. |
Pass By Reference |
Select this check box to stage the file in the archive directory and pass it as a reference in the headers. |
Post Read Action |
Select what happens to a message after it has been read:
|
Stage Directory |
Enter an intermediate directory to temporarily stage the files while processing them. Do not put the stage directory inside of the polling directory (the directory identified in the URL of the file transport proxy service; for example, file:///c:/dir1/dir2). |
Archive Directory |
Specify the path to the archive location if the Post Read Action option is set to Archive. The Archive Directory field is also a required field if you have selected the Pass By Reference field. Do not put the archive directory inside of the polling directory. |
Error Directory |
Enter the location where messages and attachments are posted if there is a problem. Do not put the error directory inside of the polling directory. |
Request Encoding |
Accept the default |
Use this page to configure transport settings for a business service using the ftp transport protocol.
Table 3-8 FTP Transport Configuration Options for Business Services
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. |
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 |
Use this page to configure transport settings for a proxy service using the ftp transport protocol.
Table 3-9 FTP Transport Configuration Options for Proxy Services
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 user. This is a required field when the User Authentication option is set to external user. |
Pass By Reference |
Select this check box to stage the file in the archive directory and pass it as a reference in the headers. |
Remote Streaming |
Select this check box to stream the FTP files directly from the remote server at the time of processing. When you select this option, the archive directory is the remote directory on the remote FTP server machine. Therefore, you should specify the archive directory as relative to the FTP user directory. |
File Mask |
Enter the regular expression for the files to be picked. The default is |
Managed Server |
Select the Managed Server for polling in a clustered domain. This field is available only in a clustered domain. |
Polling Interval |
Enter a polling interval, in seconds. The default is 60. |
Read Limit |
Specify the maximum number of messages to read per polling sweep. Enter |
Post Read Action |
Select what happens to a message after it has been read.
|
Transfer Mode |
Select ASCII or binary as the transfer mode. |
Archive Directory |
Specify the path to the archive location if the Post Read Action option is set to Archive. This field is required if the Pass By Reference option is selected. Note: The Archive, Download, and Error directories are absolute paths, and they are automatically created. If you specify a relative path, the files are created relative to the Java process that starts the Oracle WebLogic Server. |
Download Directory |
Enter the directory on your local machine where files are downloaded during the file transfer. Note: The Archive, Download, and Error directories are absolute paths, and they are automatically created. If you specify a relative path, the files are created relative to the Java process that starts the Oracle WebLogic Server. |
Error Directory |
Enter the location where messages are posted if there is a problem. Note: The Archive, Download, and Error directories are absolute paths, and they are automatically created. If you specify a relative path, the files are created relative to the Java process that starts the Oracle WebLogic Server. |
Request Encoding |
Accept the default |
Scan Subdirectories |
Select this check box to recursively scan all directories |
Sort By Arrival |
Select this check box to deliver events in the order of arrival. |
Timeout |
Enter the socket timeout interval, in seconds, before the connection is dropped. If you enter |
Retry Count |
Specify the number of retries for FTP connection failures. |
Use this page to configure transport settings for a business service using the HTTP transport protocol. The HTTP transport supports both HTTP and HTTPS endpoints.
Table 3-10 HTTP Transport Configuration Options for Business Services
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. |
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 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 |
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. |
Use this page to configure transport settings for a proxy service using the HTTP transport protocol. The HTTP transport supports both HTTP and HTTPS endpoints.
Table 3-11 HTTP Transport Configuration Options for Proxy Services
Option | To create or edit... |
---|---|
HTTPS required |
Select this check box for inbound HTTPS endpoints. To learn more, see "Configuring Transport-Level Security" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at |
Authentication |
Select one of the following:
|
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 information about Work Managers, see:
|
Request Encoding |
|
Response Encoding |
Accept the default |
Authentication Header |
Enter the HTTP header (any except For example, |
Authentication Token Type |
Select an authentication token type. Only the active token types configured for an Identity Assertion provider are available. This field is available only if you selected the Custom Authentication check box. |
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 at http://www.oracle.com/pls/as1111/lookup?id=OSBDV910
.
Table 3-12 JCA Transport Configuration Options
Option | Description |
---|---|
JCA File |
Click Browse to select a JCA resource. The JCA resource 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 resource, the remaining transport configuration fields become available. |
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 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 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 at |
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 endpoint properties, see "Endpoint Properties in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at |
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 at 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 at |
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 at http://www.oracle.com/pls/as1111/lookup?id=TKADP
.
Use this page to configure transport settings for a business service using the JEJB transport protocol.
Table 3-13 JEJB Transport Configuration for Business Services
Option | Description |
---|---|
Dispatch Policy |
Select the instance of the 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 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 Section 4.19, "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. |
Use this page to configure transport settings for a proxy service using the JEJB transport protocol.
Table 3-14 JEJB Transport Configuration for Proxy Services
Option | Description |
---|---|
Dispatch Policy |
Select the instance of the 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 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. |
Transaction Attribute |
Select one of the following options for handling transactions:
|
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 EJB. 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 client 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. |
Use this page to configure transport settings for a business service using the JMS transport protocol. For more information, see "JMS Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1037
.
Table 3-15 JMS Transport Configuration Options for Business Services
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:
|
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 at |
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 at |
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 option 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 2.1.15, "Creating Service Account Resources." |
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 Oracle Fusion Middleware Securing Oracle WebLogic Server at This field is mutually exclusive with the Service Account option. Use one or the other for JMS/JNDI authentication. |
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. |
Use this page to configure transport settings for a proxy service using the JMS transport protocol. For more information, see "JMS Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1037
.
Table 3-16 JMS Transport Configuration Options for Proxy Services
Option | To create or edit... |
---|---|
Destination Type |
Select one of the following:
|
Is Response Required |
This option is available only when Queue is selected for the Destination Type. Select this option to specify that a response is expected after an outbound message is sent. |
Response Pattern |
This option is available only when the Is Response Required check box is selected. Select one of the following:
|
Response Message Type |
This option is available only when the Is Response Required check box is selected. Select one of the following:
This option is disabled if you select a Message Type of Java for the response. |
Client Jar |
This option is available when the service is a Messaging Service with a request 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 at |
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 the Is Response Required check box is selected. Enter the character set for encoding responses. The default is UTF-8. |
Client 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 server response before dropping the connection. This only applies if the client is another proxy service in the same domain. |
Response URI |
This option is available only when JMSCorrelationID is selected for the Response Correlation 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. |
Response Connection Factory |
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. |
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 password, used for both the request and response. The same service account is used for both JMS and JNDI purposes. For more information, see Section 2.1.15, "Creating Service Account Resources." |
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. |
Message Selector |
Enter a message selector expression. Only messages with properties matching the expression are processed |
Durable Subscription |
This option is available only if Topic is selected for the Destination Type. Select this check box if the subscription is durable or leave it blank if the subscription is not durable |
Retry Count |
Enter the number of delivery retries a message can have before it is moved to the error destination. This field only applies to Oracle WebLogic Server JMS destinations. |
Retry Interval |
Enter the amount of time, in milliseconds, before rolled back or recovered messages are redelivered. This field only applies to Oracle WebLogic Server JMS destinations. |
Error Destination |
Enter the name of the target destination for messages that have reached their redelivery limit. This field only applies to Oracle WebLogic Server JMS destinations. |
Expiration Policy |
Select an Expiration Policy to use when an expired message is encountered on a destination. This field only applies to Oracle WebLogic Server JMS destinations. |
Is XA Required |
Select this check box if your connection factory is XA. This value is into account when the remote connection factory is unavailable. If your connection factory is available and this value is true, make sure that the connection factory is defined as transactional. |
Topic Messages Distribution |
This option is available when you select Topic for the Destination Type. Topic Messages Distribution provides different options for handling inbound JMS messages and providing high availability and failover. Select one of the following properties to determine how message-driven beans handle incoming JMS messages:
Note: For topic destinations deployed on Oracle WebLogic Server prior to version 10.3.4, the only valid option is Compatibility. The "One Copy" options you select for Topic Messages Distribution override the Subscription Sharing Policy and/or Client ID Policy configured on the JMS Connection Factory. |
Target |
This option is available only in an Oracle Service Bus cluster when you select Compatibility for the Topic Messages Distribution option. Select the target server that will handle incoming JMS messages. If you select one of the "One Copy" options for Topic Messages Distribution, this field displays the name of the cluster. If you do not set a target, the JMS proxy service instance (reading messages off the Topic) on each Managed Server in the cluster gets a copy of the message. |
JNDI Timeout |
The JNDI connection timeout (in seconds) used while looking up the destination or connection factory in the JNDI tree. |
Before you use the MQ transport, you must configure a MQ Connection resource. See Section 2.6, "Working with MQ Connections." For more information about the MQ transport, see "MQ Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1117
.
Use this page to configure transport settings for a proxy service using the native MQ transport protocol.
Table 3-17 MQ Transport Configuration Options for Business Services
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 option 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 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_name 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 at |
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 |
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 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 at |
Before you use the MQ transport, you must configure a MQ Connection resource. See Section 2.6, "Working with MQ Connections." For more information about the MQ transport, see "MQ Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1117
.
Use this page to configure transport settings for a proxy service using the native MQ transport protocol.
Table 3-18 MQ Transport Configuration Options for Proxy Services
Option | To create or edit... |
---|---|
Polling Interval |
Enter a polling interval, in milliseconds. The default is |
Is Response Required |
Select this option to specify that a response is expected after an outbound message is sent. |
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. |
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: |
Response Message Type |
This option is available only when the Is Response Required check box is selected. Select one of the following:
|
Client 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 |
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 information about Work Managers, see:
|
Backout Threshold |
Enter a value representing the number of times the pipeline should retry a message before redirecting the message to the queue specified in the Dead Letter URI field. If you do not specify a value for this field, the message is redirected to the dead letter queue without attempting any retries. |
MQ Dead Letter URI |
Enter the URI of the dead letter queue to which request messages should be redirected after attempting the number of retries specified in the Backout Threshold field. If you do not specify a value for this field, the message is discarded after retrying the number of times specified in the Backout Threshold field. The Dead Letter URI uses the same format as the EndPoint URI. |
Endpoint URI 'GET' options |
Enter the MQ GET message options from among the following:
You can use either "|" or "+" to separate multiple options. For example, you can specify the following: MQC.MQGMO_ACCEPT_TRUNCATED_MSG | MQC.MQGMO_LOCK The MQ GET message options are applied when reading a message from the inbound queue. |
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 at |
Use this page to configure transport settings for a proxy service using the SB (Service Bus) transport protocol. For more information about the SB transport, see "SB Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV997
.
Table 3-19 SB Transport Configuration Options for Business Services
Option | To create or edit... |
---|---|
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 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. |
Use this page to configure transport settings for a proxy service using the SB (Service Bus) transport protocol. For more information about the SB transport, see "SB Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV997
.
Table 3-20 SB Transport Configuration Options for Proxy Services
Option | To create or edit... |
---|---|
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 information about Work Managers, see:
|
Use SSL |
When specified, requests must be sent over an SSL connection. However, unsecured connections are not forbidden. The administrator must close all unsecured protocols on the server (for example, t3 or http) to strictly enforce secured client connections. |
Use this page to configure transport settings for a proxy service using the sftp transport protocol. For more information about the SFTP transport, see "SFTP Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV975
.
Table 3-21 SFTP Transport Configuration Options for Business Services
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 |
Use this page to configure transport settings for a proxy service using the sftp transport protocol. For more information about the SFTP transport, see "SFTP Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV975
.
Table 3-22 SFTP Transport Configuration Options for Proxy Services
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. |
Pass By Reference |
Select this check box to stage the file in the archive directory and pass it as a reference in the headers. |
Remote Streaming |
Select this check box to stream the SFTP files directly from the remote server at the time of processing. When you select this option, the archive directory is the remote directory on the remote SFTP server machine. Therefore, you should specify the archive directory as relative to the SFTP user directory. |
File Mask |
Enter the regular expression for the files to be picked. The default is |
Managed Server |
This field is available only in a clustered domain. Select the Managed Server to act as the polling server. All of the Managed Servers can process the message, but only one can poll for the message. |
Polling Interval |
Enter the interval in seconds at which the file is polled from the specified location. The default is 60. |
Read Limit |
Specify the maximum number of messages to read per polling sweep. Enter |
Post Read Action |
Select what happens to a message after it has been read.
|
Archive Directory |
Specify the path to the archive location if the Post Read Action option is set to Archive. This field is required if the Pass By Reference option is selected. Note: The Archive, Download, and Error directories are absolute paths, and they are automatically created. If you specify a relative path, the files are created relative to the Java process that starts the Oracle WebLogic Server. |
Download Directory |
Enter the directory on your local machine where files are downloaded during the file transfer. Note: The Archive, Download, and Error directories are absolute paths, and they are automatically created. If you specify a relative path, the files are created relative to the Java process that starts the Oracle WebLogic Server. |
Error Directory |
Enter the location where messages are posted if there is a problem. Note: The Archive, Download, and Error directories are absolute paths, and they are automatically created. If you specify a relative path, the files are created relative to the Java process that starts the Oracle WebLogic Server. |
Request Encoding |
Accept the default |
Scan Subdirectories |
Select this check box to recursively scan all directories |
Sort By Arrival |
Select this check box to deliver events in the order of arrival. |
Timeout |
Enter the socket timeout interval, in seconds, before the connection is dropped. If you enter |
Retry Count |
Specify the number of retries for SFTP connection failures. |
Table 3-23 describes the transport-specific configuration options for the SOA-DIRECT transport.
Table 3-23 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:
There is no load balancing or failover for Callback services. |
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. |
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 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 at |
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. |
Use this page to configure transport settings for a proxy service using the Tuxedo transport protocol. For more information about the Tuxedo transport, see "Tuxedo Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1200
.
Table 3-24 Tuxedo Transport Configuration Options for Business Services
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 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. 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:
|
Use this page to configure transport settings for a proxy service using the Tuxedo transport protocol. For more information about the Tuxedo transport, see "Tuxedo Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1200
.
Table 3-25 Tuxedo Transport Configuration Options for Proxy Services
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
If an incoming request contains a |
Classes Jar |
Select a JAR resource that contains a JAR file with the |
Local Access Point |
Select a local access point from the list that is associated with the export. The list contains local access points configured in WTC. A proxy service cannot be created if there is not an associated local access point. If no local access points exist or to create a new one, select New. Enter the corresponding Local Access Point Name and Local 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. You can enter an existing access point name after selecting the New option. This causes the existing information to be updated with the new parameters. You can change only the host name and port number. |
Remote Access Point |
This field appears only when you select New in the Local Access Point field. From the list, select a remote access point to be associated with the newly created local access point. If none exist or to create a new one, select New. Enter the corresponding Access Point Name and Network Address in the adjacent fields. You can enter an existing access point name after selecting the New option. This causes the existing information to be updated with the new parameters. You can change only the host name and port number. The remote access point will also be the authentication principal for the WTC connection for inbound requests. Optionally, you can create a user with the same access point ID in the default security realm to allow incoming calls. To do so, select Yes from the Create User? list. The password will be randomly generated using a temporary variable to avoid security issues. |
Reply Buffer Type |
This option is available only if the Response Required? field is selected. Select the type of buffer that the remote Tuxedo client will receive. |
Reply Buffer Subtype |
This option is available only when the Response Required? option is selected and the Reply Buffer Type value is VIEW or VIEW32. Enter the buffer subtype with which to associate the reply buffer. |
Response Required? |
Select this check box if this service is expected to send a response. The default status is that this option is selected. This option is cleared and the unavailable if the service type is Messaging Service and the response message type is None. |
Request Encoding |
Specify a character set encoding for requests in Tuxedo transports. |
Response Encoding |
Specify a character set encoding for responses in Tuxedo transports. |
Transformation Style |
Select one of the following:
|
Use this page to configure transport settings for a proxy service using the WS transport protocol. For more information about the WS transport, see "WS Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1083
.
Table 3-26 WS Transport Configuration Options for Business Services
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 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. |
Use this page to configure transport settings for a proxy service using the WS transport protocol. For more information about the WS transport, see "WS Transport" in the Oracle Fusion Middleware Developer's Guide for Oracle Service Bus at http://www.oracle.com/pls/as1111/lookup?id=OSBDV1083
.
Table 3-27 WS Transport Configuration Options for Proxy Services
Option | To create or edit... |
---|---|
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 information about Work Managers, see:
|
Retry Count |
The number of times to retry delivery of a message to the pipeline. If an unhandled exception occurs in the request pipeline of a proxy service, the incoming WS transport message will be redelivered to the pipeline up to the number of times specified by the retry count. This value is important for reliably processing WS transport messages. |
Retry Delay |
The number of seconds the system pauses before retrying to send a message to the pipeline after an error. |