It's all about the answers!

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

×42,874
×10,962
×4,316
×3,954

question asked: Feb 05 '13, 2:25 a.m.
question was seen: 7,332 times
last updated: Feb 05 '13, 4:31 p.m.

Related questions

How can I configure a reverse proxy for same context roots

0
Ruslan Luchnikov (31●2●13●11) | asked Feb 05 '13, 2:25 a.m.
edited Feb 05 '13, 2:40 a.m.
Hi,
I am trying configure reverse proxy for jazz 3.0.1 with old the context roots:
CCM server: https://ccm.ca.sbrf.ru:9443/jazz
RM server: https://rm.ca.sbrf.ru:9443/rdm
QM server: https://qm.ca.sbrf.ru:9443/jazz
I tried to use ProxyPass \jazz for  https://ccm.ca.sbrf.ru:9443/jazz and  ProxyPass \jazz for https://qm.ca.sbrf.ru:9443/jazz,
but but it does't work.
Are there any example or trick in configuring HTTP server to treat same context roots in different way?
Thanks in advance!

2 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Feb 05 '13, 2:59 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Feb 05 '13, 4:31 p.m.
Ruslan,

I don't fully understand your question, probably because the information on QM is missing.

However, this is what I know about feasibility of reverse proxies. See https://jazz.net/library/article/831 for more topology information and the library for additional content.

  • If you want to use a reverse proxy, all applications have to be set up with the same URL prefix. For example https://qualifiedhostname:port/ .
  • You can use the postfix to pass the requests to the dedicated server. To be able to do that, the postfix (in Jazz the context root), needs to be different.
  • If you do a new install, you can follow the infocenter topic on installing with a different context root. You would install e.g as ccm1, ccm2,..... This then allows to use https://qualifiedhostname:port/ccm1, https://qualifiedhostname:port/ccm2 as public URI that can be distinguished.
If you upgrade from a 2.x install and have the public URI already set to https://ccm.qualifiedhostname:port/jazz and https://qm.qualifiedhostname:port/jazz I am not aware of a way to use a common public URI with the same host name like https://qualifiedhostname:port/jazz in a proxy scenario. I am also not sure what advantage you would gain, because after forwarding the applications would use their old public URI's. In the works case you could get wrong references using the common public URI into the system.

I am not sure if there is a solution for the setup you use. The only way I see would be very tricky, using server rename and changing the context root of the applications, plus an install with a different context root and manually moving the restore data into the new install. Server rename does not support this kind of scenario today, for what I am aware of and I would not suggest to go down this route today. 

Comments
Vladimir Amelin commented Feb 05 '13, 3:17 a.m. | edited Feb 05 '13, 3:18 a.m.

Some clarifications after Ruslan:

Current Public URI for ccm and qm are:

https://server:9443/jazz

https://server:9445/jazz

It was upgraded from 2.x so we have to use "old" context roots.

We would like to migrate to enterprise toipology from existing all-on-one-machine (and no proxy) deployment. CLM version is 3.x so we cannot change Public URI before moving to enterprise topology with reverse proxy. 

Question is if there's a way to setup reverse proxy to distinguish incoming requests with same context root. All examples describe "classic" case with default, different context roots for each application.

Ralph Schoon commented Feb 05 '13, 3:44 a.m. | edited Feb 05 '13, 3:45 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I am not aware of a way to do this. For one thing the ports are different and the context root is not. You can't have the same proxy listen to two different posts, can you? So you would need two seperate proxies serving the original public URI's. What would you hope to gain with this?

You would have to change the port as well as the context root. I can imagine this could be done with a server rename, however this scenario is not yet supported by server rename as far as  I can tell. As mentioned server rename is only available in 4.x. In addition it would be probably require quite complex install and backup/restore strategies to change the context roots during server rename.

Without server rename, which is not available in 3.x, you would not even be able to install two applications with the same context root into the same application server.  So I don't see any possible scenario. Similar requests I have seen in the past were not pursued for the reasons above.

You might want to work with your IBM contacts or support if there is a supported scenario, but I doubt it.


0
permanent link
Ruslan Luchnikov (31●2●13●11) | answered Feb 05 '13, 3:29 a.m.
I want make forwarding from reverse proxy to targets server with same context root.
Example:
ProxyPass \ccm  https://ccm.ca.sbrf.ru:9443/jazz
ProxyPass \qm   https://qm.ca.sbrf.ru:9443/jazz
Am i understand correctly, that before configuring  reverse proxy i need change the context roots for the target servers(CCM server: https://ccm.ca.sbrf.ru:9443/jazz and QM server: https://qm.ca.sbrf.ru:9443/jazz) ?
Can't i to use “rewrite” rules, other Apache tricks or this configuration?

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.