Sunbird RC Setup Failed in Local

[priyanka-TL]

Like Course Certificate generation, In ML services, We have to generate improvement project certificates. You can refer to the JIRA ticket here for the improvement project certificate story
https://project-sunbird.atlassian.net/browse/SB-28231

So we are trying to understand how it works and generate the certificate. I have followed the below guide to set up the RC
https://project-sunbird.atlassian.net/wiki/spaces/UM/pages/3085500423/Sunbird+RC+Setup

But while building the registry I got an error

Can you please help to fix this error? I am trying to see how we can use the Sunbird RC to generate the certificate and understand how it will work for the project use case

cc - @aks30 @vijiurs @kiranharidas187 @varsha-sl @Prateek-slokam @aishwaryashikshalokam

[pramodkvarma]

@coolbung @tejash-jl @dileepbapat any of you can help?

[gamemaker1]

Could you please try running ./mnvw clean install -DskipTests=true instead?

-./mnv clean install -DskipTests=true
+./mnvw clean install -DskipTests=true

[priyanka-TL]

@gamemaker1 can you share the full URL of search API

[gamemaker1]

http://localhost:8081/api/v1/search is the full URL.

[tejash-jl]

POST: http://localhost:8081/api/v1/<entity-name>/search
BODY:

{"filters": {}}

@priyanka-TL search api

[priyanka-TL]

@tejash-jl im getting error on search api also
curl --location --request POST 'http://localhost:8081/api/v1/TrainingCertificate/search' \ --header 'Content-Type: application/json' \ --data-raw '{ "filters": {} }'

Error
registry_1 | 04:11:52.199 [http-nio-8081-exec-9] ERROR d.s.r.c.RegistryEntityController:157 - Exception in controller while searching entities ! registry_1 | java.lang.NullPointerException: null registry_1 | at dev.sunbirdrc.registry.controller.RegistryEntityController.searchEntity(RegistryEntityController.java:145) registry_1 | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) registry_1 | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) registry_1 | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) registry_1 | at java.lang.reflect.Method.invoke(Method.java:498) registry_1 | at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) registry_1 | at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) registry_1 | at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105) registry_1 | at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:878) registry_1 | at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:792) registry_1 | at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) registry_1 | at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040)

[tejash-jl]

@priyanka-TL
Can you join the Discord community channel and ping me there, we can connect and resolve this.

[tejash-jl]

@priyanka-TL you can follow this sample usecase we have built to generate certificates.
https://github.com/Sunbird-RC/demo-certificate-issuance
Docker Compose: https://github.com/Sunbird-RC/demo-certificate-issuance/blob/main/docker-compose.yml
Notebook / API Documentation: https://github.com/Sunbird-RC/demo-certificate-issuance/blob/main/certificate-api.ipynb

[priyanka-TL]

@tejash-jl I have tried to generate the certificate using the existing entity TrainingCertificate

curl --location --request POST 'http://localhost:8081/api/v1/TrainingCertificate' \
--header 'Content-Type: application/json' \
--data-raw '{
    "name":"Sunbird Learner", 
    "contact":"12345",
    "trainingTitle":"Sunbird RC Certificate Module",
    "note":"Ceritifcate issued"
}'

But I got the below error. Can you help me to fix this error

[priyanka-TL]

@tejash-jl Thank you. Issue got resolved after adding the path instead of pwd in the docker-compose file