Set up model security - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

AWS Mainframe Modernization - Data Replication for IBM i

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
AWS Mainframe Modernization > AWS Mainframe Modernization Service
Version
Latest
Language
English
Product name
AWS Mainframe Modernization
Title
AWS Mainframe Modernization - Data Replication for IBM i
Copyright
2024
First publish date
2003
Last updated
2024-02-01
Published on
2024-02-01T23:02:31.099696

You may define one or more model user IDs, passwords, and roles to be stored with a particular model. If a model is secured, then only an Admin user can add, delete, or modify user ids, passwords and roles.

Additional roles may be defined if more security is necessary.

To set up the user IDs, passwords, and roles, select Properties from the context menu of the Data Movement Model. If the Enable model security check box is not checked, the grid is disabled.

If the Enable model security check box is checked, then at least one Admin ID is required.

Note: Ensure that you remember the assigned password as it will require a call to Precisely Support to recover it

The Enable XML hashcode check box is used to request that message digests (short representations of streams of bytes) be used to secure both the XML files (network and dataflow) in their entirety. This is optional.

If Secure Logging is selected (enabled) then messages in the Listener logs, Kernel logs, the Console logs and MonCon logs sensitive data. To enable this option you must select Enable model security. For detailed information refer to Secure logging.

If Secure Logging is disabled in the model then all users connected to that kernel could potentially view any source or target table customer data contained in messages sent to the log or the clients. The default value for Secure Logging is disabled. Refer to

Connect CDC MonCon and Connece CDC Console can implement the use of any model user IDs provided.

 Director actions by user type details the Director model security role actions by user type:

  • Admin    

  • User    

  • Modeler

  • Monitor

Table 1. Director Actions by User Type

Director actions by user type

Admin

User

Modeler

Monitor

Install Source-Only Metabase    

Yes

No

No

No

Install Target-Only Metabase

Yes

No

No

No

Remove Metabase

Yes

No

No

No

Prepare User Database

Yes

Yes

Yes

No

Update XML Files

Yes

Yes

No

No

Update Configuration Files

Yes

No

No

No

Commit

Yes

No

No

No

Load/Save the secured Model

Yes

Yes

Yes

No

Add/Remove/Modify Host

Yes

Yes

Yes

No

Add/Remove/Modify Server

Yes

Yes

Yes

No

Add/Remove/Modify Change Selector

Yes

Yes

Yes

No

Add/Remove/Modify Distributions

Yes

Yes

Yes

No

Add/Remove/Modify Requests

Yes

Yes

Yes

No

Add/Remove/Modify Mappings

Yes

Yes

Yes

No

Add/Remove/Modify Data Enhancement Methods

Yes

Yes

Yes

No

Refresh Tables

Yes

Yes

Yes

No

Generate DDL

Yes

Yes

Yes

No

Catalog synchronization report

Yes

Yes

Yes

No

Add or Remove users from model security

Yes

No

No

No

Add or Remove Admin from model security

Yes

No

No

No

View all users in model security

Yes

Yes

Yes

No

Export/Import RSL

Yes

No

No b  

No

SQL Window

Yes

Yes

No

No

Add Email Alerts

Yes

Yes

Yes

No

Validate

Yes

Yes

Yes

No