2 Replies Latest reply on Dec 30, 2015 10:50 AM by Abhijit Humbe

    Not getting Endpoint  while deploying drools application on kie-server-6.3.0.Final-ee7

    Chirag Soni Newbie

      i have developed a drools application using "kie-drools-wb-webapp-6.3.0.Final" and deploying application on "kie-server-6.3.0.Final-ee7" but while creating a container I am not getting Rest Service Endpoint to call the application.


      Please Find out the attachment of screenshot

        • 2. Re: Not getting Endpoint  while deploying drools application on kie-server-6.3.0.Final-ee7
          Abhijit Humbe Master

          Start server instance with following options, you can add them in standalone.xml file as well


          <property name="org.kie.server.user" value="anton"></property>

          <property name="org.kie.server.pwd" value="password1!"></property>

          <property name="org.kie.server.location" value="http://localhost:8080/kie-server/services/rest/server"></property>

          <property name="org.kie.server.controller" value="http://localhost:8080/business-central/rest/controller"></property>

          <property name="org.kie.server.controller.user" value="kieserver"></property>

          <property name="org.kie.server.controller.pwd" value="kieserver1!"></property>

          <property name="org.jbpm.server.ext.disabled" value="true"></property>

          <property name="org.kie.server.id" value="local-server-123"></property>



          org.kie.server.user needs to have kie-server role assigned (for example in an application-roles.properties file in JBoss EAP)

          org.kie.server.location can point to a different host, but for testing purposes we can use same server for both, Controller and Server. Note that this is not suitable for production, as it means once this machine will be down, both Controller and Decision Server will be unavailable.

          org.kie.server.controller.user currently this user is hardcoded to kieserver value due to this bugzilla

          org.kie.server.controller.pwd similarly to the controller user, this is a hardcoded value and can't be changed for now. It is covered by the same bugzilla as mentioned above.


          Note that it is not necessary to use Controller at all - this is just for our convenience, because it gives us the GUI for managing the Decision Server. If GUI is not required, then all of the operation can be achieve by direct usage of REST API.


          org.jbpm.server.ext.disabled this is not required property, just to demonstrate that the process execution capabilities can be turned off like this.

          org.kie.server.id This is too, not required property. If it is omitted then the BxMS will generate unique ID on its own, but usually this is some long, random value, not easily memorable.



          Once this configuration is in place, let's start the BxMS.To confirm decision server is registed sucessfully we can use following URL


          http://localhost:8080/kie-server/services/rest/server/ [GET]


          Respose looks like as:



          <response type="SUCCESS" msg="Kie Server info">













          Once the Decision Server is registered we may add some Containers to id, by clicking  on '+' icon on the line with Decision Server and register new Container - it is necessary to pick the groupid:artifactid:version of the KJAR and also select some name of the Container - this name will be used later on in the interaction with the Container.To execute rules we have to use following URL


          http://localhost:8080/kie-server/services/rest/server/containers/instances/Container_ID  [POST]


          and request payload looks like as:



            <insert out-identifier="obj">





            <fire-all-rules />



          Hope it helps.