The table of contents lists the known problems, workarounds, and limitations related to the Web Client and Server functionality in the Rational Requirements Composer 4.0.2 and DOORS Next Generation 4.0.2 release.

Workarounds

Use the links below to learn more about the issues and workarounds in this release:

Problem summary

Custom Word templates are not updated in an upgrade

Problem

In releases of version 3.0 and earlier of the Requirements Management (RM) application,
custom Word templates use the .dot extension. In version 4.0 and later, those templates
use the .doc extension. When you upgrade to version 4.0 or later, the templates that are
included in the RM application are automatically updated to the .doc extension; however,
custom templates are not updated. As a result, problems can occur in the custom templates.

Workaround

An administrator must manually update the custom templates:

Open the Word template folder, which is in this location:
RM_Install\server\conf\rm\reporting\initialization\templates\word.

Sort the files by type. The custom templates use the .dot extension; other files use the .doc extension.

Open each .dot template in Word and then save each template as a .doc file.

Delete the .dot templates.

Open the manifest file, which is in this location: RM_Install\server\conf\rm\reporting\initialization\META-INF\.

Verify that each custom template in the RM_Install\server\conf\rm\reporting\initialization\templates\word folder
has the .doc extension and the exact name as the related files with the .dta extension.

Initialize the publish service by entering this URL in a browser: https://server_name/rm/publish/initialize.

Related information

Problem summary

After a document is imported into a module, images that are in headings are not shown in artifacts

Problem

This problem occurs in version 4.0.2 of the Requirements Management (RM) application. In version 4.0.3 and later, it is fixed. The following screen captures show an example of this problem:Figure 1. In the original document, the heading contains an image

Figure 2. After the import, the image is not shown in the heading in the RM application

Figure 3. Although the image is not in the heading, it is in the module's folder

You might experience this issue after you import a document as follows:

Click Artifacts > Import requirements from within a text document.

On the “Select text document” page of the import wizard, select a rich text document to import, and select Yes, import the requirements and create a module.

On the “Specify how to identify requirements” page, select artifact types for images and headings. Do not select None.After the import is complete, the images that were in headings in the document are not displayed in the artifacts in the module. An example of this behavior is shown in Figure 2.

If you open the folder that contains the module's artifacts, you see the image, as shown in Figure 3.

Workaround

Tip: To avoid this problem, before you import a document, move any images that are in headings out of headings.

If the problem already occurred, complete these steps:

Open the heading artifact for editing.

Right-click the heading artifact and select Insert Image.

Browse to and select the image artifact, and then click OK. The image is now in the artifact.

Problem summary

Problem

In some situations, you might notice that the import wizard does not detect images or text as artifacts. The following screen capture shows such a case:Figure 1. Example of no artifacts being detected

This issue usually occurs when the artifact types for the content that the wizard can detect are incorrectly set. You set the artifact types on the “Specify how to identify requirements” page of the import wizard. The next two screen captures show a request to extract all of the content that the wizard supports.

Figure 2. Settings on the upper half of the “Specify how to identify requirements” page

Figure 3. Settings on the lower half of the “Specify how to identify requirements” page

As you can see, artifact types were specified for headings, images, all other text, keywords, and text delimiters. No artifact types were set to None.

Depending on your request and document, the wizard might not detect images, even if an artifact type is set for them. This issue is resolved in version 4.0.3. For version 4.0.2, this issue occurs because the artifact type of the content that the image is embedded in takes precedence over the image's artifact type. For example, if an image is in a block of text that is of the “All other text” content type and that type is set to None, the image is never extracted.

Workaround

Complete these steps:

Return to the “Specify how to identify requirements” page of the import wizard.

Re-evaluate the artifact types that are specified for each type of content, and make sure that none of them are incorrectly set to None.

Related information

Problem summary

After you save selected text as a new artifact, when the new artifact is linked to or inserted, an error occurs.

Problem

This issue occurs for artifacts that are created from selected text that includes an embedded artifact that is the last element in the document. When you link to or from the new artifact or insert it into a document, the operation to link or insert the artifact fails, and an error message is displayed.

