Domain Infrastructure

The domain namespace infrastructure consists of two sections: The Database Collections and the Event topics.

Database collections

The database collections can either be created while creating a new root entity or in the infrastructure page by using the Create capability. Each root entity has to be assigned to a database collection.

Create database collection

Property Description
Local identifier

This is the identifier (name) of the database collection. It is unique within a namespace. Please note that only the characters A-z (without special characters), digits and the special character "_" are permitted for naming database collections! Furthermore, identifiers may not begin with a digit and the first character must be lowercase. The local identifier cannot be changed after creation.

This field is mandatory.

Notes

This is a description of the database collection.

This field is optional.

Edit a database collection

You edit the master data of a database collection by using the Information capability and navigating to the Details view where you can navigate to the Master data section and use the Edit master data capability. Alternatively, you can use the inline or header Edit capability. For a description of the master data, see the section Managing Infrastructure. The local identifier cannot be changed. When editing the master data of a database collection, you can overwrite the values for notes. The overwritten values are lost as soon as the editing action has been completed.

Delete a database collection

You can delete the database collection by using the inline or header Delete capability in the infrastructure overview page . Alternativerly, you can use the Information capability to access the details view and there you can use the Delete capability.

You can only delete a database collection if it is not in use. You can check the usages of a database collection. by using the Information capability and navigating the Usages section.

You will need to confirm the action before the selected response is permanetely deleted.

Event Topic

Event topics are used to define a channel in which events are published. For each domain namespace a default event topic is automatically created. They are used to publish events. It is possible to create new event topics. However, when an event topic is not created then the default event topic is used automatically. Event topics are unique within a cluster and once they are published, they cannot be deleted anymore.

Create event topic

Property Description
Local identifier

This is the identifier (name) of the entity. It is unique within a namespace. Please note that only the characters A-z (without special characters), digits and the special character "_" are permitted for naming entities! The Database collection cannot be changed after creation.

This field is mandatory.

Global A global topic allows to publish and consume events also to/from another solution(s). Therefore you have to create a similar topic with the same namespace prefix and the same name in other solution(s). In addition also the events have to be modelled similar in the other solution(s).

This field is optional.

Attention: Please be aware that this functionality is experimental and can be changed in upcoming versions without further notice.
Retention Hours

Defines the period of a time the information regarding the event is save on a topic before it is discarded. The possible retention hours are: 1…720, with the value of the automatically created default value being 24 hours.

This field is mandatory.

Notes

This is a description of the event topic.

This field is optional.

Edit a event topic

You edit the master data of an event topic by using the inline or header Edit capability. For a description of the master data, see the section Managing Infrastructure. The local identifier cannot be changed. When editing the master data of an event topic, you can overwrite the values for notes. The overwritten values are lost as soon as the editing action has been completed.

Delete an event topic

You can delete the event topic by using the inline or header Delete capability. Alternativerly, you can use the Information capability to access the details view and there you can use the Delete capability.

You can only delete a response if it is not in use. You can check the usages of an event topic by using the Information capability and navigating the Usages section.

You will need to confirm the action before the selected response is permanetely deleted.