For the list of all supported Decision Insight downloads and releases, see the Downloads
Understand and create test data
This section provides an overview of the different types of data that you work with in Decision Insight, and how to create some test data for the Order entity.
In almost every business solution, some data is not liable to change very often. It is still considered data – something you want to define and access rather than build into the solution – because it is on the business side of the boundary between the process and the monitoring solution. This is static data. You can use static data to translate internal nomenclature into human-factored information.
Static data is usually only read by the solution at start-up, or when a refresh is initiated manually.
For example, an insurance claim process might use EDI message types of 270, 271, 276 and 277. Your solution could use those numbers and some people would understand what they are seeing; others might not. To accommodate both user types, your dashboards could use labels for messages that would read:
- Benefit Inquiry (270)
- Benefit Response (271)
- Claim Status Request (276)
- Claim Status Notification (277)
The definitions for EDI messages are not likely to change, which is why they are considered static. Over time, additional message types might be included into the deployment, so you want to allow for new message type definitions to be added easily into the system.
The other type of data is transaction data. For flow-based business processes, transaction data represents information about the operations of the business process itself, for example, information about a file or a transaction that is changing state or location. This information can be the result of pulling data into or pushing data toward the solution.
Transaction data inherently represents current information that is updated as time goes by.
Apache Camel for data access
To manage data access, Axway Decision Insight uses the Apache Camel open-source java framework . Camel is a rule-based routing and mediation engine that is bundled into each Decision Insight deployment.
For the tech savvy, take a look at Integration with Apache Camel by Jonathan Anstey. You can find that article at https://dzone.com/articles/open-source-integration-apache.
If you are not tech savvy, Camel helps connect Decision Insight to the external information it needs to run your application. That information can be in a messaging application, a database, a log file, or essentially any file that contains data you need. In this exercise, you will link to static data and a comma separated value (csv) file.
2. Create the test data
The test data set starts small. The idea is to test the logic of your route to verify it is working before attempting to manage a larger volume of information. The data you need will contain only one type of event. As a reminder, the process events are:
|Purchase Orders Received
||Line Request Scheduled
||Line Request Completed
|Purchase Order Invoicing
For the initial test data, you need the New Order event.
Create a resource
To create a resource for the Order entity, follow these steps.
On the main menu, click the Data Integration icon.
||On the left menu, click Resources. The Resources pane is displayed.
From the In space drop-down box, select the Initializers space. This is the space in which you want to create your resource.
Click New Resource. The Details pane is displayed.
||Give the resource a Name. For names, it is recommended to use the camel case convention and give your resources relevant names.
Because you are creating a resource for orders, prefix the word order with the first three letters in the word resource to name the resource resOrder.
||Leave the Type and Charset fields as is. In this tutorial, you are creating a text resource in UTF-8 encoding.
In the Content text box, enter the following text, which corresponds to the Kabels log file:
2016-12-01T14:36:38|Springbok Space | ORDN051|16040023
Note: The first line of text provides heading names for the different types of data. We will define the following entities: Timestamp, CustomerName, CustomerReference, and CycleNumber.
||Check your data. If you're satisfied, click Save.