Disabling encryption of files
You can enable and disable encryption as often as necessary. If you disable the encryption configuration, the files will be written in clear text; however, the system will continue to transparently read any existing encrypted files. The encryption for files written on each peer and
Development Studio is enabled or disabled independently.
To disable encryption on
Development Studio
- In a text editor, open the AO_Home/Studio/DevelopmentStudio.properties file.
Add the following line:
com.bmc.security.encryption.DISABLED=trueIf this parameter is not set, or if it is set to false, encryption is enabled for
Development Studio.
If this parameter is set to true, the files on the peer are decrypted whenDevelopment Studio is restarted.
The following figure shows an example of a DevelopmentStudio.properties file where encryption is disabled.
Disabling encryption in DevelopmentStudio.properties filedevstudio.workspace=C:\\Documents and Settings\\user1\\DevStudio
realops.home.dir=C:\\Program Files\\BMC Software\\AO\\Studio
JXTA_HOME=C:\\Program Files\\BMC Software\\AO\\Studio\\server\\.jxta
messages.home.dir=C:\\Program Files\\BMC Software\\AO\\Studio\\messages
default.context=baocdp
com.bmc.security.encryption.DISABLED=true
To disable encryption on a peer
- In a text editor, open the AO_Home/tomcat/conf/context.xml file.
Add the following line:
<Environment name="com.bmc.security.encryption.DISABLED" override="true" type="java.lang.String" value="true"/>If this parameter is not set, or if it is set to false, encryption is enabled for the peer.
If this parameter is set to true, the files on the peer are decrypted when theservice is restarted.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*