About OSM Model Variables

In OSM, you can set model variables in both composite and component cartridges.

Note:

Ensure that you define any model variables that are common to both a composite cartridge and its component cartridges so that they have the same value. If you define the same cartridge management variable with different values on both a composite cartridge and its component cartridge, the value that will be used in OSM depends on how they are deployed. If you deploy them as a single composite cartridge, the variable is derived from the composite cartridge, but if you then deploy the component cartridge alone, the variable defined on the component cartridge are used instead. This can cause unexpected changes to cartridge behavior.

Design Studio for OSM provides the following default model variables:

Default Variable	Use
DEFAULT_AUTOMATION_USER	Use this model variable to represent the security principal whose credentials are used to run the automation plug-ins. By default, the value of this variable is oms-automation.
DEFAULT_REQUEST_QUEUE	Use this model variable to identify the JMS destination to which automation plug-ins will send messages by default. By default, this variable has no value.
DEFAULT_RESPONSE_QUEUE	Use this model variable to identify the JMS destination from which automation plug-ins will receive messages by default. By default, the value of this variable is mslv/oms/oms1/internal/jms/events.
DEFAULT_MESSAGE_PROPERTY_SELECTOR	Use this model variable to identify the messages for which automation plug-ins listen. By default, this variable has no value.
ACTIVATION_ENVIRONMENT_ID	Use this model variable to represent the Oracle Communications ASAP environment ID to which service action requests are sent. By default, the value of this variable is ENV1.