Anda di halaman 1dari 90

Integrate

Guide 8
Software Version 5.4.1-0

Document Version 3.3

Release Date 1 July 2016

Status Release
FEAtures Integrate

Table of Contents
History ............................................................................................................................................................ 3
Tell Me About… ............................................................................................................................................... 4
Integration Editor, Data Store Editor and Data Source............................................................................................. 4
XML Attribute..........................................................................................................................................................13
XML Integration Interface .......................................................................................................................................19
XML Integration Source ..........................................................................................................................................22
XML Interface Chooser............................................................................................................................................24
XML Node................................................................................................................................................................25
XML Source Chooser ...............................................................................................................................................32
What Can I Build? .......................................................................................................................................... 33
Application Form Integration ..................................................................................................................................33
Exercise 1 » Add an XML Integration Source.......................................................................................................35
Exercise 2 » Add an XML Integration Interface using Drag and Drop from Data Store Editor............................44
Exercise 3 » Add an XML Node ............................................................................................................................50
Exercise 4 » Add an XML Attribute ......................................................................................................................53
Exercise 5 » Add an Error Management Phase to Manage XML Integration Rule Errors ...................................59
Exercise 6 » Add an XML Integration Rule to Save Data to an XML Document ..................................................64
Exercise 7 » Add an XML Integration Rule to Load Data from an XML Document .............................................78

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

History
Author Version Date Comments

Dr Kevin M Potter 1.0 7 August 2014 Initial document.

Dr Kevin M Potter 2.0 15 January 2015 New Foundation, Enterprise, Advanced Features
(FEAtures) true multi-channel learning platform.

Dr Kevin M Potter 2.3 2 July 2015 Q3 Release.

Dr Kevin M Potter 2.4 18 September 2015 Q4 EC54 New Features Release.

Dr Kevin M Potter 3.1 15 January 2016 2016 Q1 EC54 Release.

Dr Kevin M Potter 3.2 8 April 2016 2016 Q2 EC54 Release.

Dr Kevin M Potter 3.3 1 July 2016 2016 Q3 EC54 Release.

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Tell Me About…
Integration Editor, Data Store Editor and Data
Source
What you need to know
Integration Editor and Data Store Editor enable your solution to talk to a Data Source.

Figure 1 Integration Editor, Data Store Editor and Data Source.

You build Integration Source and Integration Interface objects that describe data transfer (at run-time) between a
Data Source and the Data Store (as defined using Data Store Editor).
 Integration Source: An Integration Source describes the connection to the Data Source that you want to
integrate with. The Source dialog allows you to build all Integration Sources. When you select an Integration
Source Type additional tabs are displayed; these allow you to set properties to build a specific Integration
Source.
 Integration Interface: An Integration Interface describes how to map Data between the Data Source and the
Data Store. The Interface dialog allows you to build all Integration Interfaces. When you select an Integration
Interface Type additional tabs are displayed; these allow you to set properties to build a specific Integration
Interface.
 Generate Interface: A Generate Interface dialog allows you to automatically generate an Integration
Interface based on existing Data Groups and Data Items in the Data Store. You can drag-drop Data Groups
from the Data Store Editor to the Integration Editor. This opens the Generate Interface dialog.

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

 Data Source: You can integrate with many different types of Data Source.
 COM Integration: Integrate to Microsoft COM objects.
 Database Integration: Integrate to a Database using JDBC or JNDI.
 Java Integration: Integrate to Properties and Methods in a Java class.
 Log Integration: Integrate to a Log file.
 Web Service Integration: Integrate to an external Web Service.
 Polaris Integration: Integrate to Polaris. (This option is only displayed if you have a license that allows
you to work with Polaris.)
 XML Integration: Integrate to an XML file, URL, Socket or Data Item.
 Browse Class Integration: Display a Choose Source Class dialog. Manually select and integrate to
Properties and Methods in a Java class. (This is not the same as Java Integration.)

Information Component Object Model (COM) is a binary-interface standard for software components
introduced by Microsoft in 1993. It is used to enable inter-process communication and dynamic
object creation in a large range of programming languages.

Information Java Database Connectivity (JDBC) is an application programming interface (API) for the
programming language Java that defines how a client may access a database.

Information The Java Naming and Directory Interface (JNDI) is a Java API for a directory service that allows Java
software clients to discover and look up data and objects via a name.

Information Polaris is a third-party software application developed for the insurance business. It holds details of
external components such as occupations and motor vehicle classifications.

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Essential Commands

