Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Application Server

Upload run-time configuration changes

  • Last UpdatedJul 25, 2024
  • 2 minute read

You can upload run-time configuration changes to the Galaxy database. This lets you set new default attribute values, based on observations of run-time behavior.

Note: A node cannot upload run-time changes to the Galaxy if the version of Application Server it is running is older than the version running on the GR node.

Certain attribute values can be set in the configuration environment, but they can also be changed at run time. As a result, the values of these attributes can differ between the run-time and configuration environments. These types of attribute writeability are:

  • Calculated

  • Calculated Retentive

  • Object Writeable

  • User Writeable

For example, you create an object with a User Writeable attribute called myInteger and specify an initial value of 30 in the Object Editor.

Then you deploy the object. At run time, you write a new value to myInteger of 31. If you redeploy this object, the original value of 30 overwrites any value assigned during run time. To avoid losing changes made during run time, upload changes before redeploying an object.

Objects whose configuration are successfully uploaded have a new version number and a change log entry for the upload operation. The run-time object’s version number also has a new version number. That version number matches the version in the configuration database.

Upload changes to auto assigned objects and object wizard instances

In most cases, uploading run-time changes sets new default values for the affected objects in the GR. However, if your galaxy uses auto assigned I/O references, or if the attribute values you changed were in objects derived from object wizards, run-time configuration changes are not saved as new default configuration values. The run-time changes are saved instead as overrides to the default attribute values in the GR.

  • Run-time configuration changes to auto assigned I/O references are uploaded as overrides to the original I/O assignments. I/O references will continue to be auto assigned and the run-time changes are retained when the objects are redeployed. See Upload runtime configuration changes for auto-assigned objects for additional information.

  • If you upload a run-time change to an instance derived from an object wizard, the change does not overwrite the configured object wizard value. Instead, the change is saved as an override to the default value configured for the attribute in the object wizard.

To upload run-time changes to the galaxy

  1. Select one or more objects in the Model view or Deployment view. For example, you could select an entire hierarchy from AppEngine down.

  2. On the Home ribbon, in the Runtime area, select Upload changes.

  3. The runtime attributes of the selected objects are copied over those in the Galaxy database, with the following exceptions:

    • Auto Assigned Objects: The new run-time values are set as overrides to the default values in the Galaxy database.

    • Objects derived from Object Wizards: The new run-time values are set as overrides to the default values in the Galaxy database.

TitleResults for “How to create a CRG?”Also Available in