Best way to call javascript in ahref tag is to add href=” ” and onlick=”jsFunction(); return false;”

the false returning ensures the link in href is not evaluated. No need to add label called javascript: to the jsFunction call since that is verbose and not used internally in our function either.

Here are some points from Evan’s talk on Domain Design from the site: DDD

• Creative collaboration of domain experts and software experts
• Exploration and experimentation
• Emerging model shaping a ubiquitous language
• Explicit context boundaries
• Focus relentlessly on the core domain

So basically DDD defines the “values” that should dictate the software design.

A domain model is not a particular diagram; it is the idea that the diagram is intended to convey. It is not just the knowledge in a domain expert’s head; it is a rigorously organized and selective abstraction of that knowledge. A diagram can represent and communicate a model, as can carefully written code, as can an English sentence.

Smart, experienced people become incompetent through loss of hands-on practice.

- Eric Evans (Domain Driven Design)

Amazing. Was completely blow away with this quote today which confirmed my understanding of  the role of an architect and its significance. Go ahead , read this article now

Introduction to PGT:
Proxy authentication. It’s designed specifically for applications authenticating on behalf users. In such scenario your Web application would receive a Proxy Granting Ticket (PGT) when validating its Service Ticket and use that PGT to request Proxy Tickets to present to the Web Services. Your XFire Web Services would then validate those Procy Tickets directly with CAS. This should eliminate the need to pass username/password more than once, which is why you are implementing SSO.

ModelMBean can be created by using any simple POJO.

ModelMBeanInfo = Interface, MBeanInfo     = Class

I was wondering – why does the MBeanInfo class not implement the ModelMBeanInfo interface?. MBeanInfo class does implement some methods defined in ModelMBeanInfo interface but not all the methods – like getDescriptors etc is not implemented, and in addition to that there are other methods like fastGetAttributes.

Java resources wishing to be manageable instantiate the ModelMBean using the MBeanServer’s createMBean method. The resource then sets the ModelMBeanInfo and Descriptors for the ModelMBean instance

A Java object cannot be registered in the MBeanServer unless it is a JMX compliant MBean. By instantiating a ModelMBean, resources are guaranteed that the MBean is valid. MBeanException and RuntimeOperationsException must be thrown on every public method. This allows for wrapping exceptions from distributed communications (RMI, EJB, etc.)

The contents of the MBeanInfo for a Dynamic MBean are determined by its getMBeanInfo() method. This includes Open MBeans and Model MBeans, which are kinds of Dynamic MBeans.

We need the following class instances

<div>ModelMBeanOperationInfo[] ops;
ModelMBeanAttributeInfo[] atts ;
ModelMBeanConstructorInfo[] cons;
ModelMBeanNotificationInfo[] notifs;

  return new ModelMBeanInfoSupport( "javax.management.modelmbean.ModelMBeanInfo", "description", atts, cons, ops, notifs, desc );
  ObjectName mName = new ObjectName("JMXBookAgent:name=Modeled");
  client.createMBean( "javax.management.modelmbean.RequiredModelMBean", mName );
 

String[] sig = { "java.lang.Object", "java.lang.String" };
Object[] params = { obj, "ObjectReference" };
client.invoke( mName, "setManagedResource", params, sig );

  //Step 1: Create your object
			DBModel mypojo = new DBModel();

			//Step 2: Expose it through ModelMBeanInfo
		    ModelMBeanInfoBuilder builder = new ModelMBeanInfoBuilder();
		    //Descriptor attDesc = builder.buildAttributeDescriptor( "MyAttribute", null, "always", "10", null, "getMyAttribute", null, "10" );
		    Descriptor attDesc = builder.buildAttributeDescriptor( "MaxConn","Max Connection","never","0","0","getTotalConn",null,"-1");
		    builder.addModelMBeanAttribute( "MaxConn", "java.lang.Integer", true, false, false, "Get the max connection", attDesc );