Workaround

Before you select the text to save for the new artifact, insert carriage returns after the embedded artifact that is at the end of the document.

If you already selected the text to create an artifact and the error occurred, manually link to or insert the new artifact by following these steps:

Delete the selected text from the editor.

To insert a reference in a document to the new artifact, click either Insert Artifact or Add Link.

To create an Extracted or Extracted From traceability link between a document and the new artifact, click Create Matching Trace Link

Related information

Problem summary

After the context of the Requirements Management application is changed in a server rename, an error occurs in the converter application

Problem

After a server rename in which the context of the Requirements Management (RM) application is changed, the converter application cannot find the logging .properties file. As a result, another problem occurs in the converter application, and all requests fail with this null pointer exception:
Error 500: java.lang.NullPointerException
For more information about the problem in the converter application, see defect 70212.

Workaround

After the RM application context is changed, the system administrator must follow these steps:

Create this directory: JazzInstallDir/rm/converter, where JazzInstallDir is the location where the server is installed.

Open the JazzInstallDir/new_RM_context/converter directory, and then copy the required log4j.properties file into the directory that you just created.

Problem summary

An upgrade cannot be completed without a Requirements Management Analyst license

Problem

In certain cases, to configure the Rational solution for Collaborative Lifecycle Management (CLM) you must upgrade the Requirements Management (RM) application, even if you do not directly use that application. For example, in Rational Quality Manager, the RM application provides the requirements management capabilities. In that scenario, the Rational Quality Manager license is sufficient to provide the requirements management capabilities. However, that license is not sufficient to upgrade the RM application.

If your deployment contains expired RM application trial licenses, you cannot use the 4.0.2 RM application trial licenses to upgrade. To check for expired trial licenses, go to the Jazz Team Server Administration page at https://fullyQualifiedHostName:port/jts and click the License Key Management link. On the license key management page, you can scan for expired RM application trial licenses.

Workaround

Contact IBM Support and request a temporary license that you can use to upgrade the RM application.

Related information

Problem summary

When you remove a link to a Design Management resource, an unrelated message is shown

Problem

In the Requirements Management (RM) application, when you remove a link to a Design Management resource from the Links sidebar, the following message is displayed: While removing a link between servers, the link from the other server could not be deleted. ID CRRRW7254W The link from the other server to this server could not be deleted because the other server is not available or communication with it has failed.
Despite what the message states, the link has been removed.

Related information

Problem summary

When the import wizard extracts requirements from a document, an error occurs

Problem

While the import wizard is extracting requirements from a document, this error message might be displayed: Errors loading source. If you specified any text delimiters for extraction, doing so might have caused the error. However, this problem might be caused by other issues, such as problems processing lists. This problem occurs in documents that contain at least one delimiter that ends on the same line that another delimiter starts on. For an example, see Figure 4.

The following series of screen captures and stack trace exceptions show the symptoms of this problem. You can use this information to isolate the problem to the use of text delimiters specifically:

Figure 3. In the rm.log file, this exception uniquely verifies that the error is caused by the delimiter and content. The underlined text mentions delimiters.

Figure 4. An example of one delimiter ending and another starting on the same line.

This issue might occur as follows:

Click Artifacts > Import > Import requirements from within a text document and then click Next.

On the “Select text document” page, select the document that contains the delimited text, specify the remaining import options, and then click Next.

On the “Specify how to identify requirements” page, select the artifact types, making sure that at least one valid text delimiter is included, as shown in Figure 1. Then, click Next. The error that is shown in Figure 2 is displayed.

Workaround

In the document, ensure that no two delimited portions of text are on the same line. To do so, after the last character of the first delimiter, press Enter.

Related information

Limitation summary

Re-authenticating from the Requirements Management application to IBM Rational System Architect fails

Problem

If your authentication session to Rational System Architect expires and you try to log in again from the Requirements Management (RM) application, the authentication process enters a continuous loop. This problem occurs because the RM application passes incorrect parameters to Rational System Architect.