| Saigun
>> Technologies
>> Technology
Platforms >> |
| |
Business applications
in the current scenario, rarely live
in isolation. The expectation of users
is a fluent access to all business functions
offered by an enterprise, irrespective
of which system the functionality may
reside in. This requires a larger, integrated
solution, to which disparate applications
can be connected into. Middleware provides
the "plumbing" such as data
transport, data transformation, and
routing which facilitate integration
through its use.
Most integration vendors provide methodologies
and best practices, but these instructions
tend to be very much geared towards
the vendor-provided tool set and often
lack treatment of the bigger picture,
including underlying guidelines, principles
and best practices.
Saigun designs and implement integration
solutions, across the following six
types of integration projects:
|
Many
business users have to access
more than one system to answer
a specific question or to perform
a single business function. Some
portals require even more sophisticated
user interaction and blur the
line between a portal and an integrated
application.
|
Many business
systems require access to the
same data. For example, the customer
care system , the accounting system
, the shipping system and the
billing system, as a sequence
of a transaction . Many of these
systems are going to have their
own data stores to store customer
related information. When a customer
calls to change his or her address
all these systems need to change
their copy of the customer’s
address. This can be accomplished
by implementing an integration
strategy based on data replication
using replication functions, export
data into files and re-import
them into the other system, or
message-oriented middleware to
transport data records inside
messages.
|
Multiple
systems may need to check whether
a social-security number is valid,
whether the address matches the
specified postal code or whether
a particular item is in stock.
It makes business sense to expose
these functions as a shared business
function that is implemented once
and available as a service to
other systems.
|
Service-oriented
architectures (SOAs) blur the
line between integration and distributed
applications. Calling a service
may be considered integration
between the two applications.
A service-oriented architecture
enables calling an external service
almost as simple as calling a
local method (performance considerations
aside).
|
One of the
key drivers of integration is
the fact that a single business
transaction is often spread across
many different systems. Its a
business process management component
that manages the execution of
a business function across multiple
existing systems.
|
Integration
frequently occurs between business
partners. Communicating across
the Internet or some other network
usually raises new issues related
to transport protocols and security.
Also, since many business partners
may collaborate in an electronic
“conversation” standardized
data formats are critically important.
|
|
|
Most packaged and legacy applications
and many custom applications are not
prepared to participate in an integration
solution. We need a message endpoint
to connect the system explicitly to
the integration solution. The endpoint
can be a special piece of code or a
Channel Adapter. This is where Saigun
plays the role of an integration software
vendor.
We meticulously consider the design
trade-offs for our customers. Our solution
diagrams and descriptions describe a
solution in a vendor-and technology-neutral
language that is much more accurate
than a high-level sequence diagram.
Saigun's Software integration solutions
support EAI projects in two key ways.
First, our Adapter Manager and adapters
can be used to build enterprise application
integration solutions. Rapid message
transformation and mapping, routing,
and application access is facilitated
in order to integrate disparate systems
with an absolute minimum of custom code.
Our solutions can be easily extended
to plug into any standards-based platform
as integration architectures evolve
to support straight-through processing
initiatives and large-scale Web services
deployments.
Second, our Intuitive Adapters extend
the reach of platforms from any standards-based
framework, to easily and quickly connect
disparate enterprise information assets.
These include packaged applications,
mainframe and legacy systems, non-relational
data sources, e-business documents,
and more.
Our solutions allow value addition into
projects and facilitates quick production
without impacting any future platform
decision.
Saigun provides support and integration
services using Java based connector
services. The platforms supported are
|
• |
Saigun offers
Intuitive Adapters that are optimized
to work with BEA WebLogic Integration
application views. These adapters
can also support BEA WebLogic
Server and the rest of the WebLogic
Platform.
|
• |
Saigun integrates
easily with WebSphere Business
Integration solutions, including
WebSphere MQ (formerly MQSeries),
WebSphere MQ Integrator (formerly
MQSeries Integrator), and CrossWorlds.
We also have complete support
for WebSphere Application Server.
|
• |
Saigun provides a comprehensive
and easy way to connect complex
non-Microsoft environments to
BizTalk Server 2002 and 2004.
We also support application development
with .NET and other Microsoft
technologies, using standard interfaces
such as ODBC, OLE DB, and OLE
DB.NET.
|
• |
Saigun provides JCA-based
connectivity from SAP NetWeaver,
including Exchange Infrastructure
(XI) and Web Application Server,
to virtually any application,
information system, or middleware.
|
• |
Saigun's
adapters customized for the Sun
Java Enterprise System, including
the Sun Java System Application
Server, Sun Java System Message
Queue, and Sun Java System Portal
Server, provide seamless access
to various back-end systems.
|
|
|
|
|
|
