Improve message for missing schematype jar during discover of custom security provider (#762)

Author: CarolynRountree

core/src/main/python/wlsdeploy/tool/discover/topology_discoverer.py

@@ -341,7 +341,9 @@ def discover_security_configuration(self):
                     self._discover_subfolders(result[model_constants.REALM][realm], location, check_order)
                     location.remove_name_token(name_token)
                 except DiscoverException, de:
-                    _logger.warning('WLSDPLY-06200', self._wls_version, de.getLocalizedMessage(),
+                    wlst_path = self._aliases.get_wlst_attributes_path(location)
+                    _logger.warning('WLSDPLY-06200', wlst_path,
+                                    self._wls_version, de.getLocalizedMessage(),
                                     class_name=_class_name, method_name=_method_name)
                     result = OrderedDict()
 

core/src/main/resources/oracle/weblogic/deploy/messages/wlsdeploy_rb.properties

@@ -579,9 +579,10 @@ WLSDPLY-06155=Attribute {0} value at location {1} replaced by token {2}
 WLSDPLY-06156=MBean not defined in alias definitions at location {0}. Will skip discovery of MBean folder.
 
 # mbean_getter.py, attribute_getter.py specific to discover
-WLSDPLY-06200=Unable to get the Security Realm Provider name in version {0} with offline WLST. \
-  The SecurityConfiguration will not be added to the model. The work-around is to \
-  manually add the Security Configuration to the model or to discover the domain in online mode : {1}.
+WLSDPLY-06200=Unable to get the Security Realm Provider location {0} in version {1} with offline WLST. \
+  The SecurityConfiguration will not be added to the model. Check that the schematype jar has been generated. \
+  The work-around is to \
+  manually add the Security Configuration to the model or to discover the domain in online mode : {2}.
 WLSDPLY-06201=Invalid Security Provider name "{0}" found for provider type at location {1}
 
 # resources_discoverer.py