Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create and configure machines to run on UNIX

A machine is the logical representation of the computer that hosts one or more WebLogic Server instances. Each Managed Server must be assigned to a machine.

To create and configure machines:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane of the Console, expand Environment and select Machines.

    The Machines table displays in the right pane showing all the machines defined in the domain.

  3. Click New.
  4. Enter a name for the new machine in the Name attribute field.

    This name is used to identify the machine within the WebLogic Server domain. This name does not have to correspond to the machine's network name.

  5. Select UNIX in the Machine OS field.
  6. Click OK.

    The new machine is displayed in the Machines table.

  7. Select the name of the machine you just created.
  8. Select Configuration > General.
    1. To specify a non-privileged user account under which the server instance runs, place a check mark in the Enable Post-bind UID field and enter the user ID in the Post-Bind UID field.

      The user ID that you enter must have read, write, and execute privileges within the Oracle Middleware directory, the WebLogic Server product directory tree, and your domain directory.

      The default value of the Post-Bind UID field, nobody, is a standard UNIX account that provides the least possible privileges. While the nobody account is acceptable for use in a development environment, in a production environment, Oracle recommends that you create an operating-system user account specifically for running instances of WebLogic Server. See Securing the WebLogic Server Host.

    2. To specify a non-privileged group instead of (or in addition to) providing a user ID, place a check mark in the Enable Post-bind GID field and enter the group ID in the Post-Bind GID field.
  9. Select the Node Manager tab.
    1. Select the Node Manager type from the drop-down list in the Type field.

      For more information on Node Manager types, see Administering Node Manager for Oracle WebLogic Server.

    2. Enter the DNS name or IP address upon which Node Manager listens in the Listen Address box.

      If you identify the Listen Address by IP address, you must disable Host Name Verification on Administration Servers that will access Node Manager. For more information and instructions, see "Using Hostname Verification" in Administering Security for Oracle WebLogic Server.

    3. Enter a value in the Listen Port field. This is the port where Node Manager listens for incoming requests.
    4. If you have set the Type field to SSH or RSH, you should specify values in the Node Manager Home and Shell Command fields.

      For more information on configuring Node Manager using SSH or RSH, see Administering Node Manager for Oracle WebLogic Server.

  10. Click Save.
  11. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).


The new machine entry now specifies the attributes required to connect to the Node Manager process running on the machine, as well as identify which WebLogic Server instances reside on the machine. For information on assiging servers to a machine, see Assign server instances to machines.

Back to Top