Requirement Composer cannot be configured on a virtual IP?

You can override the "JRS server URL" in the configuration wizard, but you must uncheck the "Use defaults" checkbox at the bottom of the wizard.

Hello,

You can only run the configuration tool where the RRC server is installed. The RRC server cannot be remote, hence the url is not allowed to refer to a remote host.

Each RRC server has it's own set of databases so, if you need to install 2 RRC servers on the same machine to be used in 2 different configurations, you can try these steps:

- install the first RRC server and configure it to use DB2 databases JRSXML and JRSDB (in your case it's probably already installed; if you used the defaults there's nothing more to be done here)

- go to IBM installation manager, select Install; the server should be detected as already Installed; check it; a dialog box should appear with information about updating the package, adding or removind feature and installing to a new package group; press Continue to install to a new package group; use a different installation path, for example the default C:\Program Files\IBM\RRCS_1 if allowed; Install

- after the installation of the second server is complete, check out the Release Notes and follow the steps from the "Resolving port conflicts with Rational Team Concert" section in order to modify the second server installation ports and enable it to run in parallel with the first installation (in this case, the path to the xml file would be C:\Program Files\IBM\RRCS_1\jazz\server\tomcat\conf\server.xml); stop the server after making all the required changes

- start the configuration tool from the second server program group (usually named IBM Rational Requirements Composer Server_1) and go to Configuration Setup; uncheck Use Defaults; modify jrs url to http://localhost:9081/jazz; modify jrs server path to the new path: C:\Program Files\IBM\RRCS_1\jazz ;specify the db2admin password; change the DB2 database alias to JRSDB1 and the index database alias to JRSXML1; make sure you have enough free space (at least 3 Gb) on the databases drive and leave the rest of the values to their defaults; press Check to validate the parameters; Save

- run the Server Initialization phase from the menu; this should create the JRSDB1 and JRSXML1 databases and start the second JRS server on port 9081 and upload the resources

- after the Server Initialization completes successfully, go to User Management (the url in the address bar now should something like https://localhost:9444/jazz/secure); login as ADMIN/ADMIN and create your user and assign it to the project area just like in the tutorial; save the project area and start the RRC open beta client; specify http://localhost:9081/jazz/ for the url of the new local repository; try to create a project and a couple of artifacts to make sure the second server has been configured successfully

Good luck!

Thanks for the comment.

If multiple projects want to use port 443, is it possible to assign a virtual IP for each project so that they can all use the same port 443? I guress not since the configuration tool does not allow to replace 'localhost'. Could you please confirm?.

If I already configured two projects using port 9080 using the Configuration Tool. Of course, these two instances cannot be run at the same time. Is it possible to change the port for one instance to 9081? It seems that the port number is also saved somewhere besides Tomcat configuration file? Maybe in the DB2 database?

Thanks.

Hi,

I'm not sure what you mean by multiple projects using 443. Multiple configurations should not be able to use the same port when created on the same machine. The configuration tool checks to see if the url is local because it also uses the JRS path to configure the JRS server. It would make no sense to configure a local JRS server while the URL would access a remote one. That's why whatever name you put in the jrs url parameter must be resolved to the local machine. You can use 127.0.0.1 or replace it with the local ip, or the hostname of the local machine; whatever name/ip you use needs to be local. Of course, you can still save a remote name if you don't validate before. But it would fail later...

To change one of the RRC servers to use 9081 follow these steps (changing only 9080 to 9081 would not work; see below):
- start the RRC server the you want to move to a different port
- type http://localhost:9080/jazz/secure in a web browser and login as ADMIN/ADMIN
- go to Server tab and click on Advanced Properties; search for 9080 and you should find URL HTTP Port; changed it to 9081; the next one underneath should be URL HTTPS Port; change that one to 9444 (9080 is only used to redirect to the secured 9443; without moving the 443 port it's useless to move only 9080); save and stop the RRC server
- go to the Release Notes and modify server.xml according to the "Resolving port conflicts with Rational Team Concert" section; save server.xml and start the server
- go to the web browser and this time type http://localhost:9081/jazz/secure ; it should redirect to 9444
- if that happens go to the RRC client and define a new local repository using http://localhost:9081/jazz or a remote repository using http://ip/remote_host:9081/jazz/secure
- try to connect to the new repository; if the server had projects and artifacts you should be able to connect to the new repository and see them
- if this is successful, start the first server in parallel and try to access it through a repository pointing to http://localhost:9080/jazz/

Hope this helps,
Petru

Thanks, Petru.

1. What you recommended to setup a new RRC instance to run on the same server works fine. One instance uses 9080/9443, another instance uses 9081/9444, and so on. In this case, we need to change ports first and then configure the RRC repository using the Configuration Tool. Thanks. Based on this, in the single server envirionment, we can have remote connection URLs like https://RRCserver:9443/jazz, https://RRCserver:9444/jazz, and so on. While the number of projects (instances) grow, we have to opening more ports (the server is behind a firewall).


2. For an existing RRC instance that had been configured using a specific URL like http://localhost:9080/jazz in the Configuration Tool, I was able to change Tomcat ports to 9081/9444 and it worked fine in IE browser (http://localhost:9081/jazz/secure). However, after launch RRC Eclipse client, I was not able to connect to the existing repository nor create a new one. The error says "Connection to the repository failure". Any comment? The Configuration Tool seems saving the JRS URL or port somewhere. I wonder whether we can find it and manually change it. I actually do not worry too much about this issue. The worst scenario is to recreate the RRC repository (DB2 database and tables, etc.).


3. When I say earlier about multiple RRC instaces on the same server using port 443, I meant to setup multiple virtual IPs on the server (in addition to the primary IP). In this case, each instance hopefully can run on a separate virtual IP and they all can use port 443. Using port 443 is kind of well accepted and the port number does not need to be specified in the URL. Our users typically do not like to see port numbers in the URL :(.. For a single server environment, our users would like to see connection URLs like https://DNS1/jazz, https://DNS2/jazz, and so on. DNS1 and DNS2 are corresponding to distinct virtual IPs on the same physical server. Is this possible? I tried using a virtual IP in the JRS URL field of the Configuration Tool. The tools treats the virtual IP as 'remote'. It appears that the tool only accept 'localhost' or '127.0.0.1'. Is this true?

hi,

2. something might be missing; a step might have been skipped; i tried this approach myself before recommending the solution and it worked for me; did you update the ports in the Advanced Properties section? you can start the JRS server and login using the web ui and check them in the Server tab to be 9081/9444. after updating them restart the server right away after saving that page.
also, recheck server.xml for 9080 and 9443 and replace all of them (even the ones in the comments; it's easier to make sure none was left behind).
The url from the config tool needs to be updated in order to be able to access the server and upload the resources as well as start the user management browser and connect. other than that it has no effect on the tomcat server. the others parameters do...


3. Using virtual hosts in tomcat should accomplish this although i'm not sure about the redirections...
Even in this case, you will need 2 ports (9080/9081 and 9443/9444) when running 2 servers on the same machine simply because the second server would not start properly if 443 is already taken and it needs it. However, DNS should hide these details, like you said.
I'll take a closer look at this and post a reply if i can find anything useful that actually works.

Thanks, Petru.

For #2, I might have missed the step to update the URL from from the config tool. I remember 'checking' the URL change, but not remember 'saving' the change. I'm OK now - able to change the port number to 80/443. Thanks.

Please let me know if you can figure out #3 - it will be another great help to us. Thanks again.

Thanks, Petru. Any update on #3? Thanks.