IBM Sterling B2B Integrator: Difference between revisions

From Wiki
 
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
{| class="wikitable"
|-
! Context !! Description
|-
| http://<server>:5000/dashboard || Sterling B2Bi Administration
|-
| http://<server>:5000/dashboard || Sterling File Gateway
|-
| http://<server>:5078/B2BAPIs/svc || Sterling B2Bi API
|-
| http://<server>:5078/propertyUI/app || Sterling B2Bi Customization Admin
|-
| http://<server>:5078/swiftapis || SWIFT REST API (available on version 6.2)
|-
| http://<server>:5078/pgpapis || PGP REST API (available on version 6.2)
|-
| http://<server>:5078/sfgapis || SFG REST API (available on version 6.2)
|}
== IBM Sterling B2Bi Container Network Topology ==
[[File:Ibm-sterling-openshift-network.png|center]]
== Performance Tuning e Troubleshooting ==
* [[IBM Sterling B2B: Usando o JMeter para realizar testes de carga]]
* [[IBM Sterling B2B: Run FTP Load Test on Sterling B2B Integrator]]
* [[IBM Sterling B2B: Run SFTP Load Test on Sterling B2B Integrator]]
* [[IBM Sterling B2B: Configuring SB2Bi to use S3 Storage Provider]]
* [[IBM Sterling B2B: Meu arquivo customer_overrides.properties]]
* [[IBM Sterling B2B: Limpeza de Arquivos]]
* [[IBM Sterling B2B: Limpeza de Tabelas e DataSweeper]]
* Reduce log level on B2B
* [[IBM Sterling B2B: Archive e Purge]]
* [[IBM Sterling B2B: Analisando Logs]]
* [[IBM Sterling B2B: Execução do HealthCheck]]
* [[IBM Sterling B2B: Troubleshooting problemas com CPU Alta]]
== Comandos, Dicas e Procedimentos ==
* [[IBM Sterling B2B: Dicas e Ajustes Rápidos]]
* [[IBM Sterling B2B: Execução de um Business Process via Linha de Comando]]
* [[IBM Sterling B2B: Criando Usuários no B2Bi usando o XAPI]]
* [[IBM Sterling B2B: Autenticando no B2Bi via LDAP (sem o SEAS)]]
* [[IBM Sterling: Configurando o Single Sign-on entre o SSP, SEAS, B2BI e SFG]]
* [[IBM Sterling B2B: Map Editor]]
* [[IBM Sterling B2B: Permissões e Controle de Acesso]]
* [[IBM Sterling B2B: Principais comandos no Docker]]
* [[IBM Sterling B2B: Check-in de uma chave pública SSH (SSH Known Host Key)]]
== Integração Sterling B2Bi com Connect:Direct ==
Criei uma nomenclatura para facilitar a utilização do protocolo C:D no Sterling B2B
- Sterling B2B
|- Deployment > Service > Configuration > CD Server Adapter
    - CDSA Name: SINODE01
      - CD Node Name: SINODE01
      - Server Port: 5364
      - Netmap: SINODE01_NETMAP
|- Deployment > Adapter Utilities > Sterling C:D > Nodes
    - CD Node Name: CDNODE01
      - IP/Port: 192.x.x.1:1364
    - CD Node Name: CDNODE02
      - IP/Port: 192.x.x.1:2364
|- Deployment > Adapter Utilities > Sterling C:D > NetMap
    - Netmap Name: SINODE01_NETMAP
|- Deployment > Adapter Utilities > Sterling C:D > NetMap +REF
    - Netmap Name: SINODE01_NETMAP
      - Add Node Name: CDNODE01
      - Add Node Name: CDNODE02
- Connect:Direct --> CDNODE01
|- Netmap.cfg:
    SINODE01:\
    ...
    :comm.info=SINODE01;5364:\
* [[IBM Sterling B2B: Criando um Connect:Direct Server Adapter]]
* [[IBM Sterling B2B: Configurando a conexão do B2Bi-SFG para um Node C:D]]
* [[IBM Sterling Connect:Direct: Configurando a conexão para um Node C:D ou C:D Server Adapter]]
== SQL Queries ==
* [[IBM Sterling B2B: SELECT a Code List]]
* [[IBM Sterling B2B: SELECT Queue, Lifespan, PersistentLevel of Business Process]]
* [[IBM Sterling B2B: Queries for Archive]]
* [[IBM Sterling B2B: Queries for Certificates Management]]
* [[IBM Sterling B2B: Queries to collect locked sessions of Connect:Direct]]
== Instalação ==
== Instalação ==


