IBM Support

How to do a Silent Install of Connect:Direct for UNIX

How To


Summary

This presentation will show you how to setup your on-premise UNIX system to perform a Silent Installation of Connect:Direct for UNIX.
This will include providing a custom Netmap, Userfile, Secure+ configuration, and CA-signed certificates.

Objective

Provide step-by-step instructions to complete a Silent Install of Connect:Direct for UNIX on an on-premise system.
Once completed, this will give you a fully functional CDU server ready for use.
The CDU Silent Install process is documented here on the IBM Product documentation website.

Environment

The UNIX platform used is RHEL v9.5
The Connect:Direct for UNIX version used is v6.4.x.
NOTE: Ensure you have installed the required libraries as documented here.
NOTE: The CDU installation process needs read/write/execute permissions on the '/tmp' folder.
              Ensure that the 'noexec' flag is NOT set on the '/tmp' mount point.
NOTE: It is required to use 'root' to run the Silent Install process.

Steps

Step 1: Prepare the Silent Install Deployment Folder.
  • Create the desired directory structure.
  • Download and prepare the current CDU maintenance Fixpack.
  • Create and collect the required certificates.
  • Create the configuration files.
     A. Create a directory structure.
         Create a directory structure that appeals to you.
         The directory path to the Silent Install Deployment folder will be used in the configuration files.
         image-20250625093858-1
     B. Download the current CDU maintenance package from Fix Central.
         The current maintenance package is recommended so that all current defect and security vulnerability patches are in place along with all current
         features and enhancements.
         Place the Fixpack in the Silent Install Deployment folder.
         image-20250625095241-2         
     C. Un-tar the file:  tar -vxf <file_name.tar>
         image-20250625095553-3
         NOTES:
               i. The file 'cdinstall' is used to do an interactive install.
              ii. The file 'cdinstall_a' is used to do the Silent Install.
             iii. The file 'cdunix' is the cpio payload file that is used for the "cdai_cpioFile" parameter in the options file for the Silent Install.
     D. Create and gather certificates.
          NOTE: To do a Silent Install without needing to provide certificates, refer to the "No Certificate" section at the end of this document.
          1. Using openssl, create a Certificate Signing Request for your CDU server.
              Do this in a folder other than the Silent Install Deployment folder.
              This will create two files - the private key file and the CSR to be sent to your CA for signing.
              Example: 
     openssl req -newkey rsa:4096 -sha512 -keyout <distingueshed_name>_<mmddyyyy>_private_key.txt -out <distingueshed_name>_<mmddyyyy>_certreq.pem

image-20250625132238-1
image-20250625132555-3
          <<<Following are the contents of the two files:>>>
image-20250625133025-5
image-20250625133131-6
image-20250625133231-7
          2. Send the CSR to your CA for signing.
              Have the certificate signed as an Apache-style, x509, base64 encoded PEM format certificate.
          3. Combine the private key file with the CA-signed certificate file to create the key certificate file and place in the Silent Install Deployment folder.
image-20250625135328-8
image-20250625135404-9
image-20250625135435-10
          4. Collect the root and intermediate certificates in PEM format for your CA and from your remote trading partners and place in
              the Silent Install Deployment folder.
image-20250625141048-11
     E. Create the configuration files that will be imported during the Silent Install process.
          There are four configuration files that need to be created.
               netmap.silent
               userfile.silent
               spconfig.txt
               cdinstall_a install options
          These four files are placed in the Silent Install Deployment folder.
          NOTE: It is not necessary to create the netmap, userfile, or spconfig files.
                       The Silent Install process will create a minimal working CDU instance without these three files if desired.
 
          1. The netmap.silent file.
               a. Add and configure as many remote node records as you want.
               b. The records in this file are the same as is used in a production netmap.cfg file.
               c. This file is imported and appended to the existing netmap.cfg file created during the basic installation section for the Silent Install process.
               d. The import is accomplished using the 'cdai_appendNetmapFile' parameter in the Options file.
               e. Put this file in the Silent Install Deployment folder.
               Example:
               image-20250630094009-2
          2. The userfile.silent file.
               a. Add and configure as many Proxy and Local user records as you want.
               b. The records in this file are the same as is used in a production userfile.cfg file.
               c. This file is imported and appended to the existing userfile.cfg file created during the basic installation section for the Silent Install process.
               d. The import is accomplished using the 'cdai_appendUserFile' parameter in the Options file.
               e. Put this file in the Silent Install Deployment folder.
               Example:
               image-20250630093718-1
          3. The spconfig.txt file.
               a. The Silent Install process will launch the SPCLI and read in the contents of this file to fully configure the Secure+ settings.
               b. This file contains the exact commands you would enter at the SPCLI command prompt to import certificates and update
                    node records.
               c. Note the first command is to synchronize with the Netmap. This will be the Netmap created from your custom netmap.silent file.
               d. Ensure you have a command section for each node in the Netmap.
               e. Put this file in the Silent Install Deployment folder.
               f. For more detailed information on configuring Secure+, reference this Technote on the subject.
               Example:
