Objects to include in replication - Assure_Secure_File_Transfer_ - Assure_Elevated_Authority_Manager_(EAM) - Assure_Secure_File_Transfer_PGP - Assure_Encryption - Assure_Secure_File_Transfer - Required_for_All_Modules - Assure_Monitoring_and_Reporting_(AMR) - Assure_Security_Multi-Factor_Authentication_(MFA) - Assure_DB2_Data_Monitor_(DB2MON) - Assure_System_Access_Manager_(SAM) - Assure_Secure_File_Transfer_with_PGP - 7.0

Assure Security Installation (Manual) Guide
Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure Security > Assure Elevated Authority Manager (EAM)
Assure Security > Assure Encryption
Assure Security > Assure Secure File Transfer
Assure Security > Required for All Modules
Assure Security > Assure Monitoring and Reporting (AMR)
Assure Security > Assure Security Multi-Factor Authentication (MFA)
Assure Security > Assure DB2 Data Monitor (DB2MON)
Assure Security > Assure System Access Manager (SAM)
Assure Security > Assure Secure File Transfer with PGP
Version
7.0
Language
English
Content type
Installation (Manual) Guide
Product name
Assure Security
Title
Assure Security Installation (Manual) Guide
Copyright
2023
First publish date
1999
Last updated
2025-01-05
Published on
2025-01-05T12:58:06.220000
The following objects in the Assure Security product library must be configured for replication by the high availability product:
  • The product user profile and its attributes. The profile has the same name as the product library.
  • The product authorization list and its associated entries. The AUTL object has the same name as the product library and is located in library QSYS.
  • If you have any of your own libraries that contain information used by Assure Security, such as a library that contains preparation files for Assure Monitoring and Reporting, configure these files for replication.
  • The product IFS directory. The directory name may vary depending on whether you upgraded to or installed a new installation of Assure Security. Do not replicate the symbolic link to the product IFS directory. For the directory path, see Installed software components and locations.
  • The following product library (*LIB) objects in QSYS, as well as the contents of these libraries with the exceptions noted below:
    • The product library
    • The secondary library
    • The product-library_0
    Note: When your availability solution is Assure QuickEDD HA, objects in these libraries that begin with Q* must not be omitted from replication.
  • The object QUSRSYS/QUSEXRGOBJ *EXITRG must be configured for replication. If you are using Assure QuickEDD HA, this is configured when Exit Points (*EXITRG) is selected in parameters for “Manage specific objects”. If you are using Assure MIMIX, this is configured when a selection rule (data group object entry) is configured that specifies this object. Assure QuickEDD HA defers replication until the time that a switch occurs. MIMIX replicates the object in real time.
    Note: The object QUSRSYS/QUSEXRGOBJ *EXITRG contains all exit points registered on a system. If this object is replicated and the exit points used on the source are not initially the same as those used on the target, when replication occurs, you will lose any target-only exit points. This will affect all exit points, not only those managed by Assure Security.
    It is recommended that you carefully consider whether exit points should be replicated. Replicating exit points can lead to issues with applications and recovery from those issues may become problematic. For example, applications such as BRMS may use exit points that are not used by Assure Security but may be affected if the exit points are replicated.