|
|
KTNET made an ebXML Messaging Service Handler (MSH) conformed
to the ebXML Messaging Service spec. v1.0. [ebMS]. Using this
program, you can exchange messages with other business partners.
In the old days, it had been called “Partner Solution”.
But nowadays KTNET named it “GetMate MSH v1.1”.
GetMate MSH v1.1 supports XML namespaces and XML Digital Signatures.
And it is a client program for the ebXML Registry and Repository
[ebRegRep] system made by KTNET eRearch team. So you can access
it using this program.
|
KTNET eRearch team made a Messaging Service solution, GetMate MSH
v2.0. It is conformed to the ebXML Messaging Service spec. v2.0.
[ebMS].
This solution is a kind of B2Bi Solution to consist of an ebXML
Messaging Service Handler, Messaging Queues, a control console
and some adapters.
The ebXML MSH is a demon to send/receive messages and is bound
with Messaging Queues. In this solution, the ebXML MSH module
is loosely coupled with CPA. So without CPA, you can configure
your messaging service system. (According to the spec., you
should use a CPA to exchange messages with other parties.)
Messaging Queues are temporary storages for the messages to
be passed to legacies or to an ebXML MSH. In this solution,
KTNET made Messaging Queues conformed to the JMS spec.
KTNET also made several adapters for XML files, e-mails and
RDBMS. These adapters are interfaces between legacies and an
ebXML MSH. So legacies can put or get messages through these
adapters.
Finally, KTNET made a console to control
and to manage the other modules such as an ebXML MSH, Messaging
Queues and adapters.
This is a console program. Using it, you can manage these solutions.
It provides several functions such as auditing messages, routing
info., security, managing messaging queues(JMS) and managing
adapters. (But a security function is not yet implemented.)
To use this solution, Oracle 8.1 or higher should be installed
on your computer.
|
|
