License issue with Build forge
I have installed the build forge with Mysql server 5.5 and then i start it by double clicking on buildforge.exe in Program Files (x86)\IBM\Build Forge directory. This is what i am getting :
I have used the rational key server installed few months back on same machine but seems like this is the only reason.
If license is the issue then how can i use the new license file/server without installing BF again?. After License what are the steps to access the build forge using browser ?. Any help would greatly appreciated. :) :)
I have used the rational key server installed few months back on same machine but seems like this is the only reason.
If license is the issue then how can i use the new license file/server without installing BF again?. After License what are the steps to access the build forge using browser ?. Any help would greatly appreciated. :) :)
Accepted answer
Hey Naveen,
Nice to hear from you again. I see that you are having a couple more issues. I have a couple questions that I would like to ask, just to give me a clearer picture on the issue at hand.
1. While installing BF, did you supply the license server details? There is a section:
2. From the license key admin tool, I am not seeing any BF lics, does that license file/server have BF licenses?
In looking at the screenshot, it seems to point to a missing license issue. When you start the Build Forge engine, a license feature ( BuildForgeEntServer) is consumed. If that is not available, then the type of errors you are seeing would be the result.
Also, to start the Build Forge Engine/Service, please review the following:
http://www.ibm.com/support/knowledgecenter/SSB2MV_8.0.0/com.ibm.rational.buildforge.doc/topics/postinst_startstop_windows.html
I would not start the service by simply double-clicking the .exe :-)
Once the service has started, you can then proceed to bring up the Build Forge Management Console from the web browser. Typically, you can just enter:
https://localhost
Which should bring up the browser, but it all depends on how BF was installed with SSL and Security settings set prior to the install. If you've just performed a out of the box, simple install then the above address should work.
Based on your responses to the two questions, I should be able to provide a suggestion to get the license server setting in BF. Typically, that will be either a change to the BF tables or an environment variable (e.g. LM_LICENSE_FILE).
I hope that the above helps.
Many thanks,
Pritesh...
Nice to hear from you again. I see that you are having a couple more issues. I have a couple questions that I would like to ask, just to give me a clearer picture on the issue at hand.
1. While installing BF, did you supply the license server details? There is a section:
2. From the license key admin tool, I am not seeing any BF lics, does that license file/server have BF licenses?
In looking at the screenshot, it seems to point to a missing license issue. When you start the Build Forge engine, a license feature ( BuildForgeEntServer) is consumed. If that is not available, then the type of errors you are seeing would be the result.
Also, to start the Build Forge Engine/Service, please review the following:
http://www.ibm.com/support/knowledgecenter/SSB2MV_8.0.0/com.ibm.rational.buildforge.doc/topics/postinst_startstop_windows.html
I would not start the service by simply double-clicking the .exe :-)
Once the service has started, you can then proceed to bring up the Build Forge Management Console from the web browser. Typically, you can just enter:
https://localhost
Which should bring up the browser, but it all depends on how BF was installed with SSL and Security settings set prior to the install. If you've just performed a out of the box, simple install then the above address should work.
Based on your responses to the two questions, I should be able to provide a suggestion to get the license server setting in BF. Typically, that will be either a change to the BF tables or an environment variable (e.g. LM_LICENSE_FILE).
I hope that the above helps.
Many thanks,
Pritesh...
Comments
