This chapter describes how to develop an automation model using a GUI editor and graphically express, using a diagram, logic that corresponds to a service. It also describes development methods for actually collecting and processing data using various services.

The X-UP model development stages are as follows:

1. Develop a model using X-UP Builder.

2. Test a developed model in X-UP Builder.

3. Deploy a developed model on an X-UP Server by using X-UP Builder’s deployment feature.

4. Test a deployed model on the X-UP test web page.

Acquire data from a data source with an invoke used in an automation model.

Each invoke can be processed modularly, and you can compose a model using multiple invokes.

This chapter contains the following sections:

• Model Development Using SAP RFC Invoke

• Model Development Using SAP Table Invoke

• Model Development Using Select Invoke

• Model Development Using Modify Invoke

• Model Development Using Procedure Invoke

• Model Development Using X-UP Invoke

• Model Development Using OData Invoke

• Data Processing Using the DataSet Row Loop Function

• Data Processing Using the Merge Function

• Data Processing Using the Quick Merge Function

• Data Processing Using the XML Parser Function

Model Development Using SAP RFC Invoke

This section describes model development using the SAP RFC function.

An automation model's SAP RFC Invoke development stages described in this section are as follows:

• X-UP Project Creation

• Automation Model and SAP RFC Invoke Creation

• Data Source Creation and Properties Setup

• Invoke Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and SAP RFC Invoke Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [SAP RFC] from the invokes on the palette, and then click the editor to create an SAP RFC invoke.

Data Source Creation and Properties Setup

1. Double-click the generated SAP RFC invoke, or click the [Properties] tab. Click the [SAP RFC] icon to start the wizard.

2. Click the [Create New DataSource] button from the Invoke SAP RFC Wizard.

3. Define a new data source on the New DataSource page. Enter each field value as follows, and click the [Test Connection] button. Verify that a connection is properly established to the datasource.

4. Click the [Finish] button when complete.

5. Select [SAP RFC] as the data source type, and click the [Get Function List] button to call the function list registered on a server.

6. Wildcard (*) search is possible when using [Search Group].

7. When you select a function to be called from the function list search results, its input and output parameter information can be verified.

8. The information appears simultaneously in the SAP RFC and X-UP parameter formats.

9. Click the [Test] button and set an input parameter value in the Define Input Value Wizard. Then click the [Finish] button to verify that the data is properly displayed.

10. You can verify that the input and output parameters were generated after clicking the [OK] button.

Invoke Testing

1. The SAP RFC invoke's input and output parameters are generated based on its test results.

2. Select [InvokeInfo] from the SAP RFC invoke's properties menu, and then click [] to start the test.

3. When the Define Input Value Wizard is displayed, input the test value entered in the Properties menu, and then click the [Finish] button.

4. When the test is successfully completed, you can verify the results in the Test Result window.

Model Testing

1. Select [Connect] from the model editor's palette, and then connect the start and end nodes to the SAP RFC invoke.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

3. The test results are displayed in the Result ParameterSet window when completed.

Model Development Using Select Invoke

This section describes the development method for using an automation model to acquire data from a database using the Select query.

An automation model's Select Invoke development stages described in this section are as follows:

• X-UP Project Creation

• Automation Model and Select Invoke Creation

• Input Parameter and Properties Setup (SQL change)

• Invoke Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and Select Invoke Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [New DataSource] from the X-UP DataSource view on the right side of the screen and run the wizard.

5. Define a new data source in the New DataSource Wizard. Enter each field value as follows, and click the [Test Connection] button. Verify that a connection is properly established to the datasource.

6. Click the [Finish] button when complete.

7. Select [DataSource] from the X-UP DataSource view and import a table list.

8. Drag the ADDRESS_BOOK table from the table list and drop it into the editor.

9. Choose the [Select] invoke to create a select invoke.

10. Alternatively, you can select the [Select] invoke from the palette and then click the editor to create a select invoke.

