It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×11,538
×5,313
×810
×112

question asked: Apr 22 '21, 11:34 a.m.
question was seen: 645 times
last updated: Jul 16 '21, 11:09 a.m.

Related questions

FAQ - How this Forum works

Rhapsody - Cannot get OSLC root services - RMM 702

0
Vani B (125●5●29) | asked Apr 22 '21, 11:34 a.m.

When connecting from Rhapsody to (Remote Artifact PAckages)RM project using Login to server, getting below error


Rhapsody-Cannot get OSLC root services
https://<sername>/rm/rootservices
Error Message : Received fatal alert : Protocol version

Comments
1
Ian Barnard commented Apr 23 '21, 6:58 a.m.
JAZZ DEVELOPER

That looks like an RM url (i.e. DOORS Next), not RMM. Can you browse to the URL - you should get some XML. If you can't browse to it there's a problem with your server/network.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Edmund Mayer (36●1) | answered Jul 16 '21, 11:09 a.m.
I am using RMM and DOORS Next 7.0.2 ifix3 and Rhapsody 9.0.1 ifix1.  For me the solution was to update the rhapsody.ini file, as described at: https://www.ibm.com/docs/en/elm/7.0.2?topic=administering-configuration-tls-v12


Configuring Rhapsody to use the TLS v1.2 protocol

If you will be using Rhapsody Model Manager with a network that uses the TLSv1.2 protocol, you must make a number of changes to your rhapsody.ini file.

Open your rhapsody.ini file and update the [JVM] section so that it includes the following lines: 

[JVM]
Options=ClassPath,LibPath,MaxHeap,MaxStack,ClientProtocol,ClientStrictProtocol
ClientProtocol=-Dcom.ibm.team.repository.transport.client.protocol=TLSv1.2
ClientStrictProtocol=-Dcom.ibm.jsse2.sp800-131=strict

Your answer

Register or to post your answer.