It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×4,288
×2,338

question asked: Mar 25 '19, 5:05 a.m.
question was seen: 788 times
last updated: Mar 25 '19, 5:54 a.m.

Related questions

FAQ - How this Forum works

Floating license issue when using backup server

0
Daisy Huang (42●5●14) | asked Mar 25 '19, 5:05 a.m.

I'm running RTC 6.0.3 with WAS 8.5.5.10
My goal is to setup a backup web server to replace the current production server. My topology is a single server with 3 apps(jts,ccm,rqm).

Let's call production server1 and backup server2.
Basically I followed below steps:

1. backup and restored WAS profile in server2
2.install RTC apps using Installation Manager in server2
3.copy and replace /{RTC_install_dir}/server/conf in server2
4. modified db connection in teamserver.properties in server2 to the new DB(which is RAC of production DB)
5. completed jts/setup wizard, tested DB connection. This step confirmed that I'm using the same Public URI for both servers. 
6. In non-working time, shutdown server1, ask system engineer to change DNS point Public URL to server2.

7. upload license files to server2


However when I first log on to the public URL https://{name}:9443/jts/admin, it says:"CRJAZ1267I cannot receive floating licenses list from 'https://{name}:9443/jts/service/com.ibm.team.repository.service.internal.license.IFloatingLicenseService/licenses'. 
https://{name}:9443/jts/ at this time is server2's own URI.

My question is how to deal with the license management when 2 server IPs using 1 Public URI (for webapps and for licenses) not at the same time.

One answer

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
misha rajpoot (34●1) | answered Mar 25 '19, 5:54 a.m.

 The steps you followed are correct may be there is some other reason.

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.