With my previous blob entries I have discussed and documented how to
run your Java CAPS (5.1.3) applications on both the SJSAS 8.2 & 9.1
and the Glassfish V2 application servers. Given this you may well want
to switch the JMS you use but this may not be the case. Alternatively
you may want to continue running the STCMS Message Server and by
default to do this you will need to install and start a normal Logical
Host. You may consider that this is an unnecessary overhead just to run
the STCMS component. This blog therefore simply documents the process
of running the STCMS in a standalone environment outside the confines
of a Logical Host installation.[Read More]
Open ESB: The Solution for the Open Minded The Crooked Stick
| My Other Crooked Stick (Archery) |
Tuesday Dec 16, 2008
Following on from my previous entry "Configuring
SJSAS For MSMQ XA Transactions" I have put together the following
blog entry that updates the information to cover the Glassfish
Application Server. Although the procedure is essentially the same as
SJSAS 8.2 configuration we loss some of the flexibility associated with
managing and monitoring using the Enterprise Manager. Therefore this
blog quickly documents the difference and what is required to deploy
the generated ear files.[Read More]
Tuesday Dec 09, 2008
Following on from my MSMQ blog entry, "Reading
MSMQ Messages with high TPS", I was required to reproduce the
scenario running in a SJSAS 8.2 Environment. Since this is not the
standard Java CAPS 5.1.3 Runtime Application Server we need to
configure is specifically to work with the appropriate queue systems.
Although a number of documents exist informing you how to do this the
key information does not exist at present in an online format. So I
have decided to put this entry together based on a number of the
engineering documents so that I can easily access the information when
required.[Read More]
Monday Nov 24, 2008
Recently on a project I was working with a client that needed to read
messages from MSMQ and move them to STCMS with a minimum TSP of 250. In
addition this pass though scenario needed to be done using XA
transactions and hence guarantee message delivery. Now given that
implementing the standard MSMQ eWay functionality restricts the eWay to
polling with a minimum interval of 100 ms this gives the developer a
maximum of 10 TPS. Although their are many ways to implement this type
of functionality this blog entry documents the solution implemented at
the clients that exceeded their minimum TPS requirement.
[Read More]
[Read More]
Friday Nov 14, 2008
Extending on my recent blog entries around the BPEL 2 SVG Generator I
have extended the functionality so that it will now generate
highlighted paths through the SVG file by setting the various opacities
of the Complex and Simple activities. The net result of this is that is
is now easy to quickly generate SVG file on the fly from any given Open
ESB BPEL 2 file. To showcase this new
functionality I have built a small Visual Web Pack page that is linked
to the BPEL 2 persistence tables and will display the SVG based on the
selected BPEL process. This Visual Web Pack Application can be
installed as a self contained application on any Glassfish instance it
requires only the existing jdbc/bpelseNonXA JDBC connection pool
definition to the persistence
database and will provide a Graphical BPEL Monitor. For a full description see Open ESB Tip : Simple Web Based BPEL 2 SVG Monitor
Monday Nov 03, 2008
Following on from my previous blogs and some of Adam's I have noticed
that I need to add some more documentation around the usage of the BPEL
2 SVG generator. Therefore the purpose of this blog entry is to do just
that. I will take some example code (from the NetBeans Plug-in Action)
and explain what each of the parameters and settings achieve. For the full blob entry see Open ESB Tip : BPEL 2 SVG Usage Documentation
Wednesday Oct 22, 2008
Following on from my previous blog entry "Generating
SVG From BPEL 2 Files" I have updated the core code to include
those features that were originally missing. The new code samples can
be found in the original location but I decided to add this blog to
quickly sumarise the key features I added. For the full blog entry see Open ESB Tip : BPEL 2 SVG Update
Tuesday Oct 14, 2008
Following on from Adam's sterling work of graphical monitoring of BPEL
Processes in his blog entry on Graphical
BP Monitoring one of the most common question was why can't we
generate this auto-magically. Well within this blog entry I will take
you through the steps required to generate SCG files from a BPEL and
then extend the NetBeans Interface to allow the user to simply
Right-Click a bpel file and generate a svg file.
For the full blog entry see the Open ESB Tip : Generating SVG From BPEL 2 Files
Wednesday Sep 17, 2008
Following on from my blog entry "Building
a JMS Browser Monitoring / Management Plug-in Module for NetBeans"
I was asked if this was built using the Java CAPS Management API. The
previous blog entry was actually built around the Java CAPS 6
stcqueueviewer API and as such did not have access to all the new
functionality within the Management API. Therefore I decided to copy
the existing project and modify the core JMS Implementation Classes to
work with the Management API and will quickly document the key
differences.
[Read More]
[Read More]
Tuesday Sep 09, 2008
This short Blog entry will take you through building a simple NetBeans
Plug-in that can be used to browse the contents of a JMS Queue Manager.
For the purpose of the Blog I will interface to the Java CAPS 6 Message
Server although the example should be flexible enough to work with any
Message Server assuming you have the appropriate interface.
The Module implemented within this blog will create a simple Java CAPS 6 JMS Servers node that will be integrated into the NetBeans Services tab in a similar way to the existing Servers node. The module will allow the user to specify and connect to multiple Sun-SeeBeyond JMS Servers and the associated configuration will be stored within the NetBeans <userdir>/config/JMSServer directory. Once connected to the appropriate Java CAPS 6 JMS Manager the user will be able to view all the Queues and Topics that are available within that Server and then for each Queue or Topic the Messages that are currently available.
This simple implement will provide the reader with the ability to build a JMS Monitoring / Management system that is integrated into the NetBeans framework.[Read More]
The Module implemented within this blog will create a simple Java CAPS 6 JMS Servers node that will be integrated into the NetBeans Services tab in a similar way to the existing Servers node. The module will allow the user to specify and connect to multiple Sun-SeeBeyond JMS Servers and the associated configuration will be stored within the NetBeans <userdir>/config/JMSServer directory. Once connected to the appropriate Java CAPS 6 JMS Manager the user will be able to view all the Queues and Topics that are available within that Server and then for each Queue or Topic the Messages that are currently available.
This simple implement will provide the reader with the ability to build a JMS Monitoring / Management system that is integrated into the NetBeans framework.[Read More]
Wednesday Aug 13, 2008
This blog entry takes the process implemented in Part
1 of this trail, eInsight Implementation, and extends it to
integrated it into a new BPEL 2.0 style process. Because we are
extending what has already been implemented I will not be discussing
those sections in detail and assume that you have read the previous
part.[Read More]
Tuesday Aug 12, 2008
This blog entry takes the process implemented in "Simple
Visual Web Pack Implementation of the Work List Manager GUI" and
attempts to relate it to a real world example. The example chose is
that of a Vendor Management Process (VRMP) where a given company
would like to raise all its Purchase Orders (PO), to suppliers, over
the internet and allow them the Accept / Reject and then Raise
associated Advanced Shipment Note (ASN) for the PO. I will initially
build the User Process
using the classic Java CAPS 6 Repository style eInsight, within this
blog entry, as Part 1 of a three part trail.[Read More]
Friday Jul 11, 2008
Building upon my previous Blog entry "Simple
Visual Web Pack Implementation of the Work List Manager GUI" I will
demonstrate a simple dynamic, JMS based, Message Validation solution
that integrates with the Java CAPS Work List Manager (WLM). Although
this project is built using Java CAPS 5.1.x it can be imported into
the Java CAPS 6 and used in the same way. I also extend the previously
defined eInsight Workflow and associated WLM application but I will not
describe in detail the implementation of the WLM project or the
configuration because these are described in previous entries. I intend
to write a future article that will revisit this functionality based on
the new features available within Java CAPS 6 and Open ESB.[Read More]
Friday Jul 04, 2008
Following on from my previous blog entry on Reconfiguring
Java CAPS EARs I will expand on the functionality available within
the Java CAPS 5.1.x iConfigure Tool and how it can be used to
reconfigure a deployed EAR file. Then I will compare this with, its
evolutionary successor, within Java CAPS 6 configuration utility.
Although at present there is no migration tool to move the iConfigure
xml files information to the new property structure this would be an
interesting sideline project for when I have some free time.
[Read More]
[Read More]
Monday Jun 30, 2008
Given the new reconfiguration functionality available within the Java
CAPS 6 release you may be wondering why this type of functionality is
not available within the previous releases of the tool set. Well their
is a little known, undocumented, tool that is available from Sun Java
CAPS support called iConfigure.
The iConfigure
tool will allow you to take an existing 5.1.x ear file and change
its configuration based on a supplied, delta, XML configuration file.
As a result of this you can now redeploy and reconfigure you Java CAPS
5.1.x EAR file without needing to rebuild that EAR within Enterprise
Designer.
My intention within a future blog entry (Java CAPS Application Configuration) is to describe to people already using the iConfigure tool how they can successfully migrate their configuration information from their XML file to the Java CAPS 6 properties based implementation thus facilitating ease of migration.
My intention within a future blog entry (Java CAPS Application Configuration) is to describe to people already using the iConfigure tool how they can successfully migrate their configuration information from their XML file to the Java CAPS 6 properties based implementation thus facilitating ease of migration.
As a member of the Sun Elite FAST Team we specialise in enabling the GlassFish ESB, Open ESB and Java CAPS communities.
My Archery BlogBritish Longbow Tour
26th August 134619th September 1356
25th October 1415
