Workarounds: Installation and configuration problems in Design Management 4.0.1
The Design Management Team
Last Updated: April 19, 2012
Build Basis: Design Management 4.0.1
The table of contents lists the known problems and workarounds related to the installation functionality in the Design Management 4.0.1 release.
- The Design Management finalization process might stop running during the “Create Storage Areas” step if user information is imported from an LDAP registry.
- After an external Jazz application is added using the Jazz Team Server’s registered applications page, the registration success message contains a link to perform the setup for the application just added. The URL in this link is sometimes invalid and results in a setup page that does not have Back or Next buttons.
- When you perform a custom configuration of the Design Management Server, you must select the licenses to apply. If you do not choose any licenses, or choose only a Rational Rhapsody license, the Design Management Server configuration fails when the Design Management application is finalized.
- The Design Management finalize page should not be marked as complete if it is refreshed.
- A user that has JazzUser Repository permission can create workspaces and snapshots in the Configuration Management application, even without a client access license.
- During Design Management (DM) setup, the finalization of DM can take a substantial length of time. If the setup page is refreshed or if server setup is subsequently restarted, the Finalize button on the Design Management finalization page is disabled.
- When you configure the Design Management Server, the Finish button is enabled before the finalization process is complete.
- An error is displayed and the application finalization process fails when you run a scripted setup for a Design Management server.
- The server rename process fails for Design Management and the Configuration Application if the Jazz Team Server data warehouse is not configured to use Apache Derby on port 1527, which is the default value for the Apache Derby data warehouse.
- If you are running WebSphere Application Server (WAS) and you log out of Design Management, you get the following error message SESN0008E.
Problem Summary
The Design Management finalization process might stop running during the “Create Storage Areas” step if user information is imported from an LDAP registry.
Problem
During the Design Management finalization process, the users defined in an LDAP registry can be imported into the Jazz Team server. As part of this process, a synchronization request is made to obtain the user information. Design Management waits for two minutes for that synchronization to complete before proceeding with the finalization process.
If the LDAP registry is large, for example, if it contains more than than 5000 users, the synchronization might take longer than two minutes. As a result, key Design Management internal users are not registered and the finalization process to create the storage areas stops running.
Workaround
If you are importing a large LDAP user registry into Design Management, on the page that identifies the LDAP registry and the main administration user, click Next. The data warehouse initialization page opens. Wait for five minutes before you proceed from this data warehouse initialization page to allow the completion of the LDAP synchronization.
Related Information
The following links point to related information:
Problem Summary
After an external Jazz application is added using the Jazz Team Server’s registered applications page, the registration success message contains a link to perform the setup for the application just added. The URL in this link is sometimes invalid and results in a setup page that does not have Back or Next buttons.
Problem
You can install the Configuration Management and Design Management applications on server machines other than the machine that runs their common Jazz Team Server (JTS). In this scenario, these external applications must be added using the main JTS server’s registered application page. Both of these applications require additional setup steps to be performed.
After each Jazz application is added, the status message that indicates success contains a link to complete the additional setup steps for that application. The URL in this link is invalid and links to a web page that does not contain navigation controls; therefore, you cannot complete the setup.
Workaround
To install both Configuration Management and Design Management (DM) as external Jazz applications, ensure that the setup of the Configuration Management application is completed before the setup of Design Management by registering both applications first. Do not click the setup application link in the status message that indicates a successful registration. After both applications are registered, complete the application setup:
- Start the JTS server setup again by opening the setup page: https://jts/setup
- Select the custom setup option. Do not select the express setup option because the setup process is almost completed.
- On the setup pages, click Next.
- On the Jazz application registration page, you do not register either the Configuration Management application or DM because they are already registered. Click Next.
- After the data warehouse initialization page, the setup pages for the Configuration Management application and then DM should appear. Proceed with the setup as usual.
Problem Summary
When you perform a custom configuration of the Design Management Server, you must select the licenses to apply. If you do not choose any licenses, or choose only a Rational Rhapsody license, the Design Management Server configuration fails when the Design Management application is finalized.
Problem
When you install Rational Software Architect Design Manager, the setup process requires the Rational Software Architect Designer license; it fails if it is not selected. During an express configuration, a temporary license is assigned; however, during a custom configuration, you may choose to assign no licenses, or to assign only a Rational Rhapsody license.
Workaround
During a custom configuration, ensure that you assign a Rational Software Architect Designer license.
Problem Summary
The Design Management finalization page should not be marked as complete when you refresh the page.
Problem
The Jazz Team Server considers a Jazz application, such as Design Management, to have completed the finalization process after you click Finalize. If any of the finalization steps for the application fail, the finalization process on the server cannot be completed.
Running out of memory is a common problem during the finalization process. Because the finalization of Design Management can take a long time to complete, consider using an operating system mechanism to ensure that the Jazz server is running. If an out-of-memory error occurs, the server typically stops.
Workaround
The Design Management finalization can take a long time to complete. Do not refresh the web page during the finalization steps.
If the finalization process has stopped responding, use an operating system tool to verify that the Jazz server is running. You can also examine the server log files and the server console output to determine whether a problem occurred, and to determine whether Design Management is running. The log file named installation_folder/server/log/dm.log is typically updated during the finalization process for Design Management.
If a finalization error occurs, you must uninstall the server and start again. If the finalization process failed because it ran out of memory, after you reinstall Design Management, you must modify the server.startup file in the installation_folder/server folder before you restart the server. Edit the JAVA_OPTS flags to increase the memory limits (-Xmx and -Xms). If you install Design Management on a recommended 64-bit machine that has at least 6 GB of memory, set the memory flags to -Xmx6G and -Xms6G.
Problem Summary
A user that has JazzUser Repository permission can create workspaces and snapshots in the Configuration Management application, even without a client access license.
Problem
The Configuration Management application has no licensing requirements. Any user ID with the JazzUser Repository permission enabled can create workspaces and snapshots in the Configuration Management application. Without an understanding of parallel workspaces, creating snapshots and workspaces might require complicated merges at a later time.
Workaround
Advise users against creating workspaces or snapshots unless their role requires them to do so. Workspaces and snapshots cannot be deleted.
Problem Summary
During the setup of Design Management, the finalization process might take a long time to complete. If you refresh the setup page is refreshed or restart the server setup process, the Finalize button on the Design Management finalization page is disabled.
Problem
The Jazz Team Server considers a Jazz application, such as Design Management, to have completed the finalization process after you click Finalize. If any of the finalization steps for the application fail, the finalization process on the server cannot be completed.
Running out of memory is a common problem during the finalization process. Because the finalization of Design Management can take a long time to complete, consider using an operating system mechanism to ensure that the Jazz server is running. If an out-of-memory error occurs, the server typically stops.
Workaround
The Design Management finalization can take a long time to complete. Do not refresh the web page during the finalization steps.
If the finalization process has stopped responding, use an operating system tool to verify that the Jazz server is running. You can also examine the server log files and the server console output to determine whether a problem occurred, and to determine whether Design Management is running. The log file named installation_folder/server/log/dm.log is typically updated during the finalization process for Design Management.
If a finalization error occurs, you must uninstall the server and start again. If the finalization process failed because it ran out of memory, after you reinstall Design Management, you must modify the server.startup file in the installation_folder/server folder before you restart the server. Edit the JAVA_OPTS flags to increase the memory limits (-Xmx and -Xms). If you install Design Management on a recommended 64-bit machine that has at least 6 GB of memory, set the memory flags to -Xmx6G and -Xms6G.
Problem Summary
When you configure the Design Management Server, the Finish button is enabled before the finalization process is complete.
Problem
The pages for the finalization process in the Configuration Management and Design Management applications extend the Jazz Application Foundation (JAF) Software Development Kit (SDK) Finalize Application page. Because of this extension, the Finish button is enabled before the configuration is complete for the Configuration Management and Design Management applications.
Workaround
Ignore the enabled Finish button. Click Next until the server configuration is complete. The server configuration is complete when a summary page is displayed.
Problem Summary
An error is displayed and the application finalization process fails when you run a scripted setup for a Design Management server.
Problem
When you run a scripted setup against a Jazz Team Server that Design Management installed, the finalization process for Design Management fails and the following error is displayed:
Executing step: Finalize Application
CRJAZ2438E An error occurred while invoking the service https://bowas:9443/dm/configure?action=applyTemporaryLicense.
CRJAZ2247E There was an error executing setup: “CRJAZ0105E The request for the following URL was denied: /dm/configure?action=applyTemporaryLicense&oauth_token=f8b857f7e5004031a3aed9a6913af599. The status is “Unauthorized”.”. Check the log for more details.
Workaround
Run either a custom setup or an express setup.
Problem Summary
The server rename process fails for Design Management and the Configuration Application if the Jazz Team Server data warehouse is not configured to use Apache Derby on port 1527, which is the default value for the Apache Derby data warehouse.
Problem
Design Management and the Configuration Application do not use a data warehouse, therefore their teamserver.properties files specify the default value for an Apache Derby data warehouse.
As part the server rename process, Jazz reporting attempts to update all data warehouses even though Design Management and the Configuration Application have disabled it. When Jazz reporting accesses the default Apache Derby data warehouse instead of a valid data warehouse, the server rename process fails for Design Management and the Configuration Application. When the server rename process fails, the following error message is displayed in the Design Management and Configuration Application log files:
[com.ibm.team.repository.service.mapping.internal.ServerRenameService] [] ERROR com.ibm.team.repository.service.mapping.internal.ServerRenameHelper - CRJAZ2358E An error occurred while processing the server rename events.
com.ibm.team.repository.common.TeamRepositoryException: java.net.ConnectException : Error connecting to server localhost on port 1527 with message Connection refused.
Workaround
In the Design Management teamserver.properties file (installation_folder/server/conf/dm/teamserver.properties) and the Configuration Application teamserver.properties file (installation_folder/server/conf/vvc/teamserver.properties), you must specify a valid data warehouse.
Complete the following steps based on your setup:
If you have configured an Apache Derby data warehouse on a port other than 1527, you must update only the com.ibm.team.datawarehouse.db.jdbc.location property in the Design Management and Configuration Application teamserver.properties files:
From the Jazz Team Server teamserver.properties file (installation_folder/server/conf/jts/teamserver.properties), copy the com.ibm.team.datawarehouse.db.jdbc.location property and replace the entire corresponding line in the Design Management and Configuration Application teamserver.properties files.
If you use a data warehouse other than Apache Derby, such as IBM DB2:
- Create a backup copy of the Design Management and the Configuration Application teamserver.properties files.
- In the Design Management and Configuration Application teamserver.properties files, delete entries that contain the following text: datawarehouse
- From the Jazz Team Server teamserver.properties file, copy all the entries that context the text datawarehouse to the Design Management and Configuration Application teamserver.properties files.
The following example shows the entries to copy from the Jazz Team Server teamserver.properties file:
com.ibm.team.datawarehouse.auth.type=JTS com.ibm.team.datawarehouse.auth.userId=c767b5eb596c4a43a1810efb4b7cbb12 com.ibm.team.datawarehouse.db.jdbc.location=//fit-vm8-044:50001/dwDB:user=db$ com.ibm.team.datawarehouse.db.jdbc.password=[Iha3LmcQHc2qhIZHiC9JRg==] com.ibm.team.datawarehouse.auth.password=[RNkV5HUlw2Q85+RkVPlqzooMIRVRYDUqpaK6s$ com.ibm.team.datawarehouse.datawarehouse.jobs.enabled=false com.ibm.team.datawarehouse.db.automatic.setup=true com.ibm.team.datawarehouse.db.vendor=DB2 com.ibm.team.datawarehouse.datawarehouse.provider=Remote com.ibm.team.datawarehouse.db.base.folder=/var/tmp
- In the Design Management and the Configuration Application teamserver.properties files, ensure that the com.ibm.team.datawarehouse.datawarehouse.jobs.enabled property is set to false.
- Start the server rename process.
Problem Summary
If you are running WebSphere Application Server (WAS) and you log out of Design Management, you get the following error message SESN0008E.
Problem
The user is not logged out properly. The resulting message is in the form of a JavaScript object, ending with "SESN0008E: A user authenticated as anonymous has attempted to access a session owned by user…".
Workaround
Enable the fix on WebSphere Application Server (8.0.0.3+) by adding a custom session manager property. Click Application servers > server1 > Session management > Custom properties; then, add the following custom property:
InvalidateOnUnauthorizedSessionRequestException = true custom property
Alternatively, if you close your browser instead of explicitly logging out, the session eventually times out on its own.
Related Information
The following links point to related information:
Copyright © 2013 IBM Corporation