Transferring data between Remedy SSO servers

Data transfer tool usage considerations

Before exporting and importing the Remedy SSO server configuration, take into account the following considerations:

• Use the data transfer tool when you need to export configuration from one Remedy SSO server (for example, QA server), and import it to another Remedy SSO server (for example, Dev server).
• The data transfer tool is designed to work across the same versions of Remedy SSO. You must not export or import data between different versions of Remedy SSO server.
• The data transfer tool imports all data, except issued tokens, sessions, authorization codes, SAML signing, and encryption certificates.
• You can import all configurations (including general configuration, launchpad settings, registered OAuth2 clients, and admin users), or segments of the configuration (one or more realms with branding, associated local users or groups, and the assignments of those users and groups).
• The import job runs as a single transaction. 

Data transfer task overview

To transfer a configuration from one Remedy SSO server to another server, perform the following tasks:

1. Prepare for the data transfer.
2. Export the complete configuration of a source server.
3. Import either the complete configuration or segments of the configuration of a realm to a target server. 

To prepare for data transfer 

Before you use the data transfer tool, perform the following steps:

1. Download Remedy SSO server installation files to a server on which you will run the data transfer tool. 
2. Ensure that the application.properties and data-transfer-tool.jar files are located in the same directory (for example, C:\Program Files\BMC Software\RemedySSO\tools\dataTransferTool). 

To export Remedy SSO configuration 

1. Set the properties of the source server in the application.properties file as required:

   Properties	Value
   datasource.url	<jdbc_connection_string> For example: (MsSQL server) jdbc:sqlserver://<sql_server>:1433;DatabaseName=rsso
   db.type	<mssql|postgres|oracle>
   db.username	<db_username>
   db.password	<db_password_plaintext>

2. In the command line, run either of the following commands:
   • (Interactive shell) java -jar data-transfer-tool.jar
   • (Batch execution) java -jar data-transfer-tool.jar @<full_path_to_command_file.txt>

3. To use the data transfer tool in interactive shell mode, run the following command to export all the data:

   export <filename>

   If you do not specify <filename>, rsso-config-export.zip filename is used.

   Note

   You must not modify the contents of this exported zip file. 

   Make sure the exported file is stored securely. 

To import Remedy SSO configuration 

1. Set the properties of the target server in the application.properties file as required:

   Properties	Value
   datasource.url	<jdbc_connection_string> For example: (MsSQL server) jdbc:sqlserver://<sql_server>:1433;DatabaseName=rsso
   db.type	<mssql|postgres|oracle>
   db.username	<db_username>
   db.password	<db_password_plaintext>

2. Run either of the following commands to use the required operation mode:
   
   • (Interactive shell) java -jar data-transfer-tool.jar
   • (Batch execution)  java -jar data-transfer-tool.jar @<full_path_to_command_file.txt>

3. Perform one of the following steps:

   • To import  realms configuration
   • To import  configuration with renamed realm names 
   • To import  OAuth clients configuration
   • To import full  configuration

   To import Remedy SSO realms configuration

   Run one of the following commands:

   import <filename> -r <realm_list>

   import <filename> --realms <realm_list>

   The following table describes the command parameters:

   Parameter	Description
   filename	The default file name is rsso-config-export.zip.
   -r  --realms	Enter realms that you want to import. For example, <realmId1>,<realmId2>,<realmId3>.  When specified, only these realms with related local users or roles are imported. All other configuration in the target database remain unchanged. You can also rename a realm during import.

   To import Remedy SSO configuration with renamed realm names

   Run the following command:

   import <filename> -r <realm1>:<realm1NewName>,<realm2>:<realm2NewName>,<realm3>,<realm4>:<realm4NewName>

   Ensure that the new name of a realm corresponds to the following requirements:

   • Can have a maximum of 80 characters, and can contain the following characters: 
     • Asterisk (*)
     • Underscore (_) 
     • Full stop '.',
     • En dash (-)
   • Must not be empty, and must have a unique name. 

   Note

   If you rename a realm during import, and the target server has a realm with the same name, then the target realm is not overwritten, but a new realm is created.

   To import Remedy SSO OAuth clients configuration

   Run one of the following commands:

   import <filename> -o <oauth_client_ids_list>

   import <filename> --oauthclients <oauth_client_ids_list>

   The following table describes the command parameters:

   Parameter	Description
   filename	The default file name is rsso-config-export.zip.
   -o  --oauthclients	Enter client IDs that you want to import. For example, <clientId1>,<clientId2>,<clientId3>. When specified, only these OAuth2 clients are imported. All other configuration in the target database remains unchanged.

   To import full Remedy SSO configuration

   Run the following command:

   import <filename>

   Importing full Remedy SSO configuration implies importing all data from the source Remedy SSO server to the target Remedy SSO server, except issued tokens, sessions, authorization codes, SAML signing, and encryption certificates.