Hello,
We are encountering an issue when trying to update the out-of-the-box (OOTB) OSGI config for the workflow. The configuration values are not being updated even though we have kept them under the config node. The values are not updated when accessing /system/console/ConfigMgr.
AEM: 6.5.21.0
PID:
com.day.cq.wcm.workflow.impl.WcmWorkflowServiceImpl
Name of the config file:
/apps/project/osgiconfig/config/com.day.cq.wcm.workflow.impl.WcmWorkflowServiceImpl.cfg.json
Entries in the config:
{
"cq.wcm.workflow.terminate.on.activate":"false",
"maxThreadPoolSize": "100",
"minThreadPoolSize": "5",
"cq.wcm.worklfow.terminate.exclusion.list": [],
"event.filter":"(!(event.application\=*))"
}
Also, please note that we are not allowed to update/delete any OOTB config directly in /system/console/ConfigMgr. We only need to update via package deployment.
Can someone please help me identify the issue with this configuration?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @test1234567
There could be several reasons for this. The points below may help you debug further:
Incorrect Config Format:
Misformatted configs can cause issues. Use OSGi Console (http://localhost:4502/system/console/osgi-installer-config-printer) to create the config, then download it from the Config Printer to ensure correct formatting.
Missing Filter.xml Entry:
Ensure META-INF/vault/filter.xml includes your config paths. Also, verify deployment via crxde, Maven build logs, and Package Manager.
Regards,
Ayush
I can see a couple of mistakes in the configuration. After correcting that, the config looks like this:
{
"cq.wcm.workflow.terminate.on.activate":false,
"maxThreadPoolSize": "100",
"minThreadPoolSize": "5",
"cq.wcm.worklfow.terminate.exclusion.list": [],
"event.filter":"(!(event.application=*))"
}
Thank you for your reply. However, even after making the above corrections, I still do not see the changes.
Views
Replies
Total Likes
That's interesting. I tried this, and it worked for me. Have you verified whether the code is deployed correctly to the AEM instance?
Yes, it is deployed to the AEM instance but the config is not picked.
Views
Replies
Total Likes
Hi @test1234567
Try deleting the config from webconsole config first then deploy your config.
If you can access CRXDE, verify that your configuration is present in CRXDE. Additionally, check for any other existing configurations in different locations that may take precedence over this one (such as config.author, etc.).
Hi @test1234567
If you have changed config directly from osgi console then you will find that config at /apps/system folder and delete it.
Hi @test1234567
There could be several reasons for this. The points below may help you debug further:
Incorrect Config Format:
Misformatted configs can cause issues. Use OSGi Console (http://localhost:4502/system/console/osgi-installer-config-printer) to create the config, then download it from the Config Printer to ensure correct formatting.
Missing Filter.xml Entry:
Ensure META-INF/vault/filter.xml includes your config paths. Also, verify deployment via crxde, Maven build logs, and Package Manager.
Regards,
Ayush
Check the filter.xml file for the project maven module where you have osgiconfig. Make sure you added in the filter.xml
<workspaceFilter version="1.0">
<filter root="/apps/project/osgiconfig/"/>
</workspaceFilter>
@test1234567 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies