| Daniel Espen | e9fd695 | 2019-10-11 11:01:16 +0200 | [diff] [blame] | 1 | # ############################################################## |
| 2 | # Directory configuration file |
| 3 | # ############################################################## |
| 4 | |
| 5 | |
| 6 | |
| 7 | |
| 8 | # ############################################################## |
| 9 | # Directory server configuration |
| 10 | |
| 11 | |
| 12 | # URL and type of uplink server. Forward all requests that we cannot satisfy here to uplink |
| 13 | # - URL of uplink directory server |
| 14 | # - Type of uplink server. Currently supported is BASYS (BaSys registry API) or DNS (DNS server processing legalBody tag) |
| 15 | cfg.uplink = |
| 16 | cfg.uplink.type = DNS |
| 17 | |
| 18 | |
| 19 | # Downlink servers, forward matching URI patterns to downlink servers |
| 20 | # - Match all subunits that end with "is.iese", including "is.iese" |
| 21 | cfg.downlink.is.pattern = is.iese |
| 22 | cfg.downlink.is.directory = http://wherever1 |
| 23 | |
| 24 | # - Match all subunits that end with "pm.iese", including "pm.iese" |
| 25 | cfg.downlink.pm.pattern = pm.iese |
| 26 | cfg.downlink.pm.directory = http://wherever2 |
| 27 | |
| 28 | # - Match all subunits that end with ".es.iese", but not "es.iese" |
| 29 | cfg.downlink.es.pattern = .es.iese |
| 30 | cfg.downlink.es.directory = http://wherever3 |
| 31 | |
| 32 | |
| 33 | |
| 34 | |
| 35 | # ############################################################## |
| 36 | # Directory entries |
| 37 | |
| 38 | # Example AAS for device1 |
| 39 | # - Every device has a name that is not related with its ID. The name is just used to keep the |
| 40 | # configuration entries for this device together. |
| 41 | # - This is the AAS ID. We are using URIs here as AAS IDs |
| 42 | # - An URI is structured as following: urn:<legalBody>:<SubUnit>:<version>:<revision>:<elementID>#<instance> |
| 43 | # - The subunit may be separated into namespaces using dots '.' |
| 44 | device1.id = urn:de.FHG:es.iese:aas:0.98:5:lab/microscope#A-19 |
| 45 | # - This is the directory entry. Depending on the type parameter, this is either the AAS or a |
| 46 | # reference to the AAS provider |
| 47 | device1.aas = {content.aas1} |
| 48 | # - These are optional AAS tags that may be used to find an AAS |
| 49 | device1.tags = first,group1 |
| 50 | # - The type field indicates whether an AAS is a local AAS (serialized AAS data is stored in directory), |
| 51 | # whether it is a remote AAS (AAS data is provided by another provider in the network), or whether it |
| 52 | # is a proxy that forwards all requests to a different AAS with the given AAS ID (specified as URI) |
| 53 | device1.type = local |
| 54 | |
| 55 | |
| 56 | |
| 57 | # Minimum example AAS for device 2 |
| 58 | # - It defines no tags and no type |
| 59 | device2.id = urn:de.FHG:es.iese:aas:0.98:5:lab/microscope#A-18 |
| 60 | device2.aas = {content.aas2} |
| 61 | device2.type = local |
| 62 | |
| 63 | |
| 64 | # Example AAS for device 3 |
| 65 | # - This AAS is tagged to enable its discovery |
| 66 | device3.id = urn:de.FHG:es.iese:aas:0.98:5:lab/microscope#A-17 |
| 67 | device3.aas = {content.aas3} |
| 68 | device3.tags = third,group1,group2 |
| 69 | device3.type = local |
| 70 | |
| 71 | |
| 72 | # Example AAS for device 4 |
| 73 | # - This AAS is tagged to enable its discovery |
| 74 | device4.id = urn:de.FHG:es.iese:aas:0.98:5:lab/microscope#A-16 |
| 75 | device4.aas = {content.aas4} |
| 76 | device4.tags = fourth,group2 |
| 77 | device4.type = local |
| 78 | |