JMS Server
JMS Module
Node Manager
Queue Manager
Persistent Store
第1题:
A customer wants to send JMS messages to a remote WebLogic server from a Java SE application over an unreliable network connection. Which feature of WebLogic JMS will enable the customer to send messages from a Java SE client to a JMS destination that is not always easily reached?()
第2题:
在Weblogic 10.X中的config.xml中标识JMS system-resource module的4个属性是()。
第3题:
A. 1 - Oracle Loader, 2 - Oracle Data Pump, 3 - Direct Path API
B. 1 - Oracle Data Pump, 2 - Direct Path API, 3 - Oracle Loader
C. 1 - Direct Path API, 2 - Oracle Loader, 3 - Oracle Data Pump
D. 1 - Oracle Loader, 2 - Direct Path API, 3 - Oracle Data Pump
第4题:
A customer needs to implement a Highly Available solution for JMS that has a primary data center and a backup. Which three steps would you perform when designing your solution?()
第5题:
Which two statements are true about interoperating with Oracle AQ JMS with Oracle WebLogic server ?()
第6题:
An application is using WebLogic JMS Store and Forward to forward messages from a local JMS queue a remote WebLogic JMS destination. You need to determine if the messages are being sent from the local Weblogic Server. Where do you find information and metrics about Store and Forward components in the WebLogic Admin Console?()
第7题:
Weblogic管理服务器不能提供()服务。
第8题:
我已经用JMS实现了对weblogic的server Name,Listen Port,webApp的名称、domain名称。现在想实现对weblogic的执行线程(executeQueue)、集群(cluster)、堆(heap)等,不知道应该怎么实现?
能,用jmx ,google一下这方面知识,由于从weblogic8升级到weblogic9发生了比较大的变化,以前对于weblogic8比较熟悉的人,也许到了weblogic9就不一定熟悉了,还需要了解才行,特别是监控方面差别比较大,由于9采用的jdk版本是1.5,监控8实现的java方式就不能用于9了。
就目前我得测试结论是:java实现weblogic的自定义监控对于9和10都是适用的,但是对于11却没有测试,还不知道方式是否相同,实际上从文档里面也可以看出,8系列是采用的许多管理的MBean接口在9中已经不推荐使用,标明是过时的了。
我这次通过java编程来实现weblogic9的自定义监控就发现,很多地方完全地不同了。
从界面上来看,已经完全不同于8,命令行监控方式也有一些大的变化。
这是我取得监控接口封装的类:
package lht.monitor.weblogic.main9;
import java.io.IOException;
import java.net.MalformedURLException;
import java.util.Hashtable;
import javax.management.MBeanServerConnection;
import javax.management.MalformedObjectNameException;
import javax.management.ObjectName;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;
import javax.naming.Context;
public class SetEnvironment {
protected static MBeanServerConnection connection;
private static JMXConnector connector;
private static final ObjectName service;
// Initializing the object name for DomainRuntimeServiceMBean
// so it can be used throughout the class.
static {
try {
service = new ObjectName( "com.bea:Name=DomainRuntimeService,Type=weblogic.management.mbeanservers.domainruntime.DomainRuntimeServiceMBean");
}catch (MalformedObjectNameException e) {
throw new AssertionError(e.getMessage());
}
}
/*
* Initialize connection to the Domain Runtime MBean Server
*/
public static void initConnection(String hostname, String portString,String username, String password) throws IOException, MalformedURLException {
String protocol = "t3";
Integer portInteger = Integer.valueOf(portString);
int port = portInteger.intValue();
String jndiroot = "/jndi/";
String mserver = "weblogic.management.mbeanservers.domainruntime";
JMXServiceURL serviceURL = new JMXServiceURL(protocol, hostname, port, jndiroot + mserver);
Hashtable hash = new Hashtable();
hash.put(Context.SECURITY_PRINCIPAL, username);
hash.put(Context.SECURITY_CREDENTIALS, password);
hash.put(JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,"weblogic.management.remote");
connector = JMXConnectorFactory.connect(serviceURL,hash);
connection = connector.getMBeanServerConnection();
}
/*
* This MBean is the root of the runtime MBean hierarchy, and
* each server in the domain hosts its own instance.
*/
public static ObjectName[] getServerRuntimes(String servername,String hostname, String portString,String username, String password) throws Exception{
ObjectName[] bj = (ObjectName[])connection.getAttribute(service,servername);
return obj;
}
}
第9题:
Identify three advantages of Active GridLink for RAC over multidata source.()
第10题:
Identify three components of the WebLogic JMS architecture.()