Examples of activation state file contents

The following examples show how the activation state files contents is structured:

Example 1:

Successful Configuration Activation - no feedback message - Module: Login Application

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<medusaConfigActivationState version="1">
	<state>SUCCESS</state>
	<applicationId>loginapp</applicationId>
	<message/>
</medusaConfigActivationState>

Example 2

Configuration Activation in progress - no feedback message - Module: Admintool

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<medusaConfigActivationState version="1">
	<state>IN_PROGRESS</state>
	<applicationId>adminapp</applicationId>
	<message/>
</medusaConfigActivationState>

Example 3

Configuration Activation failed - with feedback message - Module: Service Container App

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<medusaConfigActivationState version="1">
	<state>FAILED</state>
	<applicationId>servicecontainerapp</applicationId>
	<message>Configuration "servicecontainerapp" in configuration file "/home/airlock/iam/instances/test/medusa-configuration.xml" is not valid for context "[DEFAULT]". See log file for details.</message>

</medusaConfigActivationState> 

Notes on Compatiblity:

  • The activation state files are valid XML documents.
  • The order of the tags within the medusaConfigActivationState tag is undefined and may change without notice.
  • Additional (new) tags may be added to the medusaConfigActivationState tag without notice.
  • If the version attribute has the value "1", the tags state, applicationId, and message are guaranteed to be present and used as in the above examples.
  • Incomplete or only partially written activation state files have to be ignored.