Host profiles and PROD

Create a profile

You create the profile in the popup, on a page of the system. It applies to exactly this host with its port: s4d.example.com:44300 and s4d.example.com are two profiles.

1. The traffic light shows Red – PROD system and the profile’s name.
2. Name: 1 to 24 characters. The first four characters appear as the short name on the icon.
3. Colour: Blue, Green, Orange, Red, Purple or Grey.
4. Productive system (PROD): lock runtime changes.

1. Open the app on the system and click the FrontTailor icon.
2. Under Profile for <host>, enter a Name, for example PRD.
3. Choose a Colour.
4. Tick Productive system (PROD): lock runtime changes.
5. Click Save profile. “Profile saved” appears, and the lock applies right away, without a reload.

Remove deletes the profile again. Profiles live only locally in the browser profile. With from Team you share them with all colleagues as a team package (Team packages); system compare and the release check work with your host profiles, too.

What the traffic light shows

Red wins over yellow: on PROD you see the errors in the popup and in the Overview tab, the icon stays red.

What is locked on PROD

On a PROD host everything that only reads stays allowed: inspector, models, OData console, system info, copying and exports. All runtime changes are locked:

1. The note “PROD system: live edit is locked.” appears without a reload as soon as the profile is saved.

1. The tag PROD – locked in the card’s header.
2. The note “PROD system: runtime changes are locked.”

PROD by policy

Administrators define PROD hosts centrally with the prodHosts policy (patterns such as *.prod.example.com, see Enterprise deployment). On such hosts the PROD box in the popup is ticked and locked, with “Marked as PROD by your administrator.” below it. You can still choose name and colour yourself.