Problem

The release notes of SecureTransport state that it is possible for C:D protocol to be utilized. How do we go about doing so?

As Connect:Direct is a proprietary protocol, you will need the CDJAI.jar file from an operational Connect:Direct server to be installed on the ST server side, following these steps:

1. Stop ST

2. Copy the CDJAI.jar file into ST's lib/jars directory

In addition, you will need a SecureTransport license that includes the Connect:Direct feature. Please contact your account representative in order to receive more information or to get an evaluation (or permanent) license with C:D enabled.

Once both of these are done, there are several further steps to follow:

1. Start (the embedded database, if you are using it, and) the ST Admin component.

2. In the Admin UI, go to Operations > Server Configuration, and set the ConnectDirectTransferAgent.transfersFolder parameter to a directory (of your choosing) that ST will use for C:D transfers. (Note that this must be a full path, relative to / on Unix or a volume root directory on Windows; it is not relative to the SecureTransport installation directory.)

3. Set the ConnectDirectTransferAgent.commandTimeout parameter to an appropriate value for your environment.

4. Create the directory specified in step 2, and make sure you have full permissions on it.

5. Start ST.

6. (for versions below 5.3.6) Enable the ConnectDirectTransfer rules package.

With all that configured, you will be able to set up a transfer site which, under the covers, calls the Connect:Direct Java API to talk to a Connect:Direct node which is either on the same box as ST or shares a disk with ST.

Note that ST cannot communicate with a remote C:D node, because we don't talk NDM. It also does not support Secure+ (though it can talk to a local C:D node which presumably then could talk Secure+ to another node) or Sterling Secure Proxy. In short, SecureTransport's C:D functionality is designed to integrate into an existing C:D network, and must have a local C:D note to do so.