After migrating the SAP adapter from version 6.x to 7.x, upon deploying the adapter application in the Admin, even if the SAP adapter 7.x version is installed , the following error is reported (the adapter application is unable to detect the 7.x version) and is still trying to use the SAP adapter 6.x version which is disabled.

Error [com.tibco.administrator.command.data.binding.ServiceInstance] AESDKJ-0000 [main] No matching software for service archive <AdapterApplicationname> The service is disabled

The above issue is caused due to the EAR file which is built on top of an existing Enterprise Archive that was created when using Unicode adapter 6.x or earlier. In the SAP Adapter 6.x we have two sets of application types for the Unicode Sap Adapter (adr3u) and the Non-Unicode SAP Adapter (adr3). This is because at that time the SAP has two sets of runtime libraries for working with Unicode or Non-Unicode. From SAP Adapter 7.x, there is no longer such a limitation as the JCo could support both Unicode and Non-Unicode. So there is only one type for SAP Adapter executable (adr3).

However, when the Unicode SAP Adapter project was created, the enterprise archive was set to use the application type to 'adr3u' and this value could not be changed afterwards. Since we are no longer using 'adr3u' from SAP Adapter 7.x, and we can not update application type in the enterprise archive setting in Designer,  we have to recreate a new enterprise archive after migrating the project to 7.x to set the application type to use adr3. 

Recreate a fresh enterprise archive after migrating the project to 7.x to set the application type to use adr3. Rebuilding the earlier created EAR will cause issues.