TIBCO ActiveMatrix Adapter for SWIFTNet Examples · TIBCO ActiveMatrix ® Adapter for SWIFTNet...

TIBCO ActiveMatrix® Adapter for SWIFTNet

ExamplesSoftware Release 5.11 August 2013

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, Two-Second Advantage, TIBCO, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO ActiveEnterprise, TIBCO Rendezvous, TIBCO Designer, TIBCO Administrator, TIBCO Adapter SDK, TIBCO Runtime Agent, TIBCO ActiveMatrix Adapter, TIBCO ActiveMatrix Adapter for MQSeries, TIBCO Enterprise Message Service, and TIBCO Hawk are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1998-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

TIBCO ActiveMatrix Adapter for SWIFTNet Examples

| iii

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiTIBCO Adapter for SWIFT Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiiOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1 Introduction to Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Prerequisites for Running the Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Examples Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2 Real Time Client Server Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Example Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Sending a RT Request Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Real Time Server Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Setting Up the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Deploying and Running the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3 Store-and-Forward Client Server Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Example Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14DelNotif Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Sending a Request Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14SnF Server Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Setting Up the Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Deploying and Running the Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Expected Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23


iv | Contents


Figures | v

Figures

Figure 1 Sending a RT Request Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Figure 2 Real Time Server Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Figure 3 Log In to SWIFT Alliance WebStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Figure 4 System Module in the SWIFT Alliance WebStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Figure 5 Modifying the DN in the Responder Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 6 Specifying the RTClient Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Figure 7 Specifying the RTServer Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Figure 8 Specify the Fields in the Run Settings Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 9 DelNotif Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Figure 10 Sending a Request Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 11 The SnF Server Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 12 Specifying the Values of DelNotif Instance in the SWIFTNet Connection Tab . . . . . . . . . . . . . . . . 18

Figure 13 Specify the Values of SnFServer Instance in the SWIFTNet Connection Tab. . . . . . . . . . . . . . . . . 18

Figure 14 Specify the Values of SnFClient Instance in the SWIFTNet Connection Tab . . . . . . . . . . . . . . . . . 19

Figure 15 Output of the DelNotifications from Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Figure 16 Output of the Send Request to Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21


vi | Figures


| vii

Preface

This guide contains examples to further your understanding of TIBCO ActiveMatrix Adapter for SWIFTNet. The preface lists important requirements and conventions.

Topics

• Related Documentation, page viii

• Typographical Conventions, page ix

• Connecting with TIBCO Resources, page xii


viii | Related Documentation

Related Documentation

This section lists documentation resources.

TIBCO Adapter for SWIFT DocumentationThe following documents form the TIBCO ActiveMatrix Adapter for SWIFTNet documentation set.

• TIBCO ActiveMatrix Adapter for SWIFT Installation Read this manual for instructions on site preparation and installation.

• TIBCO ActiveMatrix Adapter for SWIFTNet User’s Guide Read this manual for the concepts relating to the adapter, the applications with which the adapter interacts, configuration and deployment information.

• TIBCO ActiveMatrix Adapter for SWIFTNet Examples Guide Read this manual to work through the examples provided with the adapter.

• TIBCO ActiveMatrix Adapter for SWIFT Release Notes Read this release notes for a list of new and changed features. This document also contains lists of closed and known issues (in both the SWIFTNet and SWIFTNet - FIN Adapter components) for this release.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO ActiveEnterprise™

• TIBCO ActiveMatrix Adapter™ for MQSeries

• TIBCO ActiveMatrix BusinessWorks™

• TIBCO® Adapter SDK

• TIBCO Administrator™

• TIBCO Designer™

• TIBCO Enterprise Message Service™

• TIBCO Hawk®

• TIBCO Rendezvous®

• TIBCO Runtime Agent™


Preface | ix

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_NAME

TIB_ADSWIFT_HOME

CONFIG_HOME

TIBCO products are installed into an installation environment. A product installed into an installation environment does not access components in other installation environments. Incompatible products and multiple instances of the same product must be installed into different installation environments.

An installation environment consists of the following properties:

• Name Identifies the installation environment. This name is referenced in documentation as ENV_NAME. On Microsoft Windows, the name is appended to the name of Windows services created by the installer and is a component of the path to the product shortcut in the Windows Start > All Programs menu.

• Path The directory into which the product is installed. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

TIBCO ActiveMatrix Adapter for SWIFTNet - FIN is installed into a directory within TIBCO_HOME. This directory is referenced in documentation as TIB_ADSWIFT_HOME. The default value of TIBCO_ADSWIFT_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco\adapter\adswift\version.

