www.usoft.com To www.usoft.com

Topics started by frank.rijnders

127 Topics

F
frank.rijnders
published in BIRT reporting

BIRT Step 6: Parameterisation of the BIRT report definition

BIRT obtains  the data it requires data from USoft using the USoft Rules Service. The JDBC connection string to the USoft rules service contains a hostname and port number. To facilitate easy deployment of this report definition where multiple data sources are present, you can parameterize the definition to simplify configuration changes. You can create one report parameter that contains both  host name and port number variables. You can then use this parameter in the connection string of each data source that points to a USoft Rules Service. To do this follow the steps below:1. In the BIRT Report Designer’s Data Explorer, right-click Report Parameters, and choose New Parameter from the resulting menu.2. The New Parameter dialog appears. In the Name field of this dialog, type the name HOSTPORT and press OK.Your BIRT design now contains a HOSTPORT Report Parameters item.3. To use this new parameter in your data source connection string, double click the appropriate data source item in t

270
F
3 years ago
F
frank.rijnders
published in BIRT reporting

BIRT Step 5: Call the BIRT component to generate the report

To call the BIRT off-the-shelf component, and generate a report:Start the USoft application, and open the SQL Command window from the Tools menu.In SQL command execute one of the following commands:SELECT birt.generatepdf ('path-to-report-definition', 'path-to-output-file')Or INVOKE birt.generatepdf WITH SELECT 'path-to-report-definition', 'path-to-output-file'Wherepath-to-report-definition is the location of the BIRT report definition file created using the BIRT Report Designer. path-to-output-file is the location of the report that you wish to generate. GENERATEPDF can be replaced by one of the following methods, if an output file with a format other than Portable Document Format (PDF) is required.GENERATEDOC for a Microsoft Word document GENERATEHTML for HTML GENERATEXLS for a Microsoft Excel spreadsheet.Optionally, to facilitate easy deployment of this report definition where multiple data sources are present, you can parameterize the report definition and use variables in the comm

260
F
3 years ago
F
frank.rijnders
published in BIRT reporting

BIRT Step 4: Start the USoft Rules Service

The Rules Service is started and configured using the Rules Service project in the USoft Binder. Refer to the online help supplied with the Rules Service item for details of how to configure and start the Rules Service.Continue with Step 5: Call the BIRT component to generate the report.

140
F
3 years ago
F
frank.rijnders
published in BIRT reporting

BIRT Step 3: Import and configure the BIRT off-the-shelf component

To import and configure the BIRT off-the-shelf component:1. In USoft Definer, choose Define, Teamwork, Object Shopping, Import Off The Shelf from the menu bar and import the BIRT component from GITHUB.2. The BIRT component has now been added to the list of imported J2EE components in the catalog:7. Double-click the BIRT item to open the component configuration screen.8. Change the constructor of the BIRT component to:SELECT ' c:\Java\BIRT\runtime\ReportEngine', 'C:\temp', 'images'Where:c:\Java\BIRT\runtime\ReportEngine is the path to the BIRT Runtime ReportEngine folder. (Note that this make be different on your system, depending upon where you installed the BIRT software). This parameter is also used to find and load the external JAR files. C:\temp is a folder that BIRT can use to store temporary files. images is the  image URL prefix. This is optional; this parameter allows you to alter the image source URL when creating HTML reports)9. Commit your changes.Continue with Step 4: Start

210
F
3 years ago
F
frank.rijnders
published in BIRT reporting

BIRT Step 2: Create a BIRT report definition file

The report definition file contains all the information required to connect to the data source, to create a data set, and and to format the data in the data set. There are three steps associated with the creation of a report definition file:Create a data source – this step is described in this online help . Create a dataset Format the data of the datasetDataset creation and formatting are described in the BIRT Report Developer GuideCreating a Data SourceThe data source must be specified in the report definition. The BIRT Report Designer must be made aware of the location of the USoft JDBCClasses.jar file. To do this, use the following procedure.1. Start the BIRT Report Designer by executing birt.exe from the BIRT installation location, e.g. c:\birt_372\birt.exe.2. Open an existing report file, or if this is the first time you have used the BIRT Report Designer, from the BIRT Report Designer’s File Menu, choose New, followed by New Report. The New Report dialog will be displayed.3. Spec

