IBM Sterling Connect:Direct: Difference between revisions
No edit summary |
|||
| Line 46: | 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 == | == Performance Tips and High Availability== | ||
* [[IBM Sterling Connect:Direct : Load Tests]] Draft!!!! | * [[IBM Sterling Connect:Direct : Load Tests]] Draft!!!! | ||
* [[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://public.dhe.ibm.com/software/commerce/doc/mft/cdunix/whitepapers/CDU_VCS_Whitepaper.pdf Connect:Direct for UNIX in the Veritas Cluster Server Environment] | ||
| Line 63: | Line 57: | ||
* [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] | * [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 == | ||
Revision as of 15:03, 7 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
- IBM Sterling Connect:Direct : Load Tests Draft!!!!
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.
Add C:D Nodes to C:D WebService
Manage C:D Nodes and Partners
Manage Integrated File Agent
Usando a REST API do C:D WebServices
IBM Connect:Direct Integrated File Agent (Versão 6.2 ou superior)
Detalhes em IBM® Connect:Direct File Agent 6.2.
- Habilitando o Integrated File Agent, no initparm.cfg (Versão 6.2 ou superior)
fileagent.enable=Y
- Convertendo do Standalone para o Integrated
cdfaconvertcfg -i <Standalone File Agent>.ser -o <Integrated File Agent>.json
- Verificando os arquivos
cdfacfg -f Default_Config.json
- Suporte ao AWS S3.
O File Agent suporta monitorar novos arquivos em um bucket do S3. Detalhes em AWS S3 Bucket access from Connect Direct File Agent
O File agente não move os arquivos após processamento, deve ser realizado via o C:D Process. Neste caso podemos utilizar o comando
aws s3 mv s3://mybucket/test.txt s3://mybucket/test2.sent_ok
ou
aws s3 mv s3://mybucket/test.txt s3://mybucket2/
dentro do RUNSTATS.
Mais detalhes em: https://awscli.amazonaws.com/v2/documentation/api/2.0.33/reference/s3/mv.html