It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884

question asked: May 06 '08, 7:26 a.m.
question was seen: 3,487 times
last updated: May 06 '08, 7:26 a.m.

Related questions

JRS 0.6M6a configuration problems

0
Inna Skarbovsky (16●2●1) | asked May 06 '08, 7:26 a.m.
Hi,
I have installed (unzipped) the new JRS 0.6Ma version. When starting up the server I got the "database not configured for JRS" message in the database status section of jazz admin console.

After playing with the repotools a bit I run the createTables script, and after that the db passed verification and started successfully.

Now I have another problem: part of the services do not start due to the following errors:

"Service Error Summary
com.ibm.team.jrs.rdfstore.IRDFStoreService
The service "com.ibm.team.jrs.rdfstore.internal.RDFStoreService" is missing the required configuration property "com.ibm.team.jrs.rdfstore.jdbc.user".
com.ibm.team.repository.common.internal.IItemRestService
The service "com.ibm.team.repository.common.internal.IItemRestService" was not registered.
com.ibm.team.repository.common.internal.IVirtualRestService
The service "com.ibm.team.repository.common.internal.IVirtualRestService" was not registered.
com.ibm.team.repository.service.IItemRenderService
The service "com.ibm.team.repository.common.internal.IItemRestService" was not registered.
jrs-services
The service "jrs-services" was not registered.
repo
The service "repo" was not registered."

Can anyone shed some light on this problem? Pls take into account that this is the default configuration for JRS, I have tried to start the server as is - with Tomcat and Derby DB, with no changes whatsoever!

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
James Branigan (11) | answered May 06 '08, 1:19 p.m.
Hi Inna,

I'm the component-lead for JRS. Feel free to use the jrs mailing list for these sorts of questions in the future.

You were correct to re-create the database to solve the first issue that you encountered. We've had a couple reports of this in the field, and recreating the database seems to resolve it. We'll try to figure out what happened in our build to avoid this in future releases.

The first error about the RDF store is letting you know that you are not properly configured, if you intend to store the index information in RDF form in DB2 Viper. You can still use the URL query that was available in previous builds with no problems. There is documentation in the JRS doc feature on configuring viper if you want to try that configuration.

The other errors can be safely ignored. They are there because JRS subsets Jazz components and there are a few of the services that get into the JRS build that aren't happy. The unhappy services aren't used in JRS, so the warnings can be ignored for now.

James Branigan

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.