Buildforge 7.1.2.2 with RTC 3.0.1 with Reverse proxy issue
Is there any additional configuration needed to enable Build Forge Build engines to run when using a reverse proxy server
I have a CLM 2011 implementation with the following characterisitcs:
4 distinct appservers running the the CLM apps(CCM,RRC,RQM and JTS)
(WAS7.0.0.17)
1 Reverse proxy server that routes requests to the above apps based on the context root.
(IHS7.0.0.17)
1 Buildforge server running standalone.
BF(7.1.2.2 ifix1) Tomcat
When configuring the BF build engine on the application server. I observer the following results.
1. I can successfully run the test connection function from the CCM client to the BF server.
2. I can successfully retrieve the the projects from the buildforge server for the build definition.
3. However that is the end of my capabilities. All build requests remain in a pending state.
4. The Build Engine itself is always in a "warning" state with the heading:
"The build engine process may not be running."
The CCM server is an upgraded RTC 2.0.0.2 server where we had leveraged the the RationalBuildForgeConnector.
We have successfully used the new BF integration with an RTC 3.0.1 beta release with no proxy server.
Is this a known issue with upgraded RTC 2.x RationalBuildforge Connectors or is this an issue with the introduction of a reverse proxy server?
I have a CLM 2011 implementation with the following characterisitcs:
4 distinct appservers running the the CLM apps(CCM,RRC,RQM and JTS)
(WAS7.0.0.17)
1 Reverse proxy server that routes requests to the above apps based on the context root.
(IHS7.0.0.17)
1 Buildforge server running standalone.
BF(7.1.2.2 ifix1) Tomcat
When configuring the BF build engine on the application server. I observer the following results.
1. I can successfully run the test connection function from the CCM client to the BF server.
2. I can successfully retrieve the the projects from the buildforge server for the build definition.
3. However that is the end of my capabilities. All build requests remain in a pending state.
4. The Build Engine itself is always in a "warning" state with the heading:
"The build engine process may not be running."
The CCM server is an upgraded RTC 2.0.0.2 server where we had leveraged the the RationalBuildForgeConnector.
We have successfully used the new BF integration with an RTC 3.0.1 beta release with no proxy server.
Is this a known issue with upgraded RTC 2.x RationalBuildforge Connectors or is this an issue with the introduction of a reverse proxy server?
2 answers
Is there any additional configuration needed to enable Build Forge Build engines to run when using a reverse proxy server
I have a CLM 2011 implementation with the following characterisitcs:
4 distinct appservers running the the CLM apps(CCM,RRC,RQM and JTS)
(WAS7.0.0.17)
1 Reverse proxy server that routes requests to the above apps based on the context root.
(IHS7.0.0.17)
1 Buildforge server running standalone.
BF(7.1.2.2 ifix1) Tomcat
When configuring the BF build engine on the application server. I observer the following results.
1. I can successfully run the test connection function from the CCM client to the BF server.
2. I can successfully retrieve the the projects from the buildforge server for the build definition.
3. However that is the end of my capabilities. All build requests remain in a pending state.
4. The Build Engine itself is always in a "warning" state with the heading:
"The build engine process may not be running."
The CCM server is an upgraded RTC 2.0.0.2 server where we had leveraged the the RationalBuildForgeConnector.
We have successfully used the new BF integration with an RTC 3.0.1 beta release with no proxy server.
Is this a known issue with upgraded RTC 2.x RationalBuildforge Connectors or is this an issue with the introduction of a reverse proxy server?
Hi,
With the upgraded RTC 2.0.0.2 server is the RationalBuildForgeConnector still there? Starting at RTC 3.0 the function that was in the RationalBuildForgeConnector that shipped with Build Forge was moved into RTC for various reasons.
Brent Ulbricht
RTC Build Lead
It exists but does not work. Nor does any NEW Buildforge Build Engine.
Hi,
With the upgraded RTC 2.0.0.2 server is the RationalBuildForgeConnector still there? Starting at RTC 3.0 the function that was in the RationalBuildForgeConnector that shipped with Build Forge was moved into RTC for various reasons.
Brent Ulbricht
RTC Build Lead
Is there any additional configuration needed to enable Build Forge Build engines to run when using a reverse proxy server
I have a CLM 2011 implementation with the following characterisitcs:
4 distinct appservers running the the CLM apps(CCM,RRC,RQM and JTS)
(WAS7.0.0.17)
1 Reverse proxy server that routes requests to the above apps based on the context root.
(IHS7.0.0.17)
1 Buildforge server running standalone.
BF(7.1.2.2 ifix1) Tomcat
When configuring the BF build engine on the application server. I observer the following results.
1. I can successfully run the test connection function from the CCM client to the BF server.
2. I can successfully retrieve the the projects from the buildforge server for the build definition.
3. However that is the end of my capabilities. All build requests remain in a pending state.
4. The Build Engine itself is always in a "warning" state with the heading:
"The build engine process may not be running."
The CCM server is an upgraded RTC 2.0.0.2 server where we had leveraged the the RationalBuildForgeConnector.
We have successfully used the new BF integration with an RTC 3.0.1 beta release with no proxy server.
Is this a known issue with upgraded RTC 2.x RationalBuildforge Connectors or is this an issue with the introduction of a reverse proxy server?
Hi,
With the upgraded RTC 2.0.0.2 server is the RationalBuildForgeConnector still there? Starting at RTC 3.0 the function that was in the RationalBuildForgeConnector that shipped with Build Forge was moved into RTC for various reasons.
Brent Ulbricht
RTC Build Lead