Descriptor opGetDesc = builder.buildOperationDescriptor( "getTotalConn", null, "getter", null, null, "mypackage.jmx.DBModel", "10" );
		    builder.addModelMBeanMethod( "getTotalConn", null, null, null, "", "java.lang.String" , MBeanOperationInfo.INFO, opGetDesc );
		    Descriptor mbeanDesc = builder.buildMBeanDescriptor( "DB", "SampleDBModel", "never", "-1", null ,null, null, null );
		    ModelMBeanInfo myinfo = builder.buildModelMBeanInfo( mbeanDesc );

		    //Step 3: Register it
		    ObjectName oname = new ObjectName(dbDomainName);
		    MBeanServer mbs;
		    List mbsArl = MBeanServerFactory.findMBeanServer(null);
			if(mbsArl.size() > 0)
			{
				mbs = (MBeanServer)mbsArl.get(0);
				System.out.println("Got existing mbean server . . . .");
			}
			else
				mbs = ManagementFactory.getPlatformMBeanServer();

                     /mbs.createMBean("javax.management.modelmbean.RequiredModelMBean", oname);
		     RequiredModelMBean modelmbean =	new RequiredModelMBean( myinfo );
		    // Associate it with the resource (a TestBean instance)
		    modelmbean.setManagedResource(  mypojo, "objectReference");
		    //modelmbean.setModelMBeanInfo(myinfo);

         	    mbs.registerMBean(modelmbean, oname);
                            /* The below code does not work ! - so have commented it */
                              mbs.createMBean("javax.management.modelmbean.RequiredModelMBean", oname);
				//Step 4: Call the setters for our POJO and INFO objects.

				//Set our POJO
			    String[] sig = { "java.lang.Object", "java.lang.String" };
			    Object[] params = { mypojo, "ObjectReference" };
			    mbs.invoke( oname, "setManagedResource", params, sig );

				//Set our INFO
			    sig = new String[ 1 ];
			    sig[ 0 ] = "javax.management.modelmbean.ModelMBeanInfo" ;
			    params = new Object[ 1 ];
			    params[ 0 ] = myinfo;
			    mbs.invoke( oname, "setModelMBeanInfo", params, sig ); */

PersistPeriod: Specifies the number of seconds that the OnTimer or NoMoreOftenThan persistence policies use. If you do not specify this attribute in the MBeanType or

MBeanAttribute elements, the assumed value is 0.If PersistPolicy is set to OnTimer, then the attribute is persisted when the number of seconds expires. If PersistPolicy is set to

NoMoreOftenThan, then persistence is constrained to happen not more often than the specified number seconds.
Note: When specified in the MBeanType element, this value overrides any setting within an individual MBeanAttribute subelement.

PersistPolicy: Specifies how persistence will occur

Never. The attribute is never stored. This is useful for highly volatile data or data that only has meaning within the context of a session or execution period.
OnTimer. The attribute is stored whenever the MBean type’s persistence timer, as defined in the PersistPeriod attribute, expires.
OnUpdate. The attribute is stored every time the attribute is updated.
NoMoreOftenThan. The attribute is stored every time it is updated unless the updates are closer together than the PersistPeriod. This mechanism helps prevent temporarily highly

volatile data from affecting performance.
OnUnregister, that means that the value of the attribute is persisted when the MBean containing it is unregistered from the MBean Server

currencyTimeLimit: How long an attribute value is valid before needing to be refreshed.
0 = a seconds value

If you do not specify this attribute in the MBeanType or MBeanAttribute elements, the assumed value is Never. Note: When specified in the MBeanType element, this value overrides any setting within an individual MBeanAttribute subelement.

Knots of my imagination,
Tears me away from my bonds of Present,
Shreds – self respect and dignity,
Real self – lost in the mundane thoughts,
Fake mountains of past and future.
Obstructing my view of life.

Blind, enslaved,
Despising my own imagination,
Watching,
Glasses shattered around,
- Mistaks of the past.

Fragrance of the beautiful flowers,
Calls me.
Come dearest, Come to this beautiful present.
We are here.
Waiting for you.
Gently. Purely .
Ever Yours.

स्वराज   हमारा   जन्मसिद्ध  अधिकार हैं !

~~~~

आत्मा का प्रकाश शारीर में,

~~~~

निर्विचारिता मस्तिष्क में

~~~~

Swaraj is my birthright and I shall have it. Freedom from the slavery of thoughts – and guidance from the light of Atma. That is our path in this life.

One of the uses of JMX is for exposing any data across remotely.
If you need to use Jboss and Hyperic for JMX configuration then following configurations are required:

1. Select a property to be exposed. To test: take Catalina:type=StringCache , this is existing by default.
2. In Hyperic you can create the plugin .xml file either in the /hq-plugins folder or in the /hq/agent-4.1.3/bundles/agent-4.1.3-1067/pdk plugins folder.

