1. Server Manager Installation Guide
  2. Prerequisites for WebLogic Server

Prerequisites for WebLogic Server

Ensure the following prerequisites are met prior to running the Server Manager Console installer:

  • The Server Manager Console installer must be run with the same user who installed and is running WebLogic server. The user running the Server Manager Console installer should have read/write access to the directories pointed by TEMP and TMP Environment Variables. The TEMP and TMP Environment Variables must be configured to point to valid paths.

    Note:

    Linux/Solaris Platforms. The paths pointed to by TEMP and TMP environment variables should refer to the same mount point where the WebLogic Server is installed and where the Server Manager Console is to be installed. For example, the mount point might be /u01. If the variable points to a different mount point the Server Manager Console installation may fail with this message: permission denied on scf.properties file.

  • The machine on which the Server Manager Console will be installed must have adequate disk space to perform the installation.

  • You must create a new and separate WebLogic Server Domain in which you will install the Server Manager Console.

  • If there are other managed servers in the Domain in which you are attempting to install the Server Manager Console they must be in a STOPPED state at the time of installation. Only the AdminServer of the domain and the nodemanager associated with the domain should be running at the time of installation (see troubleshooting 5.6.2.4).

  • The Server Manager Console cannot be installed into a WebLogic Server Domain where a JD Edwards EnterpriseOne BSSV Instance/Server is already installed. Conversely, a JD Edwards EnterpriseOne BSSV Instance/Server cannot subsequently be installed into the same WebLogic domain where you install the Server Manager Console.

  • The nodemanager logical machine name must be known to the administrator performing the installation. This is necessary because the installer requires this value as an input. It is important to note that this value must be the logical nodemanager machine name, which is not necessarily the physical server name.

  • The nodemanager.properties file used by the nodemanager must have this value set to true (the default value is false):

    StartScriptEnabled=true

    Note that you must restart the nodemanager in order for any changed values to take effect. The nodemanager.properties file is typically located at this location:

    Microsoft Windows

    WebLogic Server 11g

    C:\Oracle\Middleware\wlserver_10.3\common\nodemanager\nodemanager.properties

    WebLogic Server 12c

    C:\Oracle\Middleware\Oracle_Home\user_projects\domains\<domain_name>\nodemanager\nodemanager.properties

    WebLogic Server 14c

    C:\Oracle\Middleware\Oracle_Home\user_projects\domains\<domain_name>\nodemanager\nodemanager.properties

    Linux and Solaris

    WebLogic Server 11g

    /u01/Oracle/Middleware/Oracle_Home/wlserver_10.3/common/nodemanager/nodemanager.properties

    WebLogic Server 12c

    /u01/Oracle/Middleware/Oracle_Home/user_projects/domains/<domain_name>/nodemanager/nodemanager.properties

    WebLogic Server 14c

    /u01/Oracle/Middleware/Oracle_Home/user_projects/domains/<domain_name>/nodemanager/nodemanager.properties

  • There must be a valid nodemanager associated with the WebLogic Domain into which the Server Manager Console will be installed as described below:

    Microsoft Windows

    Ensure the nodemanager is running as a Microsoft Windows service or using the startNodeManager.cmd program started from the command prompt.

    Linux and Solaris

    Ensure the nodemanager is started by using the startNodeManager.sh command.

  • You can also stop Node Manager using stopNodeManager.sh (for UNIX) and stopNodeManager.cmd (for Windows) under:

    <ORACLE_ HOME>\user_projects\domains<domain_name\bin\

    Other ways to stop Node Manager are as follows:

    Microsoft Windows

    Stopping the Windows service or by killing the nodemanager process.

    Linux and Solaris

    Killing the nodemanager process using this command:

    kill -9 <pid of nodemanager process>

  • Verify that the nodemanager is reachable to the AdminServer using this process:

    1. Login into WebLogic Server AdminServer console.

    2. Go to the Environment > Machines tab and select the nodemanager machine to which the Domain is registered.

    3. Go to the Monitoring tab and verify that Reachable is displayed. This value indicates that a valid nodemanager is configured with the WebLogic Server Domain and that it is running.

  • An AdminServer must be associated with the WebLogic Domain into which the Server Manager Console is to be installed and it must be running at the time of installation.

  • The administrator performing the installation must know the AdminServer http/t3 port number and the Hostname/IP Address on which the AdminServer is listening for http/t3 connections. You can find this value from the AdminServer logs or must be known because this value is configured when WebLogic is installed. Currently the https/t3s protocols are not supported for installing Server Manager Console software.

  • The administrator performing the installation will be prompted to input the path to the WebLogic Server directory during the install. The typical values are:

    Microsoft Windows

    WebLogic Server 11g

    C:\Oracle\Middleware\wlserver_10.3

    WebLogic Server 12c

    C:\Oracle\Middleware\Oracle_Home\wlserver

    WebLogic Server 14c

    C:\Oracle\Middleware\Oracle_Home\wlserver

    Linux and Solaris

    WebLogic Server 11g

    /u01/Oracle/Middleware/Oracle_Home/wlserver_10.3

    WebLogic Server 12c

    /u01/Oracle/Middleware/wlserver

    WebLogic Server 14c

    /u01/Oracle/Middleware/wlserver

  • The administrator performing the installation will be prompted to input the Listen port of the AdminServer, the admin userid and password of the AdminServer.

  • At the time of the Server Manager Console installation, the AdminServer cannot not be locked for editing. You can confirm this by determining if the "Lock & Edit" button is enabled in the WebLogic Admin Console.

    As a double-check, you can verify that no file named edit.lok exists in the Domain directory. If the file exists, you should delete it. The typical location is:

    Microsoft Windows

    C:\Oracle\Middleware\user_projects\domains\E1Apps\edit.lok

    Linux and Solaris

    /u01/Oracle/Middleware/user_projects/domains/E1Apps/edit.lok

  • The hosts file must have the entry for localhost (loopback).

  • The hosts file should have an entry for the correct IP Address of the machine mapping to the appropriate hostname of the machine.

    Microsoft Windows

    C:\Windows\System32\drivers\etc\hosts

    Linux and Solaris

    /etc/hosts

  • The hostname of the machine should not map to the IP Address 127.0.0.1, because that IP address is typically used for localhost.

  • The AdminServer must not have any particular Listen Address configured and it must be left blank. A blank setting specifies that it will listen for connection on all IP addresses available on the machine.