Open topic with navigation
All ACI communication actions sent to IDOL components in an OEM-licensed environment must be ACI encrypted. IDOL components access the
licensekey.dat file to determine the encryption keys required to decode encrypted action.
Note: You must not use the
CommsEncryptionTEAKeys (deprecated) configuration parameters to encrypt ACI communications because the key would be publicly available.
To set up licensing in an OEM environment
Encrypt ACI communications between IDOL components and the front-end application by making the appropriate API call in your application and passing in the OEM encryption keys that were provided to you. For example:
In the C API, you could make the following call:
char* szKeys = "MjR8CJCUGcb4RbRdNDKbK9RXX3pEswAiZ"; aciInitEncryption(TRUE, "TEA", szKeys);
where the value of
szKeys is the encryption key provided with the license.
In the Java API, you could make the following call:
TEAEncryptionDetails encryptionDetails = new TEAEncryptionDetails(); encryptionDetails.setEncryptionKeys(MjR8CJCUGcb4RbRdNDKbK9RXX3pEswAiZ); encryptionDetails.setEncrypting(true); aciConnection.setEncryptionDetails(encrytionDetails);
licensekey.dat file with your application by copying it to the working directory of each IDOL component. The IDOL components will then read the license from the
licensekey.dat instead of the
[License] section of the component’s configuration file.
licensekey.dat file is generated by HPE and provided to you along with your license.
Truein the ACI action you run.