Starting and Stopping Servers

5/9

2 Starting and Stopping Servers

This chapter describes how to start and stop server instances in WebLogic Server 10.3.6. The method you choose depends on whether you prefer using the Administration Console or a command line, and on whether you are using Node Manager to manage the server ‘s life cycle. No matter how you start a server, the end result passes a plant of configuration options to initialize a Java Virtual Machine ( JVM ). The server exemplify runs within the JVM, and the JVM can host only one server example .
This chapter includes the following sections :
For a concise overview of starting and stopping servers, see chapter 6, “ Starting and Stopping Servers : agile address. ”

Version Requirements for a Domain

The Administration Server and all Managed Servers in a knowledge domain must be the same WebLogic Server version. The Administration Server must be either at the lapp Maintenance Pack ( MP ) tied or at a belated MP level than the Managed Servers. For model, if the Managed Servers are at version 9.1, then the Administration Server can be either version 9.1, 9.1 MP1 or higher. however, if the Managed Servers are at MP1, then the Administration Server must be at MP1 or higher .

Starting an Administration Server with a Startup Script

An Administration Server is a WebLogic Server example that maintains shape data for a domain. In a exploitation environment, it is normally sufficient to start an Administration Server and deploy your applications immediately onto the Administration Server. In a production environment, you create Managed Servers to run applications. For more information about Administration Servers and Managed Servers, see “ Understanding WebLogic Server Domains “ in Understanding Domain Configuration for Oracle WebLogic Server .
You can start an Administration Server with a nonpayment startup script or create your own. To start an Administration Server with the WebLogic Server-included startup handwriting :

  1. If you have not already done so, use the Configuration Wizard or WebLogic Scripting Tool ( WLST ) to create a domain .
    See Creating Domains Using the Configuration Wizard or “ produce Domains Using WLST Offline “ in Oracle WebLogic Scripting Tool .
  2. Open a shell ( command prompt ) on the calculator on which you created the domain .
  3. change to the directory in which you located the domain .
    By default option, this directory is MW_HOME \user_projects\domains\ DOMAIN_NAME, where DOMAIN_NAME is the root directory of the domain. ( The name of this directory is the list of the world. )
  4. Run one of the following scripts :

    • bin/startWebLogic.cmd ( Windows )
    • bin\startWebLogic.sh ( UNIX and Windows. On Windows, this script supports the MKS and Cygnus BASH UNIX blast emulators. )
      eminence :
      If you use a Configuration Wizard template that is provided by WebLogic Server, your domain directory includes a start script named startWebLogic. If you use a domain template from another source, the wizard might not create a start script, or it might create a script with a different name. The template designer determines whether the wizard creates a start script and the name of the script.
      If you use a Configuration Wizard template that is provided by WebLogic Server, your world directory includes a start handwriting named. If you use a domain template from another source, the sorcerer might not create a startle script, or it might create a script with a different diagnose. The template designer determines whether the charming creates a start handwriting and the name of the script. The come erroneousness occurs when using startWebLogic.cmd to boot WebLogic Server :

      Enter username to boot WebLogic server:weblogic
         
         
         >
         
      

      This error is caused by installing a 32-bit JDK on a 64-bit OS. To avoid this error, install a 64-bit JDK on a 64-bit OS .

The startWebLogic handwriting does the following :

  1. Sets environment variables by invoking DOMAIN_NAME \bin\setDomainEnv.cmd ( setDomainEnv.sh on UNIX ), where DOMAIN_NAME is the directory in which you located the sphere ; for model, WL_HOME \user_projects\domains\ DOMAIN_NAME, and where WL_HOME is the location in which you installed WebLogic Server .
    bill :
    setDomainEnv is designed to be sourced from other scripts, such as the startWebLogic script. setDomainEnv should not be called directly from within an interactive shell. Doing so can cause unpredictable issues in the domain. is designed to be sourced from other scripts, such as thescript.should not be called directly from within an interactional blast. Doing so can cause unpredictable issues in the sphere .
  2. Invokes the java weblogic.Server command, which starts a JVM that is configured to run a WebLogic Server exemplify .
    When the server successfully completes its startup march, it writes the pursuit message to standard out ( which, by nonpayment, is the command window ) :

        
    

Starting an Administration Server from the Windows Start Menu

When you create an Administration Server on a Windows calculator, the Configuration Wizard creates a shortcut on the Start Menu for starting the server ( User Projects > DOMAIN_NAME > Start Admin Server for WebLogic Server Domain ) .
The command that the Configuration Wizard adds to the Start menu opens a command windowpane and calls the startup script that is described in Starting an Administration Server with a Startup Script. When the server has successfully completed its startup march, it writes the pursue message to standard out ( which, by default, is the dominate window ) :

    

