Unmanaged mode of spring boot kie-server - Container Id for the deployed kmodule

[Nick]

Hi,

I am looking at running spring boot kie-server in unmanaged mode after going pass the development phase. In this case, I don't need to run kie-wb. This can reduce the CPU and memory resources required. 

I managed to deployed the kmodule with the following code

            String deploymentUnit. = "com.myteam:demo:1.0.194";

 

             String[] gav = deploymentUnit.split(":");

            

            unit = new KModuleDeploymentUnit(gav[0], gav[1], gav[2]);

            deploymentService.deploy(unit); 

I can see the following log which indicates that the kmodule was successfully deployed

kie-server_1   | 2018-02-09 09:22:57.711  INFO 5 --- [           main] o.d.c.k.builder.impl.KieRepositoryImpl   : KieModule was added: ZipKieModule[releaseId=com.myteam:demo:1.0.194,file=/root/.m2/repository/com/myteam/demo/1.0.194/demo-1.0.194.jar]

However, when accessing the /rest/server/containers REST endpoint, I got the following

<response type="SUCCESS" msg="List of created containers">

<kie-containers/>

</response>

Any idea?

Also, how can I specify the container Id for the deployed kmodule? No such method in  deploymentService. I believe I need that as most of rest call requires container Id or deployment Id to be specified.

Regards,'

--Nick

 

[Nick]

Managed to get this done via KieServer.

ServiceResponse<KieContainerResource> createContainer = kieServer.createContainer(CONTAINER_ID, containerResource);

[Maciej Swiderski]

kie server in unmanaged mode relies on server state file {kie-server-id}.xml where you can define your containers to be started. You can do it in several ways:

- embed that file from other environment so it will already have containers defined

- use API to add containers to that file https://github.com/mswiderski/itorders-app/blob/master/itorders-web/src/main/java/org/kie/server/swarm/bpm/KieServerMain.java#L45-L57 note that this must be done before kie server is booted - so it must be before any of the auto configuration is triggered

- deploy manually as you already did

depending on your needs you might chose one option over the other but 1 or 2 seems to be the best one from my point of view

Maciej

-- 
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/8753482d-70e6-4bad-8f66-82ff8a95dc6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nick]

Hi Maciej,

I tried the following code. No error but no container gets created. /rest/server/containers returns empty list. Did I miss anything?

   

    @SpringBootApplication

    public class KieServerApplication {

    

    private static final Logger LOGGER = LoggerFactory.getLogger(KieServerApplication.class);

    @Autowired

    public KieServerApplication(@Value("${kieserver.kmodule-deployment-unit}") String deploymentUnit,

                         @Value("${kieserver.serverId}") String serverId) {

    

        String controller = System.getProperty(KieServerConstants.KIE_SERVER_CONTROLLER);

if ( controller != null && !controller.isEmpty()) {

LOGGER.info("Controller is configured ("+controller+") - no local kjars can be installed");

            return;

        }

LOGGER.info("@@@@@@@@@@@@@@@@ configure container @@@@@@@@@@@@@");

String[] gav = deploymentUnit.split(":");

        

KieServerStateFileRepository repository = new KieServerStateFileRepository();

        KieServerState currentState = repository.load(serverId);

        

        Set<KieContainerResource> containers = new HashSet<KieContainerResource>();

        

        ReleaseId releaseId = new ReleaseId(gav[0], gav[1], gav[2]);                     

        KieContainerResource container = new KieContainerResource(releaseId.getArtifactId(), releaseId, KieContainerStatus.STARTED);

        containers.add(container);        

        

        currentState.setContainers(containers);

        

        repository.store(serverId, currentState);

    }

I got this to works however.

         String[] gav = deploymentUnit.split(":");

        

         ReleaseId releaseId = new ReleaseId(gav[0], gav[1], gav[2]);

               

        KieContainerResource containerResource = new KieContainerResource(releaseId.getArtifactId(), releaseId);

        ServiceResponse<KieContainerResource> createContainer = kieServer.createContainer(releaseId.getArtifactId(), containerResource);

By the way, I found out that the system keeps making attempt to connect to controller although I didn't add  kieserver.controllers property to application.properties and didn't set -Dorg.kie.server.controller.  

kie-server_1   | 2018-02-09 17:00:45.935 DEBUG 5 --- [ntrollerConnect] o.k.s.s.i.c.ControllerConnectRunnable    : Attempting to connect to one of the controllers...

kie-server_1   | 2018-02-09 17:00:45.935 DEBUG 5 --- [ntrollerConnect] o.k.s.s.i.c.ControllerConnectRunnable    : Still cannot connect to any controllers, waiting for 10000 before next attempt

I notice that System.getProperty(KieServerConstants.KIE_SERVER_CONTROLLER) returns empty String; not null. Is this a bug?

Thanks,

--Nick

[Maciej Swiderski]

if this does not work it indicates it’s invoked too late - meaning it is after kie server initialised already so the state file is already read.

controller checks cover both null and empty string, see https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server-parent/kie-server-services/kie-server-services-common/src/main/java/org/kie/server/services/impl/controller/DefaultRestControllerImpl.java#L148

most likely you have state file being reused - search for a file named {org.kie.server.id}.xml where org.kie.server.id is identifier of your server. There you will most likely still have controller defined, remove it from there and off you go. same you can add your containers in that file so that will get deployed automatically.

Maciej

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/3f1de564-882c-4262-830b-9358885eeb1e%40googlegroups.com.

[Clinton Gomes]

Can we change the location of where it picks this file: {org.kie.server.id}.xml   . For eg: src/main/resources  or somewhere inside our project jars.

[Maciej Swiderski]

You can change it via system properties

org.kie.server.repo

Maciej

Wiadomość napisana przez Clinton Gomes <canuc...@gmail.com> w dniu 20.03.2019, o godz. 20:25:

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/f1c0fd64-867e-40a3-9940-ce1e0813595e%40googlegroups.com.

[Clinton Gomes]

Thanks Marc. 

How do we package {org.kie.server.id}.xml  in spring boot? Since it lives outside the spring boot jar.

I'd like to deploy this file on openshift environment and maintain through git source control.

Please let me know if you'd like this question posted in another thread.

[Clinton Gomes]

Perhaps PV (persistent volumes) could help with {state}.xml file

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/def76c89-25ed-4200-9168-7429b4d98d8d%40googlegroups.com.

[Maciej Swiderski]

I’d more go for config map and mount that as file in the container 

Maciej

Wiadomość napisana przez Clinton Gomes <canuc...@gmail.com> w dniu 22.03.2019, o godz. 18:53:

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/CAJGb5QcDCz4i7hZwcvUuZWvWutk%2B3SEpGK6ATiCebLpgF6fsbA%40mail.gmail.com.