3. The plugin xml file for String cache jmx  attr named: cacheSize in the file customjmx-plugin.xml  is below:

<?xml version="1.0"?>
<plugin name="customjmx" package="org.hyperic.hq.product.jmx">
  <classpath>
    <include name="pdk/lib/mx4j"/>
  </classpath>

  <config name="jmx" type="global">
    <option name="jmx.url"
            description="JMX URL to MBeanServer"
            default="service:jmx:rmi:///jndi/rmi://machineName:12345/jmxrmi"/>
  </config>

<property name="BEAN_NAME"
            value="Catalina:type=StringCache"/>
<server name="jboss_jmx">
          <property name="PROC_HOME_PROPERTY" value="program.name=testJboss.sh"/>
          <property name="PROC_MAIN_CLASS" value="org.jboss.Main"/>
	  <plugin type="autoinventory"
		class="org.hyperic.hq.product.jmx.MxServerDetector"/>
	<plugin type="measurement"
			class="org.hyperic.hq.product.jmx.MxMeasurementPlugin"/>
          <metric name="cacheSize"
                  template="${BEAN_NAME}:cacheSize"
                  alias="cacheSize"
                  indicator="true"/>
 </server>
</plugin>

Hyperic uses SIGAR for discovering processes and the PTQL is the process table query language used.
Launch sigar using java -jar sigar.jar and test the ptql in this prompt.

The important thing to know is that arguments to ps command can be seen through pargs <process_id> and then knowing that -D is appended by default when the main class is defined and then the final sigar cmd becomes:

ps  State.Name.sw=java,Args.*.eq=org.jboss.Main,Args.*.re=-Dprogram.name=testJboss.sh

Where the value program.name=testJboss.sh is defined in the customjmx-plugin.xml in the PROC_HOME_PROPERTY value.

Also, recall that if you need to associate your custom Mbean with jboss mbean viewer – then you need to register your mbean in the jboss specific mbean server whose instances can be found through the following defined ways.

Also, to expose the jboss mbeans – to jconsole – follow the steps detailed here.

I modified the run.conf with the following java opts.

JAVA_OPTS=”-Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false  -Djboss.platform.mbeanserver -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl “

To test if your plugin works:

java -jar /home/hyp/hq/agent-4.1.3/bundles/agent-4.1.3-1067/pdk/lib/hq-product.jar -Dplugins.include=customjmx  -m discover -a metric -Dlog=DEBUG

It took some time – to identify this – mainly because of incomplete(and incorrect!_) documentation which is the evil part of using open source – the good thing was – the hyperic forum is definitely alive

Hostname: name of machine where jboss is running
portnumber : is the port of jmxremote property and NOT jni and NOT RMI port defined in jboss-service.xml file.

So if you need to connect to jboss mbean through jconsole: add the following the run.conf file JAVA_OPTS

-Dcom.sun.management.jmxremote.port=12345 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djboss.platform.mbeanserver -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl

And then you can connect either remotely: localhost:12345

OR

through the JMX service url

service:jmx:rmi:///jndi/rmi://HostName:portnumber/jmxrmi

The identities of a user(username, SSN, employeeID, etc.) are stored as java.security.Principal objects in the Subject Principals set. The roles assigned to a user are also stored in the Principals set, but they are stored in named role sets using java.security.acl.Group instances. The Group interface is a subinterface of java.security.Principal. A Group is a collection of Principals and or Groups. There can be any number of role sets assigned to a Subject. Currently the JBossSX framework uses two well known roles sets named “Roles” and “CallerPrincipal”. The “Roles” set is the set of Principals for the named roles as known in the application domain the Subject has been assigned. This role set is used by methods like the EJBContext.isCallerInRole(String) which is used by EJBs to see if the current caller belongs to the named application domain role. The CallerPrincipal role set consists of the Principal identity assigned to the user in the application domain. It is used by the EJBContext.getCallerPrincipal() method to allow the application domain to map from the operation environment identity to a user identity suitable for the application. If a Subject does not have a CallerPrincipal role set then the application identity is that of the operational environment identity.

extend UsernamePasswordLoginModule
validatePassword (Authenticates user against LDAP)
getRoleSets (This adds the user role that was found in LDAP and you must hve valid role as well.