Explore topic-wise InterviewSolutions in .

WLS8 supports JMX but it uses weblogic IMPLEMENTATION of JMX server. It does not supports generalise sun javax API which can be used with any JVM. There are some PATCHES available which can be used with WLS8 which will enabled JMX BASED monitoring. Once JMX is enable there are many monitoring tools available in the MARKET. One can even GO for custom JMX utilities which can be used for server monitoring.

WLS8 supports JMX but it uses weblogic implementation of JMX server. It does not supports generalise sun javax API which can be used with any JVM. There are some patches available which can be used with WLS8 which will enabled JMX based monitoring. Once JMX is enable there are many monitoring tools available in the market. One can even go for custom JMX utilities which can be used for server monitoring.

FACTORY METHODS that will be used to create OBJECTS just LIKE in a static way.

Factory methods that will be used to create objects just like in a static way.

JMX is conceptually simple, yet BEARS the fruit of years of DOMAIN EXPERIENCE and research. In a nutshell, JMX defines a standard MEANS for APPLICATIONS to expose management functionality 

1. Instrumentation level 
2. Agent level 
3. Management level

JMX is conceptually simple, yet bears the fruit of years of domain experience and research. In a nutshell, JMX defines a standard means for applications to expose management functionality 

JMX is native to the JAVA programming language. As a result, it offers natural, efficient, and lightweight management extensions to Java-based FUNCTIONS. It consists of a set of specifications and development tools for managing Java environments and developing state-of-the-art management solutions for applications and SERVICES.

JMX is native to the Java programming language. As a result, it offers natural, efficient, and lightweight management extensions to Java-based functions. It consists of a set of specifications and development tools for managing Java environments and developing state-of-the-art management solutions for applications and services.

JMX is based on a 3-LEVEL architecture:

1. The Probe level contains the probes (called MBeans) instrumenting the resources. ALSO called the Instrumentation level.
2. The Agent level, or MBeanServer, is the core of JMX. It is an intermediary between the MBEAN and the applications.
3. The Remote Management level enables remote applications to access the MBeanServer through Connectors and Adaptors. A connector provides full remote access to the MBeanServer API using various communication frameworks (RMI, IIOP, JMS, WS), while an adaptor adapts the API to another protocol (SNMP) or to Web-based GUI (HTML/HTTP, WML/HTTP).

JMX is based on a 3-level architecture:

A managed bean - sometimes simply referred to as an MBEAN - is a type of JavaBean, CREATED with dependency injection. Managed Beans are particularly used in the Java MANAGEMENT Extensions technology. But, with the Java EE 6 specification provides for a more DETAILED meaning of a managed bean.

A managed bean - sometimes simply referred to as an MBean - is a type of JavaBean, created with dependency injection. Managed Beans are particularly used in the Java Management Extensions technology. But, with the Java EE 6 specification provides for a more detailed meaning of a managed bean.

Install Splunk 6 on your server which contains about 6 DIFFERENT JMX instances. you want to hook all of them up into our Splunk JMX PLUGIN.

It is as easy as EDITING the config.xml file and adding a NEW jmx server host? Currently this is:

<jmxserver host="[[system name]]" jvmDescription="common_raw" jmxport="53632"&GT;

Install Splunk 6 on your server which contains about 6 different JMX instances. you want to hook all of them up into our Splunk JMX plugin.

It is as easy as editing the config.xml file and adding a new jmx server host? Currently this is:

<jmxserver host="[[system name]]" jvmDescription="common_raw" jmxport="53632">

No JMX-related output in the logs. I can connect to the JVM with JCONSOLE using the supplied credentials, browse to the configured mbean, jackhammer the Refresh button and get new VALUES. Splunk, however, gets nothing, and leaves no indication as to why. Searching for "host=redacted" or "source='jmx://redacted'" yields nothing.

This is not a complicated setup, nor is it a complicated app. Single server test environment, just TRYING to get JMX data into Splunk directly instead of having to do some NASTY search-time field extraction after indexing data output from JMXTrans text files. It's currently running on JDK 1.7, I tried 1.6 for science to no AVAIL.

No JMX-related output in the logs. I can connect to the JVM with jconsole using the supplied credentials, browse to the configured mbean, jackhammer the Refresh button and get new values. Splunk, however, gets nothing, and leaves no indication as to why. Searching for "host=redacted" or "source='jmx://redacted'" yields nothing.

This is not a complicated setup, nor is it a complicated app. Single server test environment, just trying to get JMX data into Splunk directly instead of having to do some nasty search-time field extraction after indexing data output from JMXTrans text files. It's currently running on JDK 1.7, I tried 1.6 for science to no avail.

When Tomcat is running as a SERVICE on Windows, you do not NEED setenv.bat, you need to use tomcat8w.exe and GUI toll for ADDING OPTIONS.

When Tomcat is running as a service on Windows, you do not need setenv.bat, you need to use tomcat8w.exe and GUI toll for adding options.

