IBM Sterling Connect:Direct: Difference between revisions
| (26 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
= IBM Connect:Direct = | = IBM Connect:Direct = | ||
== | == Main Applications== | ||
[[file:Connect-direct-communication-path.png]] | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! | ! 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 | |||
|} | |} | ||
| Line 20: | Line 29: | ||
* [[IBM Sterling Connect:Direct : Instalação]] | * [[IBM Sterling Connect:Direct : Instalação]] | ||
* [[IBM Sterling Connect:Direct : Silent Install]] | |||
* [[IBM Sterling Connect:Direct : Start/Stop Script with SystemD Support]] | |||
* [[IBM Sterling Connect:Direct : Instalação da versão C:D Container]] | |||
* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]] | * [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]] | ||
* [[IBM Sterling Connect:Direct : Principais Comandos e Arquivos]] | * [[IBM Sterling Connect:Direct : Principais Comandos e Arquivos]] | ||
* [[IBM Sterling Connect:Direct : Dicas do comando Select Statistics|IBM Sterling Connect:Direct : Dicas do comando 'Select Statistics' ]] | |||
* [[IBM Sterling Connect:Direct: Error LTQA032I - database corruption]] | * [[IBM Sterling Connect:Direct: Error LTQA032I - database corruption]] | ||
| Line 29: | Line 46: | ||
* [[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 ]] | ||
== Performance Tips == | * [[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== | |||
* [[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!!!! | ||
* [https://public.dhe.ibm.com/software/commerce/doc/mft/cdunix/whitepapers/CDU_VCS_Whitepaper.pdf Connect:Direct for UNIX in the Veritas Cluster Server Environment] | |||
* [https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=v63-high-availability#ID1753 High-Availability in C:D] | |||
* [https://www.ibm.com/support/pages/system/files/inline-files/Running_CD_UNIX_behind_a_load_balancer_0.pdf Considerations for Running Connect:Direct for UNIX Behind a Load Balancer] | |||
* [[IBM Sterling Connect:Direct : Script to get process in HOLD and WAIT queue]] | |||
* [https://github.com/ebasso/sterling-b2b-samples/tree/master/connect-direct/cd-watch-shell Script to monitor Connect:Direct Unix 'cdwatch.sh' ] | |||
== Containers and Kubernetes == | == Containers and Kubernetes == | ||
* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub | * [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub | ||
* [[IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift]] | |||
= IBM Connect:Direct WebServices = | = IBM Connect:Direct WebServices = | ||
| Line 50: | Line 82: | ||
* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]] | * [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]] | ||
* [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files | * (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files] | ||
* [https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=file-local-user-information-record-format You can grant specific privileges to the users using the userfile record]. | * [https://www.ibm.com/docs/en/connect-direct/6.2.0?topic=file-local-user-information-record-format 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. | ** 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 Partners == | == 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]] | |||
* (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 67: | 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 73: | 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 == | ||
* [[IBM Sterling Connect:Direct : Usando a REST API do C:D WebService]] | * [[IBM Sterling Connect:Direct : Usando a REST API do C:D WebService]] | ||
= Ver também = | = Ver também = | ||
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.