Chris K 270004Y3TR Visits (9268)
Having been on the customer side of the IBM Support dialog, I often wondered why I was always asked for version information for my PMRs. Now that I have been working on the IBM TRIRIGA Support team, I understand why. The purpose of this blog will hopefully shed some light on this for the customers as well as improve the customer experience with the IBM TRIRIGA support team.
What the IBM TRIRIGA support team will be doing in the weeks ahead to help make things a bit easier is ensuring we have up to date information about customer versions of the IBM TRIRIGA Application Platform, IBM TRIRIGA CAD Integrator (if applicable), and other third party components required for a running the TRIRIGA application. To that end, we will be asking for information from you if you open a PMR without including the version information for the IBM TRIRIGA issue (whether it is an application, platform, or CAD Integrator issue). Additionally, if you do not indicate what environment this issue applies to and the associated version information for that environment, we will ask for that information as well.
What you can do to help is to provide this information up front when you open a PMR. I suggest keeping a document with the environment configuration information. Having been on the client side of this picture, I know how I ended up making the IBM PMR process easier for me. Knowing that I would be asked version information right out of the gate, I kept a document which had the version information for the main product as well as versions of other products in our configuration that could have an impact, in any possible way, to the problem being reported. I found that this greatly smoothed out the initial response from the support team I was working with and also led to quicker turnaround time on the PMRs I submitted. While I cannot guarantee that the PMR turnaround time will be significantly improved, it should at least reduce multiple communications regarding the configuration of an environment. The main reason for back and forth about version information that I have seen is that the support team assumes the information provided will be all that is initially required to work the problem. While working and researching the issue, we may come to find that we need some additional version information (think operating system, 3rd party tool versions, etc...). Having the information up front when you open the PMR should prevent this from happening.
What I, and the rest of the IBM TRIRIGA Support team will do is look for this information on any new PMRs. If the information is provided in the PMR, we will check to see if the information has been stored on a customer record that we have set up in a tool we share with our L3 engineers. If you provide information and that customer record is not up to date, the engineer will update the information based on what was provided when the PMR was opened. If the information is NOT provided in the PMR, the engineer should ask for all of that information. I know that several of our clients are already familiar with that process and are providing that initially. We will do our part to smooth this part of the PMR process.
If you found this information helpful, please be sure to "like" it and be on the watch for my next blog regarding deployments.
RohitBalduwa 2700066W8H Visits (11360)
You might encounter some problems where the Lifecycle Project Administration (LPA) projects and templates are missing, or application dashboards are not loading post upgrade activities or any sudden database or application failure.
The direct solution is to run re-index for the application. This will regenerate the metadata (query triple store and Lucene text store indexes) required to load the page.
Error instantiating the template....
Error deploying predefined templates....
Example (click the images below for larger views):
In-case the indices are corrupt or missing, error seen on LPA admin page:
Post jts reindex done, the LPA templates and projects will be visible now.
For LPA templates, the metadata is in the jts application, so just reindex of jts will help.
Note: Collecting logs will not help you and either run the firebug to troubleshoot further.
For Dashboards, run it for JTS and the corresponding application.
Important: You must shut down the server before you run the command.
Chris K 270004Y3TR Visits (10341)
Configuring secured SAML with WebSphere requires web pages to be protected. The design of the TRIRIGA application does not currently allow you to set up the EAR or WAR (depending on TRIRIGA platform release) to include web page protection. The ability to protect the web pages in this manner would require a major change in the TRIRIGA platform, so this would not be viewed as a defect but as an enhancement.
So, what can I do to get this level of security? Your best option is to check the Request For Enhancement (RFE) site to see if someone has already requested that this be required in a future release. If an RFE exists, vote for it. The more votes an RFE has, the more likely it is to be included in a future release. If an RFE does NOT exist, create one and be sure to go to the Service Management Connect (SMC) forum and solicit votes for your enhancement request. Below is information about the RFE process that I provide to customers when a PMR leads to this sort of issue.
You might consider submitting an enhancement request via the Tivo
On the RFE page, there are 2 pick lists under the title Filter the page content by brand and product that will help you start the search process for existing RFEs regarding the TRIRIGA application. Set the left hand pick list to Internet of Things and set the right hand pick list to IBM TRIRIGA Platform. Next to this right hand pick list is an arrow pointing right. Click on it and the list will automatically filter based on the selections in the pick lists. Underneath these pick lists is a search text field. You can enter text there to further refine your search. For this issue, I typed SAML in that field and clicked the Enter key. There are 2 RFE entries listed as a result. If, after reviewing the entries, you determine they do not fit your requirements, create a new RFE. If the existing entries DO fit your requirements, vote for them.
Inside each RFE record is an ID field. This field is immediately below the title of the RFE. In order to solicit votes for your RFE, navigate to the SMC forum for IBM TRIRIGA Platform and create a new forum entry with the title of your RFE. In that forum post, be sure to include the merits of your RFE and provide the ID. This will make it easier for people who want to vote for your RFE to find it via the RFE home page. Remember, the more votes for a particular RFE, the more likely it is to be considered for a future release of the IBM TRIRIGA Platform.
dmmckinn 1200006SCS Visits (9995)
Looking for information to help with the planning and installation of your IoT Continuous Engineering solution?
The IBM Internet of Things (IoT) Continuous Engineering Solution is an integrated solution for systems lifecycle management. The combination of products, components, and practices is built on an open integration platform so you can share plans and requirements, model artifacts, and manage testing while applying best practices and built-in process guidance.
Below we have pulled together a collection of reference material from the Deployment wiki on Jazz.net:
AcdntlPoet 2700019V2G Visits (8614)
Faster calibration with Maximo Anywhere - Calibration on Work Execution enables you to complete your calibration work orders in the field, in disconnected and connected environments. With it's simplified UI, you can quickly capture the calibration data that you need and receive immediate tolerance validation.
dmmckinn 1200006SCS Visits (10763)
Knowledge sharing: Below are the top 20 technotes for our Maximo, Tririga and Continuous Engineering products that were most accessed on the web thus far in 2016. We hope that highlighting them here will provide you with the information you need to avoid issues or find quick answers as you work through your
Shradha_S 270007543G Visits (4646)
If you are using RTC's Pessimistic locking feature, it doesn't work for third party editors like Microsoft Office.
For the above issue, a defect has been identified with third party editors. Below are links to the related defects:
--> Open any Microsoft Office extension (.docx) file using "Open with" option in external editor, the file remains in read-only mode and saving change in the files gives an option to do a "Save As", rather than updating the original file.
To summarize, the read-only doesn't work if the file is edited with Eclipse embedded editor, but the same works if the files is opened using an External editor.
You can also refer the below link for more details:
AcdntlPoet 2700019V2G Visits (7831)
Maximo supported versions and fix information March 2016 - Get to know Eleri Gregory and Navin Desai as they discuss info
GiuCS 270003E2P0 Visits (7967)
This is for those of you who have more than 1 application server setup!
After spinning off the TRIRIGA application server into 2 separate application servers you are checking all to see if the second application server is set as the original one, the Licenses in the second application server show 'No' in the Licensed column in Administration > System > License, but the licenses have not expired.
First thing you try is to use a user id to log into this application server. There is no problem in the front-end application, any users can log into both application servers.
This was observed before as a cache issue. Sometimes during installation of a second application server the licenses at first have a problem fetching the correct status from the database and this information gets stuck into there.
What you need to do is to go to the Administration Console and Clear the Global Cache. Log back into the application and check the Licenses again. In most cases this is resolved as it is just a misalignment from the actual database information and what is cached.
If not, contact IBM support.
More information about cache clearing: How
Romain_Barth 2700076HKB Visits (8457)
Moving a linkset from a link module to another link module in DOORS 9.
The DOORS 9 client does not provide such a feature. However, it is possible to perform this task by running a DXL script.
AcdntlPoet 2700019V2G Visits (8357)
Getting Started for Gateways in IBM Watson IoT Platform - With the introduction of the concept of gateways to IBM Watson IoT Platform, applications can receive data and control devices which are connecting through a gateway. Gateways are specialization of devices, because they share almost all of their characteristics and behavior with regular devices (events, commands, device management). Gateways have the additional permission to register new devices and act on behalf of a device that is assigned to the gateway. To support gateways a new property was introduced in device type. This new video demonstrates how to get started with Gateways in IBM Watson IoT Platform. Find out more at
New White Paper: MinGW with IBM Rational Rhapsody" provides information about how to set up a MinGW environment with IBM Rational Rhapsody
dmmckinn 1200006SCS Visits (8595)
A new white pape
This paper provides information about how to set up a MinGW environment with IBM Rational Rhapsody and includes information on the following topics:
Looking for other Rhapsody product documentation and support resources?
Preview our new IBM Support Portal beta at: http
GiuCS 270003E2P0 Visits (10030)
You are glad that after connecting your Eclipse BIRT environment to your TRIRIGA Database, and using a SQL Query you build your own very first report.
You preview it in BIRT and the report runs just fine, pulling data from the database and displaying within the format you set. It is a good looking report you think and my users will love it!
Now it is time to see it running in TRIRIGA, so you read the instructions that say you need to import it to Document Manager as a ZIP file to be used in a System Report running an External Query, and you think: Easy!
You get back to Eclipse and export the report. There are a lot of options to export it and you go for the "Archive File" one, that gives you the option to select as a zip what is the exact file you need to upload to TRIRIGA Document Manager, how convenient.
You import it to TRIRIGA, create a System Report, point to the zip file you imported to Document Manager and the report does not run, throwing an error in the front-end. Depending on the browser it could be an HTTP 500 error or a MID-xxxxxxxxx error.
What could be wrong?
Well, although BIRT Eclipse gives you the convenient option to export the report as a zip file, that zip file will preserve the folder structure from your Workspace panel (usually on bottom left of Eclipse Report Designer view).
TRIRIGA needs that the .rptdesign file inside the zip is located on the zip file root. If not, the report will not run. See the Bad and Good examples below:
In case you set the BIRT Flags in the Admin Console - Platform Logging and reproduce the issue you will see an error in server.log like this:
2016-04-18 13:11:04,682 ERROR [com
A very amicable message in the logs!
GiuCS 270003E2P0 Visits (5785)
Well, you get TRIRIGA 3.4.2 or later to install and see how cool to use the Liberty Profile for WebSphere Application Server (WAS). This lets you install both the web server and TRIRIGA at one strike and self deploys itself from TRIRIGA installer. What an easy deal!
After installing TRIRIGA and the WAS Liberty profile, the user logged into the service and running it cannot log out or the service will be stopped. Many businesses do not allow an Admin user to be logged in indefinitely.
Now you're thinking you have to install all over again in a WAS deployed first. You double check and see WAS Liberty cannot run as a service as a product limitation. What a drag...
Well, there is one workaround you can try. Using the Apache's daemon you can create a Windows service. The following instructions are an idea for how you can implement it, but it depends on your architecture and installation:
Note: If you run into any issues, check the logs in the LogPath directory location for any errors - the errors as listed in the event viewer logs from Windows do not give meaningful errors.
There is an RFE to implement this and I encourage you to vote for it:
Sizing recommendations for planning migration of data from Rational DOORS to Rational DOORS Next Generation
paulellis 270001KTVW Visits (11277)
Are you considering migrating your data from Rational DOORS to Rational DOORS Next Generation(RDNG)?
Are you looking for guidance and best practice before you begin to be successful first time?
If so, then your starting point is definitely the detailed guidance on developerWorks on how to Migr
New Sizing and Best Practice Guide on Jazz.net's Deployment wiki
Since the developerWorks article was published, we realized that more detailed sizing information was required prior to executing the migration of data packages from DOORS 9 to RDNG. We collated pertinent sizing information from the Rati
There are significant improvements to the import timings with RDNG 6.0.2 release, so please refer to this article if you are evaluating an existing or future migration as this could indeed be an influencing factor.
The document details:
Sizing Guidelines for Rational DOORS Next Generation 6.x
Recommendations on the maximum sizes of your modules, projects and repositories so as to maximize your success when importing your packages and working in the future within RDNG.
The considerations for hardware are simplified from guidance published elsewhere in the Deployment wiki, but here they are explained within the context of how to plan for your new world.
Guidance on how to convert your Rational DOORS modules prior to migration
Invariably there will be modules and projects within DOORS 9 which will not match up to the guidance prescribed for RDNG. Use this section to understand how to easily manipulate your data before migrating.
What if the data to be migrated exceeds the recommendations?
The guidance is clearly aimed for the general use cases and is very much our strongest recommendation.
It is understood that there are very large enterprise requirements management estates out there. It is recommended that you contact IBM if this applies to you.