If you used to work on Real Estate Leases and Generate Payment Schedules before 3.4.2 you know that every time you need to copy a Payment Schedule, you would need to open the record, click More.. and click Copy.
As Copy was the only action on that More.. button, development made a decision to move this out and have it aside Copy and Copy&Close. The issue is that for base 3.4.2/10.4.2 the More button was removed and the copy one never placed in the form. It was fixed in 10.4.2.1, so in the following fixpack.
So you are going to test 10.5 for evaluating an upgrade and the copy action is missing. This was a regression fixed in the most recent 10.5 fixpacks.
Chris K 270004Y3TR Visits (8687)
If you have run into an issue while deploying the IBM TRIRIGA application in any of your lower environments (UAT, DEV, TEST), then you may have seen the Support engineer asking questions regarding your deployment window. In truth, we would rather have this information in advance of any production deployment, regardless if you have run into an issue that you report to the IBM TRIRIGA support team.
There are three reasons why it is important to get this information to the TRIRIGA support team. First, we may know of some potential issues that may crop up during the upgrade process, regardless of whether you are performing an application upgrade versus a platform upgrade. Second, when you have open PMRs with the TRIRIGA support team, those that could potentially impact your go-live timeline will be viewed with a more critically eye with regards to defects and the versions of either the application or platform. In both of these cases, there is a strong potential for a change in your implementation timeline. In the first case, the potential issues may require you to upgrade to a later release where the problem was resolved. In the second case, you may have identified a previously unknown issue that cannot be resolved with any existing releases and may require a fix pack release to the application and/or platform release to which you are upgrading. The third reason why it is important to know your implementation timeline is to insure resources are prepared to respond during your production roll out. While the support team is prepared to respond on a 24/7 basis regardless of any implementation schedules, we need to insure that development resources are aware and also prepared should a problem occur during your production implementation.
Just as you would rely on your internal resources, the TRIRIGA support teams are also resources on which you need to rely during your upgrade processes. Keeping us in the loop early on in your process will allow us to work with your implementation team as a single team rather than a separate group with whom you only need to tap when an emergency arises. Our early involvement is meant to prevent such emergencies and make the upgrade process proceed as smoothly as possible.
In the weeks ahead, I will be generating communication templates for the TRIRIGA support team to insure we begin to get deployment information from you, our customers. It is my hope that this blog provided you with sufficient insight into why this information is critical to your success during the upgrade process.
AcdntlPoet 2700019V2G Visits (8261)
Maximo Watson Reactive Work Storybook- Highlights use of Maximo Asset Management with Watson Analytics using Watson's Storybook feature.
doboski 310000SJR4 Visits (9461)
When TRIRIGA discontinued using JBOSS, many clients lamented over losing a light, low cost but efficient application server for running TRIRIGA. In its' place came WebSphere Liberty, a lightweight version of the traditional WebSphere application server. Starting with TRIRIGA release 3.4.2 in the summer of 2015, WebSphere Liberty is now packaged and shipped with TRIRIGA and can be installed through the TRIRIGA platform installer. Now it begs the question, what is the difference between full blown traditional WebSphere and WebSphere Liberty and why would I use one over the other?
Traditional WebSphere is a full blown application server with many features including deployment manager, node manager, and administration console functionality. Usually, companies who deploy it have a dedicated team that has the knowledge of Traditional WebSphere and has support for it. For smaller operations or organizations without WebSphere knowledge, the software may be too complex and too expensive to run. Given the large, complex nature of Traditional WebSphere, it can take a long time to even install it. Even longer if you are using multiple servers because you need to install WebSphere on each server you are using. TRIRIGA only needs a small portion of what WebSphere has to offer and does not support some of the more complex functionality anyway. So if you do not need something on that level, why use it? Why not go for the simplified version?
WebSphere Liberty is a light weight version of Traditional WebSphere. It does not have nearly as much overhead, nor does it require a dedicated team to install, run and support, like its' bigger brother. The beauty of Liberty is that comes with TRIRIGA and is very easy to install! Not to mention it does not take long to install compared to Traditional WebSphere. The TRIRIGA installer includes Liberty so when you run the TRIRIGA install, you have the option to install Liberty without any additional files. When you select Liberty in TRIRIGA, it makes the process seamless. There is no console to worry about. Liberty has all that TRIRIGA needs to run. After the install is complete, all you do is start up and batch file and you are up and running.
I bet you might be wondering; I need to use Traditional WebSphere because we are using SSO and I may not be able to use Liberty? Au Contraire. You are able to configure TRIRIGA 3.4.2 and greater on Liberty with Microsoft IIS and Active Directory. For details on that, I will direct you to this wiki for information on that.
Can Liberty be setup as a service like Traditional WebSphere? This is a bit more complicated and I encourage you to check out a colleague's blog entry on this subject.
In the end, you need to decide what will best suite your needs. In some rare cases, Traditional WebSphere maybe the way to go, for example if your company has a dedicated WebSphere team but in most cases, Liberty will work best. It's good to have options and know what the benefits are. To help you understand the benefits, you may want to look at this wiki page.
JeffLong 270005B0Q4 Visits (10449)
Note: This tip can be used with reports from the System Reports tab in My Reports or Report Manager.
You can follow the steps below to troubleshoot Tririga reports and see if the SQL returns data:
If the report SQL does not return data, then that explains why the report is not returning data, there is no data for the report to display. Add data and test the report again, the report should return data if the SQL does.
If the SQL returns data but the report does not display data, this is likely a report problem. To troubleshoot this, refer to information available online or contact support.
We sometimes hear in support, that TRIRIGA performance is slow. No other details are given. That doesn't help us out a lot. We need to know more, like what was going on at the time that? Is it impacting the entire system or just one area?
Performance of TRIRIGA is a bit complex. and there is rarely any one thing that can be done to improve performance. Performance can be impacted by hardware, network connectivity, software versions, queries, indexes, customizations, configurations and more. The answer to performance concerns is often solving some combination of these things. But some things can be reviewed to help point you into a direction where to look and what to do.
Some things like hardware and network connectivity are out of our control and need to be reviewed by your own IT department or a business partner to perform a health check or performance analysis on your system. We do provide a list of minimum hardware requirements that TRIRIGA should be running on in our installation guides. We also have a compatibility matrix to show you what configurations are supported for your particular version here: http
To help diagnose the problem, TRIRIGA has performance logs that can be enabled, retrieved and analyzed. There is a wiki page that describes the process of enabling the performance log files as well as analyzing them, which can be found here:
The wiki will walk you through how to enable the performance log and then analyze the output.
In case of performance concerns, TRIRIGA Administrators should ALWAYS review best practices to ensure they are following recommendations before entering a PMR. The wiki regarding Performance can be found here: http
Once you have the performance log, you can create the following pivot table to help identify where something is taking too long.
Generally, if something is taking longer than 10 milliseconds then it is taking too long to. For instance, in this example, you can look at the query for the report and see if it is optimized correctly. You may need to look at your database to see if anything needs to be adjusted at the database level.
It should be noted, that if you are using multiple servers in your environment, you would need to access the console from the server that is having the problem. If you have 3 UI JVM's and 2 process servers, where one of them is the workflow agent and you know you are having issues with workflow performance, then you would access the console from the server that has the WF agent running.
So using the performance log can help you identify what could be taking so long and if you enter a PMR that is something that can help us out as well. It is important to remember, that TRIRIGA Support is committed to every clients success, however; performance is not typically covered as part of the support agreement. Our goal will be to help point you in the right direction but since most performance inhibitors are unrelated to TRIRIGA, the support team cannot commit to resolving performance related issues. We may advise you but the resolutions are often up to you.
JohnONeill 270004JPGF Visits (9378)
You may encounter an issue where the MS Outlook Reserve Add-In is not functioning properly. What you see is that the Book Selected Room button flashes briefly nearly off the page such that you can only see the left edge, then the Book Selected Room button disappears. Also the Book Selected Room button at the bottom and most other controls never come in to focus. Other controls do not function and no reservations can be made.
Following is an image of the MS Outlook screen in question.
This may be caused by a configuration of Registry and IE Compatibility Mode setting.
Resolving the problem
It is necessary to ensure that the correct registry entry exists AND that Internet Explorer Compatibility Mode is not set.
Here is a link to the Microsoft web page that describes the FEAT
JeffLong 270005B0Q4 Visits (10540)
Planning for a new install or migration of an existing IBM Tririga install can be a complicated endeavor because there are so many different possible configurations for the IBM Tririga n-Tier architecture. Below are some links that will help you with your planning.
This is a lot of information to go through, but taking the time to review this information during your planning phase of your install or migration will allow you to make informed decisions based on your intended use of the IBM Tririga product and plan accordingly.
Chris K 270004Y3TR Visits (9590)
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 (11821)
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 (10880)
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 (10328)
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 (8962)
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.
Shradha_S 270007543G Visits (4834)
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 (8071)
Maximo supported versions and fix information March 2016 - Get to know Eleri Gregory and Navin Desai as they discuss info
GiuCS 270003E2P0 Visits (8234)
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 (8693)
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 (8790)
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
GiuCS 270003E2P0 Visits (10398)
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 (6124)
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 (11680)
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.
AcdntlPoet 2700019V2G Visits (9392)
Maximo 7.6 JSON API - Getting Started: Session 1 covering an introduction to the Maximo JSON API
dmmckinn 1200006SCS Visits (11789)
The Jazz architecture allows for multiple instances of specific application servers, such as the Change and Configuration Management (CCM) application (Rational Team Concert), Quality Management (QM) application (Rational Quality Manager) and Requirements Management (RM) application (DOORS Next Gen). These application servers are registered to a common Jazz Team Server (JTS) to form a CLM Instance. The architecture further allows multiple CLM Instances to be formed. You should be aware of the tradeoffs and architectural considerations when multiple instances are needed in order to scale to support your user population/load.
The following article on jazz.net provides details about application, server and architectural considerations in addition to functional differences that you should review while planning: Planning for multiple Jazz application server instances
Romain_Barth 2700076HKB Visits (6590)
In DOORS 9, it is not possible via the user interface to manage the "baseline power" for users.
But it is possible to modify the original behavior of DOORS by editing a DXL file and by creating a "special" group for those users.
When a user attempts to create a baseline from the UI, this code will be executed and only users in the group will be able to create baseline.
dmmckinn 1200006SCS Visits (12366)
In an effort to continuously deliver product enha
Check out the following downloads which include information about product enha
RohitBalduwa 2700066W8H Visits (11637)
A tag is a defined value that you can add to configurations to filter the artifacts.
Use content assist to conveniently tag work items in the Eclipse client or Web UI work item editor.
For a particular Project Area, you can identify a list of tags available in work-item in IBM Rational Team Concert (RTC) and export them.
RohitBalduwa 2700066W8H Visits (12602)
With the new CLM 6.0.1 and upcoming IBM Rational Collaborative Lifecycle Management (CLM) releases, IBM WAS Liberty has replaced the Apache Tomcat application server. The current documentation will not assist you to configure the WAS Liberty to run as a Windows service.
There is an existing Enhancement Request for the same:
As a workaround, you can use the Apache Commons Daemon as an option.
Steps to create the service using Apache Commons Daemon to run CLM 6.0.1 in IBM WAS Liberty:
RohitBalduwa 2700066W8H Visits (13640)
Eclipse Memory Analyzer Tool (MAT) for analyzing heap dumps and identifying memory leaks from JVMs and reduce memory consumption.
This supports the IBM system dumps, heap-dumps and Sun HPROF binary dumps.
Provides memory leak detection and footprint analysis, shows areas of memory wastage. Displays Stack trace with object references.
Overview of the dump including Java heap size and total number of objects
Path to GC Roots
Provides the reference chain that prevents an object being garbage collection. Displays Stack trace with object references.
Dominator Tree grouped by Class Loader
Provides memory leak detection and footprint analysis Objects by Class, Dominator Tree Analysis, Path to GC Roots, Dominator Tree by Class Loader.
As a use-case to troubleshoot or identify the problem, MAT has been used to analyze the memory leak:
Chris K 270004Y3TR Visits (9478)
After installing CAD Integrator on a CAD users machine and assigning the appropriate security groups and licenses, does the user get an error indicating that they do not have a valid CAD Integrator license? Do not panic! This blog is meant especially for you.
The likely cause of the problem is that a problem occurred during the license assignment process. First, double check that the users profile contains the license. If it is missing there, be sure to add it. Second, go to License Manager and click on the radio button next to IBM TRIRIGA CAD Inte
Chris K 270004Y3TR Visits (10218)
Have you upgraded your IBM TRIRIGA platform only to find that you cannot see any of the graphics that were visible in your previous platform release. If so, you may want to reprocess your drawings.Please note that reprocessing your drawings can take some time, so you might want to plan this process to run during off peak hours.
To reprocess your drawings, follow these steps.
1 - As an application administrator, login to the IBM TRIRIGA Admin Console.
2 - Click on the radio button next to Database Manager
3 - Click on the link titled "Reprocess published drawings".
Under certain conditions, the reprocessing of your CAD drawings may have encountered issues during the upgrade process. It is important to always review the server log file from the 1st server startup after an upgrade. In the case of your drawings, look for "Reprocessing" in the log file. Most of the entries after that line will contain information about the reprocessing of each individual drawing. If a drawing is processed without issue, you should see a series of 7 informational messages starting with "DXF: Processing Header "to "DXF: EOF" if there is a problem during the reprocessing process, you will likely see either an error or warning message between those two informational messages. If that is the case, you will want to follow the steps outlined above once the upgrade processing has completed on that 1st server.