11. By default, a generated select invoke will have a dataset as an output parameter.

12. The generated Select SQL statement retrieves all columns without a where clause.

Input Parameter and Properties Setup (SQL change)

At this stage, you will set the properties for defining the input parameter and entering information required to obtain data from a data source.

1. Select [DataSet] from the palette, and then click the editor to create a dataset.

2. The default name of a generated dataset is dataset + index. Change the name and alias to IN_DS.

3. Use [Connect] from the palette to link the modified dataset to the Select invoke.

4. When connected, the dataset icon changes to blue and becomes a parameter required as input.

5. Verify the change using the [InOut] tab in Properties.

6. Change the name and alias of the output dataset to OUT_DS and select "out."

7. Select the IN_DS dataset, select [Schema] under Properties, and then add an ID and define the data type.

8. When the select invoke in the image below is connected to the start and end nodes using [Connect] from the palette, the invoke is run during a model test.

9. You can modify the automatically-generated SQL statement by double-clicking the select invoke. In the example, the ID (IN_DS) is received as the input variable, and the ADDRESS_BOOK is retrieved. If the ID is not null during a retrieval, only an ID received as an input variable is retrieved.

$r_title(Before changes)
 select 
	ID,
	NAME,
	COMPANY,
	EMAIL,
	PHONE,
	BIRTHDAY,
	NOTES
 from MIMASHUP.ADDRESS_BOOK

$r_title(After changes)
select 
	ID,
	NAME,
	COMPANY,
	EMAIL,
	PHONE,
	BIRTHDAY,
	NOTES
from ADDRESS_BOOK
<dynamic prepend="where">
	<isNotNull property="IN_DS.ID">
		ID = #IN_DS.ID#
	</isNotNull>
</dynamic>

Invoke Testing

1. To start a test, click the [] preview button located in the upper-right corner of the [InvokeInfo] tab in a select invoke's properties window. Add a row in the Define Test Value window, and enter “5.” Click the [Finish] button.

2. The test results will be displayed in the Result ParameterSet view.

Model Testing

1. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

2. The test results are displayed in the Result ParameterSet window when completed.

3. The [Parameters] and [DataSets] tabs are located at the bottom of the Result ParameterSet view. Verify that a dataset named “OUT_DS” exists as an output parameter.

Model Development Using Modify Invoke

This section describes the development method for changing data in a database using an automation model.

An automation model's Modify Invoke development stages described in this section are as follows:

• X-UP Project Creation

• Automation Model and Select Invoke Creation

• Input Parameter and Properties Setup

• Invoke Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and Modify Invoke Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [New DataSource] from the X-UP DataSource view on the right side of the screen and run the wizard.

5. Define a new data source in the New DataSource Wizard. Enter each field value as follows, and click the [Test Connection] button. Verify that a connection is properly established to the datasource.

6. Click the [Finish] button when complete.

7. Select [DataSource] from the X-UP DataSource view and import a table list.

8. Drag the ADDRESS_BOOK table from the table list and drop it into the editor.

9. Choose the [Select] invoke to create a select invoke.

10. Alternatively, you can select the [Modify] invoke from the palette and then click the editor to create a modify invoke.

11. When creating a modify invoke, a wizard is first executed where you can select columns.

12. Click the [Select All] button, and then click [OK]. By default, a generated modify invoke will have input and output datasets as parameters.

Input Parameter and Properties Setup

1. Click the input dataset and select [General] in the properties window. Change the name and alias to IN_DS.

2. When a modify invoke is created from the palette, the input parameter must be generated manually (No. 1 in the below image), and the IN_DS input parameter's schema must be specified. Click the [Import] button (No. 2 in the below image).

3. The user can directly enter a dataset's column settings by clicking the [Add] button, or the column information can be obtained from a database table or another X-UP or XML file by clicking the [Import] button.

4. In the Import Dataset Schema Wizard, select DB Table as the import source. Select the ADDRESS_BOOK table schema with DB_ORACLE selected as the data source.

