How do I find it?

The annotations are explained below

Creating and populating a view

Adding metrics to a chart

After having created a new view and added a chart, you will need to add some metrics. Because there are so many to choose from, you first need to narrow down the ones you’re concerned about.

Modifying the chart

 Once you have some metrics added to the chart, and you’ve clicked the green play button so that metrics are captured, you might find that you actually don’t want a line chart at all! Perhaps your data is much more suited to a bar chart.

Adjusting the chart

Interpreting the data

Mike Crofton

<?xml version="1.0" encoding="UTF-8"?>  
<Configuration status="WARN">  
<Appenders>  
<Console name="Console" target="SYSTEM_OUT">  
<PatternLayout pattern="%d{HH:mm} [%t] %-5level %logger{36} - %msg%n"/>  
</Console>  
</Appenders>  
<Loggers>  
<Root level="trace">  
<AppenderRef ref="Console"/>  
</Root>  
</Loggers>  
</Configuration> 

 import org.apache.logging.log4j.*;  

 private static Logger logger = LogManager.getLogger(TestServlet.class.getName());

 protected void processRequest(HttpServletRequest request, HttpServletResponse response)  
       throws ServletException, IOException 
 {  
      response.setContentType("text/html;charset=UTF-8");  
      try (PrintWriter out = response.getWriter())   
      {  
           logger.trace("Tracing");  
           logger.debug("Debugging!");  
           logger.info("Info - something may be about to go wrong...");  
           logger.warn("Warning! Upcoming error!");  
           logger.error("Aaaaaaaahhhhhhhhhhhhhh!!!!!!!!!!!");  
      }  
 }

 [2014-07-29T10:58:10.511+0100] [glassfish 4.0] [INFO] [] [] [tid: _ThreadID=21 _ThreadName=Thread-3] [timeMillis: 1406627890511] [levelValue: 800] [[  
  10:58 [http-listener-1(4)] TRACE testing.TestServlet - Tracing]]  
 [2014-07-29T10:58:10.511+0100] [glassfish 4.0] [INFO] [] [] [tid: _ThreadID=21 _ThreadName=Thread-3] [timeMillis: 1406627890511] [levelValue: 800] [[  
  10:58 [http-listener-1(4)] DEBUG testing.TestServlet - Debugging!]]  
 [2014-07-29T10:58:10.511+0100] [glassfish 4.0] [INFO] [] [] [tid: _ThreadID=21 _ThreadName=Thread-3] [timeMillis: 1406627890511] [levelValue: 800] [[  
  10:58 [http-listener-1(4)] INFO testing.TestServlet - Info - something may be about to go wrong...]]  
 [2014-07-29T10:58:10.511+0100] [glassfish 4.0] [INFO] [] [] [tid: _ThreadID=21 _ThreadName=Thread-3] [timeMillis: 1406627890511] [levelValue: 800] [[  
  10:58 [http-listener-1(4)] WARN testing.TestServlet - Warning! Upcoming error!]]  
 [2014-07-29T10:58:10.511+0100] [glassfish 4.0] [INFO] [] [] [tid: _ThreadID=21 _ThreadName=Thread-3] [timeMillis: 1406627890511] [levelValue: 800] [[  
  10:58 [http-listener-1(4)] ERROR testing.TestServlet - Aaaaaaaahhhhhhhhhhhhhh!!!!!!!!!!!]]  

• logback-classic-1.2.2.jar
• logback-core-1.1.2.jar
• slf4j-api-1.7.7.jar
• jul-to-slf4j-1.7.7.jar

<configuration debug="true">  
<appender name="FILE" class="ch.qos.logback.core.FileAppender">  
<file>${com.sun.aas.instanceRoot}/logs/server.log</file>  
<append>true</append>  
<encoder>  
<Pattern>%d{HH:mm:ss} [%thread] %-5level %logger{52} - %msg%n</Pattern>  
</encoder>  
</appender>  
<root>  
<level value="TRACE"/>  
<appender-ref ref="FILE"/>  
</root>  
</configuration>   

