IBM Sterling Connect:Direct: Difference between revisions
| (8 intermediate revisions by the same user not shown) | |||
| Line 45: | Line 45: | ||
* [[IBM Sterling Connect:Direct: Run Task ends with 0000000C/SRTS008I on C:D zOS ]] | * [[IBM Sterling Connect:Direct: Run Task ends with 0000000C/SRTS008I on C:D zOS ]] | ||
* [[IBM Sterling Connect:Direct: Configuring C:D to use AWS S3 Storage]] | |||
* [[IBM Sterling Connect:Direct: Configuring C:D to use Minio S3 Storage]] | |||
== Performance Tips and High Availability== | == Performance Tips and High Availability== | ||
* [[IBM Sterling Connect:Direct : Load | * [[IBM Sterling Connect:Direct : Run Load Test on IBM Sterling Connect:Direct]] | ||
* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!! | * [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!! | ||
| Line 83: | Line 87: | ||
** 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. | ** 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. | ||
== | == Manage C:D Nodes and Partners == | ||
* [[IBM Sterling Connect:Direct : Add a Connect:Direct Node in C:D WebService (Container Version)]] | |||
* [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]] | * [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]] | ||
* (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService] | * (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService] | ||
* (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration] | * (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration] | ||
| Line 100: | Line 102: | ||
== Manage Integrated File Agent== | == Manage Integrated File Agent== | ||
* [[IBM Sterling Connect:Direct Integrated File Agent]] | |||
* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic] | * [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic] | ||
| Line 106: | Line 110: | ||
* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt] | * [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt] | ||
== Usando a REST API do C:D WebServices == | == Usando a REST API do C:D WebServices == | ||
Latest revision as of 21:19, 20 September 2024
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
Performance Tips and High Availability
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.