Wily To Pry Open J2EE Business Management
Wily Technology is looking to help Java devs and architects struggling for ways to pry more visibility out of their J2EE-based integrated legacy networks. See why a maturing J2EE app architecture can create nightmares for devs and IT managers, and how Wily is looking to help both get a better night's sleep.
Wily Technology is looking to fill the gap for devs and architects struggling for ways to pry more visibility out of their J2EE-based integrated legacy networks.
"A maturing J2EE application architecture that supports applications, portals and [uses] middleware to connect to legacy apps and databases simply needs higher levels of performance and availability than can be secured out-of-the-box.," Mike Malloy, Wily's vp of marketing told Integration Developer News.
To begin to address the problem, Wily is offering Wily 5, an upgraded app management platform that includes enhancements to its Introscope line of PowerPack probes and components The key Introscope's upgrade is the ability to monitor dataflows inside Java adapters/connectors. In this latest release, Wily 5 supports IBM's Websphere Business Integration adapters. Other features include:
Wily brings a long history of offering third-party support to J2EE management. In its 6th year, Wily was the first to have a J2EE portal management solution. It was also first to market with software to mange integration connections to CICS and Tuxedo. Now, as more Java/J2EE developers look at integrating with non-Java assets, Wily turns its attention outside the stack to business workflows.
Why the "Traditional" Silo Won't Work
"With J2EE, especially as the applications are becoming more complex and are touching a lot more established applications to create a whole end-to-end business process, the traditional silos don't work anymore," Malloy said.
"It used to be a developer wrote it, he did his unit testing, he handed it to the QA group, they did some integration testing, and they handed it to the datacenter, and then they're done And the DC just ran it and ran it. But, as Java/J2EE integrates with many more backend systems (databases, applications, websites), To use a traditional management tool or approach, doesn't work."
Today, Malloy noted, many developers are dealing with or even building "a business process, that aggregates data and integrates it for users and it integrates data spread across backend systems (SAP, PS, Siebel), it will flow throw connectors, either ones you've built yourself or those from IBM or BEA.""Today," Malloy said, "our customers want to know "Is it me or is it them? Where is the problem? Is it on the J2EE side or on the SAP side.' In addition, if they are connecting SAP-to-Oracle/Siebel, they want to monitor those connections, and the adapters are the glue that are holding this transaction together. So, that's the critical point to monitor."
To cite an example, IBM's BI adapters for WebSphere do data synchronization between the applications (SAP to Siebel/PeopleSoft). But, until Wily 5, there's been no way to closely monitor what's going on inside these crucial connections from J2EE.
In response to this gap, The Introscope upgrade provides monitoring of 100% of the transactions flowing through the IBM BI adapters. Aside from Introscope's latest upgrade, Malloy said, "currently, there is no monitoring solution for these adapters. It's currently an untapped area." He did note that "IBM has a monitoring solution for the integration broker in the middle and for the Interchange Server from CrossWorlds, but there isn't anything for the adapter."
By offering devs the ability to monitor transactions as they pass through the adapter, Malloy said Wily 5 looks to "help technical staff locate and determine the nature of a problem, when it arises in a workflow or integrated application."
Helping the "Guy in the Middle"
To put it simply, Malloy said Wily 5 is designed to help "the guy in the middle" of the enterprise. This person, Malloy said, is sometimes called an "Application Support Manager (ASM)," and is typically a technical person that needs to bridge the gap between the Line of Business managers and the hands-on technologists (such as the architects and developers) who delivers an integrated application or solution. "Because in today's J2EE architecture, we're talking about a composite architecture with a lot of moving parts, visibility is the key to locating and fixing any problems.
"Users that have purchased [J2EE] components from different vendors have some issues, at least from the point of view of BEA and IBM Wily sees customers continuing to use third party components as well as adopting a [single vendor] approach," Malloy said.
So, as a use case, Malloy offered the following scenario:
Many J2EE users have a common front end framework built around a portal; which ties to a common [J2EE] app server and components that aggregate data for traffic control. In turn, this J2EE silo is tied to a set of integration connectors optimized for that platform.
"The result of this approach is that there will be less bolting that needs to take place. If you've purchases these components from different vendors, you have some issues -- at least from the point of view of IBM and BEA," Malloy said.