Starting an Administration Server with the java weblogic.Server Command

The weblogic.Server class is the main class for a WebLogic Server exemplify. You start a server example by directly invoking weblogic.Server in a Java command .
bill :
Oracle recommends using java weblogic.Server primarily for initial development but not as a standard mechanism for starting production systems for the following reasons:

  • java weblogic.Server will not function if you select a product directory outside of the Oracle Middleware Home directory .
  • When executing java weblogic.Server, patches will not be recognized by the WebLogic Server run clock time .

Oracle recommends usingprimarily for initial development but not as a standard mechanism for starting production systems for the adopt reasons : For more information, see “ weblogic.Server Command-Line Reference “ and “ Using the weblogic.Server Command Line to Start a Server Instance “ in Command Reference for Oracle WebLogic Server .

Starting an Administration Server Using WLST and Node Manager

Node Manager is a utility for distant control of WebLogic Server instances. Using Node Manager you can control and monitor Managed Servers and besides, begin, end, and restart Administration Servers .
You can access these Node Manager features using the WebLogic Scripting Tool commands and scripts. If you use the nmStart command with WLST connected to a Node Manager, Node Manager supports monitoring, stop, and restarting the Administration Server .
“ Using WLST and Node Manager to Manage Servers “ in Oracle WebLogic Scripting Tool describes how to start the Administration Server with WLST and Node Manager. “ How Node Manager Starts an Administration Server “ in the Node Manager Administrator ‘s Guide for Oracle WebLogic Server describes how Node Manager accomplishes this process .
The WebLogic Server customs installation process optionally installs and starts Node Manager as a Windows service on Windows systems. Oracle recommends running Node Manager as an operate on system service indeed that it mechanically restarts in the consequence of system bankruptcy or boot, and using Node Manager to start and restart both Administration and Managed Servers .
For more information, see “ About Installing Node Manager as a Windows Service “ in the Oracle WebLogic Server Installation Guide and “ Restart Administration and Managed Servers “ in the Node Manager Administrator ‘s Guide for Oracle WebLogic Server .

Starting an Administration Server Using WLST Without Node Manager

The WLST startServer control starts the Administration Server without using Node Manager. The server runs in a separate process from WLST ; exiting WLST does not shut down the server. See “ Starting an Administration Server Without Node Manager “ in Oracle WebLogic Scripting Tool .

Starting Managed Servers with a Startup Script

A Managed Server is a WebLogic Server case that runs deployed applications. It refers to the Administration Server for all of its shape and deployment information. normally, you use wangle Servers to run applications in a product environment .
For more information about Managed Servers and Administration Servers, see “ Understanding WebLogic Server Domains “ in Understanding Domain Configuration for Oracle WebLogic Server .
If you use one of the Configuration Wizard templates that WebLogic Server provides, your domain directory includes a start script named startManagedWebLogic that you can use to start Managed Servers. You can use this script to start all the Managed Servers in a bunch .
For more data on knowledge domain directory files, see “ Domain Configuration Files “ in Understanding Domain Configuration for Oracle WebLogic Server .
This script does not use the Node Manager to start and manage the server. alternatively, it uses a Java command to invoke the weblogic.Server class, which is the main course for a WebLogic Server example. For information about invoking weblogic.Server in a Java command, see “ weblogic.Server Command-Line Reference “ in Command Reference for Oracle WebLogic Server .
To use the WebLogic Server scripts to start Managed Servers :

  1. consult to Starting Servers : Before You Begin for prerequisite tasks .
  2. If you have not already done so, create one or more wield Servers .
    See Creating Domains Using the Configuration Wizard or “ Create Managed Servers “ in the Oracle WebLogic Server Administration Console Help .
  3. If you have not already done indeed, start the sphere ‘s Administration Server .
  4. In a shell ( command prompt ) on the computer that hosts the Managed Server, change to the directory that contains the startManagedWebLogic script :

    • DOMAIN_NAME \bin\startManagedWebLogic.cmd ( Windows )
    • DOMAIN_NAME /bin/startManagedWebLogic.sh ( UNIX )
      where DOMAIN_NAME is the directory in which you located the domain. By default, this directory is MW_HOME \user_projects\domains\ DOMAIN_NAME .
  5. Enter one of the follow commands :

    • startManagedWebLogic.cmd managed_server_name admin_url ( Windows )
    • startManagedWebLogic.sh managed_server_name admin_url ( UNIX )
      where managed_server_name specifies the name of the Managed Server and admin_url specifies the heed address ( host name, IP address, or DNS name ) and port number of the knowledge domain ‘s Administration Server .
      For example, the surveil command uses startManagedWebLogic.cmd to start a Managed Server named myManagedServer. The listen address for the domain ‘s Administration Server is AdminHost:7001 :

      c:\Oracle\Middleware\user_projects\domains\mydomain\bin\startManagedWebLogic.cmd myManagedServer http://AdminHost:7001 
      
  6. For each Managed Server that you want to start, open a separate command shell and follow steps 4 and 5. If you are starting Managed Servers on another machine, log in to that machine ( remotely or locally ) and then follow steps 4 and 5.

