fix sample package guide

8/12/2019 Fix Sample Package Guide

http://slidepdf.com/reader/full/fix-sample-package-guide 1/9

1

webMethods FIX Module 7.2 FCS

Sample Package User’s Guide

About webMethods FIX Module Sample Package

The WmFIXSample package provides samples that illustrate how to use webMethodsFIX Module. Using two Integration Servers, the samples allow you to simulate sendingand receiving messages between two partners and demonstrate the usage of IntegrationServer document types for processing incoming FIX messages. The samples include thefollowing:

Sample Trading Networks configuration items, including sender and receiverprofiles, a document type that corresponds to the FIX message types included withthe sample, and a processing rule for processing incoming messages.

Sample FIX Module services to demonstrate sending FIX messages. The sampleincludes an “Execution Report” message type for both FIX version 4.4 and FIX 5.0, as

well as an encoded “Execution Report” message type for FIX version 4.4.

A sample FIX Module service to demonstrate the processing of a received FIX(version 4.4) message and a sample Integration Server document type that maps toExecution Report FIX messages.

The following diagram illustrates a high-level configuration for using the WmFIXSamplepackage.

WmFIXSample Package Configuration



webMethods FIX Modu le 7.2 FCS Sample Package User’s Guide

2

Before You Begin

Important! FIX Module samples only demonstrate the features of the module and must not be used in the production environment. You must delete the WmFIXSample package before you go into production.

The information in this guide assumes that you are familiar with Integration Server,Trading Networks, and Designer. Before installing the sample package, complete thefollowing tasks:

Install two Integration Servers on different machines so that one can serve as theseller (sender) and the other as the buyer (receiver). You cannot run the entire samplepackage on a single computer where two Integration Servers are installed. Forinformation about installing Integration Server, see the webMethods InstallationGuide that corresponds to your release.

Install webMethods FIX Module 7.2 and all its dependent components on eachIntegration Server. For information about installing webMethods FIX Module, see

webMethods FIX Module Installation and User’s Guide. Install My webMethods and MywebMethods Server on each Integration Server. For more information, see thewebMethods Installation Guide that corresponds to your release.

Sett ing up Seller and Buyer (Sender and Receiver)

The following diagram illustrates the high-level steps for setting up the seller (sender)and buyer (receiver). You will execute these steps once to set up the sender and once toset up the receiver.

For instructions, see “Set Up a Sample Seller (Sender)” on page 3 and “Set Up a Sample

Buyer (Receiver)” on page 5.




3

WmFIXSample Package Configuration Steps

Set Up a Sample Seller (Sender)

To use the packages to simulate sending messages, on one Integration Server, define theFIX engine connection for the seller by executing the following tasks:

Define the seller’s connection to the FIX engine and the corresponding values for thelocal_firm_id and the remote_firm_id (as described below). FIX Module uses thevalues of the local_firm_id and the remote_firm_id to distinguish the seller (sender)from the buyer (receiver). The values you use to define the seller will be reversedwhen you define the buyer’s connection information.

Set up the seller’s enterprise profile.

Import the document types and buyer’s partner profile into Trading Networks.

The remainder of this section explains how to complete these tasks.

Step 1: Define the Seller’s (Sender’s) Connect ion

Define the connection to the FIX engine as the seller by specifying the following values inthe seller’s Appia.ini configuration file.

Define the connection = “SELLER”




4

Define the value of the local_firm_id = COMP2

Define the value of the remote_firm_id = COMP1

The configuration file should resemble the following:

[MAIN]

….

connection = [SELLER]

….

[SELLER]

local_firm_id = COMP2

remote_firm_id = COMP1

….

Step 2: Set Up the Seller’s (Sender ’s) Enterprise Profile

The enterprise profile must have a FIX_ID that matches the value of the local_firm_id

defined in the seller ’s Appia.ini configuration file.

To set up the seller’s enterprise profile

1 In My webMethods, create the seller’s enterprise profile using the instructions fordefining and managing profiles as described in the Trading Networks user’s guidethat corresponds to your release.

2 Define the value of the External ID Type , FIX_ID = “COMP2”

Step 3: Import the Document Type and Buyer’s Trading Profi le into

Trading Networks

The WmFIXSample package includes the following items relating to the buyer’s(receiver’s) side of the message transaction:

Trading partner profile named “BUYER”

Trading Networks document type “FIX Execution Report.” This corresponds to themessage type that is also included in the package.

To impor t these items from the sample package into Trading Networks

1 In My webMethods, select Administ rat ion > In tegrat ion > B2B > Asset Management .

2 In the Upload File Group box, click Choose file.

3 Open the file IntegrationServer_directory/packages/WmFIXSample/data/Buyer_TN_Import.

4 Click Extract Assets.




5

Step 4: Ensure the Sender’s FIX Module is Configured wi th the Appia

Engine

To ensure the sender’s FIX Module is configured with Appia connection details, performthe following:

1 At the Appia engine, run the middleware_stats command. This displays a list ofconnections.

2 Ensure there is a connection listed for each of the sessions you configured in FIXModule.

Using Services for Sending

The following sample services illustrate how to send “Execution Report” type FIXmessages:

sendExecutionReport44 sends FIX version 4.4 messages

sendExecutionReport44_encodedField sends encoded FIX version 4.4 messages

sendExecutionReport50 sends FIX version 5.0 messages

For more information about send services, see “WmFIXSample Package Services” onpage 7.

Set Up a Sample Buyer (Receiver)

To use the packages to simulate receiving messages-Monica on a different Integration

Server from where you defined your seller (sender) information, define the FIX engineconnection for the buyer (receiver) by executing the following tasks:

Define the connection to the FIX engine and the corresponding values for thelocal_firm_id and the remote_firm_id (as described below). FIX Module uses thevalues defined for the local_firm_id and the remote_firm_id to distinguish the seller(sender) from the buyer (receiver). To define the buyer, reverse the values of thelocal_firm_id and the remote_firm_id from the values you previously defined forthe sender.

Set up the buyer’s enterprise profile.

Import the document type and seller’s partner profile into Trading Networks.

Step 1: Define the Buyer’s (Receiver’s) Connection

Define the connection to the FIX engine as the buyer by specifying the following values inthe buyer’s Appia.ini configuration file:

Define the connection = “BUYER”

Define the value of the local_firm_id = COMP1




6

Define the value of the remote_firm_id = COMP2

The configuration file should resemble the following:

[MAIN]

….

connection = [BUYER]

….

[BUYER]

local_firm_id = COMP1

remote_firm_id = COMP2

….

Step 2: Set Up the Buyer’s (Receiver’s) Enterprise Profile

The enterprise profile must have a FIX_ID that matches the value of the local_firm_id

defined in the buyer’s Appia.ini configuration file.

To set up the buyer’s enterprise profile

1 In My webMethods, create the buyer’s enterprise profile using the instructions fordefining and managing profiles as described in the Trading Networks user’s guidethat corresponds to your release.

2 Define the value of the External ID Type , FIX_ID = “COMP1”

Step 3: Import the Document Types and Profiles into Trading

Networks

TheWmFIXSample package includes the following items relating to the seller’s side of themessage transaction:

Trading partner profile named “SELLER”

Trading Networks document type “FIX Execution Report”

A processing rule named “ReceiveExecutionReport44.” This processing rule saves“ExecutionReport44” FIX messages to the Integration Server document formatpipeline directory in IntegrationServer_directory/pipeline.

To impor t these items from t he sample package into Trading Networks

1 In My webMethods, select Administ rat ion > In tegrat ion > B2B > Asset Management .

2 In the Upload File Group box, click Choose file.

3 Open the file IntegrationServer_directory/packages/WmFIXSample/data/Seller_TN_Import.

4 Click Extract Assets.




7

Step 4: Ensure the Buyer’s FIX Module is Configured wi th the Appia

Engine

To ensure the sender’s FIX Module is configured with Appia connection details, performthe following:

1 At the Appia engine, run the middleware_stats command. This displays a list ofconnections.

2 Ensure there is a connection listed for each of the sessions you configured in FIXModule.

Services Used for Receiving

When FIX Module receives a FIX message type of “Execution Report,” the processingrule invokes the receiveExecutionReport44service.

For more information, see “WmFIXSample Package Services” on page 7.

WmFIXSample Package Services

TheWmFIXSample package contains services to simulate sending and receivingmessages to help you with configuring FIX Module. This section describes the sampleservices in the WmFIXSample package.

wm.fix.sample.outbound:sendExecutionReport44

Sends a FIX message of type Execution Report, version 4.4, to the Appia engine using thesession "SELLER". After this service is executed the FIX message is persisted in TradingNetworks and sent to the Appia engine. To send an encoded FIX message, usesendExecutionReport44_encodedField.

Input Parameters

None.

Output Parameters

None.




8


_encodedField

Sends an encoded FIX message of type Execution Report, version 4.4, to the Appia engine

using the session "SELLER". After this service is executed the FIX message is persisted inTrading Networks and sent to the Appia engine. This service provides a layer of securitywhen sending FIX messages. To send a non-encoded FIX message, usesendExecutionReport44.

Input Parameters

None.

Output Parameters

None.


Sends a FIX message of type Execution Report, version 5.0, to the Appia engine using thesession "SELLER". After this service is executed the FIX message is persisted in TradingNetworks and sent to the Appia engine.

Input Parameters

None.

Output Parameters

None.

wm.fix.sample.inbound:receiveExecutionReport44

Converts the FIX message into the IS Document format.

In the sample, this is set as a service to be executed for the Trading Networks processingrule "Receive Execution Report 44". Therefore, whenever a FIX message of typeExecutionReport is persisted in Trading Networks, this service is executed.

Input Parameters

bizdoc Document The business document (FIX message) received. For detailsabout the structure of this document, see the description forwm.tn.rec:BizDocEnvelope in webMethods Trading Networks Built-inServices Reference.




9

Output Parameters

ExecutionReport Document The IS Document type of the incoming FIX message.

fix sample package guide

Documents