Page History
Warning | ||
---|---|---|
| ||
This section is intended for hub administrators only. |
Here is a sample shrinesample shrine.conf file for a system running SHRINE 4.24.0 , for a node supporting researchers and distributing queries.
...
Next, configure the initial network structures and queues for the hub.
Download the shrine network lifecycle tool from https://repo.open.catalyst.harvard.edu/nexus/content/groups/public/net/shrine/shrine-network-lifecycle-tool/4.24.0-RC1/shrine-network-lifecycle-tool-4.24.0-RC1-dist.zip into /opt/shrine:
Code Block | ||||
---|---|---|---|---|
| ||||
cd /opt/shrine wget https://repo.open.catalyst.harvard.edu/nexus/content/groups/public/net/shrine/shrine-network-lifecycle-tool/4.24.0-RC1/shrine-network-lifecycle-tool-4.24.0-RC1-dist.zip -O shrine-network-lifecycle.zip unzip shrine-network-lifecycle.zip cd shrine-network-lifecycle |
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
shrine { queryEntryPoint{ audit { database { dataSourceFrom = "testDataSource" //Can be JNDI or testDataSource . Use testDataSource for tests and command line tools, JNDI everywhere else testDataSource { driverClassName = "com.mysql.cj.jdbc.Driver" //JDBC driver class name url = "jdbc:mysql://localhost:3306/qepAuditDBHUB?serverTimezone=UTC" //URL to your database credentials { username = "yourUserName" password = "yourDatabasePassword" } } } } } |
...
To configure for AWS SQS see SHRINE 4.4.0 Chapter 8.2.1 - Configuring a Hub for AWS SQS .
Kafka
Shrine can also be configured to use Kafka. Using Kafka requires setting up, securing, and maintaining a cluster of Kafka servers - more admin expertise, attention, and expense than AWS SQS without the benefits of AWS SQS' reliability.
To configure for Kafka see SHRINE 4.4.0 Chapter 8.2.2 - Configuring a Hub for Kafka .
Create the Network Record and Queues
...