Important Notes When Upgrading from DSS 5 - DSS 6 | Data Source Solutions Documentation
Documentation: Important Notes When Upgrading from DSS 5 - DSS 6 | Data Source Solutions Documentation
Important Notes When Upgrading from DSS 5
This section describes the underlying changes introduced in DSS 6 when compared to the DSS 5.x versions. The fundamental change is that DSSGUI in DSS 5 has been migrated to the web application that comes with a completely new user interface and REST API functionality. Major changes were also introduced to the process architecture, the structure of catalog tables (renamed as repository tables), CLI commands, actions, jobs, import and export system, etc.
- DSS version 6.x is not compatible with the versions 5.x and 4.x. So, ensure that DSS version 6.x is installed on the Hub machine and Agent machine.
- Only DSS Agent installation is supported on the Unix platforms (aix_6.1-powerpc-64bit, solaris_10-sparcv9-64bit).
For the instructions to upgrade from DSS 5 to DSS 6, see section Upgrading from DSS 5.
Functionality Removed in DSS 6
- Cloud-licensed agents (cloud-licensed hubs still exist).
- DSS hub on Unix (non-Linux).
- DSS for MacOS platform.
- Documentation set bundled inside our product.
Architecture
| DSS 5 | DSS 6 |
|---|---|
| DSS hub database contains a set of catalog tables. DSS hub runs on a hub machine and transmits data using DSS's remote protocol. | DSS Hub Server has a single repository database that contains repository tables. The repository database can contain multiple hubs (multi-tenancy). Hub is an abstract collection of channels, locations, tables, and actions, etc. DSS Hub Server runs on a hub machine and transmits data using the HTTP or HTTPS protocol. DSS Hub Server has a set of users that can be authenticated using the following methods:
|
Methods to communicate with DSS 5 (interfaces):
|
Methods to communicate with DSS 6 (interfaces):
|
| DSS GUI runs the Scheduler. | DSS Hub Server runs the Scheduler. |
| DSS remote protocol is used to connect between a hub machine and the DSS Agent on a remote source/target machine, and between the DSS GUI and the hub machine. | DSS Agent protocol is used to connect to an DSS Agent on a remote source/target machine. |
The following image shows the differences (highlighted in blue) between the process architectures in DSS 5 and DSS 6.
Licensing
In DSS5, applying an DSS license is a separate step performed after DSS installation. After receiving the license file by email, a user has to save into the DSS_Home/lib/ directory on a hub machine.
In DSS 6, applying a license file is part of the Hub System setup workflow (UI and CLI).
Installing DSS 6
In DSS5, there is only one workflow for installing DSS 6 as a hub or as remote agent.
In DSS 6, the redesigned installer for Windows splits the installation process into separate workflows:
-
Neither: DSS can only be used for command-line control of a remote hub machine. For more information, see Remote CLI.
DSS Agent
In DSS 6, the agent configuration workflow is now a part of a unified system setup workflow that allows to easily configure a secure, encrypted and properly authenticated connection from a hub to an agent. This is implemented by introducing agent setup modes and agent authentication methods. For more information, see section DSS Agent.
Agent Authentication
The following agent authentication methods are available in DSS 6:
-
Limiting access from hubs with only specific hub certificates, so that the agent only accept connection from a particular hub machine (this allows anonymous connections).
-
Agent user authentication (using agent user credentials)
-
Combination of the above two methods
For more information about agent authentication, see section Agent Connection Modes.
Agent Setup Mode
Agent setup mode is used for configuring the DSS Agent service. There are two types of agent setup mode:
-
Time-based setup mode
-
Token-based setup mode
For more information, see section Agent Setup Mode.
Catalog Tables
The DSS 5 'catalog tables' located inside a hub database are renamed as 'repository tables' located inside a repository database for DSS 6.
- The DSS 5 tables DSS_CONFIG_ACTION, DSS_JOB_RESOURCE*, and DSS_JOB_PARAM were removed in DSS 6.
- In DSS 6, because a repository database can include multiple hubs (multi-tenancy), a column called hub_name was added as a key column to almost all repository tables for distinguishing between jobs, database objects (channels, locations, tables, etc.) and files relating to a particular hub.
- All changes to the repository tables are tracked in the DSS_COUNTER table.
- New configuration tables are added, containing information about users (DSS_USER), user properties (DSS_USER_PROPERTY), user hub properties (DSS_USER_HUB_PROPERTY), repository properties (DSS_REPOS_PROPERTY), hub properties (DSS_HUB_PROPERTY), and location properties (DSS_LOCATION_PROPERTY).
- Each definition table (DSS_CHANNEL, DSS_TABLE, DSS_LOC_GROUP, DSS_LOCATION, DSS_COLUMN, DSS_ACTION, DSS_LOC_GROUP_MEMBER, DSS_LOCATION_PROPERTY) has two time-dimension columns insert_tstamp and delete_tstamp to better manage changes to the repository tables. This time dimensional model allows a user to make interactive changes to a channel definition without immediately introducing them into replication.
DSS 5 allows you to make changes to the definition tables directly using SQL statements, e.g. a user can insert a column into the DSS_COLUMN table. DSS 6 does not support direct modification of the definition tables using SQL statements. Instead, a user has three options for making such changes: through the User Interface, Command Line Interface (CLI), or REST API.
See section Repository Tables.
The following diagram shows the changes that have been introduced in the repository tables. The tables and columns highlighted in brown are those migrated from DSS 5. The ones highlighted in blue are new tables and columns added in DSS 6.
DSS_CONFIG Reorganization
The following image shows the difference between the DSS_CONFIG directory structures in DSS 5 and DSS 6. Because of multi-tenancy architecture introduced in DSS 6, the DSS_CONFIG directory is now partitioned into hub sub-directories. The benefit of the new DSS_CONFIG structure is that it matches the REST API object naming structure.
DSS_HOME Reorganization
The following image shows the difference between the DSS_HOME directory structures in DSS 5 and DSS 6. One significant change is that the agent directory has been renamed to plugin in DSS 6. The plugin scripts are stored in the plugin_examples directory, and to activate them, you need to explicitly move them to the DSS_CONFIG/plugin/ directory.
User Interface
The “thick” graphical user interface (DSSGUI) has been replaced with a "thin" web-based user interface. The DSS 6 web-based user interface is designed to be visually appealing and intuitive providing a better user experience.
One advantage of the new user interface is that it assists both novice and expert users. In the DSS 5 GUI, both the essential features and advanced functionality appeared all at once, whereas in DSS 6, they were separated into two layers. A layer of essential functionality is initially visible to a user so that a novice user who has no experience in DSS product could quickly set up a replication channel ready for production. At the same time, for the expert users who have solid knowledge in DSS, the advanced functionality is smartly hidden below the essential features and can be expanded if needed.
Another feature that makes DSS 6 user interface easy to interact with is that certain input fields that are only required once a user has chosen a specific option or function remain hidden until the user has selected that option, they then expand underneath. This helps users to focus on the things they need to fill over things they might not need.
The DSS 6 user interface is very informative, it provides short descriptions of basic DSS concepts and options and explanatory workflow that aids a user in setting up a replication channel, creating a location, and understanding the DSS system as a whole.
See section User Interface.
Command Line Interface
In DSS 5, the command line requires user credentials to connect to a hub database (e.g. <b>Dssinit -h</b> <b>sqlserver -u</b> <em>myuser/pwd hubdb mychn</em>). In DSS 6, options <b>-h</b> (database class) and <b>-u</b> (database user and password) were removed from all the commands that used to require them.
The DSS 6 command line interface includes two types of command lines:
- Direct command line - authentication to the DSS system is done using the credentials of an dss user logged in to a hub machine). In this case, only the hub name is needed to run a command (e.g. dssactivate myhub mychn).
- Remote command line - authentication to the DSS system is done via the DSS's REST interface. In this case, a user needs to use command **dsslogin **
<b>-R</b>to log in, the authentication token is stored for a certain period of time in ~/.config/dss. Option<b>-R</b>must be used to run commands (except dsshubserver) though the remote command line.
New option <b>--help</b> along with an DSS command displays a short description of all options available for a specific command.
For more information, see section Command Line Interface.
Commands
The following commands were either removed or replaced with new commands:
| DSS 5 Commands | Status in DSS 6 |
|---|---|
| dsscatalogcreate | Replaced with dssreposconfig option -c |
| dsscatalogdrop | Replaced with dssreposconfig option -d |
| dsscatalogexport | Replaced with dssdefinitionexport |
| dsscatalogimport | Replaced with dssdefinitionimport |
| dsscryptdb | Removed |
| dssfailover | Removed |
| dssgui | Removed |
| dssinit | Renamed to dssactivate |
| dsslivewallet | Replaced with location property Oracle_TDE_Wallet_Password |
| dsslogrelease | Removed |
| dssmaint | Split into commands dssalertconfig and (internal) dssmaintjob. See below for more details. |
| dssremotelistener | Renamed to dssagentlistener |
| dssproxy | Currently unavailable, may be implemented in future release. |
| dssstatistics | Removed |
| dssswitchtable | Currently unavailable, may be implemented in future release. |
| dsstestlistener | Renamed to dssagenttest |
| dssvalidpw | Removed. This authentication plugin for LDAP is not available in DSS 6. It was determined that most/all Linux users would integrate their LDAP in their Linux systems for regular login. So in DSS 6 they could use PAM authenitcation for LDAP authentication. |
| dss_boot | Unix reboot steps show script lines instead |
Dssmaint
The DSS 5 command Dssmaint has been split into two parts in DSS 6:
dssalert
Runs outside DSS Hub Server (by dssalertmanager)
Set up inside the user interface or via the command line interface (dssalertconfig)
Alert messages have hypertext links
Latency SLAs defined inside a channel
- action Scheduling with parameter LatencySLA
dssmaintjob
- Automatically rotates log files
The following are DSS 5 Dssmaint options that have been converted or removed in DSS 6.
| DSS 5 Dssmaint options | Status in DSS 6 |
|---|---|
| -email_to=addr1[;addr2] | Moved to alert property Email_Recipients |
| -email_from=addr | Moved to alert property Email_From_Address |
| -smtp_server=server | Moved to alert property Email_SMTP_Server |
| -smtp_port=port | Moved to alert property Email_SMTP_Port |
| -smtp_starttls | Moved to alert property Email_SMTP_Starttls |
| -smtp_user=user | Moved to alert property Email_SMTP_User |
| -smtp_pass=pass | Moved to alert property Email_SMTP_Password |
| -error_limit=N | Moved to alertproperty Message_Error_Limit |
| -slack_channel=chn | Moved to alert property Slack_Channel |
| -slack_webhook_url=url | Moved to alert property Slack_Webhook_URL |
| -snmp_version=vers | Moved to alert property SNMP_Version |
| -snmp_heartbeat | Moved to alert property SNMP_Heartbeat |
| -snmp_hostname=host | Moved to alert property SNMP_Hostname |
| -snmp_port=port | Moved to alert property SNMP_Port |
| -snmp_community=str | Moved to alert property SNMP_Community |
| -sns_destination | Moved to alert property SNS_Destination |
| -sns_access_key | Moved to alert property SNS_Access_Key_Id |
| -sns_secret_key | Moved to alert property SNS_Secret_Access_Key |
| -scan_ignore=patt | Moved to alert property Ignore_Patterns |
| -scan_channel=chn | Moved to alert property Specific_Channels |
| -scan_location=loc | Moved to alert property Specific_Locations |
| -email_repeat_suppression | Moved to alert property Repeat_Interval |
| -check_logfile_growth | Removed |
| -disable | Available from the Alerts dialog in User Interface and command dssalertconfig -D |
| -task_group=group | Removed |
| -test_scheduler | Removed. Managed by command dssalertmanager. |
| -clear_past_errors | Available from the Alerts dialog in User Interface and command dssalertconfig -C |
| -scan_dss_out | Removed. Managed by command dssalertmanager. |
| -optnm_email_test | Available from the Alerts dialog in User Interface and command dssalertconfig -t |
| -optnm_slack_test | Available from the Alerts dialog in User Interface and command dssalertconfig -t |
| -optnm_sns_test | Available from the Alerts dialog in User Interface and command dssalertconfig -t |
| -optnm_snmp_test | Available from the Alerts dialog in User Interface and command dssalertconfig -t |
| -send_slack_only_when_errors_or_warnings | Moved to alert property Ignore_Warnings=FALSE |
| -email_only_when_errors_or_warnings | Moved to alert property Ignore_Warning=FALSE |
| -sns_only_when_errors_or_warnings | Moved to alert property Ignore_Warnings=FALSE |
| -send_slack_only_when_errors | Moved to alert property Ignore_Warnings=TRUE |
| -sns_only_when_errors | Moved to alert property Ignore_Warnings=TRUE |
| -email_only_when_errors | Moved to alert property Ignore_Warnings=TRUE |
| -sns_repeat_suppression | Moved to alert property Repeat_Interval |
| -slack_repeat_suppression | Moved to alert property Repeat_Interval |
| -email_repeat_suppression | Moved to alert property Repeat_Interval |
| -latency_limit=dur | Removed |
| -latency_channel=chn | Removed |
| -latency_location=loc | Removed |
| -output=file | Removed |
| -version | Removed |
| -start | Removed |
| -stop | Removed |
| -archive_files=patt | Removed |
| -archive_keep_days=N | Removed |
| -archive_compress | Removed |
| -archive_concat | Removed |
| -archive_dir | Removed |
REST API Interface
DSS REST API is a completely new interface implemented in DSS 6 providing about 200 Rest API end-points grouped into about 20 'interfaces'. Most REST end-points accept and return JSON requests and responses.
An important purpose of the REST API is that it provides a security layer, as it is responsible for user authorization. Each REST interface is assigned an access level, e.g. you need a ReadExec access level on a hub to post a compare event.
Location Group Membership
In DSS 5, a location can be a member of multiple location groups in a channel.
DSS 6 imposes the following restrictions on the locations included in a channel:
- a location must be a member of a location group
- a location can only be a member of one location group.
Actions
In DSS 6, backslash has been removed before the parameter name of an action. For example,
- DSS 5: /IgnoreCondition in action Capture
- DSS 6: IgnoreCondition in action Capture
The DSS 5 action LocationProperties and its parameters, certain parameters of actions Capture and Integrate, as well as some environmental variables were converted to Location Properties in DSS 6. The complete list of changes are listed in the following sections below.
Action Scope
DSS 5 allows defining actions for a specific scope, e.g. actions can be defined for both a location and a location group, or a location group and a channel. In total DSS 5 allowed 24 combinations of action scopes. In DSS 6, this behavior is changed.
In DSS 6, the following action scopes are supported:
- Channel scope: all channels (*) or a specific channel
- Location scope: all locations (*) or a location group or a specific location
- Table scope: all tables or a table group or a specific table. Requires a specific channel to be selected in the channel scope.
Actions Capture and Integrate defined on a specific location will be effective in a channel only when the location is a member of the channel's location group.
Actions and Parameters
The section lists DSS 5 actions and action parameters that were either converted to the location properties, renamed, removed, or replaced with new parameters in DSS 6.
| DSS 5 Actions and Parameters | Status in DSS 6 | |
|---|---|---|
| Capture | /ArchiveLogFormat | Moved to location property Archive_Log_Format |
| Capture | /ArchiveLogOnly | Moved to location property Capture_Method with value ARCHIVE_ONLY |
| Capture | /ArchiveLogPath | Moved to location property Archive_Log_Path |
| Capture | /CheckpointFrequency | Moved to location property Capture_Checkpoint_Frequency |
| Capture | /CheckpointRetention | Moved to location property Capture_Checkpoint_Retention |
| Capture | /CheckpointStorage | Moved to location property Capture_Checkpoint_Storage |
| Capture | /KeyOnlyCaptureTable | Moved to location property Key_Only_Trigger_Tables |
| Capture | /LogJournal | Split into two separate location properties: |
| Capture | /LogJournalSysSeq | Moved to location property DB2i_Log_Journal_SysSeq |
| Capture | /LogReadMethod | Moved to location property Capture_Method with values DIRECT, SQL, or LOGMINER |
| Capture | /LogTruncate | Moved to location property Log_Truncater |
| Capture | /QuickToggle | Moved to location property Trigger_Quick_Toggle |
| Capture | /SupplementalLogging | Moved to location property Supplemental_Logging |
| Capture | /ToggleFrequency | Moved to location property Trigger_Toggle_Frequency |
| Capture | /TriggerBased | Moved to location property Capture_Method with value DB_TRIGGER |
| Capture | /XLogDirectory | Moved to location property PostgreSQL_XLog |
| ColumnProperties | /Identity | Removed |
| FileFormat | /AvroCompression | Replaced with new parameter BlockCompress |
| Integrate | /Burst | Moved inside new parameter Method having two values:
|
| Integrate | /MessageBundling | Moved to location property Kafka_Message_Bundling |
| Integrate | /MessageBundlingThreshold | Moved to location property Kafka_Message_Bundling_Threshold |
| Integrate | /MessageCompress | Moved to location property Kafka_Message_Compress |
| LocationProperties | Removed. Action LocationProperties is not available in DSS 6, its parameters are either removed or converted to location properties. | |
| LocationProperties | /BulkAPI | Moved to location property Salesforce_Bulk_API |
| LocationProperties | /CaseSensitiveNames | Moved to location property Case_Sensitive_Names |
| LocationProperties | /CloudLicense | Moved to location property Agent_Has_Cloud_License |
| LocationProperties | /IntermediateDirectory | Moved to location property Intermediate_Directory |
| LocationProperties | /Order | Removed |
| LocationProperties | /Proxy | Split into following separate location properties: |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_SSE |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_SSE_KMS |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_Master_Symmetric_Key |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_KMS_Customer_Master_Key_Id |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_KMS_Region |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_KMS_Access_Key_Id |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_KMS_Secret_Access_Key |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_KMS_IAM_Role |
| LocationProperties | /S3Encryption | Moved to location property S3_Encryption_Materials_Description |
| LocationProperties | /SerialMode | Moved to location property Salesforce_Serial_Mode |
| LocationProperties | /SslLocalCertificateKeyPair | Split into two hub properties: |
| LocationProperties | /SslRemoteCertificate | Moved to location property Agent_Server_Public_Certificate |
| LocationProperties | /StagingDirectoryDss | Moved to location property Staging_Directory |
| LocationProperties | /StagingDirectoryDss | The scheme moves to location property File_Scheme, and the credentials to appropriate credential properties. |
| LocationProperties | /StagingDirectoryDb | Moved to location property Staging_Directory_Database |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property AWS_Access_Key_Id |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property AWS_Secret_Access_Key |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property AWS_IAM_Role |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property S3_Encryption_Master_Symmetric_Key |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property Azure_Account |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property Azure_Shared_Secret_Key |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property GS_HMAC_Access_Key_Id |
| LocationProperties | /StagingDirectoryCredentials | Moved to location property GS_HMAC_Secret_Access_Key |
| LocationProperties | /StateDirectory | Split into two separate location properties: |
| LocationProperties | /ThrottleKbytes | Removed |
| LocationProperties | /ThrottleMillisecs | Removed |
| Scheduling | /StatsHistory | Moved to hub property Statistics_Retention_Policy |
| Scheduling | /RefreshStartTimes | Moved to Refresh as an option. For DSS UI, see Scheduling Options (Schedule Repeatedly at) option in Refreshing Data dialog. For CLI, see -Estr (a crono string) option in the dssrefresh command. |
| Scheduling | /CompareStartTimes | Moved to Compare as an option. For DSS UI, see Scheduling Options (Schedule Repeatedly at) option in Comparing Data dialog. For CLI, see -Estr (a crono string) option in the dsscompare command. |
| TableProperties | /DuplicateRows | Replaced with new parameter NoDuplicateRows |
Data Types Changes
The change in data type for the following expression must be considered when upgrading from DSS5 to DSS6.
dss_integ_tstamp
In DSS 5, the data type for dss_integ_tstamp is inconsistent across different location types. However, in DSS 6, this inconsistency has been resolved by standardizing the data type to TIMESTAMP(3) WITH TIME ZONE or the closest equivalent if the database does not support this type.
For example:
- In BigQuery, the data type in DSS 5 is DATETIME, but in DSS 6, it is TIMESTAMP.
- In Oracle, the data type in DSS 5 is TIMESTAMP(6) WITH TIME ZONE, but in DSS 6, it is TIMESTAMP(3) WITH TIME ZONE.
Since the data type of dss_integ_tstamp differs between DSS 5 and DSS 6, the action definition ColumnProperties /IntegrateExpression= dss_integ_tstamp may no longer function in DSS 6. In such cases, you may need to perform casting operations or change the data type in the target column of DSS 6. For example, if the target column type in BigQuery is DATETIME and you are unable to change the column type to TIMESTAMP on the target side, you would need to use a cast operation similar to CAST({dss_integ_tstamp} AS DATETIME) instead of simply using {dss_integ_tstamp} in /IntegrateExpression in DSS 6.
dss_integ_seq and dss_tx_seq
In DSS 5, the data type for dss_integ_seq and dss_tx_seq is a 36 character string. However, in DSS 6, these two integrate expressions in the ColumnProperties action now have a length of 45. While upgrading from DSS 5 to DSS 6, the dssconvert5to6 script updates the Length parameter to 45 for this action. Additionally, the script displays a warning indicating that the corresponding columns in the target locations must be updated. You can either update these columns manually in the underlying database or run Refresh in the DSS 6 environment that updates only the schema, not the data.
For example, to update only the schema using dssrefresh:
dssrefresh -r <em>srclocation</em> -cbopr <em>hub channel</em>
Jobs
DSS job is a process that performs a certain task, such as activating replication, capturing/integrating changes, refreshing data, comparing data, etc.
| DSS 5 | DSS 6 |
|---|---|
There are three options for compare and refresh jobs:
|
Activate, Refresh, and Compare operations are performed by special event-based jobs. The Scheduler always runs the activate, refresh, and compare jobs. The jobs are controlled by the state of the events in the DSS's event system. This applies to user interface, command line interface, and REST API. For example, when you perform the Compare operation, a compare event is created in the DSS's event system, then the mychn-cmp-src-tgt compare job is created in the Scheduler, which runs the compare job. If the mychn-cmp-src-tgt job is restarted from the SUSPEND state, it will resume from where it was interrupted rather than starting from the beginning. When you start the compare operation and there is an existing compare event with the same job name in the PENDING or RUNNING state, then the existing event is canceled (FAILED) by the new compare event. Job Chaining The job chaining option (the Activate Replication dialog in the UI, commands dssactivate-J and dssrefresh -J) allows a user to manage the sequence of events to be started after replication activation, such as refresh, capture, and integrate. |
Import and Export
DSS 6 import and export system offers a lot more flexibility and powerful features than that of DSS 5. For example, in DSS 6, you can download an action and reload it into a different channel, you can export a file containing properties to connect to a remote agent and share it with your colleagues, you can export changes made to a channel definition into a file and apply those changes to a different hub.
The following table reflects major changes to the DSS export/import system.
| DSS 5 | DSS 6 |
|---|---|
| Commands Dsscatalogimport and Dsscatalogexport | Commands dssdefinitionimport and dssdefinitionexport |
| Export and import to/from XML file | Export and import to/from JSON file |
Export/import of:
|
Export/ import of:
|
| Not available | Command dssdefinitionimport loads objects exported from the user interface |
| Not available | Apply Definition Change events:
|
| Not available | Use dssdefinitionimport command to make arbitrary changes to a channel, such as delete or delete a location, rename a channel, add or delete actions, and much more. For example, see section Examples on the dssdefinitionimport page. |
Environment Variables
The following DSS 5 environment variables were converted to the location properties in DSS 6.
| DSS 5 Environment Variables | Status in DSS 6 |
|---|---|
| $DSS_ASM_CONNECT | Split into three location properties: |
| $DSS_ASM_HOME | Moved to location property Oracle_ASM_Home |
Properties
Properties is a new concept in DSS 6 that specifies the characteristics/attributes of the DSS components:
- Agent Properties
- Alert Properties
- Hub Properties
- Hub Server Properties
- Location Properties
- Repository Properties
- User Properties
The following table shows the place where the properties for each DSS component are stored and the DSS commands for managing these properties.
| Object | Property storage | DSS Commands |
|---|---|---|
| Agent | $DSS_CONFIG/etc/dssagentconfig.conf | dssagentconfig |
| Alerts | $DSS_CONFIG/hubs/{hub}/alerts/{alert}.conf | dssalertconfig |
| Hub Server | $DSS_CONFIG/etc/dsshubserver.conf | dsshubserverconfig |
| Hubs | Repository table DSS_HUB_PROPERTY | dsshubconfig |
| License | Repository property Licenses. Repository properties are stored in the repository table DSS_REPOS_PROPERTY. |
dsslicense |
| Locations | Repository table DSS_LOCATION_PROPERTY | dssdefinitionexport |
| Repository | Repository table DSS_REPOS_PROPERTY | dssreposconfig |
| Users | Repository tables DSS_USER_PROPERTY and DSS_USER_HUB_PROPERTY | dssuserconfig |
Snapshots
DSS 6 allows you to create a snapshot of an DSS hub and save it to a zip file that stores all the data related to the hub, i.e. the hub snapshot metadata, information about channels, locations, location groups, tables, columns, actions and information from the DSS_CONFIG directory (log files, enroll files, capture state files, catalog cache files, etc.). The snapshot can be used to move the hub to a different repository, for reporting purposes, or for sharing with other users.
Smart Links
User interface dialogs contain links pointing to the relevant documentation pages, as well as links that can navigate you between different user interface pages.
The Log Viewer dialog displays smart links that can navigate you to the relevant UI pages. For example, clicking the name of a compare or refresh event will open the appropriate Event Details page.