In your UM Cloud installation you cannot just SSH into your machine and edit one of the well-known configuration files (cmsbs.properties, additional.attributes etc.) to update certain global settings, modify the data model or add custom CSE plugins.
This section shows how these tasks can be carried out for a Cloud UM.
Create a custom UM Plugin
In order to have a similar degree of control over your Cloud UM as you are used to from an on-premise installation, you need to create a custom UM Plugin. This Plugin may contain your custom Core Scripting Engine code – if any – but also attribute configuration and other global settings that you would otherwise put into your cmsbs-conf/cmsbs.properties file.
You can follow along Providing a custom Plugin for the UM Cloud to create an empty Plugin, test it locally and have it included in your UM Cloud instance.
Manipulating the data model (aka additional.attributes)
In a UM Cloud environment it is generally not a good idea to overwrite the global cmsbs-conf/additional.attributes file as it is provided by Pinuts and might (need to) be updated in the course of a UM update. Instead, you can create incremental changes by putting cmsbs-conf/conf.d/*.attributes files into your Plugin.
The following example shows how to setup a TABLE attribute and add it to the std_personal attribute group.
Please remember that adding new primary attributes or adding columns to an already existing TABLE attribute require providing Automating Database Schema Updates.
env/…
.properties
Ladereihenfolge der Konfigdateien
Unsere ganz vorn mit _pi.*
Tip:
Extras / System / …