IBM Sterling Connect:Direct: Difference between revisions
| (7 intermediate revisions by the same user not shown) | |||
| Line 31: | Line 31: | ||
* [[IBM Sterling Connect:Direct : Silent Install]] | * [[IBM Sterling Connect:Direct : Silent Install]] | ||
* [[IBM Sterling Connect:Direct : Silent Install without provide certificates]] | |||
* [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]] | * [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]] | ||
| Line 51: | Line 53: | ||
* [[IBM Sterling Connect:Direct: Configuring C:D to use Azure Blob Storage]] | * [[IBM Sterling Connect:Direct: Configuring C:D to use Azure Blob Storage]] | ||
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage provide an AWS credentials file as a volume]] | |||
* [[IBM Sterling Connect:Direct: Using extraVolume and extraVolumeMounts in IBM Connect:Direct Deployments]] | |||
== Secure+ == | |||
* [[IBM Sterling Connect:Direct : Secure+ Sample file]] | |||
* [https://www.ibm.com/support/pages/setting-basic-secure-configuration-using-secure-command-line-interface-spcli?view=full Setting Up A Basic Secure+ Configuration Using The Secure+ Command Line Interface (SPCLI)] | |||
* [https://www.ibm.com/support/pages/how-do-silent-install-connectdirect-unix How to do a Silent Install of Connect:Direct for UNIX] | |||
== Performance Tips and High Availability== | == Performance Tips and High Availability== | ||
| Line 103: | Line 117: | ||
* [[IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services]] | * [[IBM Sterling Connect:Direct : Certificate-Based Authentication Setup using C:D Web Services]] | ||
* [[IBM Sterling Connect:Direct : C:D WebService - Annotations to Create a Network Load Balancer (NLB) service]] | |||
== Manage C:D Nodes and Partners == | == Manage C:D Nodes and Partners == | ||
Latest revision as of 01:51, 20 May 2026
IBM Connect:Direct, IBM C:D WebServices e C:D File Agent
IBM Connect:Direct
Main Applications
| Process | Description |
|---|---|
| cdpmgr | main application daemon process |
| cdstatm | the stats daemon that launches along with the cdpmgr |
| ndmcmgr |
command manager which is spawned off from cdpmgr The ndmcmgr is defined in the netmap local.node api perimeter and normally limited to 16. If these are long time running then most likely the session did not come down gracefully so they get zombied, which shows up as stuck temp files under the work/node directory. You should code the api timeout perimeter in the local.node entry in the netmap. |
| ndmsmgr | the session manager |
| ndmumgr | the user manager for the lack of better words. You will see this when a download/upload is coded for the proxy or local id |
Install, Commands and Configurations
Secure+
Performance Tips and High Availability
CD Process Files - Samples
- Send file from C:D UNIX to Sterling B2B Mailbox
- Send file from C:D UNIX to Sterling B2B Business Process
- Submit a file using a command line in C:D MS-Windows
- Put a file in S3 Bucket
- Get a file from S3 Bucket
Containers and Kubernetes
IBM Connect:Direct WebServices
- You can grant specific privileges to the users using the userfile record.
- Anyone that wants to login to the CDU server via the CDWS Web Console will need to have a 'local user' record in the userfile.cfg file.