IBM Sterling Connect:Direct: Difference between revisions

From Wiki
 
(34 intermediate revisions by the same user not shown)
Line 3: Line 3:


= IBM Connect:Direct =
= IBM Connect:Direct =
== Main Applications==
{| 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
|}


== Portas utilizadas pelas Soluções==
== Portas utilizadas pelas Soluções==
Line 20: Line 40:


* [[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 35: Line 63:
* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!
* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!


* [[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 =
* [[IBM Sterling Connect:Direct : Install C:D Web Services]]


* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]
* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]
Line 48: Line 83:
* [[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=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService, include Secure+ config]
* (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]


* [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService]
* [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.


* [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]
== Add C:D Nodes to 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]
 
== Manage C:D Nodes and Partners ==
 
* [[IBM Sterling Connect:Direct : Import C:D certificate on 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=rL91Oiru_Nc Change a partner using C:D WebService, include Secure+ configuration]
 
* (YouTube) [https://www.youtube.com/watch?v=VT7MIKXUAkE Trusted Certificate Management From Connect:Direct Node]
 
== Manage 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 60: Line 112:
* [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]


= IBM Connect:Direct File Agent =


* Habilitando o Integrated File Agent
 
== Usando a REST API do C:D WebServices ==
* [[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
  fileagent.enable=Y
Detalhes em [https://www.ibm.com/docs/en/SS4PJT_6.2.0/pdf/CDFA_pdf.pdf IBM® Connect:Direct File Agent 6.2]


* Convertendo do Standalone para o Integrated
* Convertendo do Standalone para o Integrated
Line 75: Line 132:


  cdfacfg -f Default_Config.json
  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]]
* [[IBM Sterling Connect:Direct File Agent: Funcionamento, Principais Comandos e Arquivos]]

Latest revision as of 19:20, 19 April 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

Portas utilizadas pelas Soluções

Origem Destino Porta(s) Função
Cliente C:D SSP Engine * Definido na configuração do Connect:Direct Proxy Server Adapter
C:D Cliente C:D Server 1363 port to listen for a Client connection request
C:D Server C:D Server 1364 port to listen for a remote connection request

Install, Commands and Configurations

Performance Tips

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

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

Ver também

Retrieved from "https://ebasso.net/wiki/index.php?title=IBM_Sterling_Connect:Direct&oldid=8742"