Home / Servers / Portal / 2.2.0
Name Modified Size Downloads / Week Status
Parent folder
README 2016-10-27 6.9 kB 0
CHANGES.txt 2016-10-27 2.4 kB 0
unicore-portal-2.2.0.tar.gz 2016-10-27 101.0 MB 11 weekly downloads
Totals: 3 Items   101.0 MB 1
# # UNICORE Portal # VERSION 2.2.0 October 27, 2016 Installation ************ The portal server 2.2.0 requires Java version 1.8 or later (we recommend using OpenJDK Java 8) and is currently restricted to a Linux/UNIX operating system. Unzip the archive into a convenient folder, which will result in the following directory structure + bin : start/stop/status/sign scripts + lib : application libraries + conf : configuration files + webcontent : libraries for Java webstart application(s) used by the portal as well as VAADIN folder with UI theme files, icons, CSS style sheets + logs : default log directory + doc : readme, changelog and others UPGRADING from 2.1.0 ******************** 1. Update libs folder to latest version 2. Update <unicore-portal>/conf/web.xml 3. There are three new properties, which can be set in portal.properties, but neither is mandatory: portal.ui.menu.navigation.default=<the path to a default start up view, which the user will be redirected to after login> portal.core.workflow.templates.enable=<true or false -> the workflow templates can be disabled from the UI of the Portal; the default value is true> portal.core.defaultApplication=<the name of the application, which will be preset in the combo box at submitting a new job> UPGRADING from 2.0.0 ******************** 1. Update libs and webcontent/VAADIN folders to latest version 2. Merge portal.properties file. -There is some of new properties concerning the discovery API. -The properties with prefix userprofiles.* have been renamed to portal.userprofiles.* MIGRATING from 1.2.0 ******************** Due to numerous changes in the structure and the internal logic of the portal, we recommend a fresh installation of the new version 2.1.0. You can keep the old user 'data' folder as well as the 'conf' folder after adjusting the files as mentioned in point 4. 1. Install the new version. 2. Copy and paste the 'data' folder with the user information from the old version into the newly installed portal. 3. Keep in mind to link the workspace to the same location as it was in the older version of the portal 4. It is safe to copy your 'conf' folder and all its files taking into a consideration the following notes: 4.1. Do not directly use the old portal.properties file! There are numerous changes as well as a lot of new properties that have been added. Instead try to compare and merge the two versions. Just some hints: The authentication properties' "implementationClass": 'portal.registration.facility.REG-SAML.implementationClass' has changed to "type": 'portal.registration.facility.REG-SAML.type' whereas 'type' is one of the following: 'DEMO', 'SAML', 'TLS', 'username', 'KRB5'; The following properties are obsolete and have been removed: -portal.grid.lists.childrenLimit -portal.grid.lists.chunkSize -portal.grid.JobViewShowSite -portal.grid.JobViewShowQueue -portal.grid.JobViewShowEndTime 4.2. Keep in mind that the web.xml file has changed drastically. Please remove the old web.xml file and use the one from the new version. 4.3. portalPlugin.xml file is obsolete. You can delete it. Configuration ************* The main configuration file is conf/portal.properties This file contains central settings such as host and port of the server. You must review it before starting the portal. In the default configuration, DEMO-CA certificates are accepted, and the portal uses a certificate issued by the DEMO-CA. This will allow to test the portal against a UNICORE server demo installation. Furthermore, a "demo user" login is provided, however the credentials used by this account can be configured. If you wish to modify anything, please refer to the comments in the property file. An important configuration item refers to the location where user workspaces are stored. By default, they are stored on the portal machine, but they can also be stored remotely on a UNICORE storage. Please review the portal.properties file. Signing Java webstart archives and applet(s) ******************************************** The application includes parts that are run via Java web start or the Java applet mechanism. These need to be signed using the portal credential. Signing requires the "jarsigner" application from the Java Development Kit (JDK). A script 'unicore-portal-sign.sh' is provided in the bin folder which signs the jar files. Please review this script and provide the proper values for your portal credential. This process has to be done only once before running the portal for the first time. Note for Windows OS: ******************** Please make sure to put your Java security to the lowest level for the domain and port of the portal You also need to add an exception for the portal site and import a trusted CA certificate so that your file transfers from local file system can work properly. Setting the Security levels through the Java Control Panel In the Java Control Panel, click on the Security tab. Select the desired Security level. Click Apply. Click OK to save changes made to the Java Control Panel. Use "Edit Sites List..." to add the site for the portal. Use "Manage Certificates" to add the necessary CA certificate. Starting/stopping ***************** The application is controlled using the scripts in the bin/ folder. As usual, there are start, stop and status scripts. Getting started *************** The portal URL is "https://<host>:<port>/portal" (by default: https://localhost:9091/portal ) Before logging in, a user has to register using the "Create account" tab on the login page. After creating an account, the user can log in. * Authentication using a certificate Users who have a valid certificate in their browser can use this to register and later authenticate. Once authenticated, users must create a SAML trust delegation assertion. This is accomplished from the "Profile" view. Customisation ************* The portal can be customised in several ways to better fit your use cases. 1) conf/portal.properties The main config file contains several options that change the portal's functionality. Personal customizations of some menu items, logos, icons and others can also be configured. Please review this file carefully. 2) CSS style sheets The CSS style sheets are accessible in the webcontent/VAADIN/themes/valoPortal folder. Reporting bugs ************** Our bug tracker is at http://sourceforge.net/p/unicore/bugs Known issues ************** - If-clause in workflows does not yet support full feature functionality ROADMAP ******* The feature request tracker is at http://sourceforge.net/p/unicore/feature-requests You can also write to the support list unicore-support@lists.sf.net
Source: README, updated 2016-10-27

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks