Table of Contents |
---|
How to upgrade from version 1.x - 2.4.x to version 2.5.x
Important changeovers were made from the previous version to the current version.
The operating system has been updated from CentOS6 to CentOS7
The application server was migrated from jboss 7 to WildFly 14.0.0.Final
In addition to a series of application improvements that you can find at the changelog https://namirial.atlassian.net/wiki/display/SWS/Changelog
To complete the update you need to create a new machine and proceed to a new appliance installation that you find at the following link History - SWS OnPremise - RPM package#HowtoobtaintheOVFvirtualappliance .
A step by step installation guide can be found at the following link History - SWS OnPremise - RPM package#Deploymentandtest.
Once the installation is complete you will need to reconfigure your VA with the production keystore, you can find at this link a detail on how to do this History - SWS OnPremise - RPM package#MigratefromTESTtoPRODenvironment.
If you want to stay up to date with the latest version we recommend you follow this guide. FAQ#FAQ#HowcaniupgradeSWSappliancetolatestversion?
How can i export the log from SWS?
At this link:
History - SWS OnPremise - RPM package#ExportLogFiles
You can see the guide for export the files.
How can i see the SWS version?
There are two ways. First way:
Go to link:
Code Block |
---|
http://<IP-APPLIANCE>:8080/SignEngineWeb/help.xhtml |
And read the version software (starts with 2.x )
Or:
1) Login SSH to appliance and execute:
Code Block |
---|
rpm -q sws |
And read the version software (starts with 2.x)
NOTE: for the old appliance SWS is available only the second way.
How can i obtain the TEST Namirial App OTP?
If you download the Namirial App OTP from the official store (PlayStore and AppleStore), you can use ONLY the Namirial PROD enviroment.
If you need to use the Namirial TEST environment, you can download the app from this link:
For Android:
https://appdistribution.firebase.dev/i/e843f2440b8a7b69
For iOS:
Template support request in case of problems with integration
The fields required are:
DATE and TIME when you have received the error: ???
URL ENDPOINT: ???
METODO NAME CALLED: ???
INPUT PARAMETERS: ???
ERROR RECEIVED (from our server): ???
How can i install SWS in standalone mode?
Is possible to install SWS in standalone mode ONLY in server RedHat, Almalinux9 and CentOS (this OS is supported until June 2024). Below the procedure:
Code Block |
---|
wget https://sws.firmacerta.it/download/sws2_packages.tar.gz tar xzfv sws2_packages.tar.gz |
Move into directory just extracted and run this command:
Code Block |
---|
./install.sh |
How can i TEST SWS onPremise?
SWS onPremise is distributed in two different ways:
standalone (the SWS application is installed on Linux server)
Below the link:
Code Block |
---|
https://namirial.atlassian.net/wiki/spaces/SWS/pages/257950448/SWS+OnPremise+-+Standalone#Installation |
Docker (the image is installed on orchestrator managed by the customer)
Below the link:
Code Block |
---|
https://namirial.atlassian.net/wiki/spaces/SWS/pages/211452317/SWS+OnPremise+-+Docker+container#How-can-i-obtain-the-SWS-on-Docker? |
How can i TEST SWS SaaS?
The url prefix for TEST SWS SaaS is:
Code Block |
---|
https://sws-companynamesaas.test.namirialtsp.com/SignEngineWeb |
This is the link for download SSL certificate on our service
For example during the integration the full url to use for SOAP request is:
Code Block |
---|
https://sws-companynamesaas.test.namirialtsp.com/SignEngineWeb/sign-service?wsdl |
And the full url for REST request is:
Code Block |
---|
https://sws-companynamesaas.test.namirialtsp.com/SignEngineWeb/rest/sign/signPades |
Where can i obtain all Namirial root CA?
At this link:
View file | ||
---|---|---|
|
you can download all root CA