what should vFW-controller.properties be?

 
1
0
-1

I build the policy vm and run /opt/policy_vm_init.sh. Later, I run the command "docker ps" and can see the seven dockers running.

Using the command "docker exec -it <policy@drools's id> /bin/bash", I jump to drools container. 

In the end, in drools container, I execute the command "cat /opt/app/policy/config/vFW-controller.properties" and get the following:

rules.groupId=

rules.artifactId=

rules.version=

However, as I know, drools's Dockerfile calls "CMD  ./do-start.sh"?and "do-start.sh" calls "docker-install.sh". In "docker-install.sh", it says "groudId: artifactId:version must be set in conf file".

So, my question is whether my /opt/app/policy/config/vFW-controller.properties is right or wrong?

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      I suppose this the latest staging 1.1.0?

      pdp-d usually comes up with those values empty, it's a notification from the brms gw that a "rules" drools-application artifact is available in nexus that will set those maven coordinates to that.

      I suspect there must be a problem in the brms gw side so not to be able to create the rules jar on the file and deploy to nexus at startup.

      In nay case, vFW and vDNS will be decomissioned to use an "amsterdam" controller to support the use cases in 1.1.0, now that this release has migrated to describe policies in yaml format.   It actually is, but seems the staging image is stale from the weekend, so your install from staging is probably not picking it up.   There is a little work to be completed and testing to complete the full transition.   FYI.

        CommentAdd your comment...