A TIBCO configuration directory stores configuration data generated by TIBCO products. Configuration data can include sample scripts, session data, configured binaries, logs, and so on. This directory is referenced in documentation as CONFIG_HOME. The default location of the directory is USER_HOME\ENV_NAME\tibco\cfgmgmt\product_name. For example, on Windows, the default location is C:\Documents and Settings\username\Application Data\ENV_NAME\tibco\cfgmgmt\product_name.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.


x | Typographical Conventions

bold code font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts.

• To introduce new terms. For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


Preface | xi

Table 2 Syntax Typographical Conventions

Convention Use

[ ] An optional item in a command or code syntax.

For example:

MyCommand [optional_parameter] required_parameter

| A logical OR that separates multiple items of which only one may be chosen.

For example, you can select only one of the following parameters:

MyCommand param1 | param2 | param3

{ } A logical group of items in a command. Other syntax notations may appear within each logical group.

For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4.

MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4:

MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4.

MyCommand param1 [param2] {param3 | param4}


xii | Connecting with TIBCO Resources

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a username and password. If you do not have a username, you can request one.

http://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

http://www.tibcommunity.com


| 1

Chapter 1 Introduction to Examples

This chapter lists the prerequisites needed to run the examples.

Topics

• Prerequisites for Running the Examples, page 2


2 | Chapter 1 Introduction to Examples

Prerequisites for Running the Examples

The following software must be installed to run the examples:

• TIBCO Administrator™

• TIBCO ActiveMatrix® Adapter for SWIFT

• TIBCO ActiveMatrix BusinessWorks™

• TIBCO Enterprise Message Service™ (if JMS transport is used)

• TIBCO Runtime Agent™

The TIBCO ActiveMatrix BusinessWorks examples use TIBCO Designer to create an Enterprise Archive file (EAR) and TIBCO Administrator to deploy the EAR file.

In TIBCO Administrator, make sure that all software components needed by the adapter instance are installed on one or more machines that are part of a TIBCO administration domain and that the software is registered in the domain.

• Use the TIBCO Domain Utility to add a machine to a TIBCO Administration Domain.

• In TIBCO Administrator, use the Resource Management > Machines console to register software.

These topics are explained in the TIBCO Administrator documentation set.

Examples Location The files for the examples along with the sample messages are in the following location:

TIB_ADSWIFT_HOME\examples\SWIFTNetAdapter\Business Scenario.


| 3

Chapter 2 Real Time Client Server Example

This example demonstrates functionalities of the adapter in Real Time.

Topics

• Example Description, page 4

• Setting Up the Example, page 6

• Deploying and Running the Example, page 11

• Expected Results, page 12


4 | Chapter 2 Real Time Client Server Example

Example Description

This example shows how the adapter works in Interact Real Time Messaging.

Sending a RT Request ProcessThe RTClient service has been defined in the SWIFTNetAdapterConfiguration instance for this process. It is a Request-response service configured for Real Time.

Figure 1 Sending a RT Request Process

Reading a Request from File

Reads a message from the sampleRTrequest.txt file and sends it to the Send Request to Adapter activity.

The schemas are defined automatically. A send operation is configured for the activity in the Configuration tab automatically.

Sending the Request to the Adapter

This activity invokes the adapter Request-response service, RTClient. The service sends a message to SWIFT Alliance Gateway (SAG).

The application builds a message of a Real Time service in TIBCO ActiveMatrix BusinessWorks and provides this message as input to the Send Request to Adapter activity.

The adapter receives an invoke request from the application. The adapter then sends it to SAG, and SAG sends it to the Receiver. The Receiver sends a response to SAG, and the adapter gets the response from SAG and processes it. The payload field in the request is published to the application.


Example Description | 5

Real Time Server ProcessThe RTServer service has been defined in the SWIFTNetAdapterConfiguration instance for this process. It is a Request-response Invocation (RRI) service configured for Real Time.

Figure 2 Real Time Server Process

Requests from SWIFTNet Adapter

The requests from SWIFTNet Adapter activity receives server requests coming from SAG to the RTServer service. It invokes the RTServer service defined in the SWIFTNetAdapterConfiguration instance.

The schemas are defined automatically. A Receive operation is configured for the activity in the Configuration tab automatically.

Reading the Response from File

