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 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);

				//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

Guru Nanak was born around 500 yrs back in 1469 on 20th Oct and he lived for 70 years 5 months 7 days and got his realization at the age of 30. He was born in talvandi in pakistan.

When he was 13 his family decided to get the “janaiu” done but he refused it as to what can a thread provide me – in terms of purification. Understanding his bent towards spirituality his family decided to marry him at the age of 16. So he had two children also. He used to work as an accountant and used to work with dedication. In the morning he used to get up and meditate and also at night. When he used to count – he used to go into “complete silence” when saying “Terah – 13″ which in turn can be heard as “Tera -” meaning Yours only God Almighty.

One day he had gone to take a bath in the river Ben and there he was inside the water for 3 days and he got God Realization – Complete revelation and complete knowledge of the divine and existence. Mardana was his dear disciple.

At that time when Guru Nanaka was born there was a lot of darkness . On this darkness He had said – that the times are like knife, the king like butchers and religion has taken wings and fly away.

Baba Farid (who was Guru of Nizamudin Auliya ) had successor Ibrahim. Guru Nanaka went to meet Ibrahim and he asked what is the right way Hindu or Islam – So Guru Nanaka said there is only one way – that which has been there since Anadi Kaal. (Ancient times ) and that way is the way to grow the Chakras and Kundalini – there is no short cut or long cut to know God.

Guru Nanaka had two principles: Two things – that people are equal and belief in service of humanity

So the style of Guru Nanaka was a mild one where as Kabira was revolutionary. Kabira challenged things and proved them wrong – all superstitious things. Like he went to Maghar (earlier was Marg Har – a place where one lost the way to go and ppl had the doubt that anybody who died there would go to hell ). And Kabira at the age of 125 to prove everybody wrong died at that place only.

Also there was an incident of Saint Farid going to meet Kabir – travelled, walked a difficult path all the way and when they met – they were silent for 3 days !! Kabira’s disciples were wondering what they two would talk about – but both of them were silent. So after Baba Farid went away – their disicples asked Kabira why did you not talk something? Kabira said where were you? Did you not hear that we talked all the time 3 days – but it was all done in silence !! -

God is expressed in silence only.

Where there is any problem or any calamity – it is best to go in thoughtless awareness – that is the greatest solution available.

The Love of Spirit is the only way to Purify the Attention – not through discipline or anger. And Kundalini is the shakti of the Spirit.

When you enjoy the Nature you can enjoy the beauty and it makes you thoughtless.
And then you feel the bliss of nature inside you . When you get complete self realization then you become beauty and fragrance yourself – like a flower.

Kartik maas ki purnima has the brightest moon, though it is not full.
Kala – the art – 16 phases of moon – are 16 phases of growth inside us. Sharad_Indu = Indu is moon – so already Sahaja Yogis have got 12 phases right upto Agya (6th chakra – two parts left – right so 12) and then from 13 to 16 we need to travel with dedication.

So after Sahasrara, we have Ardh bindu then bindu and then Valay. Bindu is the complete 16 phase of moon. Completeness. Mother is in the form of complete moon – giving blessings and love

Only a thankful heart can get the knowledge of this Divine love and keep the atma awakened. So one must remember to be grateful to Almighty Mother for this beautiful blessing and love.

One can get complete 100% realization – only with the Grace of Mother and her Compassion. Completely flowered with Her Love.

A complete sahaja yogi is one who is a Guru and being a Guru means that your Swadhistan which revolves in Nabhi has to be very strong and you need to have Motherly qualities in you. Even the greatest Muni’s and greatest Tapasvis that have been there had to worship the Adi Mother to gain the Completeness.

Every day man is moving towards his graveyard – we do not realize how the days end. When we have a holiday, we say to ourselves – never came to know how quickly the holidays ended. Similarly is the case of this life, we do not know how fast it ends. And so the Yogi’s – the seekers wish to get complete realization in this lifetime itself. But also, that we do not realize how we are blessed each and every day

1986 – Mahakali Puja – Mother said everything has to happen on its own time – and you must know worry – why it is not happening at your own set time – there are deep reasons for things happening the way they are.

