Migrated from NovaTec Jira. Original ticket: INSPECTIT-1187
This ticket is the first step towards the application concepts defined in the visions documents in Confluence.
What should be addressed:
An application is a logical entity.
An application has a unique name
Each invocation sequence belongs to exactly one application
If no application definition is available, the invocation belongs to a default application
an association between the invocation and the application is helt
the association to an application can be defined by a set of rules
For this ticket we are only supporting a rule based on the URL that the request was executed on. So the user can define a pattern that should match the URL to define which invocations belong to the application
The application definition should be stored in XML format
A graphical configuration must be available in the CMR
Changing an existing application name and definition does NOT have to affect already mapped invocation sequences
Have the application in the invocation sequence view, no more visualizations for now
Documentation:Business Context Configuration