|
|
This section describes all the views, dialogs, wizards, and other user interface objects in the Oracle Service Bus plug-ins.
The following pages are provided for managing alerts:
An alert destination is a destination address for alert notifications in Oracle Service Bus. Use this page to configure an alert destination resource. For more information, see Alert Destinations in Using the Oracle Service Bus Console.
Continue in the Edit Alert Destination page. Click Add to add e-mail and JMS recipients to an alert destination. See:
For more information, see Adding E-Mail and JMS Recipients in Using the Oracle Service Bus Console.
Use this page to configure the destination target for an alert sent via e-mail (that is, using the e-mail transport). For more information, see Adding E-Mail Recipients in Using the Oracle Service Bus Console.
Use this page to configure the destination target for an alert sent via JMS (that is, using the JMS transport). For more information, see Adding JMS Recipients in Using the Oracle Service Bus Console.
You configure new business services while creating them in the New Business Service wizard. You can view and modify those settings in the Business Service editor: With a few exceptions, configuration options are identical in the wizard and the editor and are therefore documented in one place. The wizard and editor business service configuration pages are:
Use the Business Service General Configuration page to specify general configuration settings for a business service. This page appears both in the New Business Service wizard and in the Business Service editor. Options vary, depending on whether you are using the wizard or the editor, as described below.
The following table describes the options in the wizard:
The following table describes the options in the editor:
Use the Business Service Message Type Configuration page to configure message types for a business service whose type is Messaging Service. This page appears both in the New Business Service wizard and in the Business Service editor:
The binding definition for messaging services consists of configuring the content-types of the messages that are exchanged. The content-type for the response does not need to be the same as for the request; therefore, the response is configured separately (for example, the service could accept an MFL message and return an XML acknowledgment receipt).
| Note: | E-mail, File, FTP, or SFTP transport business services whose type is Messaging Service support one-way messaging only; the Response Message Type should be None. If you select an option other than None, the file, ftp, or sftp protocol will not be available on the Transport Configuration page. |
Use the Business Service - Service Policy Configuration page to configure service policy settings for a proxy service. This page appears both in the New Business Service wizard and in the Business Service editor.
Select this option to add service-level policies, operation-level policies (in which case the policy applies to both the request and response messages), request policies, and response policies directly.
For more information about configuring service policies, see
Configuring Message Level Security for Web Services in the Oracle Service Bus Security Guide.
|
Use Business Service SOAP Binding Configuration page to configure the SOAP Binding for a business service based on a WSDL. This page appears both in the New Business Service wizard and in the Business Service editor:
Select or deselect 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.
Use the Business Service Transport Configuration page to select, review, or change the service’s transport protocol and to set, review, or change general transport configuration settings. This page appears both in the New Business Service wizard and in the Business Service editor:
Outbound transport-level security applies to the connections between Oracle Service Bus proxy services and business services. For more information about transport-level security, see Configuring Transport-Level Security in the Oracle Service Bus Security Guide.
Select a transport protocol from the list. The protocols available differ, depending on the service type:
|
|||||
For every new message, there is a new order of URLs. |
|||||
Enter an endpoint URL in the format based on the transport protocol you selected in the Protocol field, above: The formats are:
Optional URI elements are shown in square brackets. For more information, see the Oracle BPEL Process Manager User Guide.
In the URI,
If the JNDI provider is located on the same server, the JNDI provider need not be specified. The URI then would be
The HTTP transport supports both
To target a JMS destination to multiple servers, use the following URI format: In a cluster: The host names in the JMS URI must exactly match the host names of the cluster servers as they are configured in WebLogic Server.
|
|||||
To make the MQ transport available in Oracle Service Bus, see the MQ Transport User Guide.
In the URI, If more than one URI is specified, you must have unique resource names for the endpoints. If no remote name is specified, its value is the value of the resource name. If no remote name is entered or if remote and resource name are the same, only one URI is allowed. In this case resource name and remote name have the same value. This allows already defined WTC Imports to make use of WTC load-balancing and failover. For more information, see Oracle Service Bus Interoperability Solution for Tuxedo.
Click Add to add one or more additional URIs. At run time, the URLs are selected based on the load balancing algorithm you selected in the Load Balancing Algorithm field.
If you selected Random-weighted in the Load Balancing Algorithm field, you can also enter a weight in the Endpoint URI field. The default is
1.
|
|||||
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.
|
|||||
Use the Business Service Message Content Handling Configuration page to specify how Oracle Service Bus is to encode outbound messages sent by business services and whether Oracle Service Bus should stream attachments in outbound response messages instead of buffering the attachment contents in memory.
Using this page, you can enable the business service to encode outbound messages in MTOM/XOP format. SOAP Message Transmission Optimization Mechanism (MTOM) is a method of sending binary data to and from Web services. MTOM uses XML-binary Optimized Packaging (XOP) to transfer the binary data.
Using this page, you can also enable the business service to store attachments in outbound response messages to a disk file and then process the data in a streaming fashion without buffering the attachment contents in memory. This enables the business service to process large attachments robustly and efficiently.
You configure new proxy services while creating them in the New Proxy Service wizard. You can view and modify those settings in the Proxy Service editor: With a few exceptions, configuration options are identical in the wizard and the editor and are therefore documented in one place. The wizard and editor business service configuration pages are:
Use the Proxy Service General Configuration page to set or modify general configuration properties for a proxy service. This page appears both in the New Proxy Service wizard and in the Proxy Service editor: Options vary, depending on whether you are using the wizard or the editor, as described below.
The following table describes the options in the wizard:
The following table describes the options in the editor:
This option shows the service type of the proxy service. You can change only some of the properties of some of the service types:
|
Use the Proxy Service Message Level Security Configuration page to configure message-level security for the proxy service. This page appears both in the New Proxy Service wizard and in the Proxy Service editor:
Message-level custom tokens and message-level user name and password are supported on proxy services of the following binding types:
The configuration for both custom user name/password and custom token is similar. In both cases, you specify XPath expressions that enable Oracle Service Bus to locate the necessary information. The root of these XPath expressions is as follows:
All XPath expressions must be in a valid XPath 2.0 format. The XPath expressions must use the XPath "declare namespace" syntax to declare any namespaces used, as follows:
declare namespace
ns='http://webservices.mycompany.com/MyExampleService';)
|
You can enter the path (
project/folder) and name of a service key provider, or click Browse to select one.
|
|
Enter the type for the custom token type. Only the active token types configured for a WebLogic Server Identity Assertion provider can be used.
See
Configuring Identity Assertion Providers for Custom Tokens for more information.
|
|
An XPath expression that specifies a path to the custom token. Oracle Service Bus evaluates the Token XPath expression against the message headers or payload, as appropriate, to obtain the token for custom authentication.
To create or edit an expression, click <XPath> (or the expression_fragment, if one is already defined) to display the XPath Expression Editor.
|
|
Optionally, specify one or more context properties to pass additional context information to the Authentication (Custom User Name and Password) or Identity Assertion (Custom Token) security provider.
Context Properties provide a way (the
ContextHandler interface) to pass additional information to the WebLogic Security Framework so that a security provider can obtain contextual information. See
Additional Context Properties for Message Level Authentication for more information.
Enter the Property Name as a literal string, and the Value Selector as a valid XPath expression. (XPath expressions can also be literal strings.)
The XPath expressions are evaluated against the same message-part that is used for the custom token or custom user name/password. That is, the Value Selector XPath expressions for SOAP-based proxy services evaluate against the header and against the payload for non-SOAP-based proxy services.
The XPath expression is evaluated at runtime to produce the property's value. A ContextHandler is essentially a name/value list and, as such, it requires that a security provider know what names to look for. Therefore, the XPath expressions are evaluated only if a security provider asks for the value of one of these user-defined properties.
|
Use Proxy Service Message Type Configuration page to configure message types for a proxy service whose type is Messaging Service. This page appears both in the New Proxy Service wizard and in the Proxy Service editor:
The binding definition for messaging services consists of configuring the content-types of the messages that are exchanged. The content-type for the response does not have 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 proxy services whose type is Messaging Service support one-way messaging only; the Response Message Type should be None. If you select an option other than None, the E-mail, File, FTP, or SFTP protocols will not be available on the Transport Configuration page. |
You can configure only one MFL file. Note: To support multiple MFL files, define the content as binary or text and use the MFL action in the message flow to convert to XML. Optionally provide some type information by declaring (in the element or type field) the XML schema type of the XML document exchanged. |
|
You can configure only one MFL file. Note: To support multiple MFL files, define the content as binary or text and use the MFL action in the message flow to convert to XML. Optionally provide some type information by declaring (in the element or type field) the XML schema type of the XML document exchanged. |
Use Proxy Service Operation Selection Configuration page to enforce WS-I compliance (for SOAP 1.1 services only) and select the selection algorithm to use to determine the operation called by this proxy service. This option is only available for SOAP or XML services defined from a WSDL.
The WSDL specification defines a default algorithm to compute which operation is called based on the type of the SOAP message received. However, there are cases (for example, performance issues, signature/encryption issues, or the default algorithm is not applicable) when you may need to select the operation based on other means.
Oracle Service Bus provides additional algorithms. Each of them follows the same pattern and are based on the evaluation of an expression to get a value that is then used to lookup the corresponding operation in a static table.
Oracle Service Bus is generally very forgiving if an inbound message is either missing data such that the operation cannot be determined, or has data that does not correspond to a valid operation. Both of these conditions result in $operation being empty. Rather than reject all such messages, Oracle Service Bus does not initialize the operation variable in the context but otherwise continues to process the message.
However, security requirements are enforced if the proxy service is WSDL-based and at least one of the following conditions is true:
If these conditions are met, then there is a runtime check to make sure the operation selection algorithm returns a valid operation name. If the operation selection returns null or an operation that is not in the WSDL, then the message is rejected and an error is raised.
Select or deselect this check box 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.
For proxies, checks are performed against request messages received by the proxy. For invoked services (i.e. services invoked by a proxy via service callout action or route node), checks are performed against the response messages received from those services. Note that it is the WS-I compliance property of the invoked service and not the proxy that determines whether or not checks are performed against messages received from the invoked service. If you specify WS-I compliance testing for an invoked service, the message flow generates a fault for response errors.
|
|
If the proxy service is configured for a Web Service security pass-through scenario with an encrypted body, you cannot select this algorithm. A similar caveat applies to pass-through encrypted SOAP headers. If you have a WSDL that has two operations with the same input message, do not select this algorithm for operations, because the operation cannot be uniquely identified by inspecting the input message. |
|
Use the Proxy Service Message Content Handling Configuration page to specify whether the proxy service should stream message content, how the service is to decode request messages received and encode response messages sent, and whether the proxy service should stream MIME attachments instead of buffering the attachment contents in memory.
Using this page, you can enable the proxy service to stream message content rather than storing it in memory. You can also enable the proxy service to decode and parse inbound messages in MTOM/XOP format and to send responses using the MTOM/XOP format, when appropriate. SOAP Message Transmission Optimization Mechanism (MTOM) is a method of sending binary data to and from Web services. MTOM uses XML-binary Optimized Packaging (XOP) to transfer the binary data.
Using this page, you can also enable the proxy service to store MIME attachment content to a disk file and then process the data in a streaming fashion without buffering the attachment contents in memory. This enables the proxy service to process large attachments robustly and efficiently.
|
For more information, see
Streaming body Content in the Oracle Service Bus User Guide.
|
|
|
Select the Enabled check box to enable the proxy service to decode and parse inbound messages in MTOM/XOP format and to send responses using the MTOM/XOP format, when appropriate. Note that this option is disabled for imported proxy 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:
Use Include Binary Data by Reference when you need direct access to binary data, for example to pass data to a Java callout or Message Format Language (MFL) transform.
|
|
|
Select the Page Attachments to Disk check box to enable the proxy service to stream MIME attachments. When enabled for HTTP proxy services, the option applies to proxy service inbound request messages.
Note that if you select 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).
|
Use Proxy Service - Service Policy Configuration page to configure service policies for a proxy service. This page appears both in the New Proxy Service wizard and in the Proxy Service editor:
This page is displayed only if the service you are creating has operations. This page appears both in the New Proxy Service wizard and in the Proxy Service editor:
Use the Proxy Service SOAP Binding Configuration page to enforce WS-I compliance (for SOAP 1.1 services only) and select the selection algorithm to use to determine the operation called by this proxy service. This option is only available for SOAP or XML services defined from a WSDL.
The WSDL specification defines a default algorithm to compute which operation is called based on the type of the SOAP message received. However, there are cases (for example, performance issues, signature/encryption issues, or the default algorithm is not applicable) when you may need to select the operation based on other means.
Oracle Service Bus provides additional algorithms. Each of them follows the same pattern and are based on the evaluation of an expression to get a value that is then used to lookup the corresponding operation in a static table.
Oracle Service Bus is generally very forgiving if an inbound message is either missing data such that the operation cannot be determined, or has data that does not correspond to a valid operation. Both of these conditions result in $operation being empty. Rather than reject all such messages, Oracle Service Bus does not initialize the operation variable in the context but otherwise continues to process the message.
However, security requirements are enforced if the proxy service is WSDL-based and at least one of the following conditions is true:
If these conditions are met, then there is a runtime check to make sure the operation selection algorithm returns a valid operation name. If the operation selection returns null or an operation that is not in the WSDL, then the message is rejected and an error is raised.
|
Select or deselect this check box if you want to specify whether or not the service is to conform to the Basic Profile defined by the Web Services Interoperability Organization.
When a service is marked WS-I compliant, checks are performed against the messages sent to and from that service. For proxies, checks are performed against request messages received by the proxy. For invoked services (i.e. services invoked by a proxy via service callout action or route node), checks are performed against the response messages received from those services. Note that it is the WS-I compliance property of the invoked service and not the proxy that determines whether or not checks are performed against messages received from the invoked service. If you specify WS-I compliance testing for an invoked service, the message flow generates a fault for response errors.
|
Use the Proxy Service Transport Configuration page to select a transport protocol for the proxy service and to set other general transport configuration settings.
This page appears both in the New Proxy Service wizard and in the Proxy Service editor:
| Note: | Inbound transport-level security applies to the client applications and Oracle Service Bus proxy services. Outbound transport-level security applies to the connections between Oracle Service Bus proxy services and business services. To learn more about transport-level security, see Configuring Transport-Level Security in the Oracle Service Bus Security Guide. |
Enter an endpoint URI in the format based on the transport protocol you selected in the Protocol field, above: The formats are:
The HTTP transport supports both To target a target a JMS destination to multiple servers, use the following URI format:
Note that when you create a proxy service, you can configure a JMS endpoint URI even if the server at that endpoint if not available. However, in the case of JMS, when you activate the session, the endpoint must be available. In a cluster: The host names in the JMS URI must exactly match the host names of the cluster servers as they are configured in WebLogic Server. This transport does not require an endpoint URI.
To make the MQ transport available in Oracle Service Bus, see the MQ Transport User Guide.
|
|||
The URI If more than one URI is specified, you must have unique resource names for the endpoints. If no remote name is specified, its value is the value of the resource name. If no remote name is entered or if remote and resource name are the same, only one URI is allowed. In this case resource name and remote name will have the same value. This allows users using already defined WTC Imports to make use of WTC load-balancing and failover. Note: If you configure two identical URIs, an error indicates that the service name already exists. |
|||
|
Select No to retrieve a defined set of headers. If you select No, enter a set of headers in the Header field, then click Add. (This step does not apply to Local transport.)
|
The following are provided for working with Oracle Service Bus configurations and projects.
This view displays a hierarchical list of all your Oracle Service Bus configurations and the projects they contain. See also New Oracle Service Bus Configuration Project wizard.
You can do the following in the Configurations view:
Use this wizard to create an Oracle Service Bus configuration project. For configuration options, see Oracle Service Bus Configuration page.
An Oracle Service Bus configuration project is a grouping of Oracle Service Bus projects and resources destined for a server, a location for system resources (SMTP, UDDI, and such), and a container for validation; for example, a resource in a project associated with one Oracle Service Bus configuration cannot refer to a resource in a project associated to another Oracle Service Bus configuration.
Use this page to create a new Oracle Service Bus configuration project (in the New Oracle Service Bus Configuration Project wizard) or to configure an existing one (in the Properties for Oracle Service Bus Configuration editor).
The preserve, session, and customization file settings are used when publishing an Oracle Service Bus configuration to the server, and used as defaults when configuring the Export wizard - Export to Server - Select Resources page.
Select this check box to discard the session if the activation fails (for example, due to conflicts). For more information, see
Activating Sessions in Using the Oracle Service Bus Console.
|
|
Specify a customization.xml file or click Browse, locate the file, then click Open. For information on customization, see
Creating Customization Files in Using the Oracle Service Bus Console.
|
|
The name of the server associated with this Oracle Service Bus configuration. This setting is automatically configured unless there is more than one server from which to choose. When multiple servers are associated with the same Oracle Service Bus configuration, use the drop-down list to select the server you want to associate with this Oracle Service Bus configuration.
|
|
Use this page to create a new Oracle Service Bus project.
Enter a unique name for the project. For more information, see
Naming Projects and Folders in Using the Oracle Service Bus Console.
|
|
Select an existing Oracle Service Bus configuration or click New to open the New Oracle Service Bus Configuration Project wizard, where you can create a new configuration.
|
You can define custom resources for use by Oracle Service Bus using the New Custom Resource wizard and the Custom Resource editor, as described in the following topics:
Use this wizard to create a new custom resource.
Use this editor to modify the configuration of a custom resource. The General page identifies the type of custom resource. The Custom page provides options for editing the configuration for that type of custom resource.
Use this page to select the type of custom resource to create. Select the type of custom resource to create from the list of available resource type.
Use this page to configure a custom MQ connection resource. For information on MQ connection resources and MQ transports, see the following:
|
The coded character set identifier (CCSID) to be used when establishing a connection. The CCSID is used mainly for internationalization support.
To learn more, see IBM’s
WebSphere MQ Fundamentals.
|
|
The Export wizard contains the following pages:
Use this page to export Oracle Service Bus resources to a configuration JAR file. For more information, see Exporting Resources in Using the Oracle Service Bus Console.
|
|||||
Use this page to select the projects or resources you want to export. Clear the check boxes next to any resources that you do not want to include in this export.
Select this check box to create and activate a session in the Oracle Service Bus console. For more information, see
Activating Sessions in Using the Oracle Service Bus Console.
|
|
Specify a customization file or click Browse, locate the file, then click Open. For information on customization, see
Creating Customization Files in Using the Oracle Service Bus Console.
|
|
Use this page to select the projects or resources you want to export.
The Import wizard has the following pages:
Use this page to select a configuration JAR to import and an import destination. For more information, see Importing Resources in Using the Oracle Service Bus Console.
Select an existing Oracle Service Bus configuration or click New to open the New Oracle Service Bus Configuration Project wizard, where you can create a new configuration.
|
|
Use this page to select the objects on which you want to operate (create, update, or delete). Resources are only scheduled for deletion when the JAR being imported is a full project JAR and there are project resources in the importing system that are not present in the imported JAR file. To prevent resources from being deleted, deselect them. For more information, see Importing Resources in Using the Oracle Service Bus Console.
Use this page to select a ZIP file with resources to import and an import destination. For more information, see Loading Resources from a Zip File in Using the Oracle Service Bus Console.
Use this page to select the objects you want to import. Clear the check boxes next to any resources that you do not want to include in this import. For more information, see Loading Resources from a Zip File in Using the Oracle Service Bus Console.
Use this page to import resources such as WSDLs or XML schemas that are available on the Web. You can import them, along with all their dependents, by specifying the URL of the root resource. For more information, see Loading Resources from a URL in Using the Oracle Service Bus Console.
Use this page to select the objects you want to import. Clear the check boxes next to any resources that you do not want to include in this import. For more information, see Loading Resources from a URL in Using the Oracle Service Bus Console.
The following are provided for working with JNDI providers:
Use this editor to modify an existing JNDI provider configuration. For descriptions of the fields, see the New JNDI Provider Resource wizard. For more information, see Editing JNDI Providers in Using the Oracle Service Bus Console.
Use this page to configure a new JNDI provider resource. For more information, see Adding JNDI Providers in Using the Oracle Service Bus Console.
Use this page to configure and edit a proxy server resource. For more information, see Adding Proxy Servers in Using the Oracle Service Bus Console.
The list of proxy server hosts. You can configure multiple proxy servers for each proxy server resource. This enables Oracle Service Bus to perform load balancing and offer fault tolerance features for the proxy server resource.
|
The Message Flow Design Palette lists all the nodes and actions you can use to construct a message flow for a proxy service. To insert a node or an action into a message flow, drag the item from the palette to the Message Flow Editor. When you drag an item to the palette, one or more targets appear (
) to indicate that you can drop the dragged item in that position on the palette. When you drag the item onto a target, the target is highlighted (
) to show that you can drop the item there.
You can also add nodes and actions to message flows by right-clicking an object in the Message Flow Editor and choosing a node or action from the Insert, Insert Into, or Insert After submenus. You can also add an error handler by selecting the Add Error Handler command. These submenus and commands are context sensitive. That is, they appear only when it is legal to add the item into the selected context in the message flow.
The Message Flow Design Palette is organized into the following categories:
The following table describes the nodes you can add to a message flow:
|
For configuration properties, see Conditional Branch Node Properties.
|
|
|
For configuration properties, see Operational Branch Node Properties.
|
|
|
For configuration properties, see Pipeline Pair Node Properties.
|
|
|
For configuration properties, see Route Node Properties.
|
|
|
For configuration properties, see Stage Node Properties.
|
|
|
For configuration properties, see Error Handler Node Properties.
|
The following table describes the communication actions you can add to a route in a message flow:
A dynamic routing action assigns a route for a message based on routing information available in an XQuery resource.
For configuration properties, see Dynamic Routing Action Properties.
|
|
A routing action identifies a target service for the message and configures how the message is routed to that service:
For configuration properties, see Routing Action Properties.
|
|
A routing table action assigns a set of routes wrapped in a switch-style condition table. Different routes are selected based upon the results of a single XQuery expression.
For configuration properties, see Routing Table Action Properties.
|
The following table describes the flow control action you can add to a route in a message flow:
An if-then action performs an action or a set of actions conditionally, based on the Boolean result of an XQuery expression.
For configuration properties, see If-Then Action Properties.
|
The following table describes the communication actions you can add to a stage in a message flow:
|
For configuration properties, see Dynamic Publish Action Properties.
|
|
|
For configuration properties, see Publish Action Properties.
|
|
A publish table action publishes a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publish.
For configuration properties, see Publish Table Action Properties.
|
|
A routing options action modifies any or all of the following properties in the outbound request: URI, Quality of Service, Mode, Retry parameters, Message Priority.
For configuration properties, see Routing Options Action Properties.
|
|
A service callout action configures a synchronous (blocking) callout to an Oracle Service Bus-registered proxy or business service.
For configuration properties, see Service Callout Action Properties.
|
|
|
For configuration properties, see Transport Headers Action Properties.
|
The following table describes the flow control actions you can add to a stage in a message flow:
|
For configuration properties, see For-Each Action Properties.
|
|
An if-then action performs an action or set of actions conditionally, based on the Boolean result of an XQuery expression.
For configuration properties, see If Action and Else-If Action Properties.
|
|
|
For configuration properties, see Raise Error Action Properties.
|
|
|
For configuration properties, see Reply Action Properties.
|
|
A skip action specifies that at run time, the execution of the current stage is skipped and the processing proceeds to the next stage in the message flow.
For configuration properties, see Skip Action Properties.
|
|
|
For configuration properties, see Resume Action Properties.
|
The following table describes the message processing actions you can add to a stage in a message flow:
|
For configuration properties, see Assign Action Properties.
|
|
|
For configuration properties, see Delete Action Properties.
|
|
An insert action inserts the result of an XQuery expression at an identified place relative to nodes selected by an XPath expression.
For configuration properties, see Insert Action Properties.
|
|
|
For configuration properties, see Java Callout Action Properties.
|
|
|
For configuration properties, see MFL Transform Action Properties.
|
|
A rename action renames elements selected by an XPath expression without modifying the contents of the element.
For configuration properties, see Rename Action Properties.
|
|
|
For configuration properties, see Replace Action Properties.
|
|
A validate action validates elements selected by an XPath expression against an XML schema element or a WSDL resource.
For configuration properties, see Validate Action Properties.
|
The following table describes the reporting actions you can add to a stage in a message flow:
|
For configuration properties, see Alert Action Properties.
|
|
|
For configuration properties, see Log Action Properties.
|
|
|
For configuration properties, see Report Action Properties.
|
Use this editor to construct a proxy service message flow. To insert a node or an action into a message flow, drag the item from the Message Flow Design Palette to the editor. When you drag an item to the editor, one or more targets appear (
) to indicate that you can drop the dragged item in that position on the palette. When you drag the item onto a target, the target is highlighted () to show that you can drop the item there.
You can also add nodes and actions to message flows by right-clicking an object in the Message Flow Editor and choosing a node or action from the Insert, Insert Into, or Insert After submenus. You can also add an error handler by selecting the Add Error Handler command. These submenus and commands are context sensitive. That is, they appear only when it is legal to add the item into the selected context in the message flow.
When you select a node or action in the editor, a configuration page for that item is displayed in the Properties view. You can add or modify configuration properties in those pages. The message flow node and action properties configuration pages are:
In a message flow, use the alert action to generate alerts based on message context in a pipeline, to send to an alert destination. Unlike SLA alerts, notifications generated by the alert action are primarily intended for business purposes, or to report errors, and not for monitoring system health. Alert destinations should be configured and chosen with this in mind. To learn more about alert destinations, see Alert Destination editor.
If pipeline alerting is not enabled for the service or at the domain level, the configured alert action is bypassed during message processing.
In the Message Flow Editor, click an alert action to display its properties in the Properties view. Use these properties pages to configure the selected alert action. The pages are:
The Alert page has the following options:
|
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
|
| Tip: | To prevent exceptions from aborting the message being processed when generating a pipeline alert, it is recommended that an error handler for the alert action be defined to handle and contain such exceptions locally, rather than having them bubble up to a global error handler. |
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use an assign action to assign the result of an XQuery expression to a context variable.
In the Message Flow Editor, click an assign action to display its properties in the Properties view. Use these properties pages to configure the selected assign action. The pages are:
The Assign page has the following options:
An expression that creates the data that is assigned to variable named in the Variable field, described below.
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a conditional branch node to specify that message processing is to proceed along exactly one of several possible paths, based on a result returned by an XPath condition.
Conditional branching is driven by a lookup table with each branch tagged with a simple, but unique, string value. A variable in the message context is designated as the lookup variable for that node, and at run time, its value is used to determine which branch to follow. If no branch matches the value of the lookup variable, the default branch is followed. You should design the proxy service in such a way that the value of the lookup variable is set before reaching the branch node.
In the Message Flow Editor, click a conditional branch node to display its properties in the Properties view. Use these properties pages to configure the selected conditional branch node. The pages are:
The Flow page has the following options:
The Conditional Branch page has the following options:
The XPath expression that defines the condition to be evaluated for determining the branch to follow.
To create or edit the XPath expression, click <XPath> (or the XPath_fragment, if one is already defined) to display the XPath Expression Editor.
|
|
A conditional branch node also always contains one or more branches, which are configured as part of the node.
Click a Branch icon in a conditional branch node to display the Branch properties page in the Properties view. Use these properties pages to configure the selected branch node in a message flow. This page has the following options.
In a message flow, use a delete action to delete a context variable or a set of nodes specified by an XPath expression.
In the Message Flow Editor, click a delete action to display its properties in the Properties view. Use these properties pages to configure the selected delete action. The pages are:
The Delete page has the following options. Select Variable to delete a variable, or select XPath to delete an XPath expression.
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a dynamic publish action to publish a message to a service specified by an XQuery expression.
In the Message Flow Editor, click a dynamic publish action to display its properties in the Properties view. Use these properties pages to configure the selected dynamic publish action. The pages are:
The Dynamic Publish page has the following options:
|
To create or edit the expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
In the editor, enter an Xquery expression or select an XQuery resource that provides a result similar to:
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a dynamic routing action to assign a route for a message based on routing information available in an XQuery resource.
This is a terminal action, which means you cannot add another action after this one. However, this action can contain request and response actions.
In the Message Flow Editor, click a dynamic routing action to display its properties in the Properties view. Use these properties pages to configure the selected dynamic routing action. The pages are:
The Dynamic Routing page has the following option:
|
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
In the XQuery/XSLT Expression editor, enter an Xquery expression, the result of which is similar to:
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
Use an error handler to specify what should happen if an error occurs in a specific location in the message flow.
All configuration for an error handler is in one or more stages contained by the error handler. See Stage Node Properties.
In a message flow, use the for-each action to iterate over a sequence of values and execute a block of actions.
In the Message Flow Editor, click a for-each action to display its properties in the Properties view. Use these properties pages to configure the selected for-each action. The pages are:
The For Each page has the following options:
An XPath expression that specifies where in the structure of the containing context variable the variable specified in the For Each Variable field is located.
To create or edit the XPath expression, click <XPath> (or the XPath_fragment, if one is already defined) to display the XPath Expression Editor.
|
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use an if-then action to perform an action or a set of actions conditionally, based on the Boolean result of an XQuery expression.
In the Message Flow Editor, click an if-then action to display its properties in the Properties view. Use this page to review and configure general properties of the if-then action. The pages are:
An if-then action always contains an if condition plus zero or more else-if condition, where you define the conditions for the if-then action. An if-then action also always contains an else condition, which defines the default path when no other condition is met.
Click an If:condition icon or an Else-If:condition icon in an if-then action to display their properties in the Properties view. Use these properties pages to configure the selected condition. This If condition properties page has the following option.
If actions and else-if actions are always contained by an if-then action. The message follows the path associated with the first if action or else-id action that returns true.
A condition in an if action or an if-else action that contains one of the tests for following alternative paths in the flow.
In the route node, you can select only the routing, dynamic routing, or routing table actions. However, these actions can contain request and response actions.
|
The else action does not have associate properties. When all if and else-if conditions return false, the message proceeds down the path associated with the else action.
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use an insert action to insert the result of an XQuery expression at an identified place relative to nodes selected by an XPath expression.
In the Message Flow Editor, click an insert action to display its properties in the Properties view. Use these properties pages to configure the selected insert action. The pages are:
The Insert page has the following options:
The XQuery expression used to create the data that will be inserted at a specified location in a named variable.
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
|
The location where the insert is performed, relative to the result of the XPath expression: Options are:
|
|
|
To create or edit the XPath expression, click <XPath> (or the XPath_fragment, if one is already defined) to display the XPath Expression Editor.
|
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a Java callout action to invoke a Java method or an EJB business service from within the message flow.
In the Message Flow Editor, click a Java callout action to display its properties in the Properties view. Use these properties pages to configure the selected Java callout action. The pages are:
The Java Callout page has the following options:
|
Click Browse to select a class and a static method from an archived resource. Once you have selected the class and method, a table appears on the Java Callout Properties page:
The Action column provides an <Expression> or
expression_fragment link to the XQuery/XSLT Expression Editor, where you can create an expression to retrieve a value for the argument.
If the type of the input value you enter does not match the declared input argument type, Oracle Service Bus tries to automatically typecast input values to the declared type of the input argument. For example a string value of
"123" will be converted to integer 123 if the declared type of the input argument is java primitive int.
|
|
An optional Service Account, which can be specified if there is a security context for this Java method.
In the case of fixed and mapped service accounts, the userid/password from the service account is authenticated in the local system and the security context propagated to the Java callout. In the case of
passthru, the security context is propagated to the Java callout. This context is the message level context if defined (with WS-Security). Otherwise, it is the transport level context.
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use the log action to construct a message to be logged and to define a set of attributes with which it will be logged.
In the Message Flow Editor, click a log action to display its properties in the Properties view. Use these properties pages to configure the selected log action. The pages are:
The Log page has the following options:
|
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
|
|
Debug - While your application is under development, you might find it useful to create and use messages that provide verbose descriptions of low-level activity within the application.
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In the Message Flow Editor, click a node or an action to display its properties in the Properties view. For most nodes and actions, one of the properties pages displayed (as a tab) is the Comment page. Use this page to add an optional comment about the item selected in the message flow.
In the Message Flow Editor, click a node or an action to display its properties in the Properties view. For most nodes and actions, one of the properties pages displayed (as a tab) is the Namespaces page. Use this page to see a list of defined namespaces or to create a new namespace.
In the Message Flow Editor, click a node or an action to display its properties in the Properties view. For many nodes and actions, one of the properties pages displayed (as a tab) is the Variables page. Use this page to see a list of all the predefined and user-defined context variables. Click Add to define a new variable.
For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a MFL (Message Format Language) transform action to convert message content from XML to non-XML, or vice versa, in the message pipeline. An MFL is a specialized XML document used to describe the layout of binary data. It is a Oracle proprietary language used to define rules to transform formatted binary data into XML data, or vice versa.
In the Message Flow Editor, click a MFL transform action to display its properties in the Properties view. Use these properties pages to configure the selected MFL transform action. The pages are:
The MFL Transform page has the following options:
|
Click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor, where you can specify the variable.
|
|
|
Click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor, where you can specify the MFL resource that will perform the action, in the format project/folder/MFLresourcename.
|
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use an operational branch node to configure branching based on operations defined in a WSDL.
When message flows define WSDL-based proxy services, operation-specific processing is required. Instead of configuring a branching node based on operations manually, Oracle Service Bus provides a branching node that automatically branches based on operations. In other words, when you create an operational branch node in a message flow, you can quickly build your branching logic based on the operations defined in the WSDL, because the Oracle Service Bus plug-ins present those operations in the operational branch node configuration page.
A branch node allows processing to proceed along exactly one of several possible paths. Branching is driven by an XPath-based switch table. Each branch in the table specifies a condition (for example, <500) that is evaluated in order down the message flow against a single XPath expression (for example, ./ns: PurchaseOrder/ns:totalCost on $body). Whichever condition is satisfied first determines which branch is followed. If no branch condition is satisfied, then the default branch is followed. A branch node may have several descendants in the message flow: one for each branch, including the default branch.
When you add an operational branch node to a message flow in the Message Flow Editor, the node contains an initial conditional branches based on the first operation defined in the WSDL, as shown below, plus a default branch:
Click the node itself (the Operational Branch Node icon or the bounding box connected to the icon) to display the Flow properties page in the Properties view. You can provide a name and a description for the node on that page.
Click an operational branch icon to display the properties for that operational branch on the Operational Branch page. That page contains a drop-down list of all the operations defined in the WSDL. You can select a different operation for that branch. You can also click the plus sign in the operational branch node, in the Message Flow Editor, to add another operation branch.
After you have added all the branches, add nodes and stages to them to define the processing for each branch.
In a message flow, use a pipeline pair node to define request and response processing.
Message flows can include zero or more pipeline pair nodes: request and response pipelines for the proxy service (or for the operations on the service), and error handler pipelines that can be defined for stages, pipelines, and proxy services. Pipelines can include one or more stages, which in turn include actions.
A pipeline pair always contains a request pipeline and a response pipeline. Add stages and actions to those pipelines, as needed.
In the Message Flow Editor, click a pipeline pair node to display its properties in the Properties view. Use this properties page to configure the selected pipeline pair node. The options are:
In a message flow, use a publish action to identify a statically specified target service for a message and to configure how the message is packaged and sent to that service.
In the Message Flow Editor, click a publish action to display its properties in the Properties view. Use these properties pages to configure the selected publish action. The pages are:
The Publish page has the following options:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a publish table action to publish a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publish. A publish table action contains one or more case actions to define conditions for following alternative paths (by default, via publish actions), as well as a default path to a default publish action. To fully define a publish table action, you must configure the publish table action, its case actions, and its publish actions (and any other actions you may add).
When you add a publish table action to a message flow in the Message Flow Editor, the publish table action contains a case action with a path to a publish action plus a default case action with a path to a default publish action, as shown below. Click add condition to add another condition to the publish table.
In the Message Flow Editor, click the publish table action itself (the Publish Table icon or the bounding box connected to the icon) to display the Publish Tables properties page in the Properties view. Use these properties pages to configure the selected publish table action. The pages are:
The Publish Table properties page has the following option:
An XQuery expression, which at run time returns the value upon which the routing decision will be made.
To create or edit an XQuery expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In the Message Flow Editor, click a case action to display its properties in the Properties view. Use this properties page to configure the selected case action, as described below:
See Publish Action Properties.
In a message flow, use the raise error action to raise an exception with a specified error code (a string) and description.
In the Message Flow Editor, click a raise error action to display its properties in the Properties view. Use these properties pages to configure the selected raise error action. The pages are:
The Raise Error page has the following options:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
If a service is transactional, a triggered Raise Error action aborts the transaction in the request (asynchronous) or in either the request or response (synchronous). For example, you may introspect messages and determine conditions under which a Raise Error action should occur even if no SOAP fault occurs, and Raise Error causes the transaction to be aborted.
In a message flow, use the rename action to rename elements selected by an XPath expression without modifying the contents of the element.
In the Message Flow Editor, click a rename action to display its properties in the Properties view. Use these properties pages to configure the selected rename action. The pages are:
The Rename page has the following options:
|
To create or edit the XPath expression, click <XPath> (or the XPath_fragment, if one is already defined) to display the XPath Expression Editor.
|
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a replace action to replace a node or the contents of a node specified by an XPath expression. The node or its contents are replaced with the value returned by an XQuery expression.
A replace action can be used to replace simple values, elements and even attributes. An XQuery expression that returns nothing is equivalent to deleting the identified nodes or making them empty, depending upon whether the action is replacing entire nodes or just node contents.
In the Message Flow Editor, click a replace action to display its properties in the Properties view. Use these properties pages to configure the selected replace action. The pages are:
The Replace page has the following options:
|
To create or edit the XPath expression, click <XPath> (or the XPath_fragment, if one is already defined) to display the XPath Expression Editor.
|
|||
The XQuery expression used to create the data that replaces the data specified by the XPath in the named variable.
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
|||
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use the reply action to specify that an immediate reply be sent to the invoker.
The reply action can be used in the request, response or error pipeline. You can configure it to result in a reply with success or failure. In the case of reply with failure where the inbound transport is HTTP, the reply action specifies that an immediate reply is sent to the invoker.
In the Message Flow Editor, click a reply action to display its properties in the Properties view. Use these properties pages to configure the selected reply action. The pages are:
The Reply page has the following options:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use the report action to enable message reporting for a proxy service.
In the Message Flow Editor, click a report action to display its properties in the Properties view. Use these properties pages to configure the selected report action. The pages are:
The Report page has the following option:
|
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
|
When you finish editing the XQuery expression, click Add a Key to add one or more key value pairs to be used to extract key identifiers from any message context variable or message payload. (The rest of the message is ignored.) The keys are a convenient way to identify a message.
|
For example, consider a report action configured on an error handler in a stage. The action reports the contents of the fault context variable in the event of an error. The report action is configured as follows:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use the resume action to resume message flow after an error is handled by an error handler. This action has no parameters and can only be used in error pipelines.
In the Message Flow Editor, click a resume action to display its properties in the Properties view. Use these properties pages to configure the selected resume action. The pages are:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use the route node to handle request and response dispatching of messages to and from business services. No other nodes can follow a route node.
In the Message Flow Editor, click a route node to display its properties in the Properties view. Use these properties pages to configure the selected route node. The pages are:
The Route page has the following option:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a routing action to identify a target service for the message and configure how the message is routed to that service.
This is a terminal action, which means you cannot add another action after this one. However, this action can contain request and response actions.
In the Message Flow Editor, click a routing action to display its properties in the Properties view. Use these properties pages to configure the selected routing action. The pages are:
The Routing page has the following option:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a routing options action to modify any or all of the following properties in the outbound request: URI, Quality of Service, Mode, Retry parameters, Message Priority.
In the Message Flow Editor, click a routing options action to display its properties in the Properties view. Use these properties pages to configure the selected routing options action. The pages are:
The Routing Options page has the following option:
|
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
|||
|
|||
|
To create or edit an expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a routing table to select different routes based upon the results of a single XQuery expression. A routing table action contains a set of routes wrapped in a switch-style condition table.
This is a terminal action, which means you cannot add another action after this one. However, this action can contain request and response actions.
When you add a routing table action to a message flow in the Message Flow Editor, the routing table action contains a case action with a path to a routing action plus a default case action with a path to a default routing action, as shown below. Click add condition to add another condition to the routing table.
In the Message Flow Editor, click the publish table action itself (the Publish Table icon or the bounding box connected to the icon) to display the Publish Tables properties page in the Properties view. Use these properties pages to configure the selected publish table action. The pages are:
The Routing Table properties page has the following option:
An XQuery expression, which at run time returns the value upon which the routing decision will be made.
To create or edit an XQuery expression, click <Expression> (or the expression_fragment, if one is already defined) to display the XQuery/XSLT Expression Editor.
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In the Message Flow Editor, click a case action to display its properties in the Properties view. Use this properties page to configure the selected case action, as described below:
See Routing Action Properties.
In the Message Flow Editor, click a service callout action to display its properties in the Properties view. Use these properties pages to configure the selected service callout action. The pages are:
The Service Callout page has the following options:
Specify how you want to configure the request and response messages by selecting one of the following options:
This option supports SOAP-RPC encoded, which is not supported when configuring payload parameters or document. |
Subsequent configuration options depend on the kind of service you selected in step 3 and on the kind of configuration options you chose for that service in step 5. Table 3-1 shows the options available for each service type.
|
||
The following table provides instructions for each of the options listed in the table above.
You must wrap the input document for the SOAP Request Header with |
|
You must provide only the core payload documents in the input variable—the SOAP package is created for you by Oracle Service Bus. In other words, do not wrap the input document with
For example, when creating a body input variable that is used for this request parameter, you would define that variable’s contents using the XPath statement |
|
For SOAP Document-type services, the variable is evaluated at runtime to form the body of the SOAP message sent to the service. For Any XML services, the variable is evaluated at runtime to form the body of the XML message sent to the service.
For SOAP Document-type services and for Any XML services, you provide only the core payload documents in the input variable—the SOAP package is created for you by Oracle Service Bus. In other words, do not wrap the input document with
For example, when creating a body input variable that is used for this request parameter, you would define that variable’s contents using the XPath statement For Messaging services, the variable is evaluated to form the body of the message, based on the type of data expected by the service. The following restrictions apply to variables used with Messaging services: |
Optionally, add one or more transport header actions. For more information about transport header actions, see Transport Headers Action Properties
| Note: | In addition to the transport headers you specify, headers are added by the Oracle Service Bus binding layer. |
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use the skip action to specify that at run time, the execution of the current stage is skipped and the processing proceeds to the next stage in the message flow. This action has no parameters and can be used in the request, response or error pipelines.
In the Message Flow Editor, click a skip action to display its properties in the Properties view. Use these properties pages to configure the selected skip action. The pages are:
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a stage node as a container for actions in a message flow. You can string multiple stages together, to compartmentalize processing logic.
In the Message Flow Editor, click a stage node to display its properties in the Properties view. Use these properties pages to configure the selected stage node. The pages are:
The Stage page has the following options:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a transport header action to set header values in messages.
In the Message Flow Editor, click a transport headers action to display its properties in the Properties view. Use these properties pages to configure the selected transport headers action. The pages are:
The Transport Header page has the following options:
|
|
|
|
Selecting this option allows you to use an XQuery or XSLT expression to set the value of the header. The expression can be simple (for example, “text/xml”) or a complex XQuery or XSLT expression. Because the Oracle Service Bus transport layer defines the XML representation of all headers as string values, the result of any expression is converted to a string before the header value is set. Expressions that return nothing result in the header value being set to the empty string. You cannot delete a header using an expression. Warning: Not all of the header settings you can specify in this action are honored at run time. Specifies that the header is removed from the request or response metadata.
Copy Header from Inbound Request (if you are setting transport headers for the Outbound Request)
Specifies that this header is copied directly from the corresponding header of the same name from the inbound message to the outbound message and vice versa. For example, if you want to set the SOAPAction header for an outbound request, selecting Copy Header from Inbound Request causes the run time to copy the value from the SOAPAction request header of If the Copy Header... option is selected for a header that does not exist in the source, this option is ignored and no action is performed on the target for this header. |
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In a message flow, use a validate action to validate elements selected by an XPath expression against an XML schema element or a WSDL resource. You can validate global elements only; Oracle Service Bus does not support validation against local elements.
In the Message Flow Editor, click a validate action to display its properties in the Properties view. Use these properties pages to configure the selected validate action. The pages are:
The Validate page has the following options:
|
To create or edit the XPath expression, click <XPath> (or the XPath_fragment, if one is already defined) to display the XPath Expression Editor.
|
|
Use the Comment page to add a comment, if desired:
Use the Namespaces page to see a list of defined namespaces or to create a new one.
Use the Variables page to see a list of defined context variables or to create a new one. For more information about context variables, see Message Context in the Oracle Service Bus User Guide.
In Oracle Service Bus, JAR resources can contain classes that depend on other classes in different JARs. Use the Modify JAR Dependencies page to add or remove referenced JAR resources. Use the Up and Down buttons to reorder the hierarchy (order of precedence) of referenced JARs. For more information, see JARs in Using the Oracle Service Bus Console.
The following editor and wizard are provided for working with SMTP servers:
Use this page to view the details of an SMTP server and edit the configuration, if required. For descriptions of the fields, see the New SMTP Server Resource wizard. For more information, see Editing SMTP Servers in Using the Oracle Service Bus Console.
Use this page to configure a new SMTP server resource. For more information, see Adding SMTP Servers in Using the Oracle Service Bus Console.
Use this page to configure a UDDI registry resource. This page is displayed in the New UDDI Registry Resource wizard and in the UDDI Configuration editor.
For more information, see UDDI in Using the Oracle Service Bus Console and UDDI in the Oracle Service Bus User Guide.
This view displays a hierarchical view, or outline, of a structured file that is currently open in the editor area. The contents of this view are editor-specific.
In Oracle Service Bus, when the proxy service is editor is open and the Message Flow Editor is selected, the Outline view displays a hierarchical view of the nodes and actions in the message flow. When the Message Flow Editor is displayed, you can switch between the hierarchical view and a thumbnail view of the service, as described in the table below:
Click this button to display a graphical thumbnail view of the contents of the Message Flow Editor. When the entire message flow does not fit in the editor, a blue mask appears in the outline view to show what portion of the flow is visible in the editor. To display a different portion of the flow, you can drag the mask to the portion of the flow you want to display in the editor.
|
The following are provided for managing resources:
Use this page to associate one or more file extensions with an Oracle Service Bus resource type.
Use this page to view resource dependencies. This view shows your current selection whether it is in the Project Explorer or the active editor.
Use this dialog to specify where to clone a project, as a new project or as a folder under a different project.
Use this dialog to select a resource, appropriate to the context, that has been created in or imported into the Oracle Service Bus plug-ins. When you click Browse from an editor or a wizard, this dialog displays the available resources that are appropriate for the context. The dialog has different names, depending on the type of resource displayed, for example, Select a WSDL, Select a MFL, Select an XML Schema, etc. In some cases, the dialog displays a hierarchical list of items contained in each resource. For example, the Select an XML Schema dialog lists elements and types defined in the schemas. The Select a WSDL dialog displays ports and bindings defined in the WSDLs.
In some cases, for example, the Select a WSDL dialog, you can click the Consume button to open the Service Consumption dialog, where you can consume services from the following resource types: Oracle Enterprise Repository, file system, UDDI, URI, workspace: consume a service residing in the current workspace.
Use this page to configure a service key provider resource. For more information, see Service Key Providers in Using the Oracle Service Bus Console.
When you associate this service key provider with a proxy service, Oracle Service Bus embeds the X.509 certificate into the proxy service’s WSDL. The proxy service then uses this certificate to encrypt the messages that it sends to its endpoint. The proxy service uses the private key in the PKI credential to decrypt the messages that the endpoint returns.
|
|
|
|
|
Web Services Policy Framework (WS-policy) is an extensible XML-based framework that extends the configuration of a Web Service with domain specific security assertions and specifies the security requirements, expectations, and capabilities of the Web Service. In Oracle Service Bus, one of the primary uses of WS-policy is configuring message-level security in proxy services and business services. For more information, see Custom WS-Policies in Using the Oracle Service Bus Console.
Use this page to select a name and location for a new WS-policy resource.
The following are provided for working with service accounts:
Use this wizard to create a new service account resource, as described in the following table.
|
For more information, see Service Accounts in Using the Oracle Service Bus Console.
Use this page to configure a service account resource, as described in the following table.
|
For more information, see Service Accounts in Using the Oracle Service Bus Console.
Use this to page to save a user name and password with the service account configuration. The service account encodes this user name and password in the outbound request. For more information, see Service Accounts in Using the Oracle Service Bus Console.
Use this to page to create a service account that maps the user name from one or more clients to user names and passwords that you specify. For more information, see Service Accounts in Using the Oracle Service Bus Console.
To map authorized clients to remote user names and passwords, in the Local User Name field, enter the name that identifies a client that has been authenticated on its inbound request.
If you have not already added this user in the Security Configuration module of the Oracle Service Bus Console, do so before you use this mapping in a runtime environment. See
Adding Users in Using the Oracle Service Bus Console. Oracle Service Bus lets you create a mapping for a non-existent local user, but the mapping will never match an authenticated user and will never be used.
|
|
The following editors help you to write expressions for use in services.
Use the XQuery/XSLT Expression editor to create variable structures, define user namespaces, use predefined message context variables to build inline XQuery expressions, build inline XQuery expressions manually, and select XQuery or XSLT resources for execution as inline XQueries.
For more information about using XQueries, see Working with Variable Structures in the Oracle Service Bus User Guide
The XQuery/XSLT Expression editor contains two panels, each containing three tabs.
Use the panel on the left to write or construct the expression. The panel contains these pages (tabs):
Use the tabs in the panel on the right to manage the variables, namespaces, and XQuery functions you can use to construct an XQuery or XSLT. The panel contains these pages (tabs):
Use the XPath Expression Editor to create an XPath expression, which is then inserted into the location from which you launched the editor.
The XPath Expression Editor contains these pages:
You can write an expression directly in the Expression text field, or you can drag variables from the Variable Structure page and drag XQuery functions from the XQuery Functions page to construct a valid XPath expression.
When you are finished constructing the expression, you can click Test to test the expression on a running server. Or click OK to insert the expression without testing it.
Use the Condition Editor to create an inline XQuery condition.
Use the panel on the left to write or construct the condition. The panel contains these tabs, each of which is described below:
Use the tabs in the panel on the right to manage the variables, namespaces, and XQuery functions you can use to construct a condition. The panel contains the following tabs. They are the same as the tabs in the right-hand panel of the XQuery/XSLT Expression Editor, and the following links display the help for those tabs in the XQuery/XSLT Expression Editor.
Use the Condition Builder page to build an inline condition. This page appears only in the Condition Editor.
Build an expression in the Condition Builder as follows:
This page appears on the XQuery/XSLT Expression Editor, the XPath Expression Editor, and the Condition Editor.
The Expression page contains a text field where you can build expressions by typing directly into the field or by dragging items from the Variable Structures page or the XQuery Functions page on the right side of the editor.
Click Test to test the expression in an Oracle Service Bus domain on a running server. WebLogic Server is packaged with Oracle Service Bus, so an installation of Oracle Service Bus includes an embedded server you can use for testing purposes.
This page appears in the XQuery/XSLT Expression Editor only.
In the message flow of a proxy service, you can assign XQuery expressions to message context variables, assign if-then-else actions based on the Boolean result of an XQuery expression, insert the result of an XQuery expression at an identified place relative to an XPath expression, specify the message context that you want to log through XQuery expressions on context variables, and so on.
Use the XQuery Resource page to configure an XQuery transformation to be executed in the message flow of a proxy service.
When you select a resource, each input parameter of the transformation is displayed. Each label corresponds to the name of a parameter, and each text box is for defining an XQuery expression to be mapped to the parameter. You must define a mapping for each parameter. Enter the expression directly, or drag variables and structures from the right panel.
|
This page appears in the XQuery/XSLT Expression Editor only.
Use the XSLT Resource tab to configure an XSLT transformation to be executed in the message flow of a proxy service.
A label and a corresponding text box is displayed for each input parameter of the transformation. Each label corresponds to the name of a parameter, and each text box is for defining an XQuery expression to be bound to the parameter. You must define a binding for each parameter. For example, if an XSL transformation has two input parameters named one and two, the Variable Name field has two labels one and two— with a text box associated with each into which the XQuery expression is entered.
Enter the expression directly, or drag variables and structures from the right panel. |
This page appears in the XQuery/XSLT Expression Editor only.
You can specify a dynamic XQuery expression that evaluates at runtime to the name of a pre-registered XQuery resource. Oracle Service Bus executes this XQuery resource, with optional variable bindings, against the message context to produce the required transformation.
Use the XQuery Resource page to configure a dynamic XQuery transformation to be executed in the message flow of a proxy service.
The XQuery expression that will evaluate at runtime to the name of a pre-registered XQuery resource.
|
|
The resource to serve as a template for the shape of the query (the number and names of the variables). Click Browse to select an existing registered resource. After selecting a template, the variables appear in the Bind Variables area. Note that the template is not persisted with the configuration. Instead, the template serves as a quick start to help you specify the variables for the query.
|
|
When you add a custom variable, it appears in the Bind Variables area. Similarly, when you select an XQuery template, each input parameter of the transformation is displayed. Each label corresponds to the name of a parameter, and each text box is for defining an XQuery expression to be mapped to the parameter. You must define a mapping for each parameter. Enter the expression directly, or drag variables and structures from the right panel.
|
This page appears in the XQuery/XSLT Expression Editor, the XPath Expression Editor, and the Condition Editor.
The Variable Structures page displays variables and their contents as trees. It includes the built-in message context variables attachments, body, header, outbound, and inbound, as well as any user-defined variables. It includes fault if the context of the expression is appropriate (that is, in an error handler). The outbound variable is always listed; even though it is not valid in every context. If outbound is used in invalid contexts, it will be reported when validating.
Each variable structure mapping entry has a label and maps a variable or variable path to one or more structures. The scope of these mappings is a stage or a route node.
You can drag items from this page to the editor’s Expression page to insert them into the current expression. They are inserted as XPath expressions.
To define a new variable and add it to the variable structure tree, click Add to open the Add Variable Structure dialog.
For more information about working with variable structures, see Working with Variable Structures in the Oracle Service Bus User Guide
This page appears in the XQuery/XSLT Expression Editor, the XPath Expression Editor, and the Condition Editor.
The Namespace Definitions page lists default Oracle Service Bus namespaces, variable namespaces, and user-defined namespaces. Click Add to define a new namespace, which is then added to the list of user-defined namespaces. To modify a user-defined namespace, select it in the list, then click Edit.
This page appears in the XQuery/XSLT Expression Editor, the XPath Expression Editor, and the Condition Editor.
The XQuery Functions page lists a set of standard XQuery functions, organized alphabetically and by type. You can drag functions from this page to the editor’s Expression page to insert them into the current expression. When you insert a function into an expression, placeholders are used for parameter values you must supply.
Use this dialog to define a variable and add it to the tree of variable structures in the Variable Structures page of the Expression Editors.
You create variable structures in this dialog to define the structure of a variable for design purposes. For example, it is easier to browse the XPath variable in the structure view rather than viewing the XML schema of the XPath variable. Variable structures do not create variables. Variables are created at runtime as the target of the assign action in the stage.
You can declare your own variable structures based on:
You can use this feature directly for all user-defined variables, as well as $inbound, $outbound, and $fault. However, you cannot use it directly to access XML attachments in $attachments, headers in $header, or documents and RPC parameters in $body, with one exception— you can use it directly to access documents and parameters in $body for request messages received by a WSDL proxy service.
When you create a variable structure based on XML types, MFLs, or service interfaces, you must enter the following information into the fields at the top of the page:
For more information about working with variable structures, see Working with Variable Structures in the Oracle Service Bus User Guide
Transformation maps describe the mapping between two data types. eXtensible Stylesheet Language Transformation (XSLT) maps describe XML-to-XML mappings. For more information, see XSL Transformations in Using the Oracle Service Bus Console.
Use this page to select a name and location for a new XSL transformation. This wizard creates a skeleton for the XSLT. Add details in the XSLT editor.
The following sections describe the fields and user interface components involved with creating and configuring Split-Joins in Oracle Service Bus.
The Split-Join Design Palette lists all the operations you can use to construct a Split-Join. To insert a control into a Split-Join, drag the icon from the palette to the Split-Join editor. When you drag an item to the editor, one or more circles (drag-points) appear (
) to indicate that you can drop the dragged item in that position on the editor. When you drag the item into such a circle, it is highlighted () to show that you can drop the item there.
The Split-Join Design palette is organized into the following categories:
The following table describes the operations you can add to a Split-Join:
Invoke Service invokes a WSDL-based, non-transport-typed Business Service, a WSDL-based Proxy Service, or a Split-Join.
For configuration properties, see Invoke Service Properties.
|
|
|
For configuration properties, see Reply Properties.
|
|
|
For configuration properties, see For Each Properties.
|
|
|
For configuration properties, see If Properties.
|
|
|
For configuration properties, see Parallel Properties.
|
|
Raise Error generates an error that causes the Split-Join to stop normal processing. If the error is not handled using an Error Handler, the Split-Join will terminate and a Fault will be sent to the Oracle Service Bus Message Flow.
For configuration properties, see Raise Error Properties.
|
|
Repeat Until lets you repeat operations until a condition evaluates to true within a Split-Join. The condition is evaluated after each loop finishes. For configuration properties, see Repeat Until Properties. |
|
|
For configuration properties, see Re-Raise Error Properties.
|
|
|
For configuration properties, see Scope Properties.
|
|
While lets you repeat operations until a condition evaluates to false within a Split-Join. The condition is evaluated before each loop commences.
For configuration properties, see While Properties.
|
|
|
For configuration properties, see Assign Operation Properties.
|
|
Lets you copy the information specified by an XPath expression from a source document to a destination document.
For configuration properties, see Copy Properties.
|
|
|
For configuration properties, see Delete Properties.
|
|
Lets you insert the result of an XQuery expression at an identified place relative to nodes selected by an XPath Expression.
For configuration properties, see Insert Properties.
|
|
Lets you invoke a static Java method from a Split-Join for custom actions such to be handled in Java such as validation, transformation, and logging.
For configuration properties, see Java Callout Properties.
|
|
|
For configuration properties, see Log Properties.
|
|
|
For configuration properties, see Replace Properties.
|
|
Operations have a General properties tab for changing the node’s label and providing comments.
The start node in a Split-Join specifies its global properties. Among these properties, global variables and associated External Services can be reviewed and configured by expanding the left-side arrow. The global Error Handler can be reviewed and configured by expanding the right-side arrow.
Use the Properties view to review and configure the Global Properties of the selected Split-Join.
The Imports tab has the following options:
The General tab has the following options:
Use the Properties view to review and configure Variables in the selected Split-Join.
Click to display the Create/Edit Variable Dialog, where you can modify the Variable’s name and type.
|
The Error Handler receives and handles all of the errors that are raised in a Split-Join.
An Error Handler lets you add Catch and CatchAll operations.
Use the Properties view to review and configure the selected Error Handler in a Split-Join.
The Catch tab has the following options.
The catchAll tab has the following options.
The Invoke Service invokes a WSDL-based, non-transport-typed Business Service, a WSDL-based Proxy Service, or another Split-Join.
Use the Properties view to review and configure the selected Invoke Service in a Split-Join.
The Operation tab has the following options:
|
When you select an operation, a dashed blue line appears pointing to the external service in the Split-Join editor. |
|
The Input Variable tab has the following options:
|
|||
The Output Variable tab has the following options:
|
|||
A Split-Join can invoke another Split-Join in the same Oracle Service Bus configuration. This functionality provides more flexibility in service design, letting you split up complex Split-Join functionality into multiple Split-Joins, allowing for componentization and re-use of Split-Join functionality. Performance is maintained, because there is no marshalling and unmarshalling of data between the Split-Joins.
You must ensure that you do not create circular Split-Join references. Oracle Service Bus does not check for circular references.
Reply sends a response or fault back to the Oracle Service Bus message flow.
Use the Properties view to review and configure the selected Reply in a Split-Join.
The Operation tab has the following options:
The Variable tab has the following Select options:
|
|||
|
|||
Reply automatically includes an implicit Exit operation to end that instance of the flow without triggering a fault. The Exit operation is not visible in the development environment.
For Each executes logic configured within its Scope a specified number of times.
Use the Properties view to review and configure the selected For Each in a Split-Join.
The Counter Variables tab has the following options:
Defines an implicit variable within the Scope of the For Each. Each iteration of the For Each contains an isolated instance of this variable. In turn, every instance is set to an iteration number; for example, the first iteration has its value set to Start Counter Value, the second iteration to Start Counter Value+1, etc. |
|
The value of the Counter Variable for the first iteration of For Each. Determined as the result of an XPath 1.0 expression. The result must be “1” or more. (“0” is not a valid Start Counter Value.) The browse button launches the expression builder. The expression should generate an integer for the initial Start Count Value. |
|
The value of the Counter Variable for the final iteration of For Each. Determined as the result of an XPath 1.0 expression. The result must be “1” or more. (“0” is not a valid Final Counter Value.) The browse button launches the expression builder. The expression should generate an integer for the Final Count Value. |
The Completion Condition tab has the following options:
If nodes contain If, Else If, and Else operations. See If and Else If Properties.
Use the Properties view to review and configure the selected If in a Split-Join.
The If and Else If operations provide conditional behavior within a Split-Join.
Use the Properties view to review and configure the selected If or Else If in a Split-Join.
If and Else If have the following options:
Parallel lets you create a static Split-Join that handles fixed number of message requests. Parallels contain one or more Scope branches.
Use the Properties view to review and configure the selected Parallel in a Split-Join.
Raise Error establishes an error condition under which the execution of the process will halt.
Use the Properties view to review and configure the selected Raise Error in a Split-Join.
The Raise Error tab has the following options:
Repeat Until lets you repeat operations until a condition evaluates to true within a Split-Join. The condition is evaluated after each loop finishes.
Use the Properties view to review and configure the selected Repeat Until in a Split-Join.
The Condition tab has the following options:
Use Re-Raise Error within an Error Handler to re-raise an error caught by a Catch or a CatchAll. In the Properties view you can rename and enter comments about the Re-Raise Error node.
Use the Properties view to review and configure the selected Re-Raise Error in a Split-Join.
The Scope creates a context which influences the behavior of its enclosed operations. Local variables and the Error Handler defined within the Scope are restricted to this context.
Use the Properties view to review and configure the selected Scope in a Split-Join.
While lets you repeat operations until a condition evaluates to false within a Split-Join. The condition is evaluated before each loop commences.
Use the Properties view to review and configure the selected While in a Split-Join.
The Condition tab has the following options:
Assign lets you perform data manipulation, including initializing and updating a Variable. You can perform the following operations in an Assign node: Assign, Copy, Delete, Insert, Java Callout, Log, and Replace.
Use the Properties view to review and configure the selected Assign in a Split-Join.
The Assign tab has the following options:
A variable to which the result of the XQuery expression is assigned. Only previously defined Variables, the Counter Variable, and SOAP Fault Variables (for Error Handlers) are available. |
Oracle Service Bus's Assign functionality in Split-Joins conforms to the WS-BPEL specification for resolution of XPath/XQuery expressions to simple type variables. Supported simple types for binding XPath/XQuery expressions to variables in Split-Joins are String, Boolean, and Float. The Assign converts the value you provide the type with which the variable is defined.
The Copy operation copies the information specified by an XPath expression from a source document to a destination document.
Use the Properties view to configure a Copy Operation in an Assign. Configure Select From and Select To using the following guidance.
The Copy tab has the following options:
Lets you determine which element name (source or destination) is used when values are copied from a source to a destination.
If you do not select this option, the existing element name in the destination is used to hold the copied value.
If you select this option, the name of the source element is used in the destination to hold the copied value.
For example, if you are copying a zip code value from <zipCode>80303</zipCode> in the source, selecting Keep Source Element uses the <zipCode> element in the destination. If you do not select the option, the zip code value is copied to the existing destination element, such as <pinCode>80303</pinCode>.
|
|||
Create an Xpath 1.0 expression to select a node from a Variable. Use this option when more complex Xpaths (potentially with predicates) are required to select a node on a Variable.
|
|||
The Delete operation deletes a set of nodes specified by an XPath Expression.
Use the Properties view to configure a Delete Operation in an Assign.
| Note: | Unlike a Delete operation in a proxy service message flow, a Delete operation in a Split-Join does not allow deleting a variable directly. |
The Delete tab has the following options:
The Insert operation inserts the result of an XQuery expression at an identified place relative to nodes selected by an XPath Expression.
Use the Properties view to configure an Insert Action in an Assign.
The Insert tab has the following options:
The location used to control where the Insert operation is performed relative to the result of the XPath 1.0 Expression. Options include:
|
|
A Java Callout operation lets you invoke a static Java method from a Split-Join for custom actions such to be handled in Java such as validation, transformation, and logging.
Use the Properties view to configure a Java Callout operation in an Assign.
The Java Callout tab has the following options:
Package your Java class in a JAR file in your Oracle Service Bus project. Click Browse to first select the JAR, then the method you want to invoke.
|
|
Oracle Service Bus provides the following errors for Java callouts:
The Log operation lets you log Split-Join data at a specified severity to the server log file. Administrators can use log information to take appropriate action based on the severity of the data logged.
Use the Properties view to configure a Log operation in an Assign.
The Log tab has the following options:
The Replace operation lets you replace a node or the contents of a node specified by an XPath expression.
Use the Properties view to configure a Replace operation in an Assign.
The Replace tab has the following options:
Specifies that the nodes selected by the expression are replaced along with all of its contents. |
|
Use the Properties view to review and configure the selected Receive in a Split-Join.
The Operation tab has the following options:
|
Browse to select an operation from the WSDL Browser.
|
The Variable tab has the following options:
|
|||
Use this dialog to create a Counter Variable.
Use this dialog to review and/or configure Variables in the Split-Join.
Although variables are visible in the scope in which they are defined and in all scopes nested within that scope, a variable declared in an outer scope is hidden when you declare a variable with an identical name in an inner scope. For example, if you define variable myVar in an outer scope (So) and then define variable myVar again in an inner scope (Si) which is contained by scope So, then you can only access the myVar you defined in the inner scope Si. This myVar overrides the myVar you defined in scope So.
Use this dialog to create a new Variable.
Use this dialog to browse for and select an operation from a business service, a proxy service, or a Split-Join in the tree.
Use this dialog to create a SOAP fault variable.
Use this dialog to browse for and select an operation from a WSDL in the depicted tree.
Use this page to locate and name the new Split-Join
Use this page to select an operation for the new Split-Join.
|
