Jems technical release notes V 2.1.0

Definition

Technical release notes include details of installation/update package for system administrators or service maintainers.

This is an second release of Jems that requires additional pre-installation steps.

Technical release notes indicates steps need to be done for installation or update of the system.

Update of the system should be done in case if first release of Jems has been already deployed.

Pre-installation requirements

Initial steps for those who is doing installation for the first time

Step	Description
Helpdesk account	Send registration request to get the Helpdesk account
Hardware procurement	Find a service provider who could deliver the environment according to the listed prerequisites. See the hardware requirements.
Request the test environment	Request service provider to mirror production on test environment
Install OS, OS updates and security packages	Request service provider to provide an environment ready for the component’s installation
Issue SSL certificate for Jems service	Request service provider to issue SSL certificate to secure Jems service
Install component dependencies	Service provider should provide support with installation of packages required by Jems service
Install Jems service	Service provider should provide support with Jems service installation

Initial steps for those who did installation before

Step

Description

Update Jems service

Service provider should provide support with Jems service update

Change startup configuration

Configuration startup should be adopted with additional startup parameter
-Dloader.path=addons

Where addons is a folder where addons are stored
Example of startup configuration

CODE

[Unit]
Description=Jems service

[Service]
WorkingDirectory=/opt/prod
ExecStart=/usr/bin/java -Dloader.path=/home/jems/addons -jar /home/jems/jems-server.jar
User=root
Type=simple
Restart=on-failure
RestartSec=10

[Install]
WantedBy=multi-user.target

Installation

Follow instructions this section in case if this is a first time installation.

The service provider should provide support with Jems service installation.

Please follow the latest installation instructions published in our Jems community http://connections.interact-eu.net/communities/service/html/communityoverview?communityUuid=4f8072e7-3678-43ad-a61a-fe8e9b9eb92e
You can also find the latest installation instructions published in Helpdesk https://helpdesk.interact-eu.net/staticdocumentation/index.html

In section: Manual → Technical manual → Installation instructions

Update

Follow instructions this section in case if installation was already done before

The service provider should provide support with Jems service update.

You can find the latest installation instructions published in Helpdesk https://helpdesk.interact-eu.net/staticdocumentation/index.html

In section: Manual → Technical manual → Update instructions

Post-installation requirements

Step	Comment
Configure Jems service	Service provider based on system user manual should provide support with Jems service configuration
Update user privilege	If you have already users in your system, you need to ensure that they have an appropriate roles. By default system is delivered with 3 user roles: 1.Administrator 2.Programme 3.Applicant

Please follow User documentation to manage the Jems configuration located on Helpdesk https://helpdesk.interact-eu.net

API Interface

This is the very first version of Jems API which could be found by the link http://jems1.interact-eu.net:8080/swagger-ui.html#/

Deliverable package

Component	Version
Jems-server	2.1.0
Pre-submission plugin	1.0.4

Technical notes

The released version is fully compatible with all components and dependencies mentioned in the Technical prerequisites and Installation instructions.
To get an access to the installed instance, please use the following user name and password

Default admin:
Login: admin@jems.eu
Password: Jems@2020admin@jems.eu

Development notes

General information

Please be informed, that we have the best intentions to help programmers to succeed and we acknowledge that some programmes might need some customization of Jems.
The interpretation of a "substantial" modification of code is directly related to the capacity that Interact has to support.
A change in the core logic of the system or the addition of a complex functionality that interferes with the original workflow of the Jems puts Interact in front of an unrecognized software.
In such circumstances, Interact will not be able to provide support (helpdesk bugs, special updates for customized solutions).
We would recommend using the plugins approach for the Jems software feature extension which supports backward compatibility with further service updates.
In case service customization is related to core functionality, the programme will lose service updates or will need to adapt and develop service additionally.

Note:
To get access to the Gitlab repository with the latest Jems software sources, please create the request via Jems Helpdesk https://helpdesk.interact-eu.net.

Addons development

With current release, we deliver first addon feature related to Pre-submission checks.

Detailed information about developer instructions could be found in latest instructions published in Helpdesk https://helpdesk.interact-eu.net/staticdocumentation/index.html

In Section: Jems add-on development

Note:
To get access to the Gitlab repository with the latest Jems Addon sources, please create the request via Jems Helpdesk https://helpdesk.interact-eu.net.