Symantec IGA

 View Only
  • 1.  increase memory allocation for Provisioning Server

    Posted Jun 18, 2021 06:55 PM
    Hi Team,
    We are using IdentitySuite 14.4 VAPP.  For Non-Product/Production env, we know that to increase memory allocation for IP, IM & IG we can modify the jvm-args.conf file. But for Userstore, Provisioning Server & CentralLogs, how do we increase the memory allocation manaully ?



    regards,
    William


  • 2.  RE: increase memory allocation for Provisioning Server

    Broadcom Employee
    Posted Jun 19, 2021 01:26 AM
    1. To modify the memory parameters for JCS, edit the file /opt/CA/IdentityManager/ConnectorServer/data/jvm_options.conf

    2. There is no need to set the memory consumption for Provisioning Server. By default, it will use upto 4 GB. It can not use memory beyond 4GB.


  • 3.  RE: increase memory allocation for Provisioning Server

    Posted Jun 21, 2021 09:05 PM

    William,

    As Shesh mentions, the IMPS service is 32bit VC++ code that will not use above 4 GB of RAM.   

    You can validate this with top or other tools for the slapd service.      top -u imps

    However, since you mentioned using the vApp, the underlying CA Directory IMPD DATA DSAs size (disk/ram) can be increased as needed.

    This is why you will see the memory requirements for the IMPS server being higher than 4 GB RAM.

    There are four (4) IMPD DATA DSA + 1 IMPD ROUTER DSA that are side-loaded with the IMPS service.

    If you start out with 2 GB size for each DATA DSA, you need to reserve 1.5 x memory for the four, e.g.    4 x 2 GB  x 1.5 (allow for re-indexing) = 12 GB RAM.    If you add the 4 GB for the IMPS service, then you would want to order / reserve a 16 GB or 25 GB RAM system for the dedicated IMPS Server.

    If you also side-load the primary userstore DATA DSA, you will need to increase RAM requirements based off its size.

    To avoid SPOF (single point of failure) you will need minimal of two of these servers.   


    To view the data size of the DATA DSA, su to the dsa service ID on the vApp, change to the config/servers folder, and review the DXI files for the size value.  If you switch to the data folder for CA Directory DATA DSA, you should see that same file size exist for the *.db  and *.zdb files. 

    A note to help review:

    https://anapartner.com/2020/08/21/directory-backup-and-restore-dar-scenarios/

    Cheers,

    Alan



    ------------------------------
    Alan Baugher
    ANA Technology Partner (anapartner.com)
    ------------------------------