Resolution
AppManager 5.x
fact
AppManager for Unix V2
fact
BEA WebLogic
fact
Discovery_WebLogicSrvrUNIX Knowledge Script
fact
Discovery_WebLogicSrvr Knowledge Script
symptom
The Discovery_WebLogicSrvrUNIX knowledge script failed.
symptom
Error: 'None of the supported versions of WebLogic Server were found on the machine.'
cause
The Discovery Knowledge Script property "Semi-colon separated list of directories in which to search for WebLogic home directories and configuration files" does not contain a valid path to the BEA WebLogic installation.
fix
One of the parameters for the WebLogic Discovery Knowledge Script is Semi-colon separated list of directories in which to search for WebLogic home directories and configuration files. This parameter must contain a valid path to the BEA WebLogic installation.
The BEA WebLogic home directory may not also be the installation directory. Look in the registry.xml file in the BEA home directory for the WebLogic Integration installation. The registry.xml file contains an XML segment similar to the following:
<bea-product-information>
<host home="c:\bea" name="hostname" number="1">
<product format="1.0" name="WebLogic Platform">
<release BeaProgramGroup="BEA WebLogic Platform 7.0"
BuiltInServicePackLevel="0" InstallDir="
c:\bea\weblogic700 " InstallTime="Jun 6, 2002
4:57:18 PM" JavaHome="c:\bea\jdk131_03" JavaVersion="1.3.1_03"
PatchLevel="1" ServicePackLevel="0" Status="installed"
level="7.0">
<component name="WebLogic Server" version="7.0.0.1">
<component name="Server"/>
<component name="Server Examples"/>
</component>
<component name="WebLogic Integration" version="7.0.0.0">
<component name="Integration Server"/>
<component name="Integration Examples"/>
</component>
</release>
</product>
</host>
</bea-product-information>
In this example, the parameter to enter for the Discovery job's Property Values is: C:\bea. (This registry.xml file is from a Microsoft Windows machine. The same principle also applies to a Unix machine.)
note
The registry.xml file can be found with the following command:
# find <search_path> -name registry.xml -print
Where <search_path> is the location of where to begin the "find". This beginning search path will depend on the conventions used for installing software applications, but more likely places are /usr, /opt, /home, etc.