The Oracle ATG Web Commerce setup program adds a protocol.jar file to the /lib subdirectory of the WebLogic domain directory that you specified during the installation process.

Edit the setDomainEnv.sh|bat file in the <domain>/bin directory. For example, you could prepend your required values to the PRE_CLASSPATH variable, which automatically prepends your values to the WebLogic CLASSPATH:

set PRE_CLASSPATH=C:\WebLogic\user_projects\domains\mydomain\protocol.jar;
%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar;
%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%

Note: The Configuration and Installation Manager (CIM) utility makes these configurations for you. See Configuration and Installation Manager (CIM).

Working with Managed WebLogic Server Instances

When a WebLogic server is started using the WebLogic Admin console, it uses the <WebLogic_Home>/common/bin/commEnv script to set up environment variables, including the CLASSPATH. This causes an Unknown Protocol error. However, when a server is started from a command prompt using the startManagedWebLogic script, it calls the <WebLogic_Domain_Home>/
bin/setDomainEnv script, avoiding any errors. To use the startManagedWebLogic script with a server that has been started using the WebLogic Admin console, you must modify the <WebLogic_Home>/common/nodemanager/nodemanager.properties and set the StartScriptEnabled property to true.