The adapter processes the request in TIBCO ActiveMatrix BusinessWorks and generates a response. The Read Response From File activity writes the response to a file named sampleRTresponse.txt.

Sending the Response

The Send Response activity publishes the values in the payload field along with other details.

The adapter receives the response and sends it back to SAG, then SAG sends the response to other parties.



Setting Up the Example

Before deploying and running the example, you need to do the following tasks to set it up:

• Task A Starting SWIFT Alliance Gateway (SAG), page 6

• Task B Importing the Project Files, page 7

• Task C Specifying the Remote API (RA) Configuration File Details, page 8

• Task D Setting the Location of the Sample Message Files, page 8

• Task E Modifying the Configuration Details, page 8

Task A Starting SWIFT Alliance Gateway (SAG)

Before running the example, you must have the SAG and other related SWIFTNet software installed on the machine.

To start SAG, do the following steps:

1. Start SWIFT Alliance WebStation, and input the username and the password to log in.

Figure 3 Log In to SWIFT Alliance WebStation

2. Click the Start the Alliance Gateway button from the Menu to start SAG. The status dialog appears.


Setting Up the Example | 7

Figure 4 System Module in the SWIFT Alliance WebStation

Task B Importing the Project Files

Before starting the example, you must import the sample project ZIP file and save it in a new project.

In TIBCO Designer:

1. Create a directory to store the project: c:\tibco\projects.

2. Start TIBCO Designer, then click the New Empty Project button. The Save Project dialog appears.

3. In the Save Project dialog, click the Browse button and navigate to the project directory you created and specify a name for the project, then click the OK button.

4. Select Project > Import Full Project from the Menu, then click the ZIP Archive tab. Click the Browse button, and navigate to TIBCO_ADSWIFT_HOME/examples/SWIFTNetAdapter/RTClientServer directory, then select the ZIP file you want to import. In this example, select RTClientServer. Click the OK button.

5. In the Import-Options dialog, select the Replace Existing Global Variables With Those In Import and Overwrite On Name Conflict radio buttons. Then click the Apply button.



Task C Specifying the Remote API (RA) Configuration File Details

A RA configuration file needs to be specified with the following minimum details:

HostName = IP address of the host on which SAG is running

PortNumber = Port number on which SAG is running

A sample file, ra_config.properties, is available in the TIBCO_ADSWIFT_HOME\examples\SWIFTNetAdapter\RTClientServer\config directory. You can copy this file and modify the HostName and PortNumber entries.

After you modify the file, make sure:

• The SWNET_CFG_PATH environment variable points to the location of the RA configuration file.

• The same file name is specified in the RA Config File Name field of the Configuration tab of the SWIFTNetAdapterConfiguration instance.

Task D Setting the Location of the Sample Message Files

Two message files, sampleRTrequest.txt and sampleRTresponse.txt, are shipped along with this example. Set the value of the global variable MsgFileLocation to the location of these message files:

TIBCO_ADSWIFT_HOME\examples\SWIFTNetAdapter\RTClientServer\

MsgFiles.

Task E Modifying the Configuration Details

Most of the example settings are pre-configured. However, you need to modify the following settings:

• In the Project panel, click the Send RT Request icon, and select the Send Request to Adapter icon in the Design panel. Click the Input tab, and expand aeRequestInputType > _caruet_request_caret..., and then modify the DN in the Responder field based on your settings. See Figure 5.



Figure 5 Modifying the DN in the Responder Field

• In the Project panel, select SWIFTNetAdapterConfiguration > Adapter Services > RTClient, specify the values in the SWIFTNet Connection tab depending on the service you have configured. See Figure 6.

Figure 6 Specifying the RTClient Values



It is recommended that you configure the values shown as below:

— Message Partner Name: interact_client

— Certificate Name: SO1

— Service Name: swift.generic.ia!x

• In the Project panel, select SWIFTNetAdapterConfiguration > Adapter Services > RTServer, specify the values in the SWIFTNet Connection tab depending on the service you have configured. See Figure 7.

Figure 7 Specifying the RTServer Values

It is recommended that you configure the values shown as below:

— Message Partner Name: interact_server

— Certificate Name: SO1


Deploying and Running the Example | 11

Deploying and Running the Example

Perform the following steps to deploy and run the example.

1. Make sure that SWIFT Alliance Gateway is running.

2. In TIBCO Designer, select Tools > Show Adapter Tester from the Menu. The Adapter Tester dialog appears.

