Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

new domain with weblogic6.1 problem?

 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all
I'm trying to create new domain with weblogic other than the default(mydomain),the problem is when i start weblogic as soon as gets to the point where to load the configuration file it exits completly.
When i check "all domain configuration"in the console i see that the new damain is active=false
is not as mydomain active=true.
please any help with that,here are my scripts to start weblogic:
startWebLogic.cmd
==================================
@echo off
@rem This script can be used to start WebLogic Server. This script ensures that
@rem the server is started using the config.xml file found in this directory and
@rem that the CLASSPATH is set correctly. This script contains the following variables:
@rem
@rem JAVA_HOME - Determines the version of Java used to start
@rem WebLogic Server. This variable must point to the
@rem root directory of a JDK installation and will be set
@rem for you by the WebLogic Server installer. Note that
@rem this script uses the hotspot VM to run WebLogic Server.
@rem If you choose to use a JDK other than the one
@rem included in the disribution, make sure that the JDK
@rem includes the hotspot VM. See the WebLogic platform support
@rem page (http://e-docs.bea.com/wls/platforms/index.html)
@rem for an up-to-date list of supported JVMs on Windows NT.
@rem
@rem When setting these variables below, please use short file names (8.3).
@rem To display short (MS-DOS) filenames, use "dir /x". File names with
@rem spaces will break this script.
@rem
@rem jDriver for Oracle users: This script assumes that native libraries
@rem required for jDriver for Oracle have been installed in the proper
@rem location and that your system PATH variable has been set appropriately.
@rem For additional information, refer to Installing and Setting up WebLogic
@rem Server (http://e-docs.bea.com/wls/docs61/install/index.html).
SETLOCAL
cd ..\..
@rem Set user-defined variables.
set JAVA_HOME=C:\bea\jdk131
@rem Check that script is being run from the appropriate directory
if not exist lib\weblogic.jar goto wrongplace
goto checkJDK

:wrongplace
echo startWebLogic.cmd must be run from the config\test directory. 1>&2
goto finish
:checkJDK
if exist "%JAVA_HOME%/bin/javac.exe" goto runWebLogic
echo.
echo Javac wasn't found in directory %JAVA_HOME%/bin.
echo Please edit the startWebLogic.cmd script so that the JAVA_HOME
echo variable points to the root directory of your JDK installation.
goto finish
:runWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
echo off
echo.
echo ***************************************************
echo * To start WebLogic Server, use the password *
echo * assigned to the system user. The system *
echo * username and password must also be used to *
echo * access the WebLogic Server console from a web *
echo * browser. *
echo ***************************************************
@rem Set WLS_PW equal to your system password for no password prompt server startup.
set WLS_PW=weblogic
@rem Set Production Mode. When set to true, the server starts up in production mode. When
@rem set to false, the server starts up in development mode. The default is false.
set STARTMODE=false
echo on
"%JAVA_HOME%\bin\java" -hotspot -ms64m -mx64m -classpath "%CLASSPATH%" -Dweblogic.Domain=test -Dweblogic.Name=myserver "-Dbea.home=C:\bea" -Dweblogic.management.password=%WLS_PW% -Dweblogic.ProductionModeEnabled=%STARTMODE% "-Djava.security.policy==C:\bea\wlserver6.1/lib/weblogic.policy" -Dweblogic.management.discover=false weblogic.Server
goto finish

:finish
cd config\test
ENDLOCAL
=================================
startManagedWebLogic.cmd
===============================
@echo off
@rem This script can be used to start Managed WebLogic Server. This script ensures that the CLASSPATH is set correctly. This script contains the following variables:
@rem
@rem JAVA_HOME - Determines the version of Java used to start
@rem WebLogic Server. This variable must point to the
@rem root directory of a JDK or JRE installation. See
@rem the WebLogic platform support page
@rem (http://e-docs.bea.com/wls/platforms/index.html)
@rem for an up-to-date list of supported JVMs on Windows NT.
@rem
@rem When setting these variables below, please use short file names (8.3).
@rem To display short (MS-DOS) filenames, use "dir /x". File names with
@rem spaces will break this script.
@rem
@rem jDriver for Oracle users: This script assumes that native libraries
@rem required for jDriver for Oracle have been installed in the proper
@rem location and that your system PATH variable has been set appropriately.
@rem For additional information, refer to Installing and Setting up WebLogic
@rem Server (documentation/install/index.html in your local documentation set
@rem or on the Internet at http://e-docs.bea.com/wls/docs61/install/index.html).
SETLOCAL
cd ..\..
@rem Set user-defined variables.
set JAVA_HOME=C:\bea\jdk131
@rem Check that script is being run from the appropriate directory
if not exist lib\weblogic.jar goto wrongplace
goto checkJDK
:wrongplace
echo startManagedWebLogic.cmd must be run from the config\test directory. 1>&2
goto finish
:checkJDK
if exist "%JAVA_HOME%/bin/javac.exe" goto runWebLogic
echo.
echo Javac wasn't found in directory %JAVA_HOME%/bin.
echo Please edit the startManagedWebLogic.cmd script so that the JAVA_HOME
echo variable points to the root directory of your JDK installation.
goto finish
@rem Set SERVER_NAME and ADMIN_URL, they must by specified before starting
@rem a managed server, the detail information can be found on the Internet at
@rem http://e-docs.bea.com/wls/docs61/install/index.html.
:runWebLogic
if "%1" == "" goto checkEnvVars
if "%2" == "" goto usage
set SERVER_NAME="%1"
set ADMIN_URL="%2"
goto startWebLogic
:checkEnvVars
if "%SERVER_NAME%" == "" goto usage
if "%ADMIN_URL%" == "" goto usage
set SERVER_NAME="%SERVER_NAME%"
set ADMIN_URL="%ADMIN_URL%"
goto startWebLogic
:usage
echo Need to set SERVER_NAME and ADMIN_URL environment variables or specify
echo them in command line:
echo Usage: startManagedWebLogic [SERVER_NAME] [ADMIN_URL]
echo for example:
echo startManagedWebLogic managedserver1 http://localhost:7001
goto finish
:startWebLogic
echo on
set PATH=.\bin;%PATH%
set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
echo off
echo.
echo ***************************************************
echo * To start WebLogic Server, use the password *
echo * assigned to the system user. The system *
echo * username and password must also be used to *
echo * access the WebLogic Server console from a web *
echo * browser. *
echo ***************************************************
@rem Set WLS_PW equal to your system password for no password prompt server startup.
set WLS_PW=
@rem Set Production Mode. When set to true, the server starts up in production mode. When
@rem set to false, the server starts up in development mode. The default is false.
set STARTMODE=true
echo on
"%JAVA_HOME%\bin\java" -hotspot -ms64m -mx64m -classpath "%CLASSPATH%" -Dweblogic.Domain=test -Dbea.home="C:\bea" -Dweblogic.management.password=%WLS_PW% -Dweblogic.ProductionModeEnabled=%STARTMODE% -Dweblogic.Name=%SERVER_NAME% -Dweblogic.management.server=%ADMIN_URL% "-Djava.security.policy==C:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Server
goto finish

:finish
cd config\test
ENDLOCAL
 
Ranch Hand
Posts: 8943
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have u copied the SerializedSystemIni.dat and the file fileRealm.properties from the default mydomain directory to your new domain directory ?
 
darine darine
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
thanks for the reply.
yes i did,but do i have to edit anything with them?
I'm still having the same problem.
thanks again
 
Pradeep bhatt
Ranch Hand
Posts: 8943
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have u copied the SerializedSystemIni.dat and the file fileRealm.properties from the default mydomain directory to your new domain directory before starting the server ? It is required to copy these files before booting the server for the first time.
 
darine darine
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you agai.
fianly it worked,but i do not see any config.xml file there?i do have that file with the default
domain(mydomain)but i do not have it with the new domain,also even i changed the port to 7011,still my server responding on 7001 and not 7011.
thanks for the help again.
 
Pradeep bhatt
Ranch Hand
Posts: 8943
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
visit
http://edocs.bea.com/wls/docs61/adminguide/overview.html#1031797 for creating a domain.
Config.xml is automatically created when u create a domain from admin console.
 
darine darine
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you very much.
    Bookmark Topic Watch Topic
  • New Topic