Version 9.6
 —  Getting Started  —

Working with the Demo Applications


The Instant Demo

Note:
When using a replay file, it is possible to navigate from one screen to the next by pressing ENTER in each web screen. Clicking on buttons which execute paths will work only if the replay file contains the relevant path navigation recorded and the session screen is in the relevant starting point to execute the path. If this is not the case, the path will fail and the user will receive an error from the web application.

When using transformations it is important to notice the order in which the transformations appear in the screen editor (Transformations tab). Transformations can change the way ApplinX perceives a host screen. If, for example, the first transformation hides a certain text on the screen and the second transformation searches for that text pattern in order to replace it with a link then the second transformation will never find a match for that pattern since it has been removed by the first transformation. So always keep in mind, the order of the transformations in the screen editor will be the order in which they will be executed.

template.jsp/template.master

Refer to Customizing the Default Template in the Web Application Development documentation for a detailed explanation on how to change the default template.

Screen Name: Login

Host Screen

graphics/instantdemologin1.png

Screen in Web Application

graphics/instantdemologin1a.png

Note:
The sections that are referred to below can be found in the Designing and Developing an Application documentation.

Screen Name: InsuranceMenu

Host Screen

graphics/instantdemoimenu1.png

Screen in Web Application

graphics/instantdemoimenu1a.png

Note:
The sections that are referred to below can be found in the Designing and Developing an Application documentation.

Screen Name: BrowseCustomers

Host Screen

graphics/instantdemobrowsecust1.jpg

Screen in Web Application

graphics/instantdemobrowsecust1a.png

Top of page

The Composite Demo

Note:
When using a replay file, it is possible to navigate from one screen to the next by pressing ENTER in each web screen. Clicking on buttons which execute paths will work only if the replay file contains the relevant path navigation recorded and the session screen is in the relevant starting point to execute the path. If this is not the case, the path will fail and the user will receive an error from the web application.

template.jsp/template.master

Refer to Customizing the Default Template in the Web Application Development documentation for a detailed explanation on how to change the default template.

JSP

In this template we use these panels (that can be overridden by specific pages):

.NET

In this template we use these panels (that can be overridden by specific pages):

Screen Name: Login

graphics/compositelogin.png

Tasks

Refer to the following sections in the Web Application Development documentation:

Screen Name: Browse Proposals

graphics/compositebrowseproposal.png

Tasks

Refer to the following sections in the Web Application Development documentation:

Screen Name: ModifyProposal1

graphics/compositemodifyp.png

Tasks

Refer to the following sections in the Web Application Development documentation:

Screen Name: BrowseCustomers1

graphics/compositebrowsecustomer.png

Tasks

Refer to the following sections in the Web Application Development documentation:

Top of page

The SOA Demo

.NET and JSP implementation can be done in many ways. This demo includes examples of one way to implement the tasks. For example, in one of the tasks below, we demonstrate how to display data collected by the procedure client. To do this we use the framework. In .NET, this can also be implemented using .NET datagrid.

The following lists the different typical tasks that we have demonstrated in the SOA application included with the ApplinX installation. Next to each task, the entities involved with this task are detailed. This enables you to further explore the configuration of each of these entities.

  1. Identify and define host screens in the ApplinX repository. Refer to Screens in the Designing and Developing an Application documentation.

  2. Create a connection pool with a connection information set (for offline use). Refer to Connection Pools and Connection Information Sets in the Designing and Developing an Application documentation.

    1. Set the pool size as required.

    2. Set a connection information set when required (SOADemo includes connection information sets that allow the application to run in offline mode).

    3. Set navigation rules:

      1. Create an initialization path for the pool that initializes each new connection in the pool. This path should finish in the "Initial screen", otherwise the initialization will fail.

      2. Set the initial screen a connection should wait on.

      3. Create and set a recycle path to recycle connections in the pool.

      4. Create and set a termination path for properly terminating a connection in the pool.

    As you may have noticed, the SOADemo repository contains three connection pools. This is for the sole reason of enabling the application to retrieve results in offline environments (that do not have connectivity to Software AG's network). All three pools share the same setting (pool size and navigation settings), but differ in their connection information sets. To enable offline execution of the application, each procedure has been executed with its own replay file (set in its connection information set), whereas, online execution requires no replay file at all.

  3. Collect data from multiple screens. Refer to Collecting Data from Multiple Host Screens in the Web Application Development documentation.

    1. Create a path procedure which collects table data (refer to the Browse_All_Customers path procedure). Refer to Creating a Path Procedure in the Designing and Developing an Application documentation.

      1. Assign a connection pool to start from the relevant screen.

      2. Create a While loop that checks if an "End of data" message appears on the screen, marking the table's end.

      3. For every table instance: Collect the tabular host screen data and page down for the next instance.

    2. Create a path procedure which collect data from multiple screens (refer to the GetCustomerByID path procedure). Refer to Creating a Path Procedure in the Designing and Developing an Application documentation.

      1. Assign a connection pool to start from the relevant screen.

      2. Add an input to allow the user to specify which customer details they wish to retrieve.

      3. Navigate to the Details screens and map host fields to the procedures' output.

    3. Assign procedures to procedure groups. Refer to Assigning a Procedure to a Procedure Group in the Designing and Developing an Application documentation.

    4. Generate a procedure client from the procedure group (refer to DemoINS procedure group in the demo repository). Refer to Procedure Clients in the Designing and Developing an Application documentation.

  4. Bind web controls to procedure response (output). Refer to Binding Procedure Outputs to an ApplinX Framework Based Web Page in the Designing and Developing an Application documentation.

    1. For each procedure, create a JSP/ASPX page with controls which match the procedure output.

    2. Fill the form (using gx_fillForm).

Top of page