"Fossies" - the Fresh Open Source Software Archive

Member "UNICORE-Client-7.4.1/README.txt" (8 Jan 2019, 6685 Bytes) of package /windows/misc/UNICORE_Client-7.4.1-win32.win32.x86.zip:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 UNICORE Rich Client README
    2 ==========================
    3 UNICORE Team <unicore-support@lists.sourceforge.net> 
    4 v7.4.1, January 2019
    5 
    6 This is the README file for the UNICORE Rich Client, which comes as a
    7 standalone rich client product based on Eclipse.
    8 
    9 The UNICORE server is available as a separate download on the
   10 UNICORE@Sourceforge page, http://sourceforge.net/projects/unicore
   11 
   12 INSTALLATION & Startup
   13 ----------------------
   14 Unzip the client package that matches your platform.
   15 
   16 Run 'UNICORE_Rich_Client' or 'UNICORE_Rich_Client.exe'. The client
   17 should start with a splash screen. Inside the splash screen, the workspace 
   18 location and your credentials and truststore must be set up.  
   19 For example, a Java keystore file (.jks) containing trusted X509
   20 certificate authorities and your private key(s) must be selected. By
   21 default, a keystore that contains everything you need in order to test
   22 the client with a UNICORE quickstart server installation is
   23 selected. This file is located inside the 'certs' folder in the
   24 client's installation directory. The password of this keystore is
   25 '321'.  A password matching the selected keystore must be provided in
   26 the splash screen. Tick the corresponding checkbox if you would like
   27 to store your password in an encrypted keyring file so you don't have
   28 to enter it at each client start (not recomended).
   29 
   30 
   31 .Command line arguments for customizing the startup process include:
   32 [options="header", cols="literal,"]
   33 |===============================================================================
   34 |Argument			|	Effect
   35 
   36 |-data workspacePath |	The path of the workspace on which to run the Eclipse
   37 platform. The workspace location is also the default location for projects. 
   38 Relative paths are interpreted relative to the directory that Eclipse was
   39 started from. Remember to use double quotes or escape special characters that
   40 the shell could try to interpret otherwise. 
   41 													
   42 |-vm vmPath			| The location of Java Runtime Environment (JRE) to use to
   43 run the Eclipse platform. By default, this is set to the included runtime.
   44 Since version 7.4.0 the URC only supports Java 8.
   45 Relative paths are interpreted relative to the directory that Eclipse was started 
   46 from.
   47 													
   48 |-vmargs args		|	When passed to the Eclipse, this option is used to 
   49 customize the operation of the Java VM used to run Eclipse. If specified, this
   50 option must come at the end	of the command line. The given arguments are
   51 dependant on VM that is being run.
   52 |===============================================================================										
   53 
   54 .Examples:
   55 [frame="topbot",grid="none",cols="literal,"]
   56 |=============================================================================== 
   57 |UNICORE_Rich_Client.exe -data 'c:\projects'| Use 'c:\projects' as workspace dir
   58 |UNICORE_Rich_Client.exe -vm 'c:\jre\bin'	| Java can be found at 'c:\jre\bin'
   59 |UNICORE_Rich_Client.exe -vmargs -Xmx256M	| Allow heap to use up to 256 MB
   60 |=============================================================================== 
   61 
   62 Arguments for the virtual machine can also be specified in the file 
   63 'UNICORE_Rich_Client.ini'.
   64 
   65 
   66 Updating from previous versions
   67 -------------------------------
   68 
   69 Due to changes in the software, you might run into some issues when 
   70 updating from a previous client version.
   71 
   72 If you are using an existing keystore, it might be required to clean it
   73 up, especially removing duplicate certificates, as the new client is a bit more 
   74 restrictive here. If you experience any SSL related issues, please check your 
   75 keystore.
   76 
   77 If you use a workspace created using a previous client version, you might 
   78 encounter messages such as "Unable to deserialize cached Grid service 
   79 information". In such a case, simply refresh the Grid browser.
   80 
   81 
   82 GETTING STARTED
   83 ---------------
   84 On first client startup, you will see the welcome screen which provides links
   85 to important functions and additional information. This screen can always be
   86 reached by selecting 'Help -> Welcome' via the window's main toolbar.
   87 
   88 In order to connect to a UNICORE server, you need to provide the URL of a
   89 UNICORE registry which comes with every UNICORE server installation and
   90 contains addresses of UNICORE server components. Please do so by leaving the
   91 welcome screen and using the context menu of the 'Grid Browser' view. Select the
   92 'add Registry' menu item and enter a URL and name for the registry. 
   93 Now double-click the Registry in order to list the registered services on the
   94 Grid. If the Registry node turns red or does not list any children, the Registry
   95 is either empty or the client could not connect to it. If this happens, please
   96 check your security setup and the URL that you entered.
   97 Please make sure that a default certificate (that is presented when connecting
   98 to UNICORE services) is selected in the 'Keystore' view.
   99 This view can also be used for importing additional private keys from other
  100 keystores and exporting certificates.
  101 In order to obtain more information about a listed service, right click it and
  102 select 'details' from the context menu that should appear. The Registry should
  103 contain at least one or more execution services, depicted by small computer
  104 icons.
  105 
  106 In order to prepare a single job for execution on a UNICORE target system
  107 service, please right-click such a service in the 'Grid Browser' view and select
  108 'create job' from the context menu. After providing parameters for the job,
  109 click the green submit button in the global toolbar. Job outcomes can be
  110 fetched with the button right next to the submit button, or from the context
  111 menu of the job node in the 'Grid Browser' view.
  112 
  113 
  114 Please note, that a standard UNICORE installation does not provide the full 
  115 UNICORE workflow functionality. Workflow engine server components are being
  116 released separately. The client's workflow capabilities do rely on the 
  117 availability of these server components in the Registry.For creating a workflow
  118 which can be edited and submitted to a workflow engine, use the 
  119 'File -> New -> Workflow Project' menu entry and enter a name for the workflow
  120 project to be created.
  121 
  122 A more complete client manual with instructions can be accessed by selecting the
  123 'Help -> Help Contents' menu entry.
  124 
  125 
  126 REPORTING BUGS
  127 --------------
  128 In case you find any bugs, please use the bug trackers of the UNICORE project at 
  129 
  130 http://sourceforge.net/p/unicore/urc-issues/
  131 
  132 You may also send an email to the support list: 
  133 
  134 unicore-support@lists.sf.net
  135 
  136 
  137 CONTACTS
  138 --------
  139 - Web site: http://www.unicore.eu/
  140 - Sourceforge project site: http://sourceforge.net/projects/unicore/
  141 - Questions, suggestions, problems: unicore-support@lists.sf.net
  142 - Developers chat: unicore-devel@lists.sf.net (subscription required)