A profile represents a collection of transaction pathway models used in a specific environment. The profile defines the set of hosts that implement the business process restricting monitoring and deployment of configurations defined within the profile to only those hosts.
Additionally, the profile defines the list of users who have the capability to create and define the transaction pathway as well as deploy configurations for monitoring.
You might have several profiles for development, quality assurance and production depending on how your environments and transaction pathways are organized.
Each profile can define users or groups of users that have permission to:
Create or edit the transaction pathways within the profile, import transaction pathways using a command line tool into the profile or move transaction pathways from one profile to this profile.
Deploy the configuration of a transaction pathway into the IT infrastructure.
You can promote parts of a profile to another profile. This is useful for working on a transaction pathway in a non-critical space and then copying it to your working environment. Once message formats, activity implementations, or transaction pathways are promoted from one profile to another, they are no longer related to the original profile.