====================================
Today’s meditation was Yummy Sweet Candy Amazing and in the end we had the bhajan Durga – Arti wow thank you Thank you very very very much.

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.

Here is a sample test cas restful java client.
To validate the service ticket you can use the code that is similar to yale cas client SecureUtil.java class sending an https request to /serviceValidate URL of CAS.

public static boolean validateFromCAS(String username, String password) throws Exception
	{

		String url = "https://myPC.com:8443/cas/v1/tickets";
		try
		{
			HttpsURLConnection hsu = (HttpsURLConnection)openConn(url);
			String s =   URLEncoder.encode("username","UTF-8") + "=" + URLEncoder.encode("adriza","UTF-8");
			s+="&" +URLEncoder.encode("password","UTF-8") + "=" + URLEncoder.encode("adriza","UTF-8");

			System.out.println(s);
			OutputStreamWriter out = new OutputStreamWriter(hsu.getOutputStream());
			BufferedWriter bwr = new BufferedWriter(out);
			bwr.write(s);
			bwr.flush();

			String tgt = hsu.getHeaderField("location");
			System.out.println( hsu.getResponseCode());
			if(tgt != null && hsu.getResponseCode() != 400)
			{
				System.out.println(tgt);

				System.out.println("Tgt is : " + tgt.substring( tgt.lastIndexOf("/") +1));
				tgt = tgt.substring( tgt.lastIndexOf("/") +1);
		        bwr.close();
		        closeConn(hsu);

		        String serviceURL = "http://myPC.com:8080/testingWebSvc";
		        s = URLEncoder.encode("service","utf-8") +"=" + URLEncoder.encode(serviceURL,"utf-8");
		        hsu = (HttpsURLConnection)openConn(url+ "/"+ tgt);
		        System.out.println("Response code is:  " + hsu.getResponseCode());

     	                BufferedReader isr = new BufferedReader(   new
                                    InputStreamReader(hsu.getInputStream()));
		        String line;
		        System.out.println( hsu.getResponseCode());
		        while ((line = isr.readLine()) != null) {
		        	System.out.println( line);
		        }
		        isr.close();
		        hsu.disconnect();
		        return true;
		    }
			else
			{
				return false;
			}
		}
		catch(MalformedURLException mue)
		{
			mue.printStackTrace();
			throw mue;
		}
		catch(IOException ioe)
		{
			ioe.printStackTrace();
			throw ioe;
		}
	}

[Original : November 2007]

[rubik:/tmp/jboss-3.2.3/bin] % ./shutdown.sh -s jnp://myremotemachineOrIP:1099Shutdown message has been posted to the server.Server shutdown may take a while – check logfiles for completion

Stopping JBoss when running multiple JBoss instances using the Service Binding Manager

./shutdown.sh -s jnp://myserver:31099 -S

You will again use the lower-case -s flag but you will need to look in your bindings file to find the port of each Naming service.

<service-bindings>
<server name=”ports-default”> <
service-config name=”jboss:service=Naming” delegateClass=”org.jboss.services.binding.AttributeMappingDelegate” >
<delegate-config portName=”Port” hostName=”BindAddress”>
<attribute name=”RmiPort”>1098
</attribute> </delegate-config>
<binding port=”1099″ host=”${jboss.bind.address}”/>
</service-config>

UPDATE – 22-Oct-2009

-> Default behavior is to shutdown (S)
Other operations:
-S, –shutdown Shutdown the server
-e, –exit= Force the VM to exit with a status code
-H, --halt= Force the VM to halt with a status code
And default port for shutdown used is jnp 1099. You can test this by experimenting with jnp port in jboss-service.xml

Another point is that usage of username , password for authentication for shutdown. (u,p)
If you have enabled the interceptor in jmx-invoker-service.xml file in deploy folder.

<!-- Uncomment to require authenticated users -->
                  <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor"
                     securityDomain="java:/jaas/jmx-console"/>