For information on running Managed Servers on a distant WebLogic Server host, see “ Creating and Starting a Managed Server on a distant Machine “ in Creating Templates and Domains Using the Pack and Unpack Commands .
For information on configuring a connection to the Administration Server, see Configuring Managed Server Connections to the Administration Server .
The startManagedWebLogic script does the succeed :

  1. Calls the startWebLogic handwriting, which sets the environment variables by invoking WL_HOME \user_projects\domains\ DOMAIN_NAME \bin\setDomainEnv.cmd ( setDomainEnv.sh on UNIX ), where WL_HOME is the location in which you installed WebLogic Server .
    note :
    setDomainEnv is designed to be sourced from other scripts, such as the startWebLogic script. setDomainEnv should not be called directly from within an interactive shell. Doing so can cause unpredictable issues in the domain. is designed to be sourced from other scripts, such as thescript.should not be called directly from within an interactional blast. Doing therefore can cause unpredictable issues in the knowledge domain .
  2. Invokes the java weblogic.Server command, which starts a JVM that is configured to run a WebLogic Server exemplify .
    When the waiter successfully completes its startup process, it writes the watch message to standard out ( which, by nonpayment, is the command window ) :

      <000360>  
    

Starting Managed Servers from the Administration Console

To use the Administration Console to start a Managed Server, see “ Start Managed Servers from the Administration Console “ in the Oracle WebLogic Server Administration Console Help .

Starting Managed Servers and Clusters with WLST and Node Manager

To start Managed Servers and clusters using WLST and Node Manager, see “ Using Node Manager to Start Managed Servers in a Domain or Cluster “ in Oracle WebLogic Scripting Tool. For detailed information about WebLogic Server clusters, see “ Setting up WebLogic Clusters “ in Using Clusters for Oracle WebLogic Server .

Starting Managed Servers with the java weblogic.Server Command

The weblogic.Server course is the main class for a WebLogic Server exemplify. You start a waiter example by directly invoking weblogic.Server in a Java control. See “ weblogic.Server Command-Line Reference “ and “ Using the weblogic.Server Command Line to Start a Server Instance “ in Command Reference for Oracle WebLogic Server .

Starting a Managed Server When the Administration Server Is Unavailable

normally, a Managed Server contacts the Administration Server during its inauguration sequence to retrieve its shape information. If a Managed Server can not connect to the Administration Server during inauguration, it can retrieve its configuration by reading its locally cached configuration data from the config directory .
notice :
The first time you start a Managed Server instance, it must be able to contact the Administration Server. Thereafter, the Managed Server instance can start even if the Administration Server is unavailable. The first fourth dimension you start a Managed Server exemplify, it must be able to contact the Administration Server. Thereafter, the Managed Server example can start even if the Administration Server is unavailable. For more information on starting Managed Servers when the Administration Server is unavailable, see Starting a Managed Server When the Administration Server Is not accessible .

Limiting Run-Time Footprint When Starting WebLogic Server

typically when you start a WebLogic Server exemplify, all services are started including EJB, JMS, Connector, Clustering, Deployment, Management, and thus forth. however, WebLogic Server provides a inauguration choice that offers a lighter weight run-time footprint by excluding a subset of these services from being started. This inauguration manner can result in flying inauguration times for WebLogic Server and a smaller resource footprint on the host machine .
The hardening of services started in a WebLogic Server example are determined by the Server Type startup command, which takes a server type option. There are two waiter type options :

  • wls — All services are started ( nonpayment )
  • wlx — All but the watch services are started :

    • enterprise JavaBeans ( EJB )
    • Java EE Connector Architecture ( JCA )
    • Java Message Service ( JMS )

If a WebLogic Server case does not require the habit of these services, running the light weight run time rather can provide a count of operation efficiencies .

Server Type Startup Command

You can run the lighter weight run-time example in any WebLogic domain. A WebLogic domain does not require any extra configuration settings to support this waiter type. however, any JMS or Messaging Bridge resources and applications that include EJBs or resource adapters will fail to deploy on servers started with the wlx server type option .
You can start a lighter burden run-time example by specifying the surveil weblogic.Server command option :

-DserverType="wlx"

