This post should be of interest for you if you want to deploy 3rd party drivers for the JDBC and JMS adapters within the com.sap.aii.adapter.lib.sda archive. I will not insist on the preparations that need to be done for this, but you can find the answer in this note: 1770304 – PI: Preparing the com.sap.aii.adapter.lib.sda for deployment. What I would like to discuss is the error that is showing up when the archive package will be deployed.
The deployment is done via SUM tool and the error appears during configuration phase:
[Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Validation of deployment queue completed with error: com.sap.engine.services.dc.api.deploy.AllItemsAlreadyDeployedValidaionException: [ERROR CODE DPL.DCAPI.1031] AllItemsAlreadyDeployedValidationException. Reason: ASJ.dpl_dc.003456 All batch items are marked as AlreadyDeployed because of Version check. com.sap.engine.services.dc.api.deploy.AllItemsAlreadyDeployedValidaionException: [ERROR CODE DPL.DCAPI.1031] AllItemsAlreadyDeployedValidationException. Reason: ASJ.dpl_dc.003456 All batch items are marked as AlreadyDeployed because of Version check. com.sap.engine.services.dc.cm.deploy.AllItemsAlreadyDeployedValidationException: ASJ.dpl_dc.003456 All batch items are marked as AlreadyDeployed because of Version check.
If you already got this error, SUM tool has to be stopped. Then, SUM has to be configured to run in force-mode, this can be done by adding the two parameters:
/jspm/deployVersionRule = updateAll
/jspm/forceMode = true
in /sdt/param/jspm_config.txt file.
After the parameters were set, restart SUM and follow the same steps to deploy the drivers, this time the error should not appear anymore.
More information can be found in SAP note 1138877 – How to Deploy External Drivers JDBC/JMS Adapters, note that should be read actually before deploying such drivers. What you will not find in the note is the error that appears in case SUM is not started with this option.
Related