Line 8: Line 124:


* [[IBM Sterling B2B: Install on Docker for Development]]
* [[IBM Sterling B2B: Install on Docker for Development]]
= Portas utilizadas pelo Sterling B2B=
Muito útil quando pedir liberação de firewall
* '''<base_port>''': definido durante a instalação. Costumo utilizar a porta 5000
[https://www.ibm.com/support/pages/node/176423 How does Gentran Integration Suite use the ports allocated during installation? (SCI90362)]
{| class="wikitable sortable"
|-
! Origem !! Destino !! Porta(s) !! Função
|-
| Web Browser || B2Bi/SFG || 5000 (http)<br>5001 (https)  || Definido durante a instalação. Acesso ao Dashboard do B2Bi, Filegateway, MyFilegateway 2.0. Costumo utilizar a porta 5000, <base_port>(http)<br><base_port + 1>(https)
|-
| Cliente SFTP || B2Bi/SFG || 5022 || Definido na configuração do SFTP Server Adapter.Costumo utilizar a porta 5022.
|-
| Cliente FTP/FTPs || B2Bi/SFG || 5021  || Definido na configuração do FTP Server Adapter.Costumo utilizar a porta 5021.
|-
| Cliente HTTP(s) || B2Bi/SFG || * || Definido na configuração do HTTP Server Adapter.
|-
| Mapper || B2Bi/SFG || 5033(MAPTEST_HTTP_SERVER_PORT) || Map Test
|-
| SOAP Client || B2Bi/SFG || 5040(SOA_PORT)<br>5041(SOA_SSL_PORT) || Definido na configuração do SOAP/HTTP Server Adapter
|-
| Rest Client || B2Bi/SFG || 5060<br>5061(secure) || Definido na configuração do Rest/HTTP Server Adapter
|-
| B2Bi/SFG || Perimeter Server || <base_port + 2> || Definido na instalação do Perimeter Server
|-
| B2Bi/SFG || LDAP || 389 (ldap)<br>636 (ldaps)<br>3268 (MSAD) ||
|-
| B2Bi/SFG || DB2 || 50000 ||
|-
| B2Bi/SFG || Oracle || 1521 ||
|-
| Admin Console (Web Browser) || Control Center Monitor|| 58082 (http)<br>58083 (https) || Acesso ao Dashboard Web do Control Center
|-
| Control Center Console || Control Center Monitor|| 58080 <br>58081 (secure) || Acesso ao Control Center
|-
| Control Center Monitor || DB2 || 50000 ||
|-
| Control Center Monitor|| Oracle || 1521 ||
|-
| Control Center Director|| C:D Server || 1365 ||
|-
| Admin Console (Web Browser) || SEAS || 9080 || Acesso ao console de administração
|-
| Seas GUI || SEAS || 61365 <br>61366 (secure) ||
|-
| B2Bi/SFG || SEAS || 61365 <br>61366 (secure) ||
|-
| SSP Engine || SEAS || 61365 <br>61366 (secure) ||
|-
| SEAS || LDAP || 389 (ldap), 636 (ldaps) ||
|-
| Admin Console (Web Browser) || SSP Configuration Manager || 8443 || Example
|-
| SSP Configuration Manager || SSP Engine || 63366 || Example
|-
| Cliente SFTP || SSP Engine || * || Definido na configuração do SFTP Proxy Server Adapter
|-
| Cliente FTPs || SSP Engine || * || Definido na configuração do FTP Proxy Server Adapter
|-
| Cliente HTTP(s) || SSP Engine || * || Definido na configuração do HTTP Proxy Server Adapter
|-
| 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
|}





Latest revision as of 20:42, 25 September 2024

Context Description
http://<server>:5000/dashboard Sterling B2Bi Administration
http://<server>:5000/dashboard Sterling File Gateway
http://<server>:5078/B2BAPIs/svc Sterling B2Bi API
http://<server>:5078/propertyUI/app Sterling B2Bi Customization Admin
http://<server>:5078/swiftapis SWIFT REST API (available on version 6.2)
http://<server>:5078/pgpapis PGP REST API (available on version 6.2)
http://<server>:5078/sfgapis SFG REST API (available on version 6.2)

IBM Sterling B2Bi Container Network Topology

Performance Tuning e Troubleshooting

  • Reduce log level on B2B

Comandos, Dicas e Procedimentos

Integração Sterling B2Bi com Connect:Direct

Criei uma nomenclatura para facilitar a utilização do protocolo C:D no Sterling B2B

- Sterling B2B
|- Deployment > Service > Configuration > CD Server Adapter
   - CDSA Name: SINODE01
     - CD Node Name: SINODE01 
     - Server Port: 5364
     - Netmap: SINODE01_NETMAP

|- Deployment > Adapter Utilities > Sterling C:D > Nodes
   - CD Node Name: CDNODE01
     - IP/Port: 192.x.x.1:1364
   - CD Node Name: CDNODE02
     - IP/Port: 192.x.x.1:2364

|- Deployment > Adapter Utilities > Sterling C:D > NetMap
   - Netmap Name: SINODE01_NETMAP

|- Deployment > Adapter Utilities > Sterling C:D > NetMap +REF
   - Netmap Name: SINODE01_NETMAP
     - Add Node Name: CDNODE01
     - Add Node Name: CDNODE02
- Connect:Direct --> CDNODE01
|- Netmap.cfg: 
   SINODE01:\
   ...
   :comm.info=SINODE01;5364:\


SQL Queries

Instalação


Portas utilizadas pelo Sterling B2B

Muito útil quando pedir liberação de firewall

  • <base_port>: definido durante a instalação. Costumo utilizar a porta 5000

How does Gentran Integration Suite use the ports allocated during installation? (SCI90362)

Origem Destino Porta(s) Função
Web Browser B2Bi/SFG 5000 (http)
5001 (https)
Definido durante a instalação. Acesso ao Dashboard do B2Bi, Filegateway, MyFilegateway 2.0. Costumo utilizar a porta 5000, <base_port>(http)
<base_port + 1>(https)
Cliente SFTP B2Bi/SFG 5022 Definido na configuração do SFTP Server Adapter.Costumo utilizar a porta 5022.
Cliente FTP/FTPs B2Bi/SFG 5021 Definido na configuração do FTP Server Adapter.Costumo utilizar a porta 5021.
Cliente HTTP(s) B2Bi/SFG * Definido na configuração do HTTP Server Adapter.
Mapper B2Bi/SFG 5033(MAPTEST_HTTP_SERVER_PORT) Map Test
SOAP Client B2Bi/SFG 5040(SOA_PORT)
5041(SOA_SSL_PORT)
Definido na configuração do SOAP/HTTP Server Adapter
Rest Client B2Bi/SFG 5060
5061(secure)
Definido na configuração do Rest/HTTP Server Adapter
B2Bi/SFG Perimeter Server <base_port + 2> Definido na instalação do Perimeter Server
B2Bi/SFG LDAP 389 (ldap)
636 (ldaps)
3268 (MSAD)
B2Bi/SFG DB2 50000
B2Bi/SFG Oracle 1521
Admin Console (Web Browser) Control Center Monitor 58082 (http)
58083 (https)
Acesso ao Dashboard Web do Control Center
Control Center Console Control Center Monitor 58080
58081 (secure)
Acesso ao Control Center
Control Center Monitor DB2 50000
Control Center Monitor Oracle 1521
Control Center Director C:D Server 1365
Admin Console (Web Browser) SEAS 9080 Acesso ao console de administração
Seas GUI SEAS 61365
61366 (secure)
B2Bi/SFG SEAS 61365
61366 (secure)
SSP Engine SEAS 61365
61366 (secure)
SEAS LDAP 389 (ldap), 636 (ldaps)
Admin Console (Web Browser) SSP Configuration Manager 8443 Example
SSP Configuration Manager SSP Engine 63366 Example
Cliente SFTP SSP Engine * Definido na configuração do SFTP Proxy Server Adapter
Cliente FTPs SSP Engine * Definido na configuração do FTP Proxy Server Adapter
Cliente HTTP(s) SSP Engine * Definido na configuração do HTTP Proxy Server Adapter
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


Ver também