Siebel Security Guide > Physical Deployment and Auditing > Securing Siebel Reports Server >

Securing Communications Between the AOM and Actuate iServer

During report generation, Actuate iServer establishes a separate session to the AOM to obtain data for report generation. This communication can be encrypted by setting the desired encryption type (RSA or MSCRYTPO) for the Actuate Server Connect String parameter in the configuration file for the AOM. The following example specifies RSA as the encryption type to use:

Actuate Server Connect String = siebel.TCPIP.RSA.none://SiebelServerHost:SCBPort/EnterpriseServerName/XXXObjMgr_language

For details on setting this parameter, see the postinstallation tasks described in the Siebel Installation Guide for the operating system you are using.

Using the Siebel Strong Encryption Pack with Siebel Reports Server

If you choose to encrypt communications between the AOM and the Actuate iServer, and if you have installed the Siebel Strong Encryption Pack (SSEP), you must perform the steps in the following procedure to enable the SSEP for the Siebel Reports Server. For information on the Siebel Strong Encryption Pack, see About the Siebel Strong Encryption Pack.

To use the Siebel Strong Encryption Pack with Siebel Reports Server

1. After installing the SSEP, copy one of the following SSEP library files from the Siebel Server directory to the Reports Server installation directory (for example, on Windows the default directory is sba_thirdparty_800\Actuate8\Server):
   • sslcrsaxxx.dll file (Windows)
   • libsslcrsaxxx.so file (UNIX)
2. Restart all Actuate process services.

   For information on starting Actuate services, see Siebel Reports Administration Guide.

3. Resynchronize accounts for Siebel report users.

   For information on this task, see Siebel Reports Administration Guide.