• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Himai Minh

why not to create domain

Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have create domian according webloic6.0 doc.
then i startup startweblogic.cmd, but startweblogic.cmd executeing window disappear after loading config.xml
and application server still doesn't startup.
doc below
/*----------webloic6.0 doc of creating domian ---------*/

To create a new domain, do the following:

Start the Administration Server under an existing domain such as mydomain.
Invoke the Administration Console by pointing your browser to: http://hostname ort/console
where hostname is the name of the machine where you started the Administration Server and port is the Administration Server's listen port (default is 7001).

Select mydomain��>Create or edit other domains.
This displays the domains table.

Select Default��>Create a new Domain.
Enter the name of the new domain and click Create.

Select the new domain from the list of domains at left to make that the current domain.
Now you will need to create an Administration Server entry for the new domain:
Select Servers��>Create a new Server.
Enter the name of the new Administration Server and click Create.
The Administration Console will have created a new subdirectory with the name of your domain and a configuration file, config.xml, under that subdirectory. Now you need to create an \applications subdirectory in that domain directory. You can create an \applications subdirectory in a command shell or, on Windows, by using Explorer.
The default mydomain directory contains start scripts for starting the WeLogic Server. For Windows installations, these are startWebLogic.cmd and startManagedWebLogic.cmd. For UNIX installations, these are startWebLogic.sh and startManagedWebLogic.sh. Copy these start scripts to the new domain directory.
You will need to edit the start scripts in a text editor. By default, the name of the domain is set as:
Replace mydomain with the name of the new domain.
By default the name of the Administration Server is set as:
Replace MyServer with the name of the new Administration Server.

At the end of the start script there is a cd command:
cd config\mydomain
Replace mydomain with the subdirectory name of the new domain. There is also a line in the start script that reads:
echo startWebLogic.cmd must be run from the config\mydomain
Replace mydomain here with the name of the new domain.

Copy the file SerializedSystemIni.dat and the file fileRealm.properties from the default mydomain directory to your new domain directory. Do not try to boot the new Administration Server before copying these files.
Once you have completed this procedure, you can start the Administration Server for your new domain.
/*----------webloic6.0 doc of creating domian ---------*/

Ranch Hand
Posts: 1871
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Try to check up your log files and see if there is anything specified in them. The logs folder exists under config-> domainname -> logs.
Just see if any of the log file provide any info as to the problem.


IBM/Websphere Forum Moderator

Consultant - Zensar Technologies ,Pune India.
Wanna see my flashlight? How about this tiny ad?
Free, earth friendly heat - from the CodeRanch trailboss
    Bookmark Topic Watch Topic
  • New Topic