Manage Integration Editor


Click Window » Integration Editor to open the Integration Editor.
Right-click Integrations root node.
 Add Source: Display the Add Source dialog. Add a new Source.
 Add Interface: Display the Add Interface dialog. Add a new Interface.
Right-click Interfaces node.
 Generate Interface: Display the Generate Interface dialog. The dialog allows you to automatically generate
an Interface.
Right-click Source.
 Properties: Display the Source Properties dialog. The dialog allows you to edit the Source.
Right-click Interface.
 Properties: Display the Interface Properties dialog. The dialog allows you to edit the Interface.

Figure 2 Manage Integration Editor.

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

User Interface

Integration Editor
Integration Editor allows you to build a Source to enable your solution to integrate with a Data Source. Integration
Editor allows you to build an Interface to enable your solution to transfer data between a Data Source and the Data
Store.

Figure 3 Integration Editor.

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Source Dialog
The Source dialog allows you to build all Data Sources.

Details Tab
The Details Tab allows you to Name and select the Type of Integration Source that you need.

Figure 4 Source dialog » Details tab.

You can set the following options.


 Name: The Integration Data Source name.
 Type: The Type of Integration Data Source.
 COM Integration: Integrate to Microsoft COM objects.
 Database Integration: Integrate to a Database using JDBC or JNDI.
 Java Integration: Integrate to Properties and Methods in a Java class.
 Log Integration: Integrate to a Log file.
 Web Service Integration: Integrate to an external Web Service.
 Polaris Integration: Integrate to Polaris. (This option is only displayed if you have a license that allows
you to work with Polaris.)
 XML Integration: Integrate to an XML file, URL, Socket or Data Item.
 Browse Class Integration: Display a Choose Source Class dialog. Manually select and integrate to
Properties and Methods in a Java class. (This is not the same as Java Integration.)

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Interface Dialog
The Interface dialog allows you to build all Data Interfaces.

Details Tab
The Details Tab allows you to Name and select the Type of Integration Interface that you need.

Figure 5 Interface dialog » Details tab.

You can set the following options.


 Name: The Integration Data Interface name.
 Type: The Type of Integration Data Interface.
 COM Integration: Integrate to Microsoft COM objects.
 Database Integration: Integrate to a Database using JDBC or JNDI.
 Java Integration: Integrate to Properties and Methods in a Java class.
 Web Service Integration: Integrate to an external Web Service.
 Polaris Integration: Integrate to Polaris. (This option is only displayed if you have a license that allows
you to work with Polaris.)
 XML Integration: Integrate to an XML file, URL, Socket or Data Item.
 Browse Class Integration: Display a Choose Source Class dialog. Manually select and integrate to
Properties and Methods in a Java class. (This is not the same as Java Integration.)

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Generate Interface Dialog


The Generate Interface dialog allows you to automatically generate all Types of Data Interface.

Generator Tab
The Generator Tab allows you to Name and select the Type of Integration Interface that you need.

Figure 6 Generate Interface dialog » Generator tab.

You can set the following options.


 Name: The Interface name.

10

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

 Generator Type: The Type of Integration Data Interface.


 COM Integration: Integrate to Microsoft COM objects.
 Database Integration: Integrate to a Database using JDBC or JNDI.
 Java Integration: Integrate to Properties and Methods in a Java class.
 Web Service Integration: Integrate to an external Web Service.
 Polaris Integration: Integrate to Polaris. (This option is only displayed if you have a license that allows
you to work with Polaris.)
 XML Integration: Integrate to an XML file, URL, Socket or Data Item.
 Browse Class Integration: Display a Choose Source Class dialog. Manually select and integrate to
Properties and Methods in a Java class. (This is not the same as Java Integration.)
 Data Group: Select the (Parent) Data Group that acts as the starting point for Interface Integration.
 Perform Read Operation: Read from the XML or Database Integration Source.
 Perform Write Operation: Write to the XML or Database Integration Source.
 Perform Delete Operation: Delete from the Database Integration Source.

Information Component Object Model (COM) is a binary-interface standard for software components
introduced by Microsoft in 1993. It is used to enable inter-process communication and dynamic
object creation in a large range of programming languages.

Information Java Database Connectivity (JDBC) is an application programming interface (API) for the
programming language Java that defines how a client may access a database.

Information The Java Naming and Directory Interface (JNDI) is a Java API for a directory service that allows Java
software clients to discover and look up data and objects via a name.

