This section briefly discusses the relationships between
the Content Integrator components and then describes in detail how to configure
the Content Integrator system catalog and Server log.
As you start working with Content Integrator, it is helpful
to keep in mind the relationships between the various Content Integrator
components: the Composer, the Server, the Server Manager, the system catalog,
and the Server log. The following diagram illustrates the relationships
between these components.
Composer and Server
The Composer is the Content Integrator development
environment. It consists of a graphical interface with wizards and property
sheets for creating Content Integrator objects. The Composer writes the
definition of each object to the Content Integrator system catalog.
The Content Integrator Server reads the system catalog
in order to run the objects.
The Composer and Server can point to (or interact with)
only one system catalog at a time.
The system catalog is a database or folder that contains
the definitions for all the Content Integrator objects. Content Integrator
supports system catalogs in several database formats. For a list of supported
formats, see "Creating a New System Catalog". Depending on your
particular configuration of ecKnowledge, you may have multiple system catalogs.
In order to work together, the Content Integrator Composer and the Content
Integrator Server must point to the same system catalog. Similarly, if
you have multiple Composers and Servers for the same set of objects, they
must all point to the same system catalog. See "Selecting the System
Catalog" for information on changing system catalog settings in the
Composer and Server Manager.
By default, when you install Content Integrator, the Composer
and Server will point to a system catalog that stores a number of sample
Content Integrator applications. To run the sample applications, the Composer
and Server must both point to this particular system catalog (located,
by default, in the Examples subdirectory of the Content Integrator Program
If you wish, you can use the same Examples system catalog
to define your own Content Integrator applications for testing purposes.
However, it is recommended that you create a different system catalog to
use for real-life production jobs. See "Creating a New System Catalog"
for information on how to create a new system catalog.
The Content Integrator Server writes the progress of each
Content Integrator job to the Content Integrator Server log, which is either
a database or folder. As with the system catalog, Content Integrator supports
logs in several database formats. For a list of supported formats, see
"Creating a New System Catalog".
By default, the Server points to a particular log and will
use the same log for all subsequent jobs that you run. If you want the
Server to use a different log, you can use the Server Manager to change
the log file that it points to. For example, you will probably want a separate
log file for each system catalog. See "Selecting the Log Location"
for information on how to point the Server to a different log.
Selecting the System Catalog
As mentioned previously, the system catalog is a database
or folder that stores all the information about Content Integrator objects.
The Composer writes Content Integrator object definitions to the particular
system catalog to which it points. An Content Integrator Server must point
to the same system catalog in order to run those objects. The system catalog
is thus the means of communication between the Composer and the Server.
If you install the Content Integrator Composer and Server
at the same time and on the same computer, they will automatically point
to the same system catalog and will be able to communicate with each other
However, if you install the Composer and Server at different
times or on different machines, or if you install multiple copies of the
Composer or Server, you may need to adjust the system catalog settings
in order for the different components to communicate with each other and
operate on the same set of objects. The same is true when you move objects
from a development or test environment to a production environment.
Note: One indication that you need to adjust the
system catalog setting is if the Composer or Server cannot locate a particular
Content Integrator object that you want to edit or run.
The Options dialog box in the Composer — and the Properties
window in the Server Manager — show the current system catalog settings
for the Composer and Server, respectively. The remainder of this section
describes how to view and change the system catalog settings. The rest
of this chapter describes how to view and adjust the log settings, how
to create a new system catalog or log, and how to copy or migrate objects
between system catalogs.
Changing the Composer's System Catalog Setting
WARNING: The system catalog contains crucial Content
Integrator information. Never edit it by hand, unless specifically told
to do so by CASAHL Technology personnel. Hand-editing under any other
circumstances can create unpredictable results, including possible corruption
of connections and databases.
To view the Composer's current system catalog setting,
launch the Composer and select View | Options. The Options
dialog box shows the Composer's current system catalog setting:
In this example, the Database Type field is set to "Access",
indicating that the current system catalog is a Microsoft Access database.
As noted in "System
Catalogs and Logs Installed by Content Integrator", Access is the
default database type for system catalogs.
The other fields, below Database Type, contain additional information to
identify the specific system catalog database. The required information
varies, depending on the type of database, but usually includes the path
and file name of the system catalog database and any associated login information.
To switch to another system catalog of the same database
type, click on the Browse button ("...") to the right of the
Database field (below Database Type). The system will display a dialog
box with a list of available databases. Select the system catalog
you want to use. Then click on the Open button to close the dialog
box and return to the Options screen, with the selected database loaded
into the Database field.
To choose a system catalog of another database type, select
the desired database type from the drop-down list and enter the information
to identify the desired system catalog. Then click on the Browse button
to select the specific system catalog database. You can select to use any
of the system catalogs that were installed with Content Integrator (see
"System Catalogs and Logs Installed by Content Integrator"),
or you can select one that you created post-installation (see "Creating
a New System Catalog").
Note: If the system catalog you want to use resides
on another computer, you must first establish a Windows "share"
on that machine so that you can access the file over the network. You must
also have an account on the remote machine.
System Catalogs and Logs Installed by Content Integrator
As part of the installation process, Content Integrator
installs the following five "empty" system catalogs (containing
no Content Integrator objects) and log files:
These empty file sets are installed in the top-level Content Integrator
program directory (the default is C:\Program Files\QuickrContent Integrator).
It is recommended that you save a copy of these empty files in another
directory post-installation, so they can be used as templates later, if
The Content Integrator installation process also installs
a system catalog containing various sample applications that you can study,
experiment with, and use as models for creating your own Content Integrator
jobs. Content Integrator creates this "Examples" system catalog
and a corresponding log (both in Microsoft Access format) and places them
in the "\Examples" subdirectory within the Content Integrator
program directory. (For more information, see Chapter 6, "Getting
Started: Content Integrator Sample Applications".)
During the installation, Content Integrator prompts you
to select which system catalog to point to initially. If you do not choose
the Examples system catalog (or your previous catalog, if you are upgrading
from a previous version of the software), Content Integrator will use the
empty Access database in the top-level Content Integrator program directory
as the default system catalog and log.
Changing the Server's System Catalog Setting
Any Content Integrator objects you define will be stored
in the system catalog that the Composer is pointing to when you define
the object. To run Content Integrator jobs that are based on those objects,
the Content Integrator Server must point to the same system catalog.
To view the Server's system catalog settings, launch the
Server Manager, and click on the desired Server name. Then select Server
The System Catalog page in the Server Manager's Server
Properties screen shows the current system catalog settings:
The following screenshot shows an example of the System
To change the Server's current system catalog settings,
enter the appropriate information on the System Catalog page, and then
click on the OK button to save your changes. In most cases, you
will need to restart the Server in order for the changes to take effect.
Selecting the Log Location
The Server records the progress of each Content Integrator
job in the Content Integrator log. By default, the Server points to a particular
log file. Ordinarily, the Server will use the same log for all subsequent
jobs that you run. If needed, you can change the settings in the Server
Manager to point the Server to a different log file or database. If you
do this, the Server will continue to use the new file until you change
its settings again.
To change the log that a Server uses, launch the Server
Manager, select Server | Properties, and display the Log
Like the system catalog, by default, log databases are
stored in Microsoft Access format, but they can be stored in a number of
other formats as well. Usually, the System Catalog and log will have
the same file format. For a list of allowed formats, see "Creating
a New System Catalog" below. For a list of empty (template) log files
installed with Content Integrator, see "System Catalogs and Logs Installed
by Content Integrator". For information on creating a new log file
when the old file is full or creating log files in other formats, see "Creating
a New Content Integrator Log".
System Catalog Conversion Tool
The System Catalog Conversion Tool is an Content Integrator
utility program that allows you to copy or migrate selected objects (or
all objects) from one Content Integrator system catalog to another. Migrated
objects are converted to the format of the Destination system catalog.
The original objects in the Source system catalog remain unchanged.
Note: It is recommended that you make a backup copy
of both Source and Destination system catalogs before you begin working
with the System Catalog Conversion Tool.
To invoke this utility, type SCMigrate.exe from the Content
Integrator program directory. The following screen will appear:
The following sections describe how to use this utility.
Selecting the Source and Destination System Catalogs
The top portion of the System Catalog Conversion
Tool screen identifies the Source system catalog (where objects will be
copied from) and the Destination system catalog (where objects will be
copied to). Both system catalogs must already exist, although one of them
can be "empty".
By default, when this screen is first displayed, the Source
system catalog will be unassigned and the Destination system catalog will
be the system catalog that the Content Integrator Composer is currently
Select or enter the information needed to identify and
access the appropriate system catalogs. The Connection Type (that is, the
database type of the selected system catalog) determines what type of information
is needed. You can also use the "< >" button to reverse
the identities of the Source and the Destination.
In the example shown, the Source system catalog is the
Access database named "LotusQuickrTemplate.mdb" that is installed
with Content Integrator as an example, and the Destination system catalog
is an Access system catalog named "RASSYSCAT".
Specifying Migration Parameters
The remainder of the screen is where you enter the migration
You can select to "Migrate All Objects" from
the Source to the Destination (middle section of the screen), or you can
select to "Migrate Selected Objects" from one system catalog
to the other (bottom portion of the screen).
Migrate All Objects
Follow these steps to Migrate All Objects.
1. First, you must specify
the migration parameters. Do you want the migrated objects to be appended
to, or to replace, any previously existing objects in the Destination system
a. If you want to add the newly migrated objects to any
objects that are already in place in the Destination system catalog, then
select the option to "Append all entries to the destination".
b. If you want the newly migrated objects to replace any
previous objects in the Destination system catalog, then select the option:
"Delete all existing entries from destination, then Append".
you are ready, click on the Migrate All Objects button.
The System Catalog Conversion Tool will migrate all the objects from the
Source system catalog to the Destination. An error message will be displayed
if any objects cannot be migrated.
3. When the migration is
finished, you can point to a different Source or Destination system catalog
and migrate additional objects, or you can click on the Done button
at the bottom of the screen to exit the System Catalog Conversion Tool.
Note: The System Catalog Conversion Tool does not change the system
catalog settings in the Composer or Server Manager. You will need to change
these settings separately to point to the appropriate system catalog, if
needed. For details, see "Changing the Composer's System Catalog Setting"
and "Changing the Server's System Catalog Setting".
Migrate Selected Objects
The previous screenshot of the System Catalog Conversion
tool is repeated here for your convenience:
Follow these steps to Migrate Selected Objects.
1. First, select an Object
Type from the drop-down list (Replications and Import/Export objects, Real
Time Transactions, Stored Requests, VS .NET Applications, Connections,
Actions, Data Transformation, etc.).
2. Click on the Refresh
Objects button to the right of the drop-down list.
Content Integrator will display a list of all the objects of the selected
type that are currently stored in the Source and Destination system catalogs.
"Source Objects" are listed on the left side of the screen; "Destination
Objects" are listed on the right.
Note: The Refresh Objects button does not refresh or change
any objects in the actual system catalog databases. That is done by the
Copy and Delete buttons described in the next steps.
3. Above the list of Destination
Objects, select how you would like the conversion tool to handle any migrated
objects that have a "duplicate" (object with the same name) in
the Destination system catalog. You can direct the utility to always "Overwrite"
or always "Do not overwrite" any pre-existing duplicate objects
— or you can direct it to prompt you to
decide each case individually.
4. You can migrate one object
at a time or multiple objects all at once:
- To migrate an object, click on the object name in the
list of Source Objects to select it. Then click the Copy button
in the lower middle portion of the screen.
- To copy multiple objects at the same time, hold down the
Control key (CTRL) while you click to select the desired object
names. Then click on the Copy button to migrate all the selected
objects at once.
The conversion tool will migrate
each selected object and any associated component objects from the Source
to the Destination system catalog. For example, if you select to
migrate a replication job, the conversion tool will migrate the replication,
associated Source and Target connections, and any associated data transformations,
rules, events, or other component objects associated with the replication.
An error message will be displayed if any objects cannot be migrated.
5. You can delete one object at a time or multiple objects all at once:
- To delete an object from the Destination system catalog,
select the object name in the list of Destination Objects, then click on
the Delete button in the lower middle portion of the screen.
- To delete multiple objects at the same time, hold down
the Control key (CTRL) while you click to select multiple object
names. Then click on the Delete button to delete all the selected
objects at once.
The conversion tool will delete only the selected object(s) from the Destination
system catalog. An error message is displayed if any objects cannot be
Note: Clicking on Delete changes only the Destination system
catalog; it does not change the Source system catalog.
When you are finished, you can point to a different Source or Destination
system catalog and migrate (or delete) additional objects, or you can click
on the Done
button at the bottom of the screen to exit the System
Catalog Conversion Tool.
As noted previously, the System Catalog Conversion Tool does
not change system catalog settings in the Composer or Server Manager. For
information on changing Composer and Server Manager settings, see "Changing
the Composer's System Catalog Setting" and "Changing the Server's
System Catalog Setting".
to the Lotus Quickr Content Integrator Installation and Configuration Guide