Creating or Editing an Archive Connection
It is possible to archive What-ifs, Requests or Process Insight analyses to the database of your choice. Users have the option of using an existing archive database or creating a new archive connection to connect to the server where the database will be located. Once the connection is created, you can schedule an archive to archive data.
Note: If you have updated your Infor Risk & Compliance
		  application to a recent version, you must create a new archive database.
		  Archiving analyses using connections created in the earlier version will not be
		  successful. 
		
 
		- Create a new archive
			 connection : 
			 
- Specify a unique name to identify the new connection. This name cannot be used for creating other target databases even if the SQL server is different.
 - From the SQL Server Name panel, either select the SQL server from the drop-down list or type the SQL Server name in the textbox. The new archive database will be created on this SQL Server. The database may be on the same server as Infor Risk & Compliance or on a different server.
 - Depending on the
				  authentication option available for the target server, select the appropriate
				  authentication: 
				  
- For Windows authentication, the Infor Risk & Compliance service context will be used to connect to the database server.
 - For SQL authentication, specify the user name and password to connect to the database server.
 
 - Click to validate the user name and password provided. A confirmation message is displayed stating that the database is validated. If the credentials provided are not successfully validated, the message 'SQL Server Authentication Failed' is displayed.
 - In the Database Name panel, specify the target database
				  where the What-ifs, requests or Process Insight analyses will be archived. You
				  have the following options: 
				  
- To create a new
						database, select 
						New Database and
						provide a unique name for the database in the field provided. If the specified
						name already exists, an error message is displayed and you need to provide
						another name. 
						Note:
- For SQL authentication, the user creating the database must have Bulkadmin and DBCreator roles on the target database server as they are required for creating the database and new tables in the database.
 - For Window authentication, the user creating the new archive database must be an Infor Risk & Compliance service context user having DBCreator and Bulkadmin roles on the target database server.
 
 - To use an existing
						database, select the radio button next to 
						Select Database.
						Select the required database from the drop-down list which displays only those
						existing databases for which the validated user has public and db_owner user
						mapping permissions or public user mapping permissions only. For successful
						data archival, the databases for which the validated user is assigned both
						public and db_owner user mapping permissions must be selected. 
						Note: To select an existing database, the validated user must have the Bulkadmin role assigned on the target database.
 
 - To create a new
						database, select 
						New Database and
						provide a unique name for the database in the field provided. If the specified
						name already exists, an error message is displayed and you need to provide
						another name. 
						
 - Click 
				  . 
				  Note: The save button will not be enabled unless the connection is first validated.
The newly created archive connection will be displayed on the Archive Connection home page.
 
 - Modify an existing archive
			 connection: 
			 
- On the Archive page, click the archive connection link that you want to modify. The page for that connection is displayed.
 - Make the required
				  changes as explained in 
				  Create a new archive
					 connection section and click 
				  . 
				  Note: If you have upgraded from older versions, then no fields are modifiable on this page. For new installations, only the authentication field is modifiable .