windows error 2 occur while loading the java vm" during ADT (adaptr development tool installation)

I  face this below error during adapter development tool installation on window 7 OS.

Error:- windows error 2 occur while loading the java vm" during ADT (adaptr development tool installation



I had fixed this issue and below are the solution steps.

Steps: - 1. install the installer from the below command because that will specify the java jre path

ADT5124_ITIM51_TDI71x.exe LAX_VM "C:\Program Files (x86)\Java\jre1.8.0_101\bin\java.exe

CTGIMD803E The protocol portion of the Host URL field value is not valid

ISIM Service profile connection is not established with Manage resource SQL Database and I got this error CTGIMD803E  The protocol portion of the Host URL field value is not valid from ISIM service profile.

My Environment details:-


Connecting ISIM with SQL Server 2012, so i completed these steps:

1 ) SQL Server adapter installed on window-7. already SQL Server 2012 present on the machine.

2 ) SQL Profile is imported successfully. in ISIM

So I found the solution for this that I was using wrong URL field like (URL: jdbc:sqlserver://machineIP:1433;databaseName=dbname) in service profile which was wrong.
so i used correct URL like ( https://targetapplicationIP:45580).
after that I able to connect with target SQL application and my issue resolved.

where : 45580 --  it is sql adapter port

Tunning Tivoli Identity Manager

Tunning Tivoli Identity Manager

1 Configuring LDAP connection pooling in enRole.properties
2 Configuring list controls in ui.properties
3 Configuring Configuring report data synchronization in adhocreporting.properties file
4 Configuring the commitFrequency property in adhocreporting.properties file
5 Configuring Java™ heap size while running the report data
6 synchronization utility on OS.
7 Configuring report batch sizes in adhocreporting.properties file
8 Configuring email notifications from ITIM GUI
9 Disabling the recycle bin
10 Emptying the recycle bin
11 Configuring reconciliation threads
12 Configuring the maximum duration of a reconciliation
13 Configuring paged searches in enRole.properties file
14 disabling server-side sorting in enRole.properties file
15 Configuring the ACI cache in in enRole.properties file
16 Controlling the size of the database
 



   

Tunning RMI Dispatcher

Tunning RMI Dispatcher:-

1 ) Configuring timeouts for large reconciliations
Steps
a. Stop the RMI Dispatcher.
b. In itdi_home/itim_listener.properties, update the following option:
SearchALUnusedTimeout=searchal_timeout
c. Restart the RMI Dispatcher for this change to take effect.


2 ) Configuring assembly line caching

Steps
a. Stop the RMI Dispatcher.
b. In itdi_home/itim_listener.properties, update or add the following option:
   ALCacheSize=num_cached_ALs
c. Restart the RMI Dispatcher for this change to take effect.


3 ) Configuring the number of concurrently running assembly lines
Steps
a. Stop the RMI Dispatcher.
b. In itdi_home/itim_listener.properties, update the following configuration options:
GlobalRunALCount=max_running_ALs
MaxWaitingALcount=max_waiting_ALs
c. Restart the RMI Dispatcher for this change to take effect.


Happy sharing...!!

Maintenance Activity for TIVOLI IDENTITY MANAGER

 Maintenance Activity for TIVOLI IDENTITY MANAGER:-

Perform regular maintenance to maintain optimal performance for IBM Tivoli Identity Manager environment.

• Clean out the recycle bin.
• Update database statistics.
• Clean out the IBM Tivoli Identity Manager database.
• Evaluate and apply fixes.
• Access the latest version of the tuning guide.
• Take regular backups.

exception in thread "main" java.lang.ExceptionLnlnitalizerError: A security class cannot be found in this jvm because of the following reason: sun.security.x509.CertAndKeyGen

exception in thread "main" java.lang.ExceptionLnlnitalizerError: A security class cannot be found in this jvm because of the following reason: sun.security.x509.CertAndKeyGen




Solution:-
OUD installation setup throws this error because of java jre was not supportable with the product So I use supportable jre. issue got fixed.