5. After changing the name of the input dataset, double-clicking a modify invoke will display the Target DataSet combo box in the Invoke Modify SQL popup window. The input parameters of dataset types are displayed. Select IN_DS from the drop-down menu. Verify that the insert, update, and delete queries are automatically entered.

Invoke Testing

1. To start a test, click the preview button[] located in the upper-right corner of the [InvokeInfo] tab in a modify invoke's properties window.

2. When the Define Test Value window is displayed, enter the data to be used in the modify invoke test.

3. Click the [Add] button and enter the data.

4. Click the [Finish] button when completed.

Refer to the table below for descriptions of transaction processing methods (Action field).

5. You can verify the results in the Result ParameterSet view when testing is successfully completed.

Model Testing

1. Connect the start and end nodes to the modify invoke.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

3. Enter the same test data from "Invoke Testing" and conduct the test.

4. The test results are displayed in the Result ParameterSet window when completed.

5. The [Parameters] and [DataSets] tabs are located at the bottom of the Result ParameterSet view. You can verify that "RESULT0" exists as the dataset output parameter.

Model Development Using Procedure Invoke

This section describes the development method for calling a procedure or function in a database using an automation model.

An automation model's Procedure Invoke development stages described in this section are as follows:

• X-UP Project Creation

• Automation Model and Procedure Invoke Creation

• Invoke Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and Procedure Invoke Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [New DataSource] from the X-UP DataSource view on the right side of the screen and run the wizard.

5. Define a new data source in the New DataSource Wizard. Enter each field value as follows, and click the [Test Connection] button. Verify that a connection is properly established to the datasource.

6. Click the [Finish] button when complete.

7. Select [DataSource] from the X-UP DataSource view and import procedure and function lists.

8. Drag a target from the imported procedure list and drop it into the editor.

9. Alternatively, you can select the [Procedure] invoke from the palette and then click the editor to create a procedure invoke.

10. Click the [Test] button on the wizard.

11. Enter a value into Define Input Value, and then click the [Finish] button.

12. The output value can be verified when the procedure is called.

13. Click the [OK] button to complete the procedure invoke’s input and output parameter setup.

Invoke Testing

1. The procedure invoke's input and output parameters are generated based on its test results.

2. Select [InvokeInfo] from the procedure invoke's properties menu, and then click to start the test.

3. Follow the same invoke testing procedure from "Automation Model and Procedure Invoke Creation" by entering a test value in the properties menu and clicking the [Test] button. The results can be verified when the test is completed.

4. When the test is successfully completed, you can verify the results in the Result ParameterSet window.

Model Testing

1. Select [Connect] from the model editor palette, and then connect the start and end nodes to the procedure invoke.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

3. Enter the same test data from "Procedure Invoke Testing" and conduct the test.

4. The test results are displayed in the Result ParameterSet window when completed.

Model Development Using OpenApi Invoke

This section describes OpenApi model development using the App Store service of Apple Inc.

App Store offers new applications classified according to categories as well as a most-popular list. Data will be provided in the form of the XML-based RSS format. X-UP builder collects XML-formatted data and converts it into standard parameters.

In this section, you will go through the following stages to develop the OpenApi Invoke of an automation model.

• X-UP Project Creation

• Automation Model and OpenApi InvokeCreation

• Data Source Creation and Properties Setup

• Invoke Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and OpenApi Invoke Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when New Model Wizard is completed.

4. Select Open API from the invokes on the palette, and then click the editor to create an OpenApi Invoke.

Data Source Creation and Properties Setup

1. Double-click the generated OpenApi Invoke (1) to start the wizard. Otherwise, click the InvokingInfo tab (2) of the Properties view and click the OpenApi icon’[ ](3).

2. Click create new DataSource [] in the wizard.

3. Define a new data source on the New DataSource page. Enter each field value as below, and click the Test Connection button. Verify that a connection is properly established to the datasource.

