Change encrypted communications - 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

If it is necessary to change the encryption setting, do the following:

  1. Open the non-encrypted model.

  2.  From the context menu of the model, go to Model Properties and click the XML/Encryption tab.

  3. Change the connection encrypted properties to encrypted. (Do not stop or start any Connect CDC Listeners.)

  4. Commit these changes.

  5. Execute a Model Update.

  6. Once the Model Update has parsed and loaded the new XML (with the new connection properties changes), stop the existing non-encrypted Connect CDC Listeners.

  7. Start the encrypted Connect CDC Listeners.

  8. Re-commit and update the model.

Now the model will be able to complete a successful encrypted handshake with the encrypted-started Connect CDC Listeners. The transition is complete from non-encrypted to encrypted.

  • To transition from encrypted to non-encrypted, reverse the order of these steps.

If you change the connection from non-encrypted to v using a different order, you may be unable to update the model and collect information.

Whether you use Connect CDC MonCon or Connece CDC Console, you would receive a message like the following:

No information will be available.