=========================================================================

content

Demo users [Details]

DAS3 Cluster [Details]

Full deployment and PoC test [Details]

Microsoft Windows users [Details]

For workflow components developers here are examples of module developed in C++, java, python and Legacy Application [download]

========================================================================

DEMO users [Table of Contents]

Your can try to run a simple workflow using our demo tesbed. You just need to click on the following link [start]

This will start the wsvlam composer as a web start application. The first time you run the web start application, a configuration window will popup showing the default configuration and the default locations, just press the Ok button.

When the composer starts, you can follow the instructions described in step 5 to run a demo without graphical output and step 6 to run demo with graphical output

========================================================================

Use the DAS3 clusters [Table of Contents]

Pre-requisites:

1. An account on the DAS3 clusters:

2. Valid grid credentials

3. The variable environment VLAM_INSTALL must be added to your default environment

   WS-VLAM can be loaded as a module in DAS3:

   add the following line to your .bashrc (bash users) or .cshrc (tshell users)

   module add wsvlam/dev

4. Some auxtools must be added to your default environment

   the vlet module:

   add the following line to your .bashc (bash users) or .cshrc (tcshell users)

   module add vlet/0.8.0

   the Globus module:

   add the following line to your .bashc (bash users) or .cshrc (tcshell users)

   module add globus/4.0.3

5. If you have used previous versions of WS-VLAM, don't forget to remove ".vlecomposer".

Step 1:

Download the WS-VLAM client [Download]

NOTE: This is only needed if you want to run the WS-VLAM client on your own desktop. If you are planing to log onto DAS3 using ssh you just need to execute on the command line:

$ wsvlam-composer-start.sh -initconf

The -initconf is used to set the WS-VLAM workflow composer. It is needed only the first time you run the composer. After that, you just need to start the composer without arguments.

$ wsvlam-composer-start.sh

Now you can go directly to Step 5

Step 2:

Untar the zip file by typing the following command:

$ tar -zxvf wsvlam-client.tar.gz

NOTE: If you are running the WS-VLAM client on host where Globus is not installed it is likely that you do not have CA certificate available on this machine. The Dutch CA certificate can be downloaded from [caCert.pem]. Perform the following steps:

create .globus/ in your home directory: mkdir $HOME/.globus

copy your userkey.pem usercert.pem to $HOME/.globus/

create a certificates directory: mkdir $HOME/.globus/certificates

copy the CA certificate to $HOME/.globus/certificates/

Step 3:

Go to the myvlam directory and start the WS-VLAM client application by typing the following command[short movie]:

$ ./composer/bin/wsvlam-composer-start.sh

Step 4:

The first time you start the WS-VLAM a configuration pop up window will appear, and you have to specify the location of some auxiliary tools. If you have downloaded ws-vlam-client-complete use the following locations:

Vlet Location

should be set to: YOUR-PATH/myvlam/composer/lib/auxTools/vlet-0.7.3e

GLOBUS Location

should set to: YOUR-PATH/myvlam/composer/lib/auxtools/gt4.1

Vle Libraries path

should set to location where you have untared WS-VLAM client application: YOUR-PATH/myvlam/composer/lib

Other entries on the configuration panel

Keep the default values. They should be Ok for DAS3

Step 5:

Run a test without graphical output [short movie]:

1. Load the test workflow: from the menu-bar item File > Load > select the "copy-file-workflow-farming.xml" from the Popup window

2. Delegate your grid credentials: use the "send credential to the delegation service" button ()

   If the delegation has succeded you will see a text appearing in the message window of the WS-VLAM client application "... Delegation EPR is set to: ..." you will also see the "proxy time" decreasing in the bottom left corner of the WS-VLAM client application

3. Run the experiment: use the "execute workflow" button ()

   If the execution has succeded you will see a popup window appearing containing a tab "Farmed Jobs". This tab should contain a table with two rows each row representing a farmed job.

   If you select one of the rows and press the button "Start Monitoring" you will be able to see the standard Output, standard Error, and the status of each component composing your workflow

Step 6:

Run a test with graphical output "xclock" [short movie]

1. Clear the composing canvas by deleting the component composing the workflow using the Delete key. Or start a new WS-VLAM client using the button ()

2. Instantiate the xclock module using the component tree in the component palette window in WS-VLAM client window: local module set > Generic > xclock (drag-and-drop the "xclock" icon to the composition canvas).

