The Update procedure
This repository update adds RabbitMQ connection objects to the repository. Run it when the product version supports RabbitMQ but the connection group is missing from the designer. Message queues are useful. Missing metadata is just a queue of one problem, waiting patiently.
It applies to repositories used by Advanced ETL Processor and Visual Importer ETL.
Before you run the SQL
- Create a repository backup.
- Stop services using the repository.
- Confirm that the repository belongs to the product installation you are upgrading.
- Run the update once, then restart the application.
Run this SQL against the repository
Insert into OBJECT_TYPES
(OBJECT_TYPE,OBJECT_TYPE_NAME,OBJECT_TYPE_GROUP)
Values
(915,'RabbitMQ Connection',29000)
Insert into OBJECT_TYPES
(OBJECT_TYPE,OBJECT_TYPE_NAME,OBJECT_TYPE_GROUP)
Values
(916,'RabbitMQ Connections',29000)
INSERT INTO OBJECTS_TREE
(OBJECT_ID,
PARENT_ID,
NAME,
OBJECT_TYPE
)
Select
OBJECT_ID*-8 as OBJECT_ID,
PARENT_ID,
'RabbitMQ' as NAME,
915 as OBJECT_TYPE
From
OBJECTS_TREE
where
OBJECTS_TREE.OBJECT_TYPE=322
UPDATE OBJECT_TYPES
set OBJECT_TYPE_GROUP=29000
WHERE OBJECT_TYPE= '915'
UPDATE OBJECT_TYPES
set OBJECT_TYPE_GROUP=29000
WHERE OBJECT_TYPE= '916' After the repository update
Restart the product and check the connection tree. RabbitMQ should appear as an available connection group. If it does not, check that the repository connection points to the database you updated.
RabbitMQ is a trademark of VMware, Inc. in the U.S. and other countries.