Professional Documents
Culture Documents
Jump Start
Teacher Edition
STATUS: Released
REVISION HISTORY:
Incentage
Incentage Education Table of Content
TABLE OF CONTENTS
1 PREFACE 1-1
1 Preface
1.1 Goal
This document provides an outline of the Incentage Middleware Suite. It
documents the installation procedure and prepares for the first usage.
1.2 Audience
The primary audience for the Incentage Education Jump Start volume is:
Integration project team members: Those responsible for carrying out the
tasks required to achieve the project objectives.
1.4 Icons
Whenever this icon appears, you are supposed to follow the steps or find out yourself how to
do something. This indicates a hands-on exercise that requires you to use your notebook.
This icon introduces a section consisting of test questions. You either have the answers in
your handout or you are supposed to fill in the correct answer yourself.
This icon highlights an important hint. Read this very carefully as it is a recommendation
about the proper usage of the Incentage Middleware Suite.
2.1 Goal
The goal of this chapter is to provide an outline of the Incentage Middleware
Suite architecture to enable integrators who are not familiar with Incentage to
properly use it and understand solution designs based on the Incentage
Middleware.
2.2 Overview
Incentage consists of three building blocks:
Figure 2-1 illustrates the building blocks of the Incentage Middleware Suite.
Incentage
Appl. A Appl. B
Component
Status
Commands
Mapping Reporting
Rules DB
Configuration
The next sections will give you a detailed view of the three building blocks.
2.2.1 Component
The Incentage Middleware Suite provides highest flexibility with
a component oriented architecture. The connection between
two or more applications is represented by an Incentage flow
and consists of a set of components.
Appl. A Appl. C
MA MB
Incentage Incentage
Component Component
Transaction Mgmt.
Configuration
Machine C
Status
Incentage
Component
MD
Incentage Incentage
Component Component
Appl. A Appl. C
The components are combined as needed and allow the realisation of arbitrary
Integration topologies.
2.2.2 Modules
An Incentage component is subdivided into modules. It is
important to understand this module structure. It is used in many
different contexts. The module structure is the basis of the
flexibility of Incentage. It allows custom configuration, a flexible
version management, development by different persons, decoupling of the
components from their presentation, and more.
Transaction
Input Output
Input Output
Source Convertor Target
Log
Control
Remote Control
Service
Component Control
Note that it is possible for the converter to replicate messages and route them
to different target modules.
The following picture shows the role of the CCD when starting up a component:
JAVA
JAVA
JAVA
classes
classes
classes
Load
appropriate
classes
Generic Configured
Component Customized
Executable Component
Component
Configuration
Descriptor
The GCE is started and reads in the CCD. From the CCD the GCE recognizes
which component it needs to start and loads the appropriate class(es). These
classes are then initialised with the settings stored in the CCD. The result is a fully
customized and configured component.
• Version updating can be done partially. You need to add the JAVA
classes to the repository and modify the CCD to support the new
version.
The following picture explains the steps. Feel free to take the illustration on the
next page out of the file and place it onto your table so that you can keep an
eye on it.
Processing Reading Message Parsing Message Conversion Building Message Writing Message
Steps
Incentage
Input Adapter Parser Converter Builder Output Adapter
Module
Reading message Analysing syntax of Restructering, Creating a string from Writing message to
from protocol or messages. Creating mapping, converting, the message object media or sending via
Description media. Splitting message object with formatting the following a certain a protocol.
batches of messages fields. Business message object. syntax
objects are created.
Id F ie ld Id F ie ld
1:F01BCITITMMAXXX6438407 Aer akkk ll
Id F ie ld Id F ie ld
:16R:GENL Id F ie ld Id F ie ld
Rii jjcs 84
Id F ie ld Id F ie ld
:28E:1/ONLY Id F ie ld Id F ie ld
Apo cmwo 82
:20C::SEME//253310748 Id F ie ld Id F ie ld
Aer akkk ll
Visual :23G:NEWM :28E:1/ONLY Aer akkk ll Rii jjcs 84
:69A::STAT//20030329/20030331 :20C::SEME/ Id F ie ld
Id F ie ld Id F ie ld
Id F ie ld
Rii jjcs 84 Apo cmwo 82
:22F::SFRE//DAIL :23G:NEWM Apo cmwo 82 Aer akkk ll
:97A::SAFE//253310748} Id F ie ld Id F ie ld Rii jjcs 84
:97A::SAFE//253310748} Id F ie ld Id F ie ld
Apo cmwo 82
:97A::SAFE//253310748}
As the Incentage Middleware is built upon Java that runs on both, Windows
and Unix, the RulesStudio and the Middleware are loosely coupled through XML
documents. This means that you can save the rules into XML documents that
are fully compatible to any operating system.
Rules Studio
Test Windows
Rules Repository
*.xml
ccd.xml
3.1 Goal
In this chapter you get an overview on the Incentage runtime environment. This
allows you to quickly install Incentage and understand the steps.
The next section gives an overview over the building blocks of an Incentage
installation.
Incentage
EMail
ODBC Security
MQSeries XML
Java Virtual Machine
OS
: Libraries (jar files)
: java.exe & java libraries ( jar files)
: Binaries (.class files) & ressources
Incentage consists of a core system (red in Figure 3-2) and additional libraries
(the yellow and blue boxes). All this software consists of Java .class or .jar files
and can be found in the Incentage Installation directory.
To run Incentage a set of start scripts (batch files in Windows) are used.
The scripts start the JVM, load Incentage and include the required libraries. The
scripts provide you with a single entry point to the Incentage Runtime
Environment.
3.6 Questions
What is the advantage of Incentage being a Java
application?
b, c
4 Installing Java
4.1 Goal
The goal of this chapter is to learn und understand how to install Java in order to
make your computer ready for an Incentage installation. You will understand
what is necessary to install Java, what main components belong to Java and
how you can test whether the Java installation was successful.
4.2 Overview
Incentage requires Java from Sun Microsystems. Make sure to
install a supported version to profit from Java optimizations and
bug fixes. Information about the newest release of Java can be
found on the internet on http://java.sun.com/j2se/.
4.3 Installation
Java has become a very popular platform and is widely
used. Therefore you should first see whether you already
have Java installed:
Open a Dos Prompt and type:
java.exe –version
If the result you get looks like this, you can skip the next steps and proceed
with the last point, the testing of the Java installation:
C:\>java -version
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.2_04-b02)
Java HotSpot(TM) Client VM (build 1.4.2_04-b02, mixed mode)
Note, that it is sufficient if the first three numbers match (1.4.2). The sub
release (04) is not relevant.
C:\>java –version
Now you should get the version information as shown in Listing 4-1.
5 Installing Incentage
5.1 Goal
This chapter guides you through the process of installing Incentage on a
Windows machine. The installation on UNIX machine is described in a separate
document.
5.2 Setup
Locate the file setup.jar on the CD.
On the first page (see Figure 11) of the Installer, the directory where Incentage
should be installed to, can be specified. Incentage does not rely on being
installed in a specific directory, so you are free in the choice of this directory.
Good practice is C:\incentage or C:\Program Files\incentage. Click "Next" to
start the installation.
Click "Next" after the installation has succeeded. Incentage is installed now;
you will configure it in the next section. Click "Launch ConfigurationManager" to
jump directly to the configuration.
5.3 Configuration
Before proceeding to starting the ManagementConsole the
new installation must be configured. If the Incentage
ConfigurationManager is not yet running (because it was not
launched from the final installation screen), start it now by
double-clicking ConfigMgr.bat in the directory where Incentage
was installed.
Chose the Java Virtual Machine Incentage should use. The default value is the
Java VM in your system path. If the instructions above to install Java were
followed, all default values of this page can safely be accepted. Click "Next".
Some libraries exist in more than one version. For example, MQ Series 5.3 needs
different drivers than version 5.2. Select the appropriate version or choose
"Default" if the version is unknown or the library is not used.
6.1 Goal
This chapter enables you to take over an Incentage environment, start it and
process a message.
Login with username admin and leave the password field empty.
Right-click on the monitor icon in the tree and choose [start]. The component
is started and the rules are loaded into the converter. All lights in the tree
should become green.
b and c
7 Further Exercises
7.1 Goal
This chapter contains further exercises to illustrate the processing of messages
with Incentage.
These exercises are optional and not required in order to proceed with the
training.
Open the file message.done with an editor. You will see the following
message:
SOM
999MessageType=MT1
Amount=13'400.30
Amount_Cur=EUR
Valuta=19.06.2002 10:43:22
EOM
Duplicate the message by marking the whole content of the file, copying it,
and pasting it to the end of the file. Now the content of the file should look as
follows:
SOM
999MessageType=MT1
Amount=13'400.30
Amount_Cur=EUR
Valuta=19.06.2002 10:43:22
EOM
SOM
999MessageType=MT1
Amount=13'400.30
Amount_Cur=EUR
Valuta=19.06.2002 10:43:22
EOM
Mark the file message.done. Press Ctrl+C to copy the file. Press Ctrl+V to
paste the file. Repeat pressing Ctrl+V until there are about ten copies of the
file.
To rename all the files to *.in, we use a batch file that allows to rename all the
files in one go.
Open the text document in the Editor and enter the following text:
Save the file, close the editor and rename the file to “rename.bat”.
Double-click on the file rename.bat. All files are renamed and the messages
are processed. Note the message count in the Management Console.