You can use the -DserverType="wlx" choice in any of the methods for starting WebLogic Server, such as :

  • directly on the command argumentation, as described in Starting an Administration Server with the coffee weblogic.Server Command and Starting Managed Servers with the coffee weblogic.Server Command
  • In a server beginning handwriting, as described in Starting an Administration Server with a Startup Script and Starting Managed Servers with a Startup Script
  • When using WLST, as described in “ Managing the Server Life Cycle ” in Oracle WebLogic Scripting Tool
  • When using Node Manager, as described in “ Using Node Manager to Control Servers “ in Node Manager Administrator ‘s Guide for Oracle WebLogic Server .
  • When using the weblogic.Server command to create a world, as described in “ Using the weblogic.Server Command Line to Create a Domain ” in Command Reference for Oracle WebLogic Server

Limitations

Note the pursue limitations regarding lighter weight run-time instances of WebLogic Server :

  • WebLogic Server contains several services that internally use the EJB service. If you start a lighter weight run-time case, some the follow features are not available :

    • management EJBs
      These EJBs are used to support JSR-77. If the EJB service is disabled, JSR-77 support is unavailable, besides. however, all other management APIs are placid available .
    • Remote Deployer from WebLogic Server 9.0 and 9.1
      The Remote Deployer EJB is only used by the weblogic.Deployer utility in WebLogic Server 9.0 and 9.1 when the -remote choice is specified. You can still use the -remote option from the weblogic.Deployer utility in Version 9.2 and later releases .
  • If the Administration Server is started as a lighter weight run-time exemplify, the Administration Console does not display links to JMS, EJB, and Resource Adapters. This provides a ocular clue regarding the server type of the Administration Server. however, if the Administration Server is started as the default server type ( that is, not started using the wlx server type choice ), the Administration Console does not distinguish lighter weight Managed Server instances that are running in the world .

Shutting Down Instances of WebLogic Server

It is recommended that you shutdown WebLogic Server instances through the Administration Console. See “ Shut Down a Server Instance, ” “ Control Graceful Shutdowns “, and “ closure servers in a cluster “ in the Oracle WebLogic Server Administration Console Help .
On Windows, you can stop Administration Servers that you have created using the Configuration Wizard from the Start menu .

Shutting Down Servers with a Stop Script

If you use a Configuration Wizard template that is provided by WebLogic Server, the bin directory under your world directory includes a diaphragm script named stopWebLogic that you can use to stop an Administration Server and one named stopManagedWebLogic for stopping Managed Servers. To use the scripts, you must set SERVER_NAME, ADMIN_URL, USERID, and PASSWORD as environment variables or specify them on the dominate line. When using the stopWebLogic script, if you do not specify SERVER_NAME, the Administration Server name is used by default .

  • For an Administration Server, appeal :
    DOMAIN_NAME \bin\stopWeblogic.cmd username password admin_url ( Windows )
    DOMAIN_NAME /bin/stopWeblogic.sh username password admin_url ( UNIX )
  • For Managed Servers, raise :
    DOMAIN_NAME \bin\stopManagedWeblogic.cmd managed_server_name admin_url username password ( Windows )
    DOMAIN_NAME /bin/stopManagedWeblogic.sh managed_server_name admin_url username password ( UNIX )
    bill :
    On the command line, specify parameters in the order shown. User credentials come before the ADMIN_URL with stopWebLogic.cmd and after the ADMIN_URL with stopManagedWebLogic.cmd. On the command credit line, specify parameters in the order shown. User credentials come before thewithand after thewith

Killing the JVM

Each WebLogic Server example runs in its own JVM. If you are unable to shut down a server case using the methods described in the previous sections, you can use an operating arrangement command to kill the JVM .
circumspection :
If you kill the JVM, the server immediately stops all processing. Any session data is lost. If you kill the JVM for an Administration Server while the server is writing to the config.xml file, you can corrupt the config.xml file. If you kill the JVM, the server immediately stops all processing. Any session data is lost. If you kill the JVM for an Administration Server while the server is writing to thefile, you can corrupt thefile. Some common ways to kill the JVM are as follows :

  • If the shell ( command prompt ) in which you start the server is still open, you can type Ctrl-C .
  • On a Windows calculator, you can use the Task Manager to kill a JVM .
  • On a UNIX computer, you can use the ps instruction to list all run processes. then you can use the kill command to kill the JVM .
source : https://thefartiste.com
Category : Tech

About admin

I am the owner of the website thefartiste.com, my purpose is to bring all the most useful information to users.

Check Also

articlewriting1

Manage participants in a zoom meeting webinar

Call the people who attend the meet as follows Alternate host host Who scheduled the …

Leave a Reply

Your email address will not be published.