• No replies
1 Post

Pinned topic Problem synchronizing RAM with WSRR 7.0

‏2010-06-11T16:18:09Z |

We've been trying to synchronize a fresh installation of RAM with our pre-production environment WSRR 7.0, in what we have read constitutes the WSRR ALE product.

We have run into multiple problems, must of which we have been able to solve successfully, but the most important one remains. After installing and configuring a fresh RAM, we follow the steps for the synchronization, including the interchange of certificates in the TrustStore of both WAS and the loading of the SOA library in the RAM interface.

The problem occurs after creating a new community for the sync, and after creating the WSRR connection. When creating the connection, in the web form provided by RAM, we test the connection with the "Test Connection" button and RAM indicates that the connection has been successful. Both RAM and WSRR SystemOut.log logs display messages about the success. After hitting the "OK" button in the web form, we get back to the "Connections" screen. Here, when we use the link "Synchronize Classification", we get the very mysterious message at the top of the page "The server is not valid". At the WSRR SystemOut log we get no message, and at the RAM SystemOut log we get the following message:

code06/07/10 9:38:41:768 CDT 00000056 SystemOut O 06/07/10 09:38:41 CDT CRRAM0001E 4246446 ERROR web - The server is not vaild."[/code]

We have checked every one of our steps at least three times, including going as far as reinstalling the OS. The same error was showed to us when we first used the eWAS included with RAM 7.2, but we moved to a standalone WAS in order to do the synchronizing.
Right now, the specs for the two virtual machines running RAM and WSRR are:

OS: SLES 10 SP 2
Memory: 3 GB
WAS version: ND
Database used: Oracle 11g release 1 (running in another VM)

We would appreciate any pointers as to what we may be doing wrong, or about what does the "server is not valid" message actually means, as we have not been able to found any documentation surrounding this error, beyond the minimal info included in the InfoCenter which tells us nothing.

Thank you very much