|
|
This document includes the following topics:
| Note: | For more information, see the Oracle Service Bus Product Documentation. |
Oracle Service Bus is an enterprise-class service bus that connects, manages, and mediates interactions between heterogeneous services. Oracle Service Bus accelerates service configuration, integration, and deployment, thus simplifying management of shared services across the SOA.
Oracle Service Bus is policy-driven and enables loose coupling between service clients (service consumers) and business services (service providers). It provides a point of security control, monitoring, and Service Level Agreement (SLA) enforcement. Changes to service integration relationships are implemented dynamically through configuration, not code, allowing you to evolve and customize your service architectures with respect to security, service location, availability, data formats, monitoring, transports, communications, and so on.
As part of an enterprise messaging fabric, Oracle Service Bus can be used horizontally across many applications and systems, potentially spanning service implementations built by different teams in different departments. Oracle Service Bus separates a set of management functions from the service implementations, thus allowing the implementations to evolve independently and dynamically as driven by the needs of the business without requiring costly infrastructure development efforts.
For more information about Oracle Service Bus concepts and architecture, see Oracle Service Bus Concepts and Architecture.
To download Oracle Service Bus, go to the Oracle Downloads site.
In addition to its comprehensive connectivity, mediation, and management capabilities, Oracle Oracle Service Bus 10g Release 3 adds new advanced mediation features to easily handle complex SOA scenarios.
In addition to the features described in Oracle Service Bus 10g Release 3 (10.3) Features, Oracle Service Bus 10g Release 3 Maintenance Pack 1 (10.3.1) includes the following features:
Oracle Service Bus provides a J2EE Connector Architecture (JCA) transport that interacts with Enterprise Information Systems (EIS), such as Enterprise Resource Planning (ERP) systems, letting EIS applications and services participate in the service bus environment. For more information, see the JCA Transport User Guide.
Oracle Service Bus lets you automatically handle WebSphere MQ RFH2 headers in proxy and business services. For more information, see the MQ Transport User Guide.
The Oracle Service Bus documentation provides examples of exporting and importing Oracle Service Bus configurations using Ant, the WebLogic Scripting Tool (WLST), and the command line. For more information, see Exporting Resources and Importing Resources in Using the Oracle Service Bus Plug-ins for Workshop for WebLogic (Oracle Workshop for WebLogic online help).
The SOA Management Pack for Oracle Service Bus and Oracle WebLogic Server lets you manage your domains and configurations in Oracle Enterprise Manager. You can manage Oracle Service Bus in the context of your entire SOA environment, including project and resource deployment, historic monitoring (including action- and stage- level metrics), and configuration and service-level management. For more information, see the Oracle Enterprise Manager documentation.
The major themes and features in Oracle Service Bus 10g Release 3 (10.3) include:
For more information, see the Oracle Service Bus datasheet.
Oracle Service Bus provides a visual debugger in Workshop for WebLogic for debugging proxy service message flows and Split-Joins. You can set breakpoints in your message flows to automatically stop test execution at specific places, letting you view errors, variable values, and a graphical indication of where the test is in the message flow. For more information, see Using the Oracle Service Bus Plug-ins for Workshop for WebLogic.
Oracle Service Bus provides native support for REST (Representational State Transfer), letting you offer REST functionality in an SOA environment. Enhancements to the Oracle Service Bus native HTTP transport let you flexibly invoke REST-based external services, invoke external services from a REST-based application, or provide an end-to-end REST architecture in the service bus layer. For more information, see the "HTTP Transport" section of the HTTP and Poller Transports User Guide.
Oracle Service Bus now supports Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP). This enables you to configure business and proxy services to process messages in the MTOM/XOP format using the HTTP/S, Local, and SB transports, choosing to have the service include the binary data by reference or by value. For more information about configuring your services to use the MTOM/XOP format, see the “Message Content Handling Configuration page” sections for both business and proxy services in Using the Oracle Service Bus Console.
Oracle Service Bus provides support for streaming MIME attachments, enabling you to configure business and proxy services to store attachments to disk and process the data without buffering the contents in memory. This enables business and proxy services to process large attachments robustly and efficiently. For more information about configuring your services to stream MIME attachments, see the “Message Content Handling Configuration page” sections for both business and proxy services in Using the Oracle Service Bus Console.
Oracle Service Bus provides support for monitoring information about actions in a service pipeline, presented as a hierarchy of nested actions and nodes. The displayed metrics include a count of the number of invocations, the average execution time per invocation, and the total execution time for the action. For more information about action metrics, see the “Viewing Action Metrics” section in Using the Oracle Service Bus Console.
Oracle Service Bus expands its security support by letting you set Web Service Security policies on business and proxy services of type Any SOAP Service, in addition to the already-supported WSDL-based services. For more information on using WS-Security in Oracle Service Bus, see the “Using WS-Policy in Oracle Service Bus Proxy and Business Services” section in the Oracle Service Bus Security Guide.
Oracle Service Bus provides support for message tracing, enabling you to configure the system to log messages exchanged between proxy and business services and the Oracle Service Bus pipeline. You can specify the level of detail, the maximum size of the message payload, and the default encoding for logging the payload. For more information about configuring your services, see the “Configuring Operational Settings for Business Services” and “Configuring Operational Settings for Proxy Services” sections in Using the Oracle Service Bus Console.
Oracle Service Bus provides native support for interaction with Oracle BPEL Process Manager, letting you offer Oracle BPEL Process Manager process as services in an SOA environment. The new functionality also lets you call external services from Oracle BPEL Process Manager through Oracle Service Bus. For more information, see the Oracle BPEL Process Manager Transport User Guide.
Oracle Service Bus provides interoperability with Oracle Web Services Manager, letting you ensure perimeter security, message integrity, message confidentiality, message authentication, transport-level security, and identity propagation. For more information, see the Oracle Service Bus Security Guide.
For more information about Oracle Web Services Manager, see http://www.oracle.com/technology/products/webservices_manager/index.html.
Oracle Service Bus introduces new capabilities to the Split-Join feature, as well as usability and performance enhancements. New features include the ability to perform Java callouts for custom validation, transformation, logging, and so on; enhanced service administration capabilities through the ability to log data at a specified severity to the server log file; and high-performance invocations of one Split-Join from another Split-Join. For information on Split-Join, see the “Working with Split-Join” section in Using the Oracle Service Bus Plug-ins for Workshop for WebLogic.
Oracle Service Bus provides dynamic message transformation based on XQuery supporting both XML and non-XML message formats. This feature reduces integration complexity and time to market due to the ability to provide heterogeneous legacy assets with comprehensive data transformation capabilities. For more information, see Binding Dynamic XQuery Expressions to Inline XQueries in Using the Oracle Service Bus Console.
Following are updates to the Oracle Service Bus Transport SDK from AquaLogic Service Bus 2.6:
The Transport SDK provides improved error handling support, giving you more control over how communication and application errors are identified and handled. See Handling Errors in the Oracle Service Bus Transport SDK User Guide.
The Transport SDK provides the following expanded configuration capabilities through the TransportCommon.xsd schema, described throughout the Oracle Service Bus Transport SDK User Guide.
The following methods in class com.bea.wli.sb.services.BindingTypeInfo have been deprecated: hasWSSecurityPolicy() and hasRMPolicy().
The following sections summarize the supported configurations for Oracle Service Bus 10g Release 3 (10.3).
For information about supported operating systems, databases, drivers, browsers, plug-ins, and other hardware and software requirements, see Supported Configurations.
For information about installing Oracle Service Bus, see Oracle Service Bus Installation Guide.
For information about Oracle Service Bus 10g Release 3 (10.3) interoperability, including information about support for compliance with messaging standards including SOAP, HTTP, JMS, SMTP/POP/IMAP, FTP, SSL, XML, XML Schema, WSDL, WSRP, and WS-Security, see Oracle Service Bus Interoperability Support Matrix.
Two data transformation tools are installed when you install Oracle Service Bus and Workshop for WebLogic—the BEA XQuery Mapper plug-in for Eclipse 3.3 and Format Builder. Eclipse 3.3 and Format Builder are supported on Windows and Linux.
When you install Oracle Service Bus 10g Release 3 (10.3), the required patches listed in Table 1 are installed automatically. If you uninstall any of these required patches and need to reinstall them, use the information in Table 1 in conjunction with Smart Update to reinstall and apply the patches.
For more detailed information about the patches, run Smart Update and click the information icon next to the patch ID.
See the Oracle Service Bus Upgrade Guide .
The following sections describe known problems in Oracle Service Bus 10g Release 3 (10.3), as well as problems that were resolved in 10g Release 3 (10.3). Entries include a description of the problem and a workaround or solution where appropriate. A notation in the Fixed In column indicates that the problem has been resolved:
An ALSB domain cannot boot and generates weblogic.transaction.loggingresource.LoggingResourceException if the domain is a new domain using the same database, schema, and LLR table as an existing domain.
When you move a domain template to a different machine and use the template to create the new domain, the new domain is not able to boot and
weblogic.transaction.loggingresource.LoggingResourceException is thrown. The following details outline the scenario:
|
|||||
Workaround: You must use the same domain name when you create the new domain using the same template on a different machine. Alternatively, change the name of the LLR table that the new domain uses. You can configure this on the Oracle WebLogic Server Administration Console on a per Server basis, using the
JDBCLLRTableName attribute on the ServerMBean.
|
|||||
Keep the path of proxy services short for successful deployment on Windows machines because of a system path length limitation.
This limitation applies to both JMS proxy services and business services with responses. Because the generated proxy service EAR file is created in the domain directory, you should keep the path to the domain directory short. It is not necessary to keep the name of the proxy service or business service short.
The limit for the generated EAR file is 50 characters and the null terminator is 1 character. Therefore, in a single server domain, the domain directory path (including the following slash) may not exceed 209 characters. In a cluster domain, the domain directory path plus the name of any managed server may not exceed 142 characters.
|
|||||
|
When you create a non-system fault in ALSB, you cannot use the default system prefix (
soap-env) for the namespace. You must declare a new namespace prefix and use it in the faultcode.
|
|||||
When you copy large files into an input directory in Windows, misleading errors are logged to the server log file.
In the Windows operating system, when you copy large files (for example, 100MB) into the input directory of a file transport proxy service, errors are logged in the server log file that state:
|
|||||
A single stand-alone JMS client cannot consume all messages on uniform distributed queues (UDQs) when the default ForwardDelay is set.
|
|||||
Publishing to UDDI intermittently returns an error when you publish a service to AquaLogic Service Registry.
|
|||||
Due to hot deployment, the correct version of an invoked service's MFL or WSDL may not be properly seen by a proxy service that invokes that service.
|
|||||
Updates to an EJB client JAR or an EJB converter JAR are not reflected in the deployed EJB transport-based business service.
Suppose you have an EJB transport-based business service that uses an EJB Client JAR file and a Converter JAR file. If you update the implementation in one of those dependent JAR files, ALSB re-validates the business service, but because the interface has not changed, no errors are raised. However, ALSB will not redeploy the EJB transport-based business service, so it will continue to contain the implementation from the previous version of the JAR file. The EJB endpoint needs to be redeployed to contain the updated JAR file implementation.
|
|||||
ALSB can successfully import services from a UDDI registry even if those services were created with a newer version of ALSB. For example, services created in 2.6 can be published to UDDI and subsequently imported into 2.5.
This presents no problem if the proxy service published by the later version uses no features new in the later release—that is, the service can be imported and invoked in the earlier ALSB version.
However, if a proxy service published by the later version uses features new in that version, it cannot be used in the earlier version. (for example, a SOAP1.2-based business service can be imported, but it does not work.)
It is also possible that a proxy service published by a later version of ALSB differs in how it is published compared to how services were published from older versions. The service may be supported after import to the earlier version; however, the imported business service may need to be fixed after import (for example, in 2.6, there were changes to how transport security was published).
|
|||||
Attributes on the SOAP envelope element may not be preserved when the message is modified in the pipeline.
Previously, insert, replace, delete and rename operations on $body or $header left attributes on the SOAP envelope unaffected (though not so for an assign to $body or $header). These attributes can include the
encodingStyle attribute or other custom attributes whose loss may have a serious impact on the processing of the message. However, namespace attributes are preserved in the message.
Workaround: Do not use attributes, other than namespace declarations, on the SOAP envelope. Instead, push these attributes (such as
soap:encodingStyle) down to the SOAP Body element. When attributes are on the SOAP Body or Header element, they are fully exposed in the pipeline and under the control of the transformation operations.
|
|||||
A monitoring run-time exception can occur at startup for managed servers if activation notifications reach different managed nodes at different times
|
|||||
A new SLA alert may not fire if you change the order it appears in the list of alerts for a service in the ALSB Console.
|
|||||
Using a very large input MFL with a file transport proxy service that routes to a business service causes the output file to be duplicated.
|
|||||
|
BEA JRockit R27.2.0 is installed with ALSB 2.6 RP1. To avoid potential issues when running the SFTP transport on JRockit R27.2.0, download JRockit R27.3.1 from
http://www.oracle.com/technology/software/products/jrockit/index.html.
|
|||||
The following JNDI and JMS resources are secured in ALSB 3.0 and only users in ALSBSystem role or Admin role can access them:
|
|||||
|
When running MQ Server under a heavy load (for example, 200 clients) or over an extended period of time (for example, 24 x 7 production system), a connection error occurs.
|
|||||
Message flow editing is HTTP session based. While using the message flow editor, you will not be aware of any changes that were done in another browser window or in core. Once you save the message flow and activate your changes, you'll have the option of undoing your changes or another user's changes.
|
|||||
When you configure JMS endpoints with SSL ports in a clustered environment and use a local queue, rather than a distributed queue, as an inbound request queue, you might see connection exceptions. These exceptions are thrown by the MDBs deployed on the cluster nodes different from the node on which the local queue is deployed.
|
|||||
The activation of a session that deletes a JMS proxy service will hang when an instance of that proxy service is stuck on some operation.
|
|||||
Upon initially launching WorkSpace Studio and specifying a workspace directory location, do not locate your workspace in a deeply nested directory.
|
|||||
If your reliable client code stores any instances of
weblogic.wsee.connection.transport.https.SSLAdapter or weblogic.wsee.connection.transport.http.HttpTransportInfo, these objects must be serializable and their classes must be on the system classpath. Otherwise, SAF may fail during restart if there are reliable conversations pending.
If you see an error similar to the following, then your implementation of
SSLAdapter or HttpTransportInfo is probably not on the system classpath:
|
|||||
Using the MQ transport, you cannot define retry counts on a queue. Therefore if a message is read and rolled back by the pipeline, the proxy service will keep trying to read and process the message indefinitely.
Workaround: Implement the retry logic in the pipeline by checking the
backoutCount MQMD header that is set by MQ on the message. The backoutCount MQMD header tells you the number of times a message has been backed out. The pipeline can be configured to publish the message to a dead letter queue and stop the processing when the backoutCount reaches a certain number.
|
|||||
Creating a domain template or creating an application extension template from an existing ALSB domain, and then creating additional domains from your template doesn't work.
The newly created domain doesn't have the right policy definitions, as a result you can't login to the ALSB Console.
This is because the tool which generates templates from an existing domain (config_builder.cmd/sh) does not include the following files in the resulting template JAR:
DefaultAuthorizerInit.ldift and XACMLAuthorizerInit.ldift.
Workaround: After creating the template, and before you create any new domains from this template, you must do the following:
|
|||||
Running simultaneous MFL transformations on the same MFL resource may result in the following error:
|
|||||
Creating a domain template from an existing ALSB domain, and then using the template to create a domain in a different
BEA_HOME location will not work.
When creating a domain template from an existing domain, the
setDomainEnv file includes a reference to a hard-coded BEA_HOME location. Therefore, if you use the template to create a new domain in a different BEA_HOME location, ALSB_HOME points to the old BEA_HOME.
|
|||||
|
WSDLs with partnerLinkType extensions are not properly handled by the extension parser unless all namespaces used within that element are defined on the element itself with unique namespace prefixes.
Workaround: If the WSDL resource has
<plnk:partnerLinkType/>, it is necessary to define all the namespaces used within the partnerLinktype on the <plnk:partnerLinkType/> element itself. In addition, the namespace prefix has to be unique within the WSDL even if the namespace values are similar to ones defined on the parent node.
This WSDL will not work because
xmlns:tns is defined both on <wsdl:definitions/> and <plnk:partnerLinkType/> even though the namespace value is exactly the same.
<wsdl:definitions name='LoanServices'
|
|||||
For it to work, change the WSDL as follows. Notice that on the
<plnk:partnerLinkType/> element, the namespace prefix and all its references are changed from tns to tns2.
<wsdl:definitions name='LoanServices'
<plnk:partnerLinkType name='loanPartnerLinkType'
|
|||||
|
|||||
When you make a change to a property sheet and use UNDO or REDO, the property sheet does not show the correct state.
Workaround: To see the correct GUI state, you must select a different type of node and then reselect the original node you were editing.
For example: On a JavaCallout, you modify the method name and set an expression for a method parameter. Select the UNDO action twice. If the JavaCallout node is selected it will continue to incorrectly show the method and the expression name. If you select a different type of node (anything other than a JavaCallout node, for example Receive), and then re-select the JavaCallout node, the UI reflects the correct state after the UNDO.
|
|||||
|
In certain cases, when you import from UDDI using the Oracle Service Bus plug-in for Workshop for WebLogic, the Problems View shows the error message:
This error is most likely due to file extensions being removed during the export to UDDI, the import from UDDI, or both.
|
|||||
ALSB 3.0 allowed an insert in a Split-Join to insert into an uninitialized variable. From Oracle Service Bus 10g Release 3 (10.3) onwards, such an insert will fail with the following error:
|
|||||
|
The following message may appear in the Oracle Service Bus server log file if the Oracle Service Bus debugger is left idle on a breakpoint for more than 10 minutes:
####<Sep 24, 2008 2:49:08 PM PDT> <Error>
|
|||||
Transport endpoint deployment fails with TransportException “No transport provider registered with ID”
In Oracle Service Bus 10g Release 3 (10.3), Oracle Service Bus applications that use custom transports or an earlier version of the Oracle Service Bus sample socket transport may fail to deploy their endpoints after server restart with an exception like:
Exception on
For more information, see “Changing the Order of Deployment at Server Startup” in Deploying Applications to WebLogic Server. |
|||||
|
When a JCA-compliant adapter activates a JCA proxy service with an inbound request, the proxy service endpoint seems to be activated successfully, but the console and server log show an activation error. The error is accurate. The Oracle Service Bus JCA adapter framework uses two-phase commit for endpoint activation with createEndpoint and activationComplete methods. The activationComplete method does not support exception propagation, so if an exception occurs during activationComplete the endpoint appears to be successfully activated when it is not.
|
|||||
Intermittent database connection failures when using a JCA business service with the Oracle AQ adapter.
|
|||||
Database polling exception in a JCA proxy service with Oracle Database adapter when you change maxTransactionSize.
|
|||||
Managed servers in a cluster perform duplicate database operations on Sybase with a JCA Oracle Database service.
When using a JCA service with the Oracle Database adapter in a cluster to perform database operations on a Sybase database, the managed nodes in the cluster process the messages and attempt to perform duplicate operations. Supported versions of Sybase do not support Oracle Toplink record locking, therefore allowing the duplicate operation attempts.
|
|||||
|
When using an Oracle Service Bus JCA service in conjunction with the Oracle AQ adapter, exceptions occur when the adapter’s data source is transactional (for example, uses an XA driver). The Oracle AQ adapter does not support using a transactional data source in a non-Java Transaction API (JTA) environment.
|
|||||
|
After importing an Oracle Service Bus configuration that contains Tuxedo services, the Tuxedo services are not activated. The cause of the issue is manual modifications made to WebLogic Tuxedo Connector (WTC) resources in the Oracle WebLogic Server console.
Workaround: The workaround involves deleting all WTC resources from the Oracle WebLogic Server console before re-importing the Oracle Service Bus configuration JAR that contains Tuxedo services. If you have WTC resources manually configured in the Oracle WebLogic Server console that are not defined in the Tuxedo services you are importing, you must also delete those before you re-import the Oracle Service Bus configuration, then manually re-create those resources in the Oracle WebLogic Server console.
To help avoid this issue, when working with WTC resources in Oracle Service Bus, modify those WTC resources in the Oracle Service Bus service editors instead of in the Oracle WebLogic Server console. However, if you also use WTC resources not defined by Oracle Service Bus services, you must always use the workaround when importing Oracle Service Bus configurations that contain Tuxedo services.
For more information, see
Configuring WebLogic Tuxedo Connector in the Oracle Service Bus Interoperability Solution for Tuxedo guide.
|
|||||
Before deleting, moving, renaming, cloning or deleting a proxy service (or deleting, renaming, or moving a project or folder (which, in effect, changes the URL for proxy services in the projects or folders)), delete all associated Transport-level (HTTP and HTTPS) and Service-level access control security policies.
Failure to delete these policies will leave the policies in the authorization-provider database and potentially cause unexpected results and potential security vulnerabilities, such as leaving unprotected a service which was previously protected.
|
|||||
A problem in the client-side Web Service Security runtime causes X.509 token authentication to fail in certain cases.
Make sure to include a dummy username token
CredentialProvider (see source code that follows) along with a ClientBSTCredentialProvider in the list of credential providers passed to the JAX-RPC client. The credential provider list is passed to the client as the value of the property named weblogic.wsee.security.wss.CredentialProviderList.
For more information, see “Updating a Client Application to Invoke a Message-Secured Web Service” under “Configuring Message-Level Security (Digital Signatures and Encryption)” in
WebLogic Server Web Services: Security.
|
|||||
|
ALSB 2.5 service validation generates warnings when a policy bound to the service has unknown policy assertions. However, this release does not check for unknown policy assertions in WSDL or WS-Policy resources.
Workaround: Check for unknown WS-policy assertions in the WSDL. Ensure that the WSDL contains only valid assertion entries. For more information see
Using WS-Policy in Oracle Service Bus Proxy and Business Services in the Security Guide.
|
|||||
Workaround: Establish domain trust. When there is no cross-domain transaction, these security exceptions can occur for WebLogic Server 9.1 and earlier releases. For 9.2 to 9.2 cross clustered domain JMS/JNDI/RMI calls, this exception is intermittent. Workaround: Configure the JTA SecurityInteropMode to “Performance” in the WebLogic Server Administration Console for 9.x domains, and on the command line for older versions. For more information, see “Setting Security Interoperability Mode” in Configuring Domains for Inter-Domain Transactions in Programming WebLogic JTA. |
|||||
|
Consider the scenario in which an HTTPS request (HTTP over SSL) comes into the Web server front end; the WebLogic Server Web server plug-in subsequently forwards that request to an ALSB managed server containing an ALSB HTTP proxy service.
The Web server plug-in can be configured to forward the request over HTTP—that is, without using SSL. However, the ALSB HTTP proxy service interprets the request as having come over HTTPS and rejects it. In this case, the server log shows an error of the form:
<Exception in HttpTransportServlet.service:
Workaround: Configure the proxy service with the HTTPS transport. Even though the message comes over the non-SSL port from the Web server, ALSB recognizes that the message originally used the HTTPS protocol and accepts the message as an HTTPS message. The SSL port in the ALSB domain must be enabled to do this, even though it is not used in this scenario.
|
|||||
|
When trying to use cross-domain security between ALSB and other domains, such as WLI and ALDSP, WebLogic Server throws an
Invalid Subject exception.
Workaround: None. By design, cross-domain security cannot be used for RMI calls between EJBs. RMI calls work only between JMS, JTA, MDB, and WAN replication.
For more information on cross-domain security in WebLogic Server, see
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/domain.html.
|
|||||
Web Services security user name token with password digest requires using the default Authentication provider.
The DefaultAuthenticator is the only out-of-the-box Authentication provider that supports password digest authentication. For more information on Authentication providers, see
Configuring Authentication Providers in the AquaLogic Service Bus Security Guide.
|
|||||
You must enable domain trust to validate a caller's subject passed from an ALSB domain to another ALSB or WLS domain
Consider two ALSB domains or ALSB and WLS domains that each contain a user with the same credentials. If you pass a JMS message as that user from one domain to another with a JMS business service with
Pass Caller's Subject enabled in the Request Pipeline, the operation will fail with an Invalid Subject exception.
Workaround: When
Pass Caller's Subject is enabled, you must also enable global trust. For more information on enabling global trust, see
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/domain.html#wp1176064.
|
|||||
One-way SSL from Oracle Service Bus to OC4J without valid key allows encrypted payload transmission without certificate enforcement
The Oracle Service Bus BPEL Transport uses an ormi client to access BPEL PM over the ormi protocol. However, the Oracle ormi client does not naturally authenticate the server.
|
|||||
A "Graphics Library Disabled" image is displayed instead of charts in the Monitoring module if the Graphics Library cannot be initialized.
A "Graphics Library Disabled" image is displayed instead of pie and bar charts in the Monitoring module if the Graphics Library cannot be initialized in a Linux environment. Links on the Server Summary, Server Detail, Alert Summary, and Alert Detail pages are also removed. The problem may be that the graphics library support (X11) toolkit is not installed on your machine.
|
|||
|
Only users in the WebLogic Server built-in Administrator role are allowed to manage access control policies on ALSB resources; that is, transport-level HTTP or HTTPS proxy service access control policies and proxy service policies. To configure these policies, users must log in to the ALSB Console as the WebLogic Server Administrator and select Access Controls in the Security Configuration module.
|
|||
The default browser options for Windows 2003 Server cause a browser JavaScript Error when you click a link in the left navigation pane of the ALSB Console.
|
|||
The ALSB Console incorrectly includes non-public classes and their methods when listing Java methods that can be called from a JavaCallout Action.
|
|||
You can view and edit the Description field of a flow resource only in the Oracle Service Bus Console. Workshop for WebLogic does not currently support this field. The Description field value is preserved when you export and import using only the Oracle Service Bus Console. The Description field value is not preserved if you export from the Oracle Service Bus Console, modify the exported resources in Workshop for WebLogic, and import using Oracle Service Bus Console.
|
|||
|
When the Oracle WebLogic Server Administration Console is deployed, both the console and its help application is deployed. The Oracle Service Bus Console depends on this help application. In a development mode domain, the Oracle WebLogic Server Administration Console is deployed on-demand. In this case, if you do not access the Oracle WebLogic Server Administration Console, neither it nor the help application is deployed and will not be available for use by the Oracle Service Bus Console. In a production mode domain, Oracle WebLogic Server Administration Console is deployed at server start time.
|
|||
Importing WSDLs and dependent resources into an Oracle Service Bus project shows referencing errors.
When you import a WSDL into an Oracle Service Bus project, you get reference errors even after you subsequently import the dependent resources.
Workaround: Import WSDLs using the “Resources from URL” feature, as described in
Loading Resources from a URL in “Working with Projects, Folders, and Resources” in Using the Oracle Service Bus Console. Parallel functionality is available in Oracle Workshop for WebLogic when selecting Import > Oracle Service Bus – Resources from URL in an Oracle Service Bus project.
|
|||
“Business Service configuration requires at least one URI” message in Workshop for WebLogic Business Service editor.
|
|||
In some cases, a code defect will prevent an MFL type name from being resolved because the code is not properly handling the namespace URI part of the MFL type name.
Workaround: Before upgrading the xq file (or if the upgrade has already failed due to this bug), open the xq file in a text editor and remove the namespace URI part of the type names for the return type and any parameters. For example:
xquery version '1.0' encoding 'Cp1252';
should be edited to remove the
@schemas/tcpuzoneddecimalranges part of the “type” attributes’ values:
xquery version '1.0' encoding 'Cp1252'; |
|||
Required patches are not automatically installed when you use the BEA Smart Update tool to upgrade from ALSB 2.6 to ALSB 2.6 RP1.
|
|||
Installing Oracle Service Bus 10g Release 3 (10.3.0) will fail if Mercury profiling tools support is enabled. Oracle Service Bus requires JDK 1.6 which no longer supports the JVMPI interface that Mercury Interactive classes use.
|
|||
After upgrading from previous releases to Oracle Service Bus 10g Release 3 (10.3), one may get conflict messages, such as:
|
|||
When creating a new domain, if you choose to customize JDBC data sources, Oracle Service Bus scripts may disappear from the screen if you select a data source other than wlsbjmsrpDataSource, then re-select wlsbjmsrpDataSource.
|
|||
|