• Change the handlers attribute to org.slf4j.bridge.SLF4JBridgeHandler
• This is to bridge any java.util.logging log statements to SLF4J
• Set com.sun.enterprise.server.logging.GFFileHandler.file to ${com.sun.aas.instanceRoot}/tmp/server.log
• This is to stop there being any file conflicts from both GlassFish and SLF4J trying to write to the same file (only a few lines of code will be logged here when GlassFish is started as it won't have loaded SLF4J yet).
• Add the following attributes:
• com.sun.enterprise.server.logging.GFFileHandler.formatter=com.sun.enterprise.server.logging.UniformLogFormatter
• com.sun.enterprise.server.logging.GFFileHandler.alarms=false

• -Djava.util.logging.config.file=${com.sun.aas.instanceRoot}/config/logging.properties
• -Dlogback.configurationFile=file:///${com.sun.aas.instanceRoot}/config/logback.xml

<configuration debug="true">  
<contextListener class="ch.qos.logback.classic.jul.LevelChangePropagator"/>
<appender name="FILE" class="ch.qos.logback.core.FileAppender">  

 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;

 private static Logger logger = LoggerFactory.getLogger(TestServlet.class.getName()); 

 protected void processRequest(HttpServletRequest request, HttpServletResponse response)  
       throws ServletException, IOException 
 {  
      response.setContentType("text/html;charset=UTF-8");  
      try (PrintWriter out = response.getWriter())   
      {  
           logger.trace("Tracing");  
           logger.debug("Debugging!");  
           logger.info("Info - something may be about to go wrong...");  
           logger.warn("Warning! Upcoming error!");  
           logger.error("Aaaaaaaahhhhhhhhhhhhhh!!!!!!!!!!!");  
      }  
 }

11:24 [http-listener-1(1)] DEBUG org.glassfish.grizzly.websockets.WebSocketFilter - handleRead websocket: null content-size=0 headers=
HttpRequestPacket (
   method=GET
   url=/LogbackTest/TestServlet
   query=testybutton=push+meh%21
   protocol=HTTP/1.1
   content-length=-1
   headers=[
      host=linux-njt2:8080
      user-agent=Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0
      accept=text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
      accept-language=en-gb,en;q=0.5
      accept-encoding=gzip, deflate
      referer=http://linux-njt2:8080/LogbackTest/
      connection=keep-alive]
)
11:24 [http-listener-1(1)] DEBUG org.glassfish.grizzly.filterchain.DefaultFilterChain - after execute filter. filter=org.glassfish.grizzly.extras.addons.WebSocketAddOnProvider$GlassfishWebSocketFilter@28d6271 context=FilterChainContext [connection=TCPNIOConnection{localSocketAddress={/127.0.0.1:8080}, peerSocketAddress={/127.0.0.1:43194}}, operation=READ, message=org.glassfish.grizzly.http.HttpContent@40e01f50, address=/127.0.0.1:43194] nextAction=org.glassfish.grizzly.filterchain.InvokeAction@4f86bdf5
11:24 [http-listener-1(1)] DEBUG org.glassfish.grizzly.filterchain.DefaultFilterChain - Execute filter. filter=org.glassfish.grizzly.http.server.HttpServerFilter@1039ea06 context=FilterChainContext [connection=TCPNIOConnection{localSocketAddress={/127.0.0.1:8080}, peerSocketAddress={/127.0.0.1:43194}}, operation=READ, message=org.glassfish.grizzly.http.HttpContent@40e01f50, address=/127.0.0.1:43194]
11:24 [http-listener-1(1)] TRACE testing.TestServlet - tracing
11:24 [http-listener-1(1)] DEBUG testing.TestServlet - Debugggggggggggggging!
11:24 [http-listener-1(1)] INFO  testing.TestServlet - infoooooooo
11:24 [http-listener-1(1)] WARN  testing.TestServlet - warnings!
11:24 [http-listener-1(1)] ERROR testing.TestServlet - aaaaaaaahhhhhhhhhhhhhh!!!!!!!!!!!
11:24 [http-listener-1(1)] TRACE org.glassfish.grizzly.ProcessorExecutor - executing connection (TCPNIOConnection{localSocketAddress={/127.0.0.1:8080}, peerSocketAddress={/127.0.0.1:43194}}). IOEvent=NONE processor=org.glassfish.grizzly.filterchain.DefaultFilterChain@73f5289 

• Admin console access – enable https access for admin console
• Domain Controller – Host controller communication – Communication between the main domain controller and all the other host controllers should be secured.
• Jboss CLI – enable ssl for the command line interface

1. Create the keystores (certificates for each of the servers)

• keytool -genkeypair -alias testServer.prd -keyalg RSA -keysize 2048 -validity 730 -keystore testServer.prd.jks

• keytool -certreq -alias testServer.prd -keystore testServer.prd.jks -file testServer.prd.csr

• keytool -import -trustcacerts -alias root -file rootCA.crt -keystore testServer.prd.jks

• Keytool -importcert -keystore testServer.prd.jks -trustcacerts -alias testServer.prd -file  testServer.prd.crt

1. Import the signed certificates of all the (slave) servers that the Domain Controller must trust onto the Domain Controllers Keystore

• keytool -importcert -keystore testServer.prd.jks  -trustcacerts -alias slaveServer.prd -file slaveServers.prd.crt
•  repeat step for all slave hosts.

•  keytool -importcert -keystore slaveServer.prd.jks  -trustcacerts -alias testServer.prd -file testServer.prd.crt
• repeat steps for all slave hosts

• The new BAM server runtime architecture
•  New developer features

• Ability to display business data in over 30 different business view types including treemap, bubble, scatter and geo-map (preview only) view types.
• Due to the underlying architectural changes noted above, the BAM server now supports active-active cluster mode.
• Finer grained security is enabled: Query, View and Dashboard and row level security
• There are numerous preassembled BPM process analytics dashboards which come out of the box when the BPM suite is deployed. Note you need to enable process metrics to be collected by modifying the mbean property DisableProcessMetrics to true in the Fusion middleware control console for the BAM server.

•  BPM Development Installer
• JDeveloper Debugger Utilities
•  Detailed Diagnostics Tools for BAM

<?xml version="1.0" encoding="UTF-8"?>  
<Configuration status="WARN">  
<Appenders>  
<Console name="Console" target="SYSTEM_OUT">  
<PatternLayout pattern="%d{HH:mm} [%t] %-5level %logger{36} - %msg%n"/>  
</Console>  
</Appenders>  
<Loggers>  
<Root level="trace">  
<AppenderRef ref="Console"/>  
</Root>  
</Loggers>  
</Configuration> 

 ./startWebLogic -Dlog4j.configurationFile=log4j2.xml

•  Import the two Log4j JARS, log4j-api-2.0.jar and log4j-core-2.0.jar, into the project, and import the package into the servlet:

 import org.apache.logging.log4j.*; 

•  Declare and initialise a logger:

private static Logger logger = LogManager.getLogger(TestServlet.class.getName());

• And alter the processRequest method to look like this:

 protected void processRequest(HttpServletRequest request, HttpServletResponse response)  
       throws ServletException, IOException 
 {  
      response.setContentType("text/html;charset=UTF-8");  
      try (PrintWriter out = response.getWriter())   
      {  
           logger.trace("Tracing a possible error");  
           logger.debug("Debugging a possible error");  
           logger.info("Gathering info on the possible error");  
           logger.warn("Warning you about the possible error");  
           logger.error("The error is indeed an error");  
      }  
 }

<html>
<head>
<title>Testing</title>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<form name="testForm" action="TestServlet">
<input type="submit" value="push me!" name="testybutton" />
</form>
</body>
</html>

• Download SLF4J and Logback, and import the following three JARs into the project:
• slf4j-api
• logback-core
• logback-classic
• Import the following two packages into the servlet

 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;

•  And alter the logger initialisation to this:

private static Logger logger = LoggerFactory.getLogger(TestServlet.class.getName()); 

<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app
    xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd
    http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.4/weblogic-web-app.xsd">

<wls:container-descriptor>
<wls:prefer-web-inf-classes>true</wls:prefer-web-inf-classes>
</wls:container-descriptor>
</wls:weblogic-web-app>

<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm} [%thread] %-5level %logger{36} - %msg%n</pattern>
</encoder>
</appender>
<root level="TRACE">
<appender-ref ref="STDOUT"/>
</root>
</configuration>

 ./startWebLogic -Dlogback.configurationFile=logback.xml 

