DeploymentInformationType (Complex Type)

Items

• name

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Short name of this midPoint deployment. The name will be displayed on a prominent place in the user interface, most likely displayed as a part of the header (on every page). The name is usually used to distinguish between midPoint deployments in the same organization. Strings such as "DEVEL", "TEST", "UAT" are often used.

• description

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Free form description that specifies the details of this deployment. It may be significantly long (few paragraphs). It has no special purpose other then a form of "on-line" documentation for the deployment. It will NOT be displayed on every page. It will most likely be displayed on a system configuration pages or in configuration summaries.

• documentation

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Technical documentation for a particular object or construct.

  The purpose of this element is to document system configuration and behavior. The documentation will not be presented to end users. In fact, it will probably not be presented at all in midPoint user interface. This documentation element is supposed to be a part of the technical documentation of midPoint deployment. The tools than generate deployment configuration will look for these elements and combine them to compiled documentation document.

  AsciiDoc formatting is assumed for this element. Any leading or trailing whitespace is skipped. Indentation equivalent to he indentation of the first non-blank line of text is also skipped.

• headerColor

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Specification of a color that will be used as a background for a page header. The color can be used as a form of easy look and feel customization to match the customer corporate identity. But perhaps more often the color will be used to distinguish different midPoint environments in the same organization, e.g. green color for devel environment, blue color for testing, etc.

• skin

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Specification of the adminLTE skin that will be applied to the base template. The base template contains 12 predefined skins including: skin-blue, skin-blue-light skin-yellow, skin-yellow-light, skin-green, skin-green-light, skin-purple, skin-purple-light, skin-red, skin-red-light, skin-black and skin-black-light.

• logo

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Specification of a logo that will be used in the title bar on every screen. This can be used as an easy customization and point to a customer logo. Or it may be used as an icon to indicate the environment.

• customerName

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Short name of the organization that is end user of the midPoint deployment. It is supposed to be a company name, such as "ExAmPLE, Inc." It will be displayed together with subscription information.

• customerUrl

  Flags: RAM,runtime

  Multiplicity: [0,1]

  URL of the customer web site. It will be used as a link target in case that the customer name is displayed as hyperlink.

• partnerName

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Short name of the organization that deployed this midPoint instance. It is usually the name of Evolveum partner. It is supposed to be a company name, such as "ExAmPLE, Inc." It will be displayed together with subscription information.

• partnerUrl

  Flags: RAM,runtime

  Multiplicity: [0,1]

  URL of the partner web site. It will be used as a link target in case that the partner name is displayed as hyperlink.

• subscriptionIdentifier

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Identifier of Evolveum subscription contract that applies to this deployment.

• systemName

  Flags: RAM,runtime

  Multiplicity: [0,1]

  Custom name for midPoint identity management system.