> Configuration and User Guide > Adding Managed Servers to a WLS-VE Domain

Configuration and User Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Adding Managed Servers to a WLS-VE Domain

The following topics describe how to create and add Managed Server instances to an existing WLS-VE domain created with the P2V utility.

 

Steps for Adding a Managed Server to WLS-VE Domain

After using the P2V utility to convert a physical domain to a virtual domain to the hypervisor environment, you may need to add server instances to the WLS-VE domain. This section explains how to add a Managed Server to a WLS-VE domain.

  1. Use the VMware VI Client to start the Administration Server in the WLS-VE domain, as described in Starting WLS-VE from the VMware VI Client.
  2. Start the WLS administration console, as described in Starting the Administration Console.
  3. Create a new Managed Server but do not attempt to start it.
    4. Note: If you try to start the Managed Server you will get the following error message:
    “The server does not have a machine associated with it. All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running node manager or you are not authorized to perform the action requested.”
  4. On the launcher system, change to the virtual directory of the domain that has been transferred. For example:
    5. bea_home/user_projects/domains/testdomain/virtual
  5. Make a copy of the LVM information file for the newly created Managed Server. For example:

    6. cp AdminServer_lvm_vmware.info to Managed1Server_lvm_vmware.info

  6. Using an existing WLS-VE start script as a template, create a new startup script for the Managed Server, as shown in Listing 12-1.
    7. Listing 12-1 
    export WL_SERVER_NAME=managed1
    export ADMIN_URL=http://100.90.80.201:7001
    export LVM_NAME=managed1
    export LVM_CPUS=1
    export LVM_MEMORY=1024
    export LVM_DISKSIZE=500
    export LVM_IP_ADDRESS=100.90.80.202
    export LVM_NETMASK=255.255.248.0
    export LVM_GATEWAY=100.90.128.1
    export LVM_DNS_SERVERS=10.10.0.86
    export LVM_DOMAIN_NAME=domain.com
    export LVM_SSH=on
    export LVM_SSH_PUBLIC_KEY=
    export LVM_SSH_UNSAFE_PASSWORD=
    export LVM_SYSLOG_RECEIVER=
    export LVM_START_MODE=passive
    export LVM_INFO=/usr/local/bea_home/user_projects/domains/testdomain/virtual/Managed1Server_lvm_vmware.info
    /usr/local/bea_home/user_projects/domains/testdomain9/virtual/commonVEStart.sh
    Note: If the LVM_SSH_PUBLIC_KEY parameter is set to the public_key file, the LiquidVM launcher will install the public_key on LVM authorized_keys.

    For a description of all the start script properties, see The P2V-Generated Start Script Properties.

  7. Run the newly created startup script to start the Managed Server in passive mode (LVM_START_MODE=passive, as shown in Listing 12-1), as follows:

    8. > startManaged1Server.sh (or .cmd on Windows)

  8. Use the LiquidVM SSH service to copy the following files to the local disk for the Managed Server:
    • boot.properties
    • security .ldift files
    • SerializedSystemIni.dat
    • BEA patches
      • Note: If you are using public key authentication for SSH, and if the LVM_SSH_PUBLIC_KEY parameter was not set to the public_key file, then you also need to copy your public key file to the /etc/ssh/authorized_keys directory.

      After copying is complete, the local disk should contain the following files: 

      /domain/servers/managed1/security/boot.properties
      /domain/security/*.ldift
      /domain/security/SerializedSystemIni.dat
      /bea/patch_*

      For more information on using the SSH service, see Using the LiquidVM SSH Service.

  9. Power off the Managed Server.
  10. Edit the startup script to change from passive mode to active mode set, as follows:
    LVM_START_MODE=active or 'LVM_START_MODE='
  11. Run the startup script again to start the Managed Server in active mode.

    12. > startManaged1Server.sh (or .cmd on Windows)

 

The P2V-Generated Start Script Properties

Table 12-1 describes all the properties in the Administration Server and Managed Server start scripts generated by the P2V Domain Conversion utility.

Table 12-1 WLS-VE Start-up Options 
Property
Description
WL_SERVER_NAME
The name of the WLS instance in the domain.
ADMIN_URL
Required for Managed Servers.
The listen address (host name or IP address) and port number of the Administration Server for the domain.
This value must be set if you are configuring a Managed Server. For the Administration Server, ADMIN_URL must be left blank.
LVM_NAME
Required for all servers.
The name of the virtual server to be started. In VMware, SERVER_NAME is called WLS-SERVER_NAME. This property corresponds to the server name that you specified when you created the domain.
LVM_CPUS
The number of CPUs to use (1,2, or 4).
LVM_MEMORY
The amount of memory allocated to the virtual machine.
LVM_DISKSIZE
The size of the local disk allocated to the virtual machine. The default is defined in MB as 1024.
For details about the LiquidVM local disk, see Using the Virtual Local Disk.
LVM_IP_ADDRESS
The IP address this LVM should use. If left unset, the LVM uses DHCP to dynamically obtain an IP address
LVM_NETMASK
The subnet mask for your network. You need to set this value if you are not using DHCP or you are not using default settings for netmask. The default netmask is 255.255.255.0.
LVM_GATEWAY
The octet (###.###.###.###) for the gateway between your current network and the one you want to access. You need to set this value if you are not using DHCP. The standard gateway is the static IP address masked with the set netmask, with a 1 in the lowest octet; for example, if the netmask is the standard 255.255.255.0 and the static IP is 172.23.80.102, then the default gateway is 172.23.80.1. If the netmask is 255.255.0.0 and the static IP address is the same (172.23.80.102), then the gateway is 172.23.0.1.
LVM_DNS_SERVER
The DNS server the LVM should use.
LVM_DOMAIN_NAME
The network domain name for the LVM instance.
LVM_SSH
The SSH service mode to be used (on|off). The default is off. If you set LVM_START_MODE to passive, SSH is used by default.
LVM_SSH_PUBLIC_KEY
The local path to the SSH public key. Specify a value for this property if you are using public/private key authentication for the SSH service (recommended).
LVM_SSH_UNSAFE_PASSWORD
A clear-text password to be used to log into the LiquidVM instance over SSH. This password is not secure because it is stored in clear text. Do not use the unsafe password option in a production environment. BEA recommends that you use public/private key authentication.
LVM_SYSLOG_RECEIVER
A hostname or IP address of a remote syslog receiver.
LVM_START_MODE
Required if starting the server in passive mode.
The mode in which to start the LiquidVM instance (active|passive).
Passive mode allows you to start only the LVM services, included the SSH service. WLS is not started. Once the LVM is started in passive mode, you can log into the LVM instance using SSH and transfer files from the launcher machine, such as domains that you have created, to the local disk of the virtual machine. When you have finished transferring your files, you can restart the server.
Active mode, the default, starts both LVM and WLS.
LVM_INFO
The location of the bea.lvm.info file created by the LiquidVM Configuration Wizard on your local machine. This file contains the default settings for LiquidVM for your virtualization environment. By default, the bea.lvm.info file is created in your user home directory. If you change the location of the bea.lvm.info file, you must set this property to the new location. For more information about the bea.lvm.info file, see Understanding the bea.lvm.info File.


  Back to Top       Previous  Next