Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Designing: Creating a Connectivity Map
 

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

Creating a Connectivity Map

The Enterprise Designer’s Connectivity Map Editor provides a canvas for assembling and configuring a Project’s components. Connectivity Maps are used with both Java Collaboration (JCD) and eInsight (BP) Project implementations. The following sample demonstrates how the prjSwift_BP_Sample is created.

  1. From the Enterprise Designer’s Project Explorer, right-click the prjSwift_BP_Sample Project and select New > Connectivity Map from the shortcut menu.

  2. The New Connectivity Map appears and a node for the Connectivity Map is added under the Project on the Project Explorer tree labeled CMap1. Rename the Connectivity Map cmSwift_BP.

Selecting the External Applications

In the Connectivity Map, the eWays are associated with External Systems. For example, to establish a connection to an external file, you must first select File as an External System to use in your Connectivity Map (see Figure 6).

Figure 6 Connectivity Map - External Applications
Conn Map — External Applications
  1. Click the External Application icon on the Connectivity Map toolbar,

  2. Select the external systems necessary to create your Project (for this sample, File. Icons representing the selected external systems are added to the Connectivity Map toolbar.

Populating the Connectivity Map

The icons in the toolbar represent the available components used to populate the Connectivity Map canvas. Add the Project components to the Connectivity Map by dragging the icons from the toolbar to the canvas.

  1. For this sample, drag the following components onto the Connectivity Map canvas as displayed in Populating the Connectivity Map:

  2. File External System (2)

  3. Service (A service is a container for Collaborations, Business Processes, eTL processes, and so forth)

    Conn Map with Components
  4. Rename the File1 External Application to eaFileIn by right-clicking the object, selecting Rename from the shortcut menu, and typing in the new name. In the same way, rename the other Connectivity Map components as follows:

  5. File2 to eaFileOut

  6. cm_Swift_BP_Service1 to BusinessProcess1.

  7. Save your current changes to the Repository.