AEM with LDAP integration

Follow the Below Blog URL:

http://www.conexiogroup.com/synchronize-ldap-users-groups-aem/

How to migrate Closed User Groups from AEM 6.2 to AEM 6.3 using Migration Tool

Statement - Closed User Groups Migration Tool for migration existing CUG content.Assuming if you have upgraded the AEM older version to AEM 6.3 version.
Environment - AEM 6.3 GA

Solution :

• Go to the Felix console URL: http://localhost:4502/system/console/cug-migration
• Enter the root path you want to check CUGs for, and press the Perform dry run button. 
• This will scan for CUGs elligible for conversion in the selected location.
• After you have reviewed the results, press the Perform migration button to migrate to the new implementation.
  
• That's it!

Note : 

For AEM installations upgraded to AEM 6.3 it is important to ensure that only one CUG implementation is enabled. 

The combination of the new and the old, deprecated CUG support is not tested and is likely to cause undesired behavior:

• collisions in the Sling Authenticator with regards to authentication requirements
• denied read access when the ACL setup associated with old CUG collides with a new CUG policy.
• If the migration is performed on a publish instance, please enable the Adobe Granite Closed User Group before performing a migration.

Reference : https://helpx.adobe.com/content/dam/help/en/experience-manager/6-3/sites/administering/using/security-custom-user-groups/_jcr_content/main-pars/download-section/download-1/cug-mapping.pdf

How to run Disk Benchmark in AEM through Felix console

Statement - This is a simple disk performance benchmark. It test how fast Java can read from and write to the hard disk. The test uses temporary files, which are deleted at the end of the run.
Environment - AEM 6.3 GA

Solution :

• Go to the Felix console URL: http://localhost:4502/system/console/diskbenchmark
• Click on Startbenchmark and wait for 5 mins.
• click on stop to see the no of operations performed per second for the 4KB block size.
• This is a simple disk performance benchmark. It test how fast Java can read from and write to the hard disk. The test uses temporary files, which are deleted at the end of the run.
  Directory: 
  

  The test will pause this long until running the next test.

  File size (MB): 
  

  The test creates one temporary file with the given size.

  Run (ms): 
  

  The test will run at full speed for this many milliseconds.

  Delay (ms): 
  

  After running a test, there is a pause of this many milliseconds.

  File mode (r/rw/rw+): 
  

  The file access mode. Use rw for read+write, r for read-only, rw+ for read+write+fsync.

  StartBenchmark
  
   to collect the read and write date per second for the block size 256B, 512 Byte
  
  Below is the Windows 8.1 system read and write date for 4KB size block

  Operation Type	Operations Per Second for Block Sizes
  	256 B	512 B	1 KB	2 KB	4 KB	8 KB	16 KB
  write	142	358	478	656	3995	3879	3739
  read	40501	56407	58739	41575	52049	39297	28160
  write	3740	3801	3899	4036	3875	3914	3773
  read	54694	59831	58509	56579	53480	42740	29545

• That's it!