3. Click the SWIFTNetAdapterConfiguration icon, use the default values or specify the new values for the Working Directory and the Adapter Executable fields in the Run Settings tab.

4. Click the Start button.

Figure 8 Specify the Fields in the Run Settings Tab

5. In the Tester panel, click the Start Testing Viewed Process button , then check the Send RT Request and the RealTime Server checkboxes, and click the Load Selected button.

6. Right-click the Send RT Request.process item, then click the Create A Job item from the menu that appears. Click the job icon, the RealTime Server process gets triggered. The process will respond with a dummy payload from the file, and the Send RT Request process will get the response payload.



Expected Results

When the Send RT Request process gets the dummy response payload, the example run successfully.


| 13

Chapter 3 Store-and-Forward Client Server Example

This example demonstrates functionalities of the adapter in Store-and-Forward.

Topics

• Example Description, page 14

• Setting Up the Example, page 16

• Deploying and Running the Example, page 20

• Expected Results, page 21


14 | Chapter 3 Store-and-Forward Client Server Example

Example Description

This example shows how the adapter works in Interact Store-and-Forward Messaging.

DelNotif ProcessThis process invokes the DelNotif service. A NotifyDelivery operation is configured for the activity in the Configuration tab automatically.

Figure 9 DelNotif Process

Sending a Request Process

Reading a SnF Request from the File

Reads a message from the camt.008.002.02_sample.txt sample file provided.

Sending the Request to the Adapter

This process invokes the SnFClient service. A Send operation is configured for the activity in the Configuration tab automatically.


Example Description | 15

Figure 10 Sending a Request Process

SnF Server Process

Request from the Adapter

Receives the delivery notification details for the above Request-response Invocation service (SnFClient). A Receive operation is configured for the activity in the Configuration tab automatically.

When the adapter receives a delivery notification from SWIFT Alliance Gateway (SAG) that is sent by the SWIFTNet central SnF system, the adapter processes it and publishes the SwiftRef and AcceptStatus along with other details to TIBCO environment.

Writing the Response in a File

Writes the message received to the ServerRequests.txt file.

Sending the Response to the Adapter

Sends the response status as Accepted or Rejected back to the adapter. If the status is Rejected, then the reason for rejection is also provided.

Figure 11 The SnF Server Process



Setting Up the Example

Before deploying and running the example, you need to do the following tasks:

• Task A Starting SWIFT Alliance Gateway (SAG), page 16

• Task B Importing the Project Files, page 16

• Task C Specifying the Remote API (RA) Configuration File Details, page 16

• Task D Setting the Location of the Sample Message Files, page 17

• Task E Modifying the Configuration Details, page 17

Task A Starting SWIFT Alliance Gateway (SAG)

See Task A Starting SWIFT Alliance Gateway (SAG), page 6 for details.

Task B Importing the Project Files

Before starting the example, you must import the sample project ZIP file and save it in a new project.

In TIBCO Designer:

1. Create a directory to store the project: c:\tibco\projects.

2. Start TIBCO Designer, then click the New Empty Project button. The Save Project dialog appears.

3. In the Save Project dialog, click the Browse button and navigate to the project directory you created and specify a name for the project. Then click the OK button.

4. Select Project > Import Full Project from the Menu, then click the ZIP Archive tab. Click the Browse button, and navigate to TIBCO_ADSWIF_HOME/examples/SWIFTNetAdapter/SnFClientServer directory, then select the ZIP file you want to import. In this example, select SnFClientServer. Click the OK button.

5. In the Import-Options dialog, select the Replace Existing Global Variables With Those In Import and Overwrite On Name Conflict radio buttons. Then click the Apply button.

Task C Specifying the Remote API (RA) Configuration File Details

A RA configuration file needs to be specified with the following minimum details:



HostName = IP address of the host on which SAG is running

PortNumber = Port number on which SAG is running

A sample file, ra_config.properties, is available in the TIBCO_ADSWIFT_HOME\examples\SWIFTNetAdapter\SnFClientServer\ config directory. You can copy this file and modify the HostName and PortNumber entries.

After you modify the file, make sure:

• The SWNET_CFG_PATH environment variable points to the location of the RA configuration file.

• The same file name is specified in the RA Config File Name field of the Configuration tab of the SWIFTNetAdapterConfiguration instance.

Task D Setting the Location of the Sample Message Files