4. Click the Finish button after the verification.

5. Select 'OPENAPI_APPLE' among the defined data sources.

6. Enter an appropriate sub-path for the base path and click Test button.

   The sub-path for this example is ‘topfreeapplications/limit=10/xml.’

7. If you succeeds in calling the services, you can see the BODY value as well as values of the HTTP headers, as presented in the second picture below.

8. Click the OK button to designate the tested values as output parameters.

Invoke Testing

1. The OpenApi Invoke's input and output parameters are generated based on its test results.

2. Delete unused values of the HTTP header responses.

3. Proceed with the test by accessing the InvokeInfo(2) tab in the Properties view of OpenApi Invoke(1) and clicking [].

4. When the test is successfully completed, you can verify the results in the Result ParameterSet view. (As you can see in this example, output results will come out in no time if there is no input parameter.)

Model Testing

1. Select Connect from the model editor's palette, and then establish connection from the start, OpenApi Invoke, to the end nod.

2. Right-click on the model editor to display a popup menu. Select Test from the popup menu to test a model.

3. The test results are displayed in the Result ParameterSet window when completed.

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Model Development Using X-UP Invoke

This section describes the development method for calling an X-UP model deployed on a WAS using an automation model.

An automation model's X-UP Invoke development stages described in this section are as follows:

• X-UP Project Creation

• Automation Model and X-UP Invoke Creation

• Data Source Creation and Properties Setup

• Invoke Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and X-UP Invoke Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [X-UP] from the invokes on the palette, and then click the editor to create an X-UP invoke.

5. Double-click the generated X-UP invoke, or click the [Properties] tab. Click the [X-UP ] icon to start the wizard.

Data Source Creation and Properties Setup

1. Click the [Create New DataSource] button from the X-UP Model List Wizard.

2. Define a new data source in the New DataSource Wizard. Enter each field value as follows, and click the [Test Connection] button. Verify that a connection is properly established to the datasource.

3. Click the [Finish] button when complete.

Verify that the data source was successfully designated as XUP_REMOTE.

4. You can verify whether the input and output parameters were successfully generated after clicking the [OK] button.

Invoke Testing

1. Select [InvokeInfo] from the X-UP invoke's properties menu, and then click to start the test.

2. When the test is successfully completed, you can verify the results in the Result ParameterSet window.

Model Testing

1. Select [Connect] from the model editor palette, and then connect the start and end nodes to the X-UP invoke.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

   The test results are displayed in the Result ParameterSet window when completed.

Model Development Using OData Invoke

This section describes the method for developing an automation model that uses an OData invoke.

SAP's NetWeaver Gateway demo site is used in this example.
The demo site is located at the following URL:

Before starting, you must receive authentication to use the SAP NetWeaver Gateway demo system. Please refer to the following URL for detailed authentication information.

An automation model's OData Invoke development stages described in this section are as follows:

• X-UP Project Creation

• Automation Model and OData Invoke Creation

• Data Source Creation and Properties Setup

• Invoke Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and OData Invoke Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [OData] from the invokes on the palette, and then click the editor to create an OData invoke.

Data Source Creation and Properties Setup

1. Double-click the generated OData invoke, or click the [Properties] tab. Click the [OData] icon to start the wizard.

2. Click the [Create New DataSource] button from the Invoke OData Wizard.

3. Define a new data source on the New DataSource page. Enter each field value as follows, and click the [Test Connection] button. Verify that a connection is properly established to the datasource.

4. Click the [Finish] button after verifying the connection.

5. Select [ODATA_GW] as the datasource type, and then click the [Service List] button to call the service list registered on the server.

6. Select a service to be called from the service list results to verify the EntitySet and FunctionImport information exposed to the respective service. You can also check parameter information regarding the I/O.

7. Click the [OK] button, and then select a service.

8. Drag the item to be run from the selected service’s items and drop it into Operations.

