Identifying the itx v1 domain – Grass Valley iTX System v.2.6 User Manual
Page 384
Enabling iTX v2 to use the assets in an iTX v1 system
Enabling iTX v2 to use the assets in an iTX v1
system
For iTX v2 to be able to use assets in an iTX v1 system, two extra services must run in the iTX
v1.x domain.
•
The OPUS 2 iTX Bridge Service.
•
The Text Search Index Service.
You may install these on their own machine. Or you may install them on a machine in the iTX v2
system; in which case, we recommend you install them on the Database Server machine.
You must not, though, install the services on any machine in the iTX v1.x system; otherwise, the
iTX Installer would modify the v1.x installation.
When you install the services, you configure them to operate in the v1.x system. You configure
the iTX v2 system to link to the v1.x system.
Identifying the iTX v1 domain
Locator Services in iTX v2 and iTX v1 systems enable the two systems to communicate with
each other. For this to be possible, each Locator Service must have its domain name assigned to
it.
For an iTX v2 system, this happens when you enter the domain and Locator Service details in
the iTX Domain Configuration dialog during the installation of the Database Server module.
For an iTX v1 system, which is unlikely to be set up for multi-domain operations, you may need
to enter a domain name in a Locator Service configuration file, DomainConfig.xml. You do this
by using the Locator Service Configuration tool on the iTX v1 Database Server machine.
Enter a domain name in the Domain Name box and the address of the Locator Service in the
Primary Locator Uri box:
The Locator address requires the prefix “tcp://” and the port number 8999.
Check that the Locator Service window shows the domain name in the Service Info panel:
You may need to restart the Locator Service.
March 2015
System Administrator Guide
Page 384 of 404