The application profile is used to change application parameters without requiring code changes. The application profile defines application behavior within Symphony. It provides the information Symphony needs to run services and manage workload. Each application name in the profile must be unique in the cluster and associated with one consumer. At any time, there can be only one enabled application per consumer.
You can find example application profiles in the samples directories. You can also refer to the application profile templates to create your own application profiles. You can find templates in the $SOAM_HOME/4.1/samples/Templates directory.
With dynamic application updates, you can add a new service by registering a profile fragment (part of an application profile) that contains either new session types in the SessionTypes section, new Service sections, or both. When you register a profile fragment that adds a session type or Service section, running workload continues to run. The session director updates the session manager with the new version of the application profile.
You can add, update, or remove session types or Service sections or both by modifying an existing application in PMC using Dynamic Configuration Update. In this case, you are not required to create fragments manually. See the PMC Help or Platform Application Development Guide, available from the Platform Knowledge Center, for more details.
You can refer to the profile fragment templates to create your own profiles. You can find templates in the $SOAM_HOME/4.1/samples/Templates directory. However, this is not a recommended way for updating application parameters.
When you update a Service section or session type, the session manager only terminates workload that uses the updated service(s) and/or session type(s).