Information Polaris is a third-party software application developed for the insurance business. It holds details of
external components such as occupations and motor vehicle classifications.

11

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Details Tab (for XML Integration only)


The Details Tab (for XML Integration only) allows you to determine XML file structure and content.

Figure 7 Generate Interface dialog » Details tab (for XML Integration only).

You can set the following options.


 Attribute as separate node: Represent each attribute (or Data Item) as a separate node in the XML
Document.
 Include if empty: Include a node for attributes that do not contain data.

12

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

XML Attribute
What you need to know
In XML Document Object Model (DOM) vernacular, everything in an XML Document is a node.
 Document: The entire document is a document node.
 Element: Every XML element is an element node.
 Text: The text in the XML elements are text nodes.
 Attribute: Every attribute is an attribute node.
 Comment: Comments are comment nodes.
In edgeConnect vernacular an XML Attribute essentially allows you to build a DOM element node that simply
contains Attributes and/or Text. Or in other words, an edgeConnect XML Attribute allows you to add an XML
Element to your XML Document, where the Element contains data expressed as Attributes or as Text.

Figure 8 XML Attribute.

Best It is best practice to use meaningful Customer and/or Project Specific XML Attribute names.
Practice

13

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Essential Commands

Add XML Attribute


Right-click XML Node or XML Attribute.
 Add Attribute: Display the Add Attribute dialog. Add a new Attribute.

Figure 9 Add XML Attribute.

14

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

User Interface

Details Tab
The Details Tab allows you to enter a Name and to mark read/write operation requirements.

Figure 10 Attribute dialog » Details tab.

You can set the following options.


 Name: Enter the Attribute Name.
 Perform Read Operation: Mark to allow the Attribute to be read from (in the XML Document).
 Perform Write Operation: Mark to allow the Attribute to be written to (in the XML Document).

15

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Mapping Tab
The Mapping Tab allows you to map the attribute to a Data Item, Data Group, Variable or Value.

Figure 11 Attribute dialog » Mapping tab.

You can set the following options.


 Data Type: Select a Data Type.
 Data Item: Select a Data Item using the Data Item Chooser dialog.
 Data Group: Select a Data Group using the Data Group Chooser dialog
 Variable: Enter the name of a Session Variable
 Value: Enter a literal value

16

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Attribute Definition Tab


The Attribute Definition tab allows you to name and describe the attribute.

Figure 12 Attribute dialog » Attribute Definition tab.

You can set the following options.


 Name of XML Attribute: Enter the name of the XML Attribute (as required in the XML Document).
 Namespace: Optionally enter a Namespace.
 Attribute as separate node: Mark to create attribute as a child Element. Unmark to add as attribute within
parent element.
 Repeat Node: Mark to repeat values (where parent element is bound to a Repeating Data Group).
 As CDATA Section: Mark if attribute data is character data.
 Include if value is empty: Mark if you want to include the attribute even when it does not have a value.

17

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Information XML namespaces are used for providing uniquely named elements and attributes in an XML
document. They are defined in a W3C recommendation. An XML instance may contain element or
attribute names from more than one XML vocabulary.

Information CDATA stands for Character Data and it means that the data in between these tags includes data
that could be interpreted as XML mark-up, but should not be.
The key difference between CDATA and a Comment is, CDATA is still part of the XML Document,
while a Comment is not.

18

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

XML Integration Interface


What you need to know
An XML Integration Interface describes how to map XML Data between an XML Integration Source and the Data
Store.
 Document: The Data Source is a web server resident XML Document that you can write to and read from.
 URL (or Web Service): The Data Source is the URL of a system that accepts and returns XML messages or a
Web Service that accepts and returns XML data.
 Socket: The Data Source is the IP Address and Port Number of a Service on a computer that accepts and
returns XML data.
 Data Item: The Data Source is a Data Item that you can write XML to and read XML from.

Figure 13 XML Integration Interface.

Best It is best practice to use meaningful Customer and/or Project Specific XML Integration Interface
Practice names.

19

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

User Interface

Root Node Definition Tab


The Root Node Definition Tab allows you to name the XML Document Root Node.

Figure 14 Generate XML Interface dialog » Generator tab.

You can set the following options.


 Root Node Name: Optionally enter a Root Node name.
 Namespace: Optionally enter a Namespace.

