The PICALC consists of a portlet example able to submit a paralle MPI job that calculates the PI into one or more distributed infrastructures (DCIs). This portlet contains almost all GUI elements to provide a complete input interface together with the necessary code to deal with DCIs settings, portlet preferences etc. The aim of this portlet is to use its code as a template that Science Gateway developers may customize to fit their own specific requirements. To faciciltate the customization process, a customize.sh bash script is included inside the source code package.
Following instructions are meant for science gateway maintainers while generic users can skip this section. To install the portlet it is enough to install the war file into the application server and then configure the preference settings into the portlet preferences pane.
Preferences are splitted in three separate parts: Generic, Infrastructures and the application execution setting. The generic part contains the Log level which contains one of following values, sorted by decreasing level: info, debug, warning and error. The Application Identifier refers to theId field value of the GridEngine ‘UsersTracking’database table: GridInteractions. The infrastructure part consists of different settings related to the destination of users job execution. The fields belonging to this category are:
Enable infrastructure: A true/false flag which enables or disable the current infrastructure;
Infrastructure Name: The infrastructure name for these settings;
Infrastructure Acronym: A short name representing the infrastructure;
BDII host: The Infrastructure information system endpoint (URL). Infrastructure preferences have been thought initially for the elite Grid based infrastructures;
WMS host: It is possible to specify which is the brokering service endpoint (URL);
Robot Proxy values: This is a collection of several values which configures the robot proxy settings (Host, Port, proxyID, VO, Role, proxy renewal);
Job requirements: This field contains the necessary statements to specify a job execution requirement, such as a particular software, a particular number of CPUs/RAM, etc.
Actually, depending on the infrastructure, some of the fields above have an overloaded meaning. Please contact the support for further information or watch existing production portlet settings.
The usage of the portlet is simple; the user can select to upload a file, or insert inside the text field any input text. The job identifier text is a human readable value that users will use to keep track of any job execution on DCIs Following buttons: Demo, Submit, Reset values and About are respectively:
Submit - Executes the given macro on the distributed infrastructure
Reset - Resets the input form
About - Gives an overview of the portlet