JeffLong 270005B0Q4 Visits (7332)
We have had a few customers contact us because they could not start or stop Tririga on IBM WebSphere WAS Liberty Profile. We found that the way to resolve the issue was to implicitly run the batch file as Administrator on Windows OS.
If you have a need to restart Tririga on WAS Liberty Profile in Windows you must first find your tririga_root install path. If you used the default for the installer, this should be C:\IBM\Tririga. If you are not sure of the location, you can search for the following files (these should be in the Tririga \bin directory.): "run.bat" and "shutdown.bat"
To stop Tririga, navigate to the trir
Alternatively, on Windows servers, you can open a command prompt and run the command to shut down the Liberty profile: trir
To start Tririga back up, navigate to the trir
Alternatively, on Windows servers, you can open a command prompt and run the command to start the Liberty profile. trir
If you need further assistance please contact IBM Tririga support.
dmmckinn 1200006SCS Visits (10141)
Have you been looking for CLM-specific performance datasheets and sizing guides? Well, look no further. Below is a list of performance related articles that our CLM folks have pulled together and published on the
Deployment wiki on jazz.net.
The datasheets below are updated when performance testing shows a significant change. The 6.0 datasheets apply to the 6.0.1 and 6.0.2 releases. Note that there were major updates to the performance datasheets between the 5.x and 6.x releases.
A more complete list is available at Performance sizing guides and datasheets.
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 (8678)
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 (8253)
Maximo Watson Reactive Work Storybook- Highlights use of Maximo Asset Management with Watson Analytics using Watson's Storybook feature.
doboski 310000SJR4 Visits (9450)
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 (10427)
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 (9368)
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 (10523)
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.