Information XML namespaces are used for providing uniquely named elements and attributes in an XML
document. They are defined in a W3C recommendation. An XML instance may contain element or
attribute names from more than one XML vocabulary.

20

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

21

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

XML Integration Source


What you need to know
An XML Integration Source describes the connection to a Data Source that you can read from and write to using
XML.
 Document: The Data Source is a web server resident XML Document that you can write to and read from.
 URL (or Web Service): The Data Source is the URL of a system that accepts and returns XML messages or a
Web Service that accepts and returns XML data.
 Socket: The Data Source is the IP Address and Port Number of a Service on a computer that accepts and
returns XML data.
 Data Item: The Data Source is a Data Item that you can write XML to and read XML from.

Figure 15 XML Integration Source.

Best It is best practice to use meaningful Customer and/or Project Specific XML Integration Source
Practice names.

22

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

User Interface

Connection Tab
The Connection Tab allows you describe the connection to the XML Data Source.

Figure 16 XML Integration Source » Connection tab.

You can set the following options.


 Connection Type: Select the Connection Type.
 File: The Data Source is a server resident XML file that you can write to and read from.
 URL: The Data Source is the URL of a system that accepts and returns XML messages or a Web Service
that accepts and returns XML data.
 Socket: The Data Source is the IP Address and Port Number of a Service on a computer that accepts
and returns XML data.
 Data Item: The Data Source is a Data Item that you can write XML to and read XML from.
 File Name: If Connection Type is File then enter target XML file path and name.
 Omit XML Declaration: Mark if you want to omit the XML Declaration.
 Pretty Print: Mark if you want the generated XML to be indented.

23

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

XML Interface Chooser


What you need to know
The XML Interface Chooser dialog allows you to select an XML Interface Source.

Figure 17 XML Interface Chooser dialog.

The XML Interface Chooser dialog helps you to work with other dialogs.
 Rule dialog.

24

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

XML Node
What you need to know
In XML Document Object Model (DOM) vernacular, everything in an XML Document is a node.
 Document: The entire document is a document node.
 Element: Every XML element is an element node.
 Text: The text in the XML elements are text nodes.
 Attribute: Every attribute is an attribute node.
 Comment: Comments are comment nodes.
In edgeConnect vernacular an XML Node essentially allows you to build a DOM element node. Or in other words,
an edgeConnect XML Node allows you to add an XML Element to your XML Document, where an XML element is
everything from (and including) the element's start tag to (and including) the element's end tag.

Figure 18 XML Node.

Optionally, you can map an (edgeConnect) XML Node to a repeating Data Group. This allows you to structure and
map repeating data as child Elements and child Attributes (based on child Data Groups, Data Items, Variables and
Values) within the parent Element.

Best It is best practice to use meaningful Customer and/or Project Specific XML Node names.
Practice


25

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Essential Commands

Add XML Node


Right-click XML Interface or XML Node.
 Add Node: Display the Add Node dialog. Add a new Node.

Figure 19 Add XML Node.

26

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

User Interface

Details Tab
The Details Tab allows you to enter a Name and optionally select a repeating Data Group.

Figure 20 Node dialog » Details tab.

You can set the following options.


 Name: Enter the Node Name.
 Data Groups to Increment: Optionally select a repeating Data Group.

27

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Node Definition Tab


The Node Definition Tab allows you to enter a Name and optionally select a repeating Data Group.

Figure 21 Node dialog » Node Definition tab.

You can set the following options.


 XML Node Name: Enter the Node Name as required in the XML Document.
 Namespace: Optionally enter a Namespace.
 Include if node is empty: Mark to include the Element even if it is empty.
 Specify Search Criteria: Mark to show the Search Criteria tab.
 Repeated Instance: Mark to show the Repeated Instance tab.

Information XML namespaces are used for providing uniquely named elements and attributes in an XML
document. They are defined in a W3C recommendation. An XML instance may contain element or
attribute names from more than one XML vocabulary.

28

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Search Criteria Tab (Unmark Specify XPath Query)


The Search Criteria Tab allows you to enter search criteria to select XML Document Nodes.

Figure 22 Node dialog » Search Criteria tab.

You can set the following options.


 Specify XPath Query: Mark to build an XPath Query.
 Search Attributes: Enter a comma separated list of attributes.
 Search Operators: Enter a comma separated list of operators.
 Search Values: Enter a comma separated list of values.
 Search Type: Mark if you want to test all search conditions.

29

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Search Criteria Tab (Mark Specify XPath Query)


