If you have just migrated a JMS based project from Java CAPS 5.1.x to Java CAPS 6 and have taken the Environment (unchanged) as well you may see the following appearing in you Application Server Log file and the JMS Fails.

RASTCMS-E307: No port specified in URL [stcms://]

This is caused by a change in the way Java CAPS 6 Glassfish installation treats the JMS Server. In the Java CAPS 6 release the concept of a default JMS server is no longer appropriate because multiple servers can be installed with the Glassfish instance. The net result of this is that the Java CAPS 5.1.x default JMS URLs (stcms://) are nolonger valid.

The resolution to this is quiet simple you will need to edit your JMS Server properties and change the URL to stcms://localhost:18007. This change will resolve the issue and cause the Java CAPS 6 application to behave in the same way the Java CAPS 5.1.x one did, assuming that you are using the default JMS ports.

With the release of Sun Java CAPS 6 we now have a number of options on how we run traditional, build or migrate applications. This blog will take part of the forthcoming Java CAPS 6 Reference Architecture and show how you can write a number of the LDAP components using a Java CAPS Repository based application (this is essentially a Java CAPS 5.1.x application), Java CAPS BPEL Module / JBIBridge and pure Open ESB components.[Read More]

The following article describes a simple, JMS based, dynamic messaging routing solution using the Sun Java CAPS suite.[Read More]

With the advent of Visual Web Pack (VWP) and Netbean 6 as an eVision developer you may want to take advantage of the superior development and GUI facilities available within VWP. JavaCAPS does not provide any automated migration from eVision to VWP rather this article will describe what you will need to consider and implement to migrate your application to the new environment. Although the eVision application I will use may be consider simplistic and contrived the implementation strategy is based on Sun recommended architectural practices for developing eVision and SOA applications using JavaCAPS.[Read More]

Following on for my previous Java CAPS Tip on Integrating Work List Manager with Sun DSEE 6.x , found here, I will further extend the concept and illustrate how we can now build a simple Visual Web Pack (VWP) based application that allows the user to View, Accept, Reject or Escalate tasks created by a simple Workflow application. As with all example it is intentionally kept simple although I hope it provides enough information for the reader to expand upon. This posting assumes you have read the previous and if following them through implement / configure your system to work with DSEE and if not please read the previous posting.

[Read More]

Although the currently available JavaCAPS documentation describes the integration of the WorkList Manager(WLM) with Sun Directory Server it does not provide a practical example. One of the key features of the WLM is the API which will allow the advanced developer to build GUI based applications using interfaces other than the standard eVision. To do this the WLM API EJB needs to be configured to integrate with the chosen DSEE instance. I will assume that the reader has and configured DSEE instance and will only discuss the functionality / configuration I require.

[Read More]