This section describes what files and fields must be updated when one of the hostnames are changed.
Event Training Server (ETS) Hostname Change
When the ETS hostname changes, the following updates must be made:
-
If SSL is enabled, new PEM files and JKS files must be generated for the new hostname.
-
Use the generate-keystores.sh
script to create keystores from the PEM files.
-
Disable SSL: ./disable-ets-ssl.sh
-
Enable SSL: ./enable-ets-ssl.sh
-
If ETS is used for extraction, update the ETS url in the Rosette Server configuration file ./rs/config/rosapi/event-extractor-factory-config.yaml
.
-
If ETS is used for training, update ETS_URL
in the .env file of RAS: ./ras/.env
.
REX Training Server (RTS) Hostname Change
When the RTS hostname changes, the following updates must be made:
-
If SSL is enabled, new PEM files and JKS files must be generated for the new hostname.
-
Use the generate-keystores.sh
script to create keystores from the PEM files.
-
Disable SSL: ./disable-rts-ssl.sh
-
Enable SSL: ./enable-rts-ssl.sh
-
Update RTS_URL
in the Rosette Server .env file (./rs/rs-docker/.env
) with the new hostname.
-
Update RTS_URL
in the Rosette Adaptation Studio .env file (./ras/.env
) with the new hostname.
Rosette Server (RS) Hostname Change
When the RS hostname changes, the following updates must be made:
-
If SSL is enabled, new PEM files and JKS files must be generated for the new hostname.
-
Use the generate-keystores.sh
script to create keystores from the PEM files.
-
Disable SSL: ./disable-rs-ssl.sh
-
Enable SSL: ./enable-rs-ssl.sh
-
IF ETS is being used for training, then update the RS_URL in the ETS .env file (./ets/ets-docker/.env
).
-
Update ROSETTE_URL
in the Rosette Adaptation Studio .env file (./ras/.env
) with the new hostname.
Rosette Adaptation Studio (RAS) Hostname Change
When the RAS hostname changes, the following updates must be made:
-
If SSL is enabled, new PEM files and JKS files must be generated for the new hostname.
-
Use the generate-keystores.sh
script to create keystores from the PEM files.
-
Disable SSL: ./disable-ras-ssl.sh
-
Enable SSL: ./enable-ras-ssl.sh
-
Update the mongo configuration of RTS (/rts/config/mongodal_config.yaml
) with the new hostname.
Export or Backup a Project
Note
You must be registered as a manager.
You can backup an individual project to save a snapshot whenever necessary, for example at project milestones or before making major changes to the project.
-
In the project menu, select Export Project.
-
Add a descriptive name to the export. The studio will generate an ID for the download; the name you provide will be listed as the version.
-
Confirm when prompted.
To view the exported versions:
-
Select Manage from the navigation menu.
-
Scroll down to the Exported Versions table.
-
From here, you can download or delete the file. The downloaded file name will concatenate the project id and backup timestamp.
Note
You must be registered as a manager.
Note
To import models into Rosette Adaptation Studio from the command line, the utility jq must be installed on your system.
To import a project, you must have an exported project file.
-
Open a command window on the Rosette Adaptation Studio server.
-
Run the import_project.sh
command.
Usage: ./import_project.sh [options] --username <username> --password <password> export_file
Available options:
--server <server> Server to use (default: localhost)
--https Contact server with https (default is http)
--name <name> Set the name of the project being imported
--template <template> Set the template of the project being imported, e.g. --template rex
(must be compatible with existing template)
--async Upload asynchronously (may be required for large projects) [EXPERIMENTAL]
--max-wait <secs> Maximum amount of time to wait for project to be ready
(only effective when --async is set)
--skip-sanity Don't run sanity checks on imported project
You can also import a project from within Adaptation Studio from the New Project menu.
At this time, all components must be upgraded when installing a new release.
-
From Rosette Adaptation Studio backup all projects you want to move to the new release.
-
Shut down the servers in the following order:
-
Rosette Adaptation Studio
stop-standalone.sh
-
Rosette Server
docker compose down
CTRL-C
-
REX Training Server
docker compose down
-
Events Training Server
docker compose down
-
Install the new releases on a different server or virtual machine.
-
Move Rosette Server configurations into the new Rosette Server install directory:
-
Copy Rosette Server configuration files (*.cfg
and *.yaml
files) into the new Rosette Server installation.
-
Set profile-data-root
in com.basistech.ws.worker.cfg
and com.basistech.ws.frontend.config
to point towards custom-profiles directory in new install
-
Start the Servers.
-
Import the projects into the new version of Rosette Adaptation Studio.
Tip
You can change the project template when importing the project during the upgrade. The templates must be compatible.
Migrate to a New Template
Note
You must be registered as a manager.
There may be times when you want to migrate a project from one template to another. New templates may be added, or you may realize a different template will work better for your project.
Tip
The templates must be compatible.
These procedures can be used to move projects created with the NER template to the NER-Rosette template.
This option copies a project created with the NER template to the NER-Rosette Template. The new copy is on the same server.
-
Open the project.
-
From the project menu in the upper right-hand corner of the project dashboard, select Clone.
-
Enter the name of the new project.
-
Check the box: Switch to NER-Rosette Template?.
-
OK.
This option creates a copy of the project on a new server. A different template can be specified.
-
Export the project from the original server:
-
Import the project onto the new server.
Note
Rosette Adaptation Studio does not automatically backup the database. You must create a cron job or other process to create regular server backups.
The server uses a mongo database to store the projects.
The studio ships with a script file, backup_mongo.sh
. This script creates a timestamped snapshot of the entire mongo database in the mongo_data_dump
subdirectory.
The script can be run manually at any time.
We recommend setting up a cron job to backup the server automatically. For example, do crontab -e
and add the following line to run the script weekly (replacing MYDIR
with your installation directory):
0 0 * * 0 <MYDIR>/backup_mongo.sh > <MYDIR>/backup.log 2> <MYDIR>/backup.err
To restore the entire database from a backup use the mongorestore command. This restores all projects in the database. To save and restore an individual project, export and then import the project.
-
Get the container id of the mongo docker server by querying the docker containers on the Rosette Adaptation Studio (RAS) server.
docker ps
-
Get a list of all the backups available. From the machine where the backup is run, the RAS directory will have a subdirectory named mongo_data_dump
. The backups will be in the format DD-Mon-YYYY, e.g. 18-Oct-2020.
ls
-
Select the backup to restore and issue the following command:
docker exec -i <container-id> mongorestore /data/dump/<backup_version>
where <backup_version> is the backup name, 18-Oct-2020.