The Search Criteria Tab allows you to enter an XPath Query.

Figure 23 Node dialog » Details tab.

You can set the following options.


 Specify XPath Query: Mark to build an XPath Query.
 XPath Query: Build the XPath Query.

30

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Repeated Instance Tab


The Repeated Instance Tab allows you to manage required instances in a repeating Data Group.

Figure 24 Node dialog » Repeated instance tab.

You can set the following options.


 Instance Range: Enter repeated Data Group Instance range (e.g., 1-10).
 Instance Attribute Name: Enter the name of an attribute in the Element that stores the Instance count.
 Data Group Instance Start: Enter the Data Group Instance that you want to start from.

31

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

XML Source Chooser


What you need to know
The XML Source Chooser dialog allows you to select an XML Integration Source.

Figure 25 XML Source Chooser dialog.

The XML Source Chooser dialog helps you to work with other dialogs.
 Rule dialog.

32

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

What Can I Build?


Application Form Integration
What you need to know
The Exercises in this Chapter show you how to integrate the Application Form Solution with external data sources.
 XML: You are going to use the Integration Editor and Integration Rules to save and load Application Form
Data between the Data Store and an XML Document. The Rules are bound to buttons on the Save Data to
XML and Reload Data from XML Phases.

Figure 26 Sketch a Design » Application Form Integration.

33

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Figure 27 Write Data to an XML Document.

34

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Exercise 1 » Add an XML Integration Source


Step-By-Step
The following steps show you how to use Integration Editor to add an XML Integration Source of type File.
1. Start Developer.
2. Select Window menu » Integration Editor.

Figure 28 Integration Editor.

35

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

3. Right-click Integrations root node » Add » Source.


4. Enter Name.
ApplicationFormXMLSource
5. Select Type.
XML Integration

Figure 29 Add Source dialog » Details tab.

36

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

6. Select the Connection tab.


7. Select Connection Type.
File
8. Click File Name ellipsis […] button.

Figure 30 Add Source dialog » Connection tab.

37

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Text Editor dialog is displayed.


9. Click Text Editor ellipsis […] button.

Figure 31 Text Editor dialog.

38

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Value Chooser dialog is displayed.


10. Expand the System Words node.
11. Expand the Application node.
12. Select System Word.
PROJECTHOME

Figure 32 Value Chooser dialog.

13. Click OK to close the Value Chooser dialog.

39

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Text Editor dialog is displayed.


14. Append text to the expression.
$$PROJECTHOME$/FEAturesXML/FEAtures
15. Click the Text Editor ellipsis […] button.

Figure 33 Text Editor dialog.

40

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Value Chooser dialog is displayed.


16. Expand the Data Store node.
17. Expand the ApplicationFormHelperData Data Group node.
18. Select Data Item.
ApplicationReferenceNumber

Figure 34 Value Chooser dialog.

19. Click OK to close the Value Chooser dialog.

41

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Text Editor dialog is displayed.


20. Append text to the expression.
$$PROJECTHOME$/XML/FEAtures$$ApplicationFormHelperData[1].ApplicationReferenceNumber$.xml

Figure 35 Text Editor dialog.

21. Click OK to close the Text Editor dialog.

42

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Add Source dialog is displayed.


22. Confirm that the File Name property is correctly set.
$$PROJECTHOME$/FEAturesXML/FEAtures$$ApplicationFormHelperData[1].ApplicationReferenceNumb
er$.xml

Figure 36 Add Source dialog » Connection tab.

23. Click OK.

Best It is best practice to create your own Folders within the Project Folder to manage custom Files that
Practice are going to be part of your solution.

 It’s simply good housekeeping! 

The XML Integration Source is added to the Integration Editor tree-structure.

Figure 37 Integration Editor » ApplicationFormXMLSource XML Data Source.

24. Select File menu » Save.


43

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Exercise 2 » Add an XML Integration Interface using Drag and Drop from Data Store
Editor
Step-By-Step
The following steps show you how to use Integration Editor and Data Store Editor to add an XML Integration
Interface.
1. Select Window menu » Integration Editor.
2. Select Window menu » Data Store Editor.
3. Position Editors side-by-side.

Figure 38 Integration Editor and Data Store Editor.

44

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

4. Drag the ApplicationFormData Data Group from Data Store Editor to the XML Integration node in Integration
Editor.

Figure 39 Integration Editor and Data Store Editor.

5. Select Generate XML Interface.

