Application profile reference

The application profile is used to change application parameters without requiring code changes. It defines application behavior within IBM® Spectrum Symphony. It provides the information that the system needs to run services and manage IBM Spectrum Symphony workload or MapReduce jobs.

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. Note that MapReduce applications are by default registered to the MapReduceConsumer tree.

In IBM Spectrum Symphony Developer Edition, you can find sample 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/7.3.2/samples/Templates directory.

The application profile includes the following sections (note that the order of the sections is important; changing the order causes errors):
  1. Profile (for application profile identification)
  2. Consumer (for application and resources assigned to the consumer associated with the application)
  3. MDS (for multidimensional scheduling configuration of your resource plan and slot definitions)
  4. Docker (for Docker containers)
  5. ResourceGroupConfigs (for a series of resource groups defined under resourceGroupName in the Consumer section)
  6. MultiSSM (for redirecting workload across multiple applications)
  7. SOAM (for system behavior)
  8. MapReduce (for MapReduce applications only)
  9. SessionTypes (for groups of configuration settings for session attributes)
  10. Service (for service attributes)
Attention: To configure paging paths in the application profile, you can use the $EGO_SHARED_TOP and $SOAM_HOME environment variables defined for your system.

Application profile fragments

With dynamic application updates, you can add a new service by registering a profile fragment (that is, a 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.
Note: You can add, update, or remove session types or Service sections or both by modifying an existing application in the cluster management console using Dynamic Configuration Update. In this case, you are not required to create fragments manually.

IBM Spectrum Symphony provides profile fragment templates for your reference. You can find templates in the $SOAM_HOME/7.3.2/samples/Templates directory under your IBM Spectrum Symphony Developer Edition installation. Use these for reference only, not as a method for updating application parameters. Use the cluster management console to update your application profile instead.

When you update a Service section or session type, the session manager only terminates workload that uses the updated services and session types.