530
F
3 years ago
F
frank.rijnders
published in BIRT reporting

BIRT Step 1: Download and Install BIRT Software

To download and install Eclipse BIRT software on your system:1. Download the ZIP file for the Eclipse BIRT RCP Report Designer (birt-rcp-report-designer-3_7_2.zip, 68MB) from:http://download.eclipse.org/birt/downloads/2. Extract the contents of the ZIP file to a suitable location e.g. c:\birt_372.3. Download the ZIP file for the  Eclipse BIRT Runtime environment (birt-runtime-3_7_2.zip, 104MB) from:http://download.eclipse.org/birt/downloads/4. Extract the contents of this ZIP file to the location used for the Report Designer e.g. c:\birt_372\. A runtime folder will automatically be added to this location.You can start now start the BIRT Report Designer by executing c:\birt_372\birt.exe. Refer to the Eclipse BIRT Report Developer Guide supplied as online documentation with the Report Designer for a description of the BIRT system, and for details of how to use it.Continue with Step 2: Create a BIRT report definition file. 

59310
F
3 years ago
F
frank.rijnders
published in BIRT reporting

BIRT reporting

BIRT (Business Intelligence and Reporting Tools) is an open-source Eclipse and Java-based reporting system. Eclipse BIRT is supported by USoft using an off-the-shelf component named BIRT. Using BIRT, you can generate reports in various formats, for example: PDF, HTML, DOC, and XLS. BIRT includes features making it possible to add graphs (SVG is possible). Data can be imported from a variety of data sources, such as JDBC, XML, (CSV) Flat Files, etc. USoft supports Eclipse BIRT version 3.7.2 and higher. For more information about Eclipse BIRT, visit http://www.eclipse.org/birt/phoenix/Eclipse BIRT is not shipped with the USoft software distribution. However, you can download Eclipse BIRT components from the Eclipse website. To use BIRT with USoft you need the Eclipse BIRT runtime environment, and to design BIRT reports you need the Eclipse BIRT Report Designer. You will also need to import and configure the USoft BIRT off-the-shelf component, which is shipped with the USoft software dist

850
F
3 years ago
F
frank.rijnders
published in Off-the-shelf components

Importing off-the-shelf components and models

Off-the-shelf components and models are ready-made, downloadable components and models that can be used and changed at will. They provide useful components to perform various tasks, demos to show and explain functionality, and small models which can be used as starting point or can be added to an existing repository.To use them, all you need to do is to import their definitions into your USoft repository.How to importTo import an off-the-shelf component or model from GITHUB into your repository:1. In USoft Definer, choose Define, Teamwork, Object Shopping, Import Off The Shelf from the menu bar.The "Import Off the Shelf Components and Models from GITHUB" dialog opens. The dialog shows all components and models which are available in the GITHUB. Each entry has a Type (for example 'C# component', 'Demo', 'Model') and an extended description of what it does.2. Select the component or model you want to import by clicking on the left-hand border of the grid control. The selected row is high

980
F
3 years ago
F
frank.rijnders
published in DotNet components

Component references and inheritance for dotNet

