After you set up content federation from an external repository, you can set up
federation of documents from other repositories.
About this task
In a highly available environment, you must resynchronize the connectors, data maps, and
session pools across all nodes after you make configuration changes.
Ensure that you maintain a
one-to-one correspondence of the following items:
- External repositories
- Extended connectors
- RMI proxy connectors
- Data maps
- Connectors added to the session pool
- Federator databases or table spaces
- Fixed content devices
- Fixed storage areas
Procedure
To set up additional external repositories:
- Create an RMI proxy connector for IBM® Content Integrator.
- Make a copy of the installed RMI proxy server startup script
(RMIBridge.bat or RMIBridge.sh) and change the RMI
registry port (VBR_RMIPORT) and any required Java™ command-line
arguments to start the RMI Connector external VM service. Run the new startup script and restart the
VeniceBridgeServices script.
- Create a connector by using the IBM Content Integrator Administration tool.
Specify the RMI proxy connector URL that you created for this
connector.
- Create a data map for the connector by using the IBM Content Integrator Administration tool.
- Create a session pool for this connector in the IBM Content Integrator Administration tool by using
the naming convention SessionPool-connector_name.
- Create additional
Federator databases, table spaces, and users.
- Configure the Federator database or table space.
Note: The Federator database that you configured when you installed the IBM
FileNet® CFS for Content Integrator software is by default the primary, or master, database. For
all subsequent Federator databases that you create, use the following steps:
- Open the Federation Administration application and go to the Advanced
Configuration page.
- In the Federator Databases section, click the
Edit icon for an existing database or click Add
Database.
- Enter the information for your database.
- Click Apply.
- Create a fixed content device and fixed storage area for the repository.
- Verify that you can federate documents from the additional
external repository to Content Platform Engine,
as follows:
- Stop the Content Platform Engine application server and the content
federation exporter if they are running.
- Open a browser and log on to the Federation Administration application.
- On Rule Builder page, create a rule.
Important: Be sure to select the correct data map.
- On the Rule Management tab, click Apply to start the exporter. The exporter processes the rule that you created.
- Refresh the Rule Management page to view the updated rule status. If the
rule status changes to Federated and there are no errors, the documents were
successfully federated. If there were any errors, correct the errors before you continue.
- Open the new (non-master) Federator database that you created and verify that there are entries
in the fdb_version_series table that correspond to the documents you federated.