Technical data

2 Starting and Stopping WebLogic Servers
2-16 Administration Guide
2. Starts its kernel-level services, which include logging and timer services.
3. Initializes subsystem-level services, which retrieve their configurations from
MBeans. These services include the following:
4. Deploys modules in the appropriate container and in the order that you specify in
the WebLogic Server Administration Console.
5. Loads and runs any startup classes that are configured.
Adding a WebLogic Managed Server to the
Domain
Before you can run a WebLogic Server as a managed server, you must first create an
entry for that server in the configuration for the domain. To do this, do the following:
1. Start the Administration Server for the domain.
2. Invoke the Administration Console by pointing your browser at
http://hostname:port/console, where hostname is the name of the
machine where the Administration Server is running and
port is the listen port
number that you have configured for the Administration Server (default is 7001).
3. Create an entry for the server machine (Machines
→Create a new machine) (if it
is different than the Administration Server machine).
n Security Service
n RMI Service
n Cluster Service
n IIOP Service
n Naming Service
n RMI Naming Service
n File Service
n JCA Container
n JDBC Container
n EJB Container
n Web Container
n Deployment Manager
n JMS Provider
n Remote Management
n Transaction Service