It's all about the answers!

Ask a question

Problems installing the RTC Server into WAS 6.1


Sergio Deras (14613) | asked Aug 12 '08, 5:41 p.m.
JAZZ DEVELOPER
I have several question about installing Jazz server 1.0 into WebSphere Application Server 6.1, I am able to install it, but at the end, when I run the jazz setup, first the Derby database cannot be accessed, the site says that the DB is responding, but the tables are not for Jazz use. Then I create the tables with the repotools, but at the very end, the site says that it cannot write the repository properties.
This is happening over Red Hat Ent 5 and Windows Vista Bus Ed.
Do you think that this is because of the OS?
If you have a more detailed guide, can you lend it to me?
Note: Yes, I follow all the initial guide by the book. I am using the Derby DB, is this a problem?
Thank you very much.

4 answers



permanent link
Matt Lavin (2.7k2) | answered Aug 12 '08, 6:53 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I'm sorry you are having trouble. Using Derby with WAS is possible, but
takes one extra step compared to DB2. When using Derby with WAS it
works best if you specify a fully qualified path to the Derby DB in the
teamserver.properties file.

The problem you are seeing is not likely because of your OS choice. One
thing to check is that you have the latest WAS fixpacks, both for the
application server and the VM.

About the failure to write the repository properties, have you checked
that the teamserver.properties file (and the directory it is in) is
writeable by the user who is running the WAS process?

Matt Lavin
Jazz Server Team


sderas wrote:
I have several question about installing Jazz server 1.0 into
WebSphere Application Server 6.1, I am able to install it, but at the
end, when I run the jazz setup, first the Derby database cannot be
accessed, the site says that the DB is responding, but the tables are
not for Jazz use. Then I create the tables with the repotools, but at
the very end, the site says that it cannot write the repository
properties.
This is happening over Red Hat Ent 5 and Windows Vista Bus Ed.
Do you think that this is because of the OS?
If you have a more detailed guide, can you lend it to me?
Note: Yes, I follow all the initial guide by the book. I am using the
Derby DB, is this a problem?
Thank you very much.

permanent link
Sergio Deras (14613) | answered Aug 13 '08, 1:56 p.m.
JAZZ DEVELOPER
Thanks for the answer, but any of this resolve the problem, I have changed the teamserver.properties file, adding the path to the repository. It works, but the final resulta is the same. Before the jazz setup ends, a message "An error occurred while saving the configuration properties. Please check your server log for more details".

The server log just shows INFO and WARN messages, the last WARN message is just refered to the disabling of the ADMIN user, and the files ends there.

I have changed the permission and check the owner of the proccess, the folder and the file everything is owned by the root, but I have also enabled the "others" to read and write, create and delete files.

The problem persist. Any other thing that I can try? Thanks.
I have not found any fixpack to download, I am using a Trial.

All of this over Red Hat 5 as root user.

I'm sorry you are having trouble. Using Derby with WAS is possible, but
takes one extra step compared to DB2. When using Derby with WAS it
works best if you specify a fully qualified path to the Derby DB in the
teamserver.properties file.

The problem you are seeing is not likely because of your OS choice. One
thing to check is that you have the latest WAS fixpacks, both for the
application server and the VM.

About the failure to write the repository properties, have you checked
that the teamserver.properties file (and the directory it is in) is
writeable by the user who is running the WAS process?

Matt Lavin
Jazz Server Team


sderas wrote:
I have several question about installing Jazz server 1.0 into
WebSphere Application Server 6.1, I am able to install it, but at the
end, when I run the jazz setup, first the Derby database cannot be
accessed, the site says that the DB is responding, but the tables are
not for Jazz use. Then I create the tables with the repotools, but at
the very end, the site says that it cannot write the repository
properties.
This is happening over Red Hat Ent 5 and Windows Vista Bus Ed.
Do you think that this is because of the OS?
If you have a more detailed guide, can you lend it to me?
Note: Yes, I follow all the initial guide by the book. I am using the
Derby DB, is this a problem?
Thank you very much.

permanent link
Chris Errichetti (7173) | answered Aug 13 '08, 4:57 p.m.
Sergio,

When I got Jazz working, I did things one at a time, confirming connectivity and access each step, and it worked for me. First, I got Jazz working with Derby and Tomcat. Then, I migrated from Derby to DB2 9.5. After that was confirmed, I migrated from Tomcat to WebSphere 6.1.0.15. If possible, maybe this method will work for you.

A couple of questions:

- Are you installing Jazz as root?
- Of the steps that I took, do any of those configurations work for you (i.e. is it working with Derby and Tomcat)?

Thanks.
Chris

permanent link
Matt Lavin (2.7k2) | answered Aug 13 '08, 6:11 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Thanks for the good advice.

After a little more investigation, it looks like the server was not
running the latest WAS fixpack, and that was causing at least part of
the problem.

Matt Lavin
Jazz Server Team

cerrichetti wrote:
Sergio,

When I got Jazz working, I did things one at a time, confirming
connectivity and access each step, and it worked for me. First, I
got Jazz working with Derby and Tomcat. Then, I migrated from Derby
to DB2 9.5. After that was confirmed, I migrated from Tomcat to
WebSphere 6.1.0.15. If possible, maybe this method will work for
you.

A couple of questions:

- Are you installing Jazz as root?
- Of the steps that I took, do any of those configurations work for
you (i.e. is it working with Derby and Tomcat)?

Thanks.
Chris

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.