|
|
Description and Workaround
|
|
|
ALSB (AquaLogic Service Bus) currently generates WSDLs that incorrectly import XSD using the WSDL import element. This causes a problem in the AL suite due to the fact that these ALSB WSDLs can be parsed and submitted to ALER properly by the AL common Eclipse tooling; however, the ALRR Exchange Utility is not capable of parsing the WSDLs when migrating them back to ALSR (AquaLogic Service Registry).
For more information, including an example of the proper usage of the XSD import element to import XSD, see the
Using the ALRR Exchange Utility.
|
|
|
The BEA license.bea file is not found when installing ALER for use with the standalone Apache Tomcat application server.
To resolve this issue, see the Post Installation instructions in
Installing AquaLogic Enterprise Repository.
|
|
|
The BEA licens.bea file is not found when installing ALER for use with the WebSphere application server.
To integrate the License.bea file into the classpath of your WebSphere installation, you must:
- In Application servers > server1
 Process DefinitionJava Virtual MachineCustom Properties, create the following custom property:
Name: BEA_HOME
Value: /opt/IBM61/bea_home
- Restart the application server.
|
|
|
The -Dfile.encoding=UTF-8 JVM parameter is required to support non-US character types within the application data when using a built-in Tomcat installation.
Although the installer for the built-in Tomcat installation provides the parameter, users should not remove this parameter when modifying JVM parameters.
|
|
|
XLST parsing does not function correctly in WebSphere installations.
WebSphere installations require the following additional JVM parameter in the same location as -Xverify:none:
-Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault
|
|
|
The installer fails during database installation on HP-UX Itanium 11i v2.
Run the database wizard after installation.
|
|
|
The SetOperator of Searchterm in the REX API is not sensitive to case and may return more search values than expected.
|
|
|
WorkSpace Studio cannot authenticate to the repository when ALER is configured for J2EE container authentication.
|
|
|
WorkSpace Studio cannot authenticate to the repository when ALER is configured for SSO authentication.
|
|
|
When ALER is deployed on IBM WebSphere 6.x and if ALER Event Manager is enabled, the embedded Apache ActiveMQ JMS Server cannot be used due to conflicts in the classes used by ActiveMQ and ALER.
The WebSphere 6.x customers can use the JMS server that comes with IBM WebSphere 6.x.
|
|
|
There is a limitation when configuring the embedded ActiveMQ JMS Server to use MS SQL Server since this database is not supported by ActiveMQ.
Use the file system to store messages or use an external JMS Provider. When ALER is configured in a cluster, it is important to configure ActiveMQ to use a database to store messages, and due to this limitation, MS SQL user must use an external JMS server in a clustered environment.
|
|
|
When publishing JMS messages to IBM WebSphere, the ALER Event Manager will not set the JMS Client ID due to J2EE threading restrictions in setting the ClientID within a Web container.
|
|
|
If AquaLogic Service Bus 2.6 or AquaLogic Data Service Platform 2.5 are installed after the ALER 3.0 plug-in is installed, then Eclipse must be launched using the -clean flag.
|
|
|
When uninstalling the ALER plug-ins for Eclipse, WorkSpace Studio will also be removed if WorkSpace Studio was installed by the ALER installer. This may not be desirable if other plug-ins were added to WorkSpace Studio.
To avoid uninstalling additional WorkSpace Studio plug-ins, deselect the ALER Plug-ins for Eclipse from the list of components to uninstall.
|
|
|
The XSLT viewer in ALER's Asset Editor requires the equivalent of a client side JRE version of 1.5.0_09 or later.
|
|
|
Project submissions may fail with a Enterprise Repository Connection Busy error when you attempt to re-submit a project within a short time of the initial submission and your submission is in the same Eclipse session and the initial submission is still in progress.
If the operation fails, close the current Eclipse session and restart. After Eclipse restarts, the operation will succeed.
|
|
|
The Advanced Search field Model Producing Product searches over the product name, not the product name and version. When search results are returned, the results table shows both the Name and Version together.
|
|
|
WorkSpace Studio cannot authenticate to ALER when ALER is configured for J2EE container authentication.
Use LDAP or database authentication.
|
|
|
WorkSpace Studio cannot authenticate to ALER when ALER is configured for SSO authentication.
Use LDAP or database authentication.
|
|
|
If AquaLogic Service Bus 2.6 or AquaLogic Data Service Platform 2.5 are installed after the ALER 3.0 plug-in is installed, then Eclipse must be launched using the -clean flag.
|
|
|
Creating a RAW_SCM with a downloadUri that includes & chars causes the Artifact Store to fail to appear in the list of available stores when creating a new file.
You must manually 'xml escape' characters. For example, replace & with &
|
|
|
ALER creates an Microsoft Excel a spreadsheet for every asset type of an asset being exported. Many ALER asset types use special characters, such as a colon (:) which cause Excel to throw an error message and the Tab name, which should be the asset type name, no longer matches the asset type
Rename the tabs after the export to Excel so that they match the asset types in ALER.
|
|
|
Manually replacing 'xml escape' characters, such as replacing & with & prevents downloading of ClearCase ccWeb content. See CR339815.
Use a RAW_SCM that accesses ClearCase using the ALER file store mechanism.
|
|
|
Application server using SUN JDK crashes or throws an out of memory exception.
Add the following to JAVA_OPTS:
-XX:NewSize=128m -XX:MaxPermSize=128m
|
|
|
SERVER_NAME environment variable is not correctly set by installer on WebLogic Server 9.2.1 installations.
Remove or properly set the SERVER_NAME environment variable when starting the ALER domain. For example:
set SERVER_NAME=alerServer
SERVER_NAME=alerServer
export SERVER_NAME
|
|
|
When the Advanced Registration Flow tools are installed by the installer, the appropriate execution permission is required for Unix and Linux systems before executing the scripts under BEA_Home/repository30/core/workflow-tools
For example: - chmod 777 *.sh
|
|
|
When an Asset is opened, edited in the Asset Editor, and the Advanced Registration Flow processes the asset in the background, the merge capability is not supported by ALER.
Revert the changes made within the Asset Editor or lose the changes made by the Advanced Registration Flow.You can reduce the probability of this issue occurring by increasing the Event Manager Sleep time to a large value so that the Events are emitted and processed when the traffic to ALER is low.
|
|
|
When an Asset is submitted using the Quick Submit feature, there is an issue in processing that asset by the Advanced Registration Flow when:
- The Asset is opened in the Asset Editor by a Registrar before the Advanced Registration Flow accept the asset
- Advanced Registration Flow accepts the asset
- Registrar accepts the asset and is not aware that the Advanced Registration Flow has accepted the asset as the Asset page has not refreshed
- The ALER Asset Editor update to show that Advanced Registration Flow has accepted the asset
This creates a duplicate asset entry in the Asset Editor tree and the Advanced Registration Flow has issues executing the multi-tier approval process.
When an asset enters into this condition, manually unaccept and then accept the asset.
|
|
|
In Workspace Studio, submitting an assembly model to ALER may prevent users from also performing other operations in parallel, such as performing a search, before the submission is completed.
Avoid performing multiple operations when submitting assembly models.
|
|
|
In Workspace Studio, you cannot store and retrieve binary artifacts, such Word docs and JPEG files, for assembly models.
|
|
|
When running the java process during the upgrade installation, larger data sets may run into JVM memory constraints.
If “out of memory” errors occur while running the migrate.sh or migrate.bat process, increase the memory as follows:
- Open the
r4.bat/r4.sh file.
- Increase the memory by increasing the
java -mx192m setting (e.g., java -mx1024m).
- Save the changes.
- Re-run the
migrate.sh or migrate.bat process.
|
|
|
When upgrading to ALER 3.0, importing larger data sets may cause available memory issues when running the Import/Export tool.
Save the impexp.jnlp file locally, and then edit it to increase the default max-heap-size amount to better accommodate the size of the data sets being imported. If the machine importing the data sets has enough available memory, set the max-heap-size as follows:
<j2se version="1.5" max-heap-size="1024m"/>
|
|
|
When configuring the ALBPM “FDI User Credentials” while running the ALER 3.0 installation wizard, you cannot use the @ sign as a password character because that value does not get passed into the build.properties file used by the Ant scripts to install ALBPM.
If you must use the @ character, you’ll need to manually edit the build.properties file and enter the values for a password using the @ sign character, and then manually run the Ant scripts to install ALBPM.
|
|
|
Built-in Tomcat application server throws an out of memory exception.
Add the following to JAVA_OPTS:
|