45

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Generate XML Interface dialog is displayed.


6. Enter Name.
ApplicationFormXMLInterface
7. Mark Perform Read Operation.
8. Mark Perform Write Operation.

Figure 40 Generate XML Interface dialog » Generator tab.

46

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

9. Select the Details tab.


10. Mark Attribute as separate Node.
11. Mark Include if empty.

Figure 41 Generate XML Interface dialog » Details tab.

12. Click OK.

47

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

An XML Interface is automatically generated based on Data Groups and Data Items contained in the
ApplicationFormData Data Group.

Figure 42 Drag-Drop from Data Store Editor to Integration Editor to create and Interface.

48

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

13. Select Integration Editor.


14. Expand Node Definition for ApplicationFormData node.
15. Expand Node Definition for AboutYouData node.
You’ll see that an interface has automatically been generated such that each Data Item (e.g., Title) has been mapped
to a Named Node in an XML Document.

Figure 43 Integration Editor » XML Interface.

16. Select File menu » Save.

49

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Exercise 3 » Add an XML Node


Step-By-Step
The following steps show you how to use Integration Editor to add an XML Node to an XML Interface.
1. Select Integration Editor.
2. Expand XML Integration node.
3. Expand Interfaces node.
4. Expand ApplicationFormXMLInterface.
5. Right-click Node definition for ApplicationFormData Node » Add » Node.
6. Enter Name.
XML Node ApplicationFormHelperData

Figure 44 Add Node dialog » Details tab.

50

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

7. Select the Node Definition tab.


8. Enter XML Node Name.
ApplicationFormHelperData
9. Mark Include if node is empty.

Figure 45 Add Node dialog » Node Definition tab.

10. Click OK.

51

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Node is added to the XML Interface.

Figure 46 Integration Editor.

11. Select File menu » Save.

52

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Exercise 4 » Add an XML Attribute


Step-By-Step
The following steps show you how to use Integration Editor to add an XML Attribute to an XML Interface.
1. Select Integration Editor.
2. Expand XML Integration node.
3. Expand Interfaces node.
4. Expand ApplicationFormXMLInterface.
5. Expand Node definition for ApplicationFormData node.
6. Right-click Node definition for ApplicationFormHelperData XML Node » Add » Attribute.
7. Enter Name.
XML Attribute Region
8. Mark Perform Read Operation.
9. Mark Perform Write Operation.

Figure 47 Add Attribute dialog » Details tab.

53

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

10. Select the Mapping tab.


11. Select Data Type.
Data Item
12. Click Data Item Name Select button.

Figure 48 Add Attribute dialog » Mapping tab.

54

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Data Item Chooser dialog is displayed.


13. Expand ApplicationFormHelperData Data Group.
14. Select Data Item.
Region

Figure 49 Data Item Chooser dialog.

15. Click OK to close the Data Item Chooser dialog.

55

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Add Attribute dialog is displayed.


16. Confirm that the Data Item Name property is correctly set.
ApplicationFormHelperData[1].Region

Figure 50 Add Attribute dialog » Mapping tab.

56

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

17. Select the Attribute Definition tab.


18. Enter Name of XML Attribute.
Region
19. Mark Attribute as separate Node.
20. Mark Include if value is empty.

Figure 51 Add Attribute dialog » Attribute Definition tab.

21. Click OK.

57

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Attribute is added to the XML Interface.

Figure 52 Integration Editor.

22. Select File menu » Save.

58

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Exercise 5 » Add an Error Management Phase to Manage XML Integration Rule Errors
Step-By»-Step
Errors can occur when using the XML Integration Rule. For example, if the Rule cannot locate the required Source
or Interface then an error is thrown. The Rule allows you to specify the name of a Phase to jump to when an error
occurs.
The following steps show you how use Process Editor to add a new Phase to the Error Management Process to
manage XML Integration Rule Errors.
1. Select Window menu » Process Editor.
2. Expand Error Management Process.
3. Right-click General Error Phase » Copy.
4. Right-click Error Management Process » Paste.
5. Expand General Error – Copy Phase.

Figure 53 Copy and Paste General Error Phase.

59

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

6. Right-click General Error – Copy Phase » Properties.


7. Enter a new Phase Name.
XML Integration Rule Error

Figure 54 Phase Properties dialog » Properties tab.

8. Click OK.

60

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

9. Right-click XML Integration Rule Error Phase FEAtures Info Note » Properties.
10. Enter new Comment text.
An XML Integration Rule Error occurs when a Source or an Interface cannot be found or are incorrectly
configured.

