|
|
This section contains information on the following subjects:
A domain is the basic administration unit for WebLogic Event Server. It consists of one WebLogic Event Server instance, zero or more deployed applications, and logically related resources and services that are managed, collectively, as one unit.
After you install WebLogic Event Server, you can use the empty domain called BEA_HOME/user_projects/domains/wlevs20_domain to deploy your applications, or you can use it as a template to help you create your own domain, where BEA_HOME refers to the parent directory of the main WebLogic Event Server installation directory such as d:/beahome.
The following list describes the important files and directories in a domain, relative to the main domain directory:
deployments.xml—XML file that contains the list of applications, packaged as OSGi bundles, that are currently deployed to the WebLogic Event Server instance of this domain.startwlevs.cmd—Command file used to start an instance of WebLogic Event Server. The UNIX equivalent is called startwlevs.sh.stopwlevs.cmd—Command file used to stop an instance of WebLogic Event Server. The UNIX equivalent is called stopwlevs.sh.config/config.xml—XML file that describes the services that have been configured for the WebLogic Event Server instance. Services include logging, debugging, Jetty Web Service, and JDBC data sources.applications—Default directory that contains the OSGi bundles and XML configuration files for the deployed applications, or those that are listed in the deployments.xml file. Each application lives in its own subdirectory of the applications directory.config/security*—Files that configure security for the domain.
Creating a WebLogic Event Server domain entails manually copying the sample empty domain to a new directory. In particular, copy the directory that contains the sample domain, called wlevs20_domain, to a new directory under the BEA_HOME\user_projects\domains directory. Name the new directory the same as the name of your new domain.
For example, if you installed WebLogic Event Server in the d:\beahome2\wlevs20 directory and want to create a new domain called myDomain, the copy command would be:
prompt> cd d:\beahome2\user_projects\domains
prompt> cp -r wlevs20_domain myDomain
Each WebLogic Event Server domain contains a command script that starts a server instance; by default, the script is called startwlevs.cmd (Windows) or startwlevs.sh (UNIX). The script to stop the server is called stopwlevs.cmd (Windows) or stopwlevs.sh (UNIX).
To start an instance of WebLogic Event Server:
JAVA_HOME variable in the server start script points to the correct JRockit JDK. If it does not, edit the script.
The server start script is located in the main domain directory. For example, the HelloWorld domain is located in WLEVS_HOME/samples/domains/helloworld_domain, where WLEVS_HOME refers to the main WebLogic Event Server installation directory, such as /beahome_wlevs/wlevs20.
If using the JRockit JDK installed with WebLogic Real Time 2.0, the JAVA_HOME variable should be set as follows:
JAVA_HOME=BEA_HOME_WLRT/jrockit-realtime20_150_11 (UNIX) set JAVA_HOME=BEA_HOME_WLRT\jrockit-realtime20_150_11 (Windows)
where BEA_HOME_WLRT refers to the installation directory of WebLogic Real Time 2.0, such as /beahome_wlrt (UNIX) or c:\beahome_wlrt (Windows).
If using the JRockit JDK installed with WebLogic Event Server 2.0, the JAVA_HOME variable should be set as follows:
JAVA_HOME=BEA_HOME_WLEVS/jrockit-R27.3.0-106-1.5.0_11 (UNIX) set JAVA_HOME=BEA_HOME_WLEVS\jrockit-R27.3.0-106-1.5.0_11 (Windows)
where BEA_HOME_WLEVS refers to the installation directory of WebLogic Event Server 2.0, such as /beahome_wlevs (UNIX) or c:\beahome_wlevs (Windows).
prompt> cd C:\bea_wlevs\wlevs20\samples\domains\helloworld_domain
startwlevs.cmd (Windows) or startwlevs.sh (UNIX) script:prompt> startwlevs.cmd
If you are using the JRockit JDK included in WebLogic Real Time 2.0, enable the deterministic garbage collector by passing the -dgc parameter to the command:
prompt> startwlevs.cmd -dgc
To stop a running WebLogic Event Server:
prompt> cd C:\bea_wlevs\wlevs20\samples\domains\helloworld_domain
stopwlevs.cmd (Windows) or stopwlevs.sh (UNIX) script. Use the -url argument to pass the URL that establishes a JMX connection to the server you want to stop. This URL takes the form service:jmx:rmi:///jndi/rmi://host:jmxport/jmxrmi, where host refers to the computer hosting the server and jmxport refers to the server’s JMX port, configured in config.xml file. For example: prompt> stopwlevs.sh -url service:jmx:rmi:///jndi/rmi://ariel:1099/jmxrmi
In the example, the host is ariel and the JMX port is 1099.
See
Table 5-1, Connection Arguments, on page 5-6 for additional details about the -url argument.
After creating your own WebLogic Event Server domain:
|