[CR #353320, #355077] Since there are various ways of creating the WebLogic Server start up script, the installer program may be unable to complete the necessary modifications for your environment. You may need to modify the startup file manually.
Workaround: Perform one of the following procedures.
If you use the startWebLogic.sh startup script:
Open the file used to start the WebLogic Server in a text editor. For example, if you use the default WebLogic startup file, open:
$BEA/user_projects/domains/<domain_name>/startWebLogic.sh
where $BEA is the WebLogic installation directory
Check to make sure the following line, which invokes the commEnv.sh script, is included:
# Call commEnv here AFTER setting the java_vendor to
get common environmental settings.
${BEA}/common/bin/commEnv.sh
If the line is missing from the startup file, add it above the Java call that starts the WebLogic server process, and save the file. This modification makes additions to the CLASSPATH before the WebLogic Server starts up.
Start the WebLogic Servers.
Alternatively, if you use another way to start the WebLogic Server, other than the startWebLogic.sh script:
Check to make sure the CLASSPATH includes these entries:
$BEA/weblogic81/server/ext/jdbc/sybase/jConnect-5_5/classes/ jconn2.jar:$BEA/sybepsecurity/sybepsecurity_classes.jar: $BEA/sybepsecurity/log4j-1.2.8.jar:$BEA/sybepsecurity/etc
Start the WebLogic Servers.
