User Guide

This user’s guide is designed to help understand the functionalities and operations of “TecDawg: Template Construction, Service Discovery and Web Process Generation” tool.

 

After installing the respective software, for running the tool, the user need to type the following command in the directory that contains the classes for the tool.

 

java –classpath %BCP%;%UDDI%;%JENA%;%WSD%;XIN%;. MainWindow

 

BCP - includes the jar files of BPWS4J

JENA – includes jar files of Jena

WSD – includes jar files of WSDL4J

XIN – includes jar files of Xindice

UDDI – includes jar files of UDDI4J

                       

Before using the tool, it is required to start the start the required UDDI registries (if needed).

 

Operating the tool

It should be noted that this tool could be used for “Template Design” and “Process Composition”

 

Template Design

The template can be designed in three ways.

 

Concrete Web Service:

  1. Select the ADDWEBSERVICES tab from the GUI.

  2. The following fields appear on the GUI

  3. After entering corresponding details in these fields click on the SAVE tab.

 

Interface:

Interface Implementation can be done by two methods

 

Method1: To be used when the tModel id for a particular type of interface is known.

  1. Select the ADDACTIVITYINTERFACE tab from the GUI.

  2. The following fields appear on the GUI

         3.   After entering corresponding details in these fields click on the SAVE tab.

 

Method2: To be used when you want to select a particular type of interface from a list of interfaces in the repository.

  1. Select the INTERFACEBROWSER tab from the GUI.

  2. The following fields appear on the GUI

  3.   After entering corresponding details in these fields click on the SAVE tab.

 

Semantic Template:

  1. Select the ADDSEMANTICACTIVITY tab from the GUI

  2. The following fields appear on the GUI

  3. After entering corresponding details in these fields click on the SAVE tab

 

Process Composition

Process Composition assumes that the WSDL file of the process and the template for the process is already present.

The steps for “Process Composition” are as follows.

1.       Select the PROCESS NAME tab from the GUI. This step is required to initialize all the required details. The following fields appear on the GUI after selection

·         Process Name: Enter the name of the Process

·         URL for WSDL of process: Specify the URL of the WSDL file of the process.

·         Operation Name in process WSDL: Specify the name of the operation for which the process is to be generated.

·         Read Details: Click on Read Details after entering all the details.

 

2.       Select SERVICE SELECTION tab from the GUI. This step is required for selecting a particular service for a particular activity. The following fields appear on the GUI after selection

·         Update Activities: Click on Updates Activities so that all the activities that needed to be discovered are updated.

·         Select: Click on Select, this lists the activities from which on can be selected.

·         List Services: Click on List Services, this lists the services for the selected activity along with the Operation Name, WSDL, Ranking value for each of the services.

-Operation Name: Displays the operation name of the service selected to be used for the selected activity

-WSDL: Displays the WSDL URL for the service selected

-Ranking value: Displays the ranking value for the selected activity.

·         Select Services: Select a particular service from the list and click on Select Services.

·         This procedure can be repeated for other activities.

·         After selecting services for all the activities, click on SAVE DETAILS tab which will save all the details in a file called “activities.list”.

 

3.       Select DATA FLOW tab from the GUI. This step is required for establishing the data flow from one activity to another. The following fields appear on the GUI after selection

·         Load Activity: Click on Load Activity, this loads all the activities

·         Source Activity: Click on Source Activity, this loads the output messages of all the activities except for receive where in it loads the input messages.

·         Target Activity: Click on Target Activity, this loads all the input messages for all the activities except for reply where in it loads the output messages.

·         After selecting the Source Activity and Target Activity click on SELECT AND ASSIGN. This creates a data flow from the source activity to the target activity.

·         The data flow is represented in five columns namely Source From Target To Expression.

·         If you desire to give a constant as an input to a particular activity, click on the FROM column and delete the details in it and enter the XPATH expression and check in the Expression box.

·         Press SAVE and details of the dataflow are saved in a file called SerializedAssignmentDetails.

 

4.       Select PROCESS VARIABLES from the GUI.

Executable process variables should carry assignments. This is the requirement of the BPEL4WS specifications. Therefore unassigned process variables in the template have to be assigned to values ( output of Web services ) to generate executable process.

The following fields appear on the GUI after selection

·         UPDATE VARIABLES and ACTIVITIY: Click on Update Variables and this updates the variables and activities.

·         SELECT ACTIVITY: Select a particular activity for which you want to assign variable(s). The output messages for this activity are displayed.

·         Select an output message to assign to the variable.

·         SELECT VARIABLE: Select the required variable.

·         ASSIGN: Click on ASSIGN, this assigns the selected output to the selected variable.

·         Repeat the same procedure for other variables and activities

·         SAVE: Click on SAVE, this will save all the assignment details to a file called SerializableVariableAssignmentDetails.

 

5.       Select GENERATE PROCESS

This generates the process taking into account the template and the WSDL file specified and the Data Flow constructed and the variable assignments done.

 

There are few other tabs on the GUI, which have the following functionalities.

·         View BPEL Tree: This tab on the GUI gives a view of the process tree that is generated.

·         List Activities: This tab on the GUI lists all the activities present

·         List Ontology: This tab on GUI lists all the ontologies present

·         View Template: This tab on the GUI displays the template used.

·         View Process WSDL: This tab on the GUI displays the WSDL of the process.

·         Control Flow: Under construction.

 

After the process is generated the output is in the form of two files called the generatedBPEL_final.bpel and utils.wsdl and two intermediate files namely the intermediateBPEL.xml and generatedBPEL_initial.bpel. The intermediateBPEL.xml has the skeletal structure of the process. The generatedBPEL_initial.bpel has the generated process but with redundancies with respect to namespaces, containers, partners etc.  The generatedBPEL_final.bpel has the generated process without the redundancies. The utils.wsdl has the service link types of the services used in the generated process.