Two message files, camt.008.002.02_sample.txt and ServerRequests.txt, are shipped along with this example. Set the value of the global variable MsgFileLocation to the location of these message files: TIBCO_ADSWIFT_HOME\examples\SWIFTNetAdapter\SnFClientServer\ MsgFiles.

Task E Modifying the Configuration Details

Most of the example settings are pre-configured. However, you need to modify the following settings:

• In the Project panel, click the Send RT Request icon, then select the Send Request to Adapter icon in the Design panel. Click the Input tab, then expand aeRequestInputType > _caret_request_caret..., then modify the DN in the Responder field based on your settings. See Figure 5.

• In the Project panel, select SWIFTNetAdapterConfiguration > Adapter Services > DelNotif, specify the values in the SWIFTNet Connection tab depending on the service you have configured. For example, the name in the Receiver Queue field is provided by SWIFT and may differ from customer to customer. It is recommended that you configure the values as shown below:

Ensure that you have the corresponding XSD schema for the message type present in the gateway\data directory of the SAG instance.



Figure 12 Specifying the Values of DelNotif Instance in the SWIFTNet Connection Tab

• In the Project panel, select SWIFTNetAdapterConfiguration > Adapter Services > SnFServer, specify the value in the SWIFTNet Connection tab depending on the service you have configured. For example, the name in the Receiver Queue field is provided by SWIFT and may differ from customer to customer. It is recommended that you configure the values as shown below:

Figure 13 Specify the Values of SnFServer Instance in the SWIFTNet Connection Tab



• In the Project panel, select SWIFTNetAdapterConfiguration > Adapter Services > SnFClient, specify the values in the SWIFTNet Connection tab depending on the service you have configured. For example, the name in the Receiver Queue field is provided by SWIFT and may differ from customer to customer. It is recommend that you configure a service of type Server as shown below:

Figure 14 Specify the Values of SnFClient Instance in the SWIFTNet Connection Tab



Deploying and Running the Example

Perform the following steps to deploy and run the example.

1. Make sure that SWIFT Alliance Gateway is running.

2. In TIBCO Designer, select Tools > Show Adapter Tester from the Menu. The Adapter Tester dialog appears.

3. Click the SWIFTNetAdapterConfiguration icon, use the default values or specify the new values for the Working Directory and the Adapter Executable fields in the Run Settings tab.

4. Click the Start button. See Figure 8.

5. In the Tester panel, click the Start Testing Viewed Process button , then check the DelNotif, Send Request, and SnF Server checkboxes, then click the Load Selected button.

6. Right-click the Send Request.process item, then click the Create A Job item from the menu that appears. Click the job icon, the SnF Server process gets triggered. The process will respond with a dummy payload from the file, and the Send Request process will get the response payload.


Expected Results | 21

Expected Results

To make sure the delivery notification for the message that was initially sent, the value of the SwiftReference field in the Output tab for the DelNotifications from Server instance and the Send Request to Adapter instance must match, and the value of the Status field in the Output tab for the Send Request to Adapter of the Send Request instance must be Success.

Figure 15 Output of the DelNotifications from Server

Figure 16 Output of the Send Request to Adapter




| 23

Index

C

CONFIG_HOME ixconventions used in this manual xiicustomer support xii

D

DelNotif process 14deploy and run the example 11, 20

E

ENV_NAM ixexample description 4, 14expected results 12, 21

I

importing the project files 7, 16

L

location 2

M

modifying the configuration details 8, 17

P

prerequisites for running the examples 2

R

read response from file 5reading the request from file 4reading the response from file 5reading the SnF request from the file 15real time client server example 3real time server process 5request from the adapter 16requests from SWIFTNet adapter 5

S

sending the request process 14sending the request to the adapter 4, 14sending the response 5sending the response to the adapter 15sending the RT request process 4set up the example 6, 16setting the location of the sample message files 8, 17SnF server process 15specifying the remote API (RA) configuration file

details 8, 8, 8, 16starting SWIFT Alliance Gateway (SAG) 6, 16, 16, 16,

17, 17store-and-forward client server example 13support, contacting xii


24 | Index

T

technical support xiiTIB_ADSWIFT_HOME ixTIBCO_HOME ixtypographical conventions ix

U

using TIBCO ActiveMatrix BusinessWorks 2Using TIBCO IntegrationManager 2

W

writing the response in the file 15

Date post:	30-Jul-2018
Category:	Documents
Upload:	trantruc
View:	223 times
Download:	0 times