Source: https://www.jboss.org/dms/wildfly_splash/splash_wildflylogo_small.png

• Create a Server in NetBeans that maps to your WildFly installation (you'll need the WildFly plugin: tools, plugins, Available Plugins, WildFly Application Server)
• Create a Java Web application
• Create a Servlet in this project.
• Download Log4j and add the following two JARs into the project:
• log4j-api-2.0.2.jar
• log4j-core-2.0.2.jar
•  Add the following import statement into your servlet:

 import org.apache.logging.log4j.*; 

•  Declare and initialise the logger:

 private static Logger logger = LogManager.getLogger(TestServlet.class.getName());

•  Edit the processRequest method to this:

 protected void processRequest(HttpServletRequest request, HttpServletResponse response)  
       throws ServletException, IOException 
 {  
      response.setContentType("text/html;charset=UTF-8");  
      try (PrintWriter out = response.getWriter())   
      {  
            logger.trace("Tracing!");  
            logger.debug("Debugging!");  
            logger.info("Information!");  
            logger.warn("Warnings!");  
            logger.error("Oh noes!");  
      }  
 }

<html>
<head>
<title>Testing</title>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<form name="testForm" action="TestServlet">
<input type="submit" value="push me!" name="testybutton" />
</form>
</body>
</html>

• In the WEB-INF folder of your NetBeans project, create a folder called classes
• Create an xml file in here named log4j2.xml, and populate it with this: 

<?xml version="1.0" encoding="UTF-8"?>  
<Configuration status="WARN">  
<Appenders>  
<File name="FileLogger" fileName="/home/andrew/wildfly.log">  
<PatternLayout pattern="%d{HH:mm} [%t] %-5level %logger{36} - %msg%n"/>  
</Console>  
</Appenders>  
<Loggers>  
<Root level="trace">  
<AppenderRef ref="FileLogger"/>  
</Root>  
</Loggers>  
</Configuration> 

• Download SLF4J and Logback, and add the following JARs to your web application:
• slf4j-api
• logback-core
• logback-classic
•  Remove the Log4j package and instead import:

 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;

•  Alter the logger initialisation to:

 private static Logger logger = LoggerFactory.getLogger(TestServlet.class.getName());

<configuration>  
<appender name="FILE" class="ch.qos.logback.core.FileAppender">  
<file>/home/andrew/wildfly.log</file>  
<append>true</append>  
<encoder>  
<Pattern>%d{HH:mm} [%thread] %-5level %logger{52} - %msg%n</Pattern>  
</encoder>  
</appender>  
<root>  
<level value="TRACE"/>  
<appender-ref ref="FILE"/>  
</root>  
</configuration> 

 jboss-cli.sh -c controller=$ip:$port --gui

What is RBAC?

Did you get the outcome you were looking for?

• Setup RHQ on amazon ec2 instances
• Setup Weblogic on amazon ec2 instances
• Got RHQ monitoring the Weblogic with the default JMX plugin
• Tried adding some custom plugins – faced a few issues with this. Needs further investigation.
• Looked at the possibility of writing our own java plugin.

What do you think the benefit of C2B2 tech days are?

Featured News

GlassFish is here to stay. We heard it from the Oracle - read more
JavaOne Keynotes Available for Streaming - read more  

  JAVAONE 2014

JavaOne Keynotes Available for Streaming - see more at Java.net 

Final Keynotes Reflect Back, Move Forward - read more on the Oracle blog 

Oracle Shares Key Updates on Java Platform, Enterprise Edition, Introduces GlassFish Server Open Source Edition 4.1 at JavaOne 2014 - read more on MarketWatch 

JavaOne 2014 in Depth - read the article by Peter Pilgrim 

JavaOne 2014 Observations by Proxy - read more by Dustin Marx

The highlights of Java EE 8 - read more on the ServerSide 

Life around the Java Hub - read more on the Oracle Blog

User Group Sunday Kicks Things Off - read more on the Oracle Blog 

 JAVA EE / OPEN SOURCE

GlassFish

GlassFish Server Open Source Edition 4.1 Released! – find out more 

GlassFish is here to stay. We heard it from the Oracle. – read more by Steve Millidge

Alternative Logging Frameworks for Application Servers: GlassFish - read more on the C2B2 Blog 

London GUG event: Testing Java EE Applications Using Arquillian & GlassFish by Reza Rahman – find out more and register 

Payara - The New Fish on the Block, 24/7 GlassFish support - find out more 

Other

2014 Duke's Choice Award Winners – read more on the Oracle Blog 

Java Magazine – read the latest issue here 

Apache Tomcat 7.0.56 has arrived - read more on Jaxenter 

5 JAX London sessions every developer should see - read more on Jaxenter 

Jsr107 come, code, cache, compute! -  see Steve Millidge’s JavaOne slides here ; see the code on GitHub 

Java EE 8 will not include Configuration JSR for Java EE applications – find out more here 

Apache Tomcat 8: What It Is, What You Need To Know - read more on the Pivotal Blog 

Apache Warns of Tomcat Remote Code Execution Vulnerability – read more on the Threat Post 

Devoxx 2014 Schedule is now available to view – find out more

Reducing the frequency of GC pauses - seemingly an easy task? – read more on The Server Side 

How to Get the Most Out of a Tech Conference - read more on the Oracle Blog 

TomEE Security Episode 1: Apache Tomcat and Apache TomEE Security Under the Covers –read more on the Tomitribe Blog 

ORACLE

JBOSS & RED HAT

Red Hat Launches Red Hat Cloud for Government to Help Agencies Build Strategies to Address Cloud Challenges - read more on the Business Wire 

  DATA GRIDS

Hazelcast raises $11 million in funds for further NoSQL expansion - read more on Jaxenter.com  

Beginner’s Guide To Hazelcast Part 1- read the article by Daryl Mathison 

JSR-000107 JCACHE - Java Temporary Caching API Compatible Implementations – find out more on the JCP website 

Running Tabular Reports with Coherence 12.1.3 Reporter - read more on the Oracle blog 

In-Memory Data Grids: Why market needs them? - listen to the podcast with VPs here 

New eBook: In-Memory Data Grids for Dummies – find out more on the Oracle Blog 

 ./asadmin start-domain --debug true

 ./asadmin start-domain -d

 ./asadmin start-domain  

 ./asadmin start-domain myDomain  

 ./asadmin stop-domain  

 ./asadmin stop-domain domain1

 ./asadmin stop-domain --kill true domain1

 ./asadmin start-instance instance1

 ./asadmin start-local-instance instance2  

• The none parameter means that the instance will not synchronise itself with the DAS, so will not reflect any changes made to it since it was last synchronised. This can be useful if you know that there have been no changes made, and want the instance to start as quickly as possible.
• The normal has the instance synchronise with any changes since it was last synchronised (which is typically the last time it was online). If you do not specify the --sync option, this will be the option that the start-instance or start-local-instance command will default to. As the help of the command states, this parameter causes the instance to synchronise the config directory, and the changed subdirectories in the applications and docroot directories. An exception to the synchronisation of the subdirectories exists however: only the subdirectories that have had a change at their top level will be synchronised; if a change is made lower down the file system hierarchy, but not at the top level, then the changes will not be synchronised.
• The final option, full, is not subject to this caveat. This synchronisation parameter will synchronise all files, even if they have not been changed. This is the most thorough way of ensuring that an instance is correctly synchronised, but comes with its own downsides: it is slower than the normal and none options, and requires the DAS to be running; the start instance command will fail, and the instance will not be able to start till it contacts the DAS again.

 ./asadmin start-local-instance --sync full --verbose true --debug true instance1  

./asadmin stop-instance instance1 

./asadmin stop-local-instance instance2 

./asadmin start-cluster cluster1

./asadmin stop-cluster cluster1

./asadmin create-domain 

• adminport - This option will specify with port will be used for administration (defaults to 4848).
• instanceport - This option specifies which port will be used for the web application context roots (defaults to 8080).
• portbase - This option is used to determine port assignments, and cannot be used with the adminport,instanceport, or domainproperties options. The value specified for this option will be a base value, upon which the other required ports (e.g. the administration port) are calculated by a port specific offset. So if the port base was specified as 500, the administration port would be 548 (500 + the administration port offset of 48). Each of the port offsets can be seen under the create-domain help.
• template - Useful if you already have a domain template that you wish to copy from machine to machine, this option allows you to specify a template that the domain will be created to match.
• usemasterpassword - For added security, you can protect the GlassFish keystore with a password. If not specified, then the password changeit is used; this default is fairly well known, so it is advised that you change it (get it?) when securing GlassFish.
• domainproperties - This option allows you to specify each port that will be used individually, rather than by relying on portbase. It is worth noting however that the adminport and instanceport options will override the admin and instance port specified by this command. The full list of ports that can be set are available in the command's help, though I'll list a few here: domain.adminPort, domain.instancePort, http.ssl.port, java.debugger.port. When specifying multiple values, you separate them with a colon e.g. domain.adminPort=3456:domain.instanceport=4567

./asadmin create-node-config --nodehost localhost --installdir /home/andrew/glassfish --nodedir /home/andrew/nodes configNode

• force - This will force the creation of the node in the DAS configuration, even if the parameters passed in for the creation of the node fail validation. This can be useful if you know the target node will not be able to be validated against, such as if the target node host is not currently available. This option is also available to the create-node-dcom command.
• sshport - If you are using a a non-defualt SSH port (22), then use this option to specify what port is being used instead.
• sshuser - This specifies the user to use when connecting to the host through SSH, which by default is the user that is running the DAS.

•  windowsuser - This sets which Windows user to use to connect through DCOM. If not set, this defaults to the user running the DAS process.
• windowsdomain - This specifies the domain that the Windows user will be found under. This defaults to the host that the subcommand is run under.
•  install - This option specifies whether or not GlassFish will be installed on the node host specified. This option is also available to the create-node-ssh command.

./asadmin create-cluster cluster1

./asadmin create-cluster --systemproperties ASADMIN_LISTENER_PORT=666:JAVA_DEBUGGER_PORT=777 cluster1

./asadmin create-instance instance1

./asadmin create-local-instance instance2 

./asadmin create-instance --config instance-config-1 instance3

./asadmin create-instance --cluster cluster12 instance4 

./asadmin create-instance --node node1

./asadmin change-admin-password

./asadmin change-master-password

./asadmin --user admin change-admin-password

./asadmin deploy $path_to_war

./asadmin deploy --target cluster1 testyWar

./asadmin deploy --target instance1 testyWar 

• Navigate to the Protocols menu, which can be found under Network Config.
• For each of the listeners listed, click on the listener's name:
• Check if the Security box is ticked; you will not be able to disable SSL3 via the Admin console unless Security is already enabled.
• Assuming the Security box is checked, Navigate to the SSL tab, and uncheck the SSL3 box.
• Click on the Save button, and move on to the next listener.

• Navigate to your IIOP Listeners, which can be found under ORB.
• For each of your listeners, click on the name of the listener, then:
• Check if the Security box is ticked; you will not be able to disable SSL3 via the Admin console unless Security is already enabled.
• Assuming the Security box is checked, Navigate to the SSL tab, and uncheck the SSL3 box.
• Click on the Save button, and move on to the next listener.
• Restart your domain.

<protocol name="http-listener-2" security-enabled="true">  
<http max-connections="250" default-virtual-server="server">  
<file-cache></file-cache>  
</http>  
<ssl classname="com.sun.enterprise.security.ssl.GlassfishSSLImpl" cert-nickname="s1as"></ssl>  
</protocol> 

<protocol name="http-listener-2" security-enabled="true">  
<http max-connections="250" default-virtual-server="server">  
<file-cache></file-cache>  
</http>  
<ssl ssl3-enabled=false classname="com.sun.enterprise.security.ssl.GlassfishSSLImpl" cert-nickname="s1as"></ssl>  
</protocol> 

<iiop-listener address="0.0.0.0" port="3820" id="SSL" security-enabled="true">
<ssl classname="com.sun.enterprise.security.ssl.GlassfishSSLImpl" cert-nickname="s1as"></ssl>
</iiop-listener>
<iiop-listener address="0.0.0.0" port="3920" id="SSL_MUTUALAUTH" security-enabled="true">
<ssl classname="com.sun.enterprise.security.ssl.GlassfishSSLImpl" cert-nickname="s1as" client-auth-enabled="true"></ssl>
</iiop-listener>

<iiop-listener address="0.0.0.0" port="3820" id="SSL" security-enabled="true">
<ssl ssl3-enabled="false" classname="com.sun.enterprise.security.ssl.GlassfishSSLImpl" cert-nickname="s1as"></ssl>
</iiop-listener>
<iiop-listener address="0.0.0.0" port="3920" id="SSL_MUTUALAUTH" security-enabled="true">
<ssl ssl3-enabled="false" classname="com.sun.enterprise.security.ssl.GlassfishSSLImpl" cert-nickname="s1as" client-auth-enabled="true"></ssl>
</iiop-listener>

 ./asadmin set server.network-config.protocols.protocol.http-listener-2.ssl.ssl3-enabled=false

 ./asadmin set server.network-config.protocols.protocol.sec-admin-listener.ssl.ssl3-enabled=false

 ./asadmin set server.iiop-service.iiop-listener.SSL.ssl.ssl3-enabled=false

 ./asadmin set server.iiop-service.iiop-listener.SSL_MUTUALAUTH.ssl.ssl3-enabled=false

 openssl s_client -connect localhost:4848 -ssl3

 CONNECTED(00000003)                                                                                            
 139973006218896:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:598:                                                                                                                                                  
 ---                                                                                                                                                                                                                                               
 no peer certificate available                                                                                                                                                                                                                     
 ---                                                                                                                                                                                                                                               
 No client certificate CA names sent                                                                                                                                                                                                               
 ---                                                                                                                                                                                                                                               
 SSL handshake has read 0 bytes and written 0 bytes

'Through the JMX Window' - Hands-on-Lab by Matt Brasier

Through the JMX Window from C2B2 Consulting

 

• Part 1 – GlassFish
• Part 2 – WebLogic
• Part 3 – WildFly

Log4j2

• Create a Server in NetBeans that maps to your Tomcat installation. 
• Create a Java web application.
• Create a Servlet in this new project.
• Import the Log4j2 JARs to the project:
• Right click on the project, and select properties
• Go to the Librariespage
• Select Add JAR/Folder, and import the following two files:
• log4j-api-2.1.jar
• log4j-core-2.1.jar
• Click OK
• Import the log4j package into your servlet by adding this code snippet below:

 import org.apache.logging.log4j.*;  

• Declare and initialise a logger:

 private static Logger logger = LogManager.getLogger(TestServlet.class.getName());  

• Add some logger messages at each log level to the processRequest method, so that they get executed when the Servlet is called:

 protected void processRequest(HttpServletRequest request, HttpServletResponse response)
         throws ServletException, IOException 
 {
     response.setContentType("text/html;charset=UTF-8");
     try (PrintWriter out = response.getWriter()) 
     {           
         logger.trace("Tracing!");  
         logger.debug("Debugging!");  
         logger.info("Information!");  
         logger.warn("Warnings!");  
         logger.error("Oh noes!"); 
     }
 }  

<html>
<head>
<title>Testing</title>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<form name="testForm" action="TestServlet">
<input type="submit" value="push me!" name="testybutton" />
</form>
</body>
</html>

• Expand the Web Pages folder of your test application in the project navigator pane.
• Right click on the WEB-INF folder, and create a new folder inside it called classes.
• Right click on this new classes folder, expand the Newmenu, and select XMLDocument.
• Call it log4j2, and just create it as a well-formed document.
• Fill it out as follows (replacing the fileName value with your own file path and file name):

<?xml version="1.0" encoding="UTF-8"?>  
<Configuration status="WARN">  
<Appenders>  
<File name="FileLogger" fileName="/home/andrew/tomcat.log">  
<PatternLayout pattern="%d{HH:mm} [%t] %-5level %logger{36} - %msg%n"/>  
</File> 
<Console name="ConsoleLogger" target="SYSTEM_OUT"> 
<PatternLayout pattern="%d{HH:mm:ss} [%t] %-5level %logger{36} - %msg%n"/>
</Console>
</Appenders>  
<Loggers>  
<Root level="trace">  
<AppenderRef ref="FileLogger"/>
<AppenderRef ref="ConsoleLogger"/>  
</Root>  
</Loggers>  
</Configuration>  

Testing

• Clean and build the project, this will add the two JARs needed by the logger (log4j-api-2.1.jarand log4j-core-2.1.jar) to $project_install_location/build/web/WEB-INF/libdirectory, so that Tomcat can use them.
• Right click on the project, and deploy it to Tomcat.
• Click on the play button, and your browser should load with the application.
• Click the button, and then check in your log file and in the catalina.out log file (this can be found in $tomcat_install_location/logs), you should see your logger messages.

Logback

• Create a Server in NetBeans that maps to your Tomcat installation.
• Create a Java Web application.
• Create a Servlet in this new project.
• Import the Logback and SLF4J JARs into the project:
• Right click on the project, and select properties
• Go to the Librariespage
• Select Add JAR/Folder, and import the following files:
• slf4j-api-1.7.7.jar
• logback-classic-1.1.2.jar
• logback-core-1.1.2
• Click OK
• Import the following SLF4J packages into your servlet:

 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;

• Declare and initialise a logger:

 private static Logger logger = LoggerFactory.getLogger(TestServlet.class.getName());

• Log some messages at various levels in the processRequest method, such that they get triggered when the Servlet is called:

 protected void processRequest(HttpServletRequest request, HttpServletResponse response)
      throws ServletException, IOException 
 {
    response.setContentType("text/html;charset=UTF-8");
    try (PrintWriter out = response.getWriter()) 
    {
       logger.trace("Tracing!");  
       logger.debug("Debugging!");  
       logger.info("Information!");  
       logger.warn("Warnings!");  
       logger.error("Oh dears!");
    }
 }

<html>
<head>
<title>Testing</title>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<form name="testForm" action="TestServlet">
<input type="submit" value="push me!" name="testybutton" />
</form>
</body>
</html>

• Expand the Web Pages folder of your test application in the project navigator pane.
• Right click on the WEB-INF folder, and create a new folder inside it called classes.
• Right click on this new folder, expand the New menu, and select XMLDocument.
• Call it logback, and create it as a well-formed document; we don’t need any schema or DTD constraints for this.
• Populate it with this (replacing /home/andrew/tomcat.log with your own file path and file name):

<?xml version="1.0" encoding="UTF-8"?>  
<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH} [%thread] %-5level %logger{36} - %msg%n</pattern>
</encoder>
</appender>

