Manipulating table catalogs

You can use the Campaign session utility to manipulate table catalogs outside of Campaign.

A common use of XML table catalogs is to perform global search and replace of data source names, for example to convert a table catalog developed for use against a test database, so that it works against a production database. In this case, you can export the table catalog as XML, perform global search and replace as needed, then save the XML table catalog and load it for use.

Step 1 - Convert to XML format

You use the Campaign session utility only for the first step of this process, which is to generate an XML format file that contains all the data from the requested catalog. If the catalog is already in an XML format, this step is not required.

Use the command:


unica_acsesutil -t catFileName -x [-o outputFileName] [-u] [-p] 
[{-a | -n | -l}][-S dataSource -U DBUserName -P DBPassword]

Step 2 - Edit as needed

You can now edit the XML file generated in step 1 as needed. To ensure that the file remains well formed, you should use an XML editor that checks the file syntax.

Step 3 (optional) - Convert to binary format

If required, you can convert the XML catalog file back to a binary format catalog.

Use the command:

unica_acsesutil -t <catFileName> -x -o <outputFileName>

Keeping catalogs in XML format risks exposing data access passwords. If you maintain catalogs in XML format, you should ensure that the file(s) are protected at the operating system level.

Step 4 - Load the new catalog in a session

Are conversion back into a binary format, you can now load the new catalog into a session.