BEA AquaLogic Service Bus is designed to simplify the life cycle costs and complexities of integrating and managing shared services in an enterprise Service-Oriented Architecture (SOA) environment. It combines intelligent message brokering with service monitoring and administration to provide a unified software product for implementing and deploying your SOA.
AquaLogic Service Bus is policy driven and enables loose coupling between service clients (the service consumers) and business services (the service providers), providing 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 your service architectures with respect to security, service location, availability, data formats, monitoring, transports, communications, and so on.
As part of an enterprise's messaging fabric, AquaLogic Service Bus can be used horizontally across many applications and systems, potentially spanning service implementations (built by different teams) in different departments. AquaLogic 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.
This release of AquaLogic Service Bus introduces key new functionality and provides improved usability and enhanced performance. The following sections summarize the innovations in AquaLogic Service Bus 2.1:
The following new actions are available in the message flow:
For Each—Allows iteration over a sequence of values and execution of a block of actions within pipelines, branch and route nodes
Transport Headers—Provides a convenient way to set the transport header values in messages
Web Service Callout actions are renamed to Service Callout actions to reflect their more general functionality. Service Callouts can now invoke any kind of request/response service, not only Web services.
A test console can be invoked from the AquaLogic Service Bus Console. From the test console, you can invoke and test any proxy service or business service defined in the system. The built-in test console also allows you to test XQuery, XSLT, and MFL resources. You can also test in-line XQueries in the pipelines.
AquaLogic Service Bus 2.1 supports interoperability with version 3 compliant UDDI registries. You can publish proxy services to and import business services from v3 UDDI registries.
AquaLogic Service Bus 2.1 provides support for SAML 1.1 inbound and/or outbound with WS-Security. This includes identity propagation through an intermediary using SAML outbound.
The following enhancements were made to the alerts and monitoring subsystems:
Alerts are now logged to the server log
You can reset statistics for all services or individual services from the AquaLogic Service Bus Console
From the Monitoring summary display, you can view metrics for the last aggregation interval (last x minutes) or since the last reset
The Monitoring details page displays retry counts, min. and max. response times, success and failure ratios. In addition, you can now define alerts on these metrics.
A JMS filter can be defined if the proxy service inbound transport is JMS. With this feature, multiple proxy services can share the same JMS request queue
You can define JMS inbound retry behavior and an error queue for a proxy service whose inbound transport is JMS
Usability
You can bulk import resources in to AquaLogic Service Bus using a ZIP or JAR file or from a URL. This allows registration of large numbers of resources at one time and provides the ability to get the WSDLs and included schemas, policies, and WSDLs of a proxy service in a JAR file
The XQuery and XPath editor functionality in the AquaLogic Service Bus Console is enhanced for better usability and easier creation of XQuery statements
A read-only view of proxy service message flow is supported
You can now attach a description to projects and folders and to a session at activation. This allows you to tag your projects, folders, and sessions with metadata that is useful in managing your AquaLogic Service Bus system and resources
You can perform recursive undo operations in sessions and undo the activation of an old session into a new session
All objects in the AquaLogic Service Bus resource cache now show the time at which they were created and the name of the user who created them
Access all resources, except business services, in the repository via a URL
The user interface for the message flow configuration has been improved to provide an enhanced user experience
Performance
Performance has been improved in many areas including:
Reporting—JMS Reporting Provider takes advantage of MDB transction batching along with JDBC batching to improve throughput performance
AquaLogic Service Bus Console—tuned for thousands of artifacts and services in the resource cache
HTTP outbound—when the quality of service is best effort, HTTP outbound is now non blocking
Deployment
Deployment has been improved in many areas including:
Support for online deployment of any repository artifacts and services in a running system.
In other words, you can update the configuration on a production system without affecting the in-flight messages through the pipeline. The in-flight messages in the pipelines have a consistent view of the configuration and are processed by the old definition of the configuration; they are not affected by the new configuration definition. However, new messages coming into the running system see the new configuration definition.
Support for durable subscriptions, and pinning of a proxy service subscribing to a topic to a single managed server
The tutorial provides the steps to configure the AquaLogic Service Bus Console and test the configured system to demonstrate message validation and error handling.
The BEA XQuery Mapper is provided as a set of plug-ins to Eclipse 3.1.
You can select an element or attribute in the Source, Target, or Expression Variable paneand view the associated schema properties in the Property Editor. The Property Editor displays a read-only view of the schema properties for the selected element.
For more information, see "Using the Property Editor When Editing an XQ file", which is available at the following URL:
You can create a WSDL file using the WSDL Editor that is shipped with Eclipse. The XML schema defined in the WSDL files can be used in the transformation.
For more information about using the WSDL Editor, see the WSDL Editor Tutorial, which is available at the following URL:
Upgrading AquaLogic Service Bus 2.0 Service Accounts and Proxy Service Providers to AquaLogic Service Bus 2.1
If you have service accounts or proxy service providers in AquaLogic Service Bus 2.0, you must pay special attention to the upgrade guide when you export and import the usernames, passwords, and PKI key-pair mappings. (Reference CR255531).
Supported Configurations and System Requirements
This section summarizes the supported configurations for AquaLogic Service Bus 2.1. It includes the following topics:
The following data transformation tools are installed when you install AquaLogic Service Bus 2.0: The BEA XQuery Mapper plug-in for Eclipse 3.1 and Format Builder. Eclipse 3.1 and Format Builder are supported on Windows platforms only (see Operating Systems, Databases and Drivers, and Browsers and Plug-Ins).
The BEA XQuery Mapper is a set of plug-ins in Eclipse. Note that the installation of Eclipse with the AquaLogic Service Bus product does not include the Java Development Tooling (JDT) plug-ins or the Plug-in Development Environment (PDE) toolkit. You can add other plug-ins to the Eclipse IDE provided with AquaLogic Service Bus. However, when you attempt to install a plug-in, any plug-ins that it depends on must already be installed. Likewise, if the plug-in you want to install depends on the JDT or the PDE, you must install these first. You can download the PDE and JDT plug-ins from http://www.eclipse.org/.
Support for RPC and Document Encoded WSDL-Based Web Services
Web services can expose one of two styles for binding to their Web operations in the Web Service Description Language (WSDL) contract that describes them: Document or RPC. AquaLogic Service Bus does not support encoding and decoding aspects for RPC or Document encoded proxy or business services, but does support RPC literal and Document literal.
If a WSDL specifies an encoded binding, an error is not returned—instead, AquaLogic Service Bus uses literal encoding. However, straight pass through of encoded envelopes without manipulation in the message flow does work.
(Reference CR234886)
Known and Resolved Issues
The following sections describe known problems in AquaLogic Service Bus 2.1, as well as problems that were resolved in 2.1. 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:
Do Not Specify the Same Directory for Polling as is Specified for Archiving Files
In general, it is not advisable to specify the same directory location for your poller and archive file locations when you design a proxy service with a file transport. If you need to specify the same directory location that is specified for the poller and archive files, you must specify an appropriate mask for the files to be polled; for example, you can specify *.txt, *.bmp, and so on.
2.0
2.1
CR209177
Version Utility weblogic.version Does Not Display Version Information for AquaLogic Service Bus
Version information for AquaLogic Service Bus is contained in the version.jar file that is located at BEA_HOME/weblogic90/servicebus/lib, but it is not displayed by the utility java weblogic.version.
Workaround:
Set up your environment by running domain/bin/setDomainEnv.cmd, where domain is the name you gave your domain when you created it. For Windows, use setDomainEnv.cmd; for UNIX, use domain\bin\setDomainEnv.sh.
Add BEA_HOME/weblogic90/servicebus/lib/version.jar to your CLASSPATH, where BEA_HOME is the directory in which you installed your BEA product.
Invoke java weblogic.version. The version information for AquaLogic Service Bus is now displayed.
Alternatively, you can open the servicebus/lib/version.jar file and manually examine the version information in the manifest file, Manifest.mf.
Note:
The Service Bus version.jar file contains the temporary product name and version "WebLogic Service Bus 9.0". The correct name and version is "AquaLogic Service Bus 2.0".
2.0
2.1
CR221833
Some Updates to Policies in the AquaLogic Service Bus WS-Policy Repository are not Picked up by Proxy or Business Services that Depend on the Policy
When a proxy service or business service depends on a WS-Policy in the WS-Policy repository via a reference in the WSDL of the form policy:<policyId>, updates to the WS-Policy are not reflected on the proxy or business service.
Workaround: Make a change to the WSDL that references the policy. Any inconsequential change to the WSDL will do (for example, add a space).
2.0
2.1
CR234940
CR235638
Do Not Use the Default System Prefix (soap-env) when Constructing a Non-System Fault in AquaLogic Service Bus
When you create a non-system fault in AquaLogic Service Bus, 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.
Workaround: To construct a non-system fault in AquaLogic Service Bus:
Assign the SOAP body with the desired fault format to the body context variable ($body).
When creating <faultcode>, you must declare a new namespace prefix for http://schemas.xmlsoap.org/soap/envelope and use the new prefix in the faultcode. For example:
Do not write recursive XQuery statements when you design your proxy services.
2.0
CR231102
Keep the Path of Proxy Services Short for Successful Deployment on Windows Machines
Keep the path of proxy services short for successful deployment on Windows machines, as there is a system path length limitation on Windows machines.
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.
Note:
To learn about maximum path lengths, see the following information: "Maximum Path Length" at the following URL:
AquaLogic Service Bus Domain Cannot be Started with weblogic.transaction.loggingresource.LoggingResourceException
You cannot start an AquaLogic Service Bus domain with weblogic.transaction.loggingresource.LoggingResourceException when you move a domain template to a different machine and use the template to create the new domain. The scenario is as follows:
Create the original domain.
Start the server for the original domain. At this point, the domain is now "used"—a domain is considered used once you have started the server for a domain after you have created it.
Create the domain template. You can create it in several different ways—use the Domain Template Builder tool and the Configuration Wizard, the pack\unpack command, or the Weblogic Scripting Tool in offline mode.
Move the domain template to a different machine.
Create a new domain using the template. Again, you can create it in several different ways—use the Domain Template Builder tool and Configuration Wizard, the pack\unpack command, or the Weblogic Scripting Tool in offline mode.
Start the server for the domain. If the new domain does not have the same name as the initial domain, the new domain cannot be started. This is because the JMS Reporting Provider provided with AquaLogic Service Bus uses the Logging Last Resources (LLR) option. The new domain is attempting to use the same database, schema, and LLR table name to store LLR transaction records. LLR does not allow this to prevent different domains from corrupting each other's tables. To learn more about the LLR feature, see Configuring JDBC Data Sources in Configuring and Managing WebLogic JDBC.
Note:
You can access the Domain Template Builder, Configuration Wizard, and the WebLogic Scripting Tool from the BEA ProductsTools menu on your machine. The tools and the pack and unpack commands are located in the BEA_HOME/weblogic90/common/bin directory.
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 WebLogic Server Administration Console on a per Server basis, using the JDBCLLRTableName attribute on the ServerMBean.
2.0
CR231843 (continued)
Note:
There is no protection mechanism similar to LLR's for standard WebLogic JDBC store tables. Therefore, if you replicate a domain that has WebLogic JDBC stores configured without renaming the store tables or without using a different database user and schema for the new store's connection pool, data corruption occurs if both the old and the new domains remain active. Similarly, corruption (without warnings) may occur if same-named WebLogic file stores share the same directory.
2.0
CR231880
CR249881
If the Administration Server Crashes When a Session Activation is in Progress, a WebLogic Server Change Lock Prevents Further Session Activations
When a session is activated, AquaLogic Service Bus acquires a WebLogic Server lock that is held throughout the activation, and then released when the activation completes (successfully or not). However, if the administration server crashes before the session activation completes, the lock is not released automatically when you restart the server. This lock prevents further session activations.
Workaround: Log on to the WebLogic Server Administration Console, and release the lock held by WebLogic Server.
2.0
CR233226
The Response Destination May Not be a WebLogic Server Distributed Destination in the Same Cluster as AquaLogic Service Bus for JMS Business Services
The response destination may not be a WebLogic Server distributed destination in the same cluster as AquaLogic Service Bus for JMS business services.
Workaround: WebLogic Server regular (pinned) destinations, WebLogic Server distributed destinations in a different cluster, and non-WebLogic Server destinations may be configured as response destination.
2.0
2.1
CR233275
A Messaging Proxy Service Still Receives and Routes Messages After it has been Deleted if the User Sends Messages to it
A Messaging Proxy Service still receives and routes messages after it has been deleted if the user sends messages to it.
Workaround: Do not use the JMS destination to which the deleted Messaging Proxy Service was listening.
2.0
2.1
CR234549
CR232996
CR235638
Namespace Declarations May be Dropped if They are Only Declared at the <Envelope> Level And if They are Only Used in QName Values Such As xsi:type
Namespace declarations may be dropped if they are only declared at the <Envelope> level and if they are only used in QName values such as xsi:type. This problem prevents interoperating with encoded web services, either RPC encoded or Document encoded. In addition, this is a factor that causes problems in interoperating with .NET.
Workaround: Contact your BEA Customer Support Representative and request patch numbers CR234549 and CR232996 for AquaLogic Service Bus 2.0.
2.0
2.1
CR233092
The Reporting Module May Display Service Names in the $ Format in AquaLogic Service Bus 2.0
In AquaLogic Service Bus 2.0, the Reporting module stores and displays the proxy service and business service name in the global service name format:
Proxyservice$project$service
BusinessService$project$service
In AquaLogic Service Bus 2.1, the JMS Reporting Provider also stores the service name in the global service format in the database. However, it displays the service name in the project/service format to make it consistent with other AquaLogic Service Bus Console service display formats.
2.1
CR236402
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 "File cannot be moved from location <filename> to the stage directory. Current Process may not have permission to do this operation". These errors may occur while the file is copying. However, the file is processed successfully on the next polling cycle after the copy completes.
2.1
CR240463
An Exception Thrown by a Non XML Transformation at the Stage Level is Only Caught by the Service Level Error Handler
An exception thrown by a non XML transformation at the Stage level is only caught by the Service level error handler. For example, suppose a transformation occurs that transforms XML to MFL for an outgoing proxy service response message, it always occurs in the binding layer. Therefore, for example, if a nonXML output is missing a mandatory field at the stage level, only a service level error handler can catch this error.
2.1
CR240546
In AquaLogic Service Bus 2.1, the Implementation for the RPC-based Service Callout has Changed to Maintain the Integrity of Namespace and xsi:type Information
This is a backward-compatibility issue only in the following Service Callout cases:
It is RPC-style
The response uses simple types
The pipeline uses XQueries that depend on the fact that the response expects a string (that is, a string was returned in the response in the AquaLogic Service Bus 2.0 implementation of Web Service Callouts)
Workaround: When you use Service Callouts, change the XQueries that use the response and strip the element wrapper, such as using the fn:string() function.
2.1
CR241915
A Single Stand-Alone JMS Client Cannot Consume All Messages on Uniform Distributed Queues (UDQs) When the Default ForwardDelay is Set
The default ForwardDelay on Uniform Distributed Queues is set as -1. Consequently a single stand-alone JMS client is unable to consume all the messages on the UDQs.
Workaround: Manually set ForwardDelay to a positive number; for example, set it to 1.
2.1
CR245838
Using the Pass Through All Headers Option Causes an Exception When You Set an Inbound Response Header
When you use the Pass Through All Headers option, the Transport Header action in a request pipeline stage throws the exception "com.bea.wli.sb.pipeline.PipelineException: The outbound variable has not yet been initialized" when you set the header on inbound response in your configuration. This exception occurs because $outbound does not exist yet; therefore, there is nothing to pass through. The same exception is caused by using the copy-all option.
Workaround: Do not use the pass through options for setting inbound response headers when you are working in a request pipeline path. You may set it inside a Publish or Route node action, or in the response pipeline.
2.1
CR247821
Error Generated When You Import a Configuration File with a WSDL that References a Custom Policy Using an Implicit Policy
When you import an AquaLogic Service Bus configuration file with a WSDL that references a custom policy using an implicit policy URI (that is, an attribute of the form PolicyURI="policy:<policy-id>"), the following error is generated: "This resource has been manually updated outside the management API and the set of dependencies is out of sync."
For information about defining Web Service policies see "Web Service Policy" in Securing Inbound and Outbound Messages in AquaLogic Service Bus User Guide.
Workaround: In the Resource Browser, select the WSDL, and then edit, save, and commit the WSDL to resolve the <policy-id>. For more information, see "Viewing and Changing WSDL Details" in WSDLs in AquaLogic Service Bus Console Online Help.
2.1
CR251184
The Get All Headers Checkbox for a Proxy Service is Ignored Under Certain Conditions
The Get All Headers checkbox for a proxy service is ignored in two cases:
When the proxy service is calling another proxy service
When the test console is calling the proxy service
In both these cases, the headers are passed irrespective of the checkbox selection.
2.1
CR254608
A UIControlException Occurs for Users of the Monitor Role When They Attempt to Access the WebLogic Server Roles Portlet from the AquaLogic Service Bus Console
AquaLogic Service Bus uses the WebLogic Server Roles portlet for creating, viewing, and editing roles. However, WebLogic Server does not allow a user to view the portlet if the user is not a member of the WLS Administrator role. Because there is no filtering mechanism to disable the navigation portlet based on the role of the user logged in, AquaLogic Service Bus allows a user to view the WebLogic Server Roles portlet but generates a UIControlException.
2.1
CR254750
Publish to UDDI Intermittently Returns an Error When Publishing a Service to AquaLogic Service Registry
When you publish proxy services, you may receive an error on one or more of them with the message "CannotCreate Premature end of file encountered". However, the proxy services are correctly published, even though the error is reported.
Workaround: Use the AquaLogic Service Registry Business Service Console to confirm that the proxy services have been successfully published.
2.1
CR255246
Under Certain Conditions an Alert Rule may Fire if the Expiration of a Sample Interval Completes an Aggregation Interval
If you update an alert rule aggregation interval from tn1 to tn2, or create an alert rule with aggregation interval tn2, and one or both of the following conditions apply:
tn2 is the aggregation interval set for the service and the conditions specified in the rule has statistical metrics that are associated with the service.
There is a previous definition of an alert rule with tn2 as the aggregation interval and the conditions specified for this rule have statistical metrics that may be part of this newly created or updated rule
Then the alert rule will fire if the expiration of the sample interval for tn2 completes the aggregation interval.
For example, suppose the message-count (Service Level) statistics for a service is set with an aggregation interval of 10 minutes. Messages are being processed and statistics are being collected. Suppose you change the aggregation interval of an alert rule Rule 1 from 5 minutes to 10 minutes, and the conditions of Rule 1 specify that if the message-count > 0 (Service Level), then this rule will not fire from t1 + 10(where t1 is the time in which the aggregation interval was changed). However, because the aggregation interval for statistics being collected for the service is already set at 10 minutes, the alert rule may fire at t1 + tSI (where tSI is the time left to complete the sample interval); that is, whenever the sample interval for the 10 minute interval completes.
2.1
CR256408
JMS Transport Provider Does Not Support Certain Valid URLs
It is possible for more than one hostname to use the same port; the following example specifies a list of WebLogic Servers using the same port:
However, the JMS transport provider currently assumes that each hostname is followed by a port number.
Workaround: You can explicitly list the port number following the hostname.
2.1
CR256419
The Endpoint URL of a Service on AquaLogic Service Registry is Incorrect when the Endpoint URI of a Proxy Service Does Not Begin with a Forward Slash Character
The access point for a proxy service published to UDDI is malformed and looks like this: http://machinename:7001myProxyURI; it is missing the delimiter between the host:port and the path.
Workaround: When you create the proxy service, ensure that the value entered in the EndPoint URI field begins with the slash (/) character; for example: /myProxyURI.
2.1
CR256573
Under Certain Conditions, Trying to Import or Publish Services from/to a Registry Causes an Exception on the Console Page that Lists the Business Entities
If a business entity has a category bag with no keyed references and an empty keyed reference group, an exception occurs when trying to publish or import services from or to a registry.
Workaround: Log in to the Registry Console and remove any empty keyed reference groups (or add the desired keyed references to this group) for all business entities that have an empty keyed reference group. If no such business entities are found, please view the server log file for more information about this error.
2.1
AquaLogic Service Bus Security
Problem ID
Description
Found In
Fixed In
CR222177
Delete all Transport-Level and Service-Level Access-Control Security Policies Before Deleting a Proxy Service
Before you delete that service from AquaLogic Service Bus, you must delete all transport-level (HTTP and HTTPS) and service-level security policies associated with a proxy service. Failure to do so will leave the security policy in the authorization-provider database and potentially cause unexpected results and potential security vulnerabilities.
2.0
CR230663
Service Account Usernames and Passwords may be Recovered by Administrators
When using the built-in XQuery function fn-bea:lookupBasicCredentials, the username and password associated with a service account is sent in clear-text in the SOAP envelope. This risk is reduced by the fact that only AquaLogic Service Bus administrators can edit Proxy service message flows and deploy configurations to AquaLogic Service Bus.
2.0
CR231589
Inbound Web Service Security Limitation
2.0
2.1
CR234237
Inbound Web Services Security Authentication with X.509 Token Limitation
A bug exists in the client-side Web Service Security run time that 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 Configuring Security in Programming Web Services for WebLogic Server.
Insufficient Error Message if Mismatch Exists in the Encryption Key Between the Client Service and Endpoint Service
When encryption is used with Web Service Security between a proxy service and a business service, AquaLogic Service Bus retrieves the business service's certificate from the business service's WSDL in the WSDL repository. The certificate must be embedded in a WS-Policy that is inlined in the WSDL. It is possible for this certificate to get out-of-sync with the actual certificate used by the business service. In this case, the proxy service encrypts (with the wrong key) and routes the message to the business service. However, the business service is unable to decrypt the message. This scenario is difficult to debug. If the target service is a WebLogic Server 9.0 Web Service, you may get an error in the target server log that includes the following text:
<CertPathBuilder does not support building cert path from class weblogic.security.pk.IssuerDNSerialNumberSelector java.security.InvalidAlgorithmParameterException: [Security:090596]The WebLogicCertPathProvider was passed an unsupported CertPathSelector.
To help diagnose this type of error, retrieve a fresh copy of the business service's WSDL by dereferencing the <service>?WSDL URL or some other out-of-band method. Then, by comparing the base64-encoded strings in the fresh copy to the WSDL in the AquaLogic Service Bus WSDL repository, you can determine if the certificates match. To fix the problem re-import the WSDL into the WSDL repository.
Resolution: Improved error message now states:
Unable to resolve encryption key.
2.0
2.1
CR234481
If you Add or Delete a Security Provider, You Must Reboot the Server for the Security Changes to Take Effect
If you add or delete a security provider, you must reboot the server for the security changes to take effect. In particular, if you configure a new PKI credential mapper and fail to reboot the server, you will get an exception whenever you access any page in the Credentials section of the AquaLogic Service Bus. The Credentials section will be available again after you reboot the server.
2.0
CR234995
AquaLogic Service Bus Servers Must Have the Clear-Text Listen Port Enabled
AquaLogic Service Bus Servers are configured with a clear-text listen port by default. An additional SSL listen port can be configured. The clear-text listen port is required—do not disable it.
2.0
2.1
CR235062
Unbound JMS Service Account Leads to Continuous Run-Time Exceptions
When a service account is specified for a proxy service or business service to access the JMS server and/or JNDI lookup, you must first associate the service account with a username and password before invoking the service. Failure to do so results in AquaLogic Service Bus continually reporting the error as an exception. You can correct this problem in the AquaLogic Service Bus Console by assigning the username and password to the service account in the Credentials section of the Security Configuration module. The administration server does not have to be restarted.
You can correct this problem in the AquaLogic Service Bus Console by assigning the username and password to the service account in the Credentials section of the Security Configuration module. The administration server does not have to be restarted.
Note:
There are other conditions that can cause the same problem of continuous run-time exceptions. To avoid this problem again, we recommend that you configure JMS queues to have a limited number of retries.
2.0
CR236391
Warning Message Appears When Deploying a Web Application with CustomRolesAndPolicies Mode
The following warning message appears:
<Warning> <Security> <BEA-090866> <The deployment of an unchecked policy for the resource "type=<url>, application=XBus Kernel, contextPath=/someproxyuri, uri=/" has been ignored. Unchecked policy is the default policy for URL and EJB resources. An unchecked policy can result if a deployment descriptor specifies a transport guarantee without the use of an authorization constraint.>
This warning appears when creating HTTP/S proxy services (when submitting the session) and during server startup when the HTTP/S proxy services are initialized. This warning is harmless. Access control for proxy services is configured through the AquaLogic Service Bus console, not through deployment descriptors.
2.1
CR245178
Service-level (WSS) Access Control Changes May Require Adjusting Policies to Ensure Proper Access
In AquaLogic Service Bus 2.1, two changes have been made to the service-level access control policy:
Service-level access control is now invoked on all WSS requests (after WS-Policy is successfully enforced), regardless of whether the WS-Policy specifies an identity assertion. In 2.0, service-level access control was only invoked if the WS-Policy specified an identity assertion, access control was not invoked if there was no identity assertion.
In 2.1, the default behavior for service-level access control (that is, when no service-level access control policy has been explicitly assigned to the proxy service) is to allow access to all users. In 2.0, the default behavior was to deny access.
Web Service Security over JMS Fails when doing Authentication
WSS authentication over JMS fails with exception error.
Workaround: None.
In some cases, depending on various configuration settings, WSS authentication relies on the use of timestamps. It is hard to adequately configure the timestamp validity duration and other timestamp properties to guarantee successful processing of legitimate requests in a WSS over JMS scenario.
Note:
BEA recommends you do not use WSS authentication over JMS.
2.1
CR249194
Web Service Security UsernameToken without Password must be Digitally Signed
Web Service Security username tokens can be used in various ways. The token may include a username and password or just a username. When a username token is used without a password, the Web service security runtime will only accept it if it is covered by a signature. If the token is not signed, the runtime will reject it. The configuration-time WS-Policy validator does not enforce this restriction in this release.
2.1
CR249627
AquaLogic Service Bus 2.1 does not Support WS-Policy on SOAP Fault
2.1
CR249965
After Moving a Service Account to a New Location, its username/password is no Longer Mapped
If you move an existing service account to a new location or rename the service account, the associated username/password is missing.
Workaround: Before you move or rename a service account, you must first delete its username/password credential. After you move or rename the service account, assign it the username/password again.
2.1
CR250184
The Test Console Fails when Testing a Proxy Service with Inbound SAML Policy
It is not possible to test a proxy service with an inbound SAML policy in this release.
2.1
CR252942
Server Runtime Error for Encrypted SAML holder-of-key token
Server-side run time error results while decrypting the SAML token for a Web service with WS-Policy in which the policy specifies SAML holder-of-key token for identity+encryption of this token.
2.1
CR253683
Changing PSP Encryption Credentials Causes Stale Dynamic WSDL
Anytime the encryption credential assigned to a proxy service provider is modified, the proxy service must be redeployed for the new credential to take effect.
This limitation only influences a dynamic WSDL, which affects clients that dynamically retrieve the WSDL, as well as the test browser.
Note:
This does not affect the run time. The run time picks up the new credential immediately.
Workaround: Create a session, do a dummy edit of the proxy and submit the session. This causes the dynamic WSDL cache to be flushed. Restarting the server also solves the problem.
2.1
CR254018
Incomplete Test Service Validation of Security Configuration for SAML Holder-of-Key Outbound Service.
When testing a business service that has an Integrity assertion with a SAML holder-of-key token, the user must specify both a service provider and a username/password. If either one is missing, the test service is unable to invoke the business service.
If you do not specify a username/password you get this error message:
Error Invoking Test Service - <service name> Error applying WS-Security to the SOAP message: null
If you do not specify a service provider you get this error message:
Error Invoking Test Service - <service-name> The service requires a digital signature, you must specify a service provider
2.1
CR255199
Security Interoperability Tests using X509 Token from WebLogic Workshop 8.1 SP4 Service Control to ALSB 2.1 is not working
The following interoperability scenarios fail:
AquaLogic Service Bus (ALSB) calling a Business service, based on Workshop Web Service, set with a security policy as Signature required on the input. The Business service is created from a WSDL with the OOTB Sign policy.
A Workshop Web Service calling an AquaLogic Service Bus proxy service via a service control. The Web Service control has the signature on outgoing request. The AquaLogic Service Bus proxy service has the OOTB Sign Policy set on the request.
A Workshop Web Service calling an AquaLogic Service Bus proxy service via a service control. The Web Service control has the signature on outgoing request. The AquaLogic Service Bus proxy service has a custom sign policy which requires only the body to be signed on the request.
2.1
CR255331
Some WS-Policies Fail to Show Up in Dynamic WSDL
In AquaLogic Service Bus 2.1, you bind ws-policies to services by adding annotations to various WSDL constructs. This is commonly referred to as "WS-Policy attachment". Some WS-Policy attachment points do not work correctly. AquaLogic Service Bus 2.1 supports attaching ws-policies to the following elements:
If you attach a WS-Policy to any WSDL construct other than the previous ones, the WS-Policy will be effective at run time, but it will not be included in the dynamic WSDL.
2.0
CR255331 (continued)
To attach a WS-Policy to these elements, add a nested wsp:Policy element. The Policy element may have an embedded wsp:PolicyReference. For example:
Workaround: Make sure you attach all policies on the supported WSDL constructs.
2.0
CR256146
After Renaming or Moving a Proxy Service Provider, its PKI Credentials are Lost
If you move a proxy service provider to a new location, or rename the proxy service provider, the associated PKI credentials are no longer mapped.
Workaround: Before you move or rename a proxy service provider, you must first delete its PKI credentials. After you move or rename the proxy service provider, re-assign the PKI credentials.
2.1
CR256282
Intermittent Web Service Security Timestamp Validation Errors: "Message is too old" or "Message Created time in the future"
A bug in the Web service security runtime causes intermittent timestamp validation errors when the message age is short and clock precision is specified. When this happens you will get one of these error messages in server stdout:
'Message is too old' 'Message Created time in the future'
If you suspect you are having this problem, contact your BEA representative and request a patch for CR251516.
2.1
AquaLogic Service Bus Interoperability
Problem ID
Description
Found In
Fixed In
CR205484
Problems Using the WebLogic Workshop JMS Control to Send Messages to a Queue in Another Domain
A problem exists when using a JMS Control to send and receive messages to and from remote queues on a server in a WebLogic 8.1 domain. If your use case requires this functionality, contact your BEA Customer Support representative and request patch number CR205484.
Workaround: Use WLI Event Generator for cross-domain JMS receives to WLI. See the following resolution for sending messages from a JMS Control.
Resolution: The issue of sending a message from a JMS Control is fixed in WebLogic Workshop 8.1 SP4.
WLW 8.1 SP4
WLW 8.1 SP4 (SEND only)
CR214028
Enabling WebLogic Server 8.1 JMX Interoperability with AquaLogic Service Bus 2.0
To achieve full interoperability between WebLogic 8.1SP4 domains and AquaLogic Service Bus 2.1 or WebLogic Server 9.0, the following patch is required for WebLogic Platform 8.1SP4: CR214028. Contact your BEA Customer Support representative and request the patch number CR214028.
Resolution: Issue fixed in WebLogic Server 7.0 SP7 and 8.1 SP5.
WLS 7.0 SP7
WLS 7.0 SP7 & WLS 8.1 SP5
CR225422
Routing to External Web Service Raising Fault "no SOAPAction header"
A Business service for an external web service is configured as a SOAP Service by providing the URI of the external web service. When a method is called on the proxy service using a standalone web service client, a fault is raised saying "no SOAPAction header".
Resolution: Issue fixed in WebLogic Server 9.1.
WLS 9.0
WLS 9.1
CR227283
WSDLs Generated for XML Web Services in WebLogic Workshop Cannot be Used in AquaLogic Service Bus
Because of a problem retrieving the correct part name and therefore the expected schema type of the message from WSDLs generated for XML Services in WebLogic Workshop, you cannot use these WSDLs in AquaLogic Service Bus.
Workaround: Use a SOAP Web service to generate the WSDL or edit the WSDL generated by WebLogic Workshop from the XML Web service before using it in AquaLogic Service Bus. Replace <mime:mimeXml part="Body"/> with <mime:mimeXml />.
Resolution: Issue fixed in WebLogic Workshop 8.1 SP5.
WLW 8.1 SP4
WLW 8.1 SP5
CR229661
Problem Sending SOAP 1.1 Attachments From AquaLogic Service Bus 2.0 to WebLogic Workshop 8.1 Services
A known problem exists when sending SOAP 1.1 attachments from AquaLogic Service Bus to WebLogic Workshop 8.1 Web Services—the javax.activation.DataHandler always returns null.
Resolution: Issue fixed in WebLogic Workshop 8.1 SP5.
WLW 8.1 SP4
WLW 8.1 SP5
CR235638
XBeans Do Not Preserve Namespace Declaration for Prefix used in QName Values
XBeans seem to handle QName values (of attributes and elements) as strings. This creates a problem if a namespace declaration is used only for QName values and not for elements, as XBeans will sometimes drop the namespace declaration entirely.
Possible issues also exist with the prefix being changed in the declaration and the QName values not being updated.
Resolution: Issue fixed in WebLogic Server 9.1.
WLS 9.0
WLS 9.1
CR235863
Reverting the Code Workaround for not Preserving Namespace Declaration for Prefix used in QName Values
This reverts the workaround applied previously with CR235638.
Resolution: Workaround code added to ALSB 2.0 has been removed in ALSB 2.1 because of the resolution available in WLS 9.1 for CR235638.
ALSB 2.0
ALSB2.1
CR251398
Tools->Import->EDI Importer Menu Does Not Come Up Due to XSLT Parser Incompatibility
The EDI Importer tool does not come up due to XSLT parser incompatibility.
ALSB 2.1
AquaLogic Service Bus Console
Problem ID
Description
Found In
Fixed In
CR222586
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.
Workaround: Linux requires the X11 modules installed as a precursor to the installation of AquaLogic Service Bus. Isolate the libraries required for installing the X11 toolkit or the native graphics library for Linux. You can fix this problem by setting the proper "DISPLAY" environment variable.
2.0
CR222851
After Clicking a Link within the AquaLogic Service Bus Console, if You Click a Second Link before the First is Done Loading, the Console Throws an Exception
Workaround: Allow the current page to finish loading before clicking another link.
2.0
CR222870
Your Browser Continues to Display the Same Page When You Click Save on the View Policy Details Page for Transport Access Control Policy or Service Access Control Policy
When you click Save on the View Policy Details page for transport policies or service policies in the Security Configuration module, your browser continues to display the same page instead of returning to the Access Control for Proxy Services page.
Workaround: From the left navigation pane, select Access Controls from under Security Configuration. The Access Control for Proxy Services page is displayed. You can also click a navigation link on the top of the page, then navigate to the Access Control for Proxy Services page.
2.0
2.1
CR227616
Only WebLogic Server Administrators Can Define Access Control Policies
Only users in the WebLogic Server built-in Administrator role are allowed to manage access control policies on AquaLogic Service Bus 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 AquaLogic Service Bus Console as the WebLogic Server Administrator and select Access Controls in the Security Configuration module.
2.0
CR230763
Deleting An Alert May Not Immediately Reduce the Alert Count on the Alert Summary Page
When you delete an alert in the Monitoring module, the alert count on the Alert Summary page may not be immediately reduced. This behavior is seen in situations where a large number of alerts are being generated. The reason for this is when an alert is generated, the data record is stored in a memory cache before it is written to a repository after a time interval. When you delete an alert on the console, the alert record is marked in the memory cache for deletion in the alert repository. Because there is a delay in flushing out this marked record to the repository from memory cache, the deleted alert is displayed on the console until it is flushed from the memory cache.
Workaround: Refresh the console after you delete the alert. After 2-3 minutes, the deleted alert is no longer included in the alert count.
2.0
2.1
CR230873
Blank Page Displayed When An Invalid Selection is Made for the Purpose of a Credential
A blank page is displayed when you make an invalid selection in the Purpose of this Credential dropdown list in the Credentials section of the Security Configuration module.
Workaround: Click the Back button in your browser, then make a different selection in the Purpose of this Credential dropdown list.
2.0
2.1
CR231616
Request Encoding Value is Required for JMS Proxy Services
It is not necessary to specify a value in the Request Encoding field for JMS proxy services that send TextMessages. The default for text/XML proxy services is UTF-8. However, for inbound request, a JMS proxy service may receive a Bytes or Text message. Because a proxy service may receive BytesMessage, encoding information is required to correctly interpret those bytes. To avoid this problem, BEA recommends that you use one that is Unicode-based such as UTF-8 or UTF-16.
2.0
2.1
CR233186
The Start and End Times Must Be At Least One Minute Apart When You Filter Messages in the Reporting Module
When you use the search filter to retrieve or purge messages in the Reporting module, if you specify the same start and end times to filter messages for a specific minute, the search filter returns zero messages even if there are reporting messages with that timestamp. For example, if you specify 7.10pm as the start and end time, the search filter does not return the messages that are marked with that timestamp. The reason for this issue is that messages are persisted in the database with timestamps up to the second, whereas on the AquaLogic Service Bus Console the messages are displayed with timestamps up to the minute only.
Workaround: Specify the end time at least one minute after the start time. For example, if you specify the start time as 7.10pm and the end time as 7.11pm, then the search filter returns all messages that are marked with a timestamp from 7.10pm up to but not including 7.11pm.
2.0
CR234094
Fewer Message and Alert Counts May Be Reported After A Managed Server Is Restarted
In the event that a managed server in your cluster is stopped and then restarted, fewer message counts and alert counts may be displayed in the Dashboard Monitoring Summary page than were displayed before the managed server went down. Because only statistic summary information is written to disk and recovered after a failure, it is necessary to approximate some of the data during the server restart. This can result in the slightly reduced counts. The accurate counts are available again after a full aggregation interval has elapsed.
2.0
2.1
CR235412
CR234878
The Expiration Date for Alert Rules Only Accepts the Last Two Digits of the Year
The Rule Expiration Date field on the New Alert Rule - General Configuration page has a format of MM/DD/YY. If you enter a four digit number for the year, it is persisted correctly and the rule is evaluated correctly against the entered date. However, the AquaLogic Service Bus Console interprets only the last two digits of the date entered and can incorrectly flag the rule as Expired. Therefore, an expiration date entered as 12/21/2100 is interpreted as 12/21/00 and marked as Expired in the AquaLogic Service Bus Console even though the rule is evaluated correctly at run time.
Reference CR235412
Additionally, if you enter a two digit number for the year and the entered date occurs in the past, the date is correctly displayed as Expired in the AquaLogic Service Bus Console but is incorrectly persisted as belonging to the next century and the rule is not considered expired at run time. For example, a date entered as 06/28/05 is correctly displayed as Expired in the AquaLogic Service Bus Console but incorrectly persisted as 06/28/2105 for run-time evaluation.
Reference CR234878
2.0
2.1
CR235004
Web Service Security Errors Not Counted by Message Error Counter
If a WS-Security error occurs for a business service, it increments only the security error count on the Service Monitoring Details page and is not counted in the overall error counter. This means that the displayed success rate is higher than it should be because the WS-Security errors are not taken into account.
2.0
2.1
CR235005
When You Restart Managed Servers in a Cluster the Server Summary Panel May Not Display a Managed Server on Which an Aggregation Server is Deployed
In the event that managed servers in a cluster are stopped and then restarted, a managed server on which an aggregration server is deployed may not be displayed on the Server Summary panel on the Dashboard.
Workaround: First, shut down the managed servers, then shut down and restart the Administration Server, followed by the managed servers. The Server Summary display will then include the managed server on which the aggregation server is deployed.
2.0
2.1
CR235011
No Visual Indication that an Alert Rule Set to Fire "Once Until Condition Clears" is Occurring if the Condition is Still True After a Long Period of Time
When you configure an Alert Rule to fire Once until Condition Clears, an alert is fired the first time the condition is true and does not fire again until the condition is reset and evaluates to true again. The timestamp for the alert (the date and time that the alert occurred) remains the same. Therefore, in cases where the condition remains true for several hours or maybe days, the single alert generated for the condition moves down the Alert Summary list on the Dashboard, leaving no visible indication that the alert is still occurring.
2.1
CR236033
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 AquaLogic Service Bus Console
The default Internet OptionsSecurity Settings for Windows 2003 Server are set to High, which disables active scripting. This causes a browser error when you click a link in the left navigation pane of the AquaLogic Service Bus Console.
Workaround: Modify the Internet OptionsSecurity Settings to Active Script: Enable. Because AquaLogic Service Bus uses JavaScript in the console pages, make sure JavaScript is enabled in your browser.
2.0
CR248068
Providing An Invalid Filename In The Test Console results in a JavaScript Error
When using the XQuery/XPath Expression Test Console with Internet Explorer on Windows XP, if you provide a filename that does not exist, you receive a JavaScript error. This is a known limitation in Internet Explorer introduced in Windows XP SP2 (http://support.microsoft.com/default.aspx?scid=kb;en-us;892442).
Workaround: None. It is suggested to always use the Browse button to select files to ensure valid file names.
2.0
CR248432
You Must Manually Edit The JMS URI from the WSDL When You Register a JMS Business Service
When you register a JMS business service in AquaLogic Service Bus, you must manually edit the URI from the WSDL file when adding it to service definition. The URI format is as follows:
When using Service Monitoring Details in the AquaLogic Service Bus Console, the Success Ratio plus the Failure Ratio may not equal 100%. There may be a +/- 1% margin of error when reporting these success and failure ratios.
2.1
CR253979
The Endpoint URL in the Dynamic WSDL
In a clustered domain, when generating the dynamic WSDL, AquaLogic Service Bus rewrites the endpoint URL based on the server or cluster configuration. If a front-end HTTP host/port (or a front-end HTTPS host/port for HTTPS endpoints) has been specified, it will be used; otherwise, the managed server host or port will be used. It is strongly advised that a front-end HTTP or HTTPS host/port is assigned in clustered domains.
2.1
CR254231
Alert Rules Are Replaced with Newly Imported Rules
Importing an alert rule with the same ID as an existing alert rule that is associated with a different service results in inconsistent alert rule behavior.
Workaround: You should not import configurations that have alert rules with the same alert rule ID but associated with different services.
2.1
CR255038
Alerts Do Not Fire In a Cluster Environment when One Server's Interval Has Expired and the Other Server's Interval Has Not Expired
The Alert queries currently only take into account data set for which the aggregation interval has expired. Therefore, in a cluster environment, valid data present in node could potentially be ignored on a server whose interval has not expired. This happens only at server start and only for the first aggregation interval of the server who is yet to receive data when one server has already received data and the sampling cycle has started while the other server's sampling cycle has not started.
2.1
CR255059
404-Not Found Message Appears If English Version Is Used In Japanese, Korean or Simplified Chinese Browser
If the English version of AquaLogic Service Bus is installed for use within a browser whose language is set to Japanese, Korean, or Simplified Chinese, a 404 message appears when a user clicks the More Info button within the console.
Workaround: Install a localized version or set the browser's language to English ('en').
2.1
CR255571
Wildcard Searches within User Management Do Not Work if Wildcard is Placed before Text
Within the User Management page of the AquaLogic Service Bus Console, wildcard searches do not work when the wildcard precedes the text. For example, "*de".
Workaround: When using wildcards in searches, the wildcard character must be at the end of the text. For example, "de*".
2.1
CR255685
Duplicate Alerts Are Generated Under Certain Conditions in a Cluster Environment
When you operate in a cluster environment, if you have a short aggregation interval set for a service and a much longer aggregation interval set for the alert rules defined for this service, it is possible that you can receive duplicate alerts for the same alert aggregation interval period. This occasionally occurs if the alert timers running in the managed servers become unsynchronized because of the individual server start timings.
2.1
CR256432
Proxy and Business Services With Same Name in Same Folder Create Alert Problems
If services (regardless of type) that reside in the same folder have the same name, alerts do not function properly.
Workaround: Ensure that services that reside in the same folder have unique names.
2.1
BEA WebLogic Server Administration Console
Problem ID
Description
Found In
Fixed In
CR227120
Ensure that You Select the `Use Default User Name Mapper' Option When You Configure a Default Identity Asserter in the WebLogic Server Administration Console
To generate a vaild config.xml file, you must specify the Use Default User Name Mapper option when you configure a DefaultIdentityAsserter from the following page in the WebLogic Server Administration Console:
If you do not select the Use Default User Name Mapper option, you must have specified the User Name Mapper Class Name.
Workaround: If you set neither the Use Default User Name Mapper nor the User Name Mapper Class Name option, you can fix the problem at run time as follows:
Shut down the Administration Server.
Manually edit the config.xml file and set the Use Default User Name option to true.
Start the Administration Server.
Log on to the WebLogic Server Administration Console and configure the identity asserter correctly.
2.0
BEA XQuery Mapper
Problem ID
Description
Found In
Fixed In
CR222617
Pasting Expressions in the Expression Boxes in Constraint View Causes Error
When expressions are pasted in the left-hand or right-hand expression box in the Constraints view, a compilation error occurs.
Workaround: Instead, type expressions in the left-hand or right-hand expression box.
2.0
CR223103
Undoing a Delete Operation of a Disabled Node Link Does Not Bring it Back
Disable a Target Node, which has a mapped link. Delete the mapped link of the disabled node. Now hit the Undo button in the XQuery Mapper. The Disabled Target Node link is not retrieved back. It is lost.
Workaround: Press CTRL Z a few times and the Undo will happen.
2.0
CR223388
For a Recursive Element, in Test View, Source Data is Not Properly Generated
The generated data for a recursive element is empty. Therefore, when you use such a generated recursive element, the resultant data is empty in the Test View on Run too.
Workaround: Correct the generated data and then run the Query.
2.0
CR225324
Property Editor is Not Displaying the Properties of Variables in the Expression Variable Pane
The Property Editor does not refresh to display the properties for a variable when a variable is clicked in the Expression Variable pane—unlike the Design view nodes.
Workaround: You can obtain the property by hovering the mouse over the variable in the Expression Variable pane.
2.0
2.1
CR225380
Closing and Relaunching of Expression Variable Pane Does Not Refresh with the Current Variables in the File
Open an XQuery file. Now close the Expression Variable pane alone by clicking the "x" button in it, and then relaunch the view. The view is blank and does not display the variables of the current XQuery file.
Workaround: Click on any target node in the Design view to refresh the Expression Variable pane.
2.0
2.1
CR225672
Design View Is Not Able to Recover a Namespace Change
If an XQuery file is kept open while the schema files (used in the XQuery file) are modified with namespace changes, the Design view is not able to recover if the user switches to this view.
Workaround: Close the XQuery file and reopen the XQuery file after refreshing the project.
2.0
CR225715
MFL Data Testing Unnecessarily Mandates the Availability of Unused XML Files
When the transformation file involves both XML and non-XML schema as inputs—even if the XML schemas are not mapped for output—testing of such transformation requires both the XML and MFL (non-XML types) source data to be available in order to perform testing. However, this is not the case with XML-only transformations.
2.0
CR225903
Result Data is Incorrect When Join Links Exist Between Non XML Files
The resultant data for a non-XML element is not correct when there is a join link. When the join link is removed, the resultant data is generated properly.
2.0
CR226069
If-Then-Else expression is Not Displayed When Target Node is Selected
When there is a If-Then-Else expression for a target node, that expression is not displayed when you click on the target node. However, this problem only occurs the first time the XQuery file is open and the node is selected.
Workaround: Click on any target node, then click on the required target node.
2.0
CR227845
The Signature of Built-in XQuery Functions Is Not Updated to the Latest Signature in the User Interface
For some built-in functions, XQuery Mapper still displays the signature based on the 2002 XQuery specification instead of the 2004 XQuery specification.
2.0
2.1
CR231623
Generate Data Generates Data for All the Choices
A choice element accepts only one data choice among the many choices at a given time. In the Test view, when you select Generate Data, data is generated for all the cases of a choice element. So a validation error occurs when data is generated for the choice element.
Workaround: Delete all elements except the one for which you wish to generate data.
2.0
CR234550
Problems Opening Large XQuery Files in the Test View
The XQuery Mapper may hang, displaying the following message when attempting to open large XQuery files in the Test view: "Initializing... Please wait."
Workaround: Close the XQuery file and reopen it. Do not switch views while the file is being opened.
See CR250692
2.0
CR234559
XQuery Mapper Online Help Example Document Displays Incorrect Output Data
Changing a Join Condition from OR to AND Works Intermittently
In Eclipse, click on a target node item and right-click on any OR; then select Change Join condition to And in from the pop-up menu. Nothing happens.
Note:
This problem does not always occur. It is an occasional bug.
2.0
CR234891
Convert Data Link to Structural Link Option is Missing From Copy Link Right-Click Menu
When you right-click on a copy link, the Convert Data Link to Structural Linkoption is missing in the right-click menu options.
Workaround: Delete the copy link and create a link between one of the child-child elements. Now, create a link between parent-parent element, which will be a structural link and then delete the child-child link.
2.0
CR234961
Code Not Displayed After View Code Option is Selected From Copy Link Right-Click Menu
When you right-click on a copy link and select the View Code option, the associated code is not displayed in Source view.
Workaround: Click Source tab to manually switch to the Source view.
2.0
CR250692
Mapper Exits Abruptly While Creating a New XQuery Transformation with a Large Schema
Unable to open an XQuery file in XQuery Mapper, when the file contains many inputs and is used in conjunction with a large schema.
Workaround: Limit the number of inputs in the schema.
2.1
CR252888
Unable to Create Copy Link While Doing Non-XML to XML and XML to Non-XML Data Transfer
While doing data transfer from Non-XML to XML and XML to Non-XML, the copy link is not created even when the data structures at both source and target types are similar.
Workaround: Create a link between parent-parent element. Right-click on this link and select the Induce Map option.
2.1
CR252895
Unable to Validate Date Format for Non-XML Result Data During Execution
In Test view, the date format is not being validated if the result is non-XML This is specific to XML to non-XML transformation.
2.1
CR252944
Namespace Prefix Not Generated When Target is Non-XML
When the target is non-XML, target namespace prefix is not generated properly in the XQuery source. This causes an error while executing the XQuery in Test view.
Workaround: In Source view, specify the target type in element() of the main XQuery function and add the namespace prefix for each of the target elements.
