You can define an encrypted managed data source using the Eclipse extension points and the Lotus® Expeditor Toolkit.
Follow these steps to define a managed data source:
- Using the Lotus Expeditor Toolkit, define a managed data source by specifying the com.ibm.rcp.database.core.datasource extension point.
- Use the existing Apache Derby database provider and specify the following connection encryption attributes:
Table 1. Apache Derby Encryption attributes
|encryptionProvider||Specifies the provider for data encryption. If none is specified, the provider of the JRE is used.|
|encryptionAlgorithm||Specifies the algorithm for data encryption. If none is specified, the default value is DES/CBC/NoPadding. |
|encryptionKeyLength||Specifies the key length used to encrypt the Derby database. The Derby database implementation uses a default key length based on the selected encryption algorithm. The default key lengths used by Derby are 56 bit for DES, 168 bit for TripleDES and Desede, and 128 bit for other algorithms. Key lengths longer than the default can require the installation of unrestricted policy files for the Java runtime that permit longer keys to be generated.|
|dataEncryption||Specifies data encryption on disk for a new database.|
Refer to the Apache Derby documentation for more information about specifying encryption attributes.
- Define a valid JNDI binding to match the JNDI name of the data source using the com.ibm.pvc.jndi.provider.java.binding extension point.
The encrypted managed data source is defined.
Parent topic: Defining managed data sources: XPD622