Caution: In the raddbutil
commands shown here, there are no spaces after the commas. If you cut and paste these commands from this guide or the online help, be sure to remove any spaces introduced by the paste operation.
- Connect to the test CSDB and use the
raddbutil
tool to export the relevant deck:- Go to the Configuration Server
bin
directory on the system where you want to export the data (the test environment). - If the
admin
user has a password, use the following command:raddbutil EXPORT DATA=TRUE,WALK=TRUE,OUTPUT=
<tempDir>,USERID=admin,PASSWORD=
<password> PRIMARY.
<DOMAIN>
If the admin
user does not have a password, use the following command:
raddbutil EXPORT DATA=TRUE,WALK=TRUE,OUTPUT=
<tempDir>,USERID=admin PRIMARY.
<DOMAIN>
In both cases, <tempDir> is the directory where the exported files will be placed on the test CSDB system.
For more information, see Configuration Server Database Utility (RadDBUtil) in the HP Client Automation Enterprise Configuration Server Reference Guide.
- Transport the relevant deck files to the production CSDB system using the file transfer mechanism of your choice.
- On the production CSDB system, use the
raddbutil
tool to import the relevant deck:- Go to the Configuration Server directory on the system where you want to import the data (the production environment).
- If the
admin
user has a password, use the following command:raddbutil IMPORT INPUT=
<tempDir>,COMMIT=TRUE,ACCEPT=A+D+U,USERID=admin,PASSWORD=
<password>
If the admin
user does not have a password, use the following command:
raddbutil IMPORT INPUT=
<tempDir>,COMMIT=TRUE,ACCEPT=A+D+U,USERID=admin
In this case, <tempDir> is the directory on the production CSDB system where the files were placed in the step Transport the content to the HPCA Core server..
- In the production environment, load the production Reporting database using the “master” content in the relevant deck that you just imported.
There are two ways to do this:
In either case, using the CSDB_MASTER content source forces the update tool to only update the Reporting database content and bypass performing any updates to the packages linked to the relevant content. This ensures that the service content you deployed in your test environment will exactly match the content that you will be deploying in your production environment.