IBM Rational Solution for Collaborative Lifecycle Management (CLM) release 6.0.1 was made available earlier this week. This release contains new features, quality improvements, and updates to supported platforms.
Check out the following resources for additional information
If Insight is integrated with CLM, after upgrading Insight, the "Test Connection" function might fail with the CRRE1421E error, but only in the RM XDC file, even though you downloaded the XDC file from the correct RM server.
Here is the detailed error:
'com.ibm.rational.dataservices.client.auth.oauth.OAuthCommunicatorException: CRRE1421E: Can not redirect to the OAuthentication identify URL.' is returned from the remote server through the tested URL. Please provide a valid URL in the URL field. If you still get this warning, please copy the correct "Relative path" from one resource of this resource group, paste it in the "Test relative path" field of the resource group editor, and click the "Test Connection..." button again.
You get this error even though you downloaded the RM XDC file from the correct RM server. The XDC files downloaded from the other CLM applications integrated with Insight can connect successfully.
This problem happens because the password in the RM XDC file is incorrect, as it was not successfully migrated during the CLM upgrade. To fix it, manually overwrite the password in the RM XDC file having the problem, after verifying that the login ID being used correct.
In addition to fixing the problem in the RM XDC file, you should fix the problem on the RM server, so the password is correct in future XDC file downloads:
Go to the RM Application Administration page.
Go to the Reports tab.
Click the "Data Warehouse Connection" link.
Fix the "Data Collection User Password or Consumer Secret" value so the existing password is replaced by the correct password.
Save your changes.
You may want to re-download the RM XDC file after making the above changes in order to verify that the updated XDC file works correctly.
If the Insight database is hosted on Oracle and the Insight Oracle user does not have the correct quota on the tablespaces in the Insight databases, the DCC web UI will show multiple symptoms as operations fail because the Insight database user cannot allocate an extent in the impacted tablespaces.
Common symptoms of this problem are:
The Data Collections Jobs status page no longer displays new entries.
The "Delete History" operation in the Data Collection Jobs status page fails with this error:
Error 500: CRRCD1500E An exception com.ibm.team.jfs.app.http.HttpPreconditionFailedException was caught in the class sun.reflect.NativeConstructorAccessorImpl from calling the function newInstance0.
Precondition Failed Error 412: CRJZS0220E The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.
Updates to settings in the Data Collection Jobs page fail with the error above.
You see errors like this in your application server logs:
ORA-01950: no privileges on tablespace 'ETLUSER'
Troubleshooting this issue
This problem generally happens when the Insight database user's quota on the tablespace referenced in the ORA-01950 error is 0 instead of -1 (unlimited). To determine whether you are having this problem, show each ORA-01950 error to your DBA and have your DBA verify that the IBM Rational Insight database user has the correct quota on the tablespace(s) referenced in the ORA-01950 error(s).
To fix the problem
To resolve this issue, the DBA needs to fix the tablespace allocation on each tablespace referenced in an ORA-01950 error -- the Insight database user's quota cannot be 0 (it is commonly -1, which means unlimited quota).
The Test Automation (Execution) adapter receives requests from RQM and then runs tests on the machine where the test tool is installed.
Before you try to run a test against a running Execution adapter, you can verify the adapter state on the quality management application on the RQM UI as explained below:
1. Navigate to the RQM project area, click on Execution > Adapter Console
2. The adapter's connected to this project area and the status
Note : Make sure that the adapter status is green before you run the test.
Is it possible to query adapters from outside of the RQM UI? Yes, it is possible to achieve it using RQM REST APIs; here is how...
1. Query execution adapters connected to an RQM project area using REST API:
Note : Replace the entriesserver, port, RQM Project Alias Nameand Project Area ID with correct values. Port value “443” is default for https The REST API queries can be conveniently performed using a REST client or a similar interface, other than a normal browser.
Step (1) Get the “Alias” name of the RQM project area using the link as below on browser:
Step (2) Use the link as below on the browser to get the Adapter List for the project area
2. Query the status of the execution adapter connected to an RQM project area using REST API:
Step (1) Get the “Project Area ID” of the RQM project area using the link as below on browser:
Step (2) Use the link as below on the browser to get the Adapter List for the project area
The procedure explained above can be used as input to an external application to consume the adapter query.
It may be that even though you successfully ran the Insight Setup tool to configure Insight, and the Setup tool had no problems connecting to the remote DB2 databases, neither Insight nor Cognos can connect to these databases.
If you have this problem, running an Insight report from Cognos Connection results in the error:
The logon failed
You may also see this error in cogserver.log:
Failure QE-DEF-0285 The logon failed.QE-DEF-0325 The logon failed for the following reason:RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: RIDW UDA-SQL-0031 Unable to access the "RIDW" database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.UDA-SQL-0107 A general exception has occurred during the operation "attach".
There are configuration problems that can prevent Insight from connecting to a remote DB2 database that won't impact Insight Setup because Setup tests the connection to the remote DB2 database via the JDBC thin driver, which is not impacted by configuration problems with operating system environment variables.
Things to check
If Insight is installed on a different server than DB2, find out whether the DB2 databases you cannot connect to from the Insight system were cataloged locally with the DB2 client (on the Insight system).
In addition, if you are using a 64-bit DB2 client on UNIX, please check your LD_LIBRARY_PATH environment variable to see if the 32-bit DB2 libraries are present.
To fix the problem
If using UNIX, and your system does not have the 32-bit IBM DB2 libraries in LD_LIBRARY_PATH, you should resolve this configuration issue as described in the DB2 considerations documentation.
Upon starting Rational Publishing Engine (RPE) Document Studio or generating a document using RPE Launcher, RPE checks out a license. If RPE does not successfully obtain a license, you will get a licensing error. This post explains how to resolve common RPE licensing errors. While this post is specific to RPE, these troubleshooting techniques can be used to resolve licensing problems in other Rational products that use FLEXnet licenses.
Usually, the RPE licensing error will be in a pop-up window titled "No License Available" with an error like:
Cannot read data from license server system.
The license server system appears to be running, but is not responding. If this persists, notify the System Administrator.
(The license server manager (lmgrd) and vendor daemon processes should be terminated and restarted.)
Hostname: license server host name
License path: port@host, full path to license file, or a combination of these; multiple items are delimited by a semi-colon
FLEXnet Licensing error:-16,287
For further information, refer to the FLEXnet Licensing documentation, available at "www.macrovision.com".
Licensing errors are more common in complex licensing environments -- for example, if USER_BASED licenses are used or in environments with firewalls that can block the license server ports. The following are common causes of licensing problems:
A firewall is blocking access to the license server port(s).
The license server is not running.
If you are using USER_BASED licenses, syntax errors in the license server options file can also prevent RPE from obtaining a license.
RPE can also fail to get a license if the license server or the licenses themselves are too old for that version of RPE.
Troubleshooting the issue
Before you can fix the licensing error, you need to figure out what is causing it:
Verify that all the information displayed in the error you get is correct. The information in the error will help you uncover problems resulting from an incorrect configuration -- for example, if the port or host name is wrong. You should also verify that the host name -- exactly as spelled in the error -- successfully resolves on the network from the RPE machine having the problem.
Look at the license server's license.log file to see what is going wrong. The errors in the license.log file will help you find problems with the licensing environment. The errors in the license.log file will uncover problems like:
The license server or license files are too old.
There are syntax problems with the license server options file.
The license server is not running.
The client workstation cannot reach the license server (this happens when you get a licensing error in the client but there are no corresponding entries in the license.log file).
If you see an error like the following: (lmgrd) Failed to open the TCP port number in the license.
That would indicate that either the port in the license server configuration (or license file) is incorrect, or that the license server port is being blocked by a firewall. It could also indicate that the license server is not running.
If you use USER_BASED licenses, check your license server's options file. Syntax errors in this file can prevent RPE from checking out a license. Generally, there will be errors in the license.log file (reflecting license denials) if there are options file syntax errors.
Fixing the problem
There are several things you can do to resolve licensing problems, depending on what is causing them:
In some environments, it is possible to swap out the USER_BASED licenses for regular floating licenses. If you are in such an environment and do not need the extra features from USER_BASED licenses, go ahead and make the switch, as floating licenses are easier to get working.
Whether you switch to floating licenses or not, make sure that the license server is pointing at the correct license file and that the port in the license file is available on your system (use netstat to check).
If needed, regenerate your license files or upgrade your license server.
Make sure the RPE workstation can reach the license server on the network. Some commands you can use to verify this:
If you need to use USER_BASED licenses, resolve any syntax errors in the license server options file.
Start (or restart) your license server:
if it is not running
if you changed the license file or the license server options file
If needed, reconfigure the RPE workstation to find the license server -- you would need to do this if you had to change the license server port. If the license server port is wrong, you will see that in the error details of the licensing error. To fix it, you will need to update the TELELOGIC_LICENSE_FILE environment variable on the RPE workstation.
Check out the two-part series on creating a reverse proxy configuration for CLM. Part 1 guides you how to setup and configure reverse proxy for a CLM environment using Websphere Application Server and IBM HTTP Server (IHS)
Part 2 of the series steps you through the Websphere configuration with IHS and how to setup the SSL handshake. Find both videos in the series below.
When planning your upgrades, you should review the product versions you currently have installed and check to see if they have reached (or are nearing) their end of support. There are a number of product versions that are scheduled for End of support in 2016.
Refer to the Support Lifecycle page for details about End of support dates for your installed product versions and releases. The End of support (EOS) date listed is the last date on which IBM will deliver standard support services for a given version/release of a product.
Here is a bit more information about Watson + Cognitive. Since debuting on Jeopardy! in 2011, we’ve brought Watson to the world. Are you wondering what the relationship is between Cognitive Business and Watson.
Well, “Cognitive Business” is a branded POV for the entire IBM Company, while “Watson” is the lead brand for IBM’s cognitive offerings.
IBM Watson: A business, solution, product or service that has cognitive capabilities at its core, that also meets very specific brand experience attributes.
Ex: IBM Watson for Oncology Powered by IBM Watson: A solution, product or service that has Watson capabilities as a featured enhancement. The ability to identify Watson as part of the solution, product or service experience is essential.
Ex: IBM Support, Powered by Watson IBM Watson Edition: An existing solution, product or service that is optimized for Watson.
To learn more about this exciting topic, click the link below:
Select your job from Builds and JobStreams > Jobs > CLMJobs. Right-click it and select Duplicate.
Create a job stream in the ETL you want to reconfigure to use DCC. (You can create the job stream by right-clicking in the background area where the job nodes are and choosing Insert JobStream Node.) The new job stream should reference the DCC job that you created when you followed the Integrating the Data Collection Component into Rational Insight instructions; if you used the defaults from these instructions, you would set "Business name" to DCCWrapper and set "Associated JobStream" to Jobs > DCCJobs > DCCWrapper in the JobStream Node Properties window of the new job stream you created. Do not close the JobStream Node Properties window, as you will be making further changes to it in the next 2 steps.
In the JobStream Node Properties window of the new job stream you created in the step above, set the predecessor to the Start node.
In the same window, set the successor to the ReorgCALM node, then click OK.
To collect data from all CLM applications that use the Data Collection Component, you need to disable the nodes between Start and ReorgCALM that are being replaced by the new DCCWrapper node and leave only the Data Collection Component job active. Here is an example of what the ETL would look like after the nodes are disabled:
Save the catalog.
Run the Data Manager job that you just edited by right-clicking it and selecting Execute. The console window shows the progress of the job.
The thought of migrating your ReqPro production environment to a new server can be daunting, but a well thought-out plan, combined with a series of specific steps, can be just what you need to put your mind at ease. You can follow this procedure if you will continue to use the same database after the migration, and the database is hosted on a separate server than ReqPro. Otherwise, the procedure will be more complex.
To migrate ReqPro from the old server to the new server:
If you are migrating a production system, notify your users and plan for enough downtime in advance. You may want to practice the migration on a test system first.
Install ReqPro and all other required software on the new server. If you plan to upgrade ReqPro during the migration, you will need to install new ReqPro software on the new server -- the Upgrading Rational RequisitePro instructions cover this in detail.
It is that time of the year where those of us in the U.S. are taking time off of work to celebrate our Thanksgiving Holiday. This is a time to reflect on things in our lives for which we are most thankful. As we share this special time with our family and friends we would also like to give a special Thanks to all our faithful followers and hope that you have many things to be thankful for as well.
As we go offline for our extended holiday weekend (we will be back on Monday) we would like to help ease your stress a bit during this holiday season with a link to a nice little helper: IBM Watson Trend
Join us February 21-25 at the MGM Grand & Mandalay Bay in Las Vegas, NV for our InterConnect 2016 conference. InterConnect offers a unique educational experience tailored to your needs with more than 2,000 sessions. From business breakout sessions to hands-on technical explorations, the InterConnect curriculum is designed to help you quickly and easily realize the full value of your investment—allowing you to accumulate a year’s worth of professional education in just one week. In addition to sessions, labs and workshops, you’ll also enjoy countless networking opportunities with more than 24,000 peers and industry leaders representing the full lifecycle of IT—from Cloud and Mobile developers to IBM executives and distinguished engineers.
Deploying Development Environments for Administrators, one of the many tracks available, will provide guidance to successfully deploy Rational solutions, whether on-prem, private or public cloud, as-a-service, or as a hybrid combination. Administrators need to decide upon the best operational contexts, preferred technologies, required service levels, and how to effectively reuse IT services. Explore how to optimize your development environments to meet your requirements and constraints including: high availability, disaster recovery, scalability, performance, security, integrations, monitoring and management.
If you haven’t yet upgraded to Collaborative Lifecycle Management (CLM) 6.0 and need some guidance on where to start, you may want to check out the Upgrade insider topic in the Deployment wiki on jazz.net. It includes information about important points you should be aware of as you plan your upgrade. It also contains work items of interest and a list of additional reference pages that you will find helpful to bookmark.
You may also want to refer back to some of our previous postings on the subject:
11/13/2015 5:40:54 AM: ERROR: <Unknown Caller Context>: The remote server returned an error: (400) Bad Request.
11/13/2015 5:40:54 AM: EXCEPTION: : The remote server returned an error: (400) Bad Request.
Debug log file:
Log file location : C:\Users\IBM_ADMIN\AppData\Roaming\Mso2Rqm\Mso2Rqm_Debug.log The uploaded content does not consist of well-formed XML or does not match the XML schema for testscript</ns2:message><ns2:trace>javax.xml.bind.UnmarshalException
org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1d) was found in the element content of the document.
11/17/2015 11:58:05 AM: sending testscript0 named US40.2-BU_Due_Date_Triggers-Assign_to_group
11/17/2015 11:58:08 AM: ERROR: <Unknown Caller Context>: RQMConnector: PutToServer - Error putting resource: https://clm404:9443/qm/xxx/service/xxx/resources/TCS%2bTesting/testscript/US40.2-BU_Due_Date_Triggers-Assign_to_group
11/17/2015 11:58:08 AM: ERROR: <Unknown Caller Context>: The remote server returned an error: (400) Bad Request.
11/17/2015 11:58:08 AM: EXCEPTION: : The remote server returned an error: (400) Bad Request.
11/17/2015 11:58:08 AM: at System.Net.HttpWebRequest.GetResponse() at Mso2Rqm_Common.RQMConnector.PutToServer(String url, String data)
Here's why this could be happening:
The error recorded here attributed to a Invalid Character inline with the plain text failing to get exported.
Here's how you can find the character:
1.Export the Excel to XML (use Export to File option).
2.Paste the XML into the POSTER utility and you can see any such invalid character’s and edit it accordingly.
Now fix the problem!
1.Copy the Excel Cell contents to a text editor and retype the erroneous text again and paste it back to the Excel cell.
2.Attempt re-import the script again.
Have you been looking for a way to provide IBM Support staff with a visual example that shows how to reproduce an issue you are troubleshooting?
You can help to cut down on the time spent in troubleshooting your issues by providing a recording of your screen as you reproduce your issue. A cross-platform, Java-based screen recording tool is available that enables you to record your screen, which you can then send to IBM Support (along with any other data that might be requested). This tool will allow you to record your screen while recreating a problem locally or to share a set of steps with IBM Support.
You might be familiar with Rational Quality Manager (RQM) REST API's to query your artifacts. TheRQM Reportable REST APIallows a user to perform CRUD type operations on test resources via XML sequences to the RQM server. This article describes about how to manipulate resources like (test case, test execution record, test results, etc..) in RQM using REST API
CFG files are used to import data into Rational Quality Manager. The file must be in a specific format for the import to work properly. Here is a sample CFG file created for associating a Single Testplan to Multiple Testcases. Also, each Testcase is associated with multiple Testscripts, which will allow you to use with IBM Rational Quality Manager (RQM) Excel Import utility.
// this configuration file will create a single test case from the defined cells and link to all
// test scripts in the same worksheet
// since we aren't defining an ID to use, the tool will create one based on the excel worksheet
// and workbook names
// We want to start looking for scripts after row 8
// the literal "execution" will be put into the step type tag, so all steps will be of type execution
// a new script starts when we encounter an empty row
// we want to use the data we got for each test script to create a test case
testcase.XLSWorksheetID="Testcase1" : "Testcase2"
// test case defined with definite cell locations
//Config for Testplan