Uncategorized
Installing Oracle Service Bus 10gR3 on Mac Os X Jeroen van Wilgenburg 24 Dec, 2008
com.ibm.CORBA.loginSource=properties
com.ibm.CORBA.loginUserid=<your websphere username>
com.ibm.CORBA.loginPassword=<your password>
Then start WAS_HOME/java/bin/jconsole using the following options: -J-Djava.class.path=WAS_HOME/java/lib/tools.jar;WAS_HOME/runtimes/com.ibm.ws.admin.client_6.1.0.jar
-J-Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory
-J-Dcom.ibm.CORBA.ConfigURL=file:WAS_HOME/profiles/dmgr01/properties/sas.client.props
-J-Dcom.ibm.SSL.ConfigURL=file:WAS_HOME/profiles/dmgr01/properties/ssl.client.props
Fill in WAS_HOME your self and mind the semicolon on unix!
dmgr01 is my deployment manager profile
The -J gives you the opportunity to enter any standard JVM option, so jconsole -J-Xmx500M
would be the way to set the heap to 500Mb.
Then the gui pops up. Go to the advanced tab and enter service:jmx:iiop://[host]:[port]/jndi/JMXConnector
where port is the bootstrap port for the deployment manager. Connect without entering credentials (they´re already in the file) NB. You´ll have to watch your command shell, because it may prompt you to add the SSL certificate signer to the trust store. What you then get is a slightly different jconsole. It only shows you the tab containing the available mbeans instead of all monitoring like options a Sun jvm offers out of the box (like cpu heap and usage counters). Instead you have all the mbeans needed to manage the cell. Every function in be it in the web console or wsadmin can be found here. This is all really neat, but not actually helpful, because you already had administrative tools. Let´s think of something useful. Managing the SI Bus. Through Mbeans you can also do things not available in the console. Like manage messages in queues.
So I set up a Service Integration Bus (using the webconsole), defined a queue and set up JMS resources: a queue reference to the bus queue and a queue connection factory. Bus member was my application server.