Java CAPS 5.1 developer may need to determine a runtime value of one or more system properties to, perhaps, use its vale for runtime flow control. This is the first in a series of notes on the use of Java Properties for controlling runtime behaviour of Java CAPS solutions.
This note walks through an example of configuring Java CAPS 5.1 and developing, and exercising, a Java Collaboration Definition that dumps all system properties to a file and that accesses the values of two specific properties, by name, and dumping them to a file as well.
Java CAPS solutions can selectively retrieve messages from JMS Destinations using static selector expressions, configured in Connectivity Maps. This configuration is performed at design time and is static – to change a selector value requires that the solution is re-built and redeployed.
Handling very large messages in a messaging solution may require memory resources many times greater than the size of the largest message to be handled. Frequently the architect has no choice but to consume or produce a very large message, a file containing a batch or related transactions, for example, or a large and complex XML message generated by, or intended for, an external application. Handling such messages poses special challenges.
Java CAPS can assist with Batch eWay support for data streaming when large messages are manifested as files in a file system.
If it is possible to break large messages up into components and process components individually, or collect components and assemble them into a large message. eTL, another of the products in the Java CAPS Suite, can assist in processing large volumes of data. Whilst ETL (Extract, Transfer and Load) is typically associated with one off batch extraction and load of data, Java CAPS’ eTL can be used both standalone and in-stream as part of a larger Java CAPS solution. In this in-stream mode it will be discussed as a possible means of streaming data between a flat file and database table or between
This extract from the soon–to-be-released book, “Java CAPS Basics – Implementing Common EAI Patterns”, discusses the Java CAPS 5.1 Batch eWay streaming facilities, and presents and compares a number of data streaming implementations, including an eTL implementation.
As at release 5.1 Java CAPS supports WS-Security 1.0 (2004) Username Token Profile. Java CAPS eInsight- and Java Collaboration-exposed web services can be configured to require and validate Username/Password credentials before performing their programmed function. Java CAPS eInsight-based and Java Colaboration-based web service consumers can be configured to supply WS-Security 1.0 (2004) Username Token SOAP Header.
Java CAPS 5.1.3_Notes_Using_WS-Security_1.0_Username_Token_Profile.pdf discusses configuration of the Username Token, creation of users, configuration of access to service and testing secured services. It illustrates the discussion with a step-by-step example of implementing, securing and exercising a web service consumer and a web service implementation which use the Username Token infrastructure.
WSDLWSUserAuth.wsdl is the WSDL interface specification document for a service developed in the example.
XSDWSUserAuthString.xsd is the XML Schema Document defining the data structure used as input and output of the example service.