MxMLExchange Tasks

Installation

Version

Date

Reference

Author

V1

26/04/2004

MxMLExchangeTasksInstallation.doc

Murex Integration Team

Table of Contents

Introduction

Integration.jar Installation

2.1
2.2
2.3
2.4

1
1
1
1

fs/public/code/jar Directory
fs/public/download/services.mxres File (First Installation Only)
fs/public/download/guiclient.mxres File (First Installation Only)
fs/public/mxres/mxmlexchange/client/gui/mxmlexguimonitor.mxres

Definition of a New Task Type in the Palette

1 INTRODUCTION
In order to install a new task, two steps have to be performed:

Make the binary components (packaged in the JAR file integration.jar)

available.

Add a new type in the MxMLExchange palette.

If integration.jar was already installed on the environment, it just need to be

updated, and the necessary packages have to be defined in the
fs/public/mxres/mxmlexchange/client/gui/mxmlexguimonitor.mxres file (see
below).

2 INTEGRATION.JAR INSTALLATION
2.1 fs/public/code/jar Directory
The integration jar file has to be copied or updated under the fs/public/code/jar
directory. The files detailed below must be updated before restarting all the
services.

2.2 fs/public/download/services.mxres File (First Installation Only)

Add under the tag
<MxAnchor Code="SERVICE">

the following line:

<File Check="Y">public/code/jar/integration.jar</File>

to identify the path to the integration.jar file.

2.3 fs/public/download/guiclient.mxres File (First Installation Only)

Add under the tag
<MxAnchor Code="GUICLIENT">

the following line:

<File Check="Y">public/code/jar/integration.jar</File>

2.4 fs/public/mxres/mxmlexchange/client/gui/mxmlexguimonitor.mxres
This is the file were the Java names of the licensed tasks are set. If it is the first
installation of integration.jar, the following structure is added:
<Location>
<JarFile>integration.jar</JarFile>
<Packages>
</Packages>
</Location>

under the tag

<MxAnchor Code="Locations">

Copyright Murex

26/04/2004

2 MxMLExchange Tasks Installation

The following two lines have then to be added for each new task installed (where
packageName was provided along with the shipping):
<Package>murex.integration.datalayer.flow.task.exg.server.packageName</Package>
<Package>murex.integration.datalayer.flow.task.exg.gui.packageName</Package>

For example, for the ImportJMS task, whose package name is importjms:
<Location>
<JarFile>integration.jar</JarFile>
<Packages>

<Package>murex.integration.datalayer.flow.task.exg.server.importjms</Package>
<Package>murex.integration.datalayer.flow.task.exg.gui.importjms</Package>

</Packages>
</Location>

3 DEFINITION OF A NEW TASK TYPE IN THE PALETTE

First, choose a category:

Event Capture: connectivity tasks (Import, Export, Gateway tasks)

DocManager: confirmations and payments management.

Then, start task creation wizard by clicking on the Add Type button:
And set the following values, in the successive screens:
1. taskName as name (e.g. ImportJMS) and a suitable icon
2. Automatic
3. Yes
4. XMLFlow launcher
5. Choose the server component taskName in the related package (e.g.
ImportJMS in murex.integration.datalayer.flow.task.exg.server.importjms).
Please note that the list of the packages is the one set in the
mxmlexguimonitor.mxres file:

Copyright Murex

26/04/2004

Definition of a New Task Type in the Palette 3

6. Internal
7. Java
8. Choose the GUI component <taskName>Config in the related package (e.g.
ImportJMSConfig in murex.integration.datalayer.flow.task.exg.gui.importjms)

9. Default
Copyright Murex

26/04/2004

4 MxMLExchange Tasks Installation

10. The installation is now completed. A new icon will appear in the palette, and
you can now drag and drop it into the flow sheet in order to create a new
instance of the task. You will configure it accordingly to its specific
documentation.

Copyright Murex

26/04/2004