Synchronizing assets manually
By default, data available in the application is synchronized automatically with InfoSphere® Information Governance Catalog. However, in some cases you need to run manual synchronization.
Purpose
In the following cases, you must synchronize data manually. Otherwise, it is not available in the application.
- After you upgraded from an earlier version of InfoSphere
Information Governance Catalog and already
have data in the catalog. In this case, you must complete the following procedure only once. Use the
-caDefinitions
,-bundleAssets
, and-all
parameters together when you run the graph batchload command to synchronize all assets. - When you import assets of type ETL. Each time you import assets of this type to InfoSphere
Information Governance Catalog by using
the
istool
command, you must synchronize data manually. When you synchronize ETL assets manually, you must run the reindex steps in order to search for ETL assets in catalog search. For details, see the Rebuilding the index for InfoSphere Information Server clients topic. - After you install IBM® InfoSphere Information Server Enterprise Search, you must synchronize the following asset types manually: Data Classes, Data Rules, Data Rule Sets, Data Rule Definitions, Data Rule Set Definitions, and Host.
- When you manually install IBM InfoSphere Information Server Enterprise Search in addition to the base installation of IBM InfoSphere Information Server. You must synchronize all asset types, and rebuild the index. This applies to 11.7.0 releases.
Location
For the location details, see the Location of the istool command line topic.
Command syntax
Optional parameters and optional values in the syntax are enclosed in brackets, [
].
graph batchload
authentication parameters
[generic parameters]
-command
-types
-groups
[-all]
[-caDefinitions]
[-caValuesOnly]
-bundleAssets
-bundleTypesOnly
[-rids]
Parameters
- authentication parameters
- Required. All asset interchange commands use authentication parameters to connect to a specific installation of InfoSphere Information Server.
- generic parameters
- The generic parameters are available to all asset interchange commands. Use the generic parameters to request help on command syntax, to specify silent or verbose operation, and to use a script to run commands.
- -command | -c
- Required. This parameter specifies the command to be run. Supported values are START, STOP, and CONTINUE.
- -types | -t
- One of parameters
types
,groups
,bundleAssets
, orbundleTypesOnly
is required to start or restart the synchronization. - -groups | -g
- One of parameters
types
,groups
,bundleAssets
, orbundleTypesOnly
is required to start or restart the synchronization. - -all | -a
- Optional. This parameter specifies that all supported asset types and assets are synchronized,
except definitions of custom attributes of type relationship. To synchronize relationships between
assets defined by these definitions, run synchronization with both
-caDefinitions
and-all
parameters. - -caDefinitions | -cad
- Optional. This parameter specifies that all existing definitions of custom attributes of type relationship are synchronized. The actual relationships between assets that are defined by using these custom attributes are not synchronized when you use this parameter.
- -caValuesOnly | -cav
- Optional. This parameter specifies that all relationships between assets which are defined by custom attributes of type relationship are synchronized. The definitions of these custom attributes are not synchronized when you use this parameter.
- -bundleAssets | -ba
- One of parameters
types
,groups
,bundleAssets
, orbundleTypesOnly
is required to start or restart the synchronization. - -bundleTypesOnly | -bto
- One of parameters
types
,groups
,bundleAssets
, orbundleTypesOnly
is required to start or restart the synchronization. - -threads | -thr
- Deprecated. This parameter has no effect.
- -rids | -r
- Optional. This parameter specifies the rids (unique identifiers of assets) of particular assets that you want to synchronize.
Example
- Start the synchronization of selected assets, and all custom
assets:
graph batchload -u isadmin -p mypassword -c START -types DSProject,DSJobDef,DSSharedContainerDef,DSLocalContainerDef,DSTableDefinition -bundleAssets
- Stop the synchronization of selected assets, and all custom
assets:
graph batchload -u isadmin -p mypassword -c STOP
- Restart the synchronization of selected groups, and all custom
assets:
graph batchload -u isadmin -p mypassword -c CONTINUE -groups igc,db -bundleAssets
Checking synchronization status
You can check the status of the synchronization process in the following mappers log
file:
kubectl logs shop4info-mappers-service-0
Depending on the process status, you can see the following messages:
- The synchronization process is
started:
2019-05-13 06:47:40.455 INFO NONE 8 --- [threadname] c.i.i.u.k.i.InitialLoadMapper : Started
- The new synchronization process is started when the previous one is not
finished:
2019-05-13 06:47:40.517 INFO NONE 8 --- [threadname] c.i.i.u.k.i.InitialLoadMapper : Already running
Note: The new synchronization process cannot be started when a previous one is still in progress. Wait for the first process to finish and then start a new one. - The synchronization process finished for one asset
type:
2019-05-13 06:48:05.124 INFO NONE 8 --- [threadname] c.i.i.u.k.i.TypeListProcessor : Completed processing type: BusinessRule
Note: If you notice
Unexpected mismatch of provider types
errors in the log file,
see the technote for more information.