hi, can anyone tell me the main differences between the
WM4.6 and IS 6.0 architecture.
thank you

The main differnce is IS & ES are tightly coupled with IS
hosting adapters for both. Both IS & ES development can be
done with Developer. wM 6.0 adapter have local queues for
both inbound and outbound.

Rao Kalvala
Sr. Principal Architect

Hi, rocky.

There is some good discussion on the board about this. Read
up on the following link:

• [url=“wmusers.com”]wmusers.com

Phil Leary had some great remarks so be sure to stick with
the whole thread.

Thanks.

(Message edited by admin on June 12, 2003)

IS 6.0 architecture is very similar in nature to IS 4.6.
The adapter architecture changes significantly as mentioned
in earlier discussions, but the product works very much the
way it did in version 4.6. I think it’s safe to say that
the bulk the existing IS functionality remains for the most
part, unchanged and that most existing IS 4.6 flow and java
services will run as is in 6.0.

The easiest way to spot the big changes in IS is to explore
the new 6.0 version of the IS Developer tool. In addition
to some handy ease-of-use changes, its functionality has
been expanded significantly to include the following new
capabilities:

• Create and publish Enterprise document types (formerly
  events)
• Subscribe to Enterprise document types by creating Trigger
  that can invoke a flow service based on the receipt of one
  or more doc types (like the 5.0 Enterprise join adapter) as
  well as the content of those doc types (via filters)
• Synchronize either a single doc type or all IS server doc
  types created or modified in Developer with a single
  associated broker server
• Create Adapter Services to define adapter business logic
  (using Flow) for Enterprise adapters developed using the new
  ADK
• Create an Adapter Notification (and associated doc type)
  that receives a notification from an adapter and publishes
  the specified notification doc type
• Define Flat File Schemas that describe the structure of a
  flat file, Flat
• File Dictionaries that hold commonly used flat file
  structures and flat file handling services
• Define (using the IS Admin tool) new “ports” to poll a
  file system folder for the arrival of a particular file to
  process

In addition, the Tomcat servlet engine is now embedded in
the IS product to allow developers to create JSPs (using a
provided taglib) that invoke flow services (apparently there
is an underground movement within WM to replace all of the
existing DSP’s that make up the IS admin tool with JSP’s,
but I think that will take a release or two to accomplish)

But my favorite change of all can be best summed up as “ding
dong, the bridge is dead”. No more kludgy, poor performing
ES to IS bridge adapters or packages.

I’m sure that there are several things that I’ve missed, but
those are ones that come to mind first.

Mark