To export files from a One Identity Manager database
-
Start the Launchpad and log in to the One Identity Manager database.
-
In the Change & Extend view, select the Import files for software update entry and click Start.
This starts the Software Loader program.
-
On the home page, select Export from database.
-
On the Connect to database page, check the One Identity Manager database connection data and change if necessary.
-
Specify which data to export on the Select files page.
-
Specify the destination directory to export the file to.
The Files tab displays the exported files with their status and file size.
Table 50: Meaning of the status
|
Unknown file |
The file is not yet exported from the database to the given directory. |
|
Version OK |
The file version matches the version in the database. |
|
Version modified |
The file version has changed with respect to the version in the database. |
-
Mark the files to export.
-
To export all the file of a machine role, select the machine role on the Machine role tab.
-
To select single files, select the files on the Files tab.
-
The marked files are export to the given directory. This may take some time depending on the number of files selected. The export steps are displayed on the page Uploading files. Any export errors are displayed. After exporting is complete, click Next.
-
To end the program, click Finish on the last page.
Related topics
The Configuration Wizard provides you with support for enabling a restored database. The necessary database users, database roles, and server roles are created and the database is compiled.
To create a test or development database from a database backup from another system
-
Create a new database on the database server in the reference environment.
-
Create a database backup of the original database.
-
Restore the backup to the reference database.
-
Start Configuration Wizard on an administrative workstation.
-
On the Configuration Wizard's home page, select the Enable restored database option and click Next.
-
On the Select database page, select the database and installation directory.
-
Select the database connection in the Select a database connection pane. Select a user who at least has administrative permissions for the One Identity Manager database.
-
In the Installation source pane, select the directory with the installation files.
-
On the Database check page, errors are displayed that prevent the database from being processed. Correct the errors before you continue updating.
-
On the Create a new login for administrators page, decide which SQL server login to use for administrative users.
You have the following option:
-
Create new SQL Server logins for the database: Select this option if you want to work with granular permissions and create a new, administrative login on the SQL Server.
Later on in the process, the Configuration Wizard sets up additional SQL Server logins for the configuration user and the end user.
-
Use an existing SQL Server login: Select this option if you have already created an administrative SQL Server login and want to use this. Later on in the process, the Configuration Wizard sets up additional SQL Server logins for the configuration user and the end user.
-
Enter the login name, password, and password confirmation for the SQL Server login.
-
Set the Permissions option so that the SQL Server login obtains permissions for the database. If this option is not set, only the permissions are tested.
-
Use the current SQL Server login for the database: If you select this option, no other SQL server logins are created for the database. In this case, you cannot work with granular permissions concepts at SQL level.
The user you specified is used to connect to the database.
-
On the System administrator connection page, enter the login credentials for the database login with system administrator permissions.
NOTE: This page is only shown if you are working with granular permissions and you have to make changes to the administration user's permissions.
-
The installation steps are shown on the Processing database page. Installation and configuration of the database are automatically carried out by the .
TIP: Set Advanced to obtain detailed information about processing steps and the migration log.
-
During the update process, you must log in as an administrative user.
-
Enter a user name and password for the administrative system user.
-
Click Connect.
-
Once processing is complete, click Next.
-
On the Create SQL server logins page, enter the login name, the password, and password confirmation for the SQL Server logins for configuration users and end users.
NOTE: This page is only shown if you have chosen granular permissions on the Create a new login for administrators page and the SQL Server login are not yet available on the database server.
-
The Processing database tasks page is only shown if there are still DBQueue Processor tasks queued in the DBQueue that are prerequisite for installing the database. Once processing is complete, click Next.
-
On the Database Agent Service information page, you are informed that the Database Agent Service must be installed. Click Next.
-
On the last page of the Configuration Wizard, click Finish.
-
In the Designer, adjust the database's staging level.
-
In the Designer, select the Base Data > General > Databases category.
-
Select the database and change the value of the Staging level property to Test environment or Development system.
-
Select the Database > Commit to database and click Save.
-
Verify in the Designer
-
Customize the synchronization project's connection data in the Synchronization Editor.
After extending the server hardware for the SQL Server, the DBQueue Processor must be initialized again.
To initialize the DBQueue Processor manually
-
Wait until all DBQueue Processor tasks have completed. You can do this using the .
-
Start a suitable program for running SQL queries and perform the following steps one by one.
IMPORTANT: Select a user that you use for migrating the database to run the SQL queries.
-
Check whether other database sessions are active.
select *
from sys.sysprocesses p
where dbid = DB_ID()
and spid <> @@SPID
If there are still sessions active, they must be closed first.
-
Stop all DBQueue Processor components.
exec QBM_PWatchDogPrepare 1
go
exec QBM_PDBQueuePrepare 1
go
-
Initializing the DBQueue Processor.
exec QBM_PDBQueuePrepare 0,1
go
exec QBM_PWatchDogPrepare
go
For more information about using the DBQueue Processor, see the One Identity Manager Configuration Guide.
You can use various command line programs for the automation of One Identity Manager implementations.
Detailed information about this topic