9. The information appears simultaneously in the SAP RFC and X-UP parameter formats.

10. Click the [Test] button and set an input parameter value in the Define Input Value Wizard. Then click the [Finish] button to verify that the data is properly displayed.

11. You can verify that the input and output parameters were generated after clicking the [OK] button.

Invoke Testing

1. The OData invoke's input and output parameters are generated based on its test results.

2. Select [InvokeInfo] from the OData invoke's properties menu, and then click [] to start the test.

3. When the Define Input Value Wizard is displayed, input the test value entered in the Properties menu, and then click the [Finish] button.

4. When the test is successfully completed, you can verify the results in the Result ParameterSet window.

Model Testing

1. Select [Connect] from the model editor palette, and then connect the start and end nodes to the OData invoke.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

3. The test results are displayed in the Result ParameterSet window when completed.

Data Processing Using the DataSet Row Loop Function

This section describes the DataSet Row Loop function for running iterative business logic a number of times equal to the number of datasets.

In this example, FLIGHT_LIST will be retrieved using an SAP RFC invoke, and a new dataset will be created with that satisfies certain conditions.

The development stages described in this section for an automation model that uses the DataSetRowLoop function are as follows:

• X-UP Project Creation

• Automation Model Creation

• SAP RFC Logic Creation for Input Parameters

• DataSetRowLoop Function Creation and Event Inclusion

• Output Parameter Setup Using a UserMethod Function

• Function Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

SAP RFC Logic Creation for Input Parameters

1. Select [SAP RFC] from the invokes on the palette, and then click the editor to create an SAP RFC invoke.

1. Double-click the generated SAP RFC invoke, or click the [Properties] tab. Click the [SAP RFC] icon to start the wizard.

2. Click the [Create New DataSource] button from the Invoke SAP RFC Wizard.

3. Define a new data source on the New DataSource page. Enter each field value as follows, and click the [Test Connection] button. Verify that a connection is properly established to the datasource.

4. Click the [Finish] button when complete.

5. Select [SAP RFC] as the data source type, and click the [Get Function List] button to call the function list registered on a server.

6. Wildcard (*) search is possible when using [Search Group].

7. When you select a function to be called from the function list search results, its input and output parameter information can be verified.

8. The information appears simultaneously in the SAP RFC and X-UP parameter formats.

9. Click the [Test] button and set an input parameter value in the Define Input Value Wizard. Then click the [Finish] button to verify that the data is properly displayed.

10. You can verify that the input and output parameters were generated after clicking the [OK] button.

DataSetRowLoop Function Creation and Event Inclusion

1. Select [DataSetRowLoop] from the functions on the palette, and then click the editor to create a DataSetRowLoop function.

2. Use the [Connect] function to connect FLIGHT_LIST1, the SAP RFC Invoke's output parameter, to the DataSetRowLoop function's input parameter.

3. Right-click the DataSetRowLoop function, select [Add Event], and then click [loopEvent] to add an even.

Output Parameter Setup Using a UserMethod Function

1. Add a UserMethod function between the events and connect the function and events.

2. Connect the rowIndex and dataset parameters (automatically generated as event outputs) to the UserMethod function's input parameter.

3. Select and add a dataset from the palette to set the output parameter, and then connect to the UserMethod function's output parameter.

4. Change the name of the generated dataset to FILTERED_FLIGHT_LIST.

5. Add the FILTERED_FLIGHT_LIST dataset's schema as follows:

6. double-click the UserMethod function and enter the following source code into the automatically-moved logic class.

public void userMethod(ParameterSet globalParameterSet, EuserMethodParameters eps) throws AutomationFailException {
	DataSet filteredDataSet = globalParameterSet.getDataSet("FILTERED_FLIGHT_LIST");

	DataSet dataset = eps.getDataSet();
	int month = (dataset.getDateTime(0, "FLIGHTDATE").getMonth());
	// data filter
	if(month == 4) {
		int row = filteredDataSet.newRow();
		filteredDataSet .set(row, "AIRLINE", dataset.getString(0, "AIRLINE"));
		filteredDataSet .set(row, "CONNECTID", dataset.getInt(0, "CONNECTID"));
		filteredDataSet .set(row, "FLIGHTDATE", dataset.getString(0, "FLIGHTDATE"));
	}
}