<appender name="FILE" class="ch.qos.logback.core.FileAppender">
<file>/home/andrew/tomcat.log</file>
<append>true</append>
<encoder>
<pattern>%d{HH:mm} [%thread] %-5level %logger{52} - %msg%n</pattern>
</encoder>
</appender>

<root level="TRACE">
<appender-ref ref="STDOUT"/>
<appender-ref ref="FILE"/>
</root>
</configuration>

Testing

• Clean and build the project, this will add the JARs needed by the logger (logback-classic-1.1.2.jar, logback-core-1.1.2.jar, and slf4j-api-1.7.7.jar) to the $project_install_location/build/web/WEB-INF/libdirectory, so that they deploy to Tomcat with the application.
• Right click on the project, and deploy it to Tomcat.
• Click on the play button, and your browser should load with the application.
• Click the button, and then check in the log file you specified in the Logback configuration, and in the catalina.out log file (this can be found in $tomcat_install_location/logs), you should see your logger messages.

Final Thoughts

Brief

• Architecture set up
• WildFly clustering configuration on EC2
• WebSocket application on WildFly
• Storing and ensuring high availability of data using Infinispan
• Apache load balancer configuration

Introduction

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

<subsystemxmlns="urn:jboss:domain:jgroups:2.0"default-stack="tcp">
<stackname="udp">
<transporttype="UDP"socket-binding="jgroups-udp"/>
<protocoltype="PING"/>
<protocoltype="MERGE3"/>
<protocoltype="FD_SOCK"socket-binding="jgroups-udp-fd"/>
<protocoltype="FD_ALL"/>
<protocoltype="VERIFY_SUSPECT"/>
<protocoltype="pbcast.NAKACK2"/>
<protocoltype="UNICAST3"/>
<protocoltype="pbcast.STABLE"/>
<protocoltype="pbcast.GMS"/>
<protocoltype="UFC"/>
<protocoltype="MFC"/>
<protocoltype="FRAG2"/>
<protocoltype="RSVP"/>
</stack>
<stackname="tcp">
<transporttype="TCP"socket-binding="jgroups-tcp"/>
<protocoltype="TCPPING">
<propertyname="initial_hosts">$YOUR_FIRST_IP_ADDRESS[7600],$YOUR_SECOND_IP_ADDRESS[7600]</property>
<propertyname="port_range">0</property>
<propertyname="timeout">3000</property>
<propertyname="num_initial_members">2</property>
</protocol>
<protocoltype="MERGE2"/>
<protocoltype="FD_SOCK"socket-binding="jgroups-tcp-fd"/>
<protocoltype="FD"/>
<protocoltype="VERIFY_SUSPECT"/>
<protocoltype="pbcast.NAKACK2"/>
<protocoltype="UNICAST3"/>
<protocoltype="pbcast.STABLE"/>
<protocoltype="pbcast.GMS"/>
<protocoltype="MFC"/>
<protocoltype="FRAG2"/>
<protocoltype="RSVP"/>
</stack>
</subsystem>

