IBM Sterling Connect:Direct: Difference between revisions

From Wiki
 
(36 intermediate revisions by the same user not shown)
Line 4: Line 4:
= IBM Connect:Direct =
= IBM Connect:Direct =


== Portas utilizadas pelas Soluções==
== Main Applications==
 
[[file:Connect-direct-communication-path.png]]


{| class="wikitable"
{| class="wikitable"
|-
|-
! Origem !! Destino !! Porta(s) !! Função
! Process !! Description
|-
|-
| Cliente C:D || SSP Engine || * || Definido na configuração do Connect:Direct Proxy Server Adapter
| cdpmgr || main application daemon process
|-
|-
| C:D Cliente || C:D Server || 1363|| port to listen for a Client connection request
| cdstatm || the stats daemon that launches along with the cdpmgr
|-
|-
| C:D Server || C:D Server || 1364 || port to listen for a remote connection request
| 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 : Load Tests]] Draft!!!!
* [[IBM Sterling Connect:Direct: Configuring C:D to use Minio S3 Storage]]


* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!
== Performance Tips and High Availability==


* [[IBM Sterling Connect:Direct : Run Load Test on IBM Sterling Connect:Direct]]


== Containers and Kubernetes ==
* [[IBM Sterling Connect:Direct : Performance on AIX]] Draft!!!!


* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub
* [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]


= IBM Connect:Direct WebServices =
* [https://www.ibm.com/docs/en/connect-direct/6.3.0?topic=v63-high-availability#ID1753 High-Availability in C:D]


* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]
* [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 : Create User (Functional Authority) using C:D Web Services]]
* [[IBM Sterling Connect:Direct : Script to get process in HOLD and WAIT queue]]


* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]]
* [https://github.com/ebasso/sterling-b2b-samples/tree/master/connect-direct/cd-watch-shell Script to monitor Connect:Direct Unix 'cdwatch.sh' ]


* [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService, include Secure+ config]
== Containers and Kubernetes ==


* [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService]
* [https://github.com/ebasso/sterling-b2b-oncloud IBM Sterling: Deploy Connect:Direct on OpenShift at IBM Cloud - English Version] posted on GitHub


* [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]
* [[IBM Sterling Connect:Direct : Solving CrashLoopBackOff problems when deploying in Kubernetes/OpenShift]]


* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic]
= IBM Connect:Direct WebServices =
 
* [https://www.youtube.com/watch?v=heyPqKCr0ng Configure Integrate FileAgent using C:D WebService - Add Rule]
 
* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt]
 
* 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.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].


* [[IBM Sterling Connect:Direct : Install C:D Web Services]]
* [[IBM Sterling Connect:Direct : Install C:D Web Services]]


* Rest API
* [[IBM Sterling Connect:Direct : Enable tracing in C:D using C:D Web Services]]


Send file
* [[IBM Sterling Connect:Direct : Create User (Functional Authority) using C:D Web Services]]


{"processFile": "PP PROCESS \n SNODE=CDDEST \n STEP2 COPY \n FROM ( \n FILE=/connectd/cdinstall/ndm/cfg/msgfile.cfg \n ) \n TO ( \n FILE=/connectd/cdinstall/work/cddelete.me \n DISP=RPL \n ) \n PEND"}
* [[IBM Sterling Connect:Direct : Create a Transfer using C:D Web Services]]


Send file
* (YouTube) [https://www.youtube.com/watch?v=QgiiOtjHDeY Process Library Management using C:D WebService, create and store CD Process files]
{ "processFile": "/opt/cdunix/scripts/send_process.cdp" }


= IBM Connect:Direct File Agent =
* [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.


Detalhes em [https://www.ibm.com/docs/en/SS4PJT_6.2.0/pdf/CDFA_pdf.pdf IBM® Connect:Direct File Agent 6.2].
== Manage C:D Nodes and Partners ==


* Habilitando o Integrated File Agent, no initparm.cfg (Versão 6.2 ou superior)
* [[IBM Sterling Connect:Direct : Add a Connect:Direct Node in C:D WebService (Container Version)]]


fileagent.enable=Y
* [[IBM Sterling Connect:Direct : Import C:D certificates on C:D WebService]]


* Convertendo do Standalone para o Integrated
* (YouTube) [https://www.youtube.com/watch?v=y_tPtxRW4b4 Adding a Connect:Direct Node in C:D WebService]


cdfaconvertcfg -i <Standalone File Agent>.ser -o <Integrated File Agent>.json
* (YouTube) [https://www.youtube.com/watch?v=inRb0qMemBc Add a partner manually using C:D WebService, include Secure+ configuration]


* Verificando os arquivos
* (YouTube) [https://www.youtube.com/watch?v=rL91Oiru_Nc Change a partner using C:D WebService, include Secure+ configuration]


cdfacfg -f Default_Config.json
* (YouTube) [https://www.youtube.com/watch?v=VT7MIKXUAkE Trusted Certificate Management From Connect:Direct Node]


* Suporte ao AWS S3.
== Manage Integrated File Agent==


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]
* [[IBM Sterling Connect:Direct Integrated 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
* [https://www.youtube.com/watch?v=hE-su8DNDJE Configure Integrate FileAgent using C:D WebService - Basic]


aws s3 mv s3://mybucket/test.txt s3://mybucket/test2.sent_ok
* [https://www.youtube.com/watch?v=heyPqKCr0ng Configure Integrate FileAgent using C:D WebService - Add Rule]


ou
* [https://www.youtube.com/watch?v=CyZ4JJJl-EI Configure Integrate FileAgent using C:D WebService - Watch Directory Mgmt]
 
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]]
== Usando a REST API do C:D WebServices ==
* [[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

Manage C:D Nodes and Partners

Manage Integrated File Agent

Usando a REST API do C:D WebServices

Ver também