In enterprise environments it is often required to provide some kind of health check application to check the pre-requisites (i.e. installed apps and versions) on client machines. This provides an automated way of checking that the client machine is correctly setup for use in business workflows that rely on certain installed applications such as Adobe Acrobat/Reader.
You can use the Windows GUID from the Registry or the MSI API to read the Reader client version:
If you are patching DSC components through Workbench and using version numbers to track your updates, you may notice that the version of the service does not get updated. The service has actually been updated and the new functionality should be available.
This is a product issue in LiveCycle ES2 where the service version number does not get updated correctly when deploying an updated component. You can check the version numbers in Workbench after deploying the component, or you can check in AdminUI > Services > Applications and Services > Service Management:
The version numbers for the services can be updated in the component.xml file included with your DSC component JAR file. The following line is used to define the service version number:
<auto-deploy service-id=”Log” minor-version=”0″ major-version=”1″ category-id=”neo-onboarding”/>
This issue is fixed in ES3 (LiveCycle 10). There is a patch available for LiveCycle ES2 SP2 (126.96.36.199) and LiveCycle ES SP4 (188.8.131.52), so contact enterprise support if you require one of those patches.
With the fix, the service versions will be updated correctly as follows:
If you are trying to call a particular service on the LiveCycle server (e.g. renderPDFForm from the Forms service), you may encounter an error similar to the following :
ALC-DSC-013-000: com.adobe.idp.dsc.registry.ServiceConfigurationNotFoundException: Service Configuration : FormsService version: 1.0 not found
at com.adobe.idp.dsc.provider.impl.ejb.receiver.EJSRemoteStatelessInvocation_b542628e.invoke(Unknown Source)
This error occurs primarily when the service is not running. You can check the service state in the AdminUI. If you have setup the application server and database to start on boot, it may occur that the application server has started before the database service.
Set priorities for the services in the operating system boot settings to ensure the database service starts first.