The management console is a web-based application that manages all the capabilities of Apinizer. The user can log in with their user name and password through this panel and can easily manage Apinizer related operations.
If you have completed the previous steps successfully, the Apinizer Management console should be available at the address
#Apinizer TLS settings export enableHttps=false # secureProtocols is the names of the protocols to support when communicating with clients. This should be a list of any combination of the following: # SSLv2,SSLv3,TLSv1,TLSv1.1,TLSv1.2,all # Each token in the list can be prefixed with a plus sign ("+") or a minus sign ("-"). A plus sign adds the protocol, a minus sign removes it form the current list. The list is built starting from an empty list. # The token all is an alias for TLSv1+TLSv1.1+TLSv1.2. # If more than one protocol is specified for an OpenSSL based secure connector it will always support SSLv2Hello. If a single protocol is specified it will not support SSLv2Hello. # Note that SSLv2 and SSLv3 are inherently unsafe. export secureProtocols=TLSv1+TLSv1.1+TLSv1.2 # Name of the file that contains the server certificate. The format is PEM-encoded. Relative paths will be resolved against $CATALINA_BASE. export certificateFile=/opt/apinizerManager/certificate/apinizer.cer # Name of the file that contains the server private key. The format is PEM-encoded. The default value is the value of certificateFile and in this case both certificate and private key have to be in this file (NOT RECOMMENDED). Relative paths will be resolved against $CATALINA_BASE. export certificateKeyFile=/opt/apinizerManager/certificate/apinizer.keystore export certificateKeyPassword=password