<!-- Input form -->
<form>
<fieldset>
<label>Store:</label>
<inputid="putKey"type="text">
<inputid="putValue"type="text">
<inputtype="submit"id="store"value="StoreMe">
</fieldset>
</form>

<h4>Result from the submit operation:</h4>
<spanid="result"></span>


<br/>
<br/>
<!-- Get form -->
<form>
<fieldset>
<label>Get:</label>
<inputid="getKey"type="text">
<inputtype="submit"id="getValue"value="GetMe">
</fieldset>
</form>

<h4>Result from the get operation:</h4>
<spanid="getResult"></span>

<script>
var port = "";
var storerUrl = 'ws://' + window.location.host + port + window.location
        .pathname + 'store';
var ws = new WebSocket(storerUrl);

var getterUrl = 'ws://' + window.location.host + port + window
        .location.pathname + 'getter'
var wsGet = new WebSocket(getterUrl);

        ws.onconnect = function(e) {
          console.log("Connected up!");
        };

        ws.onerror = function(e) {
          console.log("Error somewhere: " + e);
        };

        ws.onclose = function(e) {
          console.log("Host has closed the connection");
          console.log(e);
        };

        ws.onmessage = function(e) {
document.getElementById("result").innerHTML = e.data;
        };

        wsGet.onconnect = function(e) {
            console.log("Connected up!");
        };

        wsGet.onerror = function(e) {
          console.log("Error somewhere: " + e);
        };

        wsGet.onclose = function(e) {
          console.log("Host has closed the connection");
          console.log(e);
        };

        wsGet.onmessage = function(e) {
          console.log("Received message from WebSocket backend");
document.getElementById("getResult").innerHTML = e.data;
        };



