Fix for issue 1351.
Using the CLI the user can specify the JMX port using the -j or --jmxPort option.
The usage has been updated to reflect this.
| | |
| | | entries.\n\ |
| | | -p {port} or --ldapPort {port}\n Specifies the port on which the \ |
| | | Directory Server should listen for LDAP\n communication.\n\ |
| | | -j {jmxPort} or --jmxPort {jmxPort}\n Specifies the port on which the \ |
| | | Directory Server should listen for JMX\n communication.\n\ |
| | | -S or --skipPortCheck\n Skip the check to determine whether the \ |
| | | specified LDAP port is usable.\n\ |
| | | -D {rootDN} or --rootUserDN {rootDN}\n Specifies the DN for the initial \ |
| | |
| | | argParser.addArgument(ldapPort); |
| | | |
| | | jmxPort = new IntegerArgument("jmxport", 'j', "jmxPort", false, false, |
| | | true, "{port}", |
| | | true, "{jmxPort}", |
| | | SetupUtils.getDefaultJMXPort(), null, true, |
| | | 1, true, 65535, |
| | | MSGID_INSTALLDS_DESCRIPTION_JMXPORT); |