The DCA-CCS connection allows communication between the DCA and CCS for agent reporting and tracking. The connection establishes an Agent Reporting and Management (ARM) service that:
Makes information on Web content shared during DCA sessions available for CCS reports.
Allows the automatic cleanup of DCA sessions when their associated CCS sessions are terminated.
Note that in the event of a failed connection, the DCA will continue to function otherwise correctly. However, any session integration made possible by the ARM will be unavailable.
Creating the DCA-CCS connection consists of the following steps:
Step 1. Define the DCA connection on CCS
Step 2. Transfer the authentication/configuration files
Step 3. Configure the connection for SSL (optional)
Step 4. Enable the connection on the DCA
Step 5. Test the connection
The first step in creating the DCA-CCS connection is to define the connection on Collaboration Server. To define the connection on Collaboration Server:
Open the CCS Administration desktop.
From the Administration desktop menu, select Server Setup > Connections > Create. The Connect Wizard screen opens.
Select Dynamic Content Adapter. Click Next.
In the DCA Connection Name field, specify a name for the connection. The name must:
Include alphanumeric characters and underscores only.
Be 30 characters or less.
Be unique (from DCA Connection Names you have created for other CCS servers, if any).
In Description, if desired, enter a description for the connection to be used in the Collaboration Administration desktop.
In DCA Host Name, enter the DCA server's unique host name (for example, myDCA.mydomain.com) or its static IP address.
Registry Port on DCA specifies the port the DCA uses to register a connection instance with CCS. You MUST use the default, 1099.
If the DCA will communicate with CCS through a firewall, you must enable a one-way connection from the DCA to CCS on your firewall for this port.
In CCS Password, create a password the DCA will use to authenticate itself to Collaboration.
In Verify CCS Password, re-enter the password.
In Registry Port on CCS, specify the port CCS should use to register a connection instance with the DCA. Cisco recommends that you use the default, 1099.
If you previously defined the CCS registry port for a different server connection (for example, Cisco Media Blender), CCS will automatically use that same port for your DCA connection.
In Connection Port on CCS, specify the port CCS should use to connect to and communicate with the DCA. If left blank, CCS will search for and use the first available port.
If the DCA will communicate with CCS through a firewall, you must specify a specific port, and then enable that port on your firewall.
In CCS Password, create a password the DCA will use to authenticate itself to Collaboration . If left blank, no password will be used.
In Verify CCS Password, re-enter the password.
Check the Disable Automatic Connect check box. This ensures that Collaboration Server operates in RMI "server" mode, while the other applications (i.e., the DCA) operate in RMI "client" mode.
Click Finish.
Restart the Web server on CCS.
When you define the CCS-DCA connection in the CCS Admin Tool, two files used to authenticate the connection are automatically created on your CCS server. These files must be copied to your DCA server.
On your Collaboration server, navigate to: <CCSrootdirectory>\Servlet\Properties\dca\<connectionname>\.
In the <connectioname> directory, locate these two files: <connectionname>.properties and messageadapter.properties.
Transfer the files to your DCA server, and place them here: DCA\WebApp\WEB-INF\Cisco\properties.
Note: The target directory on your DCA server will already contain a file named messageadapter.properties. Overwrite the existing file with the new one.
Optionally, you may want to configure the CCS-DCA connection for SSL. This ensures that data sent from the DCA to CCS are encrypted. Configuring the connection for SSL requires first generating keystore and truststore files for your connection using the JDK Keytool utility that ships with the DCA.
Using the JDK Keytool utility, generate a keystore and truststore for your DCA-CCS connection. When you generate the keystore, you will also create a certificate that you will export to the truststore.
Additional information on generating DCA keystores and truststores is included in the CCS Administration Desktop online Help. Additional information on using the Keytool is available at: http://java.sun.com/j2se/1.4/docs/tooldocs/windows/keytool.html. Steps for creating a sample keystore and truststore are available at: http://java.sun.com/j2se/1.4/docs/guide/security/jsse/JSSERefGuide.html#RMISample
Although you can create a keystore and truststore on any server, because the DCA 2.01 uses an earlier version of the JDK (1.3.1) than CCS, it's recommended that you generate your keystore and truststore on the DCA.
After generating the files, transfer the keystore file to any location on your Collaboration Server. Move the truststore file to a desired location on your DCA server.
On your Collaboration Server, in the <connectionname>.properties file, uncomment the lines pertaining to SSL and keystore. Provide the values as requested. Do not uncomment the lines pertaining to truststore.
After editing, the SSL section of your <connectionname>.properties file on Collaboration Server should look something like this:
# Uncomment this property to enable SSL
DCA_Conn_1.rmi.SocketType = SSL
# Location of key store (absolute path)
DCA_Conn_1.rmi.KeyStore = c:\cisco_cs\mykeystore.keystore
# Type of key store
DCA_Conn_1.rmi.KeyStoreType = JKS
# Key store password
DCA_Conn_1.rmi.KeyStorePassword = mykeystore_password
# Key password
# DCA_Conn_1.rmi.KeyPassword=
# Location of trust store (absolute path)
# DCA_Conn_1.rmi.TrustStore=
# Type of trust store
# DCA_Conn_1.rmi.TrustStoreType=JKS
# Trust store password
# DCA_Conn_1.rmi.TrustStorePassword=>
Restart the Web server on CCS.
On your DCA server, in the <connectionname>.properties file, uncomment the lines pertaining to SSL, key password, and truststore. Provide the values as requested. Do not uncomment the lines pertaining to keystore.
After editing, the SSL section of the <connectionname>.properties file on the DCA should look something like this:
# Uncomment this property to enable SSL
DCA_Conn_1.rmi.SocketType = SSL
# Location of key store (absolute path)
# DCA_Conn_1.rmi.KeyStore=
# Type of key store
# DCA_Conn_1.rmi.KeyStoreType=JKS
# Key store password
# DCA_Conn_1.rmi.KeyStorePassword=
# Key password
DCA_Conn_1.rmi.KeyPassword = mykey_password
# Location of trust store (absolute path)
DCA_Conn_1.rmi.TrustStore = c:\dca\mytruststore.truststore
# Type of trust store
DCA_Conn_1.rmi.TrustStoreType = JKS
# Trust store password
DCA_Conn_1.rmi.TrustStorePassword = mytruststore_password
After creating the DCA-CCS connection and copying the authentication files to the DCA, you must enable the connection on the DCA server.
To enable the DCA-CCS connection:
In the DCA Admin Tool, select Configuration > ProxyProperties.
Set the enableDCACCSConnection property to True.
Click Submit.
After creating the DCA-CCS connection, you may want to test to verify that it is active.
To test the DCA-Collaboration connection:
Open the Collaboration Administration desktop.
From the Administration desktop menu, select Server Setup > Connections > Monitor. The Connection Monitor screen opens, displaying the status of all Collaboration connections.
See Also
For related information, see:
About DCA-Collaboration Server Integration