IBM Sterling Connect:Direct: Difference between revisions

From Wiki
No edit summary
Line 111: Line 111:
== 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]]
= IBM Connect:Direct Integrated File Agent (Versão 6.2 ou superior) =
Detalhes em [https://www.ibm.com/docs/en/SS4PJT_6.2.0/pdf/CDFA_pdf.pdf 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 [https://www.ibm.com/support/pages/aws-s3-bucket-access-connect-direct-file-agent 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
* [[IBM Sterling Connect:Direct File Agent: Funcionamento, Principais Comandos e Arquivos]]


= Ver também =
= Ver também =

Revision as of 15:05, 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

Containers and Kubernetes

IBM Connect:Direct WebServices

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

Ver também