Buildforge plugin for RAM 7.5.1.1 does not seem to work.
2 answers
This policy call's BF api. The .zip that you have downloaded from the (RAM) extension page holding the RAFW policy, contains also the BF api, the rbf-services-client-java.jar ... you will need to replace it with the .jar from your version of BF/RAFW and update the policy in RAM.
Do you have any logs, for RAM? (Administration->Tool->ramDebug.log)? Comments That's an interesting idea. I will try that and see what becomes of it. I can send my logs to you privately. Please let me know what email I should send them too.
Kind regards,
Gili, I was able to update the buildforge.zip file with a version of rbf-services-client-java.jar from my raf installation. The file was slightly larger than the file that was provided in the RAM extensions page. However the problem is still present. I also uploaded just the policy.jar by itself and I still got the same issue, which eliminates the rbf-services as being a contributor to the problem.
Looking for more idea's this issue is persistent and is really slowing down our POC.
You need to have the zip that includes both the policy and the bf runtime for that Governor.
Hi Gili how do I get the correct buildforge.zip file that includes the right rbf services and ram api. We are using 7.5.1.1 we also recently purchased the product and have a support ticket open to get a fix for this functionality. Also how do I attach the logs here. I was able to use the RAM java api to pull information from the RAM custom attribute for an Asset and LIbrary information. But if we want to initiate actions as a result of a workflow lifecycle in ram we need to have the governer working. Thanks for all of your help thus far. The .jar should be in one of the directories that BF is installed at.
Hi Gili,
We are using RAF 3.0.0.3 and I do have the rbf-services-client-java.jar file from this install.
Here is the scenario.
When I use the buildforge.zip file that came with RAM 7.5.1.1 distribution the policy fails when I try to execute a buildforge job on my RAF/Buildforge server during the entrance state of a RAM lifecycle.
Over the last couple of weeks I've tried many combinations including getting the rb-services-client-java.jar from our RAF 3.0.0.3 server and re-zipping ithe buildforge.zip file with the 7.5.1.1 com.ibm.ram.buildforge.policy.jar file. But the problem still exists. I also have a PMR open with IBM support regarding this sticky issue. Thank you for reaching out, please let us know if there is anything else we can try.
Kind regards,
showing 5 of 8
show 3 more comments
|
This problem was resolved a couple of months ago with your help. All we needed to do, to solve this issue was add an environment variable in the RAF tool called RAM_GUID, and set the built in build forge policy to execute on the entrance state of our automated workflow, and now we can kick off a RAF job from RAM.
|
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.