You can have a dotNet component 'A' refer to a dotNetcomponent 'B'. Such a reference allows you to use the methods and variables of 'B' in calls to 'A'.It is also possible to have a component 'C' inherit another component 'D'. This inheritance causes 'C' to contain the methods and variables of 'D' implicitly.Component refers to other componentTo have a dotNet component 'A' refer to a dotNet component 'B', all you need to do is to declare an object of type 'B' in the Program Source of component 'A', as the Example shows.You cannot have reference circles. If 'A' refers to 'B' and 'B' refers to 'X', then 'X' cannot refer to 'A'.ExampleComponent A:using System;public class A{ public B b; public A(){ b = new B(); } public int AddOne(int val){ return val + 1; } public int AddTwo(int val){ return b.AddTwo(val); }}Component B:using System;public class B{ public B(){} public int AddTwo(int val){ return val + 2; }}To test, try these calls:select A.AddOne(1

290
F
3 years ago
F
frank.rijnders
published in DotNet components

DotNet-USoft data provider

There are two ways you can use application data in a .NET component defined in USoft Definer:By passing application data as parameters to the component. By executing a query, from the .NET code, to the running Rules Engine using a .NET-USoft data provider. This provider is called "REDataProvider" and is delivered in assembly file "REDataProvider.dll". "REDataProvider" has the following classes:Class Description USoftCommand Represents a SQL statement to execute against a running Rules Engine. Inherits from DbCommand USoftConnection Represents a connection to a running Rules Engine. Inherits from DbConnection USoftDataReader Provides a way of reading a forward-only stream of rows from a running Rules Engine. Inherits from DbDataReader USoftParameter Represents a parameter to a USoftCommand. Inherits from IDataParameter USoftParameterCollection Represents a collection of parameters associated with a USoftCommand. Inherits from ArrayList, IDataParameterCollection. To con

460
F
3 years ago
F
frank.rijnders
published in DotNet components

C# component Example 2: Tracer

Microsoft supplies debugging tools under the name of Sysinternals at the following URL:http://technet.microsoft.com/en-us/sysinternals/defaultYou can download a tool named dbgview.exe from this location. You can use this tool to catch trace information from a .Net application used in a USoft application.The following example illustrates how you could make use of dbgview.exe.1. Download and install dbgview.exe.2. Create a file with the extension .cs, e.g. myTrace.cs.3. Type the following code into the myTrace.cs file:#define TRACEusing System;using System.Diagnostics;class TRACE{ public static void write( String message ) { Trace.AutoFlush = true; Trace.Indent(); Trace.WriteLine( message); Trace.Unindent(); Trace.Close(); }}4. In USoft Definer, create a new DotNet Component named TRACE5. Provide the full path and filename of the file created in step 2 as the Program Source, e.g. C:\Program Files\myCode\myTrace.cs6. Specify the Assembly referen

320
F
3 years ago
F
frank.rijnders
published in DotNet components

C# component Example 3: External DLL

This example shows how you can call from your USoft application a method from a C# .NET class library that is made available by an external DLL.1.    In USoft Definer, from the menu, choose Define, RDMI, dotNet Components, C# Components from the Define menu. The "C#t Components" window opens.2.    Create a simple .NET C# component, by setting Name = MYCLASS and Program Code =using System;using System.Text;class MYCLASS{ public static String SimpleClass(String instr) { return "ok" + instr; }} The Assembly References field should be left empty at this stage.3. Press Commit. USoft compiles this code.4. Press the Check button. The RDMI interface is generated by USoft. If there are already methods and parameters defined, you will be asked if you want to generate a new RDMI interface (the old methods and parameters will be overwritten) or if you just want to check the existing methods and parameters5. In the Application, check the component using the following command in

730
F
3 years ago
F
frank.rijnders
published in DotNet components

C# component Example 1: Event log

This example shows how you define a .NET component that writes to a Windows event log.1.    In USoft Definer, from the menu, choose Define, RDMI, dotNet Components, C# Components from the Define menu. The "C#t Components" window opens.2.    Set Name = EVENTLOG.3.    In the Program Source field, provide the source code of the component:using System;using System.Text;using System.Diagnostics;class EVENTLOG{ public static void write(String message) { EventLog log = new EventLog(); log.Log = "USoft"; log.Source = "RDMI"; log.WriteEntry(message); log.Close(); }}4. Set Assembly References =System.dll This field contains the .NET framework DLL names of libraries referenced by the code above. In this case the System library is referenced which resides in System.dll in the .NET framework installation folder. All the types that you are using in a C# program are defined in assemblies. Add a reference to the assembly that you use in the Assembly Referenc

260
F
3 years ago
F
frank.rijnders
published in DotNet components

DotNet (.NET) components

DotNet (.NET) is a Microsoft software framework that supports of a variety of programming languages. These include C#, F#, C++, (a modern version of) Visual Basic, and a Microsoft variant of JavaScript called JScript.Class libraries in .NET can often be used from multiple languages. Not every library is available in every context. .NET comes in multiple versions and variants, including .NET Core (for mobile and Linux platforms), but also versions for Windows machines that offer more extended functionality, for example ASPX.USoft offers extensive functionality for integrating .NET code with the USoft Rules Engine. To do this, in USoft Definer, you define a .NET component. .NET components in USoft are RDMI components. As such, they may be called from many USoft SQL-based contexts, including constraints that implement rules.A .NET component will raise errors if you started the USoft executable (eg., Usd.Exe, or if started from USoft Binder, usbinder.exe) from an abbreviated file path, eg.

1050
F
3 years ago
F
frank.rijnders
published in RDMI Components

Component error handling

When a method is being invoked, RDMI supports the principle of exception handling for reporting errors. Subsequently, if the chosen middleware supports it, a message can be passed on with the exception to explain in detail what has gone wrong. Following the exception, the rules engine will display the returned message and will discontinue the transaction.Here is a Visual Basic example of raising an exception.Public Function SquareRoot(par1 As Integer) As Double If par1 < 0 Then Err.Raise vbObjectError + 1050, "USMath", "Value must be positive." Else SquareRoot = sqr(par1) End IfEnd FunctionShowing or suppressing component error messagesWith RDMI, the new Show Component Middleware Errors application behavior property is introduced. By setting this property, developers can decide whether or not error messages returned by the COM middleware component should be displayed. A USoft message will be displayed in any case.To show or suppress component error messages:1. Open t

240
F
3 years ago
F
frank.rijnders
published in RDMI Components

Calling a component

Where to call a component from?You can call a component from most USoft contexts where SELECT is permitted:Constraint SQL SQL in SqlScript() SQL Command dialog SQL in USoft Batch Server Decision SQL Remote Rules Service APIThe INVOKE clause can NOT be used in the following contexts:Graphical SQL DefinerIn Extra Query statements in the Windows Designer, the INVOKE clause may only be used in the top-level SELECT output list and in subqueries.How to call the component?You can call an RDMI component from a USoft SQL context by using one of two constructs:The USoft-proprietary INVOKE keyword. Function call syntax.Either way, the RDMI call may appear in a number of different contexts, for example:As an independent statement. In a nested manner, in association with another INVOKE clause. In association with a SELECT clause. In a WHERE condition. In the output list of a SELECT statement. In a subquery.In general, there are two different ways to access a component's functionality:By calling a m

680
F
3 years ago
F
frank.rijnders
published in RDMI Components

Component for exporting a data set to a CSV file

The following step-by-step instructions are for creating a .NET component that exports a set of data to a CSV file. This is an example of how to create and use the aggregate protocol.For simplicity, the .NET code assumes that data received does not contain a comma.The component expects data from the following columns of the SCHEDTOUR table: SCHEDTOUR_ID, DESTINATION, TOUR_TYPE, START_DATE, RETURN_DATE, PRICE.Creating a .NET component for exporting records to a CSV file1. Choose Define, RDMI, dotNet Components from the USoft Definer menu. The DotNetComponents window opens.2. Provide a Name for your new component, in this case: CSV.3. In the Program Source field, provide the source code of the component:using System;using System.Text;using System.IO;class CSV{ string csvFileName = null; StringBuilder csv = new StringBuilder(); public long fileExportExe(Nullable<Int32> id, string destination, string tourType, Nullable<DateTime> startDate, Nullable<DateTime> returnD

440
F
3 years ago
F
frank.rijnders
published in RDMI Components

Aggregate protocol

The aggregate protocol is a way of interacting with an RDMI component that involves passing a multi-row data set to the component and letting it return a single-record or single-value result. With the aggregate protocol you can:Produce a Word document, Excel spreadsheet, or CSV file by concatenating data in a multi-row data set.Feed a multi-row data set to an optimisation algorithm that produces a single value as its outcome, then continue processing by catching and processing that value.How the aggregate protocol worksFirst you need to make sure your RDMI component has one or more associated aggregate protocols. Each protocol designates one method as its EXE method, and another method as its FETCH method.Next, instead of calling a method of the component directly, you call an aggregate protocol name. An INVOKE ... WITH SELECT ... statement is processed as follows if the INVOKE calls an aggregate protocol name:1. Execute the SELECT statement.2. Create an instance of the component.3. Fe

280
F
3 years ago
F
frank.rijnders
published in RDMI Components

Component querying a CSV file

This example shows how to create a component table that returns data from a CSV file as if it were a database table with multiple rows: a component table mimics the behaviour, or part of the behaviour of a database table but is not itself in the database.The component table uses an underlying .NET component that uses the query protocol to interpret file contents as a multi-row data set.The example component expects a .CSV input file with the following structure: ID, DESTINATION, TOUR_TYPE, START_DATE, END_DATE, PRICE.ExampleHere is an input file called C:\Temp\schedtour.csv that demonstrates the data format expected by the example component:146,AUSTRALIA,ISLAND SUNTANNER,21-3-2020 11:59:01,1-4-2020 11:59:01,2500145,AUSTRALIA,ISLAND SUNTANNER,20-11-2019 11:59:01,1-12-2019 11:59:01,2500144,BRAZIL,RAINFOREST RIDE,16-10-2021 11:59:01,29-10-2021 11:59:01,3000143,BRAZIL,RAINFOREST RIDE,15-9-2021 11:59:01,28-9-2021 11:59:01,3000142,BRAZIL,RAINFOREST RIDE,15-8-2021 11:59:01,28-8-2021 11:59:01,

280
F
3 years ago
F
frank.rijnders
published in RDMI Components

Component querying multiple CSV files

This is a variation on Example 1. Instead of querying a CSV file identified by a hard-coded filepath, a column is added to the component table. This allows the user, at query time, to identify the CSV file to be queried.ExampleHere is an input file called C:\Temp\schedtour.csv that demonstrates the data format expected by the example component:146,AUSTRALIA,ISLAND SUNTANNER,21-3-2020 11:59:01,1-4-2020 11:59:01,2500145,AUSTRALIA,ISLAND SUNTANNER,20-11-2019 11:59:01,1-12-2019 11:59:01,2500144,BRAZIL,RAINFOREST RIDE,16-10-2021 11:59:01,29-10-2021 11:59:01,3000143,BRAZIL,RAINFOREST RIDE,15-9-2021 11:59:01,28-9-2021 11:59:01,3000142,BRAZIL,RAINFOREST RIDE,15-8-2021 11:59:01,28-8-2021 11:59:01,5500Step 1: .NET component for retrieving data from multiple CSV files1. Choose Define, RDMI, dotNet Components from the USoft Definer menu. The DotNetComponents window opens.2. Provide a Name for your new component, in this case: CSV.3. In the Program Source field, provide the source code of the compo

120
F
3 years ago
F
frank.rijnders
published in RDMI Components

Query protocol, component table

The query protocol What is the query protocol? How does the query protocol work? Methods Query protocol association Stateful component Component tables Component tables, definition Component tables, extended query conditions Component tables, features and limitations Component tables, error handling The query protocolWhat is the query protocol?The query protocol is a way of interacting with an RDMI component that involves passing a single row of data to the component and letting it return multiple columns and rows.The query protocol lets you present data from external sources to the Rules Engine as if it were multi-row data in a relational table.The typical way to achieve this is to build a component table. Your USoft application can use that component table (in constraint SQL, batch SQL, SQL in a GUI layer...) as if it were a normal database table. How the component table handles its data is programmed in the underlying component that uses the query protocol. The component tab

720
F
3 years ago
F
frank.rijnders
published in RDMI Components

Components: Standard protocol

The standard protocol is the default way of interacting with an RDMI component. The RDMI component is treated as a procedure that you call by (optionally) passing a single set of values as input parameters (if applicable). The input data may consist of hard-coded values or values found in a single row in a table.The method typically returns a regular return value. In addition, possibly, it returns one or more output parameters.How the standard protocol worksWhen you call a method using the standard protocol through an INVOKE ... WITH SELECT ... statement, the values from the record(s) retrieved by the SELECT (if any) are passed as input parameters to the method.Such an RDMI call is implemented by going through these steps:1. Fetch a record from the SELECT.2. Create the RDMI component.3. Execute the method and catch any Out parameters. Return the record to the calling application.4. Destroy the component.5. Fetch the next record from the SELECT, etc.In this process, the component is des

80
F
3 years ago
F
frank.rijnders
published in RDMI Components

How many times a called component is executed?

The INVOKE clause is a SQL statement. It is executed under exactly the same conditions as a SQL statement without INVOKE.How many times a component is invoked depends on a combination of things, especially on the SQL syntax construction, the context in which it is executed, and the protocol used. The application developer needs to be aware that not all combinations of input and output are appropriate in all contexts.If the INVOKE clause is used independently, the component is invoked once. In the INVOKE ... WITH SELECT ... construction, INVOKE is executed as many times as there are records in the result table of the SELECT statement. In the INVOKE ... WITH INVOKE component.method() construct, the first INVOKE is invoked once. In the INVOKE ... WITH INVOKE component.query-protocol() construction, the first INVOKE is executed once for every record returned by the query protocol.Example 1: INVOKE in a restrictive constraintSuppose, the SQL statement of a constraint has SyntaxINVOKE    com

120
F
3 years ago
F
frank.rijnders
published in RDMI Components

Constructor SQL

The constructor of a component is a method that is called at the moment that the component is created. The constructor is used primarily for initialization purposes.The constructor SQL is executed at the moment the Rules Engine creates a component. The outcome of the constructor SQL, which is a SELECT or INVOKE statement, will be passed to the constructor method. The constructor method is a method of the component with the same name as the component.The advantage of the constructor SQL is that it gives you the opportunity to create a much more flexible architecture. Some global settings of the component do not need to be made in the component itself, but can be selected from the application tables or from an external component.For example, instead of hard-coding a connection string in an external component, the connection string can be retrieved from a database table and passed on to the constructor method:SELECT    t.valueFROM      user_configuration tWHERE     t.user_name = USERAND  

130
F
3 years ago
F
frank.rijnders
published in RDMI Components

Component state

On a component's State tab, you can determine when the component is constructed and when it is destroyed. You can also set what functionality it supports:Stateful Component, LifetimeRDMI components can be stateless or stateful. This is determined by Stateful Component (Y/N).A stateless component does not have a setting for Lifetime.A stateful component has a Lifetime setting. This setting is either Transaction, User session, or Engine session.In place of the “User session” and “Engine session” options, USoft 9.x had a single option Lifetime = Session, with the meaning of the current “Engine session” option.When is a component constructed and when is it destroyed?When a Rules Engine invokes a method of a stateless component, it checks if a constructor method exists and if so, calls that constructor method. If the constructor method has parameters, these are supplied by the constructor SQL. Then the invoked method is called. The component is destroyed as soon as this method finishes exec

390
F
3 years ago

Badge winners

Show all badges
Terms & ConditionsCookie settings