Troubleshooting OSLC
The following tips can help you troubleshoot issues when you are an OSLC consumer of IBM® TRIRIGA®.
| Concern | Remedy |
|---|---|
The resource shape no longer works after you rename the IBM TRIRIGA report |
If you rename the IBM TRIRIGA report that is defined in a resource shape, it breaks the resource shape because the defined report no longer exists. You see an error message when you preview the query capability or use the creation factory. The general practice is to update the resource shape when the name of the report changes. Also, if either the module or the business object changes in the IBM TRIRIGA report, that value must be updated in the resource shape as well. The Where Used tab in the report identifies which resource shape is using the report. |
Need logs to debug the OSLC implementation |
Logging is managed in the IBM TRIRIGA Administrator Console. After you log in, select . To turn off logging, clear the OSLC check box. For more information, see the IBM TRIRIGA Application Platform 3 Administrator Console User Guide. |
Stack trace is thrown in olsc.where |
If you put single quotation marks in an oslc.where parameter, you create an invalid URL. The exception comes from an Apache filter that occurs before the oslc.where reaches the OSLC servlet. It is not within IBM TRIRIGA control. |