Figure 55 Note Properties dialog.

11. Click OK.

61

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

12. Right-click XML Integration Rule Error Phase Heading 2 Really sorry but… » Properties.
13. Enter new Display Text.
Really sorry but I could not load or save your data. Please try again...

Figure 56 Heading Properties dialog.

14. Click OK.

62

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The new XML Integration Rule Error Phase is now ready for use. 

Figure 57 New Error Management Phase for use with XML Integration Rules.

15. Select File menu » Save.

63

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Exercise 6 » Add an XML Integration Rule to Save Data to an XML Document


Step-By-Step
The following steps show you how to use Process Editor to add an XML Integration Rule to save data to an XML
Document.
1. Select Process Editor.
2. Expand Application Form Floating Areas Process.
3. Expand Save Data to XML Phase.
4. Right-click Save Data and Return to Application Form Button » Add » Button Rule » Other.
5. Enter Rule Name.
Save Application Form Data to XML Document
6. Select Rule Class.
XML Integration Rule

Figure 58 XML Integration Rule dialog » Definition tab.

64

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

7. Select Error Handling tab.


8. Click Specific Error Phase Select button.

Figure 59 XML Integration Rule dialog » Error Handling tab.

65

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Error Phase Chooser dialog is displayed.


9. Expand Error Management Process.
10. Select Phase.
XML Integration Rule Error

Figure 60 Error Phase Chooser dialog.

11. Click OK to close the Error Phase Chooser dialog.

66

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule dialog is displayed.


12. Confirm that the Specific Error Phase is correctly set.
Error Management.XML Integration Rule Error

Figure 61 XML Integration Rule dialog » Error Handling tab.

67

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

13. Select the Details tab.


14. Click Source Name Select button.

Figure 62 XML Integration Rule dialog » Details tab.

68

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Source Chooser dialog is displayed.


15. Expand XML Integration node.
16. Expand Sources node.
17. Select XML Integration Source.
ApplicationFormXMLSource

Figure 63 XML Source Chooser dialog.

18. Click OK to close the XML Source Chooser dialog.

69

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule dialog is displayed.


19. Confirm that the Source Name is correctly set.
ApplicationFormXMLSource
20. Click the Interface Name Select button.

Figure 64 XML Integration Rule dialog » Details tab.

70

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Interface Chooser dialog is displayed.


21. Expand XML Integration node.
22. Expand Interfaces node.
23. Select XML Integration Interface.
ApplicationFormXMLInterface

Figure 65 XML Interface Chooser dialog.

24. Click OK to close the XML Interface Chooser dialog.

71

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule dialog is displayed.


25. Confirm that the Interface Name is correctly set.
ApplicationFormXMLInterface
26. Select Operation.
Write

Figure 66 XML Integration Rule dialog » Details tab.

27. Click OK.

72

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule is added to the Save Data and Return to Application Form Button.

Figure 67 Process Editor » Application Form Floating Areas Process » Save Data to XML Phase.

28. Select File menu » Save.

73

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Test Functionality Test


Let’s see if we can save some Application Form Data to an XML Document using the XML Integration
Rule.
1. Select Process Editor.
2. Right-click Application Form Process » Run.
First, enter some data to save to the XML Document.
3. Select Title.
Mr
4. Enter First Name.
Joe
5. Enter Last Name.
Bloggs
6. Select a Date of Birth.
06/06/1966
7. Select a Region.
Europe
8. Select a Nationality.
United Kingdom
Second, save the data to the XML Document.
9. Click the Continue Button (to navigate to the Contact Details Phase).
10. Click the Save Data Button (to navigate to the Save Data to XML Phase).
11. Click the Save Data and Return to Application Form Button (to save the data to the XML
Document).
12. Close browser.
Third, let’s see if the XML Document exists and whether it contains our data. 
13. Open a Windows Explorer Window.
14. Navigate to the new FEAtures Project XML Folder.
C:\ECProject\Projects\FEAturesHybridSolution\FEAturesXML
15. Confirm that the XML Folder contains an XML Document.
16. Right-click XML Document » Open.
17. Confirm that the XML Document contains our data. 
18. Close XML Document.

74

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Figure 68 Enter some data.

75

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Figure 69 Save Data to an XML Document using the XML Integration Rule.

76

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Figure 70 Confirm that the XML Document exists.

