It's all about the answers!

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

×42,860
×11,990
×4,309
×864

question asked: Jan 08 '14, 12:30 a.m.
question was seen: 4,351 times
last updated: Jan 10 '14, 2:30 a.m.

Related questions

What does rsadm.war stand for?

0
ROTT NEST (3●2●4) | asked Jan 08 '14, 12:30 a.m.
edited Jan 08 '14, 5:54 p.m.
When using RDM for RSA, I noticed that there is rsadm.war under webapp 

[root@ruprecht server]# find . -name *dm.war
./tomcat/webapps/dm.war
./tomcat/webapps/rsadm.war

It is not a registered application in JTS,  but it will be loaded and run while RDM starts.
From rsadm.log, it likes like rsadm.war will handle the request of RSA model web GUI rendering.

Any one can help me to understand:

Q1: What is rsadm.war used for?
Q2: What is the relationship between rsadm.war and dm.war?
Q3: Why does rsadm.war exist as standalone war instead of being bundled into dm.war if it is only working for dm.war?

Thanks in advance!~






Accepted answer

1
permanent link
Thomas Mattsson (176●3) | answered Jan 08 '14, 1:46 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Q1: What is rsadm.war used for?
Rsadm.war is used for all RSA specific operations starting from RSA DM 4.0.3.

Q2: What is the relationship between rsadm.war and dm.war?
The rsadm app is what we call a domain extension server application and can be registered against the DM application through the admin pages. Setup will automatically add one deployed on the same application server. .

Q3: Why does rsadm.war exist as standalone war instead of being bundled into dm.war if it is only working for dm.war?
For two reasons:
1. DM is supported on AIX, but it is not a RSA supported platform. In those cases the rsadm.war would be deployed on an application server on a RSA supported platform.
2. To have the possibility to have more than one domain extension server for scalability purposes. In particular for diagram rendering since each rsadm.war instance can only render one diagram at the time.
ROTT NEST selected this answer as the correct answer
Comments
ROTT NEST commented Jan 08 '14, 6:23 p.m.

 Hi, Thomas, 


Thank you for the quick response. 

But for Q3, I don't understand why rsadm has to support the same platform as RSA.  As I know rsadm always located in different machines with RSA, and they communicate thru network, so that they should be platform independent.  Do you mean in some cases, rsadm has to be installed on the same OS as RSA?

Another derived question is why each instance rsadm can only render one diagram at a time? I am just curious, if several users, say 5,  access diagrams at the same time. That could be very slow, because it may take several seconds to render a middle complicated diagram, all others requests have to wait in the queue. So, in normal customer cases, how many rsadm servers will we configure in the case customer has 50 users, with 5 access in parallel?

Thank you very much!~

Thomas Mattsson commented Jan 09 '14, 2:49 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

Regarding Q3, the client OS has no impact on the server platform. The only thing one have to be aware of is that rsadm.war can not be deployed on AIX. Except that there are no platform restrictions.

Diagrams can only be rendered one at the time because there is only a single thread for diagram rendering per rsadm.war instance. This is however only the case for diagrams that have any changes since the last time it was rendered. Diagrams are cached persistently after rendering so when 5 users open a recently changed diagram they will all get the diagram after it has been rendered.

It should not be necessary to add additional domain extension servers for normal customer cases. Typical scenarios where this might be beneficial would be:
1. Actively managed projects with many concurrent users where there is a lot of changes happening in diagrams.
2. Externally managed projects where for example large models are imported from scratch nightly. Import can in those cases do a pre-cache of diagrams step to improve performance (diagrams would always be in cache). To lower time to render all of the diagrams the work could be spread out on multiple servers.

ROTT NEST commented Jan 09 '14, 7:20 p.m. | edited Jan 10 '14, 2:30 a.m.

 Thomas, Thanks a lots~ It's very clear.

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.