I want to understand how people are running their QA organization to support TRIRIGA implementations. What kind of automation is being used? What challenges are being faced? I’m trying to start up a discussion around QA testing for TRIRIGA.
I have created a UX app in TRIRIGA, and I’m routing a page, but it’s giving me an error while loading the routed page. It’s showing an undefined data source. I have created the data source in TRIRIGA, but I’m still getting the following error:
I am getting a strange error when I am trying to deploy to TRIRIGA with the WebSphere Application Server (WAS). TRIRIGA doesn’t come up and throws an exception. Interestingly, when I point a Liberty application on the same DB2 database, it works well. I have confirmed with my network team that this is not a network connectivity issue. Here are the error logs:
Caused by: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: DB2 SQL Error: SQLCODE=-805, SQLSTATE=51002, SQLERRMC=NULLIDR1.SYSSH200 0X5359534C564C3031, DRIVER=4.18.60 DSRA0010E: SQL State = 51002, Error Code = -805...
Have you checked to see that both the Liberty server and the WAS server are actually using the exact same version of the DB2 driver (db2jcc4.jar)?
When publishing a drawing with Xrefs, the display state of the Xref layers is not carried over to the graphics section. Meanwhile, the base drawing layers do maintain their state when published. A couple related things:
- 1. If there are no existing or active layer configurations, the default behavior seems to be that the base layers will be displayed as they were in the drawing at the time of publishing. Meanwhile, the Xref layers will all be displayed regardless of their display state at the time of publishing. Is this the intended functionality?
- 2. There does not seem to be a way to save the graphics section display of layers. When you open the graphics section, it is displayed based on the state of the last publishing. (I’ll be looking into this further and will likely open a separate L3 request. There should be a way to save the graphics section display.)
We resolved this issue by removing the code that removes the Xref layers. Now, the Xref layer states and colors, based on the main drawing, are retained when publishing a drawing. Moving forward, the Xref layer display states and colors are correctly retained when publishing to the graphics section.
[Admin: To see other related posts, use the Xref tag.]
I would like to know if it is possible to use a UX login template, created as a UX view and accessed with the WebViewSync.jar, as the ALTERNATE_INDEX_HTML. Currently, I have this configuration in the TRIRIGAWEB.properties:
- ALTERNATE_UX_LOGIN_VIEW: cstMeetingRoomsManagerViewAutoLogin
I would like to use the same login page in both places, accessing classic TRIRIGA normally, and also accessing a UX application. Can I set something like this?
- ALTERNATE_INDEX_HTML: cst-meeting-rooms-manager-autologin.html
- ALTERNATE_RESOURCE_DIRECTORY: /root/tririga/p/web
Currently, TRIRIGA does not support using a UX login view as the ALTERNATE_INDEX_HTML. That’s because of the dependency from UX views to Polymer libraries and UX components.
[Admin: To see other related posts, use the Alternate tag.]