3. Run the test workflow: as described in Step 5

   To see the xclock on your client machine, click on the "xclock" module in the composition canvas in the main WS-VLAM window then use the "viewer" button (). If the test is successful you will see an xclock on your desktop.

   Note: If you did not restart the WS-VLAM client the () will be disabled meaning that you can reuse the delegated credentials.

   FIREWALL problems:

   If you are running the WS-VLAM client on a computer running a firewall it is likely that you will not be able to use the default setting, change the vnc port to any port on which the WS-VLAM client can listen to incoming connections (you can change it using the options item in the File menu).

   If your computer is behind a NAT. PCs at home are most likely to be in this situation, you need to enable UPNP in the configuration of the WS-VLAM client application and check that your internet box is also set to enable UPNP. (You can change it using the options item in the File menu).

Full deployment of the WS-VLAM (to be followed for the POC test) [Table of Contents]

Pre-requisites:

• Software dependencies GT4 , Vlet , and java 1.5.
• Valid grid credentials.
• If you have used previous versions of WS-VLAM, don't forget to remove ".vlecomposer".

Step 1:

Download the WS-services [Download]

Step 2:

Deploy the RM and RTSM services in the Globus container:

deploy RTSM service:

$ globus-deploy-gar wsrtsm.gar

deploy RM service:

$ globus-deploy-gar ws-rm.gar

Step 3:

Download the WS-VLAM runtime sources [Download] and set the VLAM_INSTALL as indicated in the README

Download example of VLAM modules [Download]

Step 4:

Download the WS-VLAM client [Download] or [Download:including GT4 and Vlet libraries]

Step 5:

Follow the same steps described for DAS users (of course the configuration locations will be different).

NOTE

You have to specify the location of the auxiliary tools as they are installed in the PoC and the URL of the deployed RM and RTSM services.

Don't forget to specify the hostname where you want to run the test workflows. This can be done in GUI via the modules property panel. Select first a module in the composition canvas, in the property panel you will see the field "hostname" in the tab "Parameter" (by default it set to fs2.das3.science.uva.nl) change it your target host. Repeat this procedure for every module in the composition canvas.

For the test without graphical output (or copy-file workflow), don't forget to specify the file name you would like to copy. This can be done in GUI via the modules property panel: select the fileReader module in the composition Canvas, click the tab "Parameter" in property panel and change the "Value" of the "filename" parameter to the name of the file you want to copy (by default it set to No-default-value). Repeat this procedure for the fileWriter module.

=======================================================================

Microsoft Windows users [Table of Contents]

VERY IMPORTANT:

You can run the WS-VLAM client on a computer with Windows operating system but you cannot submit Job to a computer with Windows operating system.

Pre-requisites:

• You need to have access to grid-enabled computers running Linux OS where Globus 4 is instaled and WS-VLAM runTime Libraries have been deployed such as the DAS3,and the PoC. This means that you will have an account on such computer, and you have been authorized by the system admistrator to submit jobs (contact your administrator for further details).

• Valid grid credentials: You need to copy the userkey.pem and usercert.pem files to your computer as they will be needed when you start configuring the WS-VLAM Client application. You will also need a Certification Authority (The Dutch root Certification Authority file is the following [caCert.pem]. Save this file localy

• If you have used previous versions of WS-VLAM, don't forget to remove ".vlecomposer"

Step 1:

Download the WS-VLAM client [Download] [movie]

Step 2:

Untar the zip file using winZip

Step 3:

Go to the myvlam directory and start the WS-VLAM client application by executing:

$ ./composer/bin/wsvlam-composer-start.bat

Step 4:

The first time you start WS-VLAM a configuration pop up window will appear "Java CoG Kit", it will help you set up credential files. Specify the paths to the usercert.pem and userkey.pem. You also need to add the Certification Authority certificate. To do this, point the wizard to the caCert.pem you have downloaded.

Now you have to configure the WS-VLAM client application. Another pop window will appear and you have to specify the location of some auxiliary tools. Replace in the following YOUR-PATH with the location where you have installed the WS-VLAM client application.

Vlet Location

should be set to: YOUR-PATH/myvlam/composer/lib/auxtools/vlet-0.7.3e

GLOBUS Location

should set to: YOUR-PATH/myvlam/composer/lib/auxtools/gt4.1

Vle Libraries path

should set to: YOUR-PATH/myvlam/composer/lib/

Other entries on the configuration panel

Keep the default values They should be Ok for DAS3

Step 4:

To run the tests you can follow the same procedure described in Step 5 and Step 6 of the DAS users section

==================================================================