官术网_书友最值得收藏!

Using Unicast for cluster communications

The Oracle WebLogic Server 12c can use either Multicast or Unicast for cluster communications. Since WebLogic version 10, the default cluster communication is the Unicast.

To improve Unicast reliability it's recommended to enable two extra configurations.

Getting ready

The first thing is to add a JVM argument to every WebLogic Managed Server instance of the cluster. The Administration Server must be running to make the changes.

After adding the JVM argument, the config.xml configuration file must be manually edited to make the second change. Therefore you will need to make sure every WebLogic Server instance is down, including the Administration Server.

How to do it...

Add the JVM argument:

  1. Access the Administration Console with your web browser at http://prod01.domain.local:7001/console.
  2. Click on the Lock & Edit button to start a new edit session.
  3. Navigate to Configuration | Server Start by clicking on the WebLogic Server name, then on the Server Start tab.
  4. Add the argument-Dweblogic.unicast.HttpPing=true to the Arguments field. The argument must be added to all Managed Server instances of PROD_Cluster: PROD_Server01, PROD_Server02, PROD_Server03, and PROD_Server04. Click on the Save button for every change.
  5. Click on the Activate Changes button.
  6. Navigate to Domain | Control by clicking on the PROD_DOMAIN link to the left and then on the Control tab.
  7. Select and shut down all servers from the list.

Edit the config.xml file:

  1. Log in as a wls user to the first machine prod01 and navigate to the folder:
    [wls@prod01]$ cd $DOMAIN_HOME/config
    
  2. Make a backup of the config.xml file:
    [wls@prod01]$ cp config.xml config.xml_backup
    
  3. Open config.xml to be edited:
    [wls@prod01]$ vi config.xml
    
  4. Find the <cluster> definition tag of PROD_Cluster:
        <cluster>
            <name>PROD_Cluster</name>
            <cluster-messaging-mode>unicast</cluster-messaging-mode>
        </cluster>
  5. Add the <message-ordering-enabled tag:
        <cluster>
            <name>PROD_Cluster</name>
            <cluster-messaging-mode>unicast</cluster-messaging-mode>
            <message-ordering-enabled>true</message-ordering-enabled>
        </cluster>
  6. Type :wq! to save the file and exit.
  7. Copy the file to all machines in the domain:
    [wls@prod01]$ scp config.xml wls@prod02:$DOMAIN_HOME/config
    
  8. Start the Administration Server.

How it works...

The-Dweblogic.unicast.HttpPing=true argument enables an internal health check on Unicast communications that improves its reliability.

The <message-ordering-enabled> tag forces Unicast communications to be processed in order, avoiding some issues with JNDI updates and JMS Topics.

See also

  • Configuring HA WebLogic cluster parameters
  • Using Multicast for cluster communications
主站蜘蛛池模板: 三原县| 九龙县| 德惠市| 涟源市| 长沙县| 金坛市| 平谷区| 永德县| 咸丰县| 陈巴尔虎旗| 密山市| 哈密市| 灌南县| 麦盖提县| 平顶山市| 竹北市| 明光市| 兴仁县| 台北县| 屯门区| 嵊州市| 江油市| 鄂温| 孙吴县| 开鲁县| 扬中市| 宣恩县| 贺州市| 卓资县| 秀山| 临汾市| 乌兰察布市| 昌黎县| 温宿县| 马龙县| 庄浪县| 新郑市| 雅江县| 昌图县| 高阳县| 方正县|