Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Designing: SWIFT Correlation Repository Sample
 

Classic Java CAPS

Developing Java CAPS Projects

Using SOAP Message Handlers

Creating a Runtime Environment

Designing Business Processes in the Sun Business Process Manager

Working with TCP/IP HL7 Collaborations

Developing Sun Master Indexes (Repository)

Developing Sun Master Patient Indexes

Developing OTDs for Application Adapters

Developing OTDs for Communication Adapters

Developing OTDs for Database Adapters

Developing OTDs for Web Server Adapters

Designing with Application Adapters

Designing with Communication Adapters

Designing with Web Server Adapters

SWIFT Integration Projects

Overview of SWIFT Message Libraries

2008 Library Features

Library Versions and Access

What's New in Java CAPS 6 Update 1

Installing the SWIFT Message Library

SWIFT OTD Library System Requirements

Installing the SWIFT OTD Libraries

Installing the eWay on a Java CAPS Supported System

Increasing the Heap Size

Increasing the heap size from the Enterprise Designer

Using the SWIFT OTD Library

SWIFT Message Type OTDs

SWIFT Message Structure

OTD and Collaboration Locations in Enterprise Designer

SWIFT Message Type Reference

Category 1 Messages

Category 2 Messages

Category 3 Messages

Category 4 Messages

Category 5 Messages

Category 6 Messages

Category 7 Messages

Category 8 Messages

Category 9 Messages

Validation Collaborations

SWIFT Generic Library

SWIFT Message Library JAR Files

Using Message Validation Features

Basic Validation Features

Library Methods

Message Validation Rules

Message Format Validation Rules (MFVR)

MFVR Validation Methods

MFVR Errors

In Collaboration Validation Methods

validate()

SWIFT Projects

Importing a Sample Project

SWIFT Projects and the Enterprise Designer

SWIFT Sample prjSwift_JCD_MFVROnly Project

SWIFT Sample prjSwift_JCD_MFVRAndBICPlusIBAN Project

SWIFT Sample prjSwift_JCD_BICPlusIBANOnly Project

SWIFT MX Validation Sample

SWIFT Correlation Repository Sample

SWIFT Sample eInsight™ Project

Using eGate With eInsight

Using a Business Process

Configuring the Modeling Elements

Creating a Connectivity Map

Binding the eWay Components

Creating an Environment

Configuring the eWays

Configuring the Integration Server

Creating the Deployment Profile

Creating and Starting the Domain

Building and Deploying the Project

Running the Sample

Updating BICDirService

Source of Information

BICDirService Method Operation

Updating BICPlusIBAN

BICPlusIBAN Validation Method Definitions

Error Message Information

Error Messages

Message Examples

Using SWIFT FIN-Based Funds OTDs

SWIFT OTD Library Funds Features

Using SWIFT OTD Library Java Classes

Relation to OTD Message Types

SWIFT OTD Library Javadoc

OTD Library Java Classes

Java EE Based Components

Designing with Sun JCA Adapters

About the TCP/IP JCA Adapter

Defining Constants and Variables

Using Database Operations

Developing Sun Master Indexes

Using the JMS JCA Wizard

Using the JAXB Wizard and Code-Seeder Pallete

SWIFT Correlation Repository Sample

The SWIFT Correlation Repository (SCR) is a Java CAPS utility used to visualize SWIFT workflows. In addition, the SCR:

Prerequisites

The following prerequisites are needed in order to run the SRC project:

Installation steps
  1. Ensure all prerequisites are installed.

  2. Install Hotfix 109645 for the Enterprise Designer.

  3. Install the database schema from the SCR_CreateUser.sql and SCR_CreateTable.sql files (located in the SCR_Create_Cleanup zip file).

  4. Extract the contents of the SampleSCR.zip file into your local drive.

  5. Import the SampleSCR.zip file into Enterprise Designer.

  6. Set the environment variables (as shown in the figure below).

    SCR Environment Variables
  7. Create a deployment profile in the SCR project.

  8. Create a deployment profile in the TesterGatekeeper project.

  9. Deploy both the SCR and TesterGatekeeper deployment profiles.