document.getElementById("store").onclick = function(event){
          event.preventDefault();
var key = document.getElementById("putKey").value;
var value = document.getElementById("putValue").value;
var objToSend = '{"key": ' + key + ', "value": ' + value + '}';
          ws.send(objToSend);
        };

document.getElementById("getValue").onclick = function(event) {
            event.preventDefault();
var key = document.getElementById("getKey").value;
var objToGet = '{"key": ' + key + '}';
            wsGet.send(objToGet);
        };

</script>

@ServerEndpoint("/store")
publicclassStorer {

privatestatic Logger storerLogger = Logger.getLogger(Storer.class.getName());

/**
    * Method that will store some basic data using the application platform's
    * clustered caching mechanism.
    *
    * @param data - The information, as a JSON from the js/html front-end.
    * @param client - the client session
    */
@OnMessage
publicvoidstore(String data, Session client) {
      String returnText = null;

// Let's get the Json object first.
      JsonParserFactory factory = JsonParserFactory.getInstance();
      JSONParser parser = factory.newJsonParser();
      Map jsonMap = parser.parseJson(data);

if (jsonMap.containsKey("key") && jsonMap.containsKey("value")) {
// Store the data in the cache now that we have validated it.
         String key = (String) jsonMap.get("key");
         String value = (String) jsonMap.get("value");
// TODO: Not actually storing anything yet!

// Creating some string returns to go back to the front-end along
// with some logging statements.
         StringBuilder sb = new StringBuilder();
         sb.append("Well done. We now have your data!");
         storerLogger.info("Going to store key " + key + " and value " +
               value + ".");
         sb.append(" Key: ").append(key).append(" Value: ").append(value)
               .append(". ");
         sb.append(" Stored at date: ").append(buildDate()).append(".");


         returnText = sb.toString();
      } else {
// Failed the validation check. So we are now going to log some
// information to the server and return some information to the
// front-end as well.

         storerLogger.info("Seems to be a problem with the input. Cannot find" +
" the appropriate \'key\' and \'value\' string keys.");
         returnText = "Problem with the input that you sent in. Are they just" +
" the default values?";
      }

// Send to client.
      client.getAsyncRemote().sendText(returnText);
   }

private String buildDate() {
returnnewSimpleDateFormat("HH:mm dd/MM/yy").format(Calendar
            .getInstance().getTime());
   }

}

@ServerEndpoint("/getter")
publicclassGetter {

static Logger getterLogger = Logger.getLogger(Getter.class.getName());

/**
    * Method that will attempt to get a value for a given key.
    *
    * @param data - A String that is the key
    * @param client - the client session
    */
@OnMessage
publicvoidgetValue(String data, Session client) {
      getterLogger.info("Getting key: " + data);

      String returnText = "{No value found for key " + data + "}.";
try {
         returnText = getValueFromCache(data);
      } catch (Exception e) {
         returnText = e.getMessage();
         getterLogger.log(Level.WARNING, e.getMessage());
         e.printStackTrace();
      }

      client.getAsyncRemote().sendText(returnText);
   }