Documentation for all BEA products, including ALSB documentation, is available on the BEA Product Documentation Web site.
About ALSB
ALSB is an enterprise-class service bus that connects, manages, and mediates interactions between heterogeneous services. ALSB accelerates service configuration, integration, and deployment, thus simplifying management of shared services across the SOA.
ALSB 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, ALSB can be used horizontally across many applications and systems, potentially spanning service implementations built by different teams in different departments. ALSB 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.
Access to IBM WebSphere MQ Using the Native MQ Transport
ALSB supports access to IBM WebSphere® MQ using the Native MQ Transport. The Native MQ transport provides access to WebSphere MQ version 5.3 and 6.0. MQ proxy services can receive messages from WebSphere MQ and MQ business services can route messages to WebSphere MQ.
ALSB 2.6 RP1 supports Java variables and message types. You can invoke custom Java code from within proxy services.
ALSB supports a Java exit mechanism via a Java Callout action that allows you to call out to a Plain Old Java Object (POJO). Static methods can be accessed from any POJO. The POJO and its parameters are visible in the ALSB Console at design time; the parameters can be mapped to message context variables. For more information, see Extensibility Using Java Callouts and POJOs.
ALSB 2.6 RP1 also supports the ability to define dependencies between different JAR resources.
Access to ERP Systems Using ERP Transports
ERP transports allows the exchange of real-time business data between ERP systems and ALSB.
ALSB 2.6 RP1 supports the following ERP transports:
BEA SmartConnect 2.6 for SAP, which can be used to exchange data between SAP Enterprise Central Component (ECC) 5.0/6.0 systems and ALSB. This transport provides:
Support for bidirectional message interactions.
SAP object repository metadata browsing support to build WSDLs.
Support for Remote Function Call (RFC), Business Application Programming Interface (BAPI), and Intermediate Document (IDOC) interfaces to SAP.
BEA SmartConnect 2.6 for Siebel, which can be used to exchange data between instances of Siebel systems and ALSB. This transport provides:
Support for bidirectional message interactions.
Siebel object repository metadata browser support to build web services to handle business service requests or event data.
Support for Integration Objects and Business Objects.
Secure File Transfer Using SFTP Transport
The SFTP transport allows you to transfer files over SSH File Transfer Protocol (SFTP) using SSH version 2.
This poll-based transport supports three methods for authentication—password, public key, and host-based. After authentication, connection is established between ALSB services and the SFTP server for secure file transfer. This transport allows you to create ALSB business and proxy services.
For information about ALSB 2.6 RP1 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 AquaLogic Service Bus Interoperability Support Matrix.
Data Transformation Tools
Two data transformation tools are installed when you install ALSB and Workshop for WebLogic—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.
For up-to-date information about patches, contact your BEA Customer Support representative. For information about known limitations in ALSB 2.6 RP1, see Known and Resolved Issues.
Upgrading Previous Versions to ALSB 2.6 RP1
ALSB 2.6 RP1 supports in-place domain upgrade from ALSB 2.6, and migration upgrade from ALSB 2.1 and ALSB 2.5.
The following sections describe known problems in ALSB 2.6 RP1, as well as problems that were resolved in 2.6 RP1. 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 exception occurs when a Java Callout passes an array parameter that contains only one element.
Workaround: Contact BEA Support for a fix to this problem.
2.6 RP1
CR346977
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.
You can safely ignore these exceptions.
2.6 RP1
CR345936
Connection error occurs when MQ Server is running under stress condition.
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.
Workaround:
In ALSB:
Assign each MQ transport-based business or proxy service to a dedicated dispatch policy using the ALSB Console (or user-defined Work Manager in the WebLogic Server Console). Set max-thread-constraint of each Work Manager to a number that is equal to or larger than the number of concurrent calling clients.
Set the MQ Connection Pool Size to No-Limit (value of 0); this value is a field of MQ Connection resource in the ALSB Console.
In MQ Server:
Apply IBM's Fixpack 12 to the MQ server 5.3 installation.
Set MaxChannels and MaxActiveChannels of the MQ Queue Manager to 5000.
2.6 RP1
CR343122
The test console does not display the response for an indirect call to an MQ request/response proxy service.
When you test a MQ request/response proxy service with an indirect call, the response is retained in the response queue, but not displayed in the Test Console.
2.6 RP1
CR342056
The following JNDI and JMS resources are secured in ALSB 2.6 RP1 and only users in ALSBSystem role or Admin role can access them:
Blank fault variable is created if there is an error from Publish action.
The fault variable is populated if an XQuery function is set explicitly in the Request actions of the Publish action, but the fault variable fails to get populated if a Raise Error action is used in the Publish action.
This problem has been resolved. Now fault variable populates the proper error information from the Publish action.
2.6
2.6 RP1
CR335566
SOAP Fault is not correctly generated from EJB exception in EJB Transport.
When EJB is called from ALSB using EJB Transport and if EJB method throws an exception, ALSB does not generate the SOAP Fault element correctly.
This problem has been resolved. The SOAP Fault is now properly populated with user exception field values.
2.6
2.6 RP1
CR334827
Relative URI in outbound variables is not working.
This problem has been partly resolved. Business Services can now handle relative-URIs when not used simultaneously with query-strings.
2.6
2.6 RP1
CR334818
Invoking a proxy service with a file transport places the file in Error directory when the Redelivery Limit attribute is set to 0 for wlsb.internal.transport.task.queue.file queue.
When you set the Redelivery Limit attribute of message producer to 0 on the JMS queue, the following issues are noticed after executing a request on Proxy Service:
The file to process in the Entry directory is placed in the Stage directory
At the end of the process, the file is placed in the Error directory instead of the Archive directory.
An error is thrown indicating that the file or directory does not exist.
These issues have been resolved.
2.6
2.6 RP1
CR334771
When a security policy is implemented on an ALSB proxy service and when you invoke the proxy service from a web service client, the client times out instead of receiving AccessNotAllowedException.
This problem has been resolved. Now in the case of AccessNotAllowedException, the client gets the error response immediately instead of timing out.
2.6
2.6 RP1
CR329464
Messages are dropped intermittently on JmsAsyncResponseMDB.onMessage() call.
In a JMS outbound business service request/response scenario using JMS Message ID, JmsAsyncResponseMDB.onMessage() receives a message with an unknown JMS Message ID and the message is dropped.
This problem has been resolved. The response message is processed properly.
2.6
2.6 RP1
CR328211
When a SOAP document is returned to a proxy service and if there are multiple proxy services in the return path, the SOAP body content is lost in the response document.
Workaround: Add a log statement in the Response action of the route node at which the proxy service is calling the external service.
This problem has been resolved. The SOAP body content no longer gets lost and it returns to the proxy service.
2.6
2.6 RP1
CR318151
Ability to set the message type for JMS messages.
There was no method in ALSB to dynamically route a JMS message from an incoming destination to an outgoing destination which allowed the message type to pass through.
This problem has been resolved. An optional element named message-type is added to the JmsRequestMetadata element of the JmsTransport schema. Options available for this element are "Text" and "Bytes". If this element is present, the indicated message type overrides the statically defined message type in the outbound message for the service.
2.6
2.6 RP1
CR306913
You cannot use a Converter JAR with an EJB business service on UNIX platforms.
When an EJB transport-based business service uses a Converter JAR, a ClassNotFoundException occurs for the home interface.
Workaround: None.
2.6
CR306203
If the dispatch policy for a poller-transport service is set to "default" or the managed server hosting the poller is unset, and a new config.jar is imported with either of these properties set, and "Preserve Environment Values" is set, these values will get overwritten.
2.6
CR306124
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.
If you create a new SLA alert and subsequently move it relative to the other SLA alerts for a service (using the reorder feature in the table containing the alerts in the ALSB Console) your new alert may not fire.
Workaround: Edit and save the new alert after you move (reorder) it in the list of alerts. The alert will then fire when the service level violation occurs.
2.6
CR289750
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.
Workaround: You must edit and save the business service in the ALSB Console. This forces a redeploy.
2.6
CR304246 CR302531
A monitoring run-time exception can occur at startup for managed servers if activation notifications reach different managed nodes at different times
The exception is similar to the following:
Failed to initialize statistics data structure after checkpoint #### due to java.lang.Exception: [WLI-Monitoring Runtime:473230]Aggregator rejected statistics reported by server <managerserver> with tick #### because the server snapshot version xxxx is not compatible with current snapshot version yyyy
Workaround: This is an intermittent error on startup and can be ignored. It does not affect alerts firing or statistics gathered. Note that when a managed server recovers, checkpointing is stalled until the activation notifications are complete.
2.6
CR304053
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.
2.6
CR286324
The following combination is not supported for Email transport- based services: IMAP + HMail server + attachments.
2.6
CR298797
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).
Note also that ALSB 2.5 can accept WSDLs with SOAP 1.2 binding. SOAP 1.2 is not supported in ALSB 2.5 however and therefore these WSDLs will not work in your 2.5 configuration.
2.6
CR335565
A NullPointerException is thrown during MFL transformation both in Format Builder and in ALSB.
This problem has been resolved.
2.5
2.6 RP1
CR335564
HTTP proxy response does not contain Content-Length in the header.
Some HTTP messages are sent in one piece with a Content-Length header to give their length, while other HTTP messages are broken up and sent in chunks with no Content-Length header. The ALSB HTTP transport always sends responses in chunks with no Content-Length header, even if the user adds such a header in the response pipeline. See “Understanding How the Run Time Uses the Transport Headers' Settings” in Proxy Services: Actions in Using the AquaLogic Service Bus Console.
This problem has been resolved. The ALSB HTTP transport enables sending the response in one piece so that WLS can automatically calculate and set the Content-Length header on the response message.
2.5
2.6 RP1
CR294946
If the JMS destination for a proxy service is a topic and resides on a migratable target, you may get a "duplicate client ID" error when deploying the proxy service to a cluster
Workaround: When you specify the "Durable" setting for the proxy service, you can also specify a target. The target setting is, by default, cluster. Change it to specify a single managed server. Select the managed server which has the distributed destination member pointed to by the JMS URL.
2.5
CR275840
Due to class incompatibility issues, classes in a JAR file matching a certain pattern are invisible, and will not be available for use in a Java Callout.
Specifically, all classes whose names end with 814_WLStub and 815_WLStub will be invisible. These classes are stubs autogenerated by WebLogic Workshop versions 8.1.4 and 8.1.5.
2.5
CR268692
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.
For example:
A message that is to be processed by proxy service A will route to proxy service B.
Proxy service A retrieves service information for proxy service B.
Proxy service A and the MFL or WSDL for proxy service B are updated while step 2 is in progress.
Proxy service A retrieves the MFL and WSDL for proxy service B and uses this to prepare the message that will be routed to proxy service B.
In step 4, the message is executing in the old version of proxy service A, but can potentially see the new versions of the MFL and WSDL of proxy service B.
Workaround: Ensure that you do not have any messages currently executing in a proxy service when you are updating the MFL and WSDL of a second proxy service that is invoked by the first.
2.5
CR254750
Publishing to UDDI intermittently returns an error when you publish 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
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
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 being copied. However, the file is processed successfully on the next polling cycle after the copy completes.
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 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.
Workaround: To construct a non-system fault in ALSB:
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:
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:
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 ALSB 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/weblogic9xx/common/bin directory.
2.0
CR231843 (continued)
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.
Note:
There is no protection mechanism similar to LLRs 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
CR231102
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.
Note:
To learn about maximum path lengths, see the following information: “Maximum Path Length” at the following URL:
You cannot protect inbound response destinations with security policies because the inbound response message is enqueued as 'anonymous' due to the lack of the security context propagation.
2.6 RP1
CR320930
Error occurs when you send message through ALSB to a secure JBoss topic.
Although a JMS service account is defined for the business service, it is not used to obtain JMS connection. JBoss throws the following error when you send message to a secure JBoss topic:
'connection is not authorized to add message to destination'
If a service account is defined for the business service, the associated credentials are now used to obtain a JMS connection.
2.6
2.6 RP1
CR300663
X.509 cannot get the user's DN from the certificate in pipeline.
The user DN embedded inside a X.509 certificate is not sent to ALSB message flow. You cannot call an external service to get the user’s security attributes and perform data level filtering within the message flow based on these attributes.
This problem has been resolved.
2.6
2.6 RP1
CR305954
CR305954
Security errors can appear in the server logs when two or more clustered domains are configured to send messages via Store and Forward (SAF).
Workaround: None. You can ignore these errors.
2.6
CR293202
Problem using ALSB HTTP proxy services with WebLogic Server web server plug-ins when using SSL.
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: javax.servlet.ServletException: Cannot process inbound request to endpoint ProxyService Project/folder/ProxyName over https
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.
2.6
2.6 RP1
CR284336
A security error in the server log occurs in both ALSB and WebLogic Server.
The error is as follows:
“Server Identity fails validation, downgrading to anonymous.”
Employ one of the following workarounds depending on your scenario:
When there is cross-domain transaction
Workaround: Establish domain trust.
When there is no cross-domain transaction
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.
2.5
CR276562
The WebLogic Server WS-Policy parser accepts policies with unknown assertions.
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.
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.
Note:
When you clone a service, access control policies are not cloned.
2.5
CR234237
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 Configuring Security in Programming Web Services for WebLogic Server.
iWay Application explorer throws Internal Server Error on session timeout for Service adapter and Event Adapters.
Workaround: Close the browser and re-connect.
2.6 RP1
CR346814
You continue to receive messages from SAP transport even after the SAP Inbound Channel on SAP Event Adapter is stopped.
2.6 RP1
CR346807
WSDL-based SAP inbound messages show transportClient as alsb-system-user instead of anonymous.
2.6 RP1
CR346157
When running the cross-domain request-response JAX-RPC over a JMS application with different security subjects in the communicating domains, you would not be able to protect the inbound request queue with the ACL-based security policy. This is because, accessing this queue would require setting local username and password on the stub using Stub.USERNAME_PROPERTY and Stub.PASSWORD_PROPERTY. Such a setting causes propagation of the local subject into the remote domain, consequent security exception and lack of the JWS execution.
2.6 RP1
CR345758
Intra-domain transactions may sometimes be rolled back when running the cross-domain request-response JAX-RPC over a JMS application that utilizes SAF configured with SSL ports.
2.6 RP1
CR345755
SSL connection between two clustered domains may sometimes be lost when running the cross-domain request-response JAX-RPC over a JMS application with XA Connection Factories and utilizing SAF configured with SSL ports.
2.6 RP1
CR339618
JAX-RPC service response message is produced as 'anonymous' despite the @RunAs role set in JWS.
If JWS is implemented as a POJO and the @RunAs role is set in the JWS file, the outbound request message is consumed as the subject in the role, but the outbound response message is produced as 'anonymous'. Therefore, you cannot protect the outbound response queue with the ACL security policy.
2.6 RP1
CR302664
When creating a C# client stub from a proxy service WSDL that has more than one WSDL binding, the .NET wsdl.exe tool may generate a C# client stub with the wrong WSDL binding.
Workaround: If you cannot specify the service binding for which to generate the C# stub, we recommend that you comment out any unused bindings in your proxy service WSDL before generating the client stub.
2.6
CR300352
You may get a NullPointerException for an iWay Service Adapter when attempting to generate a schema in the iWay Business Services Engine (iBSE) console
Workaround: None. The schema is generated successfully and you can use it in your system.The NullPointerException is the result of the failure of the subsequent parsing of the generated schema.
2.6
CR295664
For a TUXEDO transport based service, if the service type is XML, a FML32 buffer with FLD_MBSTRING field from a tuxedo client will not be transformed to XML.
2.6
CR283942
Using the Linux SYBASE jRockit Non-XA driver with LLR enabled can result in a deadlock situation and throws a SQLException on the Sybase database.
Workaround: Use the Linux SYBASE jRockit XA driver.
2.5
CR281003
You cannot move an ALSB configuration JAR file with encrypted resources exported with the Sun or JRockit JDK to the IBM AIX JDK and vice-versa.
There are differences in the various JDK implementations of the Password-Based Encryption algorithms used by ALSB to protect resources with sensitive data. These differences cause import to fail when an encrypted resource created with the Sun or JRockit JDK is imported into the IBM JDK or vice versa.
There is no problem in exporting and importing encrypted resources with the same JDK.
Workaround: Export the resources without a pass-phrase by deselecting the Protect Sensitive Data flag when going across different JDKs.
WARNING: This resources file may contain passwords that are in the clear text.
2.5
CR269889
The iWay55 installer does not work with ALSB 2.5.
Workaround:
To deploy and access the iWay installer:
1.Copy the contents of the weblogic91/common/bin/commEnv.cmd file that the iWay55 installer creates and add it to the end of the weblogic92/common/bin/commEnv.cmd file.
2. Save the file and restart the server.
2.5
ALSB Console
Problem ID
Description
Found In
Fixed In
CR306906
Incorrect target cluster name for a clustered ALSB domain is displayed on the console after you import a configuration JAR file from a different clustered domain.
Workaround: None. Please ignore the cluster name in the console. You cannot edit this incorrect target cluster name.
2.6
CR284845
The ALSB Console incorrectly includes non-public classes and their methods when listing Java methods that can be called from a JavaCallout Action.
Selecting a Java method of a non-public class results in a java.lang.IllegalAccessException.
Workaround: You can find out what the access modifiers on a class are by using the javap utility. For example:
If you name a new resource in the ALSB Console using a badly formed path, the console may hang.
The problem happens only for the IE browser on WinXP-SP2 or Win03-SP1.
Workaround: You cannot cancel the pop-up progress meter window. You must close the browser instance running the ALSB Console and open a new one, then enter a valid file path for the new resource.
2.5
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
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 ALSB 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 ALSB Console.
Workaround: Modify the Internet OptionsSecurity Settings to Active Script: Enable. Because ALSB uses JavaScript in the Console pages, make sure JavaScript is enabled in your browser.
2.0
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 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.
2.0
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 ALSB. 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
BEA XQuery Mapper
Problem ID
Description
Found In
Fixed In
CR250692
XQuery Mapper exits abruptly while a new XQuery transformation is being created with a large schema.
You cannot 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
It is not possible to create a copy link while doing non-XML to XML and XML to non-XML data transfer.
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
It is not possible to validate the 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
The namespace prefix is not generated when the target is non-XML.
When the target is non-XML, the target namespace prefix is not generated properly in the XQuery source. This problem causes an error when XQuery is executed 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.
2.1
CR222617
Pasting expressions in the expression boxes in Constraint view causes an error.
When expressions are pasted in the left-hand or right-hand expression box in the Constraints view, a compilation error occurs.
Workaround: Instead of pasting, 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.
Workaround: Press CTRL Z a few times to undo the delete.
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
CR225672
Design view cannot 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
The If-Then-Else expression is not displayed when a 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
CR231623
Selecting Generate Data in Test view 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 occur large XQuery files are opened in 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.
Changing a Join condition from OR to AND works intermittently.
In Eclipse, if you click on a target node item and right-click on any OR, then select Change Join condition to And from the pop-up menu, nothing happens.
Note:
This problem does not always occur. It is an occasional bug.
2.0
CR234891
The Convert Data Link to Structural Link option is missing from the 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. Then, create a link between a parent-parent element, which will be a structural link, and then delete the child-child link.
2.0
CR234961
Code is not displayed after the View Code option is selected from the 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: Select the Source tab to manually switch to the Source view.
2.0
SmartConnect
Problem ID
Description
Found In
Fixed In
CR335609
ALSB WSDL-based business and proxy services created using WSDLs generated by iWay Adapters Version 5.5 fail with a run-time error.
WSDLs created by the iWay Adapters Version 5.5 can be imported into ALSB, but should not be used at run time.
2.6 RP1
3.0
CR336007
In a clustered domain, you cannot use the test console to test business services.
2.6 RP1
CR336048
CR335163
Publishing WSDLs to ALSB Console with iWay Application Explorer for SEBL transport throws error.
When you publish WSDLs for Siebel with the iWay Application Explorer, FileNotFoundException is thrown and the WSDLs are not published to ALSB Console because the Siebel adapter does not support the usage of RPC.
2.6 RP1
CR338176
WSDL-based business services exposed in ERP transport accept input with invalid namespace.
WSDL-based business services accept the request data even though the input XML has an invalid namespace, which is not defined in the WSDL. No exception is thrown.
Workaround: Validate the input data in the pipeline according to the published WSDL.
2.6 RP1
CR339447
The bulk import of XML schemas and WSDLs fails on the ALSB Console for the SAP transport.
When you try to import a zip file that contains XML schema or WSDL files with file names that contain white spaces, the import fails.
Workaround: Before you import a file, change the name of the file to remove any white space.
2.6 RP1
CR341301
Deployment of an ERP transport application fails on WebLogic Server.
The deployment of an ERP transport EAR file on WebLogic Server Console fails because required third party libraries are missing on the domain.
Workaround: Add the associated third party libraries to the system path of the domain.
2.6 RP1
CR342980
Users in the role of IntegrationDeployers cannot publish WSDLs from the BEA SmartConnect Explorer to ALSB. Only users in the role of IntegrationAdministrators can publish WSDLs to ALSB.
2.6 RP1
CR343208
Error message repeats when a SAP transport-based proxy service is detached from the SAP host.
When a SAP transport-based proxy service gets detached from the SAP host, the same error message is displayed multiple times on the WebLogic Server Administration Console.
2.6 RP1
CR343937
In the ALSB Console, on the Operations > Global Settings page, if Monitoring is enabled for WSDL-based inbound proxy services for SAP transport, the following message is displayed:
<Message text not found - Cannot locate bundle for class>
You can safely ignore this message.
2.6 RP1
CR348196
When you extend an ALSB domain using the extension template for the ERP transports, both the SAP and Siebel transports are deployed.
Upon starting the server, an error message is displayed for each transport. You can safely ignore these error messages.
2.6 RP1
3.0
Upgrade
Problem ID
Description
Found In
Fixed In
CR348242
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.
Workaround: Upgrade using any of the following options:
Obtain the ALSB 2.6 RP1 installer from BEA Support to perform the upgrade installation.
or
After you upgrade using the BEA Smart Update tool, use the Smart Update tool to install patch set Q4MZ, which automatically installs the patches BZ6J (CR287220), 7KCW (CR326377), Z7MC (CR320630), and JJPY (CR334500). If you use the Smart Update command-line tool, be sure to download the patch set and patches into the same download directory.
2.6 RP1
Documentation
Problem ID
Description
Found In
Fixed In
CR342020
Table 9-3 in the AquaLogic Service Bus Security Guide incorrectly states that a user in the IntegrationDeployer role can view and edit, but cannot create or delete UDDI registries.
A user in the IntegrationDeployer role has the same privileges as a user in the IntegrationAdministrator role for UDDI registries.
2.6 RP1
The Listing and Locating Access Control Policies topic provided in the online help that you launch from the ALSB Console does not mention that you can create a message-level access control policy for proxy services that have message-level custom authentication.