Then it will refer to the security Domain jmx-console from the login-config.xml in the conf folder to check if user credentials.If user is not valid then it will throw the following Exception:

jboss-4.2.3.GA\bin>shutdown.bat -S
Exception in thread “main” java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)

In login-config.xml you can define your own login class that will check if the user has valid roles and credentials for doing the op.

Inspektr library is an auditing aspect built inside CAS server.

This library has two aspects built in – one is AuditTrailManagementAspect and other is StatisticManagementAspect.

Like any other aspect class the above two classes are annotated with

@Aspect at top class definition and
@Around for managing aop method execution.

The notable points wrt this library are:
There is a custom annotation that is created called @Auditable (similarly @Statistics)
To create a custom annotation we need to define the class as follows:

@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.METHOD)
public @interface Auditable {}

Then there are three parts to Auditing: (user info, resource info, action info)
Principal: User info
Resource: Ticket info (ST or TGT)
Action : type of ticket created info (Failure or success)

So classes providing this info are injected along to the AuditAspect class along with the name of the class that will know how to publish this information to the right output.

User info, we have the class called TicketOrCredentialBasedAuditablePrincipalResolver.
Resource: Service ticket info, ServiceResourceResolver
Action: ObjectCreationAuditableActionResolver (prefixes failure/success based on null value check of object)

One question can come is why are we keeping all the resources in the list of of constructer. Example if I only need to audit the service ticket creation or validation then should the references of other resources is needed? . The answer is that object creation of these resources takes place one time only in the construction of the aspect class so that these object handlers of resources can be used in different places (be it TGT or ST creation etc.) .

If there is no @Auditable tag kept only at the level of service ticket creation then only one resource resolver an be kept at the list level which is ServiceResourceResolver. (Note you would need to remove @auditable annotation from other places to avoid error)

<bean id="auditTrailManagementAspect" class="org.inspektr.audit.AuditTrailManagementAspect">
		<constructor-arg index="0" ref="auditablePrincipalResolver" />
		<constructor-arg index="1">
         	<list>
	         	<bean class="org.jasig.cas.audit.spi.CredentialsAsFirstParameterResourceResolver" />
	         	<bean class="org.jasig.cas.audit.spi.TicketAsFirstParameterResourceResolver" />
	         	<bean class="org.jasig.cas.audit.spi.ServiceResourceResolver" />
			</list>
		</constructor-arg>
		<constructor-arg index="2">
			<list>
				<bean class="org.inspektr.audit.support.ConsoleAuditTrailManager" />
			</list>
      	</constructor-arg>
		<constructor-arg index="3" value="CAS" />
   </bean>
<bean id="auditablePrincipalResolver"
                class="org.jasig.cas.audit.spi.TicketOrCredentialBasedAuditablePrincipalResolver">
		<constructor-arg index="0" ref="ticketRegistry" />
	</bean>

The class that manages the final bundle of information – i.e clubbing of complete info related to resource, principal and action is AuditableActionContext that stores all the data (strings of info) in it and the object of this class is then used by the manager that “records” the information in the right output. So for example the ConsoleTrailManager will do a simple sysout of the information.

 public void record(final AuditableActionContext auditableActionContext) {
        System.out.println("Audit trail record BEGIN");
        System.out.println("=============================================================");
        System.out.println("WHO: " + auditableActionContext.getPrincipal());
        System.out.println("WHAT: " + auditableActionContext.getResourceOperatedUpon());
        System.out.println("ACTION: " + auditableActionContext.getActionPerformed());
        System.out.println("APPLICATION: " + auditableActionContext.getApplicationCode());
        System.out.println("WHEN: " + auditableActionContext.getWhenActionWasPerformed());
        System.out.println("CLIENT IP ADDRESS: " + auditableActionContext.getClientIpAddress());
        System.out.println("SERVER IP ADDRESS: " + auditableActionContext.getServerIpAddress());
        System.out.println("=============================================================");
        System.out.println("\n");
    }

So if you need to record additional information like browser info, session id , etc, then you need to see if you wish to extend Auditable or create your own custom Aspect class that will handle all the data.