Figure 71 Confirm that the XML Document contains your data.

77

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Exercise 7 » Add an XML Integration Rule to Load Data from an XML Document
Step-By-Step
The following steps show you how to use Process Editor to add an XML Integration Rule to load data from an XML
Document.
1. Select Process Editor.
2. Expand Application Form Floating Areas Process.
3. Expand Reload Data from XML Phase.
4. Right-click Reload Data and Return to Application Form Button » Add » Button Rule » Other.
5. Enter Rule Name.
Reload Application Form Data from XML Document
6. Select Rule Class.
XML Integration Rule

Figure 72 XML Integration Rule dialog » Definition tab.

78

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

7. Select Error Handling Tab.


8. Click Specific Error Phase Select Button.

Figure 73 XML Integration Rule dialog » Error Handling tab.

79

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The Error Phase Chooser dialog is displayed.


9. Expand Error Management Process.
10. Select Phase.
XML Integration Rule Error

Figure 74 Error Phase Chooser dialog.

11. Click OK to close the Error Phase Chooser dialog.

80

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule dialog is displayed.


12. Confirm that the Specific Error Phase is correctly set.
Error Management.XML Integration Rule Error

Figure 75 XML Integration Rule dialog » Error Handling tab.

81

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

13. Select the Details tab.


14. Click Source Name Select button.

Figure 76 XML Integration Rule dialog » Details tab.

82

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Source Chooser dialog is displayed.


15. Expand XML Integration node.
16. Expand Sources node.
17. Select XML Integration Source.
ApplicationFormXMLSource

Figure 77 XML Source Chooser dialog.

18. Click OK to close the XML Source Chooser dialog.

83

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule dialog is displayed.


19. Confirm that the Source Name is correctly set.
ApplicationFormXMLSource
20. Click the Interface Name Select button.

Figure 78 XML Integration Rule dialog » Details tab.

84

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Interface Chooser dialog is displayed.


21. Expand XML Integration node.
22. Expand Interfaces node.
23. Select XML Integration Interface.
ApplicationFormXMLInterface

Figure 79 XML Interface Chooser dialog.

24. Click OK to close the XML Interface Chooser dialog.

85

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule dialog is displayed.


25. Confirm that the Interface Name is correctly set.
ApplicationFormXMLInterface
26. Select Operation.
Read

Figure 80 XML Integration Rule dialog » Details tab.

27. Click OK.

86

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

The XML Integration Rule is added to the Reload Data and Return to Application Form Button.

Figure 81 Process Editor » Application Form Floating Areas Process » Reload Data from XML Phase.

28. Select File menu » Save.

87

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Test Functionality Test


Let’s see if we can reload some Application Form Data from an XML Document using the XML
Integration Rule.
First, let’s get the name of the XML Document that you generated in the last exercise. 
1. Open a Windows Explorer Window.
2. Navigate to the new FEAtures Project XML Folder.
C:\ECProject\Projects\FEAturesHybridSolution\FEAturesXML
3. Right-click XML Document » Rename.
4. Highlight the Reference Number part of the file name. For example, jb-290615-2789.

5. Copy the Reference Number.


For example, just press <CTRL> + C on your keyboard.
6. Close Windows Explorer.
Second, let’s use the Reference Number to load data back into the Application Form. 
7. Select Process Editor.
8. Right-click Application Form Process » Run.
9. Click the Continue Button (to navigate to the Contact Details Phase).
10. Click the Reload Data Button (to navigate to the Reload Data from XML Phase).
11. Paste the Reference Number (that you just copied) to the Reference Question Answer.
For example, just press <CTRL> + V on your keyboard.
12. Click the Reload Data and Return to Application Form Button (to reload the data from the XML
Document).
Third, let’s see if the data was loaded back into the Application Form. 
13. Click the Back Button (to navigate back to the About You Phase).
14. Confirm that the Application Form displays data that came from the XML Document. 
15. Close browser.

88

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Figure 82 Copy the Application Reference Number from the XML Document file name.

Figure 83 Paste the Application Reference Number to the Reference Question Answer.

89

Dr Kevin M Potter Strategy-Dev


FEAtures Integrate

Figure 84 Confirm that data has been reloaded to the Application Form from the XML Document.

Brilliant, you’ve finished all of the exercises in this chapter. Go back to the Introduction Guide and build something else! 

90

Dr Kevin M Potter Strategy-Dev

Anda mungkin juga menyukai