Arun K Sriramaiah 2700076GE8 Visits (4790)
Enabling the RepoDebug service for Jazz Team Server (JTS) and Rational Team Concert (RTC) WebSphere Application Server (WAS) Liberty application server
The debug service is a general-purpose service that serves as the central location for finding various REST APIs that are useful for debugging. It was introduced into Jazz Foundation in v4.0.6 and is available for all JAF-based web applications.
Please refer the RepoDebug wiki for more details.
JeffLong 270005B0Q4 Visits (8171)
If you have installed IBM Tririga with WebSphere Liberty Profile, you may find a need in the future to update the JAVA version you are running in WebSphere Liberty Profile. If you need guidance on how to do so, please refer to the following documentation:
If you need additional assistance please contact support.
JeffLong 270005B0Q4 Visits (7342)
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.
GiuCS 270003E2P0 Visits (6125)
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:
RohitBalduwa 2700066W8H Visits (12604)
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: