1.

2. 3.

1. 2.

MFT and JMS NotificationsIn scope for this page:

Configuring an existing MFT Command Centre (CC) and Internet Server (IS) 7.2.3 to send a JMS AlertUsing the BW MFT Palette plugin to receive the JMS AlertExample using Internet Server Thin Client

Out of scope for this page: 

Platform Server transfers (although this shouldn't be too difficult, there's at least one additional stepof ensuring the Collection Service is running)

[ ] [ ] [ ] [ Pre-requisites Set up JMS Alerts MFT Command Centre: Add JMS Service MFT Command ] [ ] [ ] [ Centre: Add Alert BusinessWorks Setup: Listen for Alert Message Upload File & Receive JMS Alert

] [ ] [ Start BusinessWorks Project Transfer file with MFT Internet Transfer Client Check BusinessWorks ] [ ] [ ]Project received Alert Appendix Management message

Pre-requisites

The target EMS instance should have the following queues and topics created:Alert (topic)Audit (queue)Notification (topic)Management (queue)Transfer (queue)

An existing user and transfer should already be configured in CC/ISInstall the BusinessWorks MFT Plug-in as local admin. Available here: G:\COMMON\jamesg\TIBCO_downloads\MFT Plugin forBusinessWorks

Set up JMS Alerts

MFT Command Centre: Add JMS Service

Log into MFT Command Centre, and go to Management -> Manage Services -> JMS Services -> Configure JMS ServiceSee the following settings as an example. The settings below assumes there's an  user setup in the EMS instance. This isn'tmft

necessarily required. All other sections on this page are left as default.

2.

3.

4.

1. 2.

Once the settings are entered, hit the 'Test' button to verify connectivity:

Done.

MFT Command Centre: Add Alert

Log into MFT Command Centre, and go to Management -> Alerts -> Add AlertsSee the following settings as an example. This particular alert is very broad. It will be invoked for all users, for send or receive, forsuccess or failure. Proper JMS Alerts should be configured so they are specific to particular scenarios and therefore stay relevant.

2.

3. 4.

Done. There's no need to update the Transfer Definition because the selection criteria in the Alert will pick up any relevant transfer.Note: If you are using Platform Server, then the Collection Service should be running. This can be configured under Management ->Alerts -> Manage Alerts -> (left side menu) Collection Service:

4.

1.

 

BusinessWorks Setup: Listen for Alert Message

The quickest way to get a process to receive JMS Alert messages is as follows.

In a BW project, create an  in a folder. See the following settings as an example. Ensure the same EMSMFT Shared Connectioninstance is used in this Connection resource as what the MFT CC is configured to use in the above Once it'sJMS Service. configured, hit 'Test Connection'. It should be successful. (If you're curious, the section has a capture of the ManagementAppendix

1.

2.

message that is sent across the wire when is invoked). Test Connection

 

Create a new process starter:Listen for Alert Message 

2.

3.

4.

1.

When configuring the Listen for Alert Message activity, point it at the object you created just before. YouMFT Shared Connectioncan optionally use message selectors if you want your process to only pick up certain alerts. Knowing which selectors to apply herewill depend on what sort of alerts you are designing your process to handle:

Ensure your project validates without errors.

Upload File & Receive JMS Alert

 

Start BusinessWorks Project

 

1. 2.

1. 2.

3.

4.

5.

Once the previous step is complete, start Designer Tester, with your process selected.Continue to the next section to upload a file.

 

Transfer file with MFT Internet Transfer Client

 

Using either Firefox or IE, open the following link: https://ws16586/cfcc/control?view=view/filetransfer/thin/fileList.jsp&FileID=#At the login screen, enter credentials:  / b2b_test password

You will be presented with a "Transfers" screen which allows the user to perform an upload. This is because there's ab2b_test

corresponding Transfer Definition created in MFT Command Centre for this user:

Click Browse. You may get a pop-up window about your browser being unable to verify the certificate presented by the MFT ThinClient. For testing purposes this doesn't matter, click OK or whatever is necessary. (Unless you pick 'Always' you will get this pop-upfor every transfer).Select the .zip file you wish to transfer and click OK:

5.

6. 7.

8. 9.

1.

With the file selected, hit the   button.Another box will pop up, indicating if the transfer has been a success:

Check if the file was successfully transferred:In a different browser, log into the MFT Command Centre , and checkhttps://ws16586:8443/cfcc/control?view=view/admin/start.jspReports -> Audits -> Search Audits:

Check BusinessWorks Project received Alert

Once the file has been transferred, go back to your Designer Tester window. You should see the following result:

1.

2. Example of  structure:AlertResponse

<?xml version = "1.0" encoding = "UTF-8"?><AlertResponse> <Properties> <JMSCorrelationID/> <JMSType>Text</JMSType> <JMSDestination>Topic[Alert]</JMSDestination> <Comment>Alert Action JMS Comment Field</Comment> </Properties> <Body> <ns0:ResponseType xmlns:ns0 ="http://www.tibco.com/MFT/JMS-XMLSchema">Alert</ns0:ResponseType> <ns0:NumRecords xmlns:ns0 ="http://www.tibco.com/MFT/JMS-XMLSchema">1</ns0:NumRecords> <ns0:AuditRecord xmlns:ns0 = "http://www.tibco.com/MFT/JMS-XMLSchema"> <ns0:AuditType>InternetServer</ns0:AuditType> <ns0:AuditID>A90440000038</ns0:AuditID> <ns0:CKPTInterval>5</ns0:CKPTInterval> <ns0:CKPTCount>1</ns0:CKPTCount> <ns0:NodeName/> <ns0:InitiatorFileName>C:\0000055410.zip</ns0:InitiatorFileName> <ns0:Delimiter>None</ns0:Delimiter>

AlertResponse Expand

source

2.

<ns0:Conversion>Binary</ns0:Conversion> <ns0:Department/> <ns0:Description>File transfer for b2b_test</ns0:Description> <ns0:Encryption>Default</ns0:Encryption> <ns0:InitiatorTransactionID>I904400040</ns0:InitiatorTransactionID> <ns0:LocalCTFile/> <ns0:ServerName>*LOCAL</ns0:ServerName> <ns0:ZOSAllocationType/> <ns0:ZOSAllocationPrimary/> <ns0:ZOSAllocationSecondary/> <ns0:ZOSRecordFormat/> <ns0:ZOSRecordLength/> <ns0:ZOSBlocksize/> <ns0:ZOSUnitName/> <ns0:ZOSVolumeName/> <ns0:ZOSStorageClass/> <ns0:ZOSDataClass/> <ns0:ZOSManagementClass/> <ns0:PPASource1>N/A (128)</ns0:PPASource1> <ns0:PPAStatus1>N/A (N/A (128))</ns0:PPAStatus1> <ns0:PPAType1>COMMAND</ns0:PPAType1> <ns0:PPAData1>C:\mft-scripts\signfile.cmdC:\MFT\from_client\received\b2b_test\0000055410.zip 20140904141600 >C:\mft-scripts\logs\20140904141600.0000055410.zip.txt</ns0:PPAData1> <ns0:PPAReturnCode1>0</ns0:PPAReturnCode1> <ns0:PPASource2>N/A (128)</ns0:PPASource2> <ns0:PPAStatus2>N/A (N/A (128))</ns0:PPAStatus2> <ns0:PPAType2>COMMAND</ns0:PPAType2> <ns0:PPAData2/> <ns0:PPAReturnCode2>0</ns0:PPAReturnCode2> <ns0:PPASource3/> <ns0:PPAStatus3/> <ns0:PPAType3/> <ns0:PPAData3/> <ns0:PPAReturnCode3/> <ns0:PPASource4/> <ns0:PPAStatus4/> <ns0:PPAType4/> <ns0:PPAData4/> <ns0:PPAReturnCode4/> <ns0:RemoteCTFile/> <ns0:ResponderFileName>C:\MFT\from_client\received\b2b_test\0000055410.zip</ns0:ResponderFileName> <ns0:SendRecv>Send</ns0:SendRecv> <ns0:EmailSuccess/> <ns0:EmailFailure/> <ns0:TransferByteCount>978</ns0:TransferByteCount> <ns0:TransferCompressedByteCount>880</ns0:TransferCompressedByteCount> <ns0:TransferStartDateTime>2014-09-04T14:16:00</ns0:TransferStartDateTime> <ns0:TransferEndDateTime>2014-09-04T14:16:00</ns0:TransferEndDateTime> <ns0:TransferType>File</ns0:TransferType> <ns0:ProcessName/> <ns0:UserData/> <ns0:TransferStatus>SUCCESS</ns0:TransferStatus> <ns0:TransferStatusMsg>Transfer Complete.</ns0:TransferStatusMsg> <ns0:InitiatorUserId>b2b_test</ns0:InitiatorUserId> <ns0:FileWriteMode>Create</ns0:FileWriteMode> <ns0:AS2MDNStatus/> <ns0:ProxyStatusMsg/> <ns0:Compression>None</ns0:Compression>

2.

</ns0:AuditRecord> </Body></AlertResponse>

 

Appendix

Management message

Request

Headers

Body

Response

Headers

Body