Fixing API publishing related issues

components/device-mgt/org.wso2.carbon.device.mgt.core/src/main/java/org/wso2/carbon/device/mgt/core/api/mgt/APIPublisherServiceImpl.java

@@ -43,10 +43,14 @@ public class APIPublisherServiceImpl implements APIPublisherService {
         }
         APIProvider provider = APIManagerFactory.getInstance().getAPIProvider(api.getApiOwner());
         if (provider != null) {
+            if (!provider.isAPIAvailable(api.getId())) {
                 provider.addAPI(api);
-            if (log.isDebugEnabled()) {
-                log.debug("Successfully published API '" + api.getId() + "' with the context '" +
-                        api.getContext() + "'");
+                log.info("Successfully published API '" + api.getId().getApiName() + "' with context '" +
+                        api.getContext() + "' and version '" + api.getId().getVersion() + "'");
+            } else {
+                log.info("An API already exists with the name '" + api.getId() + "', context '" +
+                        api.getContext() + "' and verison '" + api.getId().getVersion() +
+                        "'. Thus, the API config is not re-published");
             }
         } else {
             log.error("API provider configured for the given API configuration is null. Thus, the API is not " +

components/device-mgt/org.wso2.carbon.device.mgt.core/src/main/java/org/wso2/carbon/device/mgt/core/api/mgt/APIRegistrationStartupObserver.java

@@ -67,9 +67,6 @@ public class APIRegistrationStartupObserver implements ServerStartupObserver {
 
                 API api = DeviceManagerUtil.getAPI(apiConfig);
                 DeviceManagementDataHolder.getInstance().getApiPublisherService().publishAPI(api);
-
-                log.info("Successfully published API '" + apiConfig.getName() + "' with the context '" +
-                        apiConfig.getContext() + "' and version '" + apiConfig.getVersion() + "'");
             } catch (Throwable e) {
                 /* Throwable is caught as none of the RuntimeExceptions that can potentially occur at this point
                 does not seem to be logged anywhere else within the framework */