Preparing an SCR flow

The SCR Workflow follows the tasks, procedural steps, required input and output information, for each step in the business process. The SCR workflow is used to view, manage, and enforce the consistent handling of work. The following figure is an example of a design of an SCR flow.

SCR Flow Example
Designing an SCR flow
  1. Start the Enterprise Designer.

  2. Open the imported SCR project.

  3. Choose both a short name and a long name for the flow (example: t2 :: Target2).

  4. Choose a string name for each event / message / direction (as shown in the SCR flow example above: TO_SWIFT_INIT).

  5. Add the flow name as a new choice in the viewer by navigating to the Viewer on the SCR page, then to the 1TrxList, and then to the pgTrxList.

    1. On the Properties tab, select SelDomain.

    2. Right-click the highlighted area on the design canvas, and select Edit Options. The Edit Options window opens.

    3. Add new flow elements to the properties of the control SelDomain. This project already ahs defualted values entered (t2 :: Target2).

Linking the Domain Name and Direction to a Color

You can link the name of a Domain to specific pointer directions and colors within the monitoring application.

  1. Link the domain name and the direction to a color by opening the SCR.properties file located in c:\SampleSCR\properties.

  2. A list of available directions and colors are listed in the SCR properties file. Possible Colored Directions (CD) for message lists include:

    • DEFAULT

    • LGREY, RGREY

    • LBLUE, RBLUE

    • LGREEN, RGREEN

    • LORANGE, RORANGE

    • LRED, RRED

  3. Link the Domain to a specific pointer directin and color by using the following Syntax: CD_<Direction String> = <Colored Directions>.

Using the SCR for Monitoring Flows

Applications that send events to the SCR must do two things:

  1. Create a message following the input format shown below. Do not use the field whose usage is indicated as “Gatekeeper only”.

    SCR Message Input Format
  2. Send the message to either:

    • A file in the c:\SampleSCR\In location, with a .txt extension and a name starting with Loader.

    • A JMS message to the JMS queue, qSCRInEnv, in SCR/Loader.

Using the Viewer for Monitoring Transactions
  1. Use an Internet browser and navigate to the URL http://localhost:18001/scr. The Select Transaction window opens.

  2. Use one of the following criteria for monitoring transactions:

    • Select the 10 most recently updated transactions from the drop-down list.

    • Use the domain selector to restrict the transaction list.

    • Search for a transaction with a specific ID.

    • Search for a transaction that contains a message with a specific ID.

  3. Click the Search button.

Using the SCR as Gatekeeper

Applications sending events to the SCR as Gatekeeper must do two things:

  1. Create a message following the input format (as shown in the previous section)

  2. Send the message to the JMS queue “qGKeeperIn” in SCR/Gatekeeper. Make sure to add a JMS topic to the message. A code sample is shown below.

    com.stc.connectors.jms.Message outMsg = 
    jmsPublish.createTextMessage(); 
    outMsg.storeUserProperty( "SCRDestination", "DEST1" ); 
    outMsg.setTextMessage( input.getText() ); 
    jmsPublish.send( outMsg );
  3. Subscribe to the JMS queue ”qGKeeperOut” in SCR/Gatekeeper.

  4. Subscribe to the JMS topic that you used to publish the message.

Note - A complete test setup is located in the project TesterGatekeeper.

Tester Gatekeeper Conn Map
Using the Viewer to Repair Messages
  1. Use an Internet browser and navigate to the URL http://localhost:18001/scr. The Select Transaction window opens.

  2. Select the 10 most recently updated transactions from the drop-down list. Messages that have been held for review and resubmittion (e.g. messages that are duplicates, incorrect, or awaiting approval) are displayed.

  3. Select the message you wish to examine and click the Repair button. The Message Repair window opens, displaying detailed information regarding the message.

  4. You can resolve the message in the following ways:

    • Correct the message error and click the Resubmit button.

    • Examine a message that requires approval and click the Approve button.

    • Delete the message by clicking the Delete button