Configuration issues to consider when using RMI-based OpenEdge command like utilities in an IPv6 environment

Configuration issues to consider when using RMI-based OpenEdge command like utilities in an IPv6 environment
Configuration issues to be aware of when using IPv6 addresses with the AdminServer
Are there any configuration issues I need to be aware of when configuring OpenEdge to make use of IPv6 addresses
IPv6 considerations associated with the AdminServer
Java environment considerations when using IPv6 addresses
How to configure AdminServer to use IPv6

Some network topologies, especially where the Java system default values are “-Djava.net.preferIPv4Stack=true” and “-Djava.net.preferIPv6Addresses=false”, will cause RMI-based OpenEdge command line utilities to fail.  The failure occurs when attempting to resolve an IPv6 hostname/IP address causing the connection to the remote process to fail.
  
Example: nsman –name NS1 –query –host ::1  

Starting with OpenEdge 10.1C, this issue can be avoided by Configuring for iPv6 explicitly:

1.  Edit the $DLC/properties/JavaTools.properties and locate the “[Common]” section.
Within this section, modify the “jvmargs"” property by appending:
“-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true”.
The completed property should appear as follows:
“jvmargs=-ms8m –mx25m -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true”.

2.  Start the AdminServer with the ipver switch set to ipv6.  
These changes will result in the RMI-based OpenEdge command line utilities being able to successfully resolve IPv6 hostnames/IP addresses.

Progress Articles: 

How to set which IPv4 or IPv6 stack is used for a specific service in OpenEdge?   
OEE/OEM Fathom WebServer fails to start