blob: aa395396cfa57d051857ea4d0271bbf051e2625f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
|
#####################################################
#
# Hooks for specific environment configurations
#
#####################################################
# Indicator for whether to use AAF for authentication
UseAAF: false
enableCADI: false
# Stub out southbound calls for Unit Test cases to run. e.g. not timeout
# Comment out in other environments to get default (No)
#UnitTest: Yes
#####################################################
#
# Settings for Southbound API: Datarouter
#
#####################################################
# URI to retrieve dynamic DR configuration
ProvisioningURI: /internal/prov
# indicator for handling feed delete:
# DeleteOnDR - means use the DR API to DELETE a feed. (default for backwards compatibility)
# SimulateDelete - means preserve the feed on DR (after cleaning it up), and mark as DELETED in DBCL. Better for cloudify environments.
Feed.deleteHandling: SimulateDelete
###########################################################
# The following properties default to match ONAP DR instance.
# However, there are some non-ONAP DR instances that require other values.
# Sets the X-DR-ON-BEHALF-OF HTTP Header value
#DR.onBehalfHeader:
# Value for the Content-Type Header in DR Feed API
#DR.feedContentType:
# Value for the Content-Type Header in DR Subscription API
#DR.subContentType:
#
# END OF properties helpful for non-ONAP DR instance.
############################################################
#####################################################
#
# Settings for Soutbound API: Postgresql
#
#####################################################
# flag indicates if we are using postgresql
UsePGSQL: true
# postgres host name
# Need to connect to PG primary service, designated by service.name2
DB.host: dbc-pg
# postgres schema name
DB.schema: dmaapbc
# postgres user name
DB.user: dmaapbc
# postgres user password
DB.cred: secret
#####################################################
#
# Settings for Soutbound API: Message Router
#
#####################################################
# indicator for multi-site (locations) deployment. Give clue to buscontroller whether
# there is a need for message replication between edge and central.
# ONAP Casablanca is a single site deployment
MR.multisite: false
# FQDN of primary message router.
# In ONAP Casablanca, there is only 1 message router service, so use that.
# In a multi-site, MR cluster deployment, use the CNAME DNS entry which resolves to the primary central MR
MR.CentralCname: message-router
# Indicator for whether we want hostname verification on SSL connection to MR
MR.hostnameVerify: false
# MR Client Delete Level thoroughness:
# 0 = don't delete
# 1 = delete from persistent store
# 2 = delete from persistent store (DB) and authorization store (AAF)
MR.ClientDeleteLevel: 1
# namespace of MR Topic Factory
MR.TopicFactoryNS: org.onap.dmaap.mr.topicFactory
# AAF Role assigned to Topic Manager Identity
MR.TopicMgrRole: org.onap.dmaap-bc-topic-mgr.client
# MR topic ProjectID (used in certain topic name generation formats)
MR.projectID: mr
# Use Basic Authentication when provisioning topics
MR.authentication: none
# MR topic name style (default is FQTN_LEGACY_FORMAT)
#MR.topicStyle: FQTN_LEGACY_FORMAT
#
# end of MR Related Properties
################################################################################
#####################################################
#
# Settings for authorization of DBCAPI
#
#####################################################
# Namespace for URI values for the API used to create AAF permissions
# e.g. if ApiNamespace is X.Y.dmaapbc.api then for URI /mr_clients we create AAF perm X.Y.dmaapbc.api.mr_clients
ApiNamespace: org.onap.dmaap-bc.api
# If API authorization is required, then implement a class to enforce it.
# This overrides the Class used for API permission check.
ApiPermission.Class: org.onap.dmaap.dbcapi.authentication.AllowAll
#####################################################
#
# Certificate Management
#
#####################################################
# Indicates how we are expecting certificates to be provided:
# cadi - a set of artifacts will be downloaded from AAF at deployment time, and details will be in a cadi properties file
# legacy (default) - artifacts will be installed manually or some other way and details will be in this file
CertificateManagement: legacy
# When CertificateManagement is cadi, then this is where all the cadi properties will be.
# Note that the cadi properties include where the cert is, and the encrypted passwords to read.
cadi.properties: /opt/app/osaaf/local/org.onap.dmaap-bc.props
#####################################################
#
# HTTP Server Configuration
#
#####################################################
# Allow http access to dbcapi
HttpAllowed: true
# listen to http port within this container (server)
IntHttpPort: 8080
# listen to https port within this container (server)
# set to 0 if no certificates are available.
IntHttpsPort: 0
|
