RRM DB2 Connection problem
Guys , i'am trying to complete the jts/setup and on the RM configuration part :
I get an error.
I know that the RM database shares the database with JTS , but where do i tell RM that he is sharing with JTS the database , i noticed that in my RM folder there isn't a teamserver.properties that would allowed me to do the manual configuration.
The SystemOut log says:
[24/07/13 12:43:18:472 CLT] 00000064 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[equinoxbridgeservlet]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: CRJZS5787E The following RDF index cannot be read or used: indexer.internal.triple. Query-based operations do not work, and the application might not work at all. Before you can continue, this issue must be fixed. For more details, open the help system and search for CRJZS5787E.
(I'am using :Windows Server 2008 R2 & WAS 8.0.0.4 & CLM 4.0.1 & DB2 9.7)
Am i missing something? Help please
One answer
RM uses JTS for storage, and does not directly access the database; RM talks with REST services with JTS to store and retrieve its data.
So during the JTS setup wizard, after you register the RM application, RM knows enough to talk to JTS.
Hence no teamserver.properties. RM uses fronting.properties and friendsconfig.rdf to store its configuration.
I can't really read your image to see what error is reported on the RM finalize page. Can you copy that info here?
So during the JTS setup wizard, after you register the RM application, RM knows enough to talk to JTS.
Hence no teamserver.properties. RM uses fronting.properties and friendsconfig.rdf to store its configuration.
I can't really read your image to see what error is reported on the RM finalize page. Can you copy that info here?
Comments
Mike Jaworski
JAZZ DEVELOPER Jul 24 '13, 1:33 p.m.Have you tried taking a look at the server diagnostics page? It's possible that there may be a clue as to why this is happening there. The page is located at /jts/admin#action=com.ibm.team.repository.admin.serverDiagnostics