Model Testing

1. Select [Connect] from the model editor palette, and then connect the SAP RFC invoke, DataSetRowLoop function, and start and ends nodes.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

Data Processing Using the Quick Merge Function

This section describes the Quick Merge function, which amalgamates two datasets obtained from multiple invokes or functions to create a new dataset.

The development stages described in this section for an automation model that uses the Quick Merge function are as follows:

• X-UP Project Creation

• Automation Model and Quick Merge Function Creation

• Dataset Creation for Amalgamation

• Amalgamation Logic Setup

• Function Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and Quick Merge Function Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [Finish] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [Quick Merge] from the functions on the palette, and then click the editor to create a quick merge function.

Dataset Creation for Amalgamation

1. Select [Dataset] from the palette, and then click the editor.

2. The default name for a generated dataset is DataSet. Change the name and alias to DS_BOOK.

3. Click the [] button under [Schema] in the properties, and add the following column information.

4. Connect DS_BOOK and the merge function using the [Connect] button on the palette.

5. Create another dataset following the aforementioned procedure, and change the name and alias to DS_AUTHOR.

6. Click the [] button under [Schema] in the properties, and add the following column information.

7. Connect DS_AUTHOR and the merge function using the [Connect] button on the palette.

Amalgamation Logic Setup

1. Double-click the quick merge function from the editor, or click the [Properties] tab. Click the [Quick Merge] icon to start the wizard.

2. The two input datasets are set for merging by default. Set the key columns as "book_name" for DS_BOOK and "work" for DS_AUTHOR. The other items are set to their default values.

3. Click the [Test] button in the Quick Merge Wizard to test the amalgamation logic.

4. Enter the following values into [Define Input Value], and then click the [Finish] button.

Function Testing

1. The output parameter is generated based on test results.

2. Select [InvokeInfo] from the quick merge function's properties menu, and then click [] to start the test.

3. Follow the same procedure from the above "Amalgamation Logic Setup" by clicking the [Test] button in the wizard. The results can be verified when the test is completed.

4. You can verify the results in the Result ParameterSet view when testing is successfully completed.

Invoke Testing

1. Select [Connect] from the model editor palette, and then connect the start and end nodes to the quick merge function.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

3. Enter the same test data from "Function Testing" and conduct the test.

4. The test results are displayed in the Result ParameterSet window when completed.

Data Processing Using the Merge Function

This section describes the Merge function, which amalgamates datasets obtained from multiple models to create a new dataset.

The amalgamation model development stages described in this section are as follows:

• X-UP Project Creation

• Automation Model and Merge Function Creation

• Dataset Creation for Amalgamation

• Amalgamation Logic Setup

• Merge Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and Merge Function Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [Finish] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [Merge] from the functions on the palette, and then click the editor to create a merge function.

Dataset Creation for Amalgamation

1. Select [Dataset] from the palette, and then click the editor.

2. The default name for a generated dataset is DataSet. Change the name and alias to DS_BOOK.

3. Click the [] button under [Schema] in the properties, and add the following column information.

4. Connect DS_BOOK and the merge function using the [Connect] button on the palette.

5. Create another dataset following the aforementioned procedure, and change the name and alias to DS_AUTHOR.

6. Click the [] button under [Schema] in the properties, and add the following column information.

7. Connect DS_AUTHOR and the merge function using the [Connect] button on the palette.

Amalgamation Logic Setup

1. Double-click the merge function from the editor, or click the [Properties] tab. Click the [Merge] icon to start the wizard.

2. Click [Create Default Merging SQL] to generate a basic amalgamation logic in the SQL editor.

