Set model properties - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

You use the Model Properties page to view information about the status and history of, and to set a threshold value for, commits of the model.

To set defaults for the entire model:

1. Right-click the Enterprise Data Movement Model root, then select Properties in the menu that displays.

   The Model Properties dialog displays.

   The Model Properties dialog contains the following fields:

   Field	Description
   Model Tab
   Version number	Displays the version number of the model.
   Status	Displays the commit status of the model. See Model Commit Status. For information on the commit options, see Commit the Model.
   Last full commit	Displays the date and time of the model’s last full commit. For information on the commit options, see Commit the Model.
   Last incremental commit	Displays the date and time of the model’s last incremental commit. For information on the commit options, see Commit the Model.
   Allow commit of models containing	If a model can be committed with: Warnings and incomplete definitions Warnings only Neither warnings nor incomplete definitions For information on the commit options, see Commit the Model.
   Model Security	Enables you to optionally define one or more model user IDs, passwords, and roles to be stored with a particular model. Enable model security–If selected, at least one Admin ID is required. After IDs are set up, the user must enter an Admin ID to open the model. Enable XML hashcode–If selected, message digests (short representations of streams of bytes) are used to secure both the XML files (network and dataflow) in their entirety. Secure Logging–To enable this option you must select Enable model security. Connect CDC may include detailed replicated transaction data in messages displayed in Listener logs, Kernel logs, the Console logs and MonCon logs, when errors occur or the SQLDEBUG option is turned on. This data may include names, addresses, social security numbers and other information that could be regarded as sensitive. You can now secure your data from unauthorized access by preventing sensitive data from appearing in logs or on the terminal screen. By default, the Secure Logging option is not enabled. The Secure Logging option will only allow the SQLDEBUG option to be turned on when Secure Logging has been deactivated in the kernel by a user with administrator privileges. For detailed information refer to Secure Logging. For model security details, refer to: Set up Model Security Table 14.
   XML/Encryption Tab
   Via FTP to machine	If selected, enables you to access the XML files globally by specifying the URL of the http: web server machine to which Connect CDC sends the XML metabase files. This machine must be accessible by a web server to support global access to the XML files by URL. This is the name (or IP address) by which the computer is known on your TCP/IP network. To keep XML files locally at one host, set this on the Host Properties page (see Create Hosts ).
   Path	Enter the global location of the XML files. Specify the operating system path to the directory on an http: web server machine to which the Connect CDC sends the XML metabase files via FTP. Use the appropriate format: Windows–\path UNIX–/path IBM i–/path where path is the absolute path to the metabase directory.
   Logon ID	Enter a valid operating system login ID for the machine on which the http: web server is installed. This user account requires write access to the directory you specify in Path, above. For Windows, in addition to the Change permission for files in the directory you specify in Path, this user account requires Log on locally user rights. Specify anonymous if the FTP server is set up for anonymous access.
   Password	Enter the password for the Login ID.
   URL to access	Enter the URL by which Connect CDC components access the global XML metabase files. This URL must resolve to the same location as the FTP Path, above. For example, while your metabase XML files might be sent to the /incoming/www/data/omnimeta directory on the ourftpserver machine, the files might be accessed by the URL http://ourwebserver/omnimeta, which maps on the web server to //ourftpserver/incoming/www/data/omnimeta.
   Default host access method (unless overridden)	Specifies the default access method: Standard (unsecure) sockets Encryption—both authentication and encryption For information on Encryption, see Implement Model Authentication and Encryption.
   General Tab
   	This information is available on every Properties dialog. Use it for any notes specific to this object. You may need to reference the ID value during troubleshooting. You review the entries on each tab of the Properties dialog, accepting or modifying displayed defaults, or specifying values for items that have no default.

   Note: To access more information about an individual Properties tab item (text box, button, or drop-down list), either left-single-click it (hold the mouse button to avoid selecting the item) or press F1.

2. Click OK to record your specifications and close the dialog.

To set the commit threshold

1. From the Allow commit of models containing options, select the level of validation messages that should be accepted when this model is being committed:

   • Warnings and incomplete definitions indicates that the commit should continue even if warnings and incomplete definition validation messages occur.

   • Warnings only indicates that the commit should continue even if warning validation messages occur. If incomplete definition validation messages occur, the commit stops.

   • Neither warnings nor incomplete definitions indicates that the commit stops if warnings or incomplete validation messages occur.

2. Click OK.