Copy {WLHOME}/wlserver_**/server/lib/wlfullclient.jar file into {AGENT home}/opt/groovy-1.8.8/lib Then the Groovy script (that MIGRATED from my JMX Java APPLICATION) works.

Copy {WLHOME}/wlserver_**/server/lib/wlfullclient.jar file into {agent home}/opt/groovy-1.8.8/lib Then the Groovy script (that migrated from my JMX Java application) works.

Different collaborators for different environments can be injected - test, production, test-database, REAL database. This allows classes to be tested INDEPENDENT of its collaborators (MAKES it easy to pass in stub or MOCK objects).

Different collaborators for different environments can be injected - test, production, test-database, real database. This allows classes to be tested independent of its collaborators (makes it easy to pass in stub or mock objects).

There are NESTED ELEMENTS WITHIN each BEAN DEFINITION.

There are nested elements within each bean definition.

&LT;constructor-arg… and <property…

<constructor-arg… and <property…

Here are a few ADVANTAGES:

• Constructor
• MANDATORY
• MUTABLE
• Natural Java APPROACH.

Here are a few advantages:

It is created by SPRING AUTOMATICALLY, any SETTERS are called on the factory then its getObject() METHOD is called to allocate the actual bean.

It is created by Spring automatically, any setters are called on the factory then its getObject() method is called to allocate the actual bean.

5 scopes defined in Spring:

1. Singleton
2. Prototype
3. SESSION - only VALID in a WEB application context
4. REQUEST - ditto
5. Custom

5 scopes defined in Spring:

TWO examples:

1. NESTED or inner beans
2. CONFIGURATION beans

Two examples:

SCOPES the BEAN within the bean that USES it. One LESS bean id in the SET of bean names.

Scopes the bean within the bean that uses it. One less bean id in the set of bean names.

BEAN is not allocated until it is actually needed - dependency injected - or requested via getBean(). specify lazy="true" (FALSE by default). Only useful if bean GENUINELY may never be used in most runs of the APPLICATION.

Bean is not allocated until it is actually needed - dependency injected - or requested via getBean(). specify lazy="true" (false by default). Only useful if bean genuinely may never be used in most runs of the application.

A requirement that cuts ACROSS all the natural MODULES of your application.

Examples:

• Tracing, security, transactions, BUSINESS rules.
• Two problems with cross-cutting concerns.
• Code tangling - method doing too MANY unrelated tasks
• Code scattering - code duplication leading to maintenance headache

A requirement that cuts across all the natural modules of your application.

Examples:

Joint-point is an EXPRESSION that DEFINES ZERO or more join-points.

Joint-point is an expression that defines zero or more join-points.

The CODE that IMPLEMENTS the CROSS cutting-concern that will be INSERTED at each join-point.

The code that implements the cross cutting-concern that will be inserted at each join-point.

TYPES of ADVICE:

• Before
• AfterReturning
• AfterThrowing
• After
• AROUND

Types of advice:

A point cut EXPRESSION that has a name so it can be REUSED.

RESONS To use:

• Annotation: @POINTCUT applied to a DUMMY method - name of the dummy method is the name of the pointcut expression.
• XML aop:pointcut id=".." expression=".."

A point cut expression that has a name so it can be reused.

Resons To use:

Here are 5 steps:

1. Read BEAN file XML (or process annotations). Build internal "map" of beans and determine dependency tree.
2. Post process the definitions - e.g. resolve ${VARIABLES}
3. Allocate objects - dependency inject constructor args and invoke setter.
4. Perform any initialisation - 3 APPROACHS: @PostConstruct, init-method, InitializingBean
5. Bean post-processors - e.g. wrap with proxy, @Required

Here are 5 steps:

You have to EXPOSE the JMX port to the host and even used Sun specific options while RUNNING the Java process.

You are able to telnet to the host ip and the exposed JMX port, which tells that it is accessible. But I can't figure out a way to USE JConsole and CONNECT to the JMX service running in the container.

• Djava.rmi.server.hostname=$JMX_HOSTNAME
• Dcom.sun.management.jmxremote.port=$JMX_PORT
• Dcom.sun.management.jmxremote.rmi.port=$JMX_PORT

You have to expose the JMX port to the host and even used Sun specific options while running the Java process.

You are able to telnet to the host ip and the exposed JMX port, which tells that it is accessible. But I can't figure out a way to use JConsole and connect to the JMX service running in the container.

Here are a few advantages of Setter:

1. Natural for Java Beans
2. AVOIDS OVERLY long constructors
3. Can be INHERITED
4. Easier to UNDERSTAND in that properties have names
5. Constructor args don't have names

Here are a few advantages of Setter:

The APPLICATION JVM is CONFIGURED with the FOLLOWING OPTIONS:

• com.sun.management.jmxremote
• com.sun.management.jmxremote.port=1088
• com.sun.management.jmxremote.authenticate=false
• com.sun.management.jmxremote.ssl=false

The application JVM is configured with the following options: