Managing properties

You can use database to store properties, and then manage the properties in the System Management Administrator.

Server and database properties

To manage properties in database, use the System Management Administrator tool. To identify the properties that are supported by the database, in the runtime/yfs.properties file, see the DATABASE_SUPPORT:Y property. For more information, see Managing properties in the database.

Note: Properties added to your database through System Management Administrator takes precedence over the properties that are defined in the customer_overrides.properties file. Therefore, use the appropriate methodology for defining the properties.

Ignore the tables in the ydkprefs.xml file

During migration, you must ignore the following tables:
  • YFS_ZIP_CODE_LOCATION
  • PLT_ACTIVITY_CONFIG
  • PLT_ACTIVITY_CONFIG_METADATA
  • PLT_API_TEMPLATE
  • PLT_APPLICATION_VERSION
  • PLT_AUTH_ANSWER
  • PLT_AUTH_QUESTION
  • PLT_CALLOUT
  • PLT_CALLOUT_CLASS_LOADER
  • PLT_CALLOUT_IMPL
  • PLT_COLONY_MAP
  • PLT_DBVERIFY_SCRIPT
  • PLT_DB_COLONY
  • PLT_DB_COLONY_POOL
  • PLT_DB_POOL
  • PLT_DISPATCH
  • PLT_EOF_STATUS
  • PLT_FILE_ATTACHMENT
  • PLT_FILE_ATTACHMENT_H
  • PLT_FILE_DATA
  • PLT_FILE_DATA_H
  • PLT_INDEX_CONFIG
  • PLT_PAGED_DATA
  • PLT_PROCESS_STATUS
  • PLT_PROPERTY_METADATA
  • PLT_PWD_HIST
  • PLT_PWD_POLICY
  • PLT_PWD_REQ
  • PLT_PWD_RULE_CFG
  • PLT_PWD_RULE_DEFN
  • PLT_QUALIFIED_TAG
  • PLT_QUALIFIED_TAG_TYPE
  • PLT_QUALIFIED_TAG_VER_COMPTBLT
  • PLT_SDF_FILE_STATUS
  • PLT_SERVER_ACTIVITY_CONFIG
  • PLT_UNIQUE_ID
  • PLT_USER_LOGIN_FAIL
  • PLT_USER_UI_STATE
  • PWD_HISTORY
  • PWD_POLICY
  • SI_VERSION