image-20250626132504-5
image-20250626132626-6
          4. The cdinstall_a options file.
               a. These parameters are discussed in the CDU Silent Installation Documentation on the IBM Product documentation website.
               b. CDINSTALL_A looks for all of its files in the Silent Install Deployment folder unless otherwise specified.
               c. After the Silent Install is completed, the password values are removed from this file.
               d. Note the parameters for the key certificate and the Keystore.
               e. The 'cdai_trace' parameter creates a verbose install log. This is useful for problem determination if needed.
               f. Parameter values containing non-alphanumeric characters should be double quoted to ensure correct parsing.
               g. Put this file in the Silent Install Deployment folder.
               Working Example:
                image-20250702080230-1
              NOTES:
                   i. The 'Install Agent' component is used with Control Center Director. The 'Install Agent' component is a forced install, can't disable this.
                      If you intend to use Control Center Director, you will need to set the Install Agent parameters cdai_agentEnable, cdai_agentOSAurl,
                      cdai_agentOSADisable, cdai_agentBackupLocation, and cdai_agentInstallerLocation parameters to appropriate values.
                      If you will not be using Control Center Director, set "cdai_agentEnable=n" and "cdai_agentOSADisable=y" and do not include the 
                      cdai_agentOSAurl, cdai_agentBackupLocation, and cdai_agentInstallerLocation parameters in the options file.
                 ii. Integrated File Agent is optionally installed. Even if you do not intend to use the Integrated File Agent, it is recommended that you install
                     the component and set "cdai_fileAgentEnable=n" to leave this service disabled. This will leave the component disabled but still be updated
                     with patches and enhancements going forward in case you decide to use it in the future.
                iii. CDU uses two file backup locations - cdai_cdBackupLocation and cdai_erInstallerLocation. You can leave these in the default locations
                      or set your own locations.
     F. Import custom translation tables.
         a. The Silent Install process can import custom translation tables.
         b. The table files need to have a '.sxlt' extension.
             The Silent Install process will automatically detect files with this extension.
         c. The table files must not be compiled.
             The Silent Install process will compile the table files during processing.
         d. Put these files in the Silent Install Deployment folder.
         e. Read this section of the CDU Utilities Documentation on the IBM Product documentation website for more information.
     G. Use of native Aspera FASP (HSAO v1) is deprecated.
          Aspera faspio Gateway (HSAO v2) is now available for this service.
          Reference this Technote for information on using Aspera faspio Gateway with Connect:Direct.
     This completes the preparation work needed to perform a Silent Install of Connect:Direct for UNIX.
     Following is a final example of the contents of the Silent Install Deployment folder.
     image-20250630094352-4
STEP 2: Performing the Silent Installation Process.
     A. Navigate to the Silent Install Deployment folder.
     B. Switch to the 'root' user ID.
          1. This is required to set 'root' ownership of specific folders and files and to create the SACL folder and file.
          2. All other folders and files will be owned by the admin user ID specified in the Silent Install options file.
     C. Execute the command string.
     ./cdinstall_a -f cdai_options.txt
          1. A basic installation is performed first including creating a minimal Netmap and Userfile.
              A Basic Secure+ configuration is also done.
          2. Custom translation tables are imported if provided.
          3. Custom Netmap and Userfile files are imported.
          4. The custom Secure+ configuration is performed.
          5. The CDU service is started.
          6. A Loopback (Pnode=Snode) process is submitted and verified for completion to test the CDU server.
          Example of output from running the Silent Install.
          As you can see, the CDU service, Integrated File Agent service, and the Control Center Install Agent service are all running.
          image-20250702084227-2
     D. Examine the log files.
          1. Several log files are created - all owned by 'root'
              Example:
              image-20250702085756-3
              
          2. The 'cdaiLog.txt' file is the main log that shows the installation process details.
               a. Examine the log.
                   You want to see "finalRC=0" on the last line indicating a successful Silent Install.
                   image-20250702090649-4
             b. If the final return code is not '0', then scan through the 'cdaiLog' file checking for error conditions and make needed corrections.
             c. If you still can not get the Silent Install to complete successfully, then open a Case with CDU Support and gather the information
                 as noted in this Technote.
STEP 3: Testing the new CDU Installation.
     A. Change to the /<cdu_install_path>/ndm/bin folder.
     B. Set the NDMAPICFG environment parameter.
     export NDMAPICFG=/<cdu_install_path>/ndm/cfg/cliapi/ndmapi.cfg
     C. Enter './direct' to launch the CLI.
          1. Submit the 'sample.cd' process.  
        Direct>  submit file=sample.cd;
              This is a Loopback (Pnode=Snode) process.
              Note the given process number.
          2. Examine the Statistics for the process to verify that the CDU server is working properly.  
        Direct>  select statistics pnum=5 recids=ctrc detail=yes;
         Example output:
         image-20250715100319-1
           image-20250702095750-8
          3. The Copy Termination Record (CTRC) shows that the copy step was successful and it also shows that Secure+ was used along with the
               certificates that were installed during the Silent Install.
The CDU Silent Installation is now complete.
Notes for how to perform a CDU Silent Installation without providing certificates.
     A. You will follow the guidance provided in this document to setup a CDU Silent Installation.
     B. The CDU Silent Installation process forces the installation of the Secure+ component.
          This is unavoidable and can not be disabled.
          Therefore, you are required to provide the password for the Keystore in the options file.
                cdai_keystorePassword=Passw0rd
          Otherwise, the Silent Install will fail.
     C. To avoid the need to provide certificates for the CDU Silent Install process, you will create a "Secure+ configuration file" as noted in Step 1, section E3 above.
          But you will name the configuration file 'no_spconfig.txt'.
          Create the file and add the following single line.
     quit;
         That is all, just this one line.
     D. You will then include the following parameter in the options file to point to this file.
      cdai_spConfig="no_spconfig.txt"
     E. Now run the Silent Install process. The installation will complete without the need for certificates or configuring Secure+.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSKTYY","label":"IBM Sterling Connect:Direct for UNIX"},"ARM Category":[{"code":"a8m0z000000cwUmAAI","label":"INSTALLATION PROBLEM"}],"ARM Case Number":"","Platform":[{"code":"PF061","label":"UNIX"}],"Version":"6.3.0;6.4.0"}]

Document Information

Modified date:
15 July 2025

UID

ibm17237972

Page Feedback