During installation of the App Visibility proxy, you provide the location of the KeyStore file that handles SSL-encrypted beacons and injected requests. The values that you provide during installation are saved in the apm-proxy.properties file. If you did not have the KeyStore file during installation, or if you now need to provide a new one, you must use one of the following procedures to update the apm-proxy.properties file:
Tip
To collect end-user data, use a signed certificate; that is, a certificate approved by a recognized certificate authority.
If your application pages are only HTTP, you can change the protocol.
installationDirectory\apm-proxy\bin\
import-keystore.bat
installationDirectory/apm-proxy/
bin/
import-keystore.sh
JKS
or PCKS12
) installationDirectory\apm-proxy\bin\passwordEncrypt.bat newPassword
installationDirectory/apm-proxy/
bin/passwordEncrypt.sh newPassword
installationDirectory
is the full path of the installation directory newPassword
is the clear-text password
A message is displayed during the encryption process.
When encryption is complete, the encrypted password is displayed.
installationDirectory\apm-proxy\bin\
import-keystore.bat keyStoreType keyStoreFullPath keyStoreEncryptedPassword
installationDirectory/apm-proxy/
bin/
import-keystore.sh keyStoreType keyStoreFullPath keyStoreEncryptedPassword
keyStoreType
is PKCS12 or JKS (Do not enter lower-case characters.) keyStoreFullPath
is the full path and file name of the KeyStore file keyStoreEncryptedPassword
is the encrypted password to the KeyStore file
Oracle: KeyStores and TrustStores
Continue App Visibility configuration by performing the following procedures:
After you configure the App Visibility system, performing the following procedures:
Performing the App Visibility server installation
Changing App Visibility proxy settings