3. Modify the amalgamation logic as follows:

$r_title(Before changes)
select 
	a.id,
	a.book_name,
	a.author,
	b.no,
	b.name,
	b.work
from
DS_BOOK a, DS_AUTHOR b

$r_title(After changes)
select 
	a.id,
	a.book_name,
	a.author,
	b.no,
	b.name,
	b.work
from
DS_BOOK a, DS_AUTHOR b
where a.book_name = b.work

4. Click the [Test] button in the SQL Editor to test the amalgamation logic.

5. Enter the following values into [Define Input Value], and then click the [Finish] button.

Function Testing

1. The output parameter is generated based on test results.

2. Select [InvokeInfo] from the merge function's properties menu, and then click [] to start the test.

3. Follow the same procedure from the above "Amalgamation Logic Setup" by clicking the [Test] button in the SQL editor. The results can be verified when the test is completed.

4. You can verify the results in the Result ParameterSet view when testing is successfully completed.

Model Testing

1. Select [Connect] from the model editor palette, and then connect the start and end nodes to the merge function.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

3. Enter the same test data from "Function Testing" and conduct the test.

4. The test results are displayed in the Result ParameterSet window when completed.

Data Processing Using the XML Parser Function

This section describes how to easily generate datasets or primitive-type data from XML data using the XML Parser function.

Refer to the section Sample XML Required for the XML Parser Function for the XML used in this example.

The development stages described in this section for an automation model that uses the XML Parser are as follows:

• X-UP Project Creation

• Automation Model and XML Parser Creation

• Defining XML Parsing Rules

• Function Testing

• Model Testing

X-UP Project Creation

1. Go to [File > New > X-UP Project] and run the New X-UP Project Wizard.

2. Enter the desired name into the [Project Name] field and click the [Finish] button.

3. Verify that the X-UP project was created as shown in the image below.

Automation Model and XML Parser Function Creation

1. Go to [File > New > X-UP Automation Model] and run the New Model Wizard.

2. Enter the desired name into the [Model Name] field and click the [OK] button.

3. The below screen will be displayed when the New Model Wizard is completed.

4. Select [XML Parser] from the functions on the palette, and then click the editor to create an XML parser.

Defining XML Parsing Rules

1. Double-click the XML parser, or click the [Properties] tab. Click the [XML Parser] icon to start the XML Parser Wizard.

2. Copy the XML data from the section Sample XML Required for the XML Parser Function for data input.

3. Paste the XML strings into the [XML Content] section of the XML Parser wizard.

4. The XML is displayed in [XML Content] as shown below. Click the [Pretty View] button for a more organized view.

5. In addition, the XML is displayed in tree form in the [Parser Info] section at the bottom.

6. Drag the PLANT node iterated in ParseInfo and drop it into the [Parse List] to parse the data.

7. Alternatively, you can click the [Add] button in the upper-left corner by the [Parse List].

8. When the node is added to the [Parse List], the [XPath, Const Column, Condition, and Option] tabs become active next to the [Parse Info].

9. The selected node is automatically assigned to [XPath], and child nodes are included. The information is converted into a dataset.

10. Click the [Test] button to verify the results in the [Preview] area.

11. A dataset named PLANT will be created as an output parameter when the [OK] button is clicked.

12. The dataset schema is configured with the name of the child node that corresponds to XPath.

Function Testing

1. Select [ParserInfo] from the XML parser's properties menu, and then click [] to start the test.

2. The XML that was used to define XML parsing rules is automatically entered when the Define Input Value wizard is executed.

3. Click the [Finish] button.

4. When the test is successfully completed, you can verify the results in the Result ParameterSet window.

Model Testing

1. Select [Connect] from the model editor palette, and then connect the start and end nodes to the XML parser.

2. Right-click on the model editor to display a popup menu. Select [Test] from the popup menu to test a model.

The test results are displayed in the Result ParameterSet window when completed.