1. Connect:Direct for UNIX v4.2.x Silent Installation
Presented by
Aloysius J Connor
January 2017

2. Introduction
This presentation will show you how to setup your UNIX system to perform a Silent Installation of Connect:Direct for UNIX v4.2.x.
Including a custom Netmap, Userfile, and Secure+ configuration.
The OS platform used for this document is
Red Hat Linux Server v6.5 (Santiago).
Much of this information is available in the
Enterprise Deployment Guide – Silent Install
p.mass_deploy.doc/CDUW_CDForUNIXSilentInstallation.html
Click to add your own notes.

3. STEP 1: Prepare the Silent Install Deployment Folder.
Create the desired directory structure.
Download and prepare the FixPack.
Create and collect the required certificates.
Create the configuration files.
Make required changes to cdinstall_a.

4. 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.

5. b. Download the C:D UNIX v4.2.x FixPack.
Download the desired FixPack from IBM Fix Central.
Unpack the ‘.Z’ file.
gzip –d file_name.Z
Extract the ‘cdinstall’ and ‘cdinstall_a’ files.
cpio –ivdmB < file_name cdinstall
cpio –ivdmB < file_name cdinstall_a
Move all three files to the Silent Installation Deployment folder.

6. c. Create and gather certificates.
Using Certificate Wizard or other certificate tool, create a self-signed key certificate or a Certificate Signing Request for your C:D Server.
Collect the root and intermediate certificates for the remote C:D severs.
Be sure to include the certificates for your new C:D server.
Put all of these certificate files in the Silent Install Deployment folder.

7. d. Create the configuration files.
There are four configuration files that need to be created.
netmap.cfg
userfile.cfg
spconfig.txt
cdinstall_a install options
The four files are placed in the Silent Install Deployment folder.
Optional file for installing custom translation tables.
Silent Install
CDINSTALL_A Options
Secure+ Configuration
Netmap/UserFile Configuration

8. The netmap.cfg file
Add in and configure as many remote node records as you want.
The ‘local.node’ and ‘tcp.ip.default’ records are required.
Ensure there is a record for the local node.
This file is imported and overwrites the existing netmap.cfg file created during the basic installation section of the Silent Install.
The file contents mirrors the contents of a regular production netmap.cfg file.
Put this file in the Silent Install Deployment folder.

9. The userfile.cfg file
Add in and configure as many proxy and user records as you want.
Ensure you have the administrator ID listed.
This file is imported and overwrites the existing userfile.cfg file created during the basic installation section of the Silent Install.
The file contents mirrors the contents of a regular production userfile.cfg file.
Put this file in the Silent Install Deployment folder.

10. The spconfig.txt file.
The Silent Install process will launch the SPCLI and read in the contents of this file to fully configure the Secure+ settings.
Contains the exact commands as you would type at the SPCLI command prompt to import certificates and update a node record.
Note the first command is to sync with the Netmap. This will be the Netmap created from your custom netmap.cfg file.
Ensure you have a command section for each node in the Netmap.
Put this file in the Silent Install Deployment folder.

11. The cdinstall_a options file.
These parameters are discussed in the Enterprise Deployment Guide.
CDINSTALL_A looks for all of its files in the deployment folder unless another path is specified.
After the Silent Install is run, the Password values are removed from this file.
Note the parameters for the Certificate Keystore.
Put this file in the Silent Install Deployment folder.

12. Import custom translation tables.
The Silent Install can import custom translation tables.
The table file needs to have a ‘.sxlt’ extension.
The table file must not be compiled.
The Silent Install will compile the table file during processing.
Put these files in the Silent Install Deployment Folder.
Read this section of the online guide for more information.
p.cd52.unix.doc/com.ibm.help.cdunix_user.doc/CDU_Compiling_Translatio n_Table_.html

13. Modify the cdinstall_a script
This modification is required so that Secure+ is configured properly.
This section of the Silent Install script is located at the end of the file.
In the original cdinstall_a, Secure+ is configured before the custom Netmap is imported. This results in the nodes not being configured for Secure+.
An RTC has been opened to resolve this issue.
NOTE: This issue is resolved with CDU v iFix056. If you use this version, you do not need to make this modification.
Original
Modified

14. Prepare the Silent Install Deployment Folder - Wrap-up
This completes the preparation work needed to perform a Silent Install of C:D UNIX v4.2.x.
This is an example of the contents of the Deployment Folder.

15. STEP 2. Doing the Silent Install Process.
Ignore the “line 1534” message – irrelevant. An RTC has been opened to correct this.
NOTE: This issue has been resolved in CDU v iFix56.
Navigate to the Silent Install Deployment folder.
Switch to the ‘root’ ID.
Required to set ‘root’ ownership of specific files and to create the SACL.
The files and folders will be owned by the admin ID specified in the install options file.
Execute the command string.
cdinstall_a –f cd_inst_opt.txt
A basic installation is performed first including creating a minimal Netmap and Userfile. Also a basic Secure+ configuration is done.
Custom translation tables are imported.
Custom Netmap and Userfile files are imported.
Finally, the custom Secure+ configuration is performed.

16. Examine the Log files.
Several log files are created – all owned by ‘root’.
The ‘cdaiLog.txt’ file is the main log that shows the installation process and results.
You want to see “finalRC=0” indicating a successful installation.
If the final return code is not ‘0’, scan through the log file for the errors and make needed corrections.

17. Testing the new CDU v4.2 installation
Change directory to the /ndm/bin folder.
Enter ‘direct’ to bring up the CLI.
Submit the ‘sample.cd’ process. Note the process number.
Pull the statistics for the process to verify that the C:D server is working.

18. Testing with C:D Requester
Add the new C:D server to the Requester.
Create a process to send a file to another node.
Use ‘Select Statistics’ to verify the success of the process.

19. Summary of the Connect:Direct for UNIX Silent Installation
Preparing the Silent Install Deployment folder.
Doing the Silent Install and checking your work.
THANK YOU!