Starting WlssEchoServer on SIP Data Tier Server Machines

Monitoring and Troubleshooting 8-11 JAVA_HOMEbinjava {JAVA_VM} {MEM_ARGS} {JAVA_OPTIONS} \ -Dweblogic.Name={SERVER_NAME} \ -Dweblogic.management.username={WLS_USER} \ -Dweblogic.management.password={WLS_PW} \ -Dweblogic.management.server={ADMIN_URL} \ -Djava.security.policy={WL_HOME}serverlibweblogic.policy \ weblogic.Server to read: JAVA_HOMEbinjava -classpath WLSS_HOMEserverlibwlsswlssechosvr.jar \ -Dwlss.ha.echoserver.ipaddress=192.168.1.4 \ -Dwlss.ha.echoserver.port=6734 com.bea.wcp.util.WlssEchoServer JAVA_HOMEbinjava {JAVA_VM} {MEM_ARGS} {JAVA_OPTIONS} \ -Dweblogic.Name={SERVER_NAME} \ -Dweblogic.management.username={WLS_USER} \ -Dweblogic.management.password={WLS_PW} \ -Dweblogic.management.server={ADMIN_URL} \ -Djava.security.policy={WL_HOME}serverlibweblogic.policy \ weblogic.Server

8.3.2 Enabling and Configuring the Heartbeat Mechanism on Servers

To enable the WlssEchoServer heartbeat mechanism, you must include the -Dreplica.host.monitor.enabled JVM argument in the command you use to start all engine and SIP data tier servers. Oracle recommends adding this option directly to the script used to start Managed Servers in your system. For example, in the startManagedWebLogic.sh script, change the line: JAVA_OPTIONS=-Dweblogic.attribute=value -Djava.attribute=value to read: JAVA_OPTIONS=-Dreplica.host.monitor.enabled=true Several additional JVM options configure the functioning of the heartbeat mechanism. Table 8–1 describes the options used to configure failure detection.

8.4 Configuring SNMP

Oracle WebLogic Communication Services includes a dedicated SNMP MIB to monitor activity on engine tier and SIP data tier server instances. The Oracle WebLogic Communication Services MIB is available on both Managed Servers and the Table 8–2 WlssEchoServer Options Option Description -Dreplica.host.monitor.enabled This system property is required on both engine and SIP data tier servers to enable the heartbeat mechanism. -Dwlss.ha.heartbeat.interval Specifies the number of milliseconds between heartbeat messages. By default heartbeats are sent every 1,000 milliseconds. -Dwlss.ha.heartbeat.count Specifies the number of consecutive, missed heartbeats that are permitted before a replica is determined to be offline. By default, a replica is marked offline if the WlssEchoServer process on the server fails to respond to 3 heartbeat messages. -Dwlss.ha.heartbeat.SoTimeout Specifies the UDP socket timeout value. 8-12 Oracle WebLogic Communications Server Administration Guide Administration Server of a domain. However, Oracle WebLogic Communication Services engine and SIP data tier traps are generated only by the Managed Server instances that make up each tier. If your Administration Server is not a target for the sipserver custom resource, it will generate only WebLogic Server SNMP traps for example, when a server in a cluster fails. Administrators should monitor both WebLogic Server and Oracle WebLogic Communication Services traps to evaluate the behavior of the entire domain.

8.4.1 Browsing the MIB

The Oracle WebLogic Communication Services MIB file is installed in WLSS_ HOME serverlibwlssBEA-WLSS-MIB.asn1. Use an available SNMP management tool or MIB browser to view the contents of this file. See also Section 8.5.2, Trap Descriptions for a description of common SNMP traps.

8.4.2 Steps for Configuring SNMP

To enable SNMP monitoring for the entire Oracle WebLogic Communication Services domain, follow these steps: 1. Login to the Administration Console for the Oracle WebLogic Communication Services domain.

2. In the left pane, select the Diagnostics SNMP node.

3. In the Server SNMP Agents table, click the New button to create a new agent.

4. Enter a unique name for the new SNMP agent for example, engine1snmp and click OK. 5. Select the newly-created SNMP agent from the Server SNMP Agents table.

6. On the Configuration General tab:

a. Select the Enabled check box to enable the agent. b. Enter an unused port number in the SNMP UDP Port field.

c. Click Save.

7. Repeat the above steps to generate a unique SNMP agent for each server in your

deployment SIP data tier server, engine tier server, and Administration Server. Note: Oracle WebLogic Communication Services MIB objects are read-only. You cannot modify a Oracle WebLogic Communication Services configuration using SNMP. Note: Ensure that you create a new Server SNMP agent, rather than a Domain-Scoped agent. Note: If you run multiple Managed Server instances on the same machine, each server instance must use a dedicated SNMP agent with a unique SNMP port number.