Applications Manager version 8 is at End of Support on March 31, 2018.
A listing of products & component lifecyle can be found here: Component Support Lifecycle.
Please note, you will need to sign in with your support account to view this information.


Kristopher ThomasKristopher Thomas SupportBellevue, WATeam Automic Posts: 60 Journeyman ✭✭✭
The AM connection to Oracle(JDBC) depends on the Java version used(which by default chooses encryption) and the default encryption levels specified. You can override the default encryption levels specified by Java in the awenv.ini file to force one or more specific encryption levels. Of course setting it to one specific encryption may cause issues connecting to other databases where common encryption is not in place.

I was able to change the default net.encryption_types_client variable by defining it in the $AW_HOME/site/awenv.ini. You will need to add the following under the [default] section of the file.


*This is an example of setting AES256. If you wish to include other encryption types they can be added to the variable as well. Please ensure your master is on a version of java which supports the higher encryption (1.8).
Once in place you will need to stop and restart the Application Manager back end processes for the change to take effect.

You can confirm the setting by looking in the RmiServer log with debug enabled. The line will look as followed.
08:50:42.914 main: .AwEnvOptions: net.encryption_types_client = AES256
08:50:42.915 main: .AwEnvOptions: using default: net.crypto_checksum_types_client = MD5
08:50:42.915 main: .AwEnvOptions: net.crypto_checksum_types_client = MD5
08:50:43.177 main: .AxConnection: inUse (sync) null AM9 false
08:50:43.178 main: .AxConnection: inUse (sync) done null AM9

Please note that Applications Manager version 9.1 allows for stronger encryption if using Java 8 or above. I would advise updating to java 1.8 along with implementing the encryption